Cisco Nexus 3000 Series NX-OS Release Notes, Release 10.3(2)F

Available Languages

Download Options

  • PDF
    (414.8 KB)
    View with Adobe Reader on a variety of devices
Updated:December 19, 2022

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.

Available Languages

Download Options

  • PDF
    (414.8 KB)
    View with Adobe Reader on a variety of devices
Updated:December 19, 2022
 

 

This document describes the features, issues, and exceptions of Cisco NX-OS Release 10.3(2)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

December 19, 2022

Cisco NX-OS Release 10.3(2)F became available.


 

New and Enhanced Software Features

The enhanced features listed below are existing features introduced in earlier releases but enhanced to support new platforms in Cisco NX-OS Release 10.3(2)F for Cisco Nexus 3000 series.

Enhanced Features

Product Impact

Feature

Description

Security

Source CoPP ACLs on Nexus 3600

Source IP based filtering in CoPP is now supported on Cisco Nexus 3600 platform switches (N3K-C36180YC-R and N3K-C3636C-R) switches.

 

For more information, see Cisco Nexus 3600 Series NX-OS Security Configuration Guide, Release 10.3(x).

Diagnostics and Serviceability

MPLS Consistency Checker

Beginning with this release, proactive consistency checker supports MPLS route consistency check.

 

For more information, see Cisco Nexus 3600 Series NX-OS Label Switching Configuration Guide, Release 10.3(x).

Licensing

Support SLP on Non-Management VRF

Smart Licensing using Policy is now supported on non-management VRF for smart transport and CSLU mode of transport.

 

For more information, see Cisco Nexus 9000 and 3000 Series NX-OS Smart Licensing Using Policy User Guide.

Support for Source Interface for call home

You can now optionally specify a source interface to send Smart Call

Home messages over HTTP.

 

For more information, see Cisco Nexus 9000 and 3000 Series NX-OS Smart Licensing Using Policy User Guide.

CSSM to display PI hostname

The CSSM now displays the host name of the Product Instance (PI) instead of UDI.

 

For more information, see Cisco Nexus 9000 and 3000 Series NX-OS Smart Licensing Using Policy User Guide.

 

Hardware Features

Cisco NX-OS Release 10.3(2)F does not include any new hardware for the Cisco Nexus 3000 Series.

Release Image

Cisco Nexus 3000 Series platforms support only 64-bit image. The 64-bit Cisco NX-OS image filename begins with "nxos64-msll” (for example, nxos64-msll.10.3.2.F.bin) and this image is supported on Cisco Nexus 3600 series fixed switches and Cisco Nexus 3500-XL series witches. 32-bit image is no longer supported.

Open Issues 

Bug ID

Description

CSCwd90070

Headline: Cisco Nexus 3548 unicast fails after reload in Warp mode.

Symptoms: After reloading the Nexus 3548 on Cisco NX-OS Release 9.3(9), the switch fails to forward few traffic flows. UDP and TCP is impacted but ICMP is not impacted.

Workarounds: None

CSCwd89936

Headline: Nexus 3500 hardware fails to program L3 ltl-index for few mcast groups after mcast flow stop/start.

Symptoms: After mcast flow stops for about 3 minutes, l3-ltl ages on mtc. Then starting the mcast flow again does not program l3-ltl again.

Workarounds: None

CSCwd68210

Headline: After upgrading Cisco Nexus 9500, Cisco Nexus 9000 and Cisco Nexus 3000 Switch 100Gig Interface does not come up.

Symptoms: Interface doesn't come up after upgrading Nexus 9500 from Cisco NX-OS Release 9.3(4) to 9.3(8). SFP used is the QSFP-100G-CWDM4-S Link between Nexus 9000: N9K-X9736C-FX and leaf: N3K-C36180YC-R.

Workarounds: None

CSCwd86850

Headline: Cisco Nexus 3548 - L3 Adjacency is not programmed properly in hardware.

Symptoms: L3 adjacency is mis-programmed in hardware, and routed packets to destination hosts are dropped. Issue is seen on single or multiple hosts.

Workarounds: Run the clear ip arp force-delete command for the affected entries to trigger ARP learning again and refresh the HW entry. However, running the clear ip arp force-delete command for an entire subnet/VLAN may cause a couple of seconds of disruption.

CSCwd88051

Headline: Cisco Nexus 3000 Spanning-tree creates an instance for interface that is a part of a port-channel.

Symptoms: Spanning creates an instance on the interface that is a part of a port-channel. This causes STP disputes on the root bridge.

Workarounds: Reload.

CSCwd86342

Headline: SPAN traffic received from Cisco Nexus 9300 is dropped on Cisco Nexus 3548.

Symptoms: On Cisco Nexus 9000 SPAN is configured and the SAPN destination interface is configured to Cisco Nexus 3548. On Cisco Nexus 3548, traffic is received and dropped. The drops are verified using the show hardware internal errors module 1 command. However, SPAN/ERSPAN traffic that Cisco Nexus 3548 should have received traffic is not seen.

Workarounds: To resolve the issue, replace Cisco Nexus 9000 with Catalyst or add Catalyst switch in between Cisco Nexus 9000 and Cisco Nexus 3000.

                                                                              

