 Feedback
|
Table Of Contents
Release Notes for Cisco License Manager Release 3.2
Commercial Database Server Requirements
New Software Features in Release 3.2
Cisco License Manager and the Mozilla Browser
Extra Bytes in License File Received in a Microsoft Entourage Attachment
Device-Specific Display Variation for License Information
Resolved in Cisco License Manager Release 3.2.4
Resolved in Cisco License Manager Release 3.2.3
Resolved in Cisco License Manager Release 3.2.2
Resolved in Cisco License Manager Release 3.2.1
Resolved in Cisco License Manager Release 3.2
Resolved in Cisco License Manager Release 3.1.1
Resolved in Cisco License Manager Release 3.1
Resolved in Cisco License Manager Release 3.0.12
Resolved in Cisco License Manager Release 3.0
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco License Manager Release 3.2
March 14, 2013
Contents
•
New Software Features in Release 3.2
•
Introduction
Cisco License Manager is a software application that assists you in obtaining licenses from Cisco, deploying the licenses to the Cisco devices in your network, discovering the devices, and managing and viewing your inventory of licenses and devices. Cisco License Manager is used with Cisco devices that require Cisco licensing. New or upgraded Cisco devices should be registered, and a product authorization key (PAK) must be provided to obtain licenses from Cisco.
This application provides two external interfaces that enable you to perform several licensing tasks from a central location:
•
•
Note
Cisco License Manager includes these features:
•
•
•
•
•
•
•
•
•
System Requirements
Make sure that your system meets the Cisco License Manager server and client requirements described these sections:
•
•
Note
Server Requirements
Table 1 lists the software and hardware requirements for the Cisco License Manager server. These requirements are also valid if you are installing the server and client on the same host. See the Installation Notes for additional information.
Note
Commercial Database Server Requirements
Cisco License Manager Release 3.1 and later releases supports Oracle 11g as an external commercial SQL2 database.
Client Requirements
Table 2 lists the software and hardware requirements for the Cisco License Manager client workstation.
Note
Devices Supported
Table 3 lists the supported Cisco devices and the corresponding software release.
Third-Party Software Included
Cisco License Manager includes Java Runtime Environment (JRE) 6.0.26 in both the server package and the client package.
Related Documentation
Table 4 lists the Cisco License Manager Release documentation.
Table 4 Product Documentation
Home page for Cisco License Manager documentation (all releases)
http://www.cisco.com/en/US/products/ps7138/tsd_products_
support_series_home.htmlRelease Notes for Cisco License Manager
http://www.cisco.com/en/US/products/ps7138/prod_release_notes_list.html
Finding Documentation for Cisco License Manager
•
•
documentation_roadmaps_list.htmlUser Guide for Cisco License Manager
http://www.cisco.com/en/US/products/ps7138/products_user_
guide_list.htmlJava API Reference Guide for Cisco License Manager
•
•
installation_and_configuration_guides_list.htmlFor Cisco License Manager Release 3.2, use the Java API Reference Guide from Release 3.1.
Online help
In the user interface, click Help to display help in a separate window.
Data sheets
http://www.cisco.com/en/US/products/ps7138/products_data_
sheets_list.htmlWhite papers
http://www.cisco.com/en/US/products/ps7138/prod_white_
papers_list.html
New Software Features in Release 3.2
These features were introduced in Cisco License Manager Release 3.2:
•
Installation Notes
•
•
Limitations and Restrictions
This section describes the limitations and restrictions for Cisco License Manager. Limitations are issues that will not be fixed, and there is not always a workaround. For information about open and resolved caveats, see the "Caveats" section.
•
Symptom: Counted licenses shows as undeployed after license transfer in CLM.
Condition: During "partial" license transfer (re-host), instead of adding up the counts to the existing license feature, it results in a new license line while the old license line shows up as undeployed on the Destination Device.
Workaround: Delete and readd the device; the undeployed license will be cleared in CLM.
•
Symptom: If you click Cancel during installation, the incomplete installation prevents Cisco License Manager from being uninstalled or reinstalled normally. However, if you try to uninstall, you will see a message that the Cisco License Manager is not installed, and if you try to reinstall, you will see a message that Cisco License Manager is already installed.
Condition: Clicking Cancel during installation.
Workaround: To avoid the problem, do not click Cancel during installation. Let the installation complete, uninstall, and then reinstall, if required.
If clicking Cancel has caused an incomplete installation, follow the steps below to remedy the problem, and then reinstall.
On Windows:
1. Remove Cisco License Manager from the Registry. Open a command window and run the appropriate command, depending on the installation:
- Server and GUI client installation:
reg delete "HKLM\Software\Cisco Systems\CLM3.0"
- Server installation only:
reg delete "HKLM\Software\Cisco Systems\CLM3.0\Server"
- GUI client installation only:
reg delete "HKLM\Software\Cisco Systems\CLM3.0\Client"
2. Delete the Cisco License Manager folder.
On Solaris:
1. Remove Cisco License Manager from the registry by running the appropriate command depending on the installation:
- Server and GUI client installation:
pkgrm -n CSCOclm30; pkgrm -n CSCOclm30gui
- Server installation only:
pkgrm -n CSCOclm30
- GUI client installation only:
pkgrm -n CSCOclm30gui
2. Delete the Cisco License Manager folder.
•
Symptom: Telnet lines are not being released by Cisco License Manager for some device families.
Condition: This problem occurs on Cisco 38xx and 39xx Integrated Services Routers.
Workaround: Use SSH instead as Discovery Protocol or Upgrade the IOS image on the router.
•
Symptom: Polling multiple devices at the same time fails randomly for some.
Condition: Polling for multiple devices at the same time, which include UBR/RFGW-DS384 /ASR1001/ and so on at the same time, causes polling failure on some devices randomly.
Workaround: For failed devices, do the polling separately.
•
Symptom: Getting remote connection problem error with ssl enabled.
Condition: Install the server on Windows with ssl enabled b/w client and server. Install only the client on Solaris. When you launch the client on the Windows server, it gives the error remote connection.
Workaround: Copy cacerts file from server or "$CLM_GUI_INSTALL_DIR$/etc/jre/lib/security" on to the client "$CLM_GUI_INSTALL_DIR$/jre/tool/lib/security" folder.
Important Notes
•
•
•
Cisco License Manager and the Mozilla Browser
You might encounter problems when the Solaris or the Linux machine for the user is not properly linked with a Mozilla browser. Cisco License Manager uses the "mozilla" command to bring up the Mozilla browser. The Solaris or Linux environment might support other browsers (such as Firefox and SeaMonkey) that are brought up by other commands.
Users need to create Mozilla softlink to the path of the browser to be used. For more information, see the UNIX command ln -s.
Extra Bytes in License File Received in a Microsoft Entourage Attachment
If you use Microsoft Entourage and receive the license file from Cisco in an e-mail attachment, the license file will contain UTF-8 marking. These extra bytes in the license file cause it to be unusable during license installation. To work around this issue, you can use a text editor to remove the extra characters and then install the license file. For more information about UTF-8 encoding, go to this URL:
http://www.w3.org/International/questions/qa-utf8-bom
Device-Specific Display Variation for License Information
When you poll license information from a device, the information retrieved by Cisco License Manager is shown in two representations:
•
Figure 1 Feature-Based Representation
•
Figure 2 License-Based Representation
For most devices, Cisco License Manager Release 2.2 and later displays feature-based and license-based information as shown in Figure 1 and in Figure 2.
There is, however, a variation in the information display for the MDS9000 (see Figure 3 and Figure 4).
For MDS9000 switches, the current license information for all the features is displayed in the Device Properties window as shown in Figure 3.
Figure 3 Feature-Based License Information for MDS9000
For license-based information in the Manage Licenses window, Cisco License Manager creates a unique license ID for each license file retrieved from the device and displays the license information for the features contained in the license file under this heading, as shown in Figure 4. If licenses are obtained using a PAK, the information is grouped under the PAK name.
Figure 4 License-Based Information for MDS9000
Caveats
Open Caveats
This section describes possible unexpected behavior by Cisco License Manager. All the caveats listed in this section are open in Cisco License Manager Release 3.2.
Because the defect status continually changes, be aware that the list is a snapshot of the defects that were open at the time this release note was issued.
•
Symptom: Cannot delete canceled jobs as the job manager displays the jobs as "Running".
Condition: Start a process, cancel it before it is completed and then delete that process from the "View Job Status" screen once it reaches 100%; the delete process cannot be done.
Workaround: Currently, there is no workaround.
•
Symptom: The CLM sever is in an infinite loop because of an error on the line card.
Condition: Cannot login to DS-384 modules from the main device.
Workaround: The RFGW line cards are in working condition.
•
Symptom: CLM 3.2.2 does not allow spaces in login prompts.
Condition: CLM cannot Telnet/SSH to the managed device when username and password prompts have spaces in TACAS Authentication.
For example:
ABCD Username:
ABCD Password:
Workaround: Currently, there is no workaround.
•
Symptom: RFGW device is not available in Linux servers
Condition: Add RFGW device in Linux server using Telnet, device is not available.
Workaround: Add Device using SSH if network latency is more for the telnet connection.
•
Symptom: After instaling license from PAK, it displays as not deployed.
Condition: Deploy license on the ASA device succesfully using the new PAK, and then go to Manage License, check the License status under the PAK. It still displays the License status as not deployed.
Workaround: Currently, there is no workaround.
•
Symptom: Subdevice on ASA is not detected.
Condition: The submodule on the ASA device, which is taking more time to respond to some of the options, is not detected in CLM.
Workaround: Currently, there is no workaround.
•
Symptom: Model field value wrong for UBR-PRE5.
Condition: Model value for the UBR-PRE5 device is displayed wrongly under the Model column of the Manage Device window.
Workaround: Currently, there is no workaround.
•
Symptom: Telnet lines are not released by CLM for some device families.
Condition: Log in to the device console via PuTTY or any other terminal client. Show all the VTY lines that have a *.
Workaround: Use SSH instead as the discovery protocol or Upgrade the IOS image on the router.
•
Symptom: Cannot remove the CLM package from the Add/Remove Programs list.
Condition: The same version of CLM can be installed multiple times on the same machine by editing the registry. This can lead to loss of reg-key values of earlier installs.
Workaround: Delete CLM_Home and its sub folders.
•
Symptom: The size of the CLM package shows NULL on Windows 7.
Condition: An older version of IA is used when 64-bit Windows is not available. Windows 7 and Windows 2008 use a dedicated 64-bit registry space to store disk required information.
Workaround: Currently, there is no workaround.
•
Symptom: The module shows blank while refreshing the group.
Condition: Refresh the group in manage device; the submodule information becomes blank for the device with the submodule.
Workaround: Refresh the group so that it displays the submodule.
•
Symptom: The server is not configured completely if CLM is installed with the SSL enabled.
Condition: If "configure server" is enabled when "SSL = on" in Clm.properties and the correct password is entered, the installer displays a message that it is not able to connect to a running server or a wrong password has been entered.
Workaround: Turn off SSL and retry the "configure server" program after bouncing the server.
Resolved Caveats
Because the defect status continually changes, be aware that the list is a snapshot of the defects that were open at the time this release note was issued.
Resolved in Cisco License Manager Release 3.2.4
The caveats in this section are resolved in Cisco License Manager Release 3.2.4 but might be open in earlier Cisco License Manager releases.
•
Some unexpected packet received error is displayed on the TFTP server.
•
Some unexpected packet received error is displayed on the TFTP server.
•
Existing license comments are not displayed in CLM License properties.
•
DS384: shows as undeployed for licenses installed from PAK.
•
log4j related messages are seen on executing DeviceImport.sh and clm_import.msg.
•
Deploying same license from clm displays as success, where as the device gives error.
•
Sub device login credntials should not be modified for rfgw.
•
RMA Device operation is failing for all device families.
•
License count is not displaying for evalutaion licenses.
•
License type is shown as permanent in device report for Ultra.
•
Windows on LHS of instaler shows install progress in the background.
•
ASA's running 8.3 and 8.4 are required to be supported by CLM.
•
All the exisisting data lost after instaling the path.
•
Redeploing already deployed license givies uncaught exception.
•
Unknown error detected given for Old Permission Ticket error in device.
•
Rehost information is not deleted when the device is deleted and readded.
•
Change all reference to 3.2.4.
•
Genric error message is displayed for the swift RT format error.
•
TFTP errors seen during RT transfer for RFW line cards.
•
Start time is displayed as blank for discovery operation end message.
•
Incorrect version information is displayed for ASA device running 8.3.
•
tftp failure in RT transfer is not handled properly for RFGW.
•
The complete comment is not displayed if the length of the comment is more than 65 characters.
•
CLM license comments are not displaying when a device is added using http.
•
CLM gives the error message "null" when polling fails beacuse of dc tftp failure.
•
Device gets detected wrongly in case of tftp reachability issue.
•
Software Version information displays incorrectly for rfgw.
•
Unknown error detected msg displays while annotating lic without any string.
•
Missing Device credential error during license transfer.
Resolved in Cisco License Manager Release 3.2.3
The caveats in this section are resolved in Cisco License Manager Release 3.2.3 but might be open in earlier Cisco License Manager releases.
•
TFTP files must be cleared from the "tmp" directory.
•
The time zone is wrongly displayed in audit log for IST.
•
Poll License does not work on some of the Cat4k devices.
•
Log4j warning messages are seen on execution clm_export.bat.
•
Powerkey and DVB licenses are optionally supported on the RFGW line card.
•
Discovery, Check Device, and poll operation takes more time for DS384.
•
log4j warning messages are seen on execution of DeviceImportCSV.bat.
•
Adding a device from the getting started page gives a wrong error.
•
Transfer wizard summary: source and destination are not displayed completely.
•
License transfer is failing with the error code 4704.
•
Device type showing wrongly for Nexus 5000 and 3000 devices.
•
Users will not be able to install CLM to non default loc with choose option.
•
Device is marked as unreachable after successful check device operation.
•
License count is not displayed for evaluation license in DS-384 card.
•
License agreement is not shown in lnx and Solaris installers.
•
Client gives rcp error when client alone installed on sol and lnx.
•
Device type shown as Unknown for Ultra.
•
An unknown platform error displays during RMA operation.
•
Linux installer gives the wrong disk space requirement.
•
Linux: CLM client cannot be launched after installation.
•
sol: after installing sol, user is not able to choose pkg next install.
•
(sol and lnx) installer does not recognize the instaled clm client.
•
Cannot open the zip file that is generated using the utility clm_ziputil.bat.
•
The CLM home directory information is shown as incomplete in the "clm_stop.bat" log.
•
Same groups can be created by adding leading and trailing spaces.
•
To avoid having issues with the installer, do not install the CLM client and server separately.
•
CLM needs to support the DS-384 line card.
•
CLM reports as an unsupported device on 3800 and 3900 device family.
Resolved in Cisco License Manager Release 3.2.2
The caveats in this section are resolved in Cisco License Manager Release 3.2.2 but might be open in earlier Cisco License Manager releases.
•
Misleading message found in license obtainment operation.
•
Cisco License Manager throws error code 3005 with NX-OS 5.x software.
•
The Cisco License Manager client cannot communicate with the Cisco License Manager server in rare situations.
•
Cisco License Manager Release 3.1 is affected by the TFTPUtil GUI GET Request Directory Traversal Vulnerability.
•
The banner broke Cisco License Manager's telnet/SSH parsing if "hostname" is used.
•
Telnet hostname bug for non-IOS platforms.
•
Cisco License Manager doesn't allow users other than the admin to set the proxy username and password.
•
Cisco License Manager Zip Utility fails.
Resolved in Cisco License Manager Release 3.2.1
The caveats in this section are resolved in Cisco License Manager Release 3.2.1 but might be open in earlier Cisco License Manager releases.
•
Right after installing licenses, the show license file command returns no license information on UBR10K and Cisco License Manager throws an Uncaught exception.
•
When revoking a license, if the permission ticket file size is over 6K, certain device types (such as the Cisco 2821 router) frequently time out while copying it through TFTP. This results in the failure of revoking a license.
•
The Clm.properties file is not updated after installation of Linux build Version (Max5): 003.002.001. Cisco License Manager is unable to use the certificate to access the licensing infrastructure.
Resolved in Cisco License Manager Release 3.2
The caveats in this section are resolved in Cisco License Manager Release 3.2 but might be open in earlier Cisco License Manager releases.
•
Cisco License Manager throws error code 3005 with NX-OS 5.x software. Cisco License Manager uses the show license default command, which is no longer supported in NX-OS 5.x on the Nexus
•
Add device with poll license fails with linecard using Telnet or SSH. When using add device to discover a device and check poll license after create, the creation succeeded but poll license failed due to parent device locked.
•
Cisco License Manager should not talk to UBR linecard directly to retrieve device info. Cisco License Manager should talk to RP to collect device information for each linecard instead.
•
XML Parser error when rehosting a license on UBR10K device
•
Resend or redeploy license to UBR linecard failed due to CLI output changes.
•
Not able to add quantity with counted licenses into the obtain license list.
•
Cisco License Manager does not allow rehost the maximum available quantity of licenses. It only allows transfer maximum up to (available quantity-1) licenses at a time.
Resolved in Cisco License Manager Release 3.1.1
The caveats in this section are resolved in Cisco License Manager Release 3.1.1 but might be open in previous Cisco License Manager releases.
•
Creating an administrator password with special characters (such as % in the Windows version and $ in the Linux and the Solaris versions) during installation prevents the administrator from logging in to the system.
Resolved in Cisco License Manager Release 3.1
The caveats in this section are resolved in Cisco License Manager Release 3.1 but might be open in previous Cisco License Manager releases.
•
When moving 60,000 devices from one group to another group, the operation did not complete even after 24 hours.
•
The delete operation for 60,000 devices was not completed even after 35 hours. The Cisco License Manager GUI client does not respond during this time.
•
Cisco License Manager encounters an internal error when trying to log in. During the readDevices test with 500,000 devices in the database, the login process takes a very long time and then Cisco License Manager displays the error.
•
The subdevices are not presented in the device explorer.
•
When the user obtains a new URLF license, the license status shows deployed while the licenseline under this license shows undeployed.
•
The DB restore script does not restore all poll settings for License, EOS/EOL, and PSIRT.
•
Users try to expand the device nodes one-by-one from the top of the list of the Manage License window and find that the node at the bottom will not expand (the scroll bar is at the bottom).
•
Users find that "Active, In Use after Next Reload" is not displayed for a few image licenses after a successful license deployment and polling. If the device is added through HTTP, this information is displayed correctly.
•
The Check License Portal function does not handle the proxy server correctly.
•
Asynchronous APIs are not returning an error for invalid jobGroup and never completes.
Resolved in Cisco License Manager Release 3.0.12
The caveats in this section are resolved in Cisco License Manager Release 3.0.12 but might be open in previous Cisco License Manager releases.
•
The Cisco License Manager GUI client content area is not updated after an error window or message window is closed.
•
Cisco License Manager shows incorrect device hierarchy for multi-LC UBR10k when they are discovered using HTTP/HTTPS transport.
•
The Add button in the Get License Assistant is disabled.
•
Device type shown as "UNKNOWN" for SM-SRE module.
•
See "Deployment Module Internal Error" due to "Dynamic License Storage."
•
TS:MF: Unable to discover devices via HTTPS for Cisco License Manager.
•
TS:MF: Unable to discover devices via SSH for Cisco License Manager.
Resolved in Cisco License Manager Release 3.0
The caveats in this section are resolved in Cisco License Manager Release 3.0 but might be open in previous Cisco License Manager releases.
•
The Cisco License Manager GUI takes a long time (about an hour) to update the view when the Refresh button is clicked.
•
When managing large quantities of devices using CLM, you might see Java exceptions in Cisco License Manager error windows and log files. These Java exceptions include "out of memory error" and "RMI marshalling/unmarshalling error."
•
For valid PAK objects, the Perl API write_paks gives the error "Input is null or 0 length."
•
Creating a device by IP and discovering a device using Telnet or SSH protocols fails for Catalyst 3750-E mixed stacks.
Troubleshooting
For troubleshooting information, see the User Guide for Cisco License Manager or the online help in the GUI application.
Documentation Updates
For the latest versions of all Cisco License Manager documentation, go to:
http://www.cisco.com/en/US/products/ps7138/tsd_products_support_series_home.html
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
This document is to be used with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2007-2012 Cisco Systems, Inc. All rights reserved.
