Cisco Cisco License Manager 3.1
14
Release Notes for Cisco License Manager Release 3.1
OL-13000-05
Caveats
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.
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.
window is closed.
•
CSCtc32840
Cisco License Manager shows incorrect device hierarchy for multi-LC UBR10k when they are
discovered using HTTP/HTTPS transport.
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.
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.
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.”
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.
3750-E mixed stacks.