Cisco Cisco ONS 15454 SDH Multiservice Provisioning Platform (MSPP)

Pagina di 46
 
4
Release Notes for Cisco ONS 15454 SDH Release 4.6.1
OL-4855-01
Caveats
Line Cards
J1 and J2 Path Trace with E1-42 Cards 
On E1-42 cards, do not enable J1 or J2 monitoring in Release 4.6.1. To do so can result in a loss of traffic. 
If you do have J1 or J2 path trace turned on, and you upgrade to Release 4.6.1, turn those features off 
prior to the upgrade in order to avoid possible traffic loss. This issue will be resolved in a future release.
DDTS # CSCed30150
When the E1-42 card is fully loaded, J2 path trace cannot be retrieved on VC12 circuits. This issue will 
be resolved in a future release.
DDTS # CSCed36598
When DHCP forwarding is turned on, and the forwarding to address is set to a cellbus address instead 
of a DHCP server address, you can lose connection to your nodes. Always set the forwarding address to 
a DHCP server. This issue will be resolved in a future release.
DDTS # CSCec83712
Avoid pulling the active cross connect when the standby is locked out. If the standby cross connect card 
is locked out and the active cross connect card is pulled, the E1-42 card switches to protect. This switch 
should not occur. After the active cross connect card reboots and traffic is restored, the reverting E1-42 
card takes a hit of +/- 1 second. This issue will be resolved in a future release.
DDTS # CSCed14006
Rarely, after you power cycle a node, an installed E1-14 card might report LOF on various ports. 
Provisioning will clear the LOF. This issue will be resolved in a future release.
DDTS # CSCed27998
Rarely, a traffic hit can occur during the TCC2 switch that occurs as a part of the upgrade procedure. 
Traffic hits are only expected on E1-42 traffic; all other E3 & DS3 traffic should remain errorless during 
the upgrade's TCC2 switch portion. Hits to the E1-42 traffic occur 90% of the time during the upgrade 
if all 42 circuits are provisioned on the card. This issue will be resolved in a future release.
DDTS # CSCed15073
Rarely, a WKSWPR condition resulting from loss and recovery of power to the node can become stuck 
when there are multiple 1+1 protection groups provisioned on a single OC3-8 card. This issue will be 
resolved in a future release.