Troubleshooting for USB Hardware device activation and licensing

• Ensure that the last 5 hexadecimal digits of the serial number that is etched on the USB hardware device match the serial number in the file name of the update file you are applying. Sometimes the etched number is hard to read. If you are unable to read the etched serial number, IBM® support can assist you with an alternative method of obtaining the serial number.
• Ensure that the hardware device is recognized by your Linux® system by plugging in the device and issuing the lsusb command. If the device is available, you see an entry that shows "Rainbow Technologies Inc".

• You try to apply an update file with one serial number to a USB hardware device with a different serial number.
• You try to update a USB hardware device from a client machine that is connected to a product license server that has no local USB Hardware device

When you are starting ZD&T, (awsstart) you get any of the following messages at the Linux terminal that indicates a failure to get a license:

• Error: Failed to get license.
        Return code: 312

• Error: Unable to get expected 
        license: xxxx

  or

  Error: Unable to locate expected 
        license: xxxx

• AWSEMI315E zPDTA License Unavailable 
        for CPU 0
  AWSEMI005I Waiting for 1090 license

• CPU Address Out Of Range

• SFNTGetLicense failed. 
        Return code: 312

• The local USB Hardware device is not plugged in properly. Attempt to “reseat” the USB Hardware device. Unplug the device for 15 seconds, then reinsert it.
• The correct update file is not applied to the matching USB Hardware device, or it did not apply successfully.
  • Ensure the update file that is requested and applied has the same serial number within the file name as the serial number of the USB Hardware device. Serial numbers can be hard to read. Look carefully.
  • Ensure the SecureUpdateUtility -u or Z1091_token_update -u command responded with a "Success" message.
• The requested license type is not correct.
  • Validate that if your device map includes the cpuopt zvm_couplingfacility directive, your USB hardware key includes sysplex enabling licenses. If no sysplex license is available, your device map cannot enable sysplex operation.
  • Validate that if your device map includes the RDTSERVER= directive or you have an RDTSERVER environment variable set to enable participation in a Rational® Token licensing system, your USB hardware key includes token enabling licenses. If token enabling licenses are not available on your USB hardware key, your ZD&T instance cannot participate in a Rational Token licensing system.
• The system clock is incorrect on the system with the USB hardware device plugged in to it. Ensure that the system clock is correct. Never set the system clock to a future date or time when the USB hardware key is plugged in or you will damage the USB hardware key.
• You are trying to use a local USB Hardware device, but your client configuration points to a product license server
  • From a Linux terminal that is running as root, enter the clientconfig command that is found in /usr/z1090/bin. Ensure the License ContactServer is localhost if you are attempting to use a local USB. No other fields need be completed.
• The /usr/z1090/bin/sntlconfig.xml file is not readable by the programs that need it. Verify that /usr/z1090/bin/sntlconfig.xml is "world readable". If it is not, use chmod to change the permission bits to 644.
• You do not have the correct type of USB Hardware Device.
  • Perform the following command from a Linux terminal that is running as root:

    rpm -qa | grep z109

    If Rational Development and Test Environment for z System is properly installed, you should see an rpm of the form

    z1091-xxx and not z1090-xxx

  • Ensure the USB Hardware device that you are using is a Rational Development and Test Environment for z System Hardware device, and not a z1090 hardware device. A z1090 hardware device has a metal cable with a plastic tag attached to the end of the device. A z1091 hardware device does not.

• You do not have connectivity from the instance that is performing the awsstart to the product license server.
  • Enter a UIMCHECK on the client instance to verify whether there is proper connectivity. You see the message

    The remote QUERY command executed successfully

  • If this procedure does not complete successfully, try the following procedure.
    • From a Linux terminal that is running as root, enter the clientconfig command that is found in /usr/z1090/bin. Ensure the License ContactServer is the IP address of the product license server, that the License PortNumber is 9450, and that License ipv6 is yes or no as is appropriate for your installation.
    • From a Linux terminal on the instance that is running ZD&T, enter a ping to the IP address configured as the license server. If the ping command fails, you have an IP connectivity problem or the server is not started.
      • Ensure that the server was started once by a non-root ID with the uimserverstart command.
    • If you believe that there is connectivity to the network, from a Linux terminal that is running as root, check the firewall configuration by entering the following command

      iptables -L -n 

      Ensure ports 9450 and 9451 are allowed.
    • If this installation is a newly installed product license server, check the firewall configuration on the product license server. If security is being used on the product license server, ensure that the sentinel configuration file on the server allows for the IP address of the client. This file is in

    • /opt/safenet_sentinel/common_files/
                   sentinel_keys_server/sntlconfigsrve.xml

      For more information, see paragraph 8.4.2, “Security” in chapter 8 of the zPDT® Guide and Reference.

/opt/safenet_sentinel/common_files/sentinel_keys_server/loadserv 
      restart

When you are starting Rational Development and Test Environment for z Systems®, (awsstart) you get the following messages at the Linux terminal that indicate an expired license

CPU 0, No Sentinel License Available 65535
Unknown Error Code
CPU 1, No Sentinel License Available 65535
Unknown Error Code
CPU 2, No Sentinel License Available 65535
Unknown Error Code
Expired License. EXP=3/1/2015

AWSEMI315E zPDTA License Unavailable for CPU x

A replacement update file must be obtained from the Rational License Key Center when a license expires, and the update file must be applied to the USB hardware device being used. For more information, see “Steps to get the replacement file” in the ZD&T Activation Guide (SC27-6630).

• Time cheat errors occur when the time stored on the USB hardware device is in the future when compared to the system clock of the Linux system it is plugged into. The USB device stores the latest date of the system clock it sees and will not provide licenses until the Linux system clock matches. Verify that the Linux system clock is correct. Have your system clock set to UTC to avoid errors that are caused by semi-annual time changes. There is no way to inspect the time on the USB key. However, you might wait a short time to see whether the Linux clock catches up to the time stored on the USB key. Do NOT set the Linux clock ahead of the actual time. If you suspect that the time stored on the USB key is in the future, contact IBM support.