Release Notes

Release Notes for Cisco ONS 15454 SDH Release 4.1.3

OL-4984-01

Resolved Caveats for Release 4.1.3

ML Series

DDTS # CSCin25238

If you configure Fast EtherChannel and POS-channel in the same bridge group, during system boot, the

Fast EtherChannel or POS-channel configuration may be lost and following error message displayed:

Interface FastEthernet1 is attempting to join Port-channel1. But Port-channel1

belongs to bridge-group 1 which has another FE(C) member in it. FEC + FE(C) is not

allowed in the same bridge group. Please change your configuration and retry.

This issue is resolved in Release 4.1.

DDTS # CSCea18623

To avoid possible ML-series card resets when adding interfaces to a bridge group, always configure the

Spanning-Tree Protocol for the bridge group (using the bridge number protocol command) before

performing any other configuration on the bridge group.

If you want to use a bridge group that does not run the Spanning-Tree Protocol, you must first configure

the bridge group with the Spanning-Tree Protocol, and then disable the Spanning-Tree Protocol for that

bridge group on every interface where it is used (using the bridge-group number spanning-disabled

interface configuration command). This issue is resolved in Release 4.1.

G Series Cards

DDTS # CSCec05896

When a G-series card is used in transponder mode the severity of reported alarms is incorrect in some

cases. When using transponder mode on G-series cards, if alarm severity is an issue, use the alarm

profile editor to set the severity to the desired values. This issue is resolved in Release 4.6 and

maintenance Release 4.1.3.

DDTS # CSCeb80771

An Ethernet traffic hit of 500-600 ms may occur when upgrading to Release 4.1 from a prior release.

This can occur if active traffic is running on a G1000-4, G1K-4 or G1000-2 card when upgrading the

node to Release 4.1. The hit will occur only the first time that you upgrade to Release 4.1. On subsequent

downgrades followed by upgrades there will be no traffic hit and the upgrade will be errorless. There is

no workaround; however the issue will not occur when upgrading from Release 4.1 to a later release.

This issue is resolved in Releases 4.1.3 and 4.6.

Maintenance and Administration

DDTS # CSCsh61803

This is a request for formal written notification to customer running CTC release 4.1.3 and any other

suspected releases, of possible username corruption when the syntax takes a certain form. Upgrading the

node having the usernames with 5th character as 'A' from 4.1.3 to 6.0 is resulting in the truncation of all