Cisco Nexus 7000 Series Switches

March 6, 2012

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	06-MAR-2012	Initial Public Release

Products Affected

Products Affected
N7000 NX-OS - 5.2(1)

Problem Description

For Cisco Nexus 7000 series switches running NX-OS 5.2(1), M1-series modules can reset or link state across multiple ports can flap after configuring a new VLAN with SPAN. A full list of all M1-series modules is provided below:

N7K-M148GT-11=
N7K-M132XP-12=
N7K-M148GS-11=
N7K-M148GS-11L=
N7K-M108X2-12L=
N7K-M132XP-12L=
N7K-M148GT-11L=

Please note that this is a software caveat (CSCtt43115) and not a hardware issue on the M1-series modules.

Background

This issue only occurs on Cisco Nexus 7000 series switches running NX-OS 5.2(1) when a TX SPAN session is configured with the destination port as a trunk port. The SPAN destination port could be in either an M1 or F1 module.

Problem Symptoms

The following error messages can be seen when the issue occurs:

%MODULE-2-MOD_DIAG_FAIL: Module X (serial: ) reported failure on ports X/1-X/48 (Ethernet) due to Octopus internal
 error in device 78  (device error [ErrCode])

Workaround/Solution

There are two methods to workaround this issue:

1) Remove all the monitor sessions, configure VLAN(s) and restore all monitor session configurations.
2) Configure the SPAN destination port as an access port instead of a trunk port.

Either of the above options should be repeated every time a new VLAN needs to be configured.

This issue is applicable only to the NX-OS 5.2(1) release. This issue is NOT applicable to pre-5.2 releases or 5.2(3a) and later.

Additional Workaround Information:

If the affected Nexus 7000 module(s) are powered down after a few reloads, then follow the steps mentioned below to recover the modules (relevant CLI commands are provided):

1) Remove the newly added VLAN.

2) Remove the monitor session(s).

N7K-CORE(config)#no monitor session 1

3) Manually reload the M1 module(s) from the default VDC.

N7K#reload module [mod#]

4) Once the modules are up, add the new VLANs.

DDTS

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

DDTS	Description
{CSCtt43115} (registered customers only)	N7K/5.2(1) Adding a new vlan reloads M1-series linecards

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

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