Table Of Contents
Release Notes for Cisco License Manager Release 3.1
Updated May 17, 2011
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:
•Application programming interface (API)—A programmatic interface that enables client programs to invoke functions implemented on the back-end server, allowing you to integrate Cisco License Manager into your systems. You can also use the API to write custom programs to perform your licensing tasks using Java.
•GUI—A standalone Java application that provides an end-user interface that you can use to invoke functions implemented on the back-end server.
Note You can use the Cisco IOS CLI to license your devices. For more information, see your device documentation.
Cisco License Manager includes these features:
•Intuitive and easy-to-use GUI
•Maintenance of an up-to-date inventory of deployed licensed features on the network through notifications and optional polling
•Simplified license transfers from one device to another
•Agentless device communication using Secure Shell (SSH) or Telnet
•Improved detailed license reporting to help with audit compliance
•Full-functionality Java software developer kit (SDK)
•Enhanced security with role-based access control and per-user access control lists for the managed network devices and PAKs
•Completely automated license management through a simple rule-based policy interface
•Troubleshooting capabilities and X.733-based alerts
Make sure that your system meets the Cisco License Manager server and client requirements described these sections:
Note For network and port requirements, see the User Guide for Cisco License Manager.
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 Depending on the number of Cisco devices in your network, you might need to exceed the minimum hardware requirements listed in Table 1.
Commercial Database Server Requirements
Cisco License Manager Release 3.1 supports Oracle 11g as an external commercial SQL2 database.
Table 2 lists the software and hardware requirements for the Cisco License Manager client workstation.
Note Depending on the number of Cisco devices in your network, you might need to exceed the minimum hardware requirements listed in Table 2.
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.22 in both the server package and the client package.
Table 4 lists the Cisco License Manager Release documentation.
New Software Features in Release 3.1
These features were introduced in Cisco License Manager Release 3.1:
•Automatic upgrade—Cisco License Manager Release 3.0 or 3.012 automatically upgrades to Release 3.1. The upgrade preserves the existing database information and all user settings and install the new version with the existing user parameters and database information. The old database is converted to the new format.
•Counted licenses—Cisco License Manager allows you to enter the number of counted licenses to install if they are additive or part of a partial fulfillment PAK.
•RMA Device Assistant enhancement—A return merchandise authorization (RMA) license transfer between two devices with the same IP address is supported. The user does not need to know the unique device identifier (UDI) of either device because Cisco License Manager provides that information from previous discoveries.
•Device TACACS+ support—When Cisco License Manager uses Telnet and Secure Shell (SSH) as connection methods, it can discover devices that are configured to be authenticated through a TACACS+ server.
•Cisco License Manager client can connect to the server through a firewall—The Cisco License Manager client can connect to the Cisco License Manager server through a firewall when the Clm.properties file is modified.
•Export reports in .csv format—You can export reports to a .csv file and then import the information into another application, such as Microsoft Excel.
•Device seed file—Cisco License Manager can discover devices by importing an ASCII seed file that contains the necessary information.
•External database support—You can use a commercial Structured Query Language (SQL) database instead of using the free database that ships with Cisco License Manager.
•Dual NIC support—Cisco License Manager can be configured with dual network interface cards (NICs). In this configuration, one NIC connects to the internal management network while the other NIC connects (probably through a firewall) to the Internet to communicate with the Cisco Product License Registration Portal.
•Global password change—Cisco License Manager can globally change usernames and passwords by device group.
•Sensitive data encryption—Sensitive information, such as passwords and access control, is encrypted.
•Enable password controls reinstated—The capability to enter the enable password during the entry of the username and password is restored.
•Cisco License Manager Release 3.1 does not support sharing the same external Oracle database with multiple Cisco License Manager servers.
•The LAN Management Solution (LMS) and Cisco License Manager do not function correctly if they are installed on the same machine.
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: If you click Cancel during installation, the incomplete installation prevents Cisco License Manager from being uninstalled or reinstalled normally. Specifically, if you try to uninstall, you see a message that Cisco License Manager is not installed, and if you try to reinstall, you see a message that Cisco License Manager is already installed.
Condition: Clicking Cancel during installation.
To avoid the problem, do not click Cancel during installation. Let the installation complete, then uninstall normally, and reinstall, if desired.
If clicking Cancel has caused an incomplete installation, follow the steps below to remedy the problem, and then reinstall.
1. Remove Cisco License Managerfrom 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.
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.
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:
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:
•Feature-based information is displayed in the Device Properties window, as shown in Figure 1. All the licenses for a feature are grouped under the feature name, and information about the total usage left and the feature state is displayed.
Figure 1 Feature-Based Representation
•License-based information is displayed in the Manage Licenses window by grouping all the license information polled from a device under the Others category, as shown in Figure 2. For licenses obtained through a PAK, the information is grouped under the PAK name.
Figure 2 License-Based Representation
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
There are no noteworthy open caveats in Cisco License Manager.
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.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.
For troubleshooting information, see the User Guide for Cisco License Manager or the online help in the GUI application.
For the latest versions of all Cisco License Manager documentation, go to:
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:
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-2011 Cisco Systems, Inc. All rights reserved.