Release Notes

23
Cisco Prime Network 4.1 Release Notes
OL-31014-01
Prime Network 4.1 Bugs
CSCug27611 A system event stating "Number of orphan events reached major limit" is generated.
CSCuh96294 Element type filtering is not working in Prime Network Events.
CSCuh57307 Transaction job does not have a tasks list in the Job results screen.
CSCug34467 Date format of Device Up time as well as the value of time for a VNE is different
in the report from what is shown in the inventory.
CSCui08242 Prime Performance Manager (PPM) events are not displayed in Operations Reports.
CSCuh60428 Admin users can delete prepackaged reports and data sources but there is no way to
retrieve them.
CSCuh72640 Device selector in Operations Reports is not automatically updated when VNEs are
added/deleted.
CSCuh89330 Unassociated FA service is not deleted from the report.
CSCuh96493 Tickets generated by network events are not shown in the reports.
CSCuh06495 Drop down menus appear to the left of and far from the drop down button (instead
of just below the button).
CSCuh77441 Device configuration validation pass event is not received after adding an
unreachable VNE to the server.
CSCuh83550 RFGateway 10 device does not model when Third Party Device Package is installed
in the system.
CSCuh83890 When loading 30K VNEs at once for the first time, the system hangs.
CSCuh71133 VNE is stuck in discovering mode.
CSCuh55163 Nexus device takes time to become operational and the device CPU is increased in
a scale setup.
CSCuh25970 VNE fails to recognize the %CONTROLLER-5-UPDOWN syslog issued for T1
controller on the serial interface and therefore fails to generate the Port down
service alarm.
CSCuh97042 The Prime Central GUI may not reflect real time card in/out status. This behavior
may be temporary until an inventory sync is performed from Prime Central.
CSCuh51921 Device port line rate might not reflect properly in the Prime Central GUI.
CSCug67301 When a data store is deleted on a vCenter, the data store and all its association to
Hosts will be removed from vCenter inventory.
CSCui64970 Prime Network webstart clients fail to start.
CSCuh00593 VNEs remain in initializing state during system startup.
CSCug42988 When adding an MPLS-TP service to the map, endpoints or middle points may not
be discovered properly.
CSCud05482 High load average may be caused because of southbound IP search.
CSCug54035 Cisco Prime Network displays extra Gigabit ports for 24 port Whales
(ME3600x/ME3800x) device.
CSCuh46269 When executing the Create ISIS Router command, the specified EIGRP AS Number
is not used for execution.
CSCuh49413 Units do not start after reboot.
Table 16 Resolved Bugs in Cisco Prime Network 4.1 (continued)
Bug ID Description