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 | Publish Date | Comments |
---|---|---|
1.0 |
02-Mar-12 |
Initial Release |
10.0 |
11-Oct-17 |
Migration to new field notice system |
Affected OS Type | Affected Release | Affected Release Number | Comments |
---|---|---|---|
NON-IOS |
5 |
5.2(1) |
Defect ID | Headline |
---|---|
CSCtt43115 | N7K/5.2(1) Adding a new vlan reloads M1-series linecards |
For Cisco Nexus 7000 series switches running NX-OS 5.2(1), M1-series modules may reset or link state across multiple ports may 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 this is not a hardware issue on the M1-Series modules.
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.
The following error messages may 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])
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 new VLANs
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:
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.
Unleash the Power of TAC's Virtual Assistance