Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes for Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c)
Available Languages
Table of Contents
Cisco Nexus 5000 Series Switches
Cisco Nexus 2000 Series Fabric Extenders
Cisco Nexus Unified Port Technology
Reversed Airflow and DC Power Options
NEBS Compliance for the Cisco Nexus 2248TP and Cisco Nexus 2232PP Fabric Extenders
Unified Port Configurations on Cisco Nexus 5500 Platform Switches
Upgrading or Downgrading to a New Release
Upgrade and Downgrade Guidelines
Supported Upgrade and Downgrade Paths
Upgrading the Power Sequencer on the Cisco Nexus 5010 and Cisco Nexus 5020 Switches
Configuration Synchronization Limitation
Limitations on the Cisco Nexus 5010 and Cisco Nexus 5020
SPAN Limitations on Fabric Extender Ports
Checkpoint and Configuration Rollback Limitation
Resolved Caveats—Cisco NX-OS Release5.0(3)N1(1c)
Resolved Caveats—Cisco NX-OS Release5.0(3)N1(1b)
Installation and Upgrade Guides
Obtaining Documentation and Submitting a Service Request
Cisco Nexus 5000 Series
and Cisco Nexus 2000 Series Release Notes,
for Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c)
Current Release: NX-OS Release 5.0(3)N1(1c)
Deferred Release: NX-OS Release 5.0(3)N1(1b)
Deferred Release: NX-OS Release 5.0(3)N1(1a)
Deferred Release: NX-OS Release 5.0(3)N1(1)
This document describes the features, caveats, and limitations for Cisco Cisco Nexus 5000 Series switches and the Cisco Nexus 2000 Series Fabric Extenders. Use this document in combination with documents listed in the “Related Documentation” section.
Note
Release notes are sometimes updated with new information about restrictions and caveats. See the following website for the most recent version of the Cisco Cisco Nexus 5000 Series and Cisco Nexus 2000 Series release notes: http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/release/notes/Nexus_5000_Release_Notes.html
Note
Created NX-OS Release 5.0(3)N1(1a) release notes.
Added: CSCtn70380 and CSCtn76613.
Updated: Supported Upgrade and Downgrade Paths.
Updated: Changed Software Features.
Added: CSCtn79039, CSCtn82286, and CSCtn87115.
Published release notes for Cisco NX-OS Release 5.0(3)N1(1a).
Updated Upgrade and Downgrade Guidelines to include information about upgrading or downgrading to Cisco NX-OS Release 4.1(3).
Updated Limitations with Cisco Nexus 2148 Fabric Extender information.
Updated Limitations section with IGMP snooping Limitation.
Corrected Unified Port Module reference to N55-M16UP.
Updated Fabric Extender Scaling.
Created NX-OS Release 5.0(3)N1(1b) release notes.
Added CSCtn87115, CSCto23248, CSCto43675, and CSCto50140.
Added CSCto63412.
Updated CSCto23248.
Moved CSCtn79039 to Resolved list.
Added Unified Port Configurations on Cisco Nexus 5500 Platform Switches.
Added CSCto34674 and CSCtq04991 to Resolved list.
Added Note about RJ45 ports to Layer 3 Routing Modules.
Added Converged Network Adapters to Hardware Supported section.
Updated Limitations on the Cisco Nexus 5010 and Cisco Nexus 5020.
Added CSCtq13290 to Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) Open Caveats .
Introduction
The Cisco NX-OS software is a data center-class operating system built with modularity, resiliency, and serviceability at its foundation. Based on the industry-proven Cisco MDS 9000 SAN-OS software, Cisco NX-OS helps ensure continuous availability and sets the standard for mission-critical data center environments. The highly modular design of Cisco NX-OS makes zero-effect operations a reality and enables exceptional operational flexibility.
Several new hardware and software features are introduced for the Cisco Nexus 5000 Series switch and the Cisco Nexus 2000 Series Fabric Extender (FEX) to improve the performance, scalability, and management of the product line. Cisco NX-OS Release 5.0 also supports all hardware and software supported in Cisco NX-OS Software Release 4.2.
Cisco Nexus 5000 Series Switches
The Cisco Nexus 5000 Series switches include a family of line-rate, low-latency, lossless 10-Gigabit Ethernet, Cisco Data Center Ethernet, Fibre Channel over Ethernet (FCoE), and now native Fibre Channel switches for data center applications. The Cisco Nexus 5000 Series includes the Cisco Nexus 5500 Platform and the Cisco Nexus 5000 Platform.
Cisco NX-OS Software Release 5.0(3)N1(1b) introduces two new Cisco Nexus 5500 Platform switches that extend the versatility of the data-center class Cisco Nexus 5000 Series switches and provide higher density, lower latency, multilayer services.
The Cisco Nexus 5500 Platform includes the following switches:
For information about the new Cisco Nexus 5596UP switch and Cisco Nexus 5548UP switch, see the “New Hardware Features” section.
The Cisco Nexus 5000 Platform includes the following:
For information about the Cisco Nexus 5000 Series, see the Cisco Nexus 5000 Series and Cisco Nexus 5500 Platform Hardware Installation Guide.
Cisco Nexus 2000 Series Fabric Extenders
The Cisco Nexus 2000 Series FEX is a highly scalable and flexible server networking solution that works with the Cisco Nexus 5000 Series switches to provide high-density and low-cost connectivity for server aggregation. Scaling across 1-Gigabit Ethernet, 10-Gigabit Ethernet, unified fabric, rack, and blade server environments, the FEX is designed to simplify data center architecture and operations.
The FEX integrates with its parent Cisco Nexus 5000 Series switch which allows zero-touch provisioning and automatic configuration. The FEX provides a single point of management that supports a large numbers of servers and hosts that can be configured with the same feature set as the parent Cisco Nexus 5000 Series switch, including security and quality of service (QoS) configuration parameters. Spanning Tree Protocol (STP) is not required between the Fabric Extender and its parent switch, because the Fabric Extender and its parent switch allow you to enable a large multi-path, loop-free, active-active topology.
Software is not included with the Fabric Extender. Cisco NX-OS software is automatically downloaded and upgraded from its parent switch. For information about configuring the Cisco Nexus 2000 FEX, see the “Configuring the Fabric Extender” chapter in the Cisco Nexus 5000 Series Layer 2 Switching Configuration Guide.
System Requirements
This section includes the following topics:
Hardware Supported
The Cisco NX-OS software supports the Cisco Nexus 5000 Series. You can find detailed information about supported hardware in the Cisco Nexus 5000 Series Hardware Installation Guide.
Table 2 shows the hardware supported by Cisco NX-OS Release 5.0(x) software.
Table 2 Hardware Supported by Cisco NX-OS Release 5.0(x) Software
Generation-1 (Pre-FIP) CNAs1
For information about Cisco Nexus 5000 Series support for Fabric Manager, see the “Compatibility with Cisco Nexus 5000 Series Switches” section in the Release Notes for Cisco Fabric Manager.
New and Changed Features
This section describes the new features introduced in Cisco NX-OS Release 5.0(3)N1(1b). This section includes the following topics:
- Cisco Nexus Unified Port Technology
- New Hardware Features
- New Software Features
- Changed Software Features
Cisco Nexus Unified Port Technology
Beginning in Cisco NX-OS Release 5.0(3)N1(1b), Cisco introduces unified port technology. Cisco Nexus unified ports allow you to configure a physical port on a Cisco Nexus 5500 Platform switch as a 1/10-Gigabit Ethernet, Fibre Channel over Ethernet (FCoE), or 1-, 2-, 4-, 8-Gigabit native Fibre Channel port.
Currently, most networks have two types of switches for different types of networks. For example, LAN switches carry Ethernet traffic up to Catalyst switches and SAN switches carry FC traffic from servers to MDS switches. With unified port technology, you can deploy a unified platform, unified device, and unified wire approach. Unified ports allow you to move from an existing segregated platform approach where you choose LAN and SAN port options to transition to a single, unified fabric that is transparent and consistent with existing practices and management software. A unified fabric includes the following:
- Unified platform—Uses the same hardware platform and the same software code level and certifies it once for your LAN and SAN environments.
- Unified device—Runs LAN and SAN services on the same platform switch. The unified device allows you to connect your Ethernet and Fibre Channel cables to the same device.
- Unified wire—Converges LAN and SAN networks on a single converged network adapter (CNA) and connects them to your server.
A unified fabric allows you to manage Ethernet and FCoE features independently with existing Cisco tools.
The new Cisco Nexus 5548UP switch and the Cisco Nexus 5596UP switch provides built-in unified port technology. In addition, a new unified port expansion module and two Layer 3 modules increase the benefits of a deployed unified fabric.
New Hardware Features
The Cisco Nexus 5500 Platform switches, FEXs, and unified port extender modules available in this release provide the following benefits:
- Scalability—Increased FEX, MAC address table, VLAN, and multicast scalability with up to 24 attached FEXs, an increased limit of 16,000 to 32,000 MAC addresses, a 4000 VLAN limit, and 4000 multicast groups.
- Performance—Highest density 10G switch with wire-speed performance, low latency and full 96 ports of 10G line rate.
- Versatility—Both universal port switches support Layer 3 routing and they are Cisco Layer 2 FabricPath-ready.
- Flexibility—Unified ports that allow you to customize configuration modes for each port.
Cisco Nexus 5596UP Switch
The Cisco Nexus 5596UP switch is an Ethernet, Fibre Channel, and FCoE unified fabric switch with the following features:
- 2 RU 10-Gigabit Ethernet, Fibre Channel, and FCoE switch that offers up to 1920 Gbps of throughput.
- 48 fixed ports (all are unified-port capable).
- Up to 96 unified-ports (48 fixed unified ports and three installed unified-port expansion modules).
- Three expansion slots that are used to increase the number of 10-Gigabit Ethernet and FCoE ports or to connect to Fibre Channel SANs with 1-, 2-, 4-, 8-Gbps Fibre Channel switch ports.
- 32,000 MAC addresses of which 24,000 are available for unicast.
- Low-latency cut-through design that provides predictable, consistent traffic latency regardless of packet size, traffic pattern, or enabled features on 10-Gigabit Ethernet interfaces.
- Line-rate traffic throughput on all ports.
- Extension through the Cisco Nexus 2000 Series.
The Cisco Nexus 5596UP supports the following expansion modules:
- Unified port module that provides up to 16 1- or 10-Gigabit Ethernet and FCoE ports using SFP+ transceivers or up to 16 1-, 2-, 4-, 8-Gbps native Fibre Channel port connectivity using SFP+ and SFP transceivers. In unified port modules, the use of 1- and 10-Gigabit Ethernet or 1-, 2-, 4-, 8-Gbps Fibre Channel ports is mutually exclusive but configurable for any of the 16 physical ports per module.
- Layer 3 module that provides up to 160 Gbps of Layer 3 forwarding capability (240 mpps) that can be shared by all the I/O ports in the switch.
- Ethernet module that provides 16 1- or 10-Gigabit Ethernet and FCoE ports using SFP+ transceivers.
- FCoE and Ethernet module that provides 8 1- or 10-Gigabit Ethernet and FCoE ports using SFP+ transceivers, and 8 1-, 2-, 4-, 8-Gbps native Fibre Channel ports using SFP+ and SFP transceivers.
Cisco Nexus 5548UP Switch
The Cisco Nexus 5548UP switch is an Ethernet, Fibre Channel, and FCoE unified fabric switch that offers the following features:
- 1 RU 1- or 10-Gigabit Ethernet, Fibre Channel, and FCoE switch that offers up to 960-Gbps throughput.
- Up to 48 unified-ports (32 fixed unified ports and 16 ports with an installed unified-port expansion module).
- 32 fixed SFP+ ports and up to 1 expansion module.
- Hardware that is capable of 1- or 10-Gigabit Ethernet.
- 32,000 MAC address table entries.
- Low-latency cut-through design that provides predictable, consistent traffic latency regardless of packet size, traffic pattern, or enabled features on 10-Gigabit Ethernet interfaces.
- Line-rate traffic throughput on all ports.
- Extension through the Cisco Nexus 2000 Series.
Cisco Nexus 5548UP supports the following expansion modules:
- Unified port module that provides up to 16 1- or 10-Gigabit Ethernet and FCoE ports using SFP+ transceivers or up to 16 1-, 2-, 4-, 8-Gbps native Fibre Channel ports using SFP and SFP transceivers. In unified port modules, the use of 1- or 10-Gigabit Ethernet or 1-, 2-, 4-, 8-Gbps Fibre Channel ports is mutually exclusive but configurable for any of the 16 physical ports per module.
- FCoE and Ethernet module that provides 8 1- or 10-Gigabit Ethernet and FCoE using SFP transceivers and 8 1-, 2-, 4-, 8-Gbps native Fibre Channel ports using SFP+ and SFP transceivers.
- Ethernet module that provides 16 1- or 10-Gigabit Ethernet and FCoE expansion module using SFP+ transceivers.
Expansion Modules
Beginning with Cisco NX-OS Release 5.0(3)N1(1b), one new unified port expansion module and two new Layer 3 routing modules are available:
Unified Port Module
The new unified port module (N55-M16UP) has the following features:
- Supports the Cisco Nexus 5548P, Nexus 5548UP, and Nexus 5596UP switches.
- 16 1-, 2-, 4-, 8-Gigabit native Fibre Channel ports.
- 1- or 10-Gigabit Ethernet ports with FCoE FEX connectivity.
- SFP+ and SFP transceiver support.
- Flexibility to configure any port in Ethernet, Fibre Channel, or FCoE mode.
- No additional licensing is required; an installed and active FCoE license is used.
- Unified ports are colored orange to easily identify them.
Layer 3 Routing Modules
Two new Layer 3 routing modules are introduced in this release:
- Cisco Nexus 5548P and Nexus 5548UP switch daughter card (N55-D160L3).
- Cisco Nexus 5596UP expansion module (N55-M160L3).
The Cisco Nexus 5548P and Nexus 5548UP daughter card (N55-D160L3) has the following features:
- Provides Layer 3 routing capabilities on all 48 10-Gigabit Ethernet ports.
- Enables SVIs on all switch and FEX ports.
- Provides 160 Gbps Layer 3 processing.
Note
The Cisco Nexus 5596UP (N55-M160L3) expansion module has the following features:
- Provides Layer3 routing capabilities on all 96 ports.
- Enables SVIs on all switch and FEX ports.
- Provides 160-Gbps Layer 3 processing expandable to 480-Gbps processing. (This module functions as a 48-port module capable of up to 160 Gbps of Layer 3 forwarding capability (240 mpps) that can be shared by all the I/O ports on the switch.)
Note
1-Gigabit Transceiver Support
Beginning with Cisco NX-OS Release 5.0(3)N1(1b), the following 1-Gigabit optical transceivers are supported on all SFP+ ports on the Cisco Nexus 5500 platform, unified port expansion module, and Layer 2 routing modules:
Reversed Airflow and DC Power Options
The Cisco Nexus 2200 Series Fabric Extenders offer a choice of standard airflow (port-side exhaust) and reversed airflow (port-side intake), as well as a choice for AC and DC power options.
Table 3 shows the part numbers and descriptions of the available Cisco Nexus 2000 Series FEX airflow and power options. You can order standard airflow with dual AC power supplies, reversed airflow with dual AC power supplies, or standard airflow with dual DC power supplies package. The default option is the standard airflow with dual AC power supply.
Note
Table 3 Cisco Nexus 2000 Series FEX Reversed Airflow and Power Options
N2K-C2248-FAN-B(=)2
Cisco Nexus 2200 Series FEX Gigabit Ethernet Fan, Reversed Airflow (port-side intake)
Cisco Nexus 2200 Series FEX 10-Gigabit Ethernet Fan, Reversed Airflow (port-side intake)
Cisco Nexus 2200 Series FEX AC Power Supply, Reversed Airflow (port-side intake)
Cisco Nexus 2200 Series FEX 400W DC Power Supply, Standard Airflow (port-side exhaust)
NEBS Compliance for the Cisco Nexus 2248TP and Cisco Nexus 2232PP Fabric Extenders
The Cisco Nexus 2248TP and Cisco Nexus 2232PP Fabric Extenders (starting with hardware version 3) meet the NEBS level 3 standard standards. To determine the hardware version, use the show inventory command. For important information about NEBS Compliance and ETSI environmental requirements for the Cisco Nexus 2248TP and Cisco Nexus 2232PP Fabric Extenders, see the Regulatory Compliance and Safety Information for the Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders.
Fabric Extender Scaling
Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) supports the following on Cisco Nexus 5500 Platform switches (Nexus 5548, Nexus 5548UP, and Nexus 5596UP switches):
Note
For more information please refer to the Cisco Nexus 5000 Series Configuration Limits for Cisco NX-OS Release 5.0(3)1(1a).
New Software Features
Cisco NX-OS Release 5.0(3)N1(1b) includes the following new or changed software features:
Layer 3 Unicast Routing
Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) supports IP version 4 (IPv4) and the following routing protocols:
- Static routing
- Routing Information Protocol Version 2 (RIPv2)
- Enhanced Interior Gateway Routing Protocol (EIGRP)
- Open Shortest Path First (OSPF) Protocol Versions 2 (IPv4)
- Border Gateway Protocol (BGP)
- First-Hop Redundancy Protocols (FHRP) (HSRP/VRRP)
- Up to 8000 IPv4 host routing table entries (/32 entries)
- Up to 8000 IPv4 longest prefix match routing table entries
All protocols support Ethernet interfaces, virtual interfaces (VLAN interfaces), subinterfaces, and port channels.
For more information, see the Cisco Nexus 5000 Series NX-OS Unicast Routing Configuration Guide, Release 5.0(3)N1(1).
Layer 3 Multicast Routing
The following multicast routing protocols are supported in this release:
- Protocol Independent Multicast Source Specific Multicast IPv4 (PIM-SM)
- Internet Group Management Protocol (IGMP) Versions 2 and 3 router role
- Multicast Source Discovery Protocol (MSDP)
- Up to 2000 IGMP Groups
The implementations of these protocols are fully compliant with the latest standards and include 4-byte autonomous system numbers (ASNs) and incremental Shortest Path First (SPF). All unicast protocols support Non-Stop Forwarding Graceful Restart (NSF-GR). All protocols support all interface types, including Ethernet interfaces, switched virtual interfaces (VLAN interfaces) and subinterfaces, port channels, tunnel interfaces, and loopback interfaces.
Note
For more information, see the Cisco Nexus 5000 Series NX-OS Multicast Routing Configuration Guide, Release 5.0(3)N1(1).
Segmentation
Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) supports virtual route forwarding (VRF), VRF-lite (IP VPN), VRF-aware unicast, and VRF-aware multicast.
Quality of Service
Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) supports the following QoS features:
Redundancy
Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) supports Hot-standby Routing Protocol (HSRP) and Virtual Routing Redundancy Protocol (VRRP).
Licensing
The Cisco NX-OS licensing feature allows you to access premium features on the device after you install the appropriate license for that feature. Any feature not included in a license package is bundled with the Cisco NX-OS software and is provided to you at no extra charge.
Licensing Grace Period
You can enable most features without installing a license. The Cisco NX-OS software provides a grace period for most features during which time you can try out a feature before purchasing its license.
The Layer 3 features do not have a grace period and require an installed Layer 3 Base license to use the routing features.
Beginning with Cisco NX-OS Release 5.0(3)N1(1b), two new Layer 3 licenses are available:
Layer 3 Base License
The Layer 3 base license (N55-BAS1K9) is included with the Cisco Nexus 5500 Platform switch. The license provides the following support:
Connected, Static, RIPv2, OSPF (256 Dynamically Learnt Routes), EIGRP-Stub, HSRP, VRRP, IGMPv2/3, PIMv2, RACLs, uRPF, VRF-Lite.
Layer 3 LAN-Enterprise License
The Layer 3 LAN Enterprise license (N55-LAN1K9) includes the following:
Note
For detailed information about the features that require licensing and Cisco NX-OS license installation, see the Cisco NX-OS Licensing Guide.
For information about troubleshooting licensing issues, see the Cisco Nexus 5000 Series NX-OS Troubleshooting Guide.
Network Time Protocol (NTP)
Network Time Protocol (NTP) configuration is currently not provided in the Cisco Nexus 5000 Series NX-OS System Management Configuration Guide.
For more information on NTP commands, see the Cisco Nexus 5000 Series NX-OS System Management Command Reference.
Rate Limited SPAN
The Rate Limited SPAN feature allows you to rate-limit the SPAN traffic to 1Gbps across the entire monitor session to avoid impacting the monitored production traffic. Use the switchport monitor rate-limit 1G command to set the rate limit. This feature is not necessary and not supported on the Nexus 5500 Platform.
For more information about these features, see the Cisco Nexus 5000 Series and the Cisco Nexus 2000 Series documentation listed in the“Related Documentation” section.
Changed Software Features
The following software features have changed in this release:
- Beginning with Cisco NX-OS Release 5.0(3)N1(1b), HTTP Server is not supported.
- Device Manager is no longer packaged with Cisco Nexus 5000 NX-OS releases. You can download Fabric Manager/DCNM-SAN software (which contains Device Manager) directly from Cisco.com. For additional information, see the Release Notes for Cisco Fabric Manager.
Unified Port Configurations on Cisco Nexus 5500 Platform Switches
Unified ports allow you to configure ports as Ethernet, native Fibre Channel or FCoE ports. By default, the ports are Ethernet ports but you can change the port mode to Fibre Channel on the following unified ports:
- Any port on the Cisco Nexus 5548UP switch or the Cisco Nexus 5596UP switch.
- The ports on the Cisco N55-M16UP expansion module that is installed in a Cisco Nexus 5548P switch.
This example shows how to configure a unified port on a Cisco Nexus 5548UP switch or Cisco Nexus 5596UP switch:
This example shows how to configure a unified port on a Cisco N55-M16UP expansion module:
You must configure Ethernet ports and FC ports in a specified order:
- FC ports must be configured from the last port of the module.
- Ethernet ports must be configured from the first port of the module.
If the order is not followed, the following errors are displayed:
On a Cisco Nexus 5548UP switch, the 32 ports of the main slot (slot1) are unified ports. The Ethernet ports start from port 1/1 to port 1/32. The FC ports start from port 1/32 backwards to port 1/1.
This example shows how to configure 20 ports as Ethernet ports and 12 as FC ports:
Upgrading or Downgrading to a New Release
This section describes the upgrade and downgrade paths that are supported for Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) on the Cisco Nexus 5000 Series switch.
This section includes the following topics:
- Upgrade and Downgrade Guidelines
- Supported Upgrade and Downgrade Paths
- Upgrading the Power Sequencer on the Cisco Nexus 5010 and Cisco Nexus 5020 Switches
Upgrade and Downgrade Guidelines
The following guidelines apply to Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) for the Cisco Nexus 5000 Series switches:
- Do not change any configuration settings or network settings during the upgrade. Any changes in the network settings may cause a disruptive upgrade.
- Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) are ISSU-compatible with NX-OS Release 4.2(1)N1(1) and later releases.
- Downgrading from NX-OS Release 5.0(2) to NX-OS Release 4.2(1) is disruptive.
- Upgrading from NX-OS Release 4.2(1) to NX-OS Release 5.0(2) is a nondisruptive upgrade (ISSU).
- Upgrading from a Cisco NX-OS Release 4.2(1)-based release to NX-OS Release 5.0(2)N1(1) is nondisruptive.
- Downgrading from Cisco NX-OS Release 5.0(2)N1(1) to a previous release is disruptive.
- When a Layer 3 license is installed, the Cisco Nexus 5500 Platform does not support an ISSU. Hot swapping a Layer 3 module is not supported.
Supported Upgrade and Downgrade Paths
Table 4 shows the upgrade and downgrade possibilities for Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c):
Upgrading the Power Sequencer on the Cisco Nexus 5010 and Cisco Nexus 5020 Switches
Under certain conditions, a voltage spike that exceeds the system voltage guard band and glitch filter settings may result in a power cycle of the system mezzanine board which results in the failure of ports on the mezzanine board. To solve the issue, you need to upgrade to Cisco NX-OS Release 5.0(2)N1(1) and make sure that the power sequencer has been upgraded to v1.2 using the show version command. Follow the power sequencer upgrade procedure to upgrade the power sequencer to v1.2 and to work around CSCsy21017 and CSCth33969.
If you upgrade the switch to Cisco NX-OS Release 5.0(2)N1(1), but do not power cycle the switch following this procedure, even though the switch has instructions for the power sequencer upgrade, the power sequencer is not upgraded. The show version command output displays a v1.2 power sequencer, but that only indicates that the power sequencer upgrade instructions have been programmed. If you cannot confirm a power cycle, We recommend that you perform a power off/on to ensure the power sequencer is upgraded.
To upgrade the power sequencer with Cisco NX-OS Release 5.0(2)N1(1), follow these steps:
Note
Step 1
Step 2
After completing the installation, the system reloads and displays a Cisco NX-OS Release 5.0(2)N1(1) image.
Step 3
Step 4
Step 5
Limitations
This section describes the limitations for Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c).
- When upgrading from Cisco NX-OS Release 4.2(1)N1(1) and earlier releases, to any release, the policy description is lost. This problem does not occur when upgrading from Cisco NX-OS Release 4.2(1)N1(1) and later releases. After an upgrade, We recommend that you reconfigure the policy description. For details, see CSCth14225.
- Starting with Cisco NX-OS Release 4.2(1)N2(1), LACP fast timers are supported. If you downgrade to an earlier release that does not support this feature, entering the install all command displays the following warning:
Before downgrading to an earlier release, change the LACP rate to normal. If you ignore the warning and force the installation, then it is possible that the leftover LACP rate fast configuration would still be active with previous releases of software but the behavior would be unpredictable and link flap might occur. We recommend that you change the LACP rate setting to normal. For details, see CSCth93787.
- When an FC SPAN destination port is changed from SD to F mode and back to SD mode on a NPV switch, the port goes into an error-disabled state. Perform a shut/no-shut after the mode change recovers the port. This issue occurs only in NPV mode. For details, see CSCtf87701.
- If you configure a Cisco Nexus 2248TP port to 100 Mbps instead of autonegotiation, autonegotiation does not occur, which is expected behavior. Both sides of the link should be configured to both hardwired speed or both autonegotiate.
no speed —Autonegotiates and advertises all speeds (only full duplex)
speed 1000 —Autonegotiates only for a 802.3x pause
speed 100 —Does not autonegotiate; pause cannot be advertised. The peer must be set to not autonegotiate and fix at 100 Mbps (similar to the N2248TP)
- Given the implementation of a single CPU ISSU, the STP root on the PVST region with switches on an MST region is not supported. The PVST simulation on the boundary ports go into a PVST SIM inconsistent blocked state that breaks the STP active path. To work around this issue, move all STP roots on the MST region. However, the work around causes a nondisruptive ISSU to fail because Non-Edge Designated Forwarding Ports are required for an ISSU. For additional information, see CSCtf51577. For information topologies that a nondisruptive upgrade is supported, see to the Cisco Nexus 5000 Series NX-OS Upgrade and Downgrade Guide.
- IGMP queries sent in CSCtf94558 are group-specific queries that are sent with the destination IP/MAC address as the group's address.
GS queries are sent for IP address: 224.1.14.1 to 224.1.14.100 [0100.5E01.0E01 to 0100.5E01.0E64]
These are not link-local addresses. By default, they are not flooded by the hardware into the VLAN. They are sent only to the ports that have joined this group.
This is expected behavior during an ISSU.
In another scenario, the IGMP global queries [dest IP 224.0.0.1] get flooded correctly in the VLAN.
Group-specific queries are not forwarded to ports other than the one that joined the group during ISSU. The reason to forward group-specific queries toward hosts is to avoid having them leave the group. However, if a group has not joined the group, then this is not an issue. If there is an interface that has joined the group, then the queries are expected to make it to the host. While the behavior is different when ISSU is not occurring, it is sufficient and works as expected and there is no impact to traffic. For details, see CSCtf94558.
- The meaning of an MTU configuration has changed in Cisco NX-OS Release 4.2(1)N1(1) and earlier releases. In releases earlier than Cisco NX-OS Release 4.2(1)N1(1), the configured MTU included the Ethernet payload and Ethernet headers. In Cisco NX-OS Release 4.2(1)N1(1), the configured MTU includes only the Ethernet payload and not the Ethernet headers. When upgrading or downgrading between Cisco NX-OS Release 4.2(1)N1(1) and earlier releases, Cisco NX-OS automatically converts the configuration to address this semantic change by adding or subtracting 38 to the MTU to address the Ethernet header size.
In a vPC configuration, the MTU per class needs to be consistent on both switches in the vPC domain for the vPC peer link to come up. When upgrading/downgrading a working vPC setup between pre-4.2(1)N1(1) and 4.2(1)N1(1) releases, the MTU is adjusted to make sure that the MCT peer-link always comes up.
However if you add a peer-link between two switches in a vPC domain that are identically configured (MTU in particular) with one switch running Cisco NX-OS Release 4.2(1)N1(1) and another switch running an earlier release, then the vPC peer link does not come up because the MTU is inconsistent between the two switches.
This is not an issue when upgrading or downgrading peer switches in a vPC domain; this is only an issue when adding a peer link between two switches running Cisco NX-OS Release 4.2(1)N1(1) and earlier releases that were not previously in the same vPC domain.
To resolve this issue, upgrade or downgrade one switch to match the version on the other switch and reconfigure the MTU to be consistent on both sides. For details, see CSCtg27538.
- The channel-group configuration is not applied to the Cisco Nexus 2000 Series downlink interface after downgrading to the Cisco NX-OS Release 4.1(3)N1(1) software. This issue occurs if the speed 1000 command is present under the context of the port channel. To work around this issue, reconfigure the channel-group command after the system comes up and reapply the configuration from the saved configuration in the bootflash. For details, see CSCtc06276.
- When a private VLAN port is configured as a TX (egress) SPAN source, the traffic seen at the SPAN destination port is marked with the VLAN of the ingressed frame. There is no work around.
- In large-scale configurations, some Cisco Nexus 2000 Series Fabric Extenders may take up to 3 minutes to appear online after entering the reload command. A configuration can be termed large scale when the maximum permissible Cisco Nexus 2000 Series Fabric Extenders are connected to a Cisco Nexus 5000 Series switch, and all host-facing ports are connected and each host-facing interface has a large configuration (that supports the maximum permissible ACEs per interface).
- The Cisco Nexus 2000 Fabric Extender does not support PVLANs over VLAN trunks used to connect to another switch. The PVLAN trunks are used only on inter-switch links but the FEX ports are only meant to connect to servers. Because it is not a valid configuration to have an isolated secondary VLAN as part of a Fabric Extender port configured as a VLAN trunk, all frames on isolated secondary VLANs are pruned from going out to a FEX.
- Egress scheduling is not supported across the drop/no-drop class. Each Fabric Extender host port does not support simultaneous drop and no drop traffic. Each Fabric Extender host port can support drop or no drop traffic.
- The Cisco Nexus 2148 Fabric Extender does not support frames with the dot1p vlan 0 tag.
- VACLs of more than one type on a single VLAN are unsupported. Cisco NX-OS software supports only a single type of VACL (either MAC, IPv4, or IPv6) applied on a VLAN. When a VACL is applied to a VLAN, it replaces the existing VACL if the new VACL is a different type. For instance, if a MAC VACL is configured on a VLAN and then an IPv6 VACL is configured on the same VLAN, the IPv6 VACL is applied and the MAC VACL is removed.
- A MAC ACL is applied only on non-IP packets. Even if there is a match eth type = ipv4 statement in the MAC ACL, it does not match an IP packet. To avoid this situation, use IP ACLs to apply access control to the IP traffic instead of using a MAC ACL that matches the EtherType to IPv4 or IPv6.
- Multiple boot kickstart statements in the configuration are not supported.
- If you remove an expansion module with Fibre Channel ports, and the cable is still attached, the following FCP_ERRFCP_PORT errors are displayed:
2008 May 14 15:55:43 switch %KERN-3-SYSTEM_MSG: FCP_ERRFCP_PORT: gat_fcp_isr_ip_fcmac_sync_intr@424, jiffies = 0x7add9a:Unknown intr src_id 42 - kernel2008 May 14 15:55:43 switch %KERN-3-SYSTEM_MSG: FCP_ERRFCP_PORT: gat_fcp_isr_ip_fcmac_sync_intr@424, jiffies = 0x7add9a:Unknown intr src_id 41 - kernelThese messages are informational only, and result in no loss of functionality.
Configuration Synchronization Limitation
When you remove a switch profile using the no switch-profile name [all-config | local-config] command, the configuration in the switch profile is immediately removed from the running configuration. This disrupts the configurations that were present in the switch profile. For example, port channel and vPC configurations are disrupted. For current information about this issue, refer to CSCtl87240 and CSCtl87260.
Limitations on the Cisco Nexus 5010 and Cisco Nexus 5020
The limitations on the Cisco Nexus 5010 switch and the Cisco Nexus 5020 switch are as follows:
- If the SPAN source interface sends more than 6Gbps traffic or if traffic bursts too much, a Nexus 5020 switch or Nexus 5010 switch drops traffic on the source interface. You can use the switchport monitor rate-limit 1G command on the SPAN destination to reduce the dropping of actual traffic on the source interface; however, SPAN traffic is restricted to 1Gb.
- Traffic going out the Ethernet SPAN destination is always tagged. The SPAN destination can be in the access or trunk mode and frames on the SPAN source port can be tagged or untagged. Frames are always tagged internally as they travel through the system. Information about whether the frame was originally tagged or untagged, as it appeared in the SPAN source, is not preserved in the SPAN destination. The spanned traffic exiting the SPAN destination port always has the VLAN tag on it. The correct VLAN tag is applied on the frame as it goes out the SPAN destination. The only exception is if frames ingress on a SPAN source port on an invalid VLAN. In this case, vlan 0 is applied on a spanned frame.
- Spanned FCoE frames do not preserve original SMAC and DMAC fields. The Ethernet header gets modified as the frame is spanned to the destination. The modified header fields are displayed when monitored on the SPAN destination.
- The CoS value in spanned FCoE frames on the Ethernet SPAN destination port does not match with the CoS value in the SPAN FCoE source frame. The CoS value on the captured SPAN FCoE frame should be ignored.
- The class-fcoe cannot be removed even if Fibre Channel is not enabled on a switch.
- If a port drains traffic at a rate less than 100 Kbps, it is errdisabled in 10 seconds to avoid buffer exhaustion. However, if the drain rate is larger than 100 Kbps, the port may not be consistently errdisabled within 10 seconds which exhaust ingress buffers and discard frames. Use the shut command to disable the slow-draining port.
- The multicast storm control functionality in the Cisco Nexus 5000 Series does not distinguish between IP, non-IP, registered, or unregistered multicast traffic. All multicast traffic is subject to a single-multicast storm control policer when configured.
IGMP Snooping Limitation
On the Cisco Nexus 5010 switch and the Cisco Nexus 5020 switch with a Cisco Nexus 2000 Series Fabric Extender (FEX) installed, unregistered IP multicast packets on one VLAN are forwarded to other VLANs where IGMP snooping is disabled. We recommend that you do not disable IGMP snooping on the Cisco Nexus 5010 switch and the Cisco Nexus 5020 switch. A static IGMP join can be configured for devices intended to receive IP multicast traffic but not to send IGMP join requests. This limitation applies to the Cisco Nexus 5010 switch and the Cisco Nexus 5020 switch only.
SPAN Limitations on Fabric Extender Ports
The SPAN limitations on Fabric Extender ports are as follows:
- On a Cisco Nexus 5000 Series switch, if the SPAN source is a FEX port then the frames will always be tagged when leaving the SPAN destination.
- On a Cisco Nexus 5010 switch or a Nexus 5020 switch, if the SPAN source is an access port on a switch port or FEX port, the spanned frames at the SPAN destination will be tagged.
- On a Cisco Nexus 5010 switch or a Nexus 5020 switch, if the span source is an access port on a switch port or FEX port, the spanned frames at the SPAN destination will be tagged.
- On a Cisco Nexus 5500 Platform switch, if the SPAN source is on an access port on the switch port, then the frames will not be tagged when leaving the SPAN destination.
- Ports on a FEX can be configured as a tx-source in one session only.
If two ports on the same FEX are enabled to be tx-source, the ports need to be in the same session. If you configure a FEX port as a tx-source and another port belonging to the same FEX is already configured as a tx-source on a different SPAN session, then a error is displayed on the CLI.
In the following example, Interface Ethernet100/1/1 on a FEX 100 is already configured as a tx-source on SPAN session-1:
If you add an interface Ethernet100/1/2 as a tx-source to a different SPAN session (session-2) the the following error is displayed:
- When a FEX port is configured as a tx-source, the multicast traffic on all VLANs for which the tx-source port is a member, is spanned. The FEX port sends out only multicast packets that are not filtered by IGMP snooping. For example, if FEX ports 100/1/1-12 are configured on VLAN 11 and the switch port 1/5 sends multicast traffic on VLAN 11 in a multicast group, and hosts connected to FEX ports 100/1/3-12 are interested in receiving that multicast traffic (through IGMP), then that multicast traffic goes out on FEX ports 100/1/3-12, but not on 100/1/1-2.
If you configure SPAN Tx on port 100/1/1, although the multicast traffic does not egress out of port 100/1/1, the SPAN destination does receive that multicast traffic, which is due to a design limitation.
- When a FEX port is configured as both SPAN rx-source and tx-source, the broadcast, non-IGMP Layer-2 multicast, and unknown unicast frames originating from that port may be seen twice on the SPAN destination, once on the ingress and once on the egress path. On the egress path, the frames are filtered by the FEX to prevent them from going out on the same port on which they were received. For example, if FEX port 100/1/1 is configured on VLAN 11 and is also configured as SPAN rx-source and tx-source and a broadcast frame is received on that port, the SPAN destination recognizes two copies of the frame, even though the frame is not sent back on port 100/1/1.
- A FEX port cannot be configured as a SPAN destination. Only a switch port can be configured and used as a SPAN destination.
Checkpoint and Configuration Rollback Limitation
When FCoE is enabled, the checkpoint and configuration rollback functionality is disabled.
Asymmetric Configuration
In a vPC topology, two Cisco Nexus 5000 switches configured as vPC peer switches need to be configured symmetrically for Layer 3 configurations such as SVIs, Peer Gateway, routing protocol and policies, and RACLs.
Note
Caveats
Beginning in Cisco NX-OS Release 5.0(3)N1(1b), the open and resolved caveat record numbers are provided with links to the But Toolkit where you can find details about each caveat.
This section includes the following topics:
- Open Caveats
- Resolved Caveats—Cisco NX-OS Release 5.0(3)N1(1c)
- Resolved Caveats—Cisco NX-OS Release 5.0(3)N1(1b)
Open Caveats
Table 6 lists descriptions of open caveats in Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c). The record ID links to the Cisco Bug Toolkit where you can find details about the caveat.
The caveats are listed in the following categories:
- New Open Caveats
- Platform, Infrastructure
- Configuration Synchronization
- Layer 2 Switching
- SAN Switching
- FCoE
- Installation/Upgrade/Downgrade
- Pre-Provisioning
- Security
- Configuration Rollback
- System Management
- CFS
- Fabric Extender
- Transceiver
Resolved Caveats—Cisco NX-OS Release 5.0(3)N1(1c)
Table 6 lists the caveats that are resolved in Cisco NX-OS Release 5.0(3)N1(1c). The caveats may be open in previous Cisco NX-OS releases.
Resolved Caveats—Cisco NX-OS Release 5.0(3)N1(1b)
Table 6 lists the caveats that are resolved in Cisco NX-OS Release 5.0(3)N1(1b). The caveats may be open in previous Cisco NX-OS releases.
Related Documentation
Documentation for Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders is available at the following URL:
http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.html
The following are related Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Fabric Extender documents:
Configuration Guides
Cisco Nexus 5000 Series Configuration Limits for Cisco NX-OS Release 5.0(2)N1(1)
Cisco Nexus 5000 Series Configuration Limits for Cisco NX-OS Release 4.2(1)N1(1) and Release 4.2(1)N2(1)
Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide
Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide
Cisco Nexus 5000 Series NX-OS Multicast Routing Configuration Guide
Cisco Nexus 5000 Series NX-OS Quality of Service Configuration Guide
Cisco Nexus 5000 Series NX-OS SAN Switching Configuration Guide
Cisco Nexus 5000 Series NX-OS Security Configuration Guide
Cisco Nexus 5000 Series NX-OS System Management Configuration Guide
Cisco Nexus 5000 Series NX-OS Unicast Routing Configuration Guide
Cisco Nexus 5000 Series Switch NX-OS Software Configuration Guide
Cisco Nexus 5000 Series Fabric Manager Configuration Guide, Release 3.4(1a)
Cisco Nexus 7000 Series NX-OS Fundamentals Configuration Guide, Release 4.2
Cisco Nexus 2000 Series Fabric Extender Software Configuration Guide
Installation and Upgrade Guides
Cisco Nexus 5000 Series and Cisco Nexus 5500 Platform Hardware Installation Guide
Cisco Nexus 2000 Series Hardware Installation Guide
Cisco Nexus 5000 Series NX-OS Software Upgrade and Downgrade Guide, Release 4.2(1)N1(1)
Regulatory Compliance and Safety Information for the Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
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. (1110R)
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)