Guest

Cisco License Manager

Release Notes for Cisco License Manager, Release 3.2

  • Viewing Options

  • PDF (239.5 KB)
  • Feedback

Table Of Contents

Release Notes for Cisco License Manager Release 3.2

Contents

Introduction

System Requirements

Server Requirements

Commercial Database Server Requirements

Client Requirements

Devices Supported

Third-Party Software Included

Related Documentation

New Software Features in Release 3.2

Installation Notes

Limitations and Restrictions

Important Notes

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

Caveats

Open Caveats

Resolved Caveats

Resolved in Cisco License Manager Release 3.2.6

Resolved in Cisco License Manager Release 3.2.5

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

Troubleshooting

Documentation Updates

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco License Manager Release 3.2


December 24, 2013

Contents

Introduction

System Requirements

Related Documentation

New Software Features in Release 3.2

Installation Notes

Limitations and Restrictions

Important Notes

Caveats

Troubleshooting

Documentation Updates

Obtaining Documentation, Obtaining Support, and Security Guidelines

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:

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

System Requirements

Make sure that your system meets the Cisco License Manager server and client requirements described these sections:

Server Requirements

Commercial Database Server Requirements

Client Requirements

Devices Supported

Third-Party Software Included


Note For network and port requirements, see the User Guide for Cisco License Manager.


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.

Table 1 Server Software and Hardware Requirements 

Requirement Type
Minimum Requirements

Processor

x86-based processor, 1-GHz minimum (Solaris excluded)

SPARC platform-based processor, 250-MHz minimum (Solaris 1/13 release only)

Software

Operating system:

Windows Server 2008 R2 Enterprise Edition, 64 bit

Windows Server 2003 R2 Standard Edition, 32 bit

Windows 7 Professional, 32 bit and 64 bit

Windows XP Professional, 32 bit

Solaris 10

Red Hat Linux Enterprise 5

RAM

2 GB for Windows (2 GB for Solaris and Linux)

Disk

750 MB



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 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.

Table 2 Client Workstation Software and Hardware Requirements 

Requirement Type
Minimum Requirements

Processor

x86-based processor, 1-GHz minimum (Solaris excluded)

SPARC platform-based processor, 250-MHz minimum (Solaris 10 only)

Software

Operating system:

Windows Server 2008 R2 Enterprise Edition, 64 bit

Windows Server 2003 R2 Standard Edition, 32 bit

Windows 7 Professional, 32 bit and 64 bit

Windows XP Professional, 32 bit

Solaris 10

Red Hat Linux Enterprise 5

RAM

1GB

Disk

200 MB



Note Depending on the number of Cisco devices in your network, you might need to exceed the minimum hardware requirements listed in Table 2.


Devices Supported

Table 3 lists the supported Cisco devices and the corresponding software release.

Table 3 Supported Devices and Cisco Software Release 

Device
Cisco Software Release

Cisco 1861 Integrated Services Router

Cisco IOS Release 12.4(11)XW

Cisco 1900, 2900, 3900 Series Integrated Services Routers G2 (modular)

Cisco IOS Release 15.0(1)

Cisco 2811, 2821, 2851, 3825, and 3845 Integrated Services Routers (modular)

Cisco IOS Release 12.4(15)XY

Cisco ACE Application Control Engine Module

Release 3.0.0A1(3)

Cisco Application eXtension Platform (AXP)

Release 1.5

Cisco AS5350XM and AS5400XM Universal Gateways

Cisco IOS Release 12.4(15)XY

Cisco ASA 5500 Series Appliances

Cisco ASA Release 8.2 to 8.4

Cisco ASR 1001 Aggregation Services Routers

Cisco IOS XE Release 3.2S

Cisco ASR 901 Aggregation Services Routers


Note License transfer/Revoke license is not supported on Aggregation Services Routers


Cisco IOS XE Release 15.3(2)S

Cisco ASR 903 Aggregation Services Routers


Note Device does not support License agent communications. Device has to be added via Telnet/SSH only.


