Release Notes

24
Cisco Prime Network 4.1 Release Notes
OL-31014-01
Prime Network 4.1 Bugs
Closed Bugs
Table 17 identifies bugs that have been closed since the previous release.
CSCuf89644 Module is not discovered properly for a Nexus 7000 device because the OID
returned by the device is incorrect.
CSCuh35846 Missing values when editing a command for a second time.
CSCue71985 Wrong association of syslog alarms for TP-tunnel interfaces on ASR 9000 devices.
CSCuh52235 Repetition of Ethernet OAM Session syslog in Event Notification (ENS).
CSCue87299 Physical inventory of Nexus 3000 devices is not modeled.
CSCuh51488 The Prime Central GUI may not reflect real time power off/disconnected status for
blade servers. This behavior may be temporary until an inventory sync is performed
from Prime Central.
CSCUI28002 UCS device synchronization takes longer than expected in a scale setup.
CSCui11704 After creating a device group, some device members are not displayed in the group.
CSCuf77193 Out Of Memory does not print the stack trace.
CSCuh84707 OIR cards with DWDM do not map DWDM interface traps to the interface. The
events generated are not correlated correctly and the events are not associated with
the interface.
CSCun18257 Incorrect bundle association on ASR 9000 device.
Table 16 Resolved Bugs in Cisco Prime Network 4.1 (continued)
Bug ID Description
Table 17 Closed Bugs in Cisco Prime Network 4.1
Bug ID Description
CSCuh88641 Some tickets might not be cleared after upgrade.
CSCuh37918 Link filter in map in Vision - mismatch in group and contents after upgrade.
CSCuh56951 Commands created in Vision are not reflected in the command repository after
restarting AVM11.
CSCuh77801 When using Vision to edit a command that was created in Command Manager, a
new implementation is created instead of updating the existing implementation.
CSCug21885 P2MP MPLS-TE tunnel configuration changes are not updated on mid/tail nodes on
VNEs using reduced polling.
CSCtj30236 LAG link is not rediscovered after clearing and removing the ticket.
CSCuh96505 After the VM key is changed, e.g., due to rename or migration, all the old
VM-related alarms continue to point to the old VM location. Any new alarm,
including the renaming and migration alarm, will point to the correct VM location.
CSCuc62642 In some cases, for recurring jobs (Daily, Weekly, Monthly), the Job Manager does
not show the correct "Next Run Time" and the job is not executed at the expected
time.
CSCtx01472 Newly added event types are not forwarded through the Event Notification Service
if specific event types were selected when defining the service.