Cisco MGX 8230 Software

February 19, 2004

Products Affected

Problem Description

Due to an anomaly with the clrcnf command in MGX releases 2.0, 2.1, 3.0 and 4.0 and clrallcnf command in MGX releases 2.0, 2.1 and 3.0, it is possible to lose an entire MGX configuration resulting in a catastrophic MGX switch outage.

This anomaly applies to SES releases 1.0, 1.1, 3.0 and 4.0.

This anomaly does not apply to MGX nodes equipped with PXM1-type controller cards.

Background

This anomaly will manifest itself only if clrcnf or clrallcnf was performed followed by a resetsys, resetcd (on PXM), switchcc, PXM failover or power outage on a node that has either remnant file '.clrdskcfg' (for clrcnf command) or '.clrcfg' (for clrallcnf command).

It should be noted that these files are normally removed automatically after completion of the clrcnf or clrallcnf execution. In some instances, these files are not removed automatically, thus requiring manual removal.

Problem Symptoms

The symptoms are that the switch stops passing traffic and remote resources become unavailable to users.

Network maintenance engineers will find the nodal configuration is lost, including interfaces and connections.

Workaround/Solution

Workaround:

Sweep all PXMs, Active and Standby, in the network to look for the following files:

C:/.clrdskcfg

C:/.clrcfg

When found, remove these files. No other activity is required unless a user executes clrcnf or clrallcnf after the clean sweep was performed. In that case, perform the workaround again.

Solution:

The clrallcnf issue is resolved all releases of MGX 4.0 software.

The clrcnf anomaly will be resolved in MGX 5.0.

Recovery:

The configuration can be restored from a previous back up configuration via the saveallcnf stored at a remote server. The back-up configuration can be ftp'd to the MGX node and restored using the restoreallcnf command.

Cisco recommends that users should backup MGX configurations frequently and store the backup configuration file on a remote server.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

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:

• Open a service request on Cisco.com
• By email
• By telephone

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.