Cisco Nexus 3000 Series NX-OS Release Notes, Release 10.3(4a)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
Introduction
This document describes the features, issues, and exceptions of Cisco NX-OS Release 10.3(4a)M software for use on Cisco Nexus 3500 and 3600 platform switches.
The Cisco NX-OS Software Strategy and Lifecycle Guide provides details about the new Cisco NX-OS Software Release and Image-naming Convention.
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 |
| November 2, 2023 |
Cisco NX-OS Release 10.3(4a)M became available. |
New and Enhanced Software Features
There are no new and enhanced software features introduced in Cisco NX-OS Release 10.3(4a)M.
The are no new enhanced features listed below are existing features introduced in earlier releases but enhanced to support new platforms in Cisco NX-OS Release 10.3(4a)M.
Note: Beginning with Cisco NX-OS Release 10.3(4a)M, the existing logging rfc-strict 5424 command (optional) that enables the syslog protocol RFC 5424 is enhanced by adding a new keyword (full ) as follows: logging rfc-strict 5424 full. The addition of this keyword ensures complete compliance with the RFC 5424 standard for Syslog Protocol. However, if the values are not available for the [APP-NAME] [PROCID] [MSG-ID] [STRUCTRED-DATA] fields, then the nil value is indicated by a dash (-).
See Cisco Nexus 3548 Series NX-OS System Management Configuration Guide and Cisco Nexus 3600 NX-OS System Management Configuration Guide, Release 10.3(x).
Hardware Features
Cisco NX-OS Release 10.3(4a)M 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.4a.M.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 |
| Headline: On Nexus 3500 switch, service-reflect fails to forward MCAST traffic with *G1 to S2G2 translation configuration. Symptoms: Service-reflect MCAST traffic is not forwarded to receiver. Workarounds: Make sure that the receiver receives S2G2 to send joins all the time or use service-reflect configuration with specific S1 source. |
Resolved Issues
| Bug ID |
Description |
|
|
Headline: Cisco Nexus 3500 switch does not propagate correct PTP clock received from upstream to downstream devices. Symptoms: PTP clients receives incorrect clock information from Cisco Nexus 3500 switch that is working as a BC device. Workarounds: None. |
| Headline: eBGP-Removing template peer-policy under L2VPN EVPN address-family deletes prefixes. Symptoms: In a scenario where eBGP for L2VPN EVPN with rewrite-asn is used along with template peer-policy for L2VPN EVPN neighbor on Nexus 9000 or Nexus 3000 switches running Cisco NX-OS Release 10.2(4)F, after removing the template peer-policy under the L2VPN neighbor configuration, the Nexus deletes the rewrite-asn from BGP neighbor even though it is hardcoded under the neighbor config. Workarounds: Reconfigure affected neighbor or restart BGP <<<DISRUPTIVE. |
|
| Headline: Nexus 3550-T fails to forward L3 traffic between vPC VLANs. Symptoms: L3 traffic is not forwarded between vPC VLANs. Workarounds: Use multiple L2 vPC connected switches with one vPC VLAN on each switch. |
|
| Headline: Kernel Panic due to HR Timeout and SMC. Symptoms: Kernel panic logs are seen on the N3K-C3548P-XL switch. Workarounds: None. |
|
| Headline: MSDP peer flapping. Symptoms: MSDP performance issues may be observed if it is running in a VRF that is not enabled in BGP while BGP is configured globally. ● Adjacencies may flap due to keepalives expired, while packet captures indicate no drops. ● SA propagation may be significantly delayed, or SAs may never be received. ● The receive queue for MSDP TCP sockets in the show sockets connection command are full. Workarounds: Enable the MSDP VRF under the BGP process. No additional configuration such as address families or neighbors is required. |
|
| Headline: MAC learning issue after reloading with private VLAN configuration. Symptoms: MAC learning does not happen after reloading with private VLAN configuration. Workarounds: Perform any one of the following workarounds: 1st Workaround - 1. Delete the Primary and Secondary VLAN. 2. Delete the Interface level PVLAN configuration. 3. Add VLAN configuration again. 4. Add Interface configuration again. 5. MAC address is learned. 2nd Workaround - ● Add static MAC |
|
| Headline: Unexpected reload ipfib hap reset. Symptoms: During AM adjacency update, sometimes, the reprogramming of MPLS adjacencies goes in a loop and the system crashes. Workarounds: None. |
|
| Headline: Nexus 3548 switch does not display all SPAN sessions in SPAN drop output. Symptoms: Nexus 3548 switch does not display all SPAN sessions in the output of the show monitor session all drop command. Workarounds: Use the show monitor session X drop command for each SPAN session. |
|
| Headline: Configure Replace failed to restore configuration with hardware profile latency monitor. Symptoms: Configure Replace failed to restore the hardware profile latency monitor configuration. Workarounds: Add key value to the parameters. |
Device Hardware
The following tables list the Cisco Nexus 3500 and Cisco Nexus 3600 Series hardware that Cisco NX-OS Release 10.3(4a)M 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. From Cisco NX-OS Release 10.3(3)F, the following AC ports are supported on Cisco Nexus 36180YC-R (N3K-C36180YC-R):
● AC port-side exhaust (NXA-PAC-750W-PE)
● AC port-side intake (NXA-PAC-750W-PI)
The following table provides information about spares support:
● The Typical/Minimum port-side intake and fan speed percentage is 50% and the maximum port-side intake and fan speed percentage is 100%.
● The Typical/Minimum port-side exhaust and fan speed percentage is 70% and the maximum port-side exhaust and fan speed percentage is 100%.
For information about N3K-C36180YC-R, see Cisco Nexus 3600 Hardware Installation Guide. |
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
This document describes and provides links to the user documentation available for Cisco Nexus 3000 Series documentation. To find a document online, use one of the links in this section.
| Document Title |
Description |
| Cisco Nexus 3000 Series documentation |
|
| Cisco NX-OS Software Release and Image-naming Convention |
|
| Cisco Nexus 3000 and 9000 Series NXAPI REST SDK User Guide and API Reference |
Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference |
| ● Cisco Nexus 9000 and 3000 Series NX-OS Switch License Navigator |
Licensing Information |
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 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.