Cisco Cisco Prime Network 3.8 Release Notes

Page of 26
 
21
Cisco Prime Network 3.8.1 Release Notes
OL-26395-01
  Open Bugs in Prime Network 3.8.1
AVM/Unit/VNE Bugs
VCB Bugs
Bugs Resolved in Earlier Releases but Still Open in Prime Network 3.8.1
The bugs listed in 
 were identified too late in the Prime Network 3.8.1 development cycle to be 
fixed for this release. The fixes for these bugs have been provided to customers running older versions 
of the product as needed and are scheduled for inclusion in the next release.
T
Table 13
AVM/VNE Bugs
Identifier
Title
ClassCastException in AVM log for VNE referencing ifHighSpeed OID
Incorrect command to enable VNE Staggering mechanism
CSCtx52584
AVM with VNE is restarted by AVM99 due to an Out Of Memory
CSCty42565 
NAT unit seen as regular if other device answers with same private ip
CSCty42129 
Fail to copy VNE persistency files from an IPv4 unit to an IPv6 gateway while 
moving AVMs/VNEs
Moving AVMs operation fails; not all AVMs are moved between units
Cannot start new AVM 100 on unit when unit with old AVM 100 is down
Proxy for AVM 25 does not work in high availability (HA) scenarios
Table 14
VCB Bugs
Identifier
Title
Cross launch of VCB from Manage in Suite mode does not work
Table 15
Bugs Resolved in Earlier Releases but Still Open in Prime Network 3.8.1
Identifier
Title
CSCtr30287
Port down ticket is not cleared after the port is up
CSCtr35459
Cannot create a command with Command Builder on selection of a  row in Sub 
Interface table (Physical interface inventory)
CSCtq04992
Free memory on the unit decreases over time.
 In OSPF Neighbor for cases like Bundle-Ether Interface name - OSPF Neighbor 
down alarms do not correlate to Link down on IOX
CSCts07862
DS0 bundle and BGP vrf tickets not correlated to Sonet interface down
CSCts96142
AVM 11 does not process any links for 15 min
CSCtw62838
PP version is missing in Prime Network GUI (Help -> About)