Cisco Systems ONS 15327 manual DDTS # CSCdv62990, DDTS # CSCdu03513, DDTS # CSCds92475

Resolved Software Caveats for Release 3.3

Maintenance and Administration

DDTS # CSCdv62990

Telcordia GR-815 requires that a new password must have at least 1 numeric character (0 to 9) and at least one special character from the character set {plus-sign (+), pound-sign (#), percent-sign (%)}. CTC normally issues a warning if the password is non-compliant, but allows you to create the password. However, CTC does not issue a warning when a new password is requested that has two special characters, but no numeric component. Thus, for example, there is no warning in CTC for the password “aaaa++,” which lacks the numeric character and is non-compliant. This issue is resolved in CTC Release 3.3.

DDTS # CSCdu03513

A node can become permanently gray in the network view of a CTC session, and therefore inaccessible for that session. Under some conditions, CTC will stop trying to establish connection to a node and the node will turn gray in the network view, thus remaining inaccessible throughout the CTC session (at present you are not notified when this occurs). The conditions include:

•CTC encounters something unexpected in the CTC Cache—either a missing file, or a file that does not have the expected contents. This occurs most frequently when there are multiple topology hosts with overlapping topologies specified in the preferences file and you access the nodes during their reboot process (active card booted, standby card rebooting).

•The issue cannot be positively identified until after you are sure the node has had a reasonable length of time to be discovered. Wait at least fifteen minutes for a node to be discovered and represented as accessible.

•Also, some nodes may be validly represented as inaccessible during a CTC session when software versions are incompatible. The incompatible software version alarm might not always be raised in these circumstances.

If the inaccessible node is running a software version that differs from that of other nodes in the network, start CTC from the highest-versioned node in the network. If, however, the node ought to be accessible but is still grayed out, eliminate multiple nodes from a single topology from the group list. in other words, set up your group list such that one node can discover another node, rather than putting them into a topology host group. (Define the group list from the Edit > Preferences menu, and select it in the login dialog box when you launch CTC.) This issue is resolved in Release 3.3.

DDTS # CSCds92475

The ACT/STBY LED of the active XTC is permanently amber after the Lamp Test button in CTC is clicked. (Display the CTC node view and click the Maintenance > Diagnostic tabs to view the Lamp Test.)

Under normal conditions, the ACT/STBY LED of the active XTC should be green. The ACT/STBY LED of the standby XTC should be amber. Browse to the Maintenance > Diagnostic tabs in CTC and click the Lamp Test button. The ACT/STBY LED of the active XTC turns amber and remains that way.

It is possible to return the node to a state where the active XTC has a green ACT/STBY LED by resetting the active XTC from the CTC. Note that in a node with redundant XTCs, this reset will force an XTC protection switch and cause an in-service traffic disruption of less than 60 ms. In a node with only one XTC, the traffic disruption will be longer and may be unacceptable. Determine which XTC is active by

Release Notes for Cisco ONS 15327 Release 3.3

OL-2671-01 9