INSTALLING FLOATING CODEWORDS ON UNIX ===================================== The following instructions outline a quick procedure for installing your new ADS2002C/RFDE Codewords. If you would like more detailed instructions, please refer to Chapter 4 of the "Installation on Unix Systems" guide for ADS2002C and/or Chapter 3 of the “Installing RFDE” guide. Read the Prerequisites, follow the Procedures, and if you have questions, please read the “Common Problems and More Help” sections in this document or contact Agilent Technical Support (http://eesof.tm.agilent.com/assist/contact.html). PREREQUISITES ------------- A license server, on a network, can serve floating licenses. Any machine on that network can checkout a license up to the total number of licenses. The license server doesn't have to have a full installation of ADS2002C or RFDE on it (see step 4 for more information). RFDE works with Cadence versions 4.4.5 and 4.4.6 and is available on HP-UX, Sun and IBM platforms: HP-UX 11.0x Solaris 2.6, 2.7 and 2.8 IBM AIX 5.2 RFDE also requires the following Cadence Products: Virtuoso Schematic Composer. Analog Design Environment. OASIS. OASIS is included in the RFDE purchase price; contact your local Cadence representative to obtain codewords and/or Cadence products installation and licensing information. ADS2002C AND RFDE LICENSE INSTALLATION PROCEDURES -------------------------------------------------- If you are wish to install RFDE codewords only, skip to the “RFDE LICENSE INSTALLATION PROCEDURES” section. The following procedure assumes you are installing codewords for the first time. 1. Save the license.lic attachment to a file on your machine. If you received the files in a Windows PC, make sure that no hidden characters were added to the file by the windows application (see ADS2002C installation manual’s Appendix A for troubleshooting instructions) 2. Place the license.lic file on the license server and edit the SERVER and VENDOR lines: The license server's host ID is specified on the SERVER line in your license.lic file. If you have more than one SERVER line, you need to follow steps 2 through 4 on each of the license servers. If ADS2002C is installed on the license server, you can place the license.lic in the licenses sub-directory of the ADS2002C installation directory. For example: /apps/ads2002C/licenses/license.lic ---------------------- NOTE --------------------------------------------- It is strongly recommended that you remove any expired licenses from your license.lic file. Keeping the license file as short as possible will prevent confusion and problems. ------------------------------------------------------------------------- 3. Once you have the license.lic file in place on the license server, verify the correctness of the information on the SERVER and VENDOR lines. The SERVER line must contain the hostname of the license server and its host ID. For example: SERVER joshua 80fb214d We often send the license.lic file with hostname set to 'unknown'. This MUST be changed to the correct hostname. Optionally, you may want to specify a TCP port for the license server to listen to for requests. If a TCP port is not specified, as in the example above, FLEXlm will default to the first available port in the range 27000 to 27009. To specify a TCP port, modify the SERVER line as follows: SERVER joshua 80fb214d 27005 In this example, the TCP port is set to 27005. The VENDOR line controls which vendor daemon will be started. It must contain the name of the vendor daemon. For example: VENDOR agileesof As long as the vendor daemon exists in the same directory that lmgrd is started from, this is sufficient. If you have placed the agileesof daemon executable in a different location, then enter the full path as follows: VENDOR agileesof /apps/ads2002C/licenses/bin/agileesof Be sure to specify the actual location on your license server. 4. Once the information on the SERVER and VENDOR lines is correct, start the FLEXlm license manager on the license server machine. For example, cd /apps/ads2002C/licenses/bin ./lmgrd -c ../license.lic -l ../adsflex.log In this example, the lmgrd supplied with ADS2002C is started. The path to the license.lic file is specified using the '-c' option and a log file is started using the '-l' option. You MUST use a version of lmgrd that is equal to or greater than the version of agileesof. You can check the versions of lmgrd and agileesof as follows: cd /apps/ads2002C/licenses/bin ./lmgrd -v ./agileesof -v The latest version of lmgrd can be downloaded from the Globetrotter Software web site (see the URL in the More Help section below). You can also run a custom install of ADS2002C and choose to only install the FLEXlm software. This is a good way to get all of the latest FLEXlm software for ADS2002C. After starting lmgrd, wait about 10 to 15 seconds and then look at the contents of adsflex.log. You should not see any errors and you should see that agileesof started successfully and has enabled the licenses contained in your license.lic file. Please see Chapter 4 of the ADS2002C Installation Guide for a way to automate the startup of lmgrd. 5. You should now be ready to run ADS2002C. Any machine that will run ADS2002C (client) must be able to locate the license server. Continuing with the examples above, the license server is named joshua. If no TCP port was specified on the SERVER line, set the following environment variable: [Korn/Bourne Shell] AGILEESOF_LICENSE_FILE=@joshua export AGILEESOF_LICENSE_FILE [C Shell] setenv AGILEESOF_LICENSE_FILE @joshua If a TCP port was specified on the SERVER line, set the environment variable as follows: [Korn/Bourne Shell] AGILEESOF_LICENSE_FILE=27005@joshua export AGILEESOF_LICENSE_FILE [C Shell] setenv AGILEESOF_LICENSE_FILE 27005@joshua You will want to use the actual TCP port number you specified on your SERVER line. Note: AGILEESOF_LICENSE_FILE will override any settings specified by the environment variable LM_LICENSE_FILE. 6. You are now ready to run ADS2002C. INSTALLATION OF RFDE CODEWORDS ------------------------------ If you are adding RFDE Codewords to your ADS2002C license server, you will want to simply append the four RFDE INCREMENT lines: INCREMENT rfde_premier agileesof 2.0 31-dec-2002 2 \ VENDOR_STRING=80FB214D SIGN="029C 40BA 2688 2400 8933 6220 \ 4E4C 93CD 24C8 137C AE01 535D 0DBD EC8B CBEC D5BB 620D F369 \ C121 A0BF 6B03" INCREMENT rfde_premier_plus agileesof 2.0 31-dec-2002 2 \ VENDOR_STRING=80FB214D SIGN="0318 8986 0726 9D20 01AF CBE4 \ 44B0 18AD 6EA9 F02D 5302 25B7 FF7E 8228 B78E EF78 C21B 58E6 \ A420 9BBE 20E2" INCREMENT rfde_wireless agileesof 2.0 31-dec-2002 2 \ VENDOR_STRING=80FB214D SIGN="035D F2C4 A9D1 4187 7A0C B152 \ 0340 2432 A454 DE01 AB02 1454 5DDE 8689 7907 DA72 4586 7236 \ DB19 9A20 2480" INCREMENT rfde_wireline agileesof 2.0 31-dec-2002 2 \ VENDOR_STRING=80FB214D SIGN="000A 0F2D C23B 31A0 54B1 6556 \ 89BA 6800 686A 4B62 4303 4F32 6864 C91A E427 8572 3EF5 BC08 \ 7DF2 0B79 55B0" from your RFDE license file to your existing ADS2002 license.lic file. You can then use the lmreread command to notify your license server to reread the license file and enable the new licenses: lmutil lmreread -c ..\license.lic Remember to read the “Installing RFDE” manual for more detailed installation instructions. RFDE LICENSE INSTALLATION PROCEDURES ------------------------------------- 1. Save the license.lic attachment to a file on your machine. If you received the files in a Windows PC, make sure that no hidden characters were added to the file by the windows application (see ADS2002C installation manual’s Appendix A for troubleshooting instructions) 2. Place the license.lic file on the license server, and edit the SERVER and VENDOR lines: The license server's host ID is specified on the SERVER line in your license.lic file. If you have more than one SERVER line, you need to follow steps 2 through 4 on each of the license servers. If RFDE is installed on the license server, you can place the license.lic in the licenses sub-directory of the RFDE installation directory. For example: /apps/RFDE/licenses/license.lic 3. Once you have the license.lic file in place on the license server, verify the correctness of the information on the SERVER and VENDOR lines. The SERVER line must contain the hostname of the license server and its host ID. For example: SERVER joshua 80fb214d We often send the license.lic file with hostname set to 'unknown'. This MUST be changed to the correct hostname. Optionally, you may want to specify a TCP port for the license server to listen to for requests. If a TCP port is not specified, as in the example above, FLEXlm will default to the first available port in the range 27000 to 27009. To specify a TCP port, modify the SERVER line as follows: SERVER joshua 80fb214d 27005 In this example, the TCP port is set to 27005. The VENDOR line controls which vendor daemon will be started. It must contain the name of the vendor daemon. For example: VENDOR agileesof As long as the vendor daemon exists in the same directory that lmgrd is started from, this is sufficient. If you have placed the agileesof daemon executable in a different location, then enter the full path as follows: VENDOR agileesof /apps/RFDE/licenses/bin/agileesof Be sure to specify the actual location on your license server. 4. Once the information on the SERVER and VENDOR lines is correct, start the FLEXlm license manager on the license server machine. For example, cd /apps/RFDE/licenses/bin ./lmgrd -c ../license.lic -l ../adsflex.log In this example, the lmgrd supplied with RFDE is started. The path to the license.lic file is specified using the '-c' option and a log file is started using the '-l' option. You MUST use a version of lmgrd that is equal to or greater than the version of agileesof. You can check the versions of lmgrd and agileesof as follows: cd /apps/RFDE/licenses/bin ./lmgrd -v ./agileesof -v The latest version of lmgrd can be downloaded from the Globetrotter Software web site (see the URL in the More Help section below). After starting lmgrd, wait about 10 to 15 seconds and then look at the contents of adsflex.log. You should not see any errors and you should see that agileesof started successfully and has enabled the licenses contained in your license.lic file. Please see Chapter 3 of the RFDE Installation Guide for a way to automate the startup of lmgrd. 5. Before you run RFDE. Any machine that will run RFDE (client) must be able to locate the license server. Continuing with the examples above, the license server is named joshua. If no TCP port was specified on the SERVER line, set the following environment variable: [Korn/Bourne Shell] AGILEESOF_LICENSE_FILE=@joshua export AGILEESOF_LICENSE_FILE [C Shell] setenv AGILEESOF_LICENSE_FILE @joshua If a TCP port was specified on the SERVER line, set the environment variable as follows: [Korn/Bourne Shell] AGILEESOF_LICENSE_FILE=27005@joshua export AGILEESOF_LICENSE_FILE [C Shell] setenv AGILEESOF_LICENSE_FILE 27005@joshua You will want to use the actual TCP port number you specified on your SERVER line. Note: AGILEESOF_LICENSE_FILE will override any settings specified by the environment variable LM_LICENSE_FILE. The RF Design Environment system environment variable, ADSPKG, should be set to identify the RFDE product you purchased. This setting will correspond to the codeword in your license file. For more information about codewords and license files, see “Setting Up Licenses” in your “RFDE Installation” manual. You can set ADSPKG to the value corresponding to your RFDE product: RFDE Product ADSPKG Value RFDE Wireless Pro rfde_wireless RFDE Wireline Pro rfde_wireline RFDE Premier rfde_premier RFDE Premier+ rfde_premier_plus To set ADSPKG, do so in the shell or the Cadence environment using the appropriate value: Set the shell environment variable: For C-Shell, set ADSPKG in the file $HOME/.cshrc or enter the command: setenv ADSPKG For Bourne or Korn Shell, set ADSPKG in the file $HOME/.profile or enter the command: export ADSPKG= ----------------------------- NOTE ------------------------------------ When setting the shell environment variable from the command line, be sure to set it in the same terminal window in which you will run RFDE, and set it prior to starting RFDE. FOR MORE INFORMATION REFER TO THE “INSTALLING RFDE” MANUAL ----------------------------------------------------------------------- 6. You are now ready to run RFDE. COMMON PROBLEMS --------------- If you are having trouble after following the procedure above, please check the following: o Check the adsflex.log file on the license server for errors. o Be sure you have set correctly the HPEESOF_DIR, AGILEESOF_LICENSE_FILE, ADSPKG, CLS_CDSD_COMPATIBILITY_LOCKING, CDS_LICENSE_FILE, CDS_INST_DIR environment variables, as well as the paths to the ADS2002C and CADENCE installation directories (see the ADS2002C and RFDE installation manual for more detailed instructions) o Attempt to checkout the 'ads_schematic' license using the chksec utility supplied with ADS2002C or the 'rfde_XXXX' license using the chksec utility supplied with RFDE: For ADS2002C cd $HPEESOF_DIR/licenses/bin chksec -d -c 27005@joshua ads_schematic For RFDE cd /licenses/bin chksec -d -c 27005@joshua ads_schematic Be sure to use the TCP port number and hostname of your license server. Alternatively, you can specify the full path to your license.lic file as in: chksec -d -c /apps/ads2002C/licenses/license.lic ads_schematic The output will contain extra debugging information and can be very helpful in determining what the problem is. If you are unable to determine the problem, save the output from chksec as follows: chksec -d ads_schematic > csout.txt and send csout.txt, along with your license.lic file, to Agilent EEsof EDA Technical Support: eesof_support@agilent.com MORE HELP --------- ADS2002C Installation Guide, Chapter 4 http://contact.tm.agilent.com/tmo/eesof/docs/ RFDE Installation guide, Chapter 3 http://contact.tm.agilent.com/tmo/eesof/docs/ Technical Support Knowledge Center http://contact.tm.agilent.com/tmo/eesof/support/ Technical Support http://contact.tm.agilent.com/tmo/eesof/assist/contact.html Globetrotter Software http://globetrotter.com/flexlm/lmgrd.shtml (latest lmgrd) http://www.globetrotter.com/manual.htm Rev.11252002