#EDIR DATA# LANG=CNetwork License System Administration GuideDocument Number 007-2115-002CONTRIBUTORSWritten by Susan EllisIllustrated by Gloria AckleyCover design and illustration by Rob Aguilar, Rikk Carey, Dean Hodgkinson, Erik Lidholm and Kay MaitzEdited by Nancy SchweigerProduction by Lorrie WilliamsEngineering contributions by Roger Chickering, Ken Chin, Umesh Kanitkar© Copyright 1993, Silicon Graphics, Inc.name='mdash' font=symbol charset=fontspecific code=190 descr='[mdash]' All Rights ReservedThis document contains proprietary and confidential information of Silicon Graphics, Inc. The contents of this document may not be disclosed to third parties, copied, or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc.RESTRICTED RIGHTS LEGENDUse, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311.Silicon Graphics is a registered trademark, and CASEVision, IRIX, IRIS Networker, IRIS Volume Manager, and NetVisualyzer are trademarks, of Silicon Graphics, Inc. Network License System, and NetLS are trademarks of Apollo Computer, Inc., a subsidiary of Hewlett-Packard Company. Hewlett-Packard is a trademark of Hewlett-Packard Company. Ethernet is a registered trademark of Xerox Corporation. X Window System is a trademark of the Massachusetts Institute of Technology.About This GuideThe Network License SystemÔ (NetLSÔ) is an application licensing system used by Silicon Graphics® and other software vendors. This guide explains how to install, maintain, and administer the licenses that are required to run applications that use NetLS on Silicon Graphics workstations and servers. NetLS's powerful features enable Silicon Graphics and other vendors to make software available for demonstration purposes, to make software quickly available from widely distributed compact disks (CDs), and to provide a more cost-effective means for sites to acquire the software they need.NetLS was developed originally by ApolloÔ Computer, Inc., a subsidiary of Hewlett-PackardÔ Company. It has been ported to Silicon Graphics systems as well as to a variety of other vendors' platforms. LBL="" HELPID=""NetLS Versions DocumentedThis guide was prepared and released with IRIXÔ Release 5.0.1. It describes the version of NetLS released at that time and prior versions of NetLS as well. Differences in the versions, such as those caused by a file system reorganization in IRIX Release 5.0.1 and changes to NetLS commands, are noted with phrases such as "on IRIX Release 5.0.1 and later" and "on IRIX Release 5.0 and earlier."ID="intro1"ID="intro2"ID="intro3"ID="intro4"To find out which IRIX release a system is running, give this command:ID="intro5"uname   -r   LBL="" HELPID=""AudienceThis guide is for:Users of applications that use NetLS licensing System administrators at sites where NetLS-licensed applications are in useApplications that use NetLS licensing are available from Silicon Graphics and from other software vendors.Readers of this guide should know how to do the following:ID="intro6"Use a text editor such as vi(1), emacs(1), or jot(1G)Check and set system dates with date(1)Use ps(1) to check to see if particular commands are runningPerform simple networking checks such as ping(1M)Log in remotely to other workstations on their networkUse inst(1M) to install Silicon Graphics softwareUse versions(1M) to find out if particular subsystems are installed In addition, some knowledge of the topology of their network may be required.LBL="" HELPID=""How to Use This GuideIDREF="67384" TYPE="TITLE"Chapter 1, "NetLS Concepts," explains the basic concepts and operation of NetLS. It also lists the files associated with NetLS and the software required to create a NetLS environment on a network.IDREF="21523" TYPE="TITLE"Chapter 2, "The Licensing Process," gives an overview of the license process: how and when to acquire license passwords, how to set up a NetLS environment, and how to install licenses.IDREF="34618" TYPE="TITLE"Chapter 3, "Installing Node-locked Licenses," explains how to install node-locked licenses. This chapter is not applicable to concurrent licenses.IDREF="93641" TYPE="TITLE"Chapter 4, "Setting Up Global Location Brokers and Network License Servers," describes how to set up the NetLS environment that is required for using concurrent licenses. It is applicable to concurrent licenses only.IDREF="99449" TYPE="TITLE"Chapter 5, "Installing Concurrent Licenses," explains how to install concurrent licenses. This chapter is not applicable to node-locked licenses.IDREF="75227" TYPE="TITLE"Chapter 6, "License Administration Tasks," explains various license administration tasks that you may occasionally need to perform.IDREF="22501" TYPE="TITLE"Chapter 7, "Global Location Broker and Network License Server Administration Tasks," explains tasks that you may need to do to administer the daemons that operate in the NetLS environment when concurrent licenses are used.IDREF="80529" TYPE="TITLE"Chapter 8, "Error Messages," lists some of the error messages associated with NetLS that you may see while setting up a NetLS environment, while installing NetLS licenses, or while running applications that use NetLS. It explains the causes of error messages and suggests what to do when you see them.IDREF="99358" TYPE="TITLE"Chapter 9, "Troubleshooting," outlines a troubleshooting procedure that you can use to identify and solve various problems that can occur with NetLS. This guide also includes a glossary and an index.This guide does not cover how to add NetLS licensing while developing applications. Some features, such as the use of cells to partition networks into groups of systems, and the compound and use-once license types, are not covered in this guide.ID="intro7"LBL="" HELPID=""Documentation ConventionsThis guide uses several font conventions:ID="intro8"italicsItalics are used for command and manual page names, file names, variables, the names of buttons in graphical user interfaces, and the names of inst(1M) products and subsystems. CourierCourier is used for examples of computer output.Courier boldCourier bold is used for commands and other text that the user is to type literally.LBL="" HELPID=""For More Information You can find information about NetLS in these release notes:ID="intro9"ID="intro10"NetLS Execution Only Environment Release Notes, which provide information on known bugs in NetLS software and changes since the previous release.Release notes for software products licensed with NetLS, which provide licensing information that is specific to those products. Typically, these release notes list the type of license used by the product and which applications are licensed.In addition, these manual pages are included in the subsystem ID="intro11"ID="intro12"netls_eoe.sw.netls_eoe (netls_eoe.sw.netls_eoe and nck.sw.nck on IRIX Release 5.0 and earlier):cls_admin(1M)display and edit the Concurrent License database using a command-line interface when X Window SystemÔ libraries are not installedID="intro13"cls_stat(1M)display the status of the Network License Server system using a command-line interface when X Window System libraries are not installedID="intro14"drm_admin(1M)data replication manager administrative commandID="intro15"glbd(1M)daemon that runs on Global Location BrokersID="intro16"glb_obj.txt(4)file specifying the object UUID of the Global Location BrokerID="intro17"glb_site.txt(4)file listing possible Global Location Broker sitesID="intro18"lb_admin(1M)location broker administrative commandID="intro19"llbd(1M)daemon that runs on Global Location Brokers and Network License ServersID="intro20"ls_admin(1M)display and edit the Concurrent License databaseID="intro21"ls_nodelock(1M)node-locked license installation command (IRIX Release 5.0.1 and later only)ID="intro22"ls_stat(1M)display the status of the Network License Server systemID="intro23"ls_rpt(1M)report on Network License Server eventsID="intro24"ls_targetid(1M)print the NetLS target number for this systemID="intro25"ls_tv(1M)verify that Network License Servers are workingID="intro26"netlsd(1M)daemon that runs on Network License ServersID="intro27"stcode(1M)translate a hexadecimal code to a textual messageID="intro28"uuid_gen(1M)UUID generating commandID="intro29"uuidname.txt(4)file associating names with UUID'sID="intro30"LBL="" HELPID=""Product SupportSilicon Graphics and other distributors of Silicon Graphics products provide several comprehensive product support and maintenance programs for Silicon Graphics products. Silicon Graphics customers in the United States and Canada should call the Technical Assistance Center at 1-800-800-4SGI (1-800-800-4744). Other customers should contact their local Silicon Graphics sales office or service provider.ID="intro31"ID="intro32"ID="intro33"ID="intro34"For product support information for NetLS-licensed software products manufactured by vendors other than Silicon Graphics, contact the product vendor.To contact Silicon Graphics for licenses, see IDREF="61423" TYPE="TITLE""Contacting Silicon Graphics License Administration" in Chapter 2 .         ID="intro35"ID="intro36"ID="intro37"ID="intro38"ID="intro39"ID="intro40"ID="intro41"ID="intro42"ID="intro43"ID="intro44"ID="intro45"ID="intro46"ID="intro47"ID="intro48"ID="intro49"ID="intro50"ID="intro51"ID="intro52"ID="intro53"LBL="1"ID="67384"NetLS ConceptsNetLS is a software licensing system used by Silicon Graphics and other software vendors. This chapter briefly explains key concepts that users of licensed products may need to understand to install and use licensed products. The sections in this chapter are:IDREF="71250" TYPE="TITLE""What Is a License?"IDREF="58404" TYPE="TITLE""License Types"IDREF="59109" TYPE="TITLE""License Durations"IDREF="68902" TYPE="TITLE""System Roles for Concurrent Licensing"IDREF="17011" TYPE="TITLE""License Groups for Concurrent Licensing"IDREF="66608" TYPE="TITLE""Network License System Operation"IDREF="48641" TYPE="TITLE""Guidelines for Global Location Brokers and Network License Servers"IDREF="85083" TYPE="TITLE""Required Software, Configuration Flags, and Daemons"LBL="" HELPID=""ID="71250"What Is a License?A NetLS software license is a collection of information that includes at least a license password and a vendor ID. This information authorizes the use of a licensed software product for a period of time (days or years) on a particular number of systems (workstations or servers) at any one time. In some cases, the use of the licensed software product is restricted to a particular system.ID="ch11""License information sheets" are used to distribute license information. The license information sheet is a label affixed to the product packaging, a sheet of paper that was included with the product, a sheet of paper you receive after receiving the product, a FAX message, or an electronic mail message. ID="ch12"ID="ch13"License information sheets include some or all of this information:vendor nameThe name of the company that manufactures the licensed software product.ID="ch14"vendor IDA 36-character string. Each vendor has a unique vendor identification string that is the same for all of its products.ID="ch15"vendor passwordA 13-character password.ID="ch16"license typeThe type of license: concurrent (concurrent access) or node-locked. The license types are explained in ID="ch17"IDREF="58404" TYPE="TITLE""License Types" in this chapter.product nameThe name of the licensed software product.ID="ch18"product versionA version string for the product. This version number (or string) may or may not match the version or release number of the licensed software product.ID="ch19"license passwordA password string that authorizes the use of the licensed software product. This string contains encoded information such as the time period in which the product can be used, the maximum number of simultaneous users, and the system that the license is to be installed on. ID="ch110"license annotationA text string containing additional authorization information.ID="ch111"ID="ch112"start dateThe date on which the license becomes valid.ID="ch113"durationThe length of time the license is valid.ID="ch114"expiration dateThe date on which the license becomes invalid.ID="ch115"number of nodesThe number of systems that can be running the licensed software concurrently.ID="ch116"target typeThe authorized operating system, for example "Irix".ID="ch117"target numberA unique hexadecimal system identification number for the system that this license is to be installed on. To get the target number for a system, give the ID="ch118"ID="ch119"ID="ch120"ls_targetid(1M) command.sysinfo numberA unique decimal system identification number for the system that this license is to be installed on. To get the sysinfo number for a system, give the ID="ch121"ID="ch122"ID="ch123"sysinfo(1) command with the ­s option.serial numberA unique system identification number for the system that this license is to be installed on. It is usually printed on a bar-code label that is attached to the system.ID="ch124"LBL="" HELPID=""ID="58404"License TypesNetLS has two types of license. A license is either a "node-locked" license or a "concurrent" license. Each license information sheet lists the license type. The next two sections describe these two types of license.ID="ch125"ID="ch126"LBL="" HELPID=""Node-locked LicensesA 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.ID="ch127"Installing a node-locked license is simple: a vendor ID and a license password are entered in the file ID="ch128"/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 IDREF="34618" TYPE="TITLE"Chapter 3, "Installing Node-locked Licenses."Typically, a node-locked licensed product can be used simultaneously by multiple users on the licensed system. LBL="" HELPID=""Concurrent LicensesA 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.ID="ch129"ID="ch130"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 ID="ch131"IDREF="68902" TYPE="TITLE""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 IDREF="93641" TYPE="TITLE"Chapter 4, "Setting Up Global Location Brokers and Network License Servers," and IDREF="99449" TYPE="TITLE"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.ID="ch132"ID="ch133"LBL="" HELPID=""ID="59109"License DurationsWhen licenses are created, they are created with an expiration date. If the expiration date is within a few months, the license is called a "temporary" license. If it is longer than a few months, it is called a "permanent" license. The next two sections describe temporary and permanent licenses in more detail.ID="ch134"ID="ch135"ID="ch136"LBL="" HELPID=""Temporary LicensesTemporary 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. ID="ch137"ID="ch138"ID="ch139"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 ID="ch140"ID="ch141"IDREF="90219" TYPE="TITLE""Completing the Software License Registration Card" in Chapter 2 ).LBL="" HELPID=""Permanent LicensesPermanent 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.ID="ch142"ID="ch143"ID="ch144"ID="ch145"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.LBL="" HELPID=""ID="68902"System Roles for Concurrent LicensingWhen concurrent licensing is used, license information is often stored on a different system from the one where the licensed product is installed and used. The system with the license information is called a Network License Server. ID="ch146"At least one system on the network must serve as a Global Location Broker when concurrent licensing is used. Global Location Brokers maintain a database containing the locations of Network License Servers and the product vendors for the licenses on each Network License Server. The roles of Network License Servers and Global Location Brokers are explained in more detail in the next two sections.LBL="" HELPID=""Global Location BrokersAny 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 ID="ch147"ID="ch148"ID="ch149"ID="ch150"glbd(1M) and llbd(1M).   Each Global Location Broker maintains a database in the file ID="ch151"ID="ch152"/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." ID="ch153"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. ID="ch154"ID="ch155"ID="ch156"ID="ch157"LBL="" HELPID=""Network License ServersOn 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 ID="ch158"ID="ch159"ID="ch160"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 ID="ch161"ID="ch162"/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. LBL="" HELPID=""ID="17011"License Groups for Concurrent LicensingA license group (called a cell in other implementations of NetLS) is a set of systems that use a set of Global Location Brokers and Network License Servers. A licensed application running on a system that is part of a license group requests licenses only from Network License Servers that belong to its license group.ID="ch163"ID="ch164"ID="ch165"All systems in a license group have identical UUID (Unique Universal Identifier) values in a ID="ch166"ID="ch167"ID="ch168"ID="ch169"glb_obj.txt file. On systems running IRIX Release 5.0.1 or later, the file is /var/ncs/glb_obj.txt. On systems running IRIX Release 5.0 or earlier, the file is /usr/etc/ncs/glb_obj.txt. Systems on a network can be divided into one or more license groups and systems on different segments of a multi-segment network can belong to the same license group, but each system can belong to only one license group. Systems belonging to a license group get licenses only from Network License Servers in the license group, and the Network License Servers in a license group do not give licenses to systems outside of the license group. Global Location Brokers and Network License Servers in a license group don't respond to license requests from systems that are not in the license group.LBL="" HELPID=""ID="66608"Network License System OperationWhen a licensed application starts up, it first checks to see if the file ID="ch170"ID="ch171"/var/netls/nodelock (/usr/netls/nodelock for some applications) exists and there is a valid entry for the application. If the nodelock file the application is looking for, /var/netls/nodelock or /usr/netls/nodelock, doesn't exist or there is no valid entry in the file for the application, then the application attempts to run using a concurrent license. IDREF="12478" TYPE="GRAPHIC"Figure 1-1 shows the events that take place when a user invokes licensed software using a node-locked license. When the application starts up, it checks the file /var/netls/nodelock or /usr/netls/nodelock to see if there is a valid license for the product. If there is a valid license, the application runs.LBL="1-1" FILE="ch1.cgm" POSITION="INLINE" SCALE="FALSE"LBL="1-1"Figure 1-1 ID="12478"Node-locked License OperationID="ch172"ID="ch173"ID="ch174"ID="ch175"IDREF="69413" TYPE="GRAPHIC"Figure 1-2 shows the events that take place when an application uses a concurrent license and license groups are not used. When the application starts up, it broadcasts to find a Global Location Broker (1). The Global Location Broker looks into its database to find the locations of Network License Servers with licenses for the vendor (2, 3) and returns the list to the application (4). The application gets the address of a Network License Server from the list and uses it to contact a Network License Server (5). The Network License Server consults its database for available licenses (6,7). If a license is available, it is granted to the application (8). When the user exits the application, the application releases the license.LBL="1-2" FILE="ch1.cgm2" POSITION="INLINE" SCALE="FALSE"LBL="1-2"Figure 1-2 ID="69413"Concurrent License OperationLBL="" HELPID=""ID="48641"Guidelines for Global Location Brokers and Network License ServersUse these guidelines to choose systems to be Global Location Brokers and Network License Servers. ID="ch176"ID="ch177"When a concurrent license has been created for a specific system, that system must be a Network License Server. The system is listed on the license information sheet; the target, sysinfo, and/or serial number items identify it.ID="ch178"The system(s) that you choose for Global Location Brokers and Network License Servers should be stable; they should not be systems that are frequently taken down or unavailable. Good choices are systems that are already designated "server" systems within the network.ID="ch179"Systems that are Global Location Brokers and/or Network License Servers must be able to communicate with each other using TCP/IP. They must be able to communicate with systems running licensed applications using TCP/IP as well. The ID="ch180"ping(1M) command can be used to verify that systems can communicate.If a license group isn't used, each system that will run concurrent licensed applications must be able to broadcast and find a Global Location Broker. Typically, broadcasts don't go across routers, so each network segment where licensed applications are run on a multi-segment network should have at least one Global Location Broker.ID="ch181"ID="ch182"At least one system on a network segment (one system in a license group when a license group is used) must be a Global Location Broker. If the only system that is a Global Location Broker is shut down, then no users on that network can use licensed applications until that system is brought back up or another system is set up as a Global Location Broker. For this reason, it is recommended that more than one system be set up as a Global Location Broker.ID="ch183"To avoid a situation in which an unavailable Network License Server or a local networking failure entirely disables user access to a product, there should be two or more Network License Servers. For example, instead of obtaining a license that supports 15 concurrent users and installing it on one Network License Server, obtain three licenses for five concurrent users each and install each license on a different Network License Server. The total number of concurrent users is the same, but now, if a Network License Server becomes unavailable, there are still two Network License Servers that can grant permission for ten concurrent users.ID="ch184"A single system can be both a Global Location Broker and a Network License Server. It can also run licensed applications. System administration is easier when a single system is both a Global Location Broker and a Network License Server.ID="ch185"Diskless systems should not be Global Location Brokers or Network License Servers.ID="ch186"In an environment where systems are managed by separate administrators, creating license groups results in a more robust NetLS environment because there is less chance of interference from Global Location Brokers whose databases are not replicas.The next two sections show examples of NetLS configurations that don't use license groups. A third section shows an example NetLS configuration that uses a license group. Each section explains which systems have access to concurrent licenses under normal circumstances and in the event of the failure of a system or the network.LBL="" HELPID=""ID="64212"Simple Network ExampleID="ch187"ID="ch188"ID="ch189"IDREF="96509" TYPE="GRAPHIC"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.LBL="1-3" FILE="ch1.cgm3" POSITION="INLINE" SCALE="FALSE"LBL="1-3"Figure 1-3 ID="96509"Simple Network Example, Minimum ConfigurationIf 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.IDREF="77113" TYPE="GRAPHIC"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 IDREF="96509" TYPE="GRAPHIC"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.LBL="1-4" FILE="ch1.cgm4" POSITION="INLINE" SCALE="FALSE"LBL="1-4"Figure 1-4 ID="77113"Simple Network Example, Better ConfigurationLBL="" HELPID=""Multi-segment Network ExampleAn example multi-segment network, two network segments connected by a system serving as a router (gateway), is shown in ID="ch190"ID="ch191"IDREF="64115" TYPE="GRAPHIC"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 IDREF="64115" TYPE="GRAPHIC"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).LBL="1-5" FILE="ch1.cgm5" POSITION="INLINE" SCALE="FALSE"LBL="1-5"Figure 1-5 ID="64115"Multi-segment Network Example, Minimum ConfigurationIDREF="54103" TYPE="GRAPHIC"Figure 1-6 shows a better configuration for the example in IDREF="64115" TYPE="GRAPHIC"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.LBL="1-6" FILE="ch1.cgm6" POSITION="INLINE" SCALE="FALSE"LBL="1-6"Figure 1-6 ID="54103"Multi-segment Network Example, Better ConfigurationWhen 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. ID="ch192"ID="ch193"ID="ch194"LBL="" HELPID=""License Group ExampleID="ch195"IDREF="94201" TYPE="GRAPHIC"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.LBL="1-7" FILE="ch1.cgm7" POSITION="INLINE" SCALE="FALSE"LBL="1-7"Figure 1-7 ID="94201"License Group ExampleLBL="" HELPID=""ID="85083"Required Software, Configuration Flags, and DaemonsFor quick reference, ID="ch196"ID="ch197"ID="ch198"IDREF="13419" TYPE="TABLE"Table 1-1 and IDREF="36333" TYPE="TABLE"Table 1-2 show the software that must be installed, the chkconfig(1M) flags that must be set to "on," and the daemons that must be running for each type of system in a NetLS environment. IDREF="13419" TYPE="TABLE"Table 1-1 is for products with node-locked licenses and IDREF="36333" TYPE="TABLE"Table 1-2 is for products that have concurrent licenses.COLUMNS="5"LBL="1-1"Table 1-1 ID="13419"Required Software for Node-locked LicensesLEFT="0" WIDTH="43"IRIX ReleasesLEFT="50" WIDTH="79"System RoleLEFT="135" WIDTH="102"Required SoftwareLEFT="245" WIDTH="64"Chkconfig Flag SettingsLEFT="315" WIDTH="356"Required DaemonsLEFT="0" WIDTH="43"5.0.1 and laterLEFT="50" WIDTH="79"Running licensed applicationLEFT="135" WIDTH="102"Licensed application, netls_eoe.sw.netls_eoeLEFT="245" WIDTH="64"noneLEFT="315" WIDTH="356"noneLEFT="0" WIDTH="43"5.0 and earlierLEFT="50" WIDTH="79"Running licensed applicationLEFT="135" WIDTH="102"Licensed applicationLEFT="245" WIDTH="64"noneLEFT="315" WIDTH="356"noneCOLUMNS="5"LBL="1-2"Table 1-2 ID="36333"Required Software, Configuration Flags, and Daemons for Concurrent LicensesID="ch199"ID="ch1100"ID="ch1101"ID="ch1102"ID="ch1103"ID="ch1104"LEFT="0" WIDTH="43"IRIX ReleasesLEFT="50" WIDTH="79"System RoleLEFT="135" WIDTH="102"Required SoftwareLEFT="245" WIDTH="64"Chkconfig Flag SettingsLEFT="315" WIDTH="356"Required DaemonsLEFT="0" WIDTH="43"5.0.1 and laterLEFT="50" WIDTH="79"Global Location BrokerLEFT="135" WIDTH="102"netls_eoe.sw.netls_eoe   LEFT="245" WIDTH="64"glb on llb on network onLEFT="315" WIDTH="356"glbd llbd   LEFT="0" WIDTH="43"LEFT="50" WIDTH="79"Network License ServerLEFT="135" WIDTH="102"netls_eoe.sw.netls_eoe   LEFT="245" WIDTH="64"netls on llb on network onLEFT="315" WIDTH="356"netlsd llbd   LEFT="0" WIDTH="43"LEFT="50" WIDTH="79"Running licensed applicationLEFT="135" WIDTH="102"Licensed applicationLEFT="245" WIDTH="64"network onLEFT="315" WIDTH="356"noneLEFT="0" WIDTH="43"5.0 and earlierLEFT="50" WIDTH="79"Global Location BrokerLEFT="135" WIDTH="102"nck.sw.nck   LEFT="245" WIDTH="64"glb on llb on network onLEFT="315" WIDTH="356"glbd llbd   LEFT="0" WIDTH="43"LEFT="50" WIDTH="79"Network License ServerLEFT="135" WIDTH="102"netls_eoe.sw.netls_eoe, nck.sw.nck   LEFT="245" WIDTH="64"netls on llb on network onLEFT="315" WIDTH="356"netlsd llbd   LEFT="0" WIDTH="43"LEFT="50" WIDTH="79"Running licensed applicationLEFT="135" WIDTH="102"Licensed applicationLEFT="245" WIDTH="64"network onLEFT="315" WIDTH="356"noneThe Global Location Broker and Network License Server daemons don't work correctly if they are started up in an incorrect order. Follow these guidelines to start up daemons in the correct order:ID="ch1105"ID="ch1106"ID="ch1107"ID="ch1108"There should be at least one Global Location Broker (running   llbd and glbd) on a network before netlsd is started.llbd should be started on a system before glbd is started on that system.llbd should always be started on a system before netlsd is started on that system.Complete instructions for setting up Global Location Brokers and Network License Servers and for installing licenses are in IDREF="93641" TYPE="TITLE"Chapter 4, "Setting Up Global Location Brokers and Network License Servers," and IDREF="99449" TYPE="TITLE"Chapter 5, "Installing Concurrent Licenses."LBL="2"ID="21523"The Licensing ProcessThis chapter discusses the licensing process: obtaining, setting up, and installing licenses. It discusses obtaining license passwords from Silicon Graphics or your local service provider and also gives an overview of how to set up a NetLS environment for concurrent licenses. The sections in this chapter are:IDREF="67160" TYPE="TITLE""Flowchart of the Licensing Process"IDREF="90219" TYPE="TITLE""Completing the Software License Registration Card"IDREF="77399" TYPE="TITLE""Missing Software License Registration Card"IDREF="61423" TYPE="TITLE""Contacting Silicon Graphics License Administration"LBL="" HELPID=""ID="67160"Flowchart of the Licensing ProcessAn overview of the licensing process is shown in the flowcharts in ID="ch21"IDREF="19099" TYPE="GRAPHIC"Figure 2-1 through IDREF="43550" TYPE="GRAPHIC"Figure 2-3 . IDREF="19099" TYPE="GRAPHIC"Figure 2-1 and IDREF="76251" TYPE="GRAPHIC"Figure 2-2 cover receiving and installing the first license for a licensed software product. IDREF="43550" TYPE="GRAPHIC"Figure 2-3 covers installing a replacement license for a product that already has a license. Replacement licenses can be permanent licenses that replace temporary licenses. They are sometimes required for a software update or because hardware changes caused the system identification number to change.LBL="2-1" FILE="ch2.cgm" POSITION="INLINE" SCALE="FALSE"LBL="2-1"Figure 2-1 ID="19099"Licensing Process for New Software (Part 1)LBL="2-2" FILE="ch2.cgm2" POSITION="INLINE" SCALE="FALSE"LBL="2-2"Figure 2-2 ID="76251"Licensing Process for New Software (Part 2)LBL="2-3" FILE="ch2.cgm3" POSITION="INLINE" SCALE="FALSE"LBL="2-3"Figure 2-3 ID="43550"Licensing Process for a Replacement LicenseID="ch22"ID="ch23"ID="ch24"LBL="" HELPID=""ID="90219"Completing the Software License Registration CardIf you received a Software License Registration card, please take a moment to fill out the card. The information you supply on this card is required for generating and delivering a permanent software license.ID="ch25"ID="ch26"The card describes how to find the serial number of the system you choose to install the license on and how to get its system identification number. (See ID="ch27"IDREF="48641" TYPE="TITLE""Guidelines for Global Location Brokers and Network License Servers" in Chapter 1 for information on selecting a system to install the permanent license on.)Once the card is completed, follow the return instructions on the card. A license information sheet with a permanent license will be e-mailed, FAXed, or mailed to you within two business days of Silicon Graphics' or your local service provider's receiving the card.ID="ch28"ID="ch29"If you do not have a Software License Registration card, see IDREF="77399" TYPE="TITLE""Missing Software License Registration Card" in this chapter.LBL="" HELPID=""ID="77399"Missing Software License Registration CardIf you did not receive a Software License Registration card or can't find it, and you need to get a license (assuming that the software has been purchased), ID="ch210"IDREF="58408" TYPE="GRAPHIC"Figure 2-4 can be photocopied and substituted for the card. You can use the card to request several licenses for one software product.You can obtain the product name and version number requested on the card from:ID="ch211"ID="ch212"The label of your CD, for example:CASEVision/Workshop 1.1.1The description in ID="ch213"versions(1M) command output, for example:versions -b CaseVision    ... I CaseVision 04/09/93 CASEVision Environment, Version 1.1.1The serial number requested on the card is the serial number of the system where a node-locked licensed product will be used, or the serial number of the system that will be the Network License Server for a concurrent licensed product. In most cases, the serial number can be found on the back of a system. It is usually printed above the power cord or on a bar-code label that is above and to the left of the SCSI bus port. Enter one serial number for each license you want.ID="ch214"To get the "Sys ID Number" (sysinfo system identification number) of a system, give this command on each system whose serial number you are providing:ID="ch215"ID="ch216"/etc/sysinfo -s   The output of this command is the system identification number you need.If you are requesting one or more concurrent licenses, each license authorizes a particular number of nodes (systems) to use the product at any one time. Enter this number in the Quantity column. Mail, FAX, or phone the information listed to Silicon Graphics or your local service provider as described in IDREF="61423" TYPE="TITLE""Contacting Silicon Graphics License Administration" in this chapter.LBL="2-4" FILE="2-4.form.bw" POSITION="INLINE" SCALE="FALSE"LBL="2-4"Figure 2-4 ID="58408"Software License Registration CardID="ch217"LBL="" HELPID=""ID="61423"Contacting Silicon Graphics License AdministrationThe e-mail address, FAX number, telephone number, and mailing address for Silicon Graphics License Administration are listed below. These addresses and telephone numbers can be used if you are a Silicon Graphics customer in the United States or Canada.ID="ch218"If you are not in the United States or Canada, or you purchased the system or software from a vendor other than Silicon Graphics, please contact your local service provider.To receive the quickest reply, use the first address or telephone number on the list that is available to you.ID="ch219"ID="ch220"E-mail:license@sgi.comFAX:(415) 390-0537Mail:Software Licensing M/S 134Silicon Graphics, Inc.P.O. Box 7311Mountain View, CA 94039-9600In an emergency, you can telephone Silicon Graphics at 1-800-800-4744. However, license information isn't usually given out on the telephone because of the difficulty of communicating long passwords.ID="ch221"ID="ch222"ID="ch223"LBL="3"ID="34618"Installing Node-locked LicensesThis chapter explains how to install node-locked licenses. Two installation procedures are given; choose the one that is appropriate for your situation:ID="ch31"ID="ch32"Use IDREF="94893" TYPE="TITLE""Graphical Installation of a Node-locked License" if the system is at IRIX Release 5.0.1 or higher and the system has graphics.Use IDREF="86479" TYPE="TITLE""Non-graphical Installation of a Node-locked License" if the system is at IRIX Release 5.0 or lower or it does not have graphics.Some products include a node-locked license installation command that you can use instead of either of the procedures below. Check the release notes for a licensed product to find out if it has such a command.ID="ch33"Before beginning any installation procedure, make sure that you have a license information sheet that contains at least the following information: vendor ID, product name, product version, expiration date, license password, and one or more system identification numbers (target, sysinfo, and/or serial number). Check the expiration date to make sure the license hasn't expired.ID="ch34"ID="ch35"LBL="" HELPID=""ID="94893"Graphical Installation of a Node-locked LicenseID="ch36"ls_nodelock(1M) is a graphical command for installing node-locked licenses on systems running IRIX Release 5.0.1 or later. Follow these steps to install a license with ls_nodelock:If the sysinfo number on the license information sheet is a number rather than the word "Any", verify that the license information sheet is for the system you plan to install the license on. Compare the sysinfo number on the license information sheet with the output of this ID="ch37"sysinfo(1) command:/etc/sysinfo -s   If the numbers are different, the information on the license information sheet wasn't generated for this system. The license won't work on this system, so you should not install it.ID="21090"Become superuser:/bin/su -    Password: Install the licensed software product if it is not installed already.Install the subsystem netls_eoe.sw.netls_eoe if it is not installed already.To begin installing the license, start ls_nodelock:/usr/etc/ls_nodelock   A window border appears. After you position the window border and click the left mouse button, the window shown in IDREF="59801" TYPE="GRAPHIC"Figure 3-1 appears.If the vendor name shown on the license information sheet is not "Silicon Graphics", replace the contents of the Vendor Name field with the vendor name from the license information sheet.ID="ch38"LBL="3-1" FILE="3-1.ls_nodelock.bw" POSITION="INLINE" SCALE="FALSE"LBL="3-1"Figure 3-1 ID="59801"ls_nodelock WindowIf you replaced the vendor name, replace the contents of the Vendor ID field with the correct vendor ID.ID="ch39"Enter the product name in the Product Name field.ID="ch310"Enter the product version in the Version field.ID="ch311"Enter the expiration date in the Expiration Date field.Enter the license password in the License Password field.ID="ch312"If a license annotation appears on the license information sheet, enter it in the Annotation field.ID="ch313"Click the Add button. A notifier window appears. Click the OK button.Click the Quit button.Save the license information sheet; you may need it again later if you need to reinstall this license.ID="ch314"LBL="" HELPID=""ID="86479"Non-graphical Installation of a Node-locked LicenseThis section explains how to install a node-locked license by editing the nodelock file ID="ch315"/var/netls/nodelock   (/usr/netls/nodelock on IRIX Release 5.0 and earlier). This procedure can be used on any system.If the sysinfo number on the license information sheet is a number rather than the word "Any", verify that the license information sheet is for the system you plan to install the license on. Compare the sysinfo number on the license information sheet with the output of this ID="ch316"sysinfo(1) command:/etc/sysinfo -s   If the numbers are different, the information on the license information sheet wasn't generated for this system. The license won't work on this system, so you should not install it.Become superuser:/bin/su -    Password: Install the licensed software product if it is not installed already.Using any text editor, such as jot(1G) or vi(1), open the file /var/netls/nodelock   (/usr/netls/nodelock if the system is running IRIX Release 5.0 or earlier). On a blank line, create a comment: enter a # followed by the name of the product the license is for, the expiration date, if any, and any other information you might need later to help you remember what the license is for. For example:# temporary Tracker 1.0 license, expires on 6/16/93On the next line of the file, type the vendor ID. For example, the Silicon Graphics vendor ID:ID="ch317"546fb4684914.02.c0.1a.3d.52.00.00.00 On the same line, type a space after the vendor ID, and then type the license password from the license information sheet. For example:ID="ch318"779k6hrykgh4ec9579329c2a If there is a license annotation (see the license information sheet), type a space after the password, then type the annotation on the same line. Annotations containing spaces must be enclosed in double quotes (").ID="ch319"Write the file and exit the editor. The license is now installed. IDREF="59280" TYPE="TEXT"Example 3-1 shows a sample /var/netls/nodelock   (/usr/netls/nodelock on IRIX Release 5.0 and earlier) file that contains licenses for two products (because of line length limitations, many characters in the NetVisualyzerÔ license password are not shown).# Silicon Graphics CASEVision/Workshop 1.1.1 expires 12/31/93 546fb4684914.02.c0.1a.3d.52.00.00.00 9qscr4pncxaqwc9ai8r7wc2a # Silicon Graphics NetVisualyzer 2.0 expires 6/30/93 546fb4684914.02.c0.1a.3d.52.00.00 f2fy5t36s8smquigf8u86wv2hucz4 datastations=10LBL="3-1"Example 3-1 ID="59280"Sample /var/netls/nodelock File (/usr/netls/nodelock on IRIX 5.0 and Earlier)ID="ch320"Save the license information sheet; you may need it again later if you need to reinstall this license.ID="ch321"ID="ch322"LBL="4"ID="93641"Setting Up Global Location Brokers and Network License ServersThis chapter explains how to set up and start the Global Location Brokers and Network License Servers that are required when using concurrent licenses.On systems running IRIX Release 5.0.1 or later, use these sections:IDREF="10853" TYPE="TITLE""Creating a License Group" which explains how to set up a license group if you choose to use one.IDREF="14345" TYPE="TITLE""Setting Up a Network License Server and Global Location Broker with ­sgiauto" which explains how to configure a Network License Server and start a Global Location Broker, too, if necessary. IDREF="59272" TYPE="TITLE""Setting Up a Global Location Broker Manually" which explains how to start an additional Global Location Broker.On systems running IRIX Release 5.0 or earlier, use these sections:IDREF="10853" TYPE="TITLE""Creating a License Group" which explains how to set up a license group if you choose to use one.IDREF="59272" TYPE="TITLE""Setting Up a Global Location Broker Manually" which explains how to start a Global Location Broker.IDREF="18424" TYPE="TITLE""Setting Up a Network License Server Manually" which explains how to start a Network License Server.LBL="" HELPID=""ID="10853"Creating a License GroupLicense groups, explained in ID="ch41"IDREF="17011" TYPE="TITLE""License Groups for Concurrent Licensing" in Chapter 1 are used to restrict the use of concurrent licenses to a particular set of systems, rather than all systems on the network. Creating license groups is simplest when it is done before systems are set up as Network License Servers and Global Location Brokers. (Creating a license group later is explained in IDREF="32117" TYPE="TITLE""Creating a New License Group" in Chapter 7 .) Follow these steps to specify a license group before you set up a Network License Server and a Global Location Broker:Identify all systems to be included in the license group. This list should include all systems that are Global Location Brokers and/or Network License Servers, and all systems on which you intend to run licensed applications.ID="79503"On a system running IRIX Release 5.0.1 or later that has ID="ch42"netls_eoe.sw.netls_eoe installed, or on a system running IRIX Release 5.0 or earlier that has nck.sw.nck installed, create a glb_obj.txt file by giving this command:/usr/etc/uuid_gen > /usr/tmp/glb_obj.txt   On each system that is to be part of the license group and is running IRIX 5.0.1 or later, give these commands to create the directory ID="ch43"/var/ncs, in case it doesn't already exist, and make a copy of the glb_obj.txt file you created in step IDREF="79503" TYPE="TEXT"2 :/bin/su -    Password: mkdir /var/ncs    rcp guest@hostname:/usr/tmp/glb_obj.txt /var/ncs/glb_obj.txt   hostname is the name of the system where you performed step IDREF="79503" TYPE="TEXT"2 .On each system that is to be part of the license group and is running IRIX 5.0 or earlier, give these commands to create the directory /usr/etc/ncs, in case it doesn't already exist, and make a copy of the glb_obj.txt file you created in step IDREF="79503" TYPE="TEXT"2 :/bin/su -    Password: mkdir /usr/etc/ncs    rcp guest@hostname:/usr/tmp/glb_obj.txt \ /usr/etc/ncs/glb_obj.txt   hostname is the name of the system where you performed step IDREF="79503" TYPE="TEXT"2 .LBL="" HELPID=""ID="14345"Setting Up a Network License Server and Global Location Broker with ­sgiautoOn IRIX Release 5.0.1 and later, you can use the following procedure to set up a Network License Server. This procedure automatically starts a Global Location Broker on the same system if there are no Global Location Brokers or there is just one on the network. Alternatively, ID="ch44"ID="ch45"ID="ch46"ID="ch47"IDREF="59272" TYPE="TITLE""Setting Up a Global Location Broker Manually" and IDREF="18424" TYPE="TITLE""Setting Up a Network License Server Manually" in this chapter can be used when you want to start a Global Location Broker on a different system, or you want to make a Global Location Broker that is a replica of a Global Location Broker on a different network segment in a multi-segment network.To start a Network License Server and, if necessary, a Global Location Broker on this system, follow this procedure:If the sysinfo number on the license information sheet is a number rather than the word "Any", verify that the license information sheet is for the system you plan to install the license on. Compare the sysinfo number on the license information sheet with the output of this ID="ch48"sysinfo(1) command:/etc/sysinfo -s   If the numbers are different, the information on the license information sheet wasn't generated for this system. The license won't work on this system, so you should not make this system a Network License Server.Become superuser:/bin/su -    Password: Install the subsystem netls_eoe.sw.netls_eoe if it isn't already installed.If you are using a standalone system (one not connected to a network at all), some special setup is required. Give these commands:ID="ch49"ID="ch410"ID="ch411"ID="ch412"/etc/chkconfig network on    echo "ip:localhost" > /var/ncs/glb_site.txt   Perform the setup for a Network License Server and possibly a Global Location Broker, and start their daemons (ID="ch413"llbd, glbd, and netlsd) with this command:/usr/etc/netlsd -sgiauto &   Confirm that the llbd(1M) and netlsd(1M) daemons were started using ps(1); for example:ps -e | grep llbd    12304 ttyq1 0:00 llbd ps -e | grep netlsd    12310 ttyq1 0:00 netlsdIf the output of the netlsd command indicated that it started glbd(1M), confirm that it is running; for example:ps -e | grep glbd    12287 ttyq1 0:00 glbdLBL="" HELPID=""ID="59272"Setting Up a Global Location Broker ManuallyThis section explains how to set up a Global Location Broker and start its daemons running for the first time. Once you set up a Global Location Broker, its daemons are automatically started each time the system is rebooted. This procedure can be used on all IRIX releases. ID="ch414"ID="ch415"Follow these steps to set up a Global Location Broker:Become superuser on the system that is to become a Global Location Broker:/bin/su -    Password: If the system is running IRIX Release 5.0.1 or later, install netls_eoe.sw.netls_eoe if it isn't already installed.If the system is running IRIX Release 5.0 or earlier, install nck.sw.nck if it isn't already installed.If you are using a standalone system (one not connected to a network at all), some special setup is required. On IRIX Release 5.0.1 or later, give these commands:ID="ch416"ID="ch417"ID="ch418"/etc/chkconfig network on    echo "ip:localhost" > /var/ncs/glb_site.txt   On IRIX Release 5.0 or earlier, give these commands:/etc/chkconfig network on    echo "ip:localhost" > /usr/ncs/glb_site.txt   Set the llb and glb ID="ch419"chkconfig(1M) flags to "on":/etc/chkconfig llb on    /etc/chkconfig glb on   Give these commands to kill llbd, glbd, and netlsd in case they happen to be running:/etc/init.d/netls stop    /etc/init.d/nck stop   If this is the first Global Location Broker on the network (see ID="ch420"IDREF="38612" TYPE="TITLE""Checking Global Location Brokers" in Chapter 7 ), start the llbd and glbd daemons with this command:/etc/init.d/nck start   ID="68053"If there is already at least one Global Location Broker on the network (or on another network segment if it is a multi-segment network), start the daemons ID="ch421"ID="ch422"ID="ch423"llbd and glbd with these commands so that all Global Location Brokers know about each other:/usr/etc/llbd    /usr/etc/glbd -create -from ip:other_GLB_hostname   &   other_GLB_hostname is the host name of another Global Location Broker. These commands start this Global Location Broker as a replica of the Global Location Broker on other_GLB_hostname.ID="44454"Confirm that llbd and glbd are running; for example:ps -e | grep lbd    12293 ttyq1 0:00 llbd 12287 ttyq1 0:00 glbdIf there are now two or more Global Location Brokers on the network, verify that their clocks are within two minutes of each other, using the drm_admin(1M) command as described in IDREF="86397" TYPE="TITLE""Routine Maintenance of Global Location Brokers" in Chapter 7 . LBL="" HELPID=""ID="18424"Setting Up a Network License Server ManuallyThis section explains how to configure a Network License Server and start its daemons running for the first time. Once you set up a Network License Server, its daemons are automatically started each time the system is rebooted. This procedure can be used on all IRIX releases. ID="ch424"ID="ch425"Follow these steps to set up a Network License Server:If the sysinfo number on the license information sheet is a number rather than the word "Any", verify that the license information sheet is for the system you plan to install the license on. Compare the sysinfo number on the license information sheet with the output of this ID="ch426"sysinfo(1) command:/etc/sysinfo -s   If the numbers are different, the information on the license information sheet wasn't generated for this system. The license won't work on this system, so you should not make this system a Network License Server.Become superuser:/bin/su -    Password: Install the subsystem netls_eoe.sw.netls_eoe if it isn't already installed.If the system is running IRIX Release 5.0 or earlier, install nck.sw.nck if it isn't already installed.Set the llb and netls ID="ch427"chkconfig flags to "on":chkconfig llb on    chkconfig netls on   If this system is not a Global Location Broker, give the command:chkconfig glb off   Give this command to kill netlsd in case it happens to be running:/etc/init.d/netls stop   Start ID="ch428"llbd and netlsd:/usr/init.d/nck   start    /etc/init.d/netls start   Confirm that the Network License Server is now set up by verifying that llbd and netlsd are running; for example:ps -e | grep llbd    12304 ttyq1 0:00 llbd ps -e | grep netlsd    12310 ttyq1 0:00 netlsdSave the license information sheet; you may need it again later if you need to reinstall this license.LBL="5"ID="99449"Installing Concurrent LicensesThis chapter explains how to install concurrent licenses. It assumes that the network has at least one Global Location Broker and that the system listed on the license information sheet is a Network License Server.ID="ch51"ID="ch52"Two installation procedures are included in this chapter; you can use either one:IDREF="61920" TYPE="TITLE""Graphical Concurrent License Installation"IDREF="61736" TYPE="TITLE""Non-graphical Concurrent License Installation"Before beginning the installation procedure, make sure that you have a license information sheet that contains at least the following information: vendor name, vendor ID, vendor password, product name, product version, expiration date, license password, and one or more system identification numbers (target, sysinfo, and/or serial number). Check the expiration date to make sure the license hasn't expired.ID="ch53"ID="ch54"LBL="" HELPID=""ID="61920"Graphical Concurrent License InstallationThis procedure uses the graphical interface version of ID="ch55"ls_admin(1M) to install a concurrent license on a Network License Server. You can perform the installation from any system on the network.Become superuser:/bin/su -    Password: Install netls_eoe.sw.netls_eoe if it isn't already installed.Start the license administration command ls_admin:/usr/etc/ls_admin   A window border appears. After you position the window border and click the left mouse button, the window shown in IDREF="68676" TYPE="GRAPHIC"Figure 5-1 or one very similar appears. The Network License Server you wish to install a license onto should be listed in the Servers area.Select the Network License Server you wish to use by clicking on it in the Servers area.Click the Add Vendor... button in the Operations area. An ADD VENDOR window appears. IDREF="60841" TYPE="GRAPHIC"Figure 5-2 shows this window after it has been filled in as described in the next few steps.LBL="5-1" FILE="5-1.ls_admin.server.comp.bw" POSITION="MARGIN" SCALE="FALSE"LBL="5-1"Figure 5-1 ID="68676"ls_admin Window with Server SelectedLBL="5-2" FILE="5-2.ADDVENDOR.bw" POSITION="INLINE" SCALE="FALSE"LBL="5-2"Figure 5-2 ID="60841"ADD VENDOR WindowIn the Vendor Name field, enter the vendor name from the license information sheet.ID="ch56"In the Vendor Id field, enter the vendor ID from the license information sheet.ID="ch57"In the Vendor Password field, enter the vendor password from the license information sheet.ID="ch58"Click the Done button. If you get a NOTIFICATION window with the message "A vendor already exists under this name," click its Dismiss button and click the Cancel button in the ADD VENDOR window.If the diamond in the Vendor button in the ls_admin Window isn't selected, click the Vendor button. The Servers area changes to a Vendors area with the vendor you just added selected, and the buttons in the Operations area change as shown in IDREF="70700" TYPE="GRAPHIC"Figure 5-3 . ID="10007"Click the Add Product... button in the Operations area. An ADD PRODUCT window appears. IDREF="88097" TYPE="GRAPHIC"Figure 5-4 shows this window after it has been filled in as described in the next few steps.LBL="5-3" FILE="5-3.ls_admin.vendor.comp.bw" POSITION="MARGIN" SCALE="FALSE"LBL="5-3"Figure 5-3 ID="70700"ls_admin Window with Vendor SelectedLBL="5-4" FILE="5-4.ADDPRODUCT.bw" POSITION="INLINE" SCALE="FALSE"LBL="5-4"Figure 5-4 ID="88097"ADD PRODUCT WindowIn the Product Name field, enter the product name from the license information sheet.ID="ch59"In the Product Version field, enter the product version from the license information sheet.ID="ch510"In the License Password field, enter the license password from the license information sheet.ID="ch511"If there is a license annotation listed on the license information sheet, enter it in the License Annotation field.ID="ch512"ID="62649"Click the Done button. The concurrent license has been installed.If just one license is listed on the license information sheet, skip to step IDREF="56295" TYPE="TEXT"23 . If there are two or more licenses listed, each license needs to be installed on the Network License Server it was created for, so continue with this procedure.ID="36147"Click the Vendor button in the Operate On area.Click the Copy Vendor... button in the Operations area. A COPY VENDOR window appears. Select the Network License Server that you want to install the second license on the license information sheet on.Click the Done button.ID="69468"Repeat steps IDREF="10007" TYPE="TEXT"12 to IDREF="62649" TYPE="TEXT"17 using the second set of license information.ID="56295"Save the license information sheet; you may need it again later if you need to reinstall this license.LBL="" HELPID=""ID="61736"Non-graphical Concurrent License InstallationThis procedure uses the command-line interface version of ls_admin to install a concurrent license on a Network License Server. You can perform the installation from any system on the network. If X Window System libraries are not installed, use cls_admin(1M) instead of ls_admin in this procedure.Become superuser:/bin/su -    Password: Install netls_eoe.sw.netls_eoe if it isn't already installed.ID="88866"Specify the vendor information for the license:/usr/etc/ls_admin -a -n   license_server   -v   v_name   v_id   v_passwordID="ch513"ID="ch514"ID="ch515"license_server is the host name of the Network License Server you are installing the license on.   v_name, v_id, and v_password are the vendor name, vendor ID, and vendor password shown on the license information sheet. If any of these strings contain spaces, the strings must be surrounded with double quotes (").An example is:/usr/etc/ls_admin -a -n express -v "Silicon Graphics" \ 546fb4684914.02.c0.1a.3d.52.00.00.00 m9p9rovbcy238ID="39048"Specify the product information for the license:/usr/etc/ls_admin -a -n   license_server   -l   l_annotation   \ -p   v_name   p_name   l_password   p_versionID="ch516"ID="ch517"ID="ch518"ID="ch519"license_server is the same as in step IDREF="88866" TYPE="TEXT"3 .   l_annotation is the annotation shown on the license information sheet (omit ­l   l_annotation if there is no license annotation).   v_name, p_name, l_password, and p_version are the vendor name, product name, license password, and product version from the license information sheet. If any of these strings contain spaces, the strings must be surrounded with double quotes (").An example is:/usr/etc/ls_admin -a -n express -p "Silicon Graphics" \ CASEVision/Workshop 45nuhusrc5atda5wq7q3sn78fnaa 1.1.1ID="68191"If just one license password is listed on the license information sheet, the license is installed and you can skip to step IDREF="57592" TYPE="TEXT"8 . If there are two or more license passwords listed and just one set of vendor password, name, and ID, continue with this procedure.ID="25571"Copy the vendor information to another Network License Server:/usr/etc/ls_admin -f   license_server   -n   other_server   -v   v_namelicense_server and v_name are the same Network License Server and vendor name as in steps IDREF="88866" TYPE="TEXT"3 and IDREF="39048" TYPE="TEXT"4 . other_server is the Network License Server you want to install the license on. If any of these strings contain spaces, the strings must be surrounded with double quotes ("). For example:/usr/etc/ls_admin -f express -n annie \ -v "Silicon Graphics"ID="29487"Specify the product information for the second license:/usr/etc/ls_admin -a -n   other_server   -l   l_annotation   \ -p   v_name   p_name   l_password2 p_versionother_server is the same as in step IDREF="25571" TYPE="TEXT"5 .   l_annotation is the license annotation shown on the license information sheet (omit -l   l_annotation if there is no license annotation).   v_name, p_name, l_password2, and p_version are the vendor name, product name, second license password, and product version from the license information sheet. If any of these strings contain spaces, the strings must be surrounded with double quotes ("). For example:/usr/etc/ls_admin -a -n annie \ -p "Silicon Graphics" "CASEVision/Workshop" \ j8wh4wrdewgjuuspwfhntwvngwaa "1.1.1" Repeat steps IDREF="25571" TYPE="TEXT"5 and IDREF="29487" TYPE="TEXT"6 if there are additional licenses listed on the license information sheet.ID="57592"Save the license information sheet; you may need it again later if you need to reinstall this license.ID="ch520"ID="ch521"ID="ch522"LBL="6"ID="75227"License Administration TasksThis chapter explains how to perform various license administration tasks for both node-locked licenses and concurrent licenses. The tasks covered are:IDREF="34189" TYPE="TITLE""Verifying That a License Was Installed Properly"IDREF="46782" TYPE="TITLE""Deleting a Node-locked License"IDREF="84369" TYPE="TITLE""Deleting a Concurrent License"IDREF="95135" TYPE="TITLE""Creating a User File"IDREF="72045" TYPE="TITLE""Monitoring License Usage"IDREF="28712" TYPE="TITLE""Generating Reports on License Activity"IDREF="20799" TYPE="TITLE""Identifying Licenses in a Nodelock File"IDREF="34595" TYPE="TITLE""Installing Replacement Licenses"LBL="" HELPID=""ID="34189"Verifying That a License Was Installed ProperlyTo verify that a license was installed properly, try using one of the product's applications that is license protected. The release notes for each product list the licensed applications.ID="ch61"ID="ch62"If the application works, the license is installed and accessible. If you get a message that no license can be found, see IDREF="59073" TYPE="TITLE""License or Server Not Found" in Chapter 8 .LBL="" HELPID=""ID="46782"Deleting a Node-locked LicenseTo delete a node-locked license, simply remove the line containing the license and any comments that go with it from the ID="ch63"ID="ch64"/var/netls/nodelock (/usr/netls/nodelock on IRIX Release 5.0 and earlier) file. Instead of deleting the license line, you can leave the license in the file as a comment by putting a # (comment character) at the beginning of the license line.If you do not know which license line in the file is the one you need to delete because there are no comments, see IDREF="20799" TYPE="TITLE""Identifying Licenses in a Nodelock File" in Chapter 6 .On IRIX 5.0.1 or later, do not delete the file ID="ch65"/var/netls/nodelock even if you have deleted the last license in the file, because there is a symbolic link from /usr/netls/nodelock to this file. Breaking this link may prevent applications from running properly in the future.LBL="" HELPID=""ID="84369"Deleting a Concurrent LicenseTo delete a concurrent license, follow one of the procedures below. The first procedure can be used on a graphics terminal only; the second procedure doesn't require graphics.ID="ch66"Remember that when you delete a concurrent license, the software product is no longer available to users. Deleting a license cannot be undone; you must reinstall the license.Follow these steps to use the graphical version of ls_admin(1M) to delete a concurrent license:Become superuser:/bin/su -    Password: Give this command to start ID="ch67"ls_admin:/usr/etc/ls_admin   A window border appears. After you position the window border and click the left mouse button, the ls_admin window appears.Select the system where you installed the temporary license from the list in the Servers area.Click the Vendor button. The Servers area becomes the Vendors area with a list of vendors.Select the vendor of the product. Click the Product button. The Vendors area becomes the Products area and a list of products appears.Select the product whose license you want to delete from the list of products. Click the License button. The Products area becomes a Licenses area and a list of one or more licenses appears.Select the license you want to delete from the list of licenses. Click the Delete... button. A dialog box appears requesting confirmation.Click the Delete button in the dialog box.Follow this procedure to delete a concurrent license using the ls_admin command-line interface.Become superuser:/bin/su -    Password: ID="54012"Get the timestamp of the license you want to delete:ID="ch68"ls_admin -s -p   v_name    LS_ADMIN Version 2.01 BL04 (c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved Server: ip:clarabelle.island.sodor.com     socket address family ip     socket address 192.132.142.4     socket port 1457     target type Irix     target id 69068635 Vendor: Silicon Graphics     vendor id 546fb4684914.02.c0.1a.3d.52.00.00.00 Product: CASEVision/Workshop [2.0]     id 1     Licenses:     1 Concurrent Access from 1993/05/21 to 1994/05/21, timestamp 737998264v_name is the vendor name of the product. Be sure to surround it with double quotes if it contains spaces. Identify the license you want to delete and look for its timestamp. The timestamp for CASEVision/Workshop in this example is 737998264.Give this command to delete the license:ls_admin -d -p   v_name   p_name   timestamp LS_ADMIN Version 2.01 BL04 (c) Copyright 1991, Hewlett-Packard Company, All Rights Reservedv_name is the vendor name, p_name is the product name (double-quoted if it contains spaces), and timestamp is the timestamp from step IDREF="54012" TYPE="TEXT"2 .To confirm that the license has been deleted, give this command:ls_admin -s -p   v_name    LS_ADMIN Version 2.01 BL04 (c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved Server: ip:pele.wpd.sgi.com     socket address family ip     socket address 192.132.142.4     socket port 1457     target type Irix     target id 69068635 Vendor: Silicon Graphics     vendor id 546fb4684914.02.c0.1a.3d.52.00.00.00The CASEVision/Workshop license has been deleted because it is no longer listed.ID="ch69"ID="ch610"LBL="" HELPID=""ID="95135"Creating a User FileA Network License Server user file, ID="ch611"/var/netls/user_file (/usr/netls/user_file on IRIX Release 5.0 and earlier), can be used to prohibit some users from using certain products or give different users of a product different access priorities. If you want all users to have access to all products with the same priority, you don't need a user file. User files are used for products licensed with concurrent licenses only.LBL="" HELPID=""A Sample User FileID="ch612"IDREF="51414" TYPE="TEXT"Example 6-1 shows a sample user file. In this example, the keywords are uppercase; they may be uppercase or lowercase, but mixed-case keywords are not allowed. Comments are preceded by a percent sign (%).% NetLS User File for Shining Clock Shop, Inc. CRAWL 10 % ********************************************** VENDOR "Silicon Graphics" CASEVision/Workshop ALLOW tanya -p 2 harry -p 1 stacy -p 1 matt % ********************************************** VENDOR "Mr. Conductor, Inc." ALL DISALLOW ringo george % ********************************************** VENDOR "Silicon Graphics" CASEVision/Tracker DISALLOW schemer VENDOR "Silicon Graphics" "IRIS Volume Manager" DISALLOW schemer VENDOR "Silicon Graphics" "IRIS Networker" DISALLOW schemerLBL="6-1"Example 6-1 ID="51414"Sample User FileThe meanings of the lines in the file in IDREF="51414" TYPE="TEXT"Example 6-1 are explained below.CRAWL 10This causes all users listed in the file to move up one level in priority after the product polls the queues of users waiting for licenses a specified number of times (in this case, 10 times). Using CRAWL makes sense only when different users have different priorities. The CRAWL keyword and user priorities apply only to products that use wait queues.VENDOR "Silicon Graphics" CASEVision/Workshop ALLOW tanya -p 2 harry -p 1 stacy -p 1 mattHere, the user file declares the vendor Silicon Graphics and its only installed product, CASEVision/Workshop. The vendor name contains spaces, so it is delimited by double quotes. The product name is not quoted because it contains no spaces. Four users may use CASEVision/Workshop: Tanya is a priority 2 user; Harry and Stacy are priority 1 users (the highest), and Matt's unspecified priority defaults to priority 3 (the lowest).ID="ch613"ID="ch614"When a high-priority user requests a license for which low-priority users are already waiting, the high-priority user moves ahead of the lower-priority users in the queue. In this case, if Matt and Tanya are unsuccessful in obtaining a license and are willing to wait, CRAWL eventually changes their priority to 1. At that time, the declared priority 1 users (Harry and Stacy) can no longer displace Matt and Tanya in the user queue.VENDOR "Mr. Conductor, Inc." ALL DISALLOW ringo georgeThe keyword ALL means that all licensed products of this vendor (whatever those products may be) have the same user authorizations. In this case, everyone except Ringo and George may use all Mr. Conductor software products.VENDOR "Silicon Graphics" CASEVision/Tracker DISALLOW schemer VENDOR "Silicon Graphics" "IRIS Volume Manager" DISALLOW schemer VENDOR "Silicon Graphics" "IRIS Networker" DISALLOW schemerThese lines specify three products of Silicon Graphics: CASEVision/Tracker, IRIS Volume ManagerÔ, and IRIS NetworkerÔ. There is one VENDOR line for each product. The keyword DISALLOW excludes only Schemer from using the three products of Silicon Graphics. All other users are priority 3 by default.Since this user file specifies the products of Silicon Graphics individually, Silicon Graphics probably has other installed products that anyone, including Schemer, may use. If CASEVision/Tracker, IRIS Volume Manager, and IRIS Networker were the only installed products of Silicon Graphics (and Schemer was prohibited from using them), you would use the keyword ALL in the user file, as shown below, instead of specifying each product individually.VENDOR "Silicon Graphics" ALL DISALLOW schemerLBL="" HELPID=""User File SyntaxID="ch615"IDREF="65701" TYPE="TEXT"Example 6-2 shows the format of the file   /var/netls/user_file (/usr/netls/user_file on IRIX Release 5.0 and earlier). Square brackets, [], indicate optional items and vertical bars, |, indicate either the item on the left or the item on the right can be used.% comment [CRAWL n] VENDOR 1st_vendor_name 1st_product_name|ALL ALLOW|DISALLOW 1st_user_id [-P 1|2] nth_user_id [-P 1|2] VENDOR nth_vendor_name nth_product_name|ALL ALLOW|DISALLOW 1st_user_id [-P 1|2] nth_user_id [-P 1|2]LBL="6-2"Example 6-2 ID="65701"User File SyntaxYou may specify any number of vendors with associated products and user authorizations, and any number of user names (or none) may follow the ALLOW or DISALLOW keywords. Keywords may be uppercase or lowercase, but mixed-case keywords are not allowed. Single or double quotes must delimit vendor or product names that contain spaces. Comments can be used anywhere.These keywords can be included in a user file:ID="ch616"CRAWLCauses the priority of users to be changed to the next higher priority after the application has polled the queue n times. CRAWL may be specified only once in a user file. This keyword applies only to products that use queuing.VENDORSpecifies the vendor of a licensed product(s). Either ALL or the name of a single product must follow the declaration of a VENDOR.ALLSpecifies that all of the vendor's products have the same user authorizations. The keyword ALL and the name of a single product are mutually exclusive.ALLOWSpecifies that the user names following this keyword are allowed to use the product(s). If no user names follow this keyword, it means no users are allowed to use the product(s). ALLOW and DISALLOW are mutually exclusive.DISALLOWSpecifies that the user names following this keyword are not allowed to use the product(s). If no user names follow this keyword, it means all users are allowed to use the product(s). ALLOW and DISALLOW are mutually exclusive.­P 1Specifies a priority-1 user (highest priority). Priority-1 users may displace lower-priority users already waiting in a queue. Default if omitted: priority-3 (lowest priority). This keyword applies only to products that use queuing.­P 2Specifies a priority-2 user. Priority-2 users may displace priority-3 users already waiting in a queue. Default if omitted: priority 3. This keyword applies only to products that use queuing.LBL="" HELPID=""Writing and Integrating User FilesIf you decide to have a user file, you can use any text editor to create it. Put one copy on each Network License Server in the file ID="ch617"/var/netls/user_file (/usr/netls/user_file on IRIX Release 5.0 and earlier). You can write different user files for different Network License Servers, or put user files on some servers and not on others. However, such a policy might cause user access to a product to vary depending upon which server is granting the license. You should put the same user file on all servers in the interests of a consistent user authorization policy.You can use the ID="ch618"ls_admin command to check that the format of a user file is correct. See the ls_admin(1M) manual page for more information.LBL="" HELPID=""Maintaining User FilesWhen you add a new product or wish to change user priorities for existing products, remember to update the user files at all Network License Server systems accordingly. The ID="ch619"rdist(1C) command can be used to update these files automatically. See the rdist(1C) manual page for more information.LBL="" HELPID=""ID="72045"Monitoring License UsageID="ch620"ID="ch621"ls_stat(1M) provides users and administrators with status information including:The names of Network License Servers on the networkThe licensed products at all servers or at selected serversThe current users of licensed products and their user ID, host name, group, number of licenses held, and the times they started using the productsThe licenses installed at each Network License Server, the number of active licenses, and their start and expiration datesThe use of products: the number of licenses in use, the total number of licenses, and the licenses availablels_stat has both a graphical interface and a command-line interface. The steps below demonstrate how to get information from ls_stat using its graphical interface:Give this ls_stat command:/usr/etc/ls_stat   The ls_stat window appears with a list of Network License Servers and a list of products. Select a server and the product you are interested in.Click the Installed button to get the number of licenses for the selected product that are installed at the selected server.Click the Usage button to get the number of users of the selected product at the selected server.Click the All Users button to get the user IDs and host names of all of the users of the selected product at the selected server.Click the User button to bring up a User Name window. Enter the user ID of a user in which you are interested, then click the OK button. Information about usage of the selected product at the selected server by that user is displayed.Select "All" as the server and/or product to obtain information about all servers and products at once. Click the All Servers (Update) button to poll the network and update the server list. A check mark appears to indicate that all existing Network License Servers are displayed, and the vendors and products listed exist at the currently selected server.Click the All Products (Update) button to poll the network and update the product list. A check mark appears to indicate that all existing vendors and products are displayed, and the listed servers hold licenses for the product or vendor currently selected.The ls_stat(1M) manual page provides additional reference information on the graphical interface and on the alternative command-line interface.LBL="" HELPID=""ID="28712"Generating Reports on License ActivityThe ID="ch622"ID="ch623"ls_rpt(1M) command generates reports on all kinds of Network License Server activities that are based on the log of license activity kept by netlsd(1M). To use ls_rpt, give the command:/usr/etc/ls_rpt   A report is printed to the screen.With command-line arguments, you can specify different kinds of events to be reported (as well as all events) and use dates, software vendors, products, and users as information filters. Besides helping you monitor Network License Server activities, Network License Server reports can help you track demand for software products. This kind of information is useful in planning purchases of licenses for those products. For complete information on ls_rpt, see the ls_rpt(1M) manual page.LBL="" HELPID=""ID="20799"Identifying Licenses in a Nodelock FileIf you need to locate a specific license in a ID="ch624"ID="ch625"ID="ch626"/var/netls/nodelock or /usr/netls/nodelock file, possibly because it is a temporary license you want to delete, or if you want to find out what products have node-locked licenses on a particular system, use these techniques:Look for comments that give the product name for each license. The recommended convention is to put a comment line (comment lines start with #) that includes the product name before each license line.If you are looking for the license for a particular product, comment out all licenses except one. Try running a licensed application (see the release notes for the product for a list of licensed commands) to see if its license is the uncommented one. Test each license until you find the one you want.To figure out what products the licenses might be for, give the ID="ch627"versions(1M) command to list the installed products. Use the release notes for the products, if necessary, to identify which products require licenses. For each product, use the technique in the previous bullet to figure out if the license file contains a valid license for the product.LBL="" HELPID=""ID="34595"Installing Replacement LicensesAny time you install a license because a previous license for the same product is obsolete, you are installing a replacement license. The old and new licenses need not be of the same type: a concurrent license can replace a node-locked license or vice versa. Replacement licenses are sometimes needed when:ID="ch628"ID="ch629"ID="ch630"ID="ch631"ID="ch632"ID="ch633"The original license is a temporary licenseSystem or network reconfiguration results in a node-locked licensed application running on a system with a different system identification numberSystem or network reconfiguration results in a change in the system identification number of a Network License ServerYou upgrade to a new version of a licensed product (see the release notes for the product to determine if a new license is required)Follow these steps to install a replacement license:Remove the old license using IDREF="46782" TYPE="TITLE""Deleting a Node-locked License" or IDREF="84369" TYPE="TITLE""Deleting a Concurrent License" in this chapter.If the new license is a node-locked license, install it using the instructions in IDREF="34618" TYPE="TITLE"Chapter 3, "Installing Node-locked Licenses."If the new license is a concurrent license and the old license was a node-locked license, set up a Global Location Broker and a Network License Server if necessary using the instructions in IDREF="93641" TYPE="TITLE"Chapter 4, "Setting Up Global Location Brokers and Network License Servers."If the new license is a concurrent license, install it using the instructions in IDREF="99449" TYPE="TITLE"Chapter 5, "Installing Concurrent Licenses."LBL="7"ID="22501"Global Location Broker and Network License Server Administration TasksThis chapter explains how to perform various administrative tasks on Global Location Brokers and Network License Servers. The first two sections describe tasks that should be done on a regular basis; the remainder should be done as needed. The sections are:IDREF="99624" TYPE="TITLE""Backing Up Databases"IDREF="86397" TYPE="TITLE""Routine Maintenance of Global Location Brokers"IDREF="91739" TYPE="TITLE""Verifying That llbd Is Running"IDREF="38612" TYPE="TITLE""Checking Global Location Brokers"IDREF="38729" TYPE="TITLE""Checking Network License Servers"IDREF="42084" TYPE="TITLE""Stopping Daemons"IDREF="50200" TYPE="TITLE""Restarting Daemons"IDREF="32117" TYPE="TITLE""Creating a New License Group"IDREF="20673" TYPE="TITLE""Adding a System to a License Group"IDREF="54059" TYPE="TITLE""Reducing the Size of Network License Server Logs"IDREF="10104" TYPE="TITLE""Cleaning GLB Databases"IDREF="97379" TYPE="TITLE""Using glb_site.txt Files"IDREF="21945" TYPE="TITLE""Deleting a Network License Server"IDREF="73561" TYPE="TITLE""Deleting a Global Location Broker"IDREF="62100" TYPE="TITLE""Adjusting to Network Reconfigurations"LBL="" HELPID=""ID="99624"Backing Up DatabasesGLB databases, Concurrent License databases, and the nodelock license file should be saved onto backup media periodically as part of regular backups. The files to back up are:ID="ch71"ID="ch72"ID="ch73"/var/netls/nodelock (/usr/netls/nodelock on IRIX Release 5.0 and earlier) on systems running node-locked applications/var/ncs/* (/usr/etc/ncs/* on IRIX Release 5.0 and earlier) on all systems that are Global Location Brokers/var/netls/* (/usr/netls/* on IRIX Release 5.0 and earlier) on all systems that are Network License Servers If a GLB database is restored from a backup, it could have obsolete information that is inconsistent with other Global Location Brokers. IDREF="86397" TYPE="TITLE""Routine Maintenance of Global Location Brokers" and IDREF="10104" TYPE="TITLE""Cleaning GLB Databases" in this chapter describe some recommended restoration procedures.LBL="" HELPID=""ID="86397"Routine Maintenance of Global Location BrokersReplicated Global Location Brokers require some maintenance to ensure consistency among the Global Location Brokers. Global Location Broker consistency problems are minimized if:ID="ch74"All Global Location Brokers are kept running and available.The clocks on systems running Global Location Brokers are closely synchronized. Problems are likely to occur if clocks become skewed by more than a few minutes or if some Global Location Brokers are stopped (for example, due to hardware failure) or unavailable (for example, due to network failure) for several days. Running ID="ch75"ID="ch76"timed(1M) on each Global Location Broker enables these systems to synchronize their clocks automatically.The procedure below should be done every week or so to perform routine maintenance on the Global Location Brokers even if there are no apparent discrepancies in the GLB databases. In the example output below, thomas, henry, and percy are example host names.ID="ch77"Use drm_admin(1M) to check for clock skew:/usr/etc/drm_admin    drm_admin: set -o glb -h ip:thomas     Default object: glb default host: ip:thomas state: in service     Checking clocks of glb replicas     ip:thomas.island.sodor.com 1993/05/13.11:47     ip:henry.island.sodor.com 1993/05/13.15:13 *** clock skew warning ***     ip:percy.island.sodor.com 1993/05/12.59:26 *** clock skewed *** drm_admin: You can choose any Global Location Broker on the network when you give the ID="ch78"ID="ch79"set subcommand. If drm_admin finds that the clock of another Global Location Broker is more than two minutes different from the specified one, it prints one of these two messages:*** clock skew warning *** This message indicates that the clock disagrees with the clock of the system named in the set subcommand by more than two minutes and less than 10 minutes. You can continue to run these Global Location Brokers (at increased risk of database inconsistencies), but you should reset a clock to eliminate the difference as soon as possible.*** clock skewed *** This message indicates that a clock disagrees with the clock of the system specified in the set subcommand by more than 10 minutes. If the clocks at two systems are skewed by more than 10 minutes, the Global Location Brokers at those systems don't propagate updates to each other and do not perform drm_admin merge operations. You should reset the clocks immediately.Set clocks as necessary using the date(1) command.Use the ID="ch710"merge_all subcommand of drm_admin to reconcile copies of the database:drm_admin: merge_all     Merge from ip:henry.island.sodor.com done     Merge from ip:percy.island.sodor.com done     Merge to ip:henry.island.sodor.com done     Merge to ip:percy.island.sodor.com done     Merge_all successfully completed drm_admin: quit   LBL="" HELPID=""ID="91739"Verifying That llbd Is RunningTo verify that ID="ch711"ID="ch712"ID="ch713"llbd(1M) is running properly, give these commands on the system that is running llbd (shown with example output):/usr/etc/lb_admin    lb_admin: lookup    ------------     object = glb/object     type = glb/type     interface = 33599c670000.0d.00.00.24.34.00.00.00 "rdrm" @ ip:edward.island.sodor.com[4350] ------------     object = glb/object     type = glb/type     interface = 3e188a057000.0d.00.00.be.8a.00.00.00 "rdrm_debug" @ ip:edward.island.sodor.com[4350] ------------     object = glb/object     type = glb/type     interface = 339a6e4fe000.0d.00.00.87.84.00.00.00 "rdrm_applic" @ ip:edward.island.sodor.com[4350] ------------     object = glb/object     type = glb/type     interface = glb/interface "/usr/etc/glbd" @ ip:edward.island.sodor.com[4350] ------------ lb_admin: quit    bye.If you get the message "No entries match", then the llbd database is empty.LBL="" HELPID=""ID="38612"Checking Global Location BrokersThe procedure below explains first how to get the name of a Global Location Broker, if there is one, in the network. The remainder of the procedure explains how to get the names of other Global Location Brokers, if any, and verify that each Global Location Broker is running. ID="ch714"ID="ch715"Give the ID="ch716"lb_admin(1M) command and two subcommands to determine if there is a Global Location Broker in the network, for example:/usr/etc/lb_admin    lb_admin: use global lb_admin: lookup     Data from GLB replica: ip:thomas.island.sodor.com ------------     object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00     type = nls     interface = nls "NLS @ ip:gordon.island.sodor.com" @ ip:gordon.island.sodor.com[4467] global ------------ ...This lookup subcommand was successful. The first line of output contains the name of a Global Location Broker. In this example, it is thomas. If the ID="ch717"ID="ch718"lookup subcommand can't find a Global Location Broker, you get this error message:?(lb_admin) communications failure (network computing system/RPC runtime) No entries match.lb_admin doesn't always succeed on the first try, so if you get this error message, try again:lb_admin: lookupIf you receive an error message after you issue the lookup subcommand a second time, you can assume that there are no Global Location Brokers in the network.Exit lb_admin with this subcommand:lb_admin: quit bye.To get the names of additional Global Location Brokers and to verify that all Global Location Brokers are running, give these commands:ID="ch719"ID="ch720"/usr/etc/drm_admin    drm_admin: set -o glb -h ip:hostname     Default object: glb default host: ip:thomas state: in service     Checking clocks of glb replicas     ip:thomas.island.sodor.com 1993/04/06.11:00     ip:gordon.island.sodor.com 1993/04/06.11:00 drm_admin: quithostname is the name of a Global Location Broker (probably the one from the first line of the output from the lb_admin lookup command; it is thomas in this example). The output lists the names of Global Location Brokers in the network. In this example, both of the Global Location Brokers, thomas and gordon, are running. When Global Location Brokers have been set up but aren't currently running, you see these messages:ID="ch721"If the Global Location Broker that is not running is the one you specified in the set subcommand, this is the error message:    Default object: glb default host: ip:thomas status: not communicating communications failure (network computing system/RPC runtime)If other Global Location Brokers aren't running, you see an error message like this:ID="ch722"    ip:james.island.sodor.com *** clock unavailable ***LBL="" HELPID=""ID="38729"Checking Network License ServersThe ID="ch723"ID="ch724"lb_admin, ls_tv(1M), ls_stat(1M), and ls_admin(1M) commands provide information about Network License Servers in the network. Each command performs slightly different functions, which are explained in the next sections.LBL="" HELPID=""Checking Network License Servers Using ls_adminID="ch725"ls_admin quickly and graphically lists Network License Servers but does not automatically verify that the Network License Servers are running. To use ls_admin, give this command as superuser:/usr/etc/ls_admin   Network License Servers are listed in the Servers area. To check to see if a particular server is running, select it. Messages are printed in the scrolling area at the bottom. This message indicates that server bertie is running:Consulting server Connected to server: bertie.island.sodor.comThis message indicates that the Network License Server harold is not running:ID="ch726"Consulting server ?(ls_admin) communications failure (network computing system/RPC runtime) Connected to server: harold.island.sodor.comLBL="" HELPID=""Checking Network License Servers Using lb_adminID="ch727"ID="ch728"lb_admin quickly lists Network License Servers (and the vendors on each Network License Server), but does not verify that the Network License Servers are running. To use lb_admin for this purpose, give these commands:/usr/etc/lb_admin    lb_admin: use global lb_admin: lookup     Data from GLB replica: ip:thomas.island.sodor.com ------------     object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00     type = nls     interface = nls "NLS @ ip:bertie.island.sodor.com" @ ip:bertie.island.sodor.com[4467] global ------------     object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00     type = 3bd624ea7000.0d.00.00.80.9c.00.00.00     interface = 3bd624ea7000.0d.00.00.80.9c.00.00.00 "NLS[2.0] @ ip:bertie.island.sodor.com" @ ip:bertie.island.sodor.com[4467] global ------------     object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00     type = 4ca0fd5cf000.0d.00.02.1a.9a.00.00.00     interface = 3bd624ea7000.0d.00.00.80.9c.00.00.00 "NLS[2.0]: Hewlett-Packard NetLS Test" @ ip:bertie.island.sodor.com[4467] global ------------     object = 5e9cf4bb5a8c.02.c0.1a.4f.0d.00.00.00     type = 5806f403b277.02.82.f8.d0.17.00.00.00     interface = 3bd624ea7000.0d.00.00.80.9c.00.00.00 "NLS[2.0]: Adobe Systems" @ ip:bertie.island.sodor.com[4467] global ------------ ... lb_admin: quit bye.Each block of lines between rows of dashes is for a vendor on a Network License Server. Look at the last line of each block to see the Network License Server name.LBL="" HELPID=""Checking Network License Servers Using ls_tvID="ch729"ls_tv lists all Network License Servers and verifies that they are running (a dummy test product, Hewlett Packard NetLS Test, which is always installed by default, must be present on each Network License Server; see ls_tv(1M) for more information). This command can take some time as it communicates with each Network License Server. Give this command:/usr/etc/ls_tv    LS_TV Version 2.01 BL04 -- NetLS Test and Verification Tool (c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved Completed license transaction on node 690217e7 running NetLS 2.01 BL04 Active NetLS Servers:     bertie.island.sodor.com (Irix) running NetLS 2.01 BL04     harold.island.sodor.com (Irix) running NetLS 2.01 BL04     donald.island.sodor.com (Irix) running NetLS 2.01 BL04     douglas.island.sodor.com (Irix) running NetLS 2.01 BL04     #192.82.171.202 (Irix) running NetLS 2.01 BL04     trevor.island.sodor.com (Irix) running NetLS 2.01 BL04See the ls_tv(1M) manual page for more information and explanations of the error messages displayed by ls_tv.LBL="" HELPID=""Checking Network License Servers Using ls_statID="ch730"ls_stat lists all running Network License Servers and their licenses. To run the graphical version of ls_stat, give this command:/usr/etc/ls_stat   The Network License Servers are listed in the center area under the All Servers (Update) button when it first comes up. It can take a while for ls_stat to come up, because it is checking Network License Servers.To use the command-line interface version of ls_stat, give this command:/usr/etc/ls_stat -i    LS_STAT Version 2.01 BL04 (c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved Installed Licenses Hewlett-Packard NetLS Test    NetLS Test Product [1.0]     On server: donald.island.sodor.com     Wait queue length: 0     Licenses Type In Use Start Date Expiration Date     10000 concurrent 0 Jan 1 1970 Jan 20 2038     Total active 10000 0     On server: douglas.island.sodor.com     Wait queue length: 0     Licenses Type In Use Start Date Expiration Date     10000 concurrent 0 Jan 1 1970 Jan 20 2038     Total active 10000 0     On server: trevor.island.sodor.com     Wait queue length: 0     Licenses Type In Use Start Date Expiration Date     10000 concurrent 0 Jan 1 1970 Jan 20 2038     Total active 10000 0     On server: harold.island.sodor.com     Wait queue length: 0     Licenses Type In Use Start Date Expiration Date     10000 concurrent 0 Jan 1 1970 Jan 20 2038     Total active 10000 0The "On server" lines list Network License Servers.ID="ch731"ID="ch732"LBL="" HELPID=""ID="42084"Stopping DaemonsTo stop daemons on a Global Location Broker (ID="ch733"ID="ch734"ID="ch735"ID="ch736"glbd(1M) and llbd), give this command as superuser:/etc/init.d/nck stop   To stop daemons on a Network License Server (netlsd(1M) and llbd), give these commands as superuser:/etc/init.d/netls stop    /etc/init.d/nck stop   LBL="" HELPID=""ID="50200"Restarting DaemonsThe following sections describe how to restart daemons. Choose the section that is appropriate for your situation. Remember that to operate correctly, daemons must be started in a particular order on a single system and in a particular order on a network (see IDREF="85083" TYPE="TITLE""Required Software, Configuration Flags, and Daemons" in Chapter 1 for more information).LBL="" HELPID=""Restarting Daemons for a Global Location BrokerTo restart the daemons (ID="ch737"ID="ch738"llbd and glbd) for a Global Location Broker, give these commands:Become superuser:/bin/su -    Password: Set the glb and llb chkconfig(1M) flags to "on" in case they aren't set correctly:/etc/chkconfig glb on    /etc/chkconfig llb on   Start llbd and glbd:/etc/init.d/nck start   LBL="" HELPID=""Restarting Daemons for a Network License ServerFollow these steps to restart the daemons for a Network License Server (ID="ch739"llbd and netlsd):Become superuser:/bin/su -    Password: Set the llb and netls chkconfig(1M) flags to "on" in case they aren't set correctly:/etc/chkconfig llb on    /etc/chkconfig netls on   If this system is not a Global Location Broker, set the glb chkconfig(1M) flag "off" in case it isn't set correctly:chkconfig glb off   Start llbd:/etc/init.d/nck start   Start netlsd:/etc/init.d/netls start   LBL="" HELPID=""ID="30502"Restarting All Daemons on a NetworkThis procedure restarts all the daemons on a network in a way that ensures that they all "know about each other" and share the same GLB database.ID="ch740"ID="ch741"On each Global Location Broker, become superuser and remove its GLB database and Global Location Broker list. On IRIX 5.0.1 or later, give these commands:ID="ch742"/bin/su -    Password: rm /var/ncs/glb.*   On IRIX 5.0 or earlier, give these commands:/bin/su -    Password: rm /usr/etc/ncs/glb.*   ID="78813"On one Global Location Broker, set the llb and glb chkconfig flags to "on" in case they aren't set correctly and restart the llbd and glbd daemons by giving these commands:/bin/su -    Password: /etc/chkconfig glb on    /etc/chkconfig llb on    /etc/init.d/nck start   On each of the remaining Global Location Brokers, set the chkconfig flags and restart the daemons by giving these commands:/bin/su -    Password: /etc/chkconfig glb on    /etc/chkconfig llb on    /usr/etc/llbd    /usr/etc/glbd -create -from ip:other_GLB_hostname   &   other_GLB_hostname is the host name of the Global Location Broker in step IDREF="78813" TYPE="TEXT"2 .On each Network License Server that is also a Global Location Broker, set the netls chkconfig flag and restart the netlsd daemon by giving these commands:/bin/su -    Password: /etc/chkconfig netls on    /etc/init.d/netls start   On each Network License Server that is not a Global Location Broker, set the llb, glb, and netls chkconfig flags and restart the daemons (llbd and netlsd) by giving these commands:/bin/su -    Password: chkconfig glb off    chkconfig llb on    chkconfig netls on    /etc/init.d/nck start    /etc/init.d/netls start   LBL="" HELPID=""ID="32117"Creating a New License GroupTo turn one or more Network License Servers and one or more Global Location Brokers into a license group, follow these steps:ID="ch743"Become superuser on one of the Network License Servers or Global Location Brokers:/bin/su -    Password: Start ls_admin to get a list of all Network License Servers:/usr/etc/ls_admin   ID="86479"Write down the names of the Network License Servers that appear in the Servers area.Exit ls_admin.On each of the Network License Servers you wrote down in step IDREF="86479" TYPE="TEXT"3 , become superuser and stop the netlsd daemon:/bin/su -    Password: killall netlsd   ID="93831"On one of the Network License Servers or Global Location Brokers, get the names of all Global Location Brokers by giving these commands:/usr/etc/drm_admin    drm_admin: set -o glb -h ip:hostname     Default object: glb default host: ip:thomas state: in service     Checking clocks of glb replicas     ip:thomas.island.sodor.com 1993/04/06.11:00     ip:gordon.island.sodor.com 1993/04/06.11:00 drm_admin: quithostname is the name of any Global Location Broker you want to include in the license group. The names of the rest of the Global Location Brokers appear after Checking clocks ....On each of the Global Location Brokers in step IDREF="93831" TYPE="TEXT"6 , become superuser and stop the llbd and glbd daemons:/bin/su -    Password: /etc/init.d/nck.stop   ID="75980"On one of the Network License Servers or Global Location Brokers, create a ID="ch744"ID="ch745"glb_obj.txt file:/usr/etc/uuid_gen > /usr/tmp/glb_obj.txt   On each system that is to be part of the license group and is running IRIX 5.0.1 or later, give these commands to create the directory /var/ncs, in case it doesn't already exist, and make a copy of the glb_obj.txt file you created in step IDREF="75980" TYPE="TEXT"8 :/bin/su -    Password: mkdir /var/ncs    rcp guest@hostname:/usr/tmp/glb_obj.txt /var/ncs/glb_obj.txt   hostname is the name of the system where you performed step IDREF="75980" TYPE="TEXT"8 .On each system that is to be part of the license group and is running IRIX 5.0 or earlier, give these commands to create the directory /usr/etc/ncs, in case it doesn't already exist, and make a copy of the glb_obj.txt file you created in step IDREF="75980" TYPE="TEXT"8 :/bin/su -    Password: mkdir /usr/etc/ncs    rcp guest@hostname:/usr/tmp/glb_obj.txt \ /usr/etc/ncs/glb_obj.txt   hostname is the name of the system where you performed step IDREF="75980" TYPE="TEXT"8 .Restart all of the daemons on all of the Network License Servers and Global Location Brokers on the network by following the procedure in IDREF="30502" TYPE="TITLE""Restarting All Daemons on a Network" in this chapter.LBL="" HELPID=""ID="20673"Adding a System to a License GroupThe following sections describe how to add a system to an existing license group. Use the section that is appropriate for the system you want to add.ID="ch746"LBL="" HELPID=""System Is Not a Network License Server or a Global Location BrokerCopy the glb_obj.txt file from a system that is already in the license group when you want to add a system that is not a Network License Server or a Global Location Broker to a license group. Give these commands on the system that you want to add:/bin/su -    Password: mkdir todir    rcp guest@hostname:fromdir/glb_obj.txt todir/glb_obj.txt   hostname is the name of the system that you are getting glb_obj.txt from. If hostname is running IRIX Release 5.0.1 or later, fromdir is /var/ncs. If hostname is running IRIX Release 5.0 or earlier, fromdir is /usr/etc/ncs. If the system you are adding is running IRIX Release 5.0.1 or later, todir is /var/ncs. If the system you are adding is running IRIX Release 5.0 or earlier, todir is /usr/etc/ncs.LBL="" HELPID=""System Is a Network License Server and a Global Location BrokerFollow these steps when you want to add a system that is already a Global Location Broker and a Network License Server to a license group:Stop the netlsd daemon on the system that you want to add:/bin/su -    Password: /etc/init.d/netls stop   Follow the instructions in IDREF="72572" TYPE="TITLE""Using drm_admin delrep" in the chapter to delete the Global Location Broker from the system that you want to add to the license group.ID="91079"Copy the glb_obj.txt file from a Global Location Broker in the license group to the system you want to add:mkdir todir    rcp guest@hostname:fromdir/glb_obj.txt todir/glb_obj.txt   hostname is the name of a Global Location Broker in the license group. (If you do not know which system is a Global Location Broker, see IDREF="38612" TYPE="TITLE""Checking Global Location Brokers" in this chapter.) If hostname is running IRIX Release 5.0.1 or later, fromdir is /var/ncs. If hostname is running IRIX Release 5.0 or earlier, fromdir is /usr/etc/ncs. If the system you are adding is running IRIX Release 5.0.1 or later, todir is /var/ncs. If the system you are adding is running IRIX Release 5.0 or earlier, todir is /usr/etc/ncs.On the system you want to add, restart the Network License Server and Global Location Broker by giving these commands:llbd    glbd -create -from   hostname    /etc/init.d/netls start   hostname is the name of the Global Location Broker from step IDREF="91079" TYPE="TEXT"3 .LBL="" HELPID=""System Is a Network License ServerTo add a system that is a Network License Server to a license group, follow these steps:Become superuser on the system that you want to add:/bin/su -    Password: Stop the netlsd daemon:/etc/init.d/netls stop   Copy the glb_obj.txt file from a Global Location Broker in the license group to the system you want to add:mkdir todir    rcp guest@hostname:fromdir/glb_obj.txt todir/glb_obj.txt   hostname is the name of a Global Location Broker in the license group. (If you do not know which system is a Global Location Broker, see IDREF="38612" TYPE="TITLE""Checking Global Location Brokers" in this chapter.) If hostname is running IRIX Release 5.0.1 or later, fromdir is /var/ncs. If hostname is running IRIX Release 5.0 or earlier, fromdir is /usr/etc/ncs. If the system you are adding is running IRIX Release 5.0.1 or later, todir is /var/ncs. If the system you are adding is running IRIX Release 5.0 or earlier, todir is /usr/etc/ncs.Restart the netlsd daemon:ID="ch747"ID="ch748"/etc/init.d/netls start   LBL="" HELPID=""ID="54059"Reducing the Size of Network License Server LogsYou can use ID="ch749"ID="ch750"ls_rpt(1M) to reduce the size of the netlsd log file, /var/netls/log_file (/usr/netls/log_file on IRIX Release 5.0 and earlier). Give the command:/usr/etc/ls_rpt -x   yy/mm/ddyy/mm/dd is a date. Log messages from this date or earlier are deleted.LBL="" HELPID=""ID="10104"Cleaning GLB DatabasesOver time, GLB databases can accumulate entries for Network License Servers that no longer exist, possibly because of network reconfigurations or because they were set up only temporarily. You can use the ID="ch751"ID="ch752"lb_admin command to detect and delete these obsolete entries. It is a good idea to do this periodically or if license retrieval is slow.On a system that is a Global Location Broker, give these commands:ID="ch753"/usr/etc/lb_admin    lb_admin: clean    lb_admin: use global    lb_admin: clean   When lb_admin encounters an obsolete entry or an entry for a Network License Server that doesn't respond to an attempt to contact it, it asks you if you want to delete it. Enter y or yes to delete it and n or no to leave it in the database. You should delete entries (Network License Servers) that you know are obsolete. In some cases, you may be prompted about a Network License Server that you know is not obsolete. This can happen because the Network License Server is not responding due to a network failure or because the Network License Server system is down temporarily. When you know the Network License Server is not obsolete, follow these steps:Respond to the lb_admin prompt with yes to delete the entry for this Network License Server.Stop the Network License Server daemons on the Network License Server by giving these commands on that system:/bin/su -    Password: /etc/init.d/netls stop    /etc/init.d/nck stop   Restart the Network License Server daemons on the Network License Server by giving these commands on that system:/bin/su -    Password: /etc/init.d/nck start    /etc/init.d/netls start   When the Network License Server daemons are restarted, the Network License Server reregisters itself with the Global Location Broker.See the lb_admin(1M) manual page for additional information about how lb_admin determines obsolete entries and the possible responses when it finds an obsolete entry. LBL="" HELPID=""ID="97379"Using glb_site.txt FilesID="ch754"glb_site.txt files contain a list of the network addresses of systems that are Global Location Brokers. These files are useful when:The usual broadcast mechanism can't be used to find Global Location Brokers.ID="ch755"You don't want to use the usual broadcast mechanism when Global Location Brokers attempt to communicate with each other, possibly because of the volume of network traffic this generates.To create glb_site.txt files, follow this procedure on each system that will be running applications that request licenses:Become superuser:/bin/su -    Password: If you are running IRIX Release 5.0.1 or later and the directory /var/ncs doesn't exist, create it:mkdir /var/ncs   If you are running IRIX Release 5.0 or earlier and the directory /usr/etc/ncs doesn't exist, create it:mkdir /usr/etc/ncs   Using a text editor, open a file called /var/ncs/glb_site.txt (/usr/etc/ncs/glb_site.txt on IRIX Release 5.0 and earlier).Make a list in the file of each Global Location Broker system that you want this system to communicate with. You can use either the network address or host name for each Global Location Broker system. Each address or name must be preceded with "ip:", and IP addresses must be preceded with "#". For example, to specify that Global Location Brokers are present on the system named toby and on the system with IP address 192.9.8.7, put these two lines into the file:ip:toby    ip:#192.9.8.7   For more information on the glb_site.txt file, see the glb_site(4) manual page.LBL="" HELPID=""ID="21945"Deleting a Network License ServerIf a system is a Network License Server and you don't want it to be a Network License Server anymore, you must stop the daemons, prevent them from being restarted automatically, and remove the Concurrent License database. ID="ch756"If you are running IRIX Release 5.0.1 or later, give these commands on the system with the Network License Server you want to remove:ID="ch757"/bin/su -    Password: /etc/init.d/netls stop    chkconfig netls off    rm -f /var/netls/*db*   If you are running IRIX Release 5.0 or earlier, give these commands on the system with the Network License Server you want to remove:/bin/su -    Password: /etc/init.d/netls stop    chkconfig netls off    rm -f /usr/netls/*db*   LBL="" HELPID=""ID="73561"Deleting a Global Location BrokerThere are two different ways to delete Global Location Brokers. Normally, you use the ID="ch758"drm_admin(1M) command and its delrep subcommand described in IDREF="72572" TYPE="TITLE""Using drm_admin delrep" in this chapter. In extreme cases, when no other method works or when you require all Global Location Brokers to be deleted immediately, use the drm_admin reset command described in IDREF="98269" TYPE="TITLE""Using drm_admin reset" in this chapter.LBL="" HELPID=""ID="72572"Using drm_admin delrepThe ID="ch759"ID="ch760"delrep subcommand of the drm_admin command can be used to delete Global Location Brokers. The delrep subcommand puts the deleted glbd into the "deleted state" in which it does not accept client updates or queries. A Global Location Broker in the deleted state delivers all updates on its propagation queue to other Global Location Brokers. The Global Location Broker in the deleted state then delivers to the other Global Location Brokers a request to delete itself from their Global Location Broker lists. Finally, it deletes its own database and stops running. It can take a while for ID="ch761"ID="ch762"delrep to complete the deletion of a Global Location Broker.Follow these steps to use delrep:Invoke drm_admin:/usr/etc/drm_admin drm_admin:Specify a Global Location Broker that you are not planning to delete:drm_admin: set -o glb -h ip:hostname   Give the delrep subcommand once for each Global Location Broker you want to delete: drm_admin:    delrep ip:delhost1 drm_admin: delrep ip:delhost2Although the drm_admin prompt is returned immediately, the deletion process may take a while. To verify that a deletion has finished, give the ps(1) command to see whether glbd is still running on the system from which it was deleted. If the deletion takes too long to finish, use the reset subcommand of drm_admin as described in the next section.LBL="" HELPID=""ID="98269"Using drm_admin resetThe ID="ch763"reset procedure, which should be run only in extreme cases, uses the drm_admin reset command to delete Global Location Brokers. To delete most Global Location Brokers, use the delrep subcommand described in the previous section. The reset subcommand tells the Global Location Broker at the named system to delete its glbd, but does not propagate a request to delete the Global Location Broker from the Global Location Broker lists of other Global Location Brokers. Because it processes this way, you must run a successful merge_all subcommand before the reset subcommand and use the purgerep subcommand to delete the Global Location Broker from other systems' Global Location Broker lists after the reset.The reset procedure is given below. It uses example systems with host names thomas, henry, percy, and james. percy and james have the Global Location Brokers to be deleted.Invoke drm_admin and set the default system to a system other than the one to be deleted:/usr/etc/drm_admin drm_admin: set -o glb -h ip:thomas Default object: glb default host: ip:thomas state: in service     Checking clocks of glb replicas     ip:thomas.island.sodor.com 1993/04/09.17:09     ip:henry.island.sodor.com 1993/04/09.17:09     ip:percy.island.sodor.com 1993/04/09.17:10     ip:james.island.sodor.com 1993/04/09.17:09ID="14093"Run the merge_all subcommand to ensure that all Global Location Brokers are in a consistent state before the reset subcommand: drm_admin: merge_all     Merge from ip:henry.island.sodor.com done     Merge from ip:percy.island.sodor.com done     Merge from ip:james.island.sodor.com done     Merge to ip:henry.island.sodor.com done     Merge to ip:percy.island.sodor.com done     Merge to ip:james.island.sodor.com done     Merge_all successfully completedIf the merge_all does not process the Global Location Brokers to be deleted, you must run merge_all again after step IDREF="34740" TYPE="TEXT"4 . In the example above, the Global Location Brokers to be deleted were processed. Give the reset subcommand to delete the glbds:drm_admin:   reset ip:percy drm_admin: reset ip:jamesID="34740"Run the ID="ch764"purgerep subcommand to purge the Global Location Broker from the Global Location Broker lists:drm_admin: purgerep ip:percy drm_admin: purgerep ip:jamesIf the merge_all in step IDREF="14093" TYPE="TEXT"2 did not process the Global Location Brokers to be deleted, run merge_all again now.To verify that a deletion has finished, give the ps command to see if glbd is still running on the system from which it was deleted:ps -e | grep glbd   LBL="" HELPID=""ID="62100"Adjusting to Network ReconfigurationsReconfigurations of a network can result in changes to its systems' network addresses. When a system is a Global Location Broker, you may have to perform some administrative adjustments. Among the reconfigurations that can change a system's network address are:ID="ch765"Moving a system from one network to anotherCombining two networks to form a larger networkConnecting two networks to form a multi-segment networkPartitioning a network to form a multi-segment network or two separate networksChanging a network numberIf the network address of a Global Location Broker changes, glbd learns its new address automatically the next time it starts, and it propagates its change of address to all other Global Location Brokers. If only one system changes its address, no administrative work should be required. However, if more than one Global Location Broker changes its address, some Global Location Brokers may not be able to contact one another, and you have to edit their Global Location Broker lists manually, as described below.The procedure below corrects the Global Location Broker lists at two Global Location Brokers, henry and percy, that have new network numbers. A third Global Location Broker, thomas, has not changed.At all Global Location Brokers whose network addresses have changed, ensure that a glbd has been started since the address change. Stop and restart daemons where necessary (see IDREF="42084" TYPE="TITLE""Stopping Daemons" and IDREF="50200" TYPE="TITLE""Restarting Daemons" in this chapter).Invoke ID="ch766"drm_admin and set the default system to one of the changed sites:/usr/etc/drm_admin    drm_admin: set -o glb -h ip:henry     Default object: glb default host: ip:henry state: in service     Checking clocks of glb replicas     ip:henry.island.sodor.com 1993/04/06.11:00     ip:#192.26.52.9 *** clock unavailable ***     ip:thomas.island.sodor.com 1993/04/06.11:00 The Global Location Broker at henry knows its own new network address but knows only the old network address of percy and hence cannot communicate with the Global Location Broker there. Use the ID="ch767"drm_admin chrep command to replace the network address for percy, then use the lrep -na subcommand to verify the change:drm_admin: chrep -from ip:192.26.52.9 -to ip:percy drm_admin: lrep -na     ip:henry.island.sodor.com ip:#192.26.77.80     ip:percy.island.sodor.com ip:#192.26.77.3     ip:thomas.island.sodor.com ip:#192.26.77.17For each other Global Location Broker whose network address changed, set it to the default system, check its Global Location Broker list, replace obsolete network addresses in its Global Location Broker list, and confirm the change:drm_admin:   set -o glb -h ip:percy     Default object: glb default host: ip:percy state: in service     ... drm_admin: lrep -na     ip:percy.island.sodor.com ip:#192.26.77.3     ip:#192.26.52.5 ip:#192.26.77.5     ip:thomas.island.sodor.com ip:#192.26.77.17 drm_admin: chrep -from ip:192.26.52.5 -to ip:henry drm_admin: lrep -na     ip:percy.island.sodor.com ip:#192.26.77.3     ip:henry.island.sodor.com ip:#192.26.77.80     ip:thomas.island.sodor.com ip:#192.26.77.17 LBL="8"ID="80529"Error MessagesThis chapter lists error messages displayed by NetLS commands and by applications licensed with NetLS. Each section explains an error message and what to do about it. The sections are:IDREF="33615" TYPE="TITLE""Unable to Obtain Any Sockets"IDREF="80934" TYPE="TITLE""Unable to Locate Any Network License Servers"IDREF="51422" TYPE="TITLE""License Will Expire in n Days"IDREF="15719" TYPE="TITLE""Communications Failure"IDREF="92247" TYPE="TITLE""Unable to Register with Locating Broker"IDREF="33615" TYPE="TITLE""Unable to Obtain Any Sockets"IDREF="22620" TYPE="TITLE""No Entries Match"IDREF="25717" TYPE="TITLE""Cannot Create Replica"Error messages are displayed in shell windows and are sometimes written to ID="ch81"/var/adm/SYSLOG (/usr/adm/SYSLOG on IRIX Release 5.0 and earlier). Be sure to check this file if you are experiencing problems; it may contain a NetLS or networking error message that you might otherwise not see.LBL="" HELPID=""ID="59073"License or Server Not FoundThere is no standard error message when you attempt to start a licensed application and the application is unable to get a license. You might see phrases like these:ID="ch82"ID="ch83"no license found   cannot locate a license server   Assuming that you have installed at least one license for the product, possible causes when an application can't find a license are:The version of the product that the license is for doesn't match the version of the product.The system date is set earlier than the start date listed on the license information sheet. If the application uses a node-locked license, these additional causes are possible:The nodelock file /var/netls/nodelock (/usr/netls/nodelock on IRIX Release 5.0 and earlier) contains an incorrect vendor ID or license password.You have entered a license annotation when there is none or it was specified incorrectly. If the license annotation contains spaces, be sure to surround it with double quotes (").On IRIX Release 5.0.1 and later, the file /usr/netls/nodelock is not a symbolic link to /var/netls/nodelock. Verify that /usr/netls/nodelock is a non-dangling symbolic link to /var/netls/nodelock using file(1).If the application uses a concurrent license, these additional causes are possible:You may have received a concurrent license but installed it as a node-locked license. There are two or more Global Location Brokers on the network that do not "know about each other." (See IDREF="75872" TYPE="TITLE""Global Location Brokers That Don't Know About Each Other" in Chapter 9 for more information.)Required daemons are not running. glbd(1M) and llbd(1M) should be running on the Global Location Broker, and netlsd(1M) and llbd should be running on the Network License Server. The clock on the system running the applications differs from the clock on the Global Location Broker system by more than 12 hours.ID="ch84"The file ID="ch85"/var/ncs/glb_site.txt (/usr/etc/ncs/glb_site.txt on IRIX Release 5.0 and earlier) lists systems that are not Global Location Brokers.A ID="ch86"/var/ncs/glb_obj.txt (/usr/etc/ncs/glb_obj.txt on IRIX Release 5.0 and earlier) file exists, but no Global Location Brokers are using the UUID in that file (there are no location brokers in that cell).The daemons are in an inconsistent state. To fix this, try stopping all of the daemons on the network (see IDREF="42084" TYPE="TITLE""Stopping Daemons" in Chapter 7 ) and restarting them (see IDREF="30502" TYPE="TITLE""Restarting All Daemons on a Network" in Chapter 7 ).The GLB database may be corrupt. Follow the instructions in IDREF="60888" TYPE="TITLE""glbd Won't Run" in Chapter 9 .LBL="" HELPID=""ID="80934"Unable to Locate Any Network License Servers/usr/etc/ls_admin    LS_ADMIN Version 2.01 BL04 (c) Copyright 1991, Hewlett-Packard Company, All Rights Reserved ?(ls_admin) Unable to locate any Network License ServersID="ch87"ls_admin(1M) exits immediately with this message when it cannot find any operational Network License Servers. One or more Network License Servers may have been set up, but they are not running now and were successful in unregistering themselves in the GLB databases before going down. See IDREF="59073" TYPE="TITLE""License or Server Not Found" in this chapter for information about similar messages from applications. LBL="" HELPID=""ID="51422"License Will Expire in n Dayslicense will expire in n daysSome applications display expiration warning messages prior to the expiration date of a temporary license. What you should do depends upon your situation:ID="ch88"ID="ch89"If you returned the Business Reply Mail card that came with the product (attached to the Software License Registration card) but have not yet received a permanent license, the license should arrive shortly. If you mailed it more than two weeks ago, contact Silicon Graphics License Administration or your service provider (see IDREF="61423" TYPE="TITLE""Contacting Silicon Graphics License Administration" in Chapter 2 ).If you have received a permanent license but haven't installed it yet, replace the temporary license with a permanent license using the guidelines in IDREF="34595" TYPE="TITLE""Installing Replacement Licenses" in Chapter 6 .If you purchased the product and have not returned the Business Reply Mail card that came with it, return the card as explained in IDREF="90219" TYPE="TITLE""Completing the Software License Registration Card" in Chapter 2 . If you've lost the Business Reply Mail card, see IDREF="77399" TYPE="TITLE""Missing Software License Registration Card" in Chapter 2 .If you have installed a permanent license, you may be getting this message because you didn't delete the temporary license. See IDREF="46782" TYPE="TITLE""Deleting a Node-locked License" in Chapter 6 or IDREF="84369" TYPE="TITLE""Deleting a Concurrent License" in Chapter 6 .If you have not purchased the product and would like to, call the product manufacturer or distributor. For Silicon Graphics products, call SGI Express at 1-800-800-7441 in the United States and Canada, and in other countries call your local sales office.ID="ch810"ID="ch811"If you are unsure about the status of licenses for this product, see IDREF="61423" TYPE="TITLE""Contacting Silicon Graphics License Administration" in Chapter 2 for information on contacting Silicon Graphics License Administration or your service provider.LBL="" HELPID=""ID="15719"Communications Failure?(command) Error at server special.wpd.sgi.com - communications failure (network computing system/RPC runtime)This error message is generated by commands that broadcast on the network such asID="ch812"ID="ch813"   ls_admin, ls_stat(1M), drm_admin(1M), and lb_admin(1M). It occurs in a wide variety of situations. Some examples are:lb_admin is doing a lookup on a system where a Global Location Broker is not running:lb_admin: set global ip:pele lb_admin: use global lb_admin: lookup    ?(lb_admin) communications failure (network computing system/RPC runtime) No entries match.drm_admin cannot contact a Global Location Broker:drm_admin: set -o glb -h ip:pele    Default object: glb default host: ip:pele status: not communicating communications failure (network computing system/RPC runtime)ls_admin or ls_stat detect that a Network License Server went down without unregistering itself:Connected to server: pele.wpd.sgi.com ?(command) communications failure (network computing system/RPC runtime)A Network License Server can appear to go down without unregistering itself when the system crashes, the network becomes unavailable, or daemons are not running.LBL="" HELPID=""ID="92247"Unable to Register with Locating BrokerUnable to register with locating broker communications failure (network computing system/RPC runtime)This message can occur for a variety of reasons:ID="ch814"The network is unavailable.A system is down.Daemons are not able to locate other daemons; for example, glbd is unable to locate a llbd, or netlsd is unable to locate a llbd. To solve this problem, stop the daemons on the network and restart them using the instructions in IDREF="42084" TYPE="TITLE""Stopping Daemons" in Chapter 7 and IDREF="50200" TYPE="TITLE""Restarting Daemons" in Chapter 7 .A ID="ch815"ID="ch816"/var/ncs/glb_obj.txt or /var/ncs/glb_site.txt file (/usr/etc/ncs/glb_obj.txt or /usr/etc/ncs/glb_site.txt on IRIX Release 5.0 and earlier) is incorrect.LBL="" HELPID=""ID="33615"Unable to Obtain Any SocketsLLBD: Unable to obtain any socketsThis error message can occur when:ID="ch817"You weren't superuser when you tried to start llbd. Become superuser to start llbd.llbd is already running. Confirm that it is running using ps(1).LBL="" HELPID=""ID="22620"No Entries MatchNo entries match.This message is displayed by ID="ch818"ID="ch819"lb_admin. It occurs in these situations:When you give the lb_admin subcommand lookup, lb_admin reports "No entries match" if the Global Location Broker you've specified has no Network License Server entries in its database and you haven't specified arguments to lookup; for example: /usr/etc/lb_admin    lb_admin: lookup    Data from GLB replica: ip:pele.wpd.sgi.com No entries match.If you've given arguments to lookup and they don't match any entries, then the entire list of entries is displayed.When you are modifying GLB database entries using the delete or unregister subcommand, this message appears when no entries are affected; for example:/usr/etc/lb_admin    lb_admin: delete sl slsl sl ip:pele    No entries match.LBL="" HELPID=""ID="25717"Cannot Create Replicaglbd: ?(GLB) cannot create replica - object already exists (network computing system/DRM)You were trying to start a Global Location Broker with the command:ID="ch820"/usr/etc/glbd -create -from ip:hostname   &   The command failed because a GLB database (the files /var/ncs/glb.e and /var/ncs/glb.p on IRIX Release 5.0.1 and later, and /usr/etc/ncs/glb.e and /usr/etc/ncs/glb.p on IRIX Release 5.0 and earlier) already exists on this system. You have three choices:Start up glbd using the existing database with this command:/etc/init.d/nck start   Remove the existing database and give the same glbd command again. On IRIX Release 5.0.1 and later, the files are /var/ncs/glb.e and /var/ncs/glb.p. On IRIX Release 5.0 and earlier, the files are /usr/etc/ncs/glb.e and /usr/etc/ncs/glb.p. Merge the existing database with ID="ch821"hostname's database and start glbd using this sequence of commands:/usr/etc/drm_admin    drm_admin: set   -o glb -h ip:hostname    drm_admin: addrep ip:thishost    drm_admin: merge_all    drm_admin: quit    /etc/init.d/nck start   thishost is the host name of your system.LBL="9"ID="99358"TroubleshootingThis chapter contains troubleshooting procedures that you can use if you are having trouble obtaining a concurrent license. It also describes various problem situations that can occur in a NetLS environment and what to do about them. The sections in this chapter are:IDREF="91820" TYPE="TITLE""Basic Troubleshooting Procedure for Concurrent Licenses"IDREF="60888" TYPE="TITLE""glbd Won't Run"IDREF="36478" TYPE="TITLE""netlsd Won't Run"IDREF="49893" TYPE="TITLE""Problems While Installing a Concurrent License"IDREF="75872" TYPE="TITLE""Global Location Brokers That Don't Know About Each Other"IDREF="62479" TYPE="TITLE""Getting a License Is Very Slow"IDREF="88629" TYPE="TITLE""Propagation Queues Overflow"Additional sources of information about problems are:The list of known bugs in theID="ch91"ID="ch92"   NetLS Execution Only Environment Release Notes.The file ID="ch93"/var/adm/SYSLOG (/usr/adm/SYSLOG on IRIX Release 5.0 and earlier), which may contain messages that can help you understand an error condition.LBL="" HELPID=""ID="91820"Basic Troubleshooting Procedure for Concurrent LicensesIf you are having trouble obtaining a concurrent license for a licensed product, the procedure below can be used to identify the source of your problem.ID="ch94"ID="ch95"Verify that the file /var/netls/nodelock (/usr/netls/nodelock on IRIX Release 5.0 and earlier) does not contain a license for the product you want to use. If you find a node-locked license, comment it out using the procedure in IDREF="46782" TYPE="TITLE""Deleting a Node-locked License" in Chapter 6 .On your system, install netls_eoe.sw.netls_eoe if it isn't installed already to give you the commands that you need to troubleshoot your problem. Confirm that there is a Global Location Broker on the network and that it is running by using the procedure in IDREF="38612" TYPE="TITLE""Checking Global Location Brokers" in Chapter 7 .Verify that the clock is within 12 hours of the Global Location Broker clocks. Reset incorrect clocks.ID="ch96"Confirm that there is at least one Network License Server running in the network and that at least one of them has a license for the product you want to use by following the procedure in IDREF="38729" TYPE="TITLE""Checking Network License Servers" in Chapter 7 .Try stopping and restarting netlsd(1M) on the Network License Server that has the license you want to use. See IDREF="42084" TYPE="TITLE""Stopping Daemons" in Chapter 7 and IDREF="50200" TYPE="TITLE""Restarting Daemons" in Chapter 7 .Verify that all Global Location Broker clocks are within 10 minutes of each other and manually merge their databases using the procedure in IDREF="86397" TYPE="TITLE""Routine Maintenance of Global Location Brokers" in Chapter 7 .Stop and restart all Global Location Brokers and Network License Servers in the network using the procedures in IDREF="42084" TYPE="TITLE""Stopping Daemons" in Chapter 7 and IDREF="50200" TYPE="TITLE""Restarting Daemons" in Chapter 7 .LBL="" HELPID=""ID="60888"glbd Won't RunIf ID="ch97"ID="ch98"glbd(1M) won't start, it may be for these reasons:You weren't superuser when you tried to start the daemon.glbd may already be running.The llb or glb chkconfig(1M) flags are "off".You may not be starting ID="ch99"glbd properly. The first time you start glbd, you must give it the ­create option with either the ­first or ­from option. Subsequently, glbd should be started with no options.llbd may not be running. It must be running before glbd can run.An error condition occurred that was reported in /var/adm/SYSLOG (/usr/adm/SYSLOG on IRIX Release 5.0 and earlier).The GLB database may be corrupted.The next two sections describe ways to restore or replace a corrupted Global Location Broker. If there is a Global Location Broker whose database you can use to restore the corrupted database (the best way to restore a corrupted database), see ID="ch910"IDREF="70917" TYPE="TITLE""Restoring a Corrupted GLB Database Using Another Global Location Broker" in this chapter. If there is no Global Location Broker you can use, see IDREF="49653" TYPE="TITLE""Recreating a Corrupted GLB Database" in this chapter.LBL="" HELPID=""ID="70917"Restoring a Corrupted GLB Database Using Another Global Location BrokerTo restore a corrupted GLB database using another Global Location Broker, follow this procedure:ID="ch911"If possible, start llbd and glbd on the system with the corrupted database.If you were able to start the daemons, use the drm_admin(1M) command with the reset subcommand to delete the database (see IDREF="98269" TYPE="TITLE""Using drm_admin reset" in Chapter 7 ). If the database is corrupted so badly that ID="ch912"llbd and glbd cannot run, as superuser manually delete two database files. On IRIX Release 5.0.1 or later, give this command:rm /var/ncs/glb.p /var/ncs/glb.e   On IRIX Release 5.0 or earlier, give this command:rm /usr/etc/ncs/glb.p /usr/etc/ncs/glb.e   If there are several Global Location Brokers, inform them that this Global Location Broker is out of service. Start the drm_admin command:/usr/etc/drm_admin   Give these subcommands once for each good Global Location Broker to inform it that the corrupt Global Location Broker is out of service:ID="ch913"drm_admin: set -o glb -h ip:goodGLB    drm_admin: purgerep ip:corruptGLB   drm_admin issues a warning and asks for confirmation. Use IDREF="59272" TYPE="TITLE""Setting Up a Global Location Broker Manually" in Chapter 4 to create a new Global Location Broker (use the name of a good Global Location Broker for other_GLB_hostname in step IDREF="68053" TYPE="TEXT"8 ). Use the drm_admin merge_all command to ensure that all Global Location Brokers are consistent (see IDREF="86397" TYPE="TITLE""Routine Maintenance of Global Location Brokers" in Chapter 7 ).Restart netlsd on each Network License Server with these commands:/etc/init.d/netls stop    /etc/init.d/netls start LBL="" HELPID=""ID="49653"Recreating a Corrupted GLB DatabaseIf the corrupted GLB database is the only one, you have two options. The options are:Delete the corrupted database: On IRIX Release 5.0.1 or later, give this command:rm /var/ncs/glb.p /var/ncs/glb.e   On IRIX Release 5.0 or earlier, give this command:rm /usr/etc/ncs/glb.p /usr/etc/ncs/glb.e   Use IDREF="59272" TYPE="TITLE""Setting Up a Global Location Broker Manually" in Chapter 4 to re-create an empty, fresh database. Stop and restart all Network License Servers (see IDREF="42084" TYPE="TITLE""Stopping Daemons" in Chapter 7 and IDREF="50200" TYPE="TITLE""Restarting Daemons" in Chapter 7 ).Restore the database from backup:Restore the two database files   /var/ncs/glb.e and /var/ncs/glb.p (or /usr/etc/ncs/glb.e and /usr/etc/ncs/glb.p for IRIX Release 5.0 and earlier) from a backup. Because the backup version may have obsolete information, use the clean subcommand of the lb_admin(1M) command to remove obsolete entries from the GLB database. See IDREF="10104" TYPE="TITLE""Cleaning GLB Databases" in Chapter 7 for the procedure.Restart ID="ch914"ID="ch915"netlsd on each Network License Server with these commands:/etc/init.d/netls stop    /etc/init.d/netls start LBL="" HELPID=""ID="36478"netlsd Won't RunWhen ID="ch916"netlsd won't run, it is usually for one of these reasons:The llb or netls chkconfig flags are set to "off".The Global Location Broker(s) and Network License Server(s) aren't set up properly. See IDREF="38612" TYPE="TITLE""Checking Global Location Brokers" in Chapter 7 and IDREF="38729" TYPE="TITLE""Checking Network License Servers" in Chapter 7 for information on verifying that they are operating correctly.An error condition occurred that was reported in /var/adm/SYSLOG (/usr/adm/SYSLOG on IRIX Release 5.0 and earlier).The Concurrent License database is corrupted. If the netlsd daemon won't start, it may be because the Concurrent License database is corrupted. If netlsd was killed, the database might be in an inconsistent state. Follow these steps to attempt to salvage a corrupted Concurrent License database, and if that fails, to remove it:ID="ch917"Become superuser:/bin/su -    Password: Start ID="ch918"netlsd with the ­o option:/usr/etc/netlsd -o &   Use ps(1) to see if it started:ps -e | grep netlsd        3842 ttyq1 0:00 netlsdIf you get a line of output like the one shown above, netlsd started and the problem is solved. If netlsd didn't start, the next step is to remove the Concurrent License database. This is a drastic step that requires you to reinstall every license that was in the database. To delete the Concurrent License database, give these commands on a system running IRIX Release 5.0.1 or later:ID="ch919"/etc/init.d/netls stop    /etc/init.d/nck stop    rm /var/netls/*db*   On a system running IRIX Release 5.0 or earlier, give these commands:/etc/init.d/netls stop    /etc/init.d/nck stop    rm /usr/netls/*db*   To restart the daemons, see IDREF="50200" TYPE="TITLE""Restarting Daemons" in Chapter 7 A new, empty Concurrent License database is created.Reinstall the licenses that were in the database or restore them from a backup.LBL="" HELPID=""ID="49893"Problems While Installing a Concurrent LicenseIf ID="ch920"ID="ch921"ls_admin(1M) doesn't show the Network License Server you want to install a license on, or it doesn't allow you to add vendor or product information, some of the most likely causes are:The Network License Server wasn't properly set up. See IDREF="38729" TYPE="TITLE""Checking Network License Servers" in Chapter 7 .The system where you are using ls_admin can't communicate with the system that is the Network License Server. Try running ls_admin on the Network License Server system.The sysinfo number for this system may not be the same as the sysinfo number that the license was issued for. To check this, give the command:/etc/sysinfo   -s The result should be the same number that is listed for sysinfo on the license information sheet. If the sysinfo is "Any", then the license works with any system.You may have typed a password incorrectly.You may have entered the wrong ID or password. Make sure that the vendor ID, the vendor password, and the license password are all correct.The license you are entering may be a node-locked license rather than a concurrent license. Check the license type listed on the license information sheet.There is more than one license password listed on the license information sheet, and the vendor password was not correctly copied from one Network License Server to another. See IDREF="99449" TYPE="TITLE"Chapter 5, "Installing Concurrent Licenses."LBL="" HELPID=""ID="75872"Global Location Brokers That Don't Know About Each OtherIf a network has two or more systems that are Global Location Brokers and the system(s) started second and later were not set up using the ID="ch922"ID="ch923"ID="ch924"glbd   ­from option, then the Global Location Brokers may have different lists of Network License Servers. When an application tries to find a Network License Server, it may or may not find one because the Global Location Brokers may contain different lists of Network License Servers. One Network License Server may not have licenses available, but another Network License Server not on the list may. Each time you try to get a license, the application may try to get it from either one. If you bring up ls_admin several times and once in a while get a different list of Network License Servers in the Servers area, then this is probably the problem.There are three possible solutions to this problem:Add a ID="ch925"/var/ncs/glb_site.txt file (/usr/etc/ncs/glb_site.txt on IRIX Release 5.0 and earlier) onto all of the systems that will be requesting licenses. See IDREF="97379" TYPE="TITLE""Using glb_site.txt Files" in Chapter 7 and the glb_site(4) manual page for more information.Make sure that all of the Global Location Brokers know about each other. To do this, follow these steps:Identify all of the Global Location Brokers.Confirm that the chkconfig flags are set properly: Global Location Brokers should have glb and llb "on", and Network License Servers should have netls and llb "on". Stop the daemons on each Global Location Broker and each Network License Server by giving these commands:/bin/su -    Password: /etc/init.d/netls stop    /etc/init.d/nck stop   Follow the procedure in IDREF="30502" TYPE="TITLE""Restarting All Daemons on a Network" in Chapter 7 to restart all of the daemons.Form a license group to isolate your NetLS environment.Using a license group isolates users from Global Location Brokers that are not part of their NetLS environment. See ID="ch926"IDREF="32117" TYPE="TITLE""Creating a New License Group" in Chapter 7 for instructions on forming a license group.LBL="" HELPID=""ID="62479"Getting a License Is Very SlowIf getting a license is very slow, the GLB databases may contain obsolete entries. To remove the obsolete entries, use the procedure in ID="ch927"IDREF="10104" TYPE="TITLE""Cleaning GLB Databases" in Chapter 7 .LBL="" HELPID=""ID="88629"Propagation Queues OverflowWhen a Global Location Broker is stopped or unavailable for a long time, the propagation queues at other Global Location Brokers accumulate updates for propagation to the unreachable system. Eventually, this accumulation can overflow the propagation queues. ID="ch928"ID="ch929"If you are unable to revive or reconnect the unreachable system, invoke ID="ch930"drm_admin and use the purgerep subcommand to forcibly delete the Global Location Broker. If the Global Location Broker later becomes reachable, use the drm_admin   reset command to stop and remove the database, then re-create the Global Location Broker using the procedure in IDREF="59272" TYPE="TITLE""Setting Up a Global Location Broker Manually" in Chapter 4 .LBL="A"NetLS FilesThis appendix lists and briefly explains files associated with NetLS. ID="appa1"ID="appa2"ID="appa3"IDREF="19810" TYPE="TABLE"Table A-1 lists these NetLS files:Files included in the software subsystems ID="appa4"ID="appa5"netls_eoe.sw.netls_eoe (all IRIX Releases) and nck.sw.nck (IRIX Release 5.0 and earlier only)Files that are created automatically by NetLS commandsFiles that users might createThe first column of ID="appa6"IDREF="19810" TYPE="TABLE"Table A-1 lists file names. In cases where a file had one name in IRIX Release 5.0 and earlier and has a different name in IRIX Release 5.0.1 and later, the 5.0.1 name is listed first and the 5.0 name is shown in parentheses. The third column of IDREF="19810" TYPE="TABLE"Table A-1 lists a "file type" that explains the source of each file. The file types are:1Included in netls_eoe.sw.netls_eoe2Included in netls_eoe.sw.netls_eoe in IRIX Release 5.0.1 and later; included in nck.sw.nck in IRIX Release 5.0 and earlier 3ID="appa7"inst(1M) configuration file4Created by netlsd(1M)5Created by glbd(1M)6Created by llbd(1M)7Created by users8Created by ls_nodelock(1M) in IRIX Release 5.0.1 and later; created by users in IRIX Release 5.0 and earlierCOLUMNS="3"LBL="A-1"Table A-1 ID="19810"NetLS FilesLEFT="0" WIDTH="151"FileLEFT="160" WIDTH="156"FunctionLEFT="325" WIDTH="356"File TypeLEFT="0" WIDTH="151"/etc/config/glb   LEFT="160" WIDTH="156"Specifies whether glbd is to be started automatically during system initializationLEFT="325" WIDTH="356"2, 3LEFT="0" WIDTH="151"/etc/config/glbd.options   LEFT="160" WIDTH="156"Site-specific options for glbdLEFT="325" WIDTH="356"7LEFT="0" WIDTH="151"/etc/config/llb   LEFT="160" WIDTH="156"Specifies whether llbd is to be started automatically during system initializationLEFT="325" WIDTH="356"2, 3LEFT="0" WIDTH="151"/etc/config/llbd.options   LEFT="160" WIDTH="156"Site-specific options for llbdLEFT="325" WIDTH="356"7LEFT="0" WIDTH="151"/etc/config/netls   LEFT="160" WIDTH="156"Specifies whether netlsd is to be started automatically during system initializationLEFT="325" WIDTH="356"1, 3LEFT="0" WIDTH="151"/etc/config/netlsd.options   LEFT="160" WIDTH="156"Site-specific options for netlsd; the default is "­no c"LEFT="325" WIDTH="356"1, 3LEFT="0" WIDTH="151"/etc/init.d/nck   LEFT="160" WIDTH="156"Used to start and stop glbd and llbdLEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/etc/init.d/netls   LEFT="160" WIDTH="156"Used to start and stop netlsdLEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/etc/rc0.d/K30netls   LEFT="160" WIDTH="156"Network License Server shutdown fileLEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/etc/rc0.d/K35nck   LEFT="160" WIDTH="156"Global Location Broker shutdown fileLEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/etc/rc2.d/S40nck   LEFT="160" WIDTH="156"Global Location Broker startup fileLEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/etc/rc2.d/S45netls   LEFT="160" WIDTH="156"Network License Server startup fileLEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/tmp/llbdbase.dat   LEFT="160" WIDTH="156"llbd database LEFT="325" WIDTH="356"6LEFT="0" WIDTH="151"/usr/etc/cls_admin   LEFT="160" WIDTH="156"Displays and edits the Concurrent License database (used instead of ID="appa8"ls_admin when eoe2.sw.X11 and motif_eoe.sw.eoe aren't installed)LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/cls_stat   LEFT="160" WIDTH="156"Displays the status of concurrent licenses (used instead of ID="appa9"ls_stat when eoe2.sw.X11 and motif_eoe.sw.eoe aren't installed)LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/drm_admin   LEFT="160" WIDTH="156"Data replication management administration commandID="appa10"LEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/usr/etc/glbd   LEFT="160" WIDTH="156"Global Location Broker daemonID="appa11"LEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/usr/etc/lb_admin   LEFT="160" WIDTH="156"Local Location Broker administration commandID="appa12"LEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/usr/etc/llbd   LEFT="160" WIDTH="156"Local Location Broker daemonID="appa13"LEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/usr/etc/ls_admin   LEFT="160" WIDTH="156"Displays and edits the Concurrent License database ID="appa14"LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/ls_nodelock   LEFT="160" WIDTH="156"Installs a node-locked license (IRIX Release 5.0.1 and later only)ID="appa15"LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/ls_rpt   LEFT="160" WIDTH="156"Reports on Network License Server eventsID="appa16"LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/ls_stat   LEFT="160" WIDTH="156"Displays the status of concurrent licensesID="appa17"LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/ls_targetid   LEFT="160" WIDTH="156"   Displays the system target numberID="appa18"LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/ls_tv   LEFT="160" WIDTH="156"Verifies that Network License Servers are workingID="appa19"LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/netlsd   LEFT="160" WIDTH="156"Network License Server daemonID="appa20"LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/etc/stcode   LEFT="160" WIDTH="156"Translates a hexadecimal status code returned by some NetLS commands to a status stringID="appa21"LEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/usr/etc/uuid_gen   LEFT="160" WIDTH="156"Generates a unique identifier to use in forming cells or in generating .idl filesID="appa22"LEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/usr/lib/stcode.db   LEFT="160" WIDTH="156"Database of error code to string mappingsLEFT="325" WIDTH="356"2LEFT="0" WIDTH="151"/usr/lib/X11/app-defaults/LS_NodeLock   LEFT="160" WIDTH="156"X resources file for ls_nodelock (IRIX Release 5.0.1 and later only)LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/lib/X11/app-defaults/XLs_Admin   LEFT="160" WIDTH="156"X resources file for ls_adminLEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/lib/X11/app-defaults/XLs_Stat   LEFT="160" WIDTH="156"X resources file for ls_statLEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/netls/help/lsadmin.hlp   LEFT="160" WIDTH="156"Online help for ls_admin   LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/netls/help/lsnodelock.hlp   LEFT="160" WIDTH="156"Online help for ls_nodelock   LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/netls/help/lsstat.hlp   LEFT="160" WIDTH="156"Online help for ls_stat   LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/netls/log.h   LEFT="160" WIDTH="156"C language header file that describes the format of /var/netls/log_file (/usr/netls/log_file on IRIX Release 5.0 and earlier)LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/usr/netls/log_imp.idl   LEFT="160" WIDTH="156"Interface definition language file containing typedefs for /var/netls/log_file   (/usr/netls/log_file on IRIX Release 5.0 and earlier)LEFT="325" WIDTH="356"1LEFT="0" WIDTH="151"/var/ncs/glb_log   (/usr/etc/ncs/glb_log)LEFT="160" WIDTH="156"Global Location Broker log file (ASCII)ID="appa23"LEFT="325" WIDTH="356"5LEFT="0" WIDTH="151"/var/ncs/glb_log.bak (/usr/etc/ncs/glb_log.bak)LEFT="160" WIDTH="156"Global Location Broker log file backup copyLEFT="325" WIDTH="356"5LEFT="0" WIDTH="151"/var/ncs/glb_obj.txt (/usr/etc/ncs/glb_obj.txt)LEFT="160" WIDTH="156"Used when several disjoint GLB databases are requiredID="appa24"LEFT="325" WIDTH="356"7LEFT="0" WIDTH="151"/var/ncs/glb_site.txt (/usr/etc/ncs/glb_site.txt)LEFT="160" WIDTH="156"List of internet addresses for possible Global Location Broker systems; applications use this list rather than broadcasting to find a Global Location BrokerID="appa25"LEFT="325" WIDTH="356"7LEFT="0" WIDTH="151"/var/ncs/glb.e (/usr/etc/ncs/glb.e)LEFT="160" WIDTH="156"GLB database fileID="appa26"LEFT="325" WIDTH="356"5LEFT="0" WIDTH="151"/var/ncs/glb.p (/usr/etc/ncs/glb.p)LEFT="160" WIDTH="156"Global Location Broker propagation queueID="appa27"LEFT="325" WIDTH="356"5LEFT="0" WIDTH="151"/var/ncs/uuidname.txt (/usr/etc/ncs/uuidname.txt)LEFT="160" WIDTH="156"Maps UUIDs to namesID="appa28"LEFT="325" WIDTH="356"2, 3LEFT="0" WIDTH="151"/var/netls/cur_db (/usr/netls/cur_db)LEFT="160" WIDTH="156"Concurrent License database fileID="appa29"LEFT="325" WIDTH="356"4LEFT="0" WIDTH="151"/var/netls/cur_dbe (/usr/netls/cur_dbe)LEFT="160" WIDTH="156"Concurrent License database fileID="appa30"LEFT="325" WIDTH="356"4LEFT="0" WIDTH="151"/var/netls/lic_db (/usr/netls/lic_db)LEFT="160" WIDTH="156"Concurrent License database fileID="appa31"LEFT="325" WIDTH="356"4LEFT="0" WIDTH="151"/var/netls/lic_db.bak (/usr/netls/lic_db.bak)LEFT="160" WIDTH="156"Backup file for /var/netls/lic_db that is used if /var/netls/lic_db is missing (/usr/netls/lic_db on IRIX Release 5.0 and earlier)LEFT="325" WIDTH="356"4LEFT="0" WIDTH="151"/var/netls/log_file (/usr/netls/log_file)LEFT="160" WIDTH="156"Network License Server log file (binary)ID="appa32"LEFT="325" WIDTH="356"4LEFT="0" WIDTH="151"/var/netls/nodelock (/usr/netls/nodelock)LEFT="160" WIDTH="156"Node-locked license fileLEFT="325" WIDTH="356"8LEFT="0" WIDTH="151"/var/netls/user_file (/usr/netls/user_file)LEFT="160" WIDTH="156"Per-user permission information for licensed productsLEFT="325" WIDTH="356"7ID="appa33"ID="appa34"ID="appa35"GlossaryannotationSee license annotation.broadcastTo send a remote procedure call request to all systems in a network.concurrent licenseA concurrent license allows the use of an application by a maximum number of users simultaneously. These users can be on any system on the network where the concurrent license is installed. Concurrent licenses are installed on Network License Servers using the command ls_admin(1M).Concurrent License databaseThe Concurrent License database stores all of the concurrent licenses that have been installed on a system. Concurrent License databases have the pathname /var/netls/lic_db (/usr/netls/lic_db on IRIX Release 5.0 and earlier) on Network License Servers.GLB databaseThe GLB database stores the locations (that is, the network addresses and port numbers) where Network License Servers are set up and the product vendors for the licenses on each Network License Server.glbd daemonThe glbd(1M) daemon is one component of a Global Location Broker. glbd helps applications locate Network License Servers on a network. glbd maintains a list of Global Location Brokers and a GLB database.Global Location BrokerGlobal Location Brokers are systems that run the daemons llbd(1M) and glbd. The daemons maintain a database containing the locations of Network License Servers and the product vendors for the licenses on each Network License Server.licenseA collection of information including at least a license password and a vendor password that authorizes the use of a licensed software product for a particular period of time by a particular number of users.license annotationA string that modifies the use of a license in a manner defined by the vendor of the software product.license groupA collection of systems including one or more Network License Servers and one or more Global Location Brokers. Licensed applications running on these systems use the Global Location Broker(s) and Network License Server(s) in the collection. license information sheetThe license information sheet is a label affixed to the software product packaging, a sheet of paper that you received with the product or after receiving the product, or other source of license information such as a FAX or electronic mail message. The license information sheet contains information such as the vendor name, vendor ID, vendor password, license type, product name, product version, license password, license annotation, start date of the license, duration of the license, expiration date, number of nodes (systems) that can use the product concurrently, the target type (operating system) of the licensed system, the target number of the licensed system, the sysinfo number of the licensed system, and the serial number of the licensed system.license passwordA string encoded with license information for a software product. It is sometimes known as a product password.license typeA NetLS license is one of two types: node-locked or concurrent.licensed productA software product that has been licensed under the Network License System.llbd daemonThe local location broker daemon llbd(1M) helps applications find Network License Servers.log fileThe file that records messages and errors from the Network License Server, and sometimes from licensed products as well. The full pathname of this file is /var/netls/log_file (/usr/netls/log_file on IRIX Release 5.0 and earlier).ls_admin commandThe command used to modify a Concurrent License database, including adding concurrent licenses.ls_rpt commandThe command that reports on the history of Network License Server events.ls_stat commandThe command that reports on the status of licenses.ls_tv commandThe Network License Server daemon test and verification command.multi-segment networkTwo or more connected network segments. The connection is done by routers (gateways). For example, a system with two Ethernet interfaces connected to two different networks creates a multi-segment network.NetLSSee Network License System.NetLS Test ProductThe licensed product used by the ls_tv(1M) command to verify that Network License Servers are working properly. It is included with NetLS and installed automatically.netlsd daemonThe Network License daemon netlsd(1M) runs on Network License Servers and helps keep track of and provides access to the information in the Concurrent License database.Network License ServerA Network License Server is a system running netlsd and llbd that can have concurrent licenses installed on it. Network License System (NetLS)The Network License System is a software licensing system that supports node-locked and concurrent licenses. Various daemons and databases ensure that only authorized users or a maximum number of users are able to run applications that have calls to NetLS library routines in them.nodelock fileA text file, /var/netls/nodelock (/usr/netls/nodelock on IRIX Release 5.0 and earlier), that contains licenses for node-locked applications running on this system. node-locked licenseA type of license locked to a specific system so that the product may only be used at that system. The Network License Server does not administer node-locked licenses and no daemons are required. License administration is done within the application and licenses are installed in /usr/netls/nodelock. (In IRIX Release 5.0.1 and later, /usr/netls/nodelock is a symbolic link to /var/netls/nodelock.)passwordA string encoded with information about a software vendor (vendor password) or about a software product (license password).product nameThe name of a software product.product versionA version string for a product that is used for licensing purposes. This version string may or may not match the product's release number.propagation queueThe queue that a Global Location Broker maintains for updates that it propagates to other servers. The file /var/ncs/glb.p (/usr/etc/ncs/glb.p on IRIX Release 5.0 and earlier) contains the propagation queue.replacement licenseA node-locked or concurrent license that is supplied to a customer as a replacement for a previously provided license. Replacement licenses are issued for the reasons listed in IDREF="34595" TYPE="TITLE""Installing Replacement Licenses" in Chapter 6 .replicaGlobal Location Brokers that maintain identical databases are called replicas.serial numberA unique number that can be found on the back of a system. It is usually printed above the power cord or on a bar-code label that is above and to the left of the SCSI bus port.sysinfo numberA unique number for a system that is reported by the command sysinfo(1) with the ­s option and listed on license information sheets.systemA workstation or server.system identification numberA unique number for a system. Three types of unique numbers are used in administering NetLS licenses: the target number, the sysinfo number, and the serial number.target numberA unique number for a system that is reported by the command ls_targetid(1M) and listed on license information sheets.target typeThe operating system that must be running in order to use a particular license. For Silicon Graphics systems, it is always "Irix".user fileA text file that specifies the users who may (or may not) use licensed software products. The full pathname of this file is /var/netls/user_file (/usr/netls/user_file on IRIX Release 5.0 and earlier).UUIDA unique identifier that is generated and used by NetLS daemons and commands.vendor IDThe identifier of a vendor of licensed products. By means of vendor IDs, Network License Servers can distinguish among any number of vendors established in a network. vendor nameThe name of the manufacturer of a software product.vendor passwordA string encoded with information about a vendor that, together with a vendor ID, establishes the vendor of a licensed product in a Concurrent License database.annotation. See license annotationIDREF="ch112"What Is a License?broadcast to find Global Location BrokerIDREF="ch755"Using glb_site.txt FilesIDREF="ch175"Network License System OperationIDREF="ch181"Guidelines for Global Location Brokers and Network License Serversbug listIDREF="ch92"TroubleshootingcellIDREF="ch164"License Groups for Concurrent LicensingSee also license groupIDREF="ch165"License Groups for Concurrent Licensingchkconfig flagsrequiredIDREF="ch197"Required Software, Configuration Flags, and DaemonssettingIDREF="ch419"Setting Up a Global Location Broker ManuallyIDREF="ch427"Setting Up a Network License Server ManuallyIDREF="ch412"Setting Up a Network License Server and Global Location Broker with ­sgiautoclock synchronizationIDREF="ch84"License or Server Not FoundIDREF="ch96"Basic Troubleshooting Procedure for Concurrent LicensesIDREF="ch76"Routine Maintenance of Global Location Brokerscls_admin commandmanual pageIDREF="intro13"For More Information subsystemIDREF="appa8"NetLS Filescls_stat commandmanual pageIDREF="intro14"For More Information subsystemIDREF="appa9"NetLS Filesconcurrent access license. See concurrent licensesIDREF="intro36"Product SupportConcurrent License databasebacking upIDREF="ch72"Backing Up DatabasescontentsIDREF="ch161"Network License ServersfilesIDREF="ch162"Network License ServersIDREF="appa29"NetLS FilesIDREF="appa30"NetLS FilesIDREF="appa31"NetLS Filesremoving filesIDREF="ch757"Deleting a Network License ServerIDREF="ch919"netlsd Won't Runsalvaging corruptedIDREF="ch917"netlsd Won't Runconcurrent licensesapplication startup eventsIDREF="ch172"Network License System OperationinstallingIDREF="ch521"Non-graphical Concurrent License Installationon standalone systemsIDREF="ch49"Setting Up a Network License Server and Global Location Broker with ­sgiautoIDREF="ch416"Setting Up a Global Location Broker ManuallySee also licensesIDREF="intro52"Product SupportCPU-lock licenses. See node-locked licensesIDREF="intro38"Product Supportdaemonsglbd. See glbd daemonIDREF="intro46"Product Supportllbd. See llbd daemonIDREF="intro47"Product Supportnetlsd. See netlsd daemonIDREF="intro48"Product Supportrestarting allIDREF="ch741"Restarting All Daemons on a Networkstartup orderIDREF="ch1108"Required Software, Configuration Flags, and Daemonsstopping allIDREF="ch736"Stopping Daemonsdiskless systemsIDREF="ch186"Guidelines for Global Location Brokers and Network License Serversdrm_admin commandchecking for clock skewIDREF="ch77"Routine Maintenance of Global Location Brokerschrep subcommandIDREF="ch766"Adjusting to Network Reconfigurationsgetting names of Global Location BrokersIDREF="ch719"Checking Global Location Brokerslrep subcommandIDREF="ch767"Adjusting to Network Reconfigurationsmanual pageIDREF="intro15"For More Information merge_all subcommandIDREF="ch710"Routine Maintenance of Global Location Brokersmerging databasesIDREF="ch821"Cannot Create Replicapurgerep subcommandIDREF="ch764"Using drm_admin resetIDREF="ch930"Propagation Queues OverflowIDREF="ch913"Restoring a Corrupted GLB Database Using Another Global Location BrokersubsystemIDREF="appa10"NetLS Filesverifying Global Location Brokers are runningIDREF="ch720"Checking Global Location BrokersdurationdefinedIDREF="ch114"What Is a License?of licensesIDREF="ch136"License Durationserror messagescannot create replicaIDREF="ch820"Cannot Create Replicaclock skew warningIDREF="ch78"Routine Maintenance of Global Location Brokersclock skewedIDREF="ch79"Routine Maintenance of Global Location Brokersclock unavailableIDREF="ch722"Checking Global Location Brokerscommunications failureIDREF="ch721"Checking Global Location BrokersIDREF="ch718"Checking Global Location BrokersIDREF="ch812"Communications FailureIDREF="ch726"Checking Network License Servers Using ls_adminlicense or server not foundIDREF="ch83"License or Server Not Foundlicense will expire in n daysIDREF="ch88"License Will Expire in n Daysno entries matchIDREF="ch813"Communications FailureIDREF="ch717"Checking Global Location BrokersIDREF="ch713"Verifying That llbd Is RunningIDREF="ch819"No Entries Matchunable to locate any network license serversIDREF="ch87"Unable to Locate Any Network License Serversunable to obtain any socketsIDREF="ch817"Unable to Obtain Any Socketsunable to register with locating brokerIDREF="ch814"Unable to Register with Locating Brokerexpirationdate, checkingIDREF="ch35"Installing Node-locked LicensesIDREF="ch54"Installing Concurrent Licensesdate, definedIDREF="ch115"What Is a License?set when license createdIDREF="ch135"License Durationswarning notifierIDREF="ch140"Temporary LicensesIDREF="ch89"License Will Expire in n Daysfixed licenses. See node-locked licensesIDREF="intro37"Product Supportfloating licenses. See concurrent licensesIDREF="intro35"Product SupportGLB databasecontentsIDREF="ch151"Global Location BrokersfilesIDREF="ch152"Global Location BrokersIDREF="appa26"NetLS Filesobsolete entriesIDREF="ch752"Cleaning GLB Databasesremoving filesIDREF="ch912"Restoring a Corrupted GLB Database Using Another Global Location BrokerIDREF="ch742"Restarting All Daemons on a Networkrestoring corruptedIDREF="ch915"Recreating a Corrupted GLB DatabaseIDREF="ch910"glbd Won't Runglb_obj.txt fileIDREF="ch747"System Is a Network License ServerIDREF="appa24"NetLS FilesIDREF="ch815"Unable to Register with Locating BrokerIDREF="ch43"Creating a License GroupIDREF="ch167"License Groups for Concurrent LicensingIDREF="intro17"For More Information IDREF="ch86"License or Server Not FoundIDREF="ch745"Creating a New License Groupglb_site.txt fileIDREF="ch85"License or Server Not FoundIDREF="ch418"Setting Up a Global Location Broker ManuallyIDREF="ch411"Setting Up a Network License Server and Global Location Broker with ­sgiautoIDREF="appa25"NetLS FilesIDREF="ch816"Unable to Register with Locating BrokerIDREF="intro18"For More Information IDREF="ch925"Global Location Brokers That Don't Know About Each Otherglbd daemoncauses of not startingIDREF="ch98"glbd Won't Runmanual pageIDREF="intro16"For More Information on Global Location BrokerIDREF="ch149"Global Location Brokersstarting automaticallyIDREF="ch415"Setting Up a Global Location Broker ManuallyIDREF="ch45"Setting Up a Network License Server and Global Location Broker with ­sgiautostarting manuallyIDREF="ch99"glbd Won't Runstarting so they know about each otherIDREF="ch422"Setting Up a Global Location Broker Manuallystartup orderIDREF="ch1105"Required Software, Configuration Flags, and DaemonssubsystemIDREF="appa11"NetLS FilesGlobal Location BrokerdaemonsIDREF="ch148"Global Location Brokersdatabase. See GLB databaseIDREF="intro42"Product Supportdeleted stateIDREF="ch760"Using drm_admin delrepdon't know about each otherIDREF="ch923"Global Location Brokers That Don't Know About Each Otherexamples of choosingIDREF="ch193"Multi-segment Network ExampleIDREF="ch189"Simple Network Examplehow many to useIDREF="ch155"Global Location BrokersIDREF="ch183"Guidelines for Global Location Brokers and Network License Serverspropagation queueIDREF="ch761"Using drm_admin delrepreplicasIDREF="ch421"Setting Up a Global Location Broker ManuallyIDREF="ch153"Global Location Brokersrequired chkconfig flagsIDREF="ch1100"Required Software, Configuration Flags, and Daemonsrequired daemonsIDREF="ch1101"Required Software, Configuration Flags, and Daemonsrequired softwareIDREF="ch199"Required Software, Configuration Flags, and Daemonsrole at application startupIDREF="ch173"Network License System Operationverifying operationIDREF="ch715"Checking Global Location Brokersinst configuration filesIDREF="appa7"NetLS Filesinstallingconcurrent licenseIDREF="ch522"Non-graphical Concurrent License InstallationIDREF="ch52"Installing Concurrent LicensesNetLS subsystemsIDREF="appa6"NetLS Filesnode-locked licenseIDREF="ch321"Non-graphical Installation of a Node-locked Licensereplacement licensesIDREF="ch632"Installing Replacement LicensesIRIX Releasecovered in this guideIDREF="intro4"NetLS Versions Documentedon your systemIDREF="intro3"NetLS Versions Documentedlb_admin commandclean subcommandIDREF="ch753"Cleaning GLB Databasesmanual pageIDREF="intro19"For More Information no entries matchIDREF="ch712"Verifying That llbd Is RunningIDREF="ch818"No Entries MatchsubsystemIDREF="appa12"NetLS Filesuse subcommandIDREF="ch716"Checking Global Location BrokersIDREF="ch728"Checking Network License Servers Using lb_adminLicense Administration, contactingIDREF="ch220"Contacting Silicon Graphics License Administrationlicense annotationdefinedIDREF="ch111"What Is a License?usingIDREF="ch516"Non-graphical Concurrent License InstallationIDREF="ch319"Non-graphical Installation of a Node-locked LicenseIDREF="ch313"Graphical Installation of a Node-locked LicenseIDREF="ch512"Graphical Concurrent License Installationlicense groupadding a systemIDREF="ch748"System Is a Network License Serverto isolate NetLS environmentIDREF="ch926"Global Location Brokers That Don't Know About Each Otherlicense information sheetcontents definedIDREF="ch12"What Is a License?how to obtainIDREF="ch13"What Is a License?IDREF="ch29"Completing the Software License Registration Cardlicense passworddefinedIDREF="ch110"What Is a License?IDREF="ch318"Non-graphical Installation of a Node-locked LicenseIDREF="ch511"Graphical Concurrent License InstallationobtainingIDREF="ch26"Completing the Software License Registration CardusingIDREF="ch517"Non-graphical Concurrent License InstallationIDREF="ch312"Graphical Installation of a Node-locked LicenseLicense Registration card. See Software License Registration cardIDREF="intro53"Product Supportlicense typedefinedIDREF="ch126"License Typeson license information sheetIDREF="ch17"What Is a License?licensesconcurrent. See concurrent licensesIDREF="intro39"Product Supportcreating reportsIDREF="ch623"Generating Reports on License ActivitydeletingIDREF="ch610"Deleting a Concurrent LicenseexpirationIDREF="ch141"Temporary Licensesidentifying in nodelock fileIDREF="ch625"Identifying Licenses in a Nodelock Filemonitoring usageIDREF="ch621"Monitoring License Usagenode-locked. See node-locked licensesIDREF="intro50"Product Supportpermanent. See permanent licensesIDREF="intro41"Product SupportreplacementIDREF="ch23"Flowchart of the Licensing ProcessIDREF="ch629"Installing Replacement LicensessiteIDREF="ch133"Concurrent Licensestemporary. See temporary licensesIDREF="intro40"Product Supportlicensing processobtaining a licenseIDREF="ch223"Contacting Silicon Graphics License Administrationllbd daemonmanual pageIDREF="intro20"For More Information on Global Location BrokerIDREF="ch150"Global Location BrokersIDREF="ch159"Network License ServersstartingIDREF="ch413"Setting Up a Network License Server and Global Location Broker with ­sgiautoIDREF="ch428"Setting Up a Network License Server ManuallyIDREF="ch738"Restarting Daemons for a Global Location BrokerIDREF="ch420"Setting Up a Global Location Broker Manuallystartup orderIDREF="ch1106"Required Software, Configuration Flags, and DaemonsstoppingIDREF="ch734"Stopping DaemonssubsystemIDREF="appa13"NetLS Fileslog fileGlobal Location BrokerIDREF="appa23"NetLS FilesNetwork License ServerIDREF="appa32"NetLS FilesIDREF="ch750"Reducing the Size of Network License Server Logsls_admin commandchecking format of user fileIDREF="ch618"Writing and Integrating User Filesdeleting concurrent licensesIDREF="ch67"Deleting a Concurrent LicenseIDREF="ch69"Deleting a Concurrent Licenseinstalling concurrent licensesIDREF="ch520"Non-graphical Concurrent License Installationmanual pageIDREF="intro21"For More Information seeing different lists of Network License ServersIDREF="ch924"Global Location Brokers That Don't Know About Each OthersubsystemIDREF="appa14"NetLS Filestroubleshooting problems while usingIDREF="ch921"Problems While Installing a Concurrent Licensels_nodelock commandmanual pageIDREF="intro22"For More Information subsystemIDREF="appa15"NetLS FilesusingIDREF="ch314"Graphical Installation of a Node-locked Licensels_rpt commandmanual pageIDREF="intro24"For More Information subsystemIDREF="appa16"NetLS Filesls_stat commandmanual pageIDREF="intro23"For More Information subsystemIDREF="appa17"NetLS Filesls_targetid commandmanual pageIDREF="intro25"For More Information subsystemIDREF="appa18"NetLS FilesusingIDREF="ch119"What Is a License?ls_tv commandmanual pageIDREF="intro26"For More Information subsystemIDREF="appa19"NetLS Filesmanual pages for NetLSIDREF="intro12"For More Information multi-segment networkand Global Location BrokersIDREF="ch182"Guidelines for Global Location Brokers and Network License ServersIDREF="ch154"Global Location BrokersdefinedIDREF="ch157"Global Location BrokersexampleIDREF="ch191"Multi-segment Network ExampleIDREF="ch194"Multi-segment Network Examplestarting Global Location Broker replicasIDREF="ch423"Setting Up a Global Location Broker Manuallynck.sw.nck subsystemIDREF="appa5"NetLS FilesNetLSfiles createdIDREF="appa34"NetLS FilesIDREF="appa2"NetLS Filesfiles installedIDREF="appa33"NetLS Filesinst configuration filesIDREF="appa35"NetLS FilesIDREF="appa3"NetLS Filesmanual pagesIDREF="intro11"For More Information not covered in this guideIDREF="intro7"How to Use This GuideProduct SupportIDREF="intro32"Product Supportnetls_eoe.sw.netls_eoe subsystemIDREF="appa4"NetLS Filesnetlsd daemon­o optionIDREF="ch918"netlsd Won't Runmanual pageIDREF="intro27"For More Information on Network License ServerIDREF="ch160"Network License Serversstarting automaticallyIDREF="ch425"Setting Up a Network License Server ManuallyIDREF="ch47"Setting Up a Network License Server and Global Location Broker with ­sgiautostarting manuallyIDREF="ch46"Setting Up a Network License Server and Global Location Broker with ­sgiautostartup orderIDREF="ch1107"Required Software, Configuration Flags, and DaemonsstoppingIDREF="ch735"Stopping DaemonssubsystemIDREF="appa20"NetLS Filesnetworkcommunication via TCP/IPIDREF="ch179"Guidelines for Global Location Brokers and Network License Serversmulti-segment network definedIDREF="ch156"Global Location Brokersmulti-segment network exampleIDREF="ch192"Multi-segment Network Examplesimple network exampleIDREF="ch188"Simple Network ExampleNetwork License Serverdatabase. See Concurrent License databaseIDREF="intro43"Product Supportguidelines for choosingIDREF="ch177"Guidelines for Global Location Brokers and Network License Servershow many to useIDREF="ch184"Guidelines for Global Location Brokers and Network License ServerslocatingIDREF="ch731"Checking Network License Servers Using ls_statmust be a particular systemIDREF="ch178"Guidelines for Global Location Brokers and Network License Serversrequired chkconfig flagsIDREF="ch1103"Required Software, Configuration Flags, and Daemonsrequired daemonsIDREF="ch1104"Required Software, Configuration Flags, and Daemonsrequired softwareIDREF="ch1102"Required Software, Configuration Flags, and Daemonsrole at application startupIDREF="ch174"Network License System Operationverifying operationIDREF="ch732"Checking Network License Servers Using ls_statIDREF="ch724"Checking Network License Serversnode-locked licensesapplication startup eventsIDREF="ch171"Network License System OperationdeletingIDREF="ch64"Deleting a Node-locked LicenseinstallingIDREF="ch32"Installing Node-locked LicensesIDREF="ch322"Non-graphical Installation of a Node-locked LicenseSee also licensesIDREF="intro51"Product Supportnodelock file. See /var/netls/nodelock fileIDREF="intro44"Product Supportnumber of nodesand concurrent licensesIDREF="ch130"Concurrent LicensesdefinedIDREF="ch116"What Is a License?permanent licensesexpirationIDREF="ch144"Permanent Licensesreplacing temporary licenseIDREF="ch630"Installing Replacement Licensesphone numbersLicense AdministrationIDREF="ch221"Contacting Silicon Graphics License AdministrationLicense Administration FAXIDREF="ch222"Contacting Silicon Graphics License AdministrationSGI ExpressIDREF="ch811"License Will Expire in n DaysTechnical Assistance CenterIDREF="intro34"Product Supportprerequisitesfor installing concurrent licensesIDREF="ch131"Concurrent LicensesIDREF="ch53"Installing Concurrent Licensesfor installing node-locked licensesIDREF="ch34"Installing Node-locked Licensesfor reading this guideIDREF="intro6"Audienceproblemscorrupted GLB databaseIDREF="ch914"Recreating a Corrupted GLB Databaseproduct namedefinedIDREF="ch18"What Is a License?for Software License Registration cardIDREF="ch212"Missing Software License Registration Cardin user fileIDREF="ch613"A Sample User FileusingIDREF="ch310"Graphical Installation of a Node-locked LicenseIDREF="ch59"Graphical Concurrent License InstallationIDREF="ch518"Non-graphical Concurrent License Installationproduct versiondefinedIDREF="ch19"What Is a License?usingIDREF="ch510"Graphical Concurrent License InstallationIDREF="ch311"Graphical Installation of a Node-locked LicenseIDREF="ch519"Non-graphical Concurrent License Installationpropagation queueIDREF="ch762"Using drm_admin delrepIDREF="ch929"Propagation Queues OverflowIDREF="appa27"NetLS Filesprovisional licenseIDREF="ch139"Temporary LicensesRelease Notesabout licensed productsIDREF="intro10"For More Information IDREF="ch631"Installing Replacement Licenseschecking to see if new license is requiredIDREF="ch145"Permanent Licenseschecking to see if product includes node-locked license installation commandIDREF="ch33"Installing Node-locked Licenseslist of known bugsIDREF="ch91"Troubleshootinglist of licensed applicationsIDREF="ch62"Verifying That a License Was Installed Properlyreplacement licensesIDREF="ch22"Flowchart of the Licensing Processserial numberdefinedIDREF="ch124"What Is a License?findingIDREF="ch214"Missing Software License Registration CardSGI Express phone numberIDREF="ch810"License Will Expire in n DaysSilicon Graphics License AdministrationIDREF="ch219"Contacting Silicon Graphics License Administrationsite licenseIDREF="ch132"Concurrent LicensesSoftware License Registration cardfilling outIDREF="ch27"Completing the Software License Registration Cardinformation requiredIDREF="ch211"Missing Software License Registration CardreplacementIDREF="ch217"Missing Software License Registration CardreturningIDREF="ch28"Completing the Software License Registration Cardtemporary license information onIDREF="ch138"Temporary Licensesstandalone systemsIDREF="ch410"Setting Up a Network License Server and Global Location Broker with ­sgiautoIDREF="ch417"Setting Up a Global Location Broker Manuallystart date, definedIDREF="ch113"What Is a License?stcode commandmanual pageIDREF="intro28"For More Information subsystemIDREF="appa21"NetLS FilesSys ID number. See system identification numberIDREF="intro49"Product Supportsysinfo command­s optionIDREF="ch123"What Is a License?getting Sys ID numberIDREF="ch216"Missing Software License Registration Cardgetting sysinfo numberIDREF="ch122"What Is a License?sysinfo numbercheckingIDREF="ch426"Setting Up a Network License Server ManuallyIDREF="ch316"Non-graphical Installation of a Node-locked LicenseIDREF="ch37"Graphical Installation of a Node-locked LicenseIDREF="ch48"Setting Up a Network License Server and Global Location Broker with ­sgiautodefinedIDREF="ch121"What Is a License?system identification numberfor replacement licensesIDREF="ch143"Permanent LicensesobtainingIDREF="ch215"Missing Software License Registration Cardsystem rolesIDREF="ch198"Required Software, Configuration Flags, and DaemonsIDREF="ch185"Guidelines for Global Location Brokers and Network License Serverstarget numberdefinedIDREF="ch118"What Is a License?obtainingIDREF="ch120"What Is a License?target type, definedIDREF="ch117"What Is a License?TCP/IP and NetLSIDREF="ch180"Guidelines for Global Location Brokers and Network License ServersTechnical Assistance CenterIDREF="intro33"Product Supporttemporary licensesreplacing with permanent licenseIDREF="ch24"Flowchart of the Licensing ProcessIDREF="ch633"Installing Replacement Licensestimed, using for clock synchronizationIDREF="ch75"Routine Maintenance of Global Location Brokerstroubleshooting procedurefor concurrent licensesIDREF="ch95"Basic Troubleshooting Procedure for Concurrent Licensesuname commandIDREF="intro5"NetLS Versions Documenteduser fileexampleIDREF="ch612"A Sample User FilekeywordsIDREF="ch616"User File SyntaxsyntaxIDREF="ch615"User File Syntax/usr/etc/ncs/glb_obj.txt file. See glb_obj.txt fileIDREF="ch168"License Groups for Concurrent Licensing/usr/netls/nodelock file. See /var/netls/nodelock fileIDREF="intro45"Product SupportUUID valueIDREF="ch166"License Groups for Concurrent Licensinguuid_gen commandmanual pageIDREF="intro29"For More Information subsystemIDREF="appa22"NetLS FilesusingIDREF="ch42"Creating a License GroupIDREF="ch744"Creating a New License Groupuuidname.txt fileIDREF="appa28"NetLS FilesIDREF="intro30"For More Information /var/adm/SYSLOG fileIDREF="ch93"TroubleshootingIDREF="ch81"Error Messages/var/ncs/glb_obj.txt file. See glb_obj.txt fileIDREF="ch169"License Groups for Concurrent Licensing/var/netls/nodelock filebacking upIDREF="ch73"Backing Up DatabasesexampleIDREF="ch320"Non-graphical Installation of a Node-locked Licenseidentifying licensesIDREF="ch626"Identifying Licenses in a Nodelock Filesymbolic link to /usr/netls/nodelockIDREF="ch65"Deleting a Node-locked Licensevendor IDand node-locked licensesIDREF="ch128"Node-locked LicensesdefinedIDREF="ch15"What Is a License?usingIDREF="ch515"Non-graphical Concurrent License InstallationIDREF="ch317"Non-graphical Installation of a Node-locked LicenseIDREF="ch39"Graphical Installation of a Node-locked LicenseIDREF="ch57"Graphical Concurrent License Installationvendor namedefinedIDREF="ch14"What Is a License?in user fileIDREF="ch614"A Sample User FileusingIDREF="ch68"Deleting a Concurrent LicenseIDREF="ch38"Graphical Installation of a Node-locked LicenseIDREF="ch513"Non-graphical Concurrent License InstallationIDREF="ch56"Graphical Concurrent License Installationvendor passworddefinedIDREF="ch16"What Is a License?usingIDREF="ch58"Graphical Concurrent License InstallationIDREF="ch514"Non-graphical Concurrent License Installationversion of NetLSIDREF="intro2"NetLS Versions Documentedversions commandgetting product name and versionIDREF="ch213"Missing Software License Registration Cardlisting installed productsIDREF="ch627"Identifying Licenses in a Nodelock File