Cisco Cisco Prime LAN Management Solution 4.1 Release Notes
71
Release Notes for Cisco Prime LAN Management Solution 4.1
OL-25435-01
Bugs
CSCtq42192
Incorrect non-compliant
entity count.
entity count.
Non-complaint entity count will not match with data
shown in the details page.
shown in the details page.
For example, tt shows the count as 3 but clicking on the
link shows the details of 2 endpoints.
link shows the details of 2 endpoints.
Also blank window will open when clicking on the
count.
count.
This occurs when you:
1.
Add new endpoints to the group and trigger
compliance check job, count gets updated and
shows wrong number.
compliance check job, count gets updated and
shows wrong number.
2.
Delete devices corresponding endpoint entries get
removed. If the endpoint is shown under NC entity
count, the count is not showing correct value.
removed. If the endpoint is shown under NC entity
count, the count is not showing correct value.
Workaround:
None
CSCtr11921
EnergyWise process creates
core.
core.
EnergyWise process will be down. This occurs when
some collection is triggered.
some collection is triggered.
Core gets created on some UII operation which is
specific to solaris server and it is inconsistent also.
specific to solaris server and it is inconsistent also.
Workaround:
Delete the core and restart the EnergyWise process by
./pdexec <pid>.
./pdexec <pid>.
CSCtr30331
EnergyWise inconsistent
issue due to toolkit.
issue due to toolkit.
The following are the EnergyWise issues:
1.
EnergyWise Endpoint collection summary will
show success with partially failed collection.
show success with partially failed collection.
2.
Policy deploy will not be appropriate.
3.
Endpoint details will show wrong endpoint.
When certain device is not reachable and the first
contacted device is collection successful then the entire
collection will be successful.
contacted device is collection successful then the entire
collection will be successful.
Toolkit sometimes contact a device which is not
appropriate due to actual device reachability.
appropriate due to actual device reachability.
Workaround:
This issue happens inconsistently so collecting or
deploying again after sometime solves this issue.
deploying again after sometime solves this issue.
Table 12
Open Bugs Related to Work Center in LMS 4.1 (continued)
Identifier
Summary
Explanation