Cisco Nexus 3000 Series NX-OS Release Notes, Release 10.2(6)M
Available Languages
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- US/Canada 800-553-2447
- Worldwide Support Phone Numbers
- All Tools
Feedback
Feedback
This document describes the features, issues, and exceptions of Cisco NX-OS Release 10.2(6)M software for use on Cisco Nexus 3500 and 3600 platform switches.
The new Cisco NX-OS Software Release and Image-naming Convention information is available here — Cisco NX-OS Software Strategy and Lifecycle Guide.
Note: The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product.
The following table lists the changes to this document.
| Date |
Description |
| September 01, 2023 |
New and Enhanced Software Features
There are no new software features introduced in Cisco NX-OS Release 10.2(6)M for Cisco Nexus 3000 series.
There are no new hardware features introduced in Cisco NX-OS Release 10.2(6)M for Cisco Nexus 3000 series.
The following table lists the open issues for Cisco Nexus 3000 Series switches in Cisco NX-OS Release 10.2(6)M. Click the Bug ID to search the Cisco Bug Search Tool for additional information about the bug.
| Bug ID |
Description |
| Headline: Crash in the ptplc process Nexus# show cores VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------------------- 1 1 1 ptplc 7879 2023-08-04 14:03:21 1 1 1 ptplc 19500 2023-08-04 14:03:30 |
|
| Headline: N3548-XL does not show SPAN drops |
|
| Headline: N3500 shows incorrect next-hop in routing hash cli output |
The following tables lists the resolved issues for Cisco Nexus 3000 Series switches in Cisco NX-OS Release 10.2(6)M. Click the Bug ID to search the Cisco Bug Search Tool for additional information about the bug.
| Bug ID |
Description |
| Headline: Nexus 3000 Spanning-tree create instance for interface that is a part of a port-channel |
|
| Headline: Cisco Nexus 3000 switch (4GB) reloads with Kernel panic and no core. Symptoms: Cisco Nexus 3000 switches with 4GB RAM that run SNMP on Cisco NX-OS Releases lower than 9.3(9) or 10.2(6), frequently reload with kernel panic. There is no core getting generated due to low memory in the box. Device reports critical memory alert followed by reload due to kernel panic. Workarounds: None |
|
|
|
Headline: Nexus 3548: L3 Adjacency is not programmed properly in hardware Symptoms: L3 adjacency is mis-programed in HW and routed packets to destination hosts are dropped. Issue might happen for single or multiple hosts. Workarounds: Running 'clear ip arp force-delete' for the affected entries triggers ARP learning again and HW entry is refreshed. Doing 'clear ip arp force-delete' for an entire subnet/VLAN might cause a couple of seconds of disruption. |
| Headline: N3500 fails to program SG L3 ltl-index after receving igmpv3 source leave on mrouter port Symptoms: After mcast flow stop fzor about 3 minutes, l3-ltl will age on mtc, then start the mcast flow again, l3-ltl will never program. Workarounds: None |
|
| Headline: Nexus 3548 not acknowledging link up/down events. Symptoms: Once link is flapped, it remains in Link not connected state.Although we are receiving proper signal from other side and Good-2-bad and bad-2-good interrupts are getting generated, those are not getting asserted. Workarounds: Use the following commands: #test hardware internal mtc-usd gpe 5 disablemodule 1 #test hardware internal mtc-usd gpe 5 enable |
|
| Headline: Unexpected reload ipfib hap reset |
|
| Headline: Kernel Panic due to HR Timeout & SMC $ %KERN-0-SYSTEM_MSG: [11269926.144849] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] - kernel %KERN-0-SYSTEM_MSG: [11269926.144869] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] - kernel VDC-1 %$ %VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain 1, VPC peer keep-alive receive has failed VDC-1 %$ %KERN-0-SYSTEM_MSG: [11269926.144849] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] - kernel VDC-1 %$ %KERN-0-SYSTEM_MSG: [11269926.144869] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] - kernel VDC-1 %$ %KERN-0-SYSTEM_MSG: [11269926.148346] nxos_panic: Kernel panic - not syncing: softlockup: hung tasks - kernel VDC-1 %$ %KERN-0-SYSTEM_MSG: [11269926.148415] ttyS console device is disabled - kernel VDC-1 %$ %KERN-0-SYSTEM_MSG: [11269926.150327] END: PANIC REPORT GENERATED AT 1689769096 - kernel |
|
| Headline: N3548 does not display all SPAN sessions in SPAN drop output |
Device Hardware
| Product ID |
Description |
| N3K-C3548P-XL |
Cisco Nexus 3548-XL switch |
Cisco Nexus 3500 Series Fans, Fan Trays and Power Supplies
| Product ID |
Description |
| N2200-PAC-400W |
Cisco Nexus 2000 or 3000 400W AC power supply, forward airflow (port side exhaust) |
| N2200-PAC-400W-B |
Cisco Nexus 2000 or 3000 400W AC power supply, reverse airflow (port side intake) |
| N2200-PDC-400W |
Cisco Nexus 2000 or 3000 400W DC power supply, forward airflow (port side exhaust) |
| N3K-PDC-350W-B |
Cisco Nexus 2000 or 3000 350W DC power supply, reverse airflow (port side intake) |
| NXA-FAN-30CFM-B |
Cisco Nexus 2000 or 3000 individual fan, reverse airflow (port side intake) |
| NXA-FAN-30CFM-F |
Cisco Nexus 2000 or 3000 individual fan, forward airflow (port side exhaust) |
Cisco Nexus 3600 Switches
| Product ID |
Description |
| N3K-C3636C-R |
The Cisco Nexus 3636C-R is a 1 rack unit (RU) switch with 36 100-Gigabit QSFP28 ports, 40-Gigabit QSFP, 2 management ports, 1 console port, and 1 USB port. The switch supports both port-side exhaust and port-side intake airflow schemes. The switch has two power supplies, one for operations and the other for redundancy. Both power supplies must be either AC power supplies or DC power supplies. |
| N3K-C36180YC-R
|
The Cisco Nexus 36180YC-R is a 1 rack unit (RU) switch with 48 1/10/25-Gigabit SFP ports and 6 40-Gigabit QSFP/100-Gigabit QSFP28 ports, 1 management port, 1 console port, and 1 USB port. The switch supports both port-side exhaust and port-side intake airflow schemes. The switch has two power supplies, one for operations and the other for redundancy. Both power supplies must be either AC power supplies or DC power supplies. |
To perform a software upgrade or downgrade, follow the instructions in the Cisco Nexus 3500 Series NX-OS Software Upgrade and Downgrade Guide and Cisco Nexus 3600 Series NX-OS Software Upgrade and Downgrade Guide.
For information about an In Service Software Upgrade (ISSU), see the Cisco NX-OS ISSU Support Matrix.
The Cisco Management Information Base (MIB) list includes Cisco proprietary MIBs and many other Internet Engineering Task Force (IETF) standard MIBs. These standard MIBs are defined in Requests for Comments (RFCs). To find specific MIB information, you must examine the Cisco proprietary MIB structure and related IETF-standard MIBs supported by the Cisco Nexus 3000 Series switch. The MIB Support List is available at the following FTP sites:
ftp://ftp.cisco.com/pub/mibs/supportlists/nexus3000/Nexus3000MIBSupportList.html
To determine which transceivers and cables are supported by Cisco Nexus 3000 Series switches, see the Transceiver Module (TMG) Compatibility Matrix.
To see the transceiver specifications and installation information, see https://www.cisco.com/c/en/us/support/interfaces-modules/transceiver-modules/products-installation-guides-list.html.
Cisco Nexus 3000 Series documentation: Cisco Nexus 3000 Series switch documentation
Cisco NX-OS Software Release and Image-naming Convention: Cisco NX-OS Software Strategy and Lifecycle Guide
Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference: Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference.
Licensing Information
● Cisco Nexus 9000 and 3000 Series NX-OS Switch License Navigator
● Cisco Nexus Smart Licensing Using Policy User Guide
To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus3k-docfeedback@cisco.com. We appreciate your feedback.
Legal Information
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2023 Cisco Systems, Inc. All rights reserved.