Release Notes

12
Cisco Prime Network 4.1 Release Notes
OL-31014-01
Prime Network 4.1 Bugs
• Bugs that were fixed in previous releases of Prime Network 4.1 but are still open in the current
release because they were identified too late in the Prime Network 4.1 development cycle.
The open bugs have been grouped in the following categories:
• Installation/Upgrade Bugs, page 12
• High Availability Bugs, page 13
• Bugs Related to Hardware or Software Version Issues, page 13
• Technology-Related Bugs, page 15
• VCB Bugs, page 16
• Change and Configuration Management (CCM) Bugs, page 17
• Command Manager Bugs, page 17
• Compliance Audit Bugs, page 17
• Fault Management Bugs, page 18
• Report Manager Bugs, page 18
• Operations Reports Bugs, page 19
• VNE/AVM Bugs, page 19
• Suite-Related Bugs, page 20
• GUI-Related Bugs, page 20
• Job Scheduler Bugs, page 20
Installation/Upgrade Bugs
Table 1 Installation/Upgrade Bugs
Bug ID Description
CSCup07426 Installation of Operations Reports fails with the following in the installation log:
initdb.bin: encoding mismatch
CSCuo63266 Operations Reports installer does not integrate SSO in suite mode.
CSCun15534 Unable to log into Operations Reports a few days after upgrade to Prime Network
4.1.
CSCue00169 A report created prior to upgrade to Prime Network 3.10 or Prime Network 3.11
does not work post upgrade.
CSCug22532 When trying to install a Geographical Redundancy only scenario the following error
is received:
“SSHProcessError The ssh process was terminated. at setup_replication.pl line 859
*** ERROR: Failed to setup the replication. ABORTING. ***”
CSCug79313 Cannot decouple Prime Network from Prime Central.
CSCuj84287 The event “Prime Network SSH daemon on $machineIP is out of service” is
triggered even when SSH daemon is up and running.
CSCun39786 Network-conf fails if SMTP server address is provided using FQDN instead of the
IP address.
CSCuj37426 Downtime during upgrade is long because it takes a long time to back up Prime
Network files.