Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP)

Seite von 33
 
26
Release Notes for Cisco ONS 15454 Release 6.2
OL-9453-01
  Resolved Caveats for Release 6.2
CSCdu53509 
When a TL1 session to a remote node (ENE) is established via a gateway node (GNE) and you have 
changed the node name of the ENE via either TL1, CTC or SNMP, then you must wait for about 30 
seconds to issue a TL1 command via the GNE. This delay is to permit the updates to propagate to all 
nodes in the network. During this transition, neither the old node name nor the new node name can be 
used in the TL1 session to access the ENE. This 30 second window may be reduced in a future release.
Resolved Caveats for Release 6.2
This section documents caveats resolved in Release 6.2. 
Hardware
CSCsb77209
Split route circuits on some FC_MR-4 cards will take some errors at -5C to +10C ambient temperatures. 
This issue is resolved in Releases 6.0.1, 6.1, and 7.0. 
Maintenance and Administration
CSCsd67191
Rarely, in a large network with many host routes the Proxy ARP server might run out of ring buffer 
storage, resulting in a subsequent failure of the driver to receive new packets. This can lead to DCC 
failure and loss of all connections. This issue is resolved in Releases 6.2 and 8.
CSCsd55460
When upgrading a network to Release 6.0.1, 6.1, or 7.0, where LOS-P exists on a pass-through port of 
a WSS for a ROADM node, if you change the circuit state to OOS,DSBLD and then again to IS-AINS, 
the circuit fails to go up. There are two possible workarounds: 
1.
Change the calibration value on the pass-through port of the WSS.
2.
When the circuit is in OOS state, relaunch ANS.
This issue is resolved in Releases 6.2 and 7.0.1.
CSCsd04867
An ONS node with OSI enabled on DCC might have its control card reboot if certain conditions are met. 
This reboot can occur if the MTU size is set to 512 and if the DCC link is connected to certain releases 
of a specific third-party network element. This reboot does not occur with other NE vendors. Use any 
MTU size greater than 512 to avoid this issue. This issue is resolved in Release 6.2.