Resolved Issues

Bug ID

Description

CSCwc82191

Headline: Cisco Nexus 3500 fails to update L2 ltl-index for few mcast groups due to exhausted ltl-index pool.

Symptoms: After Nexus 3000 receives IGMP report, mtc does not program OIF into l2-ltl.

Workarounds: Reload the switch to recover.

CSCwd07045

Headline: Cisco Nexus 3000 can only configure up to three syslog servers.

Symptoms: A Nexus 3000 series switch running Cisco NX-OS Release 7.x, 9.x software shows an error message when trying to configure more than three logging servers.

Workarounds: None

CSCwd13945

Headline: Show hardware profile buffer monitor detail last 10 -or- last 15 displays repeated output.

Symptoms: Running the following command on Nexus 3500 switch running Cisco NX-OS Release 9.3(9) does not show the full interface output with "last 10" -or- "last 15" keyword. However, last one keyword functions as expected:
show hardware profile buffer monitor detail last 10:
Ethernet 1/1-24
then it repeats starting at eth 1/1
show hardware profile buffer monitor detail last 15:
Ethernet 1/1-16
then it repeats the same output twice
(Eth 1/1-16)
show hardware profile buffer monitor detail last 1:
functions as expected and shows all interfaces.

Workarounds: Use the show hardware profile buffer monitor detail last 1 command.

CSCwd15533

Headline: Removal of "flowcontrol receive on" stops pause frames from being counted on Cisco Nexus 3548.

Symptoms: Receipt of a pause frame where "flowcontrol receive on" was previously configured. The pause frame counter increment on the switch is not seen. However, the input error counter continues to increment.

Workarounds: Reload switch after removing "flowcontrol receive on" to acknowledge Rx pause frames per the interface counters.

CSCwd38617

Headline: N3K-C3548 punts DHCP/BOOTP packets to CPU for non-relay enabled VLANs.

Symptoms: Observe DHCP packets in ethanalyzer for a VLAN that either has no SVI or is not configured for DHCP relay. Packets are counted as hits in the output of show system internal access-list input entries detail command for dhcp relay entries in another VLAN.

Workarounds: None

CSCwd47148

Headline: Smart licensing - Callhome HTTP proxy does not work when it is defined using IPv6 address.

Symptoms: Communications with CSSM portal do not work when using IPv6 HTTP proxyDevice reports:
%LICMGR-3-LOG_SMART_LIC_COMM_FAILED: (pid=xxxx) Communications failure with the Cisco Smart Software Manager (CSSM) : Fail to send out Call Home HTTP message

Workarounds: Instead of referencing the HTTP proxy using IPv6, use HOSTNAME and define static IPv6 host config. For example,

Instead of:

***********
callhome
...
  transport http proxy server X:X::X:X port 8080
***********

use:
***********
ipv6 host test.proxy.com X:X::X:X
callhome
...
  transport http proxy server test.proxy.com port 8080
***********

CSCvy73558

Headline: Callhome: Unable to remove http destination for the default CiscoTAC-1 profile on non-DME Cisco Nexus 3000.

Symptoms: On non-DME Cisco Nexus 3000 devices (with 4GB of RAM), it is not possible to remove or modify default or user-configured Callhome http destinations for the default CiscoTAC-1 profile. At the same time, no such issue is seen when trying to remove or modify any Callhome email-addr destinations for the same default CiscoTAC-1 profile. Thus, the issue is seen only for the default CiscoTAC-1 profile, not for any non-default Callhome profiles.

Workarounds: None

CSCwc71075

Headline: When using authentication and issuing no feature nv overlay, OSPFv3 neighborship is brought down.

Symptoms: When you enable feature nv overlay on Cisco Nexus 3000 and then disable it by issuing "no feature nv overlay" all existing OSPFv3 neighborships are going to DOWN state.

Workarounds: Remove OSPFv3 authentication under interface.

CSCwc88680

Headline: Optimize Libutil_is_dme_enabled to accommodate timing critical paths.

Symptoms: In rare conditions, an STP topology change occurs.

Workarounds: None

Device Hardware

The following tables list the Cisco Nexus 3500 and Cisco Nexus 3600 Series hardware that Cisco NX-OS Release 10.3(2)F supports. For additional information about the supported hardware, see the Hardware Installation Guide for your Cisco Nexus 3500 and Cisco Nexus 3600 Series devices.

Cisco Nexus 3500 Switches

Product ID

Description

N3K-C3524P-XL

Cisco Nexus 3524-XL switch

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 40Gigabit 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.

 

Upgrade and Downgrade

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.  

MIB Support

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 

Supported Optics

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/interfacesmodules/transceiver-modules/products-installation-guides-list.html.

Related Content

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 NXAPI REST SDK User Guide and API Reference.

Licensing Information

   Cisco NX-OS Licensing Guide

   Cisco Nexus 9000 and 3000 Series NX-OS Switch License Navigator

   Cisco Nexus Smart Licensing Using Policy User Guide

 

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus9k-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 URLwww.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.

Learn more