Cisco Cisco ONS 15600 Multiservice Switching Platform (MSSP)

There is memory leak in the software running on 15600 nodes. The leak happens whenever there is a 
change in the entity table. Entity changes happen during events like: cards are inserted or removed; 
PPMs are inserted or removed, creating or deleting circuits. The memory leak also seems to happen 
whenever Entity alarms are raised. Though this memory leak is in SNMP code it happens irrespective of 
whether SNMP is configured on the node or not.

When a rollTo leg is not receiving a good signal, and because of this the rollPending alarm is not cleared, 
there is no alarm indicating the reason that the RollPending alarm fails to clear. This issue is resolved in 
Release 7.0.

When upgrading the software from Release 6.x.x to Release 7.x.x, the DS3 and EC1-12 cards fail to load 
if the node name begins with the letters FL. Changing the node name resolves this issue.

When the Cisco ONS 15600 is supporting 500 TL1 sessions and there is a sustained high level of 
management traffic the active TSC might reset. This issue is visible when the Cisco ONS 15600 is 
supporting 500 TL1 ENE logins to DCC-linked network nodes such as the Cisco ONS 15454. In a 
laboratory test it was observed that an alarm flood (approximately 70000 alarm messages) in the network 
would overload the active TSC and cause it to reset. The standby TSC transitions to active and the node 
recovers. To avoid this issue configure TL1 sessions to throttle the amount of alarm data that is sent 
across the management network. For example, when a TL1 session starts, the REPT^ALM and 
REPT^EVT messages are allowed by default. The TL1 command “INH-MSG-ALL” will inhibit all 
REPT-ALM and REPT^EVT autonomous messages from being transmitted. This issue is resolved in 
Release 7.0.

This section highlights new features and functionality for Release 7.0.x. For detailed documentation of 
each feature, consult the user documentation.