Guest

Cisco MDS 9500 Series Multilayer Directors

Field Notice: FN - 63019 - Under Rare Conditions, a Non-disruptive Upgrade of a DS-C9506, DS-C9509 or DS-C9513 to SAN-OS 3.1(1) through 3.2 (2c) or a Subsequent Switchover May Cause the Switch to Reboot - Workaround Provided to Resolve the Issue


January 23, 2008

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Revision History

Revision

Date

Comment

1.0

23-JAN-2008

Initial Public Release

Products Affected

Products Affected

M9500 - DS-C9506

M9500 - DS-C9509

M9500 - DS-C9513

Problem Description

Under rare conditions, a non-disruptive upgrade of a DS-C9506, DS-C9509 or DS-C9513 to SAN-OS 3.1(1) through 3.2 (2c) or a subsequent switchover or a non-disruptive upgrade, may cause the switch to reboot.

This Field Notice only applies to MDS 95xx model switches, that is DS-C9506, DS-C9509 and DS-C9513, and it applies to both supervisor models - SUP1 and SUP2.

Listed below are the three situations in which this issue can occur:

  1. A non-disruptive upgrade from any version prior to 3.1(1) to 3.1(1) through 3.2(2c) may result in an unplanned switch reboot.

  2. If a non-disruptive upgrade from any version prior to 3.1(1) has occurred, an MDS 95xx switch reboot may occur during subsequent non-disruptive upgrade from any version in this SAN-OS range to any other version in the range of 3.1(1) through 3.2(2c).

  3. A reboot may also happen if any kind of supervisor switchover, either user or system initiated, occurs after a non-disruptive upgrade has taken place from any SAN-OS version prior to 3.1(1) to 3.1(1) through 3.2(2c).

Background

A data structure change related to the Port-Channel Manager process made in SAN-OS 3.1 created an incompatibility in the size of the data structure with that in earlier SAN-OS versions.

Due to this incompatibility, after a non-disruptive upgrade or a supervisor switchover, Port Channel Manager may read invalid data.

Sometimes, this may result in a switch reboot, regardless of whether any port channels are configured on the switch.

Problem Symptoms

Under rare conditions, a non-disruptive upgrade of a DS-C9506, DS-C9509 or DS-C9513 to SAN-OS 3.1(1) through 3.2 (2c) or a subsequent switchover or a non-disruptive upgrade, may cause the switch to reboot.

SAN-OS versions vulnerable to this issue are 3.1(1) through 3.2(2c). This range includes the following releases:

SAN-OS 3.1(x)

SAN-OS 3.2(1x)

SAN-OS 3.2(2a)

SAN-OS 3.2(2b)

SAN-OS 3.2(2c)

Workaround/Solution

Solution:

Apply the workaround described below to all switches running SAN-OS 3.1(1) through 3.2(2c) to fix this issue.

For switches running a SAN-OS release prior to 3.1(1), upgrade to SAN-OS 3.2(3) or higher release to avoid this issue.

Workaround:

Each DS-C9506, DS-C9509 and DS-C9513 switch running a SAN-OS release 3.1(1) through 3.2(2c) should have an unused port-channel created and deleted on it to avoid a switch reload. It is not necessary to perform the copy running-config startup-config command.

Note: Only ONE unused port channel needs to created and deleted to avoid the switch reload.

Example of Creating and Deleting a Port-Channel with an unused ID

Step 1. Determine a port-channel ID that is not in use.

switch# show port-channel usage 
Totally 2 port-channel numbers used 
=================================== 
Used : 1 , 5 
Unused: 2 - 4 , 6 - 256

Step 2. Create a port-channel with an unused ID. In this example, ID 6 will be used.

switch# config terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
switch(config)# interface port-channel 6 
switch(config-if)# end

Step 3. Verify that the port-channel (6) was created.

switch# show port-channel database interface port-channel 6 
port-channel 6 
Administrative channel mode is on 
Operational channel mode is on 
Last membership update succeeded 
No port

Step 4. Delete the port-channel.

switch# config terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
switch(config)# no interface port-channel 6 
port-channel 6 deleted and all its members disabled 
please do the same operation on the switch at the other end of the port-channel 
switch(config)#

This completes the workaround procedure. No further actions are required to address this problem.

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.

DDTS

Description

CSCsl66072 (registered customers only)

pcm info in pss corrupt after upgrade from 3.0 to 3.1

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.