DETAIL DESCRIPTION: There's a known problem with lit (License Installation Tool) if it's not patched with PatchID 104829. Without the patch, lit puts extra characters in the license file which leads to license errors. To workaround the problem, follow the instruction below to setup a permanent license. SOLUTION SUMMARY: 1. Call the license center to get the license key via email License Center: 1-800-USA-4SUN (option 3 & then option 1) 2. Once you get the license email, save the attachment into a file. There are two attachments, one of which is the license file. The license file can be recognized by looking for the word "SERVER .." on the first line. The other attachment is "User-Info" which gives information on the products you are licensed for, serial numbers, hostname etc. Save the correct attachment into a file /tmp/lic. 3. Copy the saved license file to the correct locations as follows: # cp /tmp/lic /etc/opt/licenses/licenses_combined # cp /tmp/lic //SUNWspro/license_dir/sunpro.lic,1 is where you chose to install the compilers. The default location is /opt. NOTE: If you already have licenses in the license_dir, there may already be a file called sunpro.lic,1, or sunpro.lic.X where X is some number. You will need to name your file using the next available number. 4. Restart your license manager # cd /etc/opt/licenses # ./lmdown -a -c licenses_combined (Make sure the license daemon is down before starting again) # ps -ef | grep lmgrd # ps -ef | grep suntechd (Start the license daemon now) # /etc/rc2.d/S85lmgrd 5. Check if the license daemon reports all your licenses by issuing the following command: # ./lmstat -a -c licenses_combined. It should report the status of the daemon's as well as the usuage information for each product that is correctly licensed. 6. Now you should be able to use the compilers by doing the following: # cd //SUNWspro/bin # ./cc -xlicinfo It should report the number of licenses available to the number of licenses you purchased. If it's 0, then the license manager is probably not running. Another check: # touch /tmp/test.c # /opt/SUNWspro/bin/cc /tmp/test.c "test.c", line 1: warning: empty translation unit Undefined first referenced symbol in file main /opt/SUNWspro/SC4.2/lib/crt1.o ld: fatal: Symbol referencing errors. No output written to a.out You just successfully compiled a zero length file without any license errors. Otherwise you would have seen something like this: License Error : Cannot connect to the license server (austin).. for product(Sun WorkShop Compiler C). (License server may not have been started) Cannot connect to license server (-15,12:146) Connection refused cc: acomp failed for test.c If this happen please contact Sunservice at 1-800-USA-4SUN and also prepare to send /var/tmp/license_log file. ******************************************************************** SYNOPSIS: FlexLM PSD/FAQ DETAIL DESCRIPTION: Sunservice Product Support Document for Flexlm License Revision 1.0 Date: July, 5 1996 Mail to: Brett Berg Flexlm_License_PSD Sunservice Product Support Document for Flexlm License 1.0 About Flexlm License. 2.0 Flexlm License Product Overview. 3.0_Debugging_Flexlm_License 3.1 Licensing Check List 4.0_Hints_and_Tips 4.1 Inconsistent encryption code for... 4.2 License Error : Cannot connect to the license server 4.3 Cannot connect to license server 4.4 Retrying socket bind (address in use: port 1722)" in license_log ? 4.5 Configuring 4.1.x compiler clients after upgrading to lmgrd.ste on a 5.x license server? 4.6 "License file does not support this version"? 4.7 "Invalid returned data from license server"? 4.8 "Not a valid server host, exiting" in license_log? 5.0_Frequently_Asked_Questions 5.1 How do I set up demo licenses? 5.2 "Can't get server: cannot find license file" when trying to run "lmstat" 5.3 Does the license password obtained for SPARCompiler 2.0.1 work for SPARCompiler 3.0? 5.4 How can I access SPARCompiler/SPARCworks over the network? 5.5 Can I use a 4.1.x system as a license server to serve SPARCompiler 3.0 on 5.x systems? 5.7 Why is lmstat or the -xlicinfo switch reporting less licenses available than expected? 5.8 Can I merge 3rd party license passwords into licenses_combined file? 6.0_Installing_Flexlm 6.1 Installing the license password 6.2 Changing Hostnames 6.3 Flexlm Version 6.4 Running Licenses on a remote server 6.5_Installing_Licenses_in_Sunlink 6.5.1 Installing Flexlm Licenses 6.5.2 Software Manager Installation 6.5.3 Package Add Installation 7.0 Flexlm Patches 8.0 Known Bugs and RFEs 9.0 References 10.0 Supportability. 11.0 Where to go for additional support 1.0 About Flexlm License. The Flexible License Manager (FLEXlm*) is the standard network license manager in the Unix(TM) software industry. FLEXlm is used by over 300 leading Unix software vendors to control the use of their software products. If you are a Unix user, chances are one or more of the products on your network is licensed by FLEXlm. Over the years Highland has answered many questions from users of FLEXlm-licensed products. We realized there was a need for a manual that explains FLEXlm from an end-user standpoint. This manual grew out of that need and is provided as a service to you, the end-user. Please keep in mind that certain topics (such as password encryption) are sensitive; Sun cannot document them in any detail. Also, each vendor implements FLEXlm with a slightly different spin. If you don't find out what you need to know here, you might want to contact your vendor's technical support group. 2.0 Flexlm License Product Overview. FLEXlm Components The four main components of FLEXlm are: * the license manager daemon * the vendor daemon * the license file * the application program The License Manager Daemon The license manager daemon handles the initial contact with the client application programs, passing the connection on to the vendor daemon. It also starts and restarts the vendor daemons. FLEXlm permits multiple redundant license manager daemons on different server nodes, allowing you to make your license available if any two out of three server nodes is running. Also, you don't have to split up your licenses among multiple servers, or rely on any one machine. The Vendor Daemon In FLEXlm, licenses are handled by running processes. There is one process for each vendor who has a FLEXlm-licensed product on the network. This process is called the vendor daemon. The vendor daemon keeps track of how many licenses are checked out, and who has them. If the vendor daemon terminates for any reason, all users lose their licenses. Users normally regain their license when the daemon restarts. Client programs communicate with the vendor daemon through TCP/IP sockets. This enables client and daemon processes to be on separate nodes in a network. The traffic between the client and the daemon is machine-independent, which means any process can run on different machine types. (This is what is meant by heterogeneous.) The License File Licensing data is stored in a text file called the license file. The license file is created by the system administrator. It contains information about the server nodes and vendor daemons, and one line of data (called a FEATURE line) for each licensed feature. A feature line contains an encryption code based on the data in that line, the hostids specified in the server lines, and other vendor-specific data. In some environments, the licensing information for several vendors might be combined into a single license file in the default location: /usr/local/flexlm/licenses/license.dat You can override this location by setting the environment variable LM_LICENSE_FILE to point elsewhere, or by following instructions supplied with the licensed application. If your site has software from multiple vendors with incompatible license files (due to different sets of servers), you can keep the data in separate files and set the LM_LICENSE_FILE variable to reference multiple files. For details, see Chapter 1, The License File. The Application Program The application program using FLEXlm is linked with the program module (called the FLEXlm client library) that provides the communication with the license manager daemon. During execution, the application program communicates with the vendor daemon to request a license. The License Request Process When the application program calls the FLEXlm client library to request a license, the following occurs: 1. The license module in the client application finds the license file, which includes the host name and port number of the license manager daemon. 2. The client establishes a connection with the license manager daemon and tells it what vendor it needs to talk to. 3. The license manager daemon (lmgrd) determines which machine and port correspond to the master vendor daemon (if multiple redundant daemons are running), and sends that information back to the client. 4. The client establishes a connection with the specified vendor daemon and sends its request for a license. 5. The vendor daemon checks in its memory to see if any licenses are available and sends a grant or denial back to the client. 6. The license module in the client returns to its caller with the grant or denial, and the application takes the appropriate action. 3.0 Debugging Flexlm License 3.1 Licensing Check List * All license servers should have a license file called: /etc/opt/licenses/licenses_combined All licensing related binaries and scripts should be found in /etc/opt/licenses on the license server. These files include: LIC_CONFIG_SCRIPT, lic2.0_reconfig, lit, lit_tty, lmdown, lmgrd.ste, lmhostid, lmremove, lmreread, lmstat, lmver, suntechd. * Check the files: /tmp/license_errors for error messages from lit /tmp/license_log for error messages from lmgrd.ste * For 5.x systems, all product servers ( i.e. where the compilers are installed ) must have elementary license files in: /opt/SUNWspro/license_dir/sunpro.lic,* Each file in the /opt/SUNWspro/license_dir represents a source of license tokens. Check if these files are identical to licenses_combined on each license server. If the product server is not also the license server, make sure to copy /etc/opt/licenses/LIC_CONFIG_SCRIPT from the license server to the product server, and run it. * For 4.1.x systems, check if the router files have the correct path to the license data file. Location of router files are: /usr/lang/SC2.0.1/SC_LICENSE_FILE /usr/lang/SW2.0.1/bin/SW_LICENSE_FILE /usr/lang/SC_LICENSE_FILE ( symbolic link to SC2.0.1/SC_LICENSE_FILE ) /usr/lang/SW_LICENSE_FILE ( symbolic link to SW2.0.1/bin/SW_LICENSE_FILE ) /usr/lang/FileMerge/bin/SW_LICENSE_FILE ( symbolic link to /usr/lang/SW2.0.1/bin/SW_LICENSE_FILE ) /usr/lang/lib/License_File e.g. To make a symbolic link on a 4.1.x system for FileMerge, type the following commands as root: # cd /usr/lang/FileMerge/bin # ln -s /usr/lang/SW2.0.1/bin/SW_LICENSE_FILE SW_LICENSE_FILE * Check if LM_LICENSE_FILE is set correctly. The value of LM_LICENSE_FILE needs to be the full path to license.dat, including the file name. e.g. %% setenv LM_LICENSE_FILE /opt/SUNWspro/license_dir/sunpro.lic,1 Note: setting LM_LICENSE_FILE is not necessary if you have the c) or d) above set up correctly. * Check the number of available licenses. %% /etc/opt/licenses/lmstat -a -c /etc/opt/licenses/licenses_combined Note: This can only be run on the license server. * Make sure you are running the latest lmgrd.ste and suntechd provided by SunPro. Earlier versions of lmgrd and suntechd are not compatible with SPARCompiler/SPARCworks 3.0. * Make sure all of the FEATURE lines go before the INCREMENT lines. 4.0 Hints and Tips 4.1 Inconsistent encryption code for... "(suntechd) Inconsistent encryption code for sunpro.c" in license_log? If you get the "Inconsistent encryption code" error message after trying to run lmgrd.ste, the reason could be any one of the following: * Incorrect version-id ( needs to be the version-id used for obtaining the password ) The version-id should be a floating point number. e.g. in case of C compiler: Software Version What you need in licenses_combined 2.0 2.0 2.0.1 2.010 3.0 3.0 * You have a 30 day demo license. Please refer to question 1 above on identifying and setting up demo licenses. * You have typos in any one of the following critical password dependent components: + Hostid + The feature ID + The password itself + The vendor string (the string right after the 20 digit password) o For a list of valid feature IDs, please refer to the manual "Installing SunPro Software on Solaris", p. 13. o The password should be a 20 digit hexadecimal number. o The vendor string should have a number within the double quotes for all INCREMENT lines. This number is encrypted into the password and hence cannot be changed. Please refer to the email or fax you received from the password center for the correct number in this field. * An attempt to merge with existing FLEXlm licensed software's license data file. Use a separate license data file if not using common license servers for different softwares. Make sure you pick a different port (socket) number on the SERVER line for each license data file if 2 or more lmgrd/lmgrd.ste process will run on a particular machine. Refer to question 13 for more details. You are recommended to have all SunPro products being served by the same license manager, as there can only be one "suntechd" daemon running on each machine. * Running an old version of lmgrd which does not support the new passwords. SPARCompiler/SPARCworks 3.0 uses FLEXlm version 2.61. The license manager binary is named "lmgrd.ste". If you are not running "lmgrd.ste", you are likely not running a compatible license manager. To check the version of license manager, examine the first 2 lines of /tmp/license_log, or run "lmver lmgrd.ste". * Password was obtained for redundant servers. If the password is obtained for multiple servers, then you will need multiple SERVER lines in licenses_combined and run the lmgrd.ste process on all of those machines specified on the SERVER lines. e.g. A password obtained for 3 redundant license servers will need 3 SERVER lines in licenses_combined and lmgrd.ste needs to run on all 3 machines. Steps needed to configure redundant license servers: o Run lit on one of the redundant license servers. o Copy /etc/opt/licenses/LIC_CONFIG_SCRIPT to the other license servers and product servers, and run it. * The keyword "FEATURE" has been changed to "INCREMENT", or vice versa. These keywords are encrypted as part of the 20 digit password, and hence "FEATURE" and "INCREMENT" are not interchangeable. 4.2 License Error : Cannot connect to the license server "License Error : Cannot connect to the license server (hostfoo).. for product(SPARCompiler C). (License server might not have been started)" during compilation? Reason: * lmgrd.ste might not be running on the license server "hostfoo." * The elementary license files sunpro.lic,* might not contain the correct hostname of the license server. Solution: 1. Check if "hostfoo" is your dedicated license server. 2. Check if lmgrd.ste is running by executing the command "ps -ef grep lmgrd" on the license server. 3. Check the /tmp/license_log file on the license server for error messages from the last lmgrd.ste execution. 4.3 Cannot connect to license server "suntechd: cannot connect to license server" when trying to run "lmstat"? Reason: lmgrd.ste is not running. Solution: You need to start the lmgrd.ste process on the license server. Please refer to "Installing SunPro Software on Solaris", p.62, for details on how to start the license daemon. 4.4 Retrying socket bind (address in use: port 1722)" in license_log ? Reason: The current socket number (specified in licenses_combined as the last entry on the SERVER line ) is being used by another process. If there was an attempt to start lmgrd.ste with the same socket number right before, it means you haven't shutdown lmgrd.ste correctly before restarting it. Solution: * Check if lmgrd is running on the license server using: "ps -ef | grep lmgrd" o If lmgrd is still running, shut it down with lmdown: /etc/opt/licenses/lmdown -c /etc/opt/licenses/licenses_combined -q o If lmgrd is not running, probably some other process is using that particular socket. Just change the socket number in license.dat. (Suggested values: 1715, 1720, 1725.) 4.5 Configuring 4.1.x compiler clients after upgrading to lmgrd.ste on a 5.x license server? Copy over LIC_CONFIG_SCRIPT and lic2.0_reconfig from /etc/opt/licenses on the license server to the 4.1.x system. As root, run LIC_CONFIG_SCRIPT first, then lic2.0_reconfig. All the router files will be updated. 4.6 "License file does not support this version"? The version of the software you are running doesn't match the version of the software registered in the license manager. Ensure that at least one of the elementary license files in /opt/SUNWspro/license_dir (e.g. sunpro.lic,1) contains a FEATURE/INCREMENT line for the version of SPARCompiler/SPARCworks tools you want to use. The error message could be a result of either of the following: * None of the license files contains a password entry to support the desired version of the product, or * There is a typo somewhere in the license files. When checking for typos, make sure both /etc/opt/licenses/licenses_combined on each license server(s) and /opt/SUNWspro/license_dir/sunpro.lic,* on the product server are correct (note that the license server and the product server can be the same machine). The sunpro.lic,* file(s) are copies of all or parts of the licenses_combined file. If information in the licenses_combined file and sunpro.lic,* file(s) is not consistent, you will get the error message. Restart the license manager lmgrd.ste after any modifications to the license files are made. 4.7 "Invalid returned data from license server"? This message means that the FLEXlm licensed application you are trying to run is not compatible with the version of license manager running on the license server. This usually is a result of an attempt to merge license passwords from different software vendors into a single license data file. This might not always work. Please refer to question 13 above for more information. 4.8 "Not a valid server host, exiting" in license_log? Check the license file (either license.dat or licenses_combined) and make sure the hostname on the "SERVER" line is consistent with the /etc/nodename file, the /etc/hosts file, and NIS/NIS+ table entries. For example, if you get: 1/19 11:28:41 (lmgrd) "foo.bar.company.com": Not a valid server hostname, exiting. 1/19 11:28:41 (lmgrd) Valid server hosts are: "foo" and your /etc/hosts file contains: 129.141.17.11 foo.bar.company.com foo loghost then change the SERVER line of license.dat/licenses_combined to the following: SERVER foo.bar.company.com Restart lmgrd or lmgrd.ste. However, if you don't want to change the SERVER line in the license file and choose to instead modify /etc/hosts, /etc/nodename, or the NIS/NIS+ tables, you will need to reboot your machine before restarting the license manager. 5.0 Frequently Asked Questions 5.1 How to set up demo licenses? A typical demo license line for a FORTRAN 3.0 demo looks like: INCREMENT sunpro.f77 suntechd 3.000 20-apr-1994 0 8B3CC547D75CCDCE90FA "0" DEMO To identify a demo license, make sure you have: * a definite expiration date, which should be about 30 days since the password is requested. * 0 (zero) number of users ( means unlimited, and is located after the date ). * the keyword "DEMO" at the end of the FEATURE line. * run /etc/opt/licenses/lit, or /etc/opt/licenses/lit_tty You are all set. There is NO need to run the license manager lmgrd.ste. 5.2 "Can't get server: cannot find license file" when trying to run "lmstat"? Reason: 'lmstat' is not used with the proper option (-c), or the environment variable LM_LICENSE_FILE is not set correctly. Solution: 1. Use the -c option with 'lmstat' e.g.: lmstat -c /etc/opt/licenses/licenses_combined 2. Make sure you have LM_LICENSE_FILE pointing to the correct license data file. Refer to section I. e) above (TROUBLE SHOOTING HINTS) on how to set LM_LICENSE_FILE correctly. 5.3 Does the license password obtained for SPARCompiler 2.0.1 work for SPARCompiler 3.0? SPARCompiler/SPARCworks 3.0 is a new release of power development tools from SunPro and hence require new licenses. Passwords obtained for 2.0.1 versions will not work for 3.0. 5.4 How can I access SPARCompiler/SPARCworks over the network? Once you have the license manager (lmgrd.ste) running on the server and have verified that SPARCompiler and SPARCworks work on the server machine, you might want to allow users to access the compilers and tools via NFS/automount. If you are running SPARCompiler/SPARCworks 3.0, all you need to do is to NFS mount or automount the /opt/SUNWspro directory. If you are running SPARCompiler/SPARCworks 2.0.1 with the new license manager, the client machines will need: * NFS/automount access to the SPARCompiler and SPARCworks binary, as well as * NFS/automount access to the elementary license data file (sunpro.lic,*). It is highly recommended that the mount point on the client machines matches the physical SPARCompiler/SPARCworks directory on the server machine, so that users can make use of the router files (SC_LICENSE_FILE & SW_LICENSE_FILE ) to obtain a license. If the NFS mount point is different, you will have to add the NFS client's path in the router files. Please note that a router file is a colon-separated list of paths. For example, if your NFS client system's mount point is /opt2/SUNWspro, modify the lines in SC_LICENSE_FILE and SW_LICENSE_FILE to: /opt/SUNWspro/SunTech_License/license.dat:/opt2/SUNWspro/license_dir/sunpro.lic,1 5.5 Can I use a 4.1.x system as a license server to serve SPARCompiler 3.0 on 5.x systems? Yes. Just make sure the new licensing software from the SPARCompiler/ SPARCworks 3.0 CD is loaded on the 4.1.x system. After running "lit", copy LIC_CONFIG_SCRIPT to each 5.x client's /tmp directory and run it as root. Don't forget to run lic2.0_reconfig on the 4.1.x system. Note that the old license manager from SPARCompiler/SPARCworks 2.0.1 cannot be used to serve SPARCompiler/SPARCworks 3.0 licenses. Please refer to p. 60 of the "Installing SunPro Software on Solaris" manual for more details. 5.7 Why is lmstat or the -xlicinfo switch reporting less licenses available than expected? Some of your FEATURE/INCREMENT lines in your license file might be incorrect. Examine the /tmp/license_log file carefully for the problematic entry and correct it accordingly. 5.8 Can I merge 3rd party license passwords into licenses_combined file? Incompatibility between other 3rd party FLEXlm licensed applications and various versions of the license manager is a known problem; hence SunPro strongly recommends running a separate lmgrd.ste to serve all the SunPro and SunConnect products. However, you can try to merge 3rd party license passwords into the licenses_combined file. There is a chance it might work, depending on the version of license manager they support. If they fail, then you will need to run the license manager that comes with the 3rd party products. 6.0 Installing Flexlm 6.1 Installing the license password To install the password for Sunlink software do the following: 1. Start the Sun License Installation Tool from the command line by using the following syntax. => /etc/opt/licenses/lit & 2. The Sunlink product name should appear in the upper left hand corner of the window along with the version that is being installed. Note: This version number is only the major release version number and will not reflect any maintenance release levels. If the product that appears in the top left corner of the window is not the proper Sunlink product, use the "Select Product" menu to select the Sunlink product for license installation. 3. There are two ways to enter the license information. A. If the license center set the license password via email, there is an attachment with a file that contains all the necessary password information. Store this file. Select the "Install from file" option and enter the file location. The alternate way to install the license password is to enter it manually in the license tool form. Enter the Rights To Use as indicated in the license Fax or email. If the license is a Demo license enter the expiration date in the next field. If the license is a permanent license, leave this field blank. B. Enter the password the was faxed or emailed in the Password field. This can be done in lower case as the tool will convert it. Double check that the password is correct. C. Verify that the Password Checksum field in the form matches the checksum that was sent by the license center. These two figures MUST match. This field is a combination of all the fields in the bottom of the form. 4. When the license information had been entered correctly and verified, press the "Done With License" button. This will install the license in the /etc/opt/licenses/licenses_combined and a second copy in /opt/SUNWconn/license_dir. 5. Quit the License Tool using the "Save Licenses" option and note the message that appears. 6.2 Changing Hostnames It is possible to change the hostname of an existing license installation without re-installing the licenses. It is recommended that the license passwords be re-installed using the License Tool to insure that all the files that need to be modified have been done properly. To change the hostname by re-installing the licenses perform the following: 1. Run the Clean Sweep program in /etc/opt/licenses directory. This will clear all the licenses out of the licenses_combined file, remove the secondary copies in all known locations, and reset all products to the pre-license condition. 2. Run the License Tool as described in section 6.3 for each product that needs to have a license installed. In the event that it is not desirable to re-install all of the licenses follow this procedure: 1. The first line in the licenses_combined file and all the secondary license files will have a server line identified by the word SERVER appearing in the first column. The next entry will be the host name of the license server. This is not the name of the client requesting licenses. After making a backup copy of the licenses_combined file, Change this entry ONLY being careful to preserve the line spacing and the other entries. Save this file. 2. In the /etc/opt/licenses directory, there will be two other types of files that are part of the secondary licenses. They will be in a format that has the product name and the version number combined to identify the product license files. If there is an extension of .lic, this is the actual secondary license file. Contained in this file is the actual copy of the license_combined file headers and one line with the license password line. Change the SERVER line being careful to preserve all spacing. A file with an extension of .loc contains the location of the actual secondary license file. Modify the file that is located at in this directory. 3. Once the modifications are complete restart the license daemons by using the command "lmdown." Then restart the daemons by rebooting the system (recommended) or submitting the daemon to background with the following command: => lmgrd.ste -c /etc/opt/licenses/licenses_combined & 4, Using the "lmstat -a" command should show that the license daemons are running and a listing of all the license indicating availability. If this doesn't not happen, review the steps again. If the utility indicates that it can't find the daemon, from csh enter setenv LM_LICENSE_FILE /etc/opt/licenses/licenses_combined and re-run the utility. 6.3 Flexlm Version To find the version of Flexlm that is currently running: 1. Enter ps -ef ! grep lmgrd to discover where the daemon software is located. 2. Move to the directory where the software is located. 3. Enter lmgrd.ste -v to obtain the version of the software. Example Output: ---------------------------------------------------------------------- 5/22 11:41:07 (lmgrd) FLEXlm - Copyright 1988, 1993, Globetrotter Software, Inc. lmgrd v2.60 - Copyright 1988, 1992 Highland Software, Inc. ---------------------------------------------------------------------- 6.4 Running Licenses on a remote server Flexlm licenses can be run from a remote server to the Sunlink gateway. Install the licenses on the remote server with the procedure previously outlined. To test to insure that the Sunlink gateway is able to check out a license from a remote setver, use the LMSTAT utility. * Set the LM_LICENSE_FILE environment variable to: /etc/opt/licenses/licenses_combined, or the location of where the primary license file is located on the network. * Use the LMSTAT command with the -a option to insure that the licenses are available to the gateway. Example Output: root-> ./lmstat -a lmstat - Copyright (C) 1989, 1993 Highland Software, Inc. Flexible License Manager status on Wed 5/22/96 11:52 License server status: ice: license server UP (MASTER) Vendor daemon status (on ice): lic.SUNW (v3.x): UP Feature usage info: Users of sunlink_x.25: (Total of 1 licenses available) root ice /dev/tty (v8.000) (ice/1726 102), start Mon 5/13 8:03 6.5 Installing Licenses in Sunlink 6.5.1 Installing Flexlm Licenses To install the Flexlm license software with a Sunlink product use either the Software Manager (SWMTOOL) or Package Add Utility (PKGADD.) All the packages that are installed will be located in /etc/opt/licenses directory. In the case of Sunlink there will be an additional directory located at /opt/SUNWconn/license_dir. This second directory contains copies of each Sunlink Flexlm license. 6.5.2 Software Manager Installation To install the license software through Software Manager (SWMTOOL) perform the following steps. 1. Start Software Manager by issuing "SWMTOOL &" on the command line from the root account. The tool will have a slightly different appearance between earlier releases of Solaris and Solaris 2.5. o To select the install media for Solaris 2.5, select the Add function under the Edit Menu Bar list. This will produce a pop-up window. If Volume Manager is running, which is run by default in Solaris installations, type the directory location of the Sunlink software packages within the /cdrom top directory. If Volume Manager is not running, select the "CD without Volume Management" menu select item under Software Location and then enter the CD mount point below. o To select the install media for earlier versions of Solaris, select the props... button. This will product a pop-up window. If Volume Manager is running, change the Media Type to "Mounted Directory" and enter the directory location under /cdrom that the media is located. If Volume Manager is not running, use the "Local CD-ROM" Media Type and enter the mount point for the CDrom. 2. Select the packages in the list of installable packages that you wish to install. The Sunlink license package is contained in two separate entries. It is recommended that you install both. The Flexlm License System entry will install only the Flexlm license software. The STE License Installation Tool entry will install the Sunlink and Sun specific license information and tools. Note: It is Recommended that the Flexlm License System be install every time to insure that the proper version of the license software is available. 3. After making the proper selections for installable products, press the add button if you are running the Solaris 2.5 tool or the Begin Installation button if you are running the earlier tool. 4. During the installation process, another progress window will be displayed. This window will pause from time to time and ask for clearance to continue based on decisions that need to be made. In most cases the default will satisfy the decision and the install will proceed. 5. When the installation is complete, dismiss the tool and proceed with registering the password. 6.5.3 Package Add Installation To install the license software through Package Add (PKGADD) perform the following steps. 1. Run the PKGADD utility by using the following parameters. This utility must be run from the root account. => pkgadd -d The install directory will be the location where the SUNWlit directory appears. Command Example: => pkgadd -d /cdrom/cdrom0/s0/ 2. A list of packages will be presented in a menu format. Choose the numbers that correspond to the packages that you wish to install. In the Sunlink products, there are two separate licenses packages. It is recommended that both packages be installed to insure that the proper level of license software in running. SUNWlics contains the Flexlm license software and SUNWlit contains the Sunlink and Sun specific license tools. 3. The following screens will pause from time to time and ask for decisions from the installer. In most cases the default decision is the proper one to make. 4. When the installation process completes, terminate the tool and continue installing the password. 7.0 Flexlm Patches 101591-01 FLEXlm 2.0: License server dies when more than 50 users logged in 102381-01 FLEXlm 4.0 jumbo patch 102493-01 FLEXlm 2.4, 2.6, 2.61: Jumbo patch. 8.0 Known Bugs and RFEs There is currently no known Bugs to Flexlm. 9.0 References * Flexlm - Flexible License Manager - End User Manual * Flexlm - Flexible License Manager - Programmers Manual GLOBEtrotter Software Inc. 20045 Stevens Creek Blvd., Suite 2F Cupertino, CA. 95014 (408)255-5616 Phone (408)255-6362 Fax Mail to:info@globes.com 10.0 Supportability. SunService is responsible for assisting the user in the application of the license software and the installation of the license certificates. In addition SunService will assist in the identification of bugs and other problems that arise from the product as errors in configurations. Sun will report any bugs that are verified in the product to the vendor to be fixed in the next released version of the product. We can help resolve problems where Sun products are not behaving correctly, but in such cases the contact must be a system administrator who has a good understanding of the software and the Flexlm license product. 11.0 Where to go for additional support GLOBEtrotter Software Inc. 20045 Stevens Creek Blvd., Suite 2F Cupertino, CA. 95014 (408)255-5616 Phone (408)255-6362 Fax Mail to:info@globes.com PRODUCT AREA: Licensing PRODUCT: FLEXlm SUNOS RELEASE: any HARDWARE: any