Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Notas de publicación

CTC SendPDIP alerts might be raised on upgrades if any of the nodes in your network have the flag for 
SendPDIP set to “false” in their associated NE Defaults. This is because the upgraded node will have the 
value set to “true,” which is the default setting. You do not need to clear these alerts. They will clear 
when the upgrade is finished. 

Rarely, when the active TCC2 is removed, small traffic errors of 2 to 30 ms can sometimes occur. To 
avoid this issue, switch to the protect TCC2 before removing the working TCC2.

Rarely, if a the client associated with a TL1 ENE/GNE session stops responding to TL1 updates, then a 
common control card might autonomously reset. 

For example, say, Node A is a GNE, and Node B is an ENE. Client C opens GNE TL1 sessions with 
Node A, and from within that sessions, opens an ENE sessions to Node B. If Client C locks up and stops 
processing autonomous messages from Node B, but does not close the connection, then it is possible that 
the controller card on Node A will reboot.

This is resolved in Releases 4.6.5 and 5.0.

Rarely, the active common control card can autonomously reset when an IOS telnet session is established 
to an ML card. This does not always occur, but might occur and is repeatable in rare circumstances. This 
issue is resolved in Releases 4.6.5 and 5.0.

An expected far end LOF is never raised, and RAI becomes stuck on the DS3XM. This can occur with 
two connected DS3XMs, when a loss of frame is raised for one, and then FE-LOF is expected on the 
other. This issue will be resolved in Release 5.0.

While the DS3E protect card is active, invoking the auto frame format provisioning feature (AUTL) for 
a port might result in a misprovisioned frame format on that port (as compared to the actual frame format 
received on the DS3 receive line). If you must provision the frame format for a port while the protect 
card is active, provision it explicitly (manually select UNFRAMED, M13 or CBIT) instead of using the 
AUTL feature to ensure appropriate frame format provisioning on that port. This issue will be resolved 
in Release 5.0.