Cisco IOS XE Release 3.11.0S

Cisco ASR 9000 Aggregation Services Routers

Cisco IOS XR Release 3.9

Cisco C860 and C880 Integrated Services Routers (fixed)

Cisco IOS Release 12.4(15)XZ

Cisco Catalyst Blade Server (CBS) 3100 Series Switches

Cisco IOS Release 12.2(35)SE

Cisco Catalyst 3750-X Switch family

Cisco IOS Release 12.2(53)SE2

Cisco Catalyst 3560-X Switch family

Cisco IOS Release 12.2(53)SE2

Cisco Catalyst 3750-E Switch family

Cisco IOS Release 12.2(35)SE

Cisco Catalyst 3560-E Switch family

Cisco IOS Release 12.2(35)SE

Cisco Catalyst 4500E Series Switches

Cisco IOS XE Release 3.1.0SG

Cisco Catalyst 4500 Switches

Cisco IOS XE Release 3.2 SG

Cisco Catalyst 6500 Series Firewall Services Module

Release 3.1

Cisco ME 3600X Series Ethernet Access Switches

Cisco IOS XE Release 15.3(2)S

Cisco ME 3800X Series Ethernet Access Switches

Cisco IOS XE Release 15.3(2)S

Cisco Nexus 5000 family

Cisco Nexus 5000 NX-OS Version 5.1

Cisco Nexus 3000 family

Cisco Nexus 3000 NX-OS Version 5.0(3)

Cisco Nexus 7000 Family of Multilayer Switches

Cisco Nexus 7000 NX-OS Version 5.0

Cisco RFGW-DS384

Cisco IOS Release 15.0(02)SQA, 15.0(02)SQA2 and Cisco IOS Release 15.0(2)SQB1

Enhanced EtherSwitch Service Modules for Integrated Services Routers (ISRs)

Cisco IOS Release 12.2(52)SE

Cisco MDS 9000 Family of Multilayer Switches

Cisco SAN-OS Release 3.3.x and Cisco MDS 9000 NX-OS Release 4.1.1

Cisco uBR10000 Universal Broadband Routers (3G 60 x 60 V and 20 x 20 line-cards/products)

Cisco IOS Release 12.2(33) SCH1/SCH

Cisco uBR10012 Performance Routing Engine 5


Note Device does not support LA based protocol. Device with 3gSPA/PRE5 has to be added via Telnet/SSH only.


Cisco IOS Release SCH1/SCH

Cisco 3Gbps Wideband Shared Port Adapter

Cisco IOS Release SCH1/SCH

Cisco Unified Communications 500 Series for Small Business

Cisco IOS Release 12.4(11)XW6

Cisco Unity Express Network Modules

Release 7.1.1

Cisco XR 12000 Series Routers

Cisco IOS XR Release 3.6


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 

Document
Location

Home page for Cisco License Manager documentation (all releases)

http://www.cisco.com/en/US/products/ps7138/tsd_products_
support_series_home.html

Release Notes for Cisco License Manager

http://www.cisco.com/en/US/products/ps7138/prod_release_notes_list.html

Finding Documentation for Cisco License Manager

Adobe Acrobat PDF on SDK CD

http://www.cisco.com/en/US/products/ps7138/products_
documentation_roadmaps_list.html

User Guide for Cisco License Manager

http://www.cisco.com/en/US/products/ps7138/products_user_
guide_list.html

Java API Reference Guide for Cisco License Manager

Adobe Acrobat PDF on SDK CD

http://www.cisco.com/en/US/products/ps7138/products_
installation_and_configuration_guides_list.html

For 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.html

White 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:

The Right to Use License Report displays the right-to-use (evaluation) licenses. You can filter this report by device or by feature.

Installation Notes

Cisco License Manager Release 3.1 and later releases 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.

CSCub07356

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.

CSCsl40582

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.

CSCtx25981

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.

CSCuc21572

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.

Important Notes

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

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:

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 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

Resolved 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.

