A node-locked license (also known as a “fixed” license or a “CPU lock” license) enables a licensed application to run on the system (workstation or server) where the node-locked license is installed. Typically, a node-locked license is created for a specific system.

Installing a node-locked license is simple: a vendor ID and a license password are entered in the file /var/netls/nodelock (/usr/netls/nodelock in IRIX Release 5.0 and earlier). After that, the licensed product can run on the system with the nodelock file. Installing a node-locked license is explained in Chapter 3, “Installing Node-locked Licenses.”

Typically, a node-locked licensed product can be used simultaneously by multiple users on the licensed system.

A concurrent license (also known as a “concurrent access” or “floating” license) enables licensed applications to run on any system on the network. A concurrent license limits the maximum number of systems simultaneously executing the product. For example, if the number of nodes listed for a concurrent license is five, then users on no more than five systems on the network can be running the licensed product at any one time. Typically, a concurrent license is created for a specific system. This is the system where the license must be installed.

Installing a concurrent license is more complicated than installing a node-locked license. The network must have one or more systems set up as Global Location Brokers. In addition, the system that is listed on the license information sheet must be set up as a Network License Server (these terms are defined in “System Roles for Concurrent Licensing” in this chapter). The concurrent license can then be installed on the system using the ls_admin(1M) command. These procedures are explained in Chapter 4, “Setting Up Global Location Brokers and Network License Servers,” and Chapter 5, “Installing Concurrent Licenses.”

With NetLS, the effect of a site license is achieved by installing concurrent licenses equal to the number of systems at the site.

Temporary licenses (also known as provisional licenses) expire in a relatively short period of time, typically four months or less. Some temporary licenses can be used on any system and some can be used only on a specific system. Temporary licenses are sometimes included with new software so that the software can be used immediately. When a license is included with new software, license information appears on a label that is affixed to a Software License Registration card. Temporary licenses are also issued for demonstration software and in various emergency situations.

When a temporary license is due to expire soon, some applications display a notifier to remind you that the software will be inoperable in a short time. To replace a temporary license with a permanent license, contact Silicon Graphics or your local service provider (see “Completing the Software License Registration Card” in Chapter 2).

Permanent licenses expire in a very long time, often in the year 2038. Once you have a permanent license, you may or may not need a new license when you update the software product to a new version. The release notes included with the software update explain whether a new license is needed or not.

When possible, licensed products are shipped with a permanent license. The information for the permanent license is on a label on the outside of a hardware or software shipping box, or it is on a sheet of paper in an envelope that is labeled READ ME FIRST. If you receive both a permanent license and a temporary license, install the permanent license and do nothing with the temporary license.

Since permanent licenses (node-locked and concurrent) are usually tied to a system's target or sysinfo system identification number, you need a replacement license tied to the new system identification number when you move a node-locked product to a different system, when you move concurrent licenses from one Network License Server to another, or when the system identification number of a system that has licenses installed on it changes.

Any network that is using concurrent licenses must have at least one system that is configured as a Global Location Broker. Global Location Brokers run the daemons glbd(1M) and llbd(1M).

Each Global Location Broker maintains a database in the file /usr/etc/ncs/glb.e. This database, known as the GLB database, contains the addresses of Network License Servers and a list of the vendors that have products at each one.

Once one system on a network is configured as a Global Location Broker, other Global Location Brokers must be started up in a way that enables them to communicate with each other and share database update information. This enables the Global Location Brokers to maintain identical GLB databases. Global Location Brokers whose GLB databases are set up to be identical are known as “replicas.”

In a large multi-segment network, multiple network segments are joined by routers, or gateways. One example of a router is a system that has two Ethernet® interfaces. In this type of network, at least one Global Location Broker should run on each network segment where licensed applications are run.

On a network that is using concurrent licenses, there must be at least one system that is a Network License Server. A system is a Network License Server if it has the daemons netlsd(1M) and llbd running. Concurrent licenses are installed on Network License Servers.

Each Network License Server maintains its own license database called the Concurrent License database in the file /var/netls/lic_db (/usr/netls/lic_db in IRIX Release 5.0 and earlier). This database contains the concurrent licenses belonging to that server, along with information needed to process license requests from users.

Figure 1-3 shows an example of a small network: five systems on an Ethernet. System C has been set up as a Global Location Broker and a Network License Server. If a license for four nodes (the number of nodes that can use the product concurrently is on the license information sheet) for CASEVision™/Workshop is installed on system C, then any number of users on as many as four systems on this network can use Workshop simultaneously.

Figure 1-3. Simple Network Example, Minimum Configuration

If system C becomes unavailable to other systems on the network (for example, it is experiencing a hardware problem or new software is being installed from the miniroot), no users on the network can use Workshop.

Figure 1-4 shows a better setup for this small network example. Systems C and E are Global Location Brokers and Network License Servers. Instead of one license for four nodes for Workshop, two licenses, one for system C and the other for system E, are used. Each of these licenses supports users on two nodes concurrently. The number of systems on the network that can use Workshop concurrently and the software cost are the same as the Figure 1-3 situation, but now, the effect of an unavailable system C is different. If system C becomes unavailable, system E can make Workshop available to two systems.

Figure 1-4. Simple Network Example, Better Configuration

An example multi-segment network, two network segments connected by a system serving as a router (gateway), is shown in Figure 1-5. System F has two Ethernet interfaces and serves as the router. A Workshop license for four nodes is installed on system C. Users on systems G through J can use Workshop because system H is a Global Location Broker. To illustrate how this works, say that a user on system J invokes Workshop. Workshop broadcasts to find a Global Location Broker. This broadcast reaches only systems on the same network: systems F through J. System H responds and returns a list of the Network License Servers with a Workshop license to system J (in this case, the list contains just system C). System J can then contact system C to request permission to run Workshop.

In the configuration in Figure 1-5, if system C becomes unavailable, then no users can use Workshop. If system F becomes unavailable or either of F's network connections goes down, then only users on systems A through E can use Workshop. If system H becomes unavailable, only users on systems A through F can use Workshop (systems G, I, and J can't reach a Global Location Broker).

Figure 1-5. Multi-segment Network Example, Minimum Configuration

Figure 1-6 shows a better configuration for the example in Figure 1-5. In this configuration, system H has become a Network License Server as well as a Global Location Broker. System F has become a Global Location Broker and a Network License Server. Licenses for four nodes are split this way: one node each for systems C and H, and two nodes for system F.

Figure 1-6. Multi-segment Network Example, Better Configuration

When all systems are available, users on all systems have access to all licenses. If system C becomes unavailable, the remaining systems have access to the two remaining licenses (maximum three concurrent nodes). If systems C and H are available, but system F is not, just one system on each network can be using Workshop at a time. For example, a user on system A has access only to the license on system C because the license on system F is unavailable. Because system F is unavailable, there is no connection to the other network and to system H's license.

Figure 1-7 shows an example of a multi-segment network where a license group is used. Systems A, C, F, and H each have identical glb_obj.txt files (/var/ncs/glb_obj.txt on systems running IRIX Release 5.0.1 or later and /usr/etc/ncs/glb_obj.txt on systems running IRIX Release 5.0 or earlier). System C is a Network License Server and a Global Location Broker for the license group. It has a concurrent Workshop license for two nodes, so any two of the systems A, C, F, and H can be running Workshop at any one time.

Because systems A, C, F, and H are a license group and this license group has the only Global Location Broker and Network License Server on the network, users on the remaining systems in this network cannot use Workshop, even if there are available licenses.

Figure 1-7. License Group Example