SOFTWARE
ADVISORY NOTICE
Dear Cisco Customer,
Cisco engineering has identified a
software issue with the release that you have selected that may affect your use
of this software. Please review the Software Advisory notice here to determine if
the issue applies to your environment. You may proceed to download this
software if you have no concerns with the issue described.
For more comprehensive information
about what is included in this software, please refer to the Cisco software
Release Notes, available from the Product Selector tool. From this
page, select the product you are interested in. Release Notes are under
"General Information" on the product page.
Affected Software and Replacement Solution |
||
Software Type |
Software Affected |
Software
Solution |
Version |
Version |
|
Cisco NX-OS
Software |
NX-OS Release
5.2(1) Affected
Images: n7000-s1-dk9.5.2.1.bin n7000-s1-dk9-npe.5.2.1.bin n7000-s1-kickstart.5.2.1.bin n7000-s1-kickstart-npe.5.2.1.bin |
NX-OS Release
5.2(3a) Replacement
Images: n7000-s1-dk9.5.2.3a.bin n7000-s1-dk9-npe.5.2.3a.bin n7000-s1-kickstart.5.2.3a.bin n7000-s1-kickstart-npe.5.2.3a.bin |
Affected Platforms:
Cisco Nexus 7000 Series switches running
NX-OS Release 5.2(1). This issue does not affect releases earlier than NX-OS
Release 5.2(1) and it does not affect NX-OS Release 5.2(3a) or later releases.
Reason for Advisory:
CDETS No(s)
Headline: N7K/5.2(1) Adding a new VLAN
reloads M1-series linecards
Symptoms: After you configure a new VLAN
on a Cisco Nexus 7000 series switch where SPAN sessions are enabled, M1-series modules may reset or link state flaps might occur
across multiple ports. You might see the following error:
%MODULE-2-MOD_DIAG_FAIL:
Module X (serial: <serial#>) reported failure on ports
X/1-X/48
(Ethernet) due to Octopus internal error in device 78 (device error
<ErrCode>)
Conditions: This symptom might be seen
on a Cisco Nexus 7000 switch running Cisco NX-OS Release 5.2(1) that has a TX
SPAN session configured with the destination port as a trunk port. The SPAN
destination port can be in either an M1 series module or an F1 series module.
Workaround: To work around this issue, follow these
steps:
1.
Remove all the monitor sessions.
2.
Configure VLAN(s).
3.
Restore all monitor session
configurations.
4.
Repeat these steps every time you need
to configure a new VLAN.
Alternatively, configure the SPAN
destination port as an access port (instead of a trunk port).
Further Problem Description: If the
module gets powered down (after several reloads), follow these steps to recover
the module:
1.
Remove the newly added VLAN.
2.
Remove the monitor session(s) with
this command:
switch(config)# no
monitor session 1
3.
Manually reload the M1 series module
from the default VDC:
switch# reload
module module
4.
Add new VLANs once the module is up.
Disclaimer
Disclaimer:
To increase
availability, Cisco recommends that you upgrade affected images with the
suggested replacement software images as soon as they become available.
The terms
and conditions that governed your rights and obligations and those of Cisco,
with respect to the original software will apply to the replacement software.