CSCua28303

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.

CSCua38108

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.

CSCub10426

Symptom: Scheduled discovery is not running periodically.

Condition: If any scheduled discovery ends up in errors, then the subsequent runs are suppressed.

Workaround: Currently, there is no workaround. You can schedule a new run manually.

CSCub36454

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.

CSCue47800

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.

CSCue52785

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.

CSCue75718

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.

CSCue93959

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.

CSCuh78414

Symptom: clm_import is failing with NPE errors.

Condition: On starting with a fresh inventory_DB and invoking clm_import results in no objects being imported.

Workaround: Use backup and restore procedures to copy data across.

CSCui23647

Symptom: Install wizard does not list packages if client is already installed.

Condition: If CLM client is already installed on Solaris, and if you invoke the installer, the install wizard does not show package selection option for CLM server.

Workaround: Currently, there is no workaround.

CSCui23644

Symptom: Linux: The existing client installation is not detected by the install wizard.

Condition: If CLM client is already installed on Linux, and if you invoke the installer, the installer does not detect CLM client.

Workaround: Currently, there is no workaround.

CSCul74167

Symptom: Silent install on Windows is not working.

Condition: User attempts to run installer by providing a properties file, which forces Installer Anywhere to run in console mode instead of default GUI mode.

Workaround: Install using GUI mode.

CSCue75718

Symptom: Sub device on ASA is not being detected.

Condition: ASA device can have many modules, which are not supported by CLM.

Workaround: Currently, there is no workaround.

CSCuh35216

Symptom: Retry tries license retrival though failure is only polling.

Condition: When attempting a get License for a device, such as RFGW, if the license poll fails and user re-attempts the Retry the Get Lic from the Job status window, it can lead to potential loss of License/PAK count and hence swift throws an error.

Workaround: Instead of retrying failed ones, user can right-click on failed line card and do a poll license.

CSCtc13239

Symptom: To remember transport methods used for the latest device creation.

Condition: Device credentials and discovery method need to be provided at the time of adding or discovering the device.

Workaround: Currently, there is no workaround.

CSCul45640

Symptom: All CLM utilities get stuck when msg clm server is not up.

Condition: CLM server is shut down.

Workaround: Currently, there is no workaround.

CSCul88780

Symptom: Global password change window reports success even if it fails.

Condition: Shut down the CLM server and restart

* Log into the GUI as admin user and when system prompts to purge any running jobs, click Yes to terminate background processes and locks.

Now attempt the Global password changes for devices.

* If device connectivity check still shows that device is manually not reachable, update the password from the device properties > Connection Method1 tab

Workaround: When you are working on a device with multiple line-cards, for e.g. polling, the operation causes the device to be locked preventing global password change.

CSCtx25981

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.

CSCty18582

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.

CSCty18636

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.

CSCty18650

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.

CSCtx83583

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.6

The caveats in this section are resolved in Cisco License Manager Release 3.2.6 but might be open in earlier Cisco License Manager releases.

CSCuc13196

Getting remote connection problem error with ssl enabled.

CSCuj30717

Adding license annotation for Extension license on 3G spa fails.

CSCul13572

Win: Unable to connect after installation.

CSCuj59597

Evaluation license shown as permanent in device report for ASR903.

CSCuj56198

Installing client first then server installs both server and client pkgs.

CSCul93147

If client alone installed not able to connect to SSL enabled server.

CSCul17043

Win: With SSL enabled unable to connect to CLM server.

CSCul37917

Sol and Linux: Getting remote connection error with SSL enabled.

CSCul37930

Win: Log file settings are not proper for server-wrapper.log.

CSCul93297

Sol: Installer problem with client alone installed on Solaris.

CSCul93340

Linux: Existing client install not getting detected on Linux.

CSCul88745

SSL timeout value needs to be changed to match max value of SPA device.

CSCul88858

CLM reports unknown error for Permission ticket core parse failed error.

CSCum20300

Sol: Install path dialogue is made read only in the latest build.

Resolved in Cisco License Manager Release 3.2.5

The caveats in this section are resolved in Cisco License Manager Release 3.2.5 but might be open in earlier Cisco License Manager releases.

CSCue91580

Simultaneously polling 5 to 7 RFGW line cards are failing consistently for one card.

CSCuf65514

The interchange the slot-device module is not updated.

CSCuf73484

Polling lic fails but status displays "succeeded" in the device property field.

CSCug82603

The tftp server does not start after CLM is installed because the tmp directory is missing.

CSCug88507

The license expiry type that is displayed is permanent for evaluation licenses.

CSCuh10878

The device type is wrongly displayed for PABU devices.

CSCuh19090

The auto-discovery schedule window toll tips are incorrect.

CSCuh19451

Unspecified problem error message for some frequncy values in AD.

CSCuh50103

An unknown error detected message during polling of rfgw.

CSCuh60482

Change the default log level to ERROR for Jetty and restrict the log size.

CSCuh90906

If EULA is accepted by device without a prompt, the license tranfer fails in CLM.

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.

CSCua04880

Some unexpected packet received error is displayed on the TFTP server.

CSCub39974

Some unexpected packet received error is displayed on the TFTP server.

CSCub42286

Existing license comments are not displayed in CLM License properties.

CSCub50536

DS384: shows as undeployed for licenses installed from PAK.

CSCub60365

log4j related messages are seen on executing DeviceImport.sh and clm_import.msg.

CSCub60381

Deploying same license from clm displays as success, where as the device gives error.

CSCub60394

Sub device login credntials should not be modified for rfgw.

CSCub49860

RMA Device operation is failing for all device families.

CSCuc00759

License count is not displaying for evalutaion licenses.

CSCuc00784

License type is shown as permanent in device report for Ultra.

CSCuc01274

Windows on LHS of instaler shows install progress in the background.

CSCuc97161

ASA's running 8.3 and 8.4 are required to be supported by CLM.

CSCud06517

All the exisisting data lost after instaling the path.

CSCud14258

Redeploing already deployed license givies uncaught exception.

CSCud48530

Unknown error detected given for Old Permission Ticket error in device.

CSCud49693

Rehost information is not deleted when the device is deleted and readded.

CSCue47575

Change all reference to 3.2.4.

CSCue53551

Genric error message is displayed for the swift RT format error.

CSCue54309

TFTP errors seen during RT transfer for RFW line cards.

CSCue54315

Start time is displayed as blank for discovery operation end message.

CSCue56822

Incorrect version information is displayed for ASA device running 8.3.

CSCue57077

tftp failure in RT transfer is not handled properly for RFGW.

CSCue61552

The complete comment is not displayed if the length of the comment is more than 65 characters.

CSCue70357

CLM license comments are not displaying when a device is added using http.

CSCue75585

CLM gives the error message "null" when polling fails because of dc tftp failure.

CSCue83660

Device gets detected wrongly in case of tftp reachability issue.

CSCue95245

Missing Device credential error during license transfer.

CSCuf20400

Software Version information displays incorrectly for rfgw.

CSCtc81258

Unknown error detected msg displays while annotating lic without any string.

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.

CSCua06397

TFTP files must be cleared from the "tmp" directory.

CSCua28336

The time zone is wrongly displayed in audit log for IST.

CSCua38708

Poll License does not work on some of the Cat4k devices.

CSCua16103

Log4j warning messages are seen on execution clm_export.bat.

CSCua77730

Powerkey and DVB licenses are optionally supported on the RFGW line card.

CSCua80423

Discovery, Check Device, and poll operation takes more time for DS384.

CSCua80959

log4j warning messages are seen on execution of DeviceImportCSV.bat.

CSCua92566

Adding a device from the getting started page gives a wrong error.

CSCub04825

Transfer wizard summary: source and destination are not displayed completely.

CSCub22700

License transfer is failing with the error code 4704.

CSCub23028

Device type showing wrongly for Nexus 5000 and 3000 devices.

CSCub42350

Users will not be able to install CLM to non default loc with choose option.

CSCub73849

Device is marked as unreachable after successful check device operation.

CSCub76785

License count is not displayed for evaluation license in DS-384 card.

CSCub76452

License agreement is not shown in lnx and Solaris installers.

CSCub76505

Client gives rcp error when client alone installed on sol and lnx.

CSCuc00746

Device type shown as Unknown for Ultra.

CSCuc21743

An unknown platform error displays during RMA operation.

CSCuc18620

Linux installer gives the wrong disk space requirement.

CSCuc18609

Linux: CLM client cannot be launched after installation.

CSCuc13722

sol: after installing sol, user is not able to choose pkg next install.

CSCub82016

(sol and lnx) installer does not recognize the instaled clm client.

CSCty18247

Cannot open the zip file that is generated using the utility clm_ziputil.bat.

CSCty18901

The CLM home directory information is shown as incomplete in the "clm_stop.bat" log.

CSCty18951

Same groups can be created by adding leading and trailing spaces.

CSCty44429

To avoid having issues with the installer, do not install the CLM client and server separately.

CSCtz57780

CLM needs to support the DS-384 line card.

CSCtz98931

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.

CSCtd26763

Misleading message found in license obtainment operation.

CSCtq19363

Cisco License Manager throws error code 3005 with NX-OS 5.x software.

CSCtr54502

The Cisco License Manager client cannot communicate with the Cisco License Manager server in rare situations.

CSCtu98863

Cisco License Manager Release 3.1 is affected by the TFTPUtil GUI GET Request Directory Traversal Vulnerability.

CSCtw77663

The banner broke Cisco License Manager's telnet/SSH parsing if "hostname" is used.

CSCtx09644

Telnet hostname bug for non-IOS platforms.

CSCtx44368

Cisco License Manager doesn't allow users other than the admin to set the proxy username and password.

CSCtx44548

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.

CSCts16223

Right after installing licenses, the show license file command returns no license information on UBR10K and Cisco License Manager throws an Uncaught exception.

CSCts19573

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.

CSCts30314

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.

CSCtq19363

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

CSCtq85072

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.

CSCtr33352

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.

CSCtr67823

XML Parser error when rehosting a license on UBR10K device

CSCtr71268

Resend or redeploy license to UBR linecard failed due to CLI output changes.

CSCtr80737

Not able to add quantity with counted licenses into the obtain license list.

CSCtr73934

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.

CSCtq27917

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.

CSCtb83670

When moving 60,000 devices from one group to another group, the operation did not complete even after 24 hours.

CSCtc04008

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.

CSCtc39162

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.

CSCtc50757

The subdevices are not presented in the device explorer.

CSCtc65618

When the user obtains a new URLF license, the license status shows deployed while the licenseline under this license shows undeployed.

CSCte17851

The DB restore script does not restore all poll settings for License, EOS/EOL, and PSIRT.

CSCte29073

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).

CSCte36702

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.

CSCte84293

The Check License Portal function does not handle the proxy server correctly.

CSCtf19162

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.

CSCtb79266

The Cisco License Manager GUI client content area is not updated after an error window or message window is closed.

CSCtc32840

Cisco License Manager shows incorrect device hierarchy for multi-LC UBR10k when they are discovered using HTTP/HTTPS transport.

CSCtc73669

The Add button in the Get License Assistant is disabled.

CSCtg18565

Device type shown as "UNKNOWN" for SM-SRE module.

CSCtg34051

See "Deployment Module Internal Error" due to "Dynamic License Storage."

CSCtg49049

TS:MF: Unable to discover devices via HTTPS for Cisco License Manager.

CSCtg51417

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.

CSCsq27660

The Cisco License Manager GUI takes a long time (about an hour) to update the view when the Refresh button is clicked.

CSCso70310

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."

CSCso98199

For valid PAK objects, the Perl API write_paks gives the error "Input is null or 0 length."

CSCsv83394

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.