Field Notice 12161: TCC Might Boot up With Wrong IP Address (Release 1.0.x Only)

Available Languages

Updated:November 4, 2003

Document ID:FN12161

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Updated January 18, 2002

April 13, 2000

Products Affected

Product	Comments
Cisco ONS 15454	Formerly Cerent 454

Problem Description

Using version 1.0 software, the Timing Communications and Control (TCC) card (rev 009x or higher) may boot up with the wrong IP address.

Background

This problem was discovered during testing in the Cerent lab.

Problem Symptoms

This problem occurs when you are running version 1.0 software and two TCCs that are both board rev.009x or later. If both TCCs are booted up simultaneously, as in a shelf power reset for example, one or both of the TCCs may not get configured with the correct IP address. This might occur in either the Active or the Standby TCC. If it occurs in the Standby TCC, it may not become evident until the Standby TCC becomes the Active. This causes the TCC to utilize a default database and nothing will be provisioned.

Workaround/Solution

The workaround for this problem is to avoid allowing both TCCs booting up simultaneously. Allow one to complete its boot sequence and become active before the other. Also, any shelf that has both TCCs boot up simultaneously and has the proper IP on the Active TCC should have its Standby TCC reset to be sure that it gets the proper configuration.

If a shelf does boot with the wrong IP address, it should have both TCCs removed and booted separately to ensure that the problem does not recur. There is also a danger of database loss. If the database is lost, restore the database from the backup. The fix for this issue is to upgrade to a new release of software (2.0 or later).

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.