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.
This document describes the features, issues, and exceptions of Cisco NX-OS Release 10.2(3)F 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 |
April 26, 2022 |
New and Enhanced Software Features
There are no new software features introduced in Cisco NX-OS Release 10.2(3)F for Cisco Nexus 3000 series.
The enhanced feature listed below is an existing feature introduced in an earlier release but enhanced to support new platforms in Cisco NX-OS Release 10.2(3)F.
Enhanced Features |
|
Feature |
Description |
PVLAN support on 3600-R |
Added support for Private VLANs on Cisco Nexus 3600-R platform switches. For more information, see Cisco Nexus 3600 NX-OS Layer 2 Switching Configuration Guide, Release 10.2(3)F and Cisco Nexus 3600 NX-OS Verified Scalability Guide, Release 10.2(3)F. |
vPC Fabric Peering |
Added support for Cisco Nexus C36180YC-R and N3K-C3636C-R ToR platforms. For more information, see Cisco Nexus 3600 Series NX-OS VXLAN Configuration Guide, Release 10.2(x). |
Cisco NX-OS Release 10.2(3)F does not include any new hardware for the Cisco Nexus 3000 Series.
The following tables lists the open issues for Cisco Nexus 3000 Series switches in Cisco NX-OS Release 10.2(3)F. Click the Bug ID to search the Cisco Bug Search Tool for additional information about the bug.
Bug ID |
Description |
Headline: N9500-R/N3600-R hardware application counters may get corrupted Symptoms: N9500-R/N3600-R running 9.3(x) version of converged code may experience hardware counter corruption causing specific application counters to show incorrect information. Workarounds: Reload will clear the issue but the issue can resurface. |
|
Headline: N9500-R/N3600-R CoPP incorrectly matches fragmented UDP packet with UDP PTP port payload as PTP pkt Symptoms: N9500-R/N3600-R running 9.3.x or 10.2.x version of code matches incorrectly by CoPP redirect class mcast/ucast UDP fragmented packets with UDP PTP ports payload (319/320) as PTP packets. Workarounds: None |
|
Headline: PVLAN RACL filtering not happening for PVLAN SVI Symptoms: RACL filtering is not happening for PVLAN VLAN. (Traffic match not happening for PVLAN SVI.) Workarounds: None |
|
Headline: PVLAN Consistency checker failed for Primary VLAN Symptoms: PVLAN consistency checker failed for Primary VLAN in the latest 10.2.3 build Workarounds: None |
The following tables lists the resolved issues for Cisco Nexus 3000 Series switches in Cisco NX-OS Release 10.2(3)F. Click the Bug ID to search the Cisco Bug Search Tool for additional information about the bug.
Bug ID |
Description |
Headline: N9500-R/N3600 break link-local control-plane adj for connected L3 devices Symptoms: N9500-R/N3600 running 9.3.8 version of code breaks link-local control-plane adjacencies (e.g. OSPF) for connected L3 devices. When igmp snooping is disabled, link-local control-plane works but this prevents multicast traffic to be forwarded as pim cannot be enabled on SVI with disabled igmp snooping for respective vlan. |
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: www.cisco.com/go/trademarks. 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.
© 2022 Cisco Systems, Inc. All rights reserved.