Guest

Cisco Nexus 5000 Series Switches

Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Cisco NX-OS Release 5.2

  • Viewing Options

  • PDF (559.7 KB)
  • EPUB (101.2 KB)
  • Feedback

Table of Contents

Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Cisco NX-OS Release 5.2

Contents

Introduction

Cisco Nexus 5000 Series Switches

Cisco Nexus 2000 Series Fabric Extenders

System Requirements

Hardware Supporte d

Online Insertion and Removal Suppor t

New and Changed Software Features

New Software Features in Cisco NX-OS Release 5.2(1)N1(7)

New Software Features in Cisco NX-OS Release 5.2(1)N1(6)

N ew Software Features in Cisco NX-OS Release 5.2(1)N1(5)

New Software Features in Cisco NX-OS Release 5.2(1)N1(4)

New Software Features in Cisco NX-OS Release 5.2(1)N1(3)

New Software Features in Cisco NX-OS Release 5.2(1)N1(2a)

New Software Features in Cisco NX-OS Release 5.2(1)N1(2)

NIF Storm Control

New Software Features in Cisco NX-OS Release 5.2(1)N1(1b)

New Software Features in Cisco NX-OS Release 5.2(1)N1(1a)

N ew Software Features in Cisco NX-OS Release 5.2(1)N1(1)

Cisco Management Interface over SSH

IPv6 Support for Additional Features

PTP Support

Open Shortest Path First (OSPFv3)

Configuration Synchronization Enhancements

Predefined SAN Admin User Role

Multicast Scaling

Dynamic System Reserved VLAN Range

Increased Host Route Support

IGMP Snoop Limits

Virtual Port Channel Peer Switch

Object Tracking Enhancements

Fabric Path Multiple Topologies

ACL Logging over Management Interface

Python Scripting APIs

POAP with Python Scripts

New and Changed Hardware Features

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(7)

N ew Hardware Features in Cisco NX-OS Release 5.2(1)N1(6)

N ew Hardware Features in Cisco NX-OS Release 5.2(1)N1(5)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(4)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(3)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(2a)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(2)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(1b)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(1a)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(1)

U pgrading or Downgrading to a New Releas e

Upgrade and Downgrade Guidelines

Supported Upgrade and Downgrade Paths

Limitations

Limitations on the Cisco Nexus 5010 and Cisco Nexus 5020

IGMP Snooping Limitation

SPAN Limitations on Fabric Extender Ports

Checkpoint and Configuration Rollback Limitation

Upgrading and Downgrading Limitations

Layer 3 Limitations

Asymmetric Configuration

SVI

Upgrading and Downgrading

Cisco Nexus 5548P Daughter Card (N55-D160L3)

Caveats

Open Caveats

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(7)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(6)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(5)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(4)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(3)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(2a)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(2)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(1b)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(1a)

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(1)

Cisco Nexus 5000 Series
and Cisco Nexus 2000 Series Release Notes, Cisco NX-OS Release 5.2

Release Date: December 7, 2012
Date Last Modified: February 7, 2014
Part Number: OL-27578-10 A0

Current Release: NX-OS Release 5.2(1)N1(7)

 

This document describes the features, caveats, and limitations for the Cisco Nexus 5000 Series switches and the Cisco Nexus 2000 Series Fabric Extenders in the following software releases:

  • Cisco NX-OS Release 5.2(1)N1(7)
  • Cisco NX-OS Release 5.2(1)N1(6)
  • Cisco NX-OS Release 5.2(1)N1(5)
  • Cisco NX-OS Release 5.2(1)N1(4)
  • Cisco NX-OS Release 5.2(1)N1(3)
  • Cisco NX-OS Release 5.2(1)N1(2a)
  • Cisco NX-OS Release 5.2(1)N1(2)
  • Cisco NX-OS Release 5.2(1)N1(1b)
  • Cisco NX-OS Release 5.2(1)N1(1a)
  • Cisco NX-OS Release 5.2(1)N1(1)

Use this document in combination with documents listed in the .


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 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 Table 1 shows the online change history for this document.


Table 1 Online History Change

Part Number
Revision
Date
Description

OL-27578-01

A0

July 13, 2012

Created NX-OS Release 5.2(1)N1(1) release notes.

B0

July 16, 2012

Updated Hardware Supported section.

C0

July 22, 2012

Added Cisco Nexus B22F FEX.

D0

July 31, 2012

Updated Supported Upgrade and Downgrade Paths.

OL-27578-02

A0

August 24, 2012

Created NX-OS Release 5.2(1)N1(1a) release notes.

B0

September 4, 2012

Updated Hardware Supported.

C0

September 6, 2012

Added three routing protocols to IPv6 Support for Additional Features.

OL-27578-03

A0

September 25, 2012

Created NX-OS Release 5.2(1)N1(1b) release notes.

CSCuc37925

B0

September 27, 2012

Added CSCuc37925 to Open Caveats.

C0

October 5, 2012

Added CSCuc37057 to Open Caveats.

OL-27578-04

A0

October 19, 2012

Created NX-OS Release 5.2(1)N1(2) release notes.

B0

October 22, 2012

Added CSCuc80263 to Open Caveats.

OL-27578-05

A0

October 23, 2012

Created NX-OS Release 5.2(1)N1(2a) release notes.

B0

November 6, 2012

Updated the SFP+ Optical information in Table 2 .

OL-27578-06

A0

December 7, 2012

Created NX-OS Release 5.2(1)N1(3) release notes.

B0

December 17, 2012

Added power supply support.

C0

January 24, 2013

Revised the limitation about Cisco Nexus 5548UP and Cisco Nexus 5598UP switches with Fibre Channel connections to HP Virtual Connect modules in the “Limitations” section.

OL-27578-07

A0

March 22, 2013

Created NX-OS Release 5.2(1)N1(4) release notes.

B0

April 3, 2013

Added CSCud72948 to Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(4).

OL-27578-08

A0

July 1, 2013

Created NX-OS Release 5.2(1)N1(5) release notes.

A1

July 2, 2013

Added more detailed information and table related to DOM polling for NX-OS Releases 5.2(1)N1(5) and earlier releases.

OL-27578-09

A0

October 14, 2013

Created NX-OS Release 5.2(1)N1(6) release notes.

A1

October 18, 2013

Updated New Software Features text.

A2

November 12, 2013

Added CSCul27686 to Open Caveats.

OL-27578-10

A0

February 7, 2014

Created NX-OS Release 5.2(1)N1(7) release notes.

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.2 also supports all hardware and software supported in Cisco NX-OS Release 5.1, Cisco NX-OS Release 5.0, and 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 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.

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 Fabric Extender (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 switch. 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.2(x) software.

 

Table 2 Hardware Supported by Cisco NX-OS Release 5.2(x) Software

Cisco NX-OS Release Support
Hardware
Part Number
5.2(1)N1(7)
5.2(1)N1(6)
5.2(1)N1(5)
5.2(1)N1(4)
5.2(1)N1(3)
5.2(1)N1(2a)
5.2(1)N1(2)
5.2(1)N1(1b)5.2(1)N1(1a)
5.2(1)N1(1)
5.1(3)N2(1c)5.1(3)N2(1b)5.1(3)N2(1a)
5.1(3)N2(1)
5.1(3)N1(1b)5.1(3)N1(1a)
5.1(3)N1(1)
5.0(3)N2(2a)
5.0(3)N2(2)
5.0(3)N2(1)
5.0(3)N1(1)
5.0(2)N2(1)
5.0(2)N1(1)
Cisco Nexus 5000 Series

Cisco Nexus 5596T switch1

N5K-C5596T-FA

X

Cisco Nexus 5596UP switch

N5K-C5596UP-FA

X

X

X

X

X

Cisco Nexus 5548UP switch

N5K-C5548UP-FA

X

X

X

X

X

Cisco Nexus 5548P switch

N5K-C5548P-FA

X

X

X

X

X

X

X

Cisco Nexus 5020P switch

N5K-C5020P-BF

X

X

X

X

X

X

X

Cisco Nexus 5010P switch

N5K-C5010P-BF

X

X

X

X

X

X

X

Cisco Nexus 2000 Series

Cisco Nexus B22DELL P FEX2

N2K-B22DELL-P

X

Cisco Nexus 2232TM-E FEX3

N2K-C2232TM-E-10GE

X

Cisco Nexus B22F FEX

N2K-B22FTS-P

X

Cisco Nexus B22HP FEX4

N2K-B22HP-P

X

X

X

X

Cisco Nexus 2232TM FEX

N2K-C2232TM-10GE

X

X

X

X

Cisco Nexus 2232PP FEX

N2K-C2232PP-10GE

X

X

X

X

X

X

X

Cisco Nexus 2248TP E FEX

N2K-C2248TP-E-1GE

X

X

X

Cisco Nexus 2248TP FEX

N2K-C2248TP-1GE

X

X

X

X

X

X

X

Cisco Nexus 2224TP FEX

N2K-C2224TP-1GE

X

X

X

X

X

X

X

Cisco Nexus 2148T FEX

N2K-C2148T-1GE

X

X

X

X

X

X

X

Expansion Modules

12-port 10GBASE-T GEM5

N55-M12T

X

16-port Universal GEM

N55-M16UP(=)

X

X

X

X

X

N5596 Layer 3 GEM

N55-M160L3(=)

X

X

X

X

X

N5548 Layer 3 daughter card

N55-D160L3(=)

X

X

X

X

X

Layer 3 GEM

N55-M160L3-V2

X

X

X

Version 2 Layer 3 daughter card

N55-D160L3-V2

X

X

X

16-port SFP+ Ethernet

N55-M16P(=)

X

X

X

X

X

X

X

8 10-Gigabit Ethernet and 8 10-Gigabit FCoE ports

N55-M8P8FP(=)

X

X

X

X

X

X

X

Transceivers

Fabric Extender Transceivers

10-Gigabit Ethernet SFP (for Cisco Nexus 2000 Series to Cisco Nexus 5000 Series connectivity)

FET-10G(=)

X

X

X

X

X

X

X

SFP+ Optical

1000BASE-ZX SFP transceiver module for SMF

GLC-ZX-SM(=)

X

10-Gigabit Ethernet—short range SFP+ module

SFP-10G-SR(=)

X

X

X

X

X

X

X

10-Gigabit Ethernet—long range SFP+ module

SFP-10G-LR(=)

X

X

X

X

X

X

X

10-Gigabit Ethernet—extended range SFP+ module

SFP-10G-ER(=)

X

X

X

1000BASE-T standard

GLC-T(=)

X

X

X

X

X

Gigabit Ethernet SFP, LC connector SX transceiver (MMF)

GLC-SX-MM

X

X

X

X

X

Gigabit Ethernet SFP, LC connector SX transceiver (MMF), extended temperature range and DOM

GLC-SX-MMD

X

X

X

X

X

Gigabit Ethernet SFP, LC connector LX/LH transceiver (SMF)

GLC-LH-SM

X

X

X

X

X

Gigabit Ethernet SFP, LC connector LX/LH transceiver (SMF), extended temperature range and DOM

GLC-LH-SMD

X

X

X

X

X

SFP+ Copper

10GBASE-CU SFP+ Cable (1 meter)

SFP-H10GB-CU1M(=)

X

X

X

X

X

X

X

10GBASE-CU SFP+ Cable (3 meters)

SFP-H10GB-CU3M(=)

X

X

X

X

X

X

X

10GBASE-CU SFP+ Cable (5 meters)

SFP-H10GB-CU5M(=)

X

X

X

X

X

X

X

10GBASE-CU SFP+ Cable (7 meters)

SFP-H10GB-ACU7M(=)

X

X

X

X

X

X

X

10GBASE-CU SFP+ Cable (10 meters)

SFP-H10GB-ACU10M(=)

X

X

X

X

X

X

X

Fibre Channel

8-Gbps Fibre Channel—short wavelength

DS-SFP-FC8G-SW(=)

X

X

X

X

X

X

X

8-Gbps Fibre Channel—long wavelength

DS-SFP-FC8G-LW(=)

X

X

X

X

X

X

X

4-Gbps Fibre Channel—short wavelength

4DS-SFP-FC4G-SW(=)

X

X

X

X

X

X

X

4-Gbps Fibre Channel—long wavelength

4DS-SFP-FC4G-LW(=)

X

X

X

X

X

X

X

4-Gbps CWDM SFP

1470 nm CWDM 1/2/4-Gbps Fibre Channel, Gray

DS-CWDM4G1470(=)

X

X

1490 nm CWDM 1/2/4-Gbps Fibre Channel SFP, Violet

DS-CWDM4G1490(=)

X

X

1510 nm CWDM 1/2/4-Gbps Fibre Channel SFP, Blue

DS-CWDM4G1510(=)

X

X

1530 nm CWDM 1/2/4-Gbps Fibre Channel SFP, Green

DS-CWDM4G1530(=)

X

X

1550 nm CWDM 1/2/4-Gbps Fibre Channel SFP, Yellow

DS-CWDM4G1550(=)

X

X

1570 nm CWDM 1/2/4-Gbps Fibre Channel SFP, Orange

DS-CWDM4G1570(=)

X

X

1590 nm CWDM 1/2/4-Gbps Fibre Channel SFP, Red

DS-CWDM4G1590(=)

X

X

1610 nm CWDM 1/2/4-Gbps Fibre Channel SFP, Brown

DS-CWDM4G1610(=)

X

X

Extended Temperature Range

1000BASE-T SFP, extended temperature range

SFP-GE-T(=)

X

X

X

X

X

X

X

Gigabit Ethernet SFP, LC connector SX transceiver (MMF), extended temperature range and digital optical monitoring (DOM)

SFP-GE-S(=)

X

X

X

X

X

X

X

Gigabit Ethernet SFP, LC connector LX/LH transceiver (SMF), extended temperature range and DOM

SFP-GE-L(=)

X

X

X

X

X

X

X

Converged Network Adapters

Generation-1 (Pre-FIP) CNAs6

X

X

X

X

X

X

X

1.The Cisco Nexus 5596T and the 12-port 10-GBase-T GEM are supported starting with Cisco NX-OS Release 5.2(1)N1(1b).

2.The Cisco Nexus B22DELL P FEX is supported starting with Cisco NX-OS Release 5.2(1)N1(3).

3.The Cisco Nexus 2232TM-E FEX is supported starting with Cisco NX-OS Release 5.2(1)N1(1a).

4.The Cisco Nexus B22HP FEX is supported starting with Cisco NX-OS Release 5.0(3)N2(2).

5.The 12 port 10-GBASE-T GEM is only supported on the Cisco Nexus 5596T starting with Cisco NX-OS Release 5.2(1)N1(1b).

6.Generation-1 (Pre-FIP) CNAs are supported on the Nexus 5000 Platform switches; however, they are not supported on the Nexus 5500 Series.

Online Insertion and Removal Support

Table 3 shows the hardware and Cisco NX-OS Release 5.x software that supports online insertion and removal (OIR).

Table 3 Online Insertion and Removable Support by Cisco NX-OS Release 5.x Software

Hardware
Part Number
Cisco NX-OS Release Support
5.2(1)N1(7)
5.2(1)N1(6)
5.2(1)N1(5)
5.2(1)N1(4)
5.2(1)N1(3)
5.2(1)N1(2a)
5.2(1)N1(2),5.2(1)N1(1b)
5.2(1)N1(1a)
5.2(1)N1(1)
5.2(1)N2(1c)5.2(1)N2(1b)5.1(3)N2(1a)
5.1(3)N2(1)
5.1(3)N1(1a)
5.1(3)N1(1)
5.0(3)N2(2a)
5.0(3)N2(2)
5.0(3)N2(1)
5.0(3)N1(1)
5.0(2)N2(1)
5.0(2)N1(1) and earlier
Cisco Nexus 5000 Series

Cisco Nexus 5596T switch

N5K-C5596T-FA

X

Cisco Nexus 5596UP switch

N5K-C5596UP-FA

X

X

X

X

Cisco Nexus 5548UP switch

N5K-C5548UP-FA

X

X

X

X

Cisco Nexus 5548P switch

N5K-C5548P-FA

X

X

X

X

X

X

Expansion Modules

12-port CU GEM

N55-M12T

X

16-port Universal GEM

N55-M16UP(=)

X

X

X

X

X

Layer 3 GEM 1

N55-M160L3-V27

Version 2 Layer 3 daughter card 1

N55-D160L3-V2 1

16-port SFP+ Ethernet

N55-M16P(=)

X

X

X

X

X

8-port SFP+ Ethernet ports and 8-port SFP+ Fibre Channel ports

N55-M8P8FPL(=)

X

X

X

X

X

N5596 Layer 3 GEM 1

N55-M160L3(=) 1

N5548 Layer 3 daughter card 1

N55-D160L3(=) 1

7.Does not support online insertion and removal. You must power down the Cisco Nexus 5000 Series switch before removing or inserting a Layer 3 GEM or Version 2 Layer 3 daughter card expansion module.

New and Changed Software Features

This section describes the new software features introduced in Cisco NX-OS Release 5.2(1)N1(x). This section includes the following topics:

New Software Features in Cisco NX-OS Release 5.2(1)N1(7)

Cisco NX-OS Release 5.2(1)N1(7) does not include new software.

New Software Features in Cisco NX-OS Release 5.2(1)N1(6)

Cisco NX-OS Release 5.2(1)N1(6) is a maintenance release that includes bug fixes and introduces this new feature:

  • You can now configure static DHCP bindings and port security features simultaneously on the same interface.

New Software Features in Cisco NX-OS Release 5.2(1)N1(5)

Cisco NX-OS Release 5.2(1)N1(5) is a maintenance release that includes bug fixes and introduces this new feature:

  • CLI for controlling digital optical monitoring (DOM) on a Switchport. By default, DOM polling is disabled. The new CLI commands allow you to turn polling on and off and monitor status.

Table 4 summarizes DOM polling availability for Cisco NX-OS Release 5.2(1)N1(5) and previous 5.2(1)N1(x) releases.

Table 4 DOM Polling Capability by Cisco NX-OS Release

DOM Polling Feature
Cisco NX-OS Release 5.2(1)N1(5)
Cisco NX-OS Release 5.2(1)N1(4)
Cisco NX-OS Release 5.2(1)N1(3) and Earlier

Switchport DOM Polling

Supported, disabled by default
CLI available to enable/disable.

Supported
Enabled by default

Not supported

HIF DOM Polling

Not supported
Not configurable

Not supported

Not supported

New Software Features in Cisco NX-OS Release 5.2(1)N1(4)

Cisco NX-OS Release 5.2(1)N1(4) is a maintenance release that includes bug fixes and introduced this new feature:

  • Switchport digital optical monitoring (DOM) is available and enabled by default.

New Software Features in Cisco NX-OS Release 5.2(1)N1(3)

Cisco NX-OS Release 5.2(1)N1(3) is a maintenance release that includes bug fixes and the following software feature:

  • Support for Cisco Nexus B22 Fabric Extender for Dell (N2K-B22DELL-P).

New Software Features in Cisco NX-OS Release 5.2(1)N1(2a)

Cisco NX-OS Release 5.2(1)N1(2a) is a patch release that provides bug fixes. It does not include new software features.

New Software Features in Cisco NX-OS Release 5.2(1)N1(2)

Cisco NX-OS Release 5.2(1)N1(2) is a maintenance release that includes bug fixes and the following software feature:

  • NIF Storm Control

NIF Storm Control

You can configure traffic storm control on a Fabric Extender (FEX) port. Storm control configured on a FEX port applies to the aggregate traffic coming in on all the ports on that FEX, however, the storm control configuration is not inherited down to the host interface (HIF) ports.

New Software Features in Cisco NX-OS Release 5.2(1)N1(1b)

Cisco NX-OS Release 5.2(1)N1(1b) is a patch release that provides bug fixes. It does not include new software features.

New Software Features in Cisco NX-OS Release 5.2(1)N1(1a)

Cisco NX-OS Release 5.2(1)N1(1a) is a patch release that provides bug fixes. It does not include new software features.

Cisco Management Interface over SSH

Beginning with Cisco NX-OS Release 5.1(3)N2(1), you can configure the following devices using the XML management interface:

  • Cisco Nexus 5548UP Switch
  • Cisco Nexus 5596UP Switch
  • Cisco Nexus 5548P Switch

The interface uses the XML-based Network Configuration Protocol (NETCONF) that allows you to manage devices and communicate over the interface with an XML management tool or a program. The Cisco NX-OS implementation of NETCONF requires you to use a Secure Shell (SSH) session for communication with the device.

NETCONF is implemented with an XML Schema (XSD) that allows you to enclose device configuration elements within a remote procedure call (RPC) message. From within an RPC message, you select one of the NETCONF operations that matches the type of command that you want the device to execute. You can configure the entire set of CLI commands on the device with NETCONF. To download the Cisco NX-OS XML Schema Definition, go to the following URL and select one of the supported devices: http://www.cisco.com/cisco/software/navigator.html .

For more information, see the Cisco Nexus XML Interface User Guide .

IPv6 Support for Additional Features

IPv6 support has been added for the following features:

  • IPv6 unicast forwarding
  • IPv6 addressing (including routed interfaces, subinterfaces, switch virtual interfaces (SVI), and port-channel interfaces)
  • IPv6 support for Neighbor Discovery (ND) or Address Resolution Protocol (ARP)
  • IPv6 support for Internet Control Message Protocol (ICMP)
  • IPv6 support for router ACLs
  • IPv6 support for Control Plane Policing (CoPP)
  • IPv6 support for QoS packet classification and marking
  • IPv6 support for SNMP
  • STATICv6 routing protocol
  • BGPv6 routing protocol
  • EIGRPv6 routing protocol

PTP Support

With the Precision Time Protocol (PTP) feature, IEEE 1588 is supported. PTP is a time synchronization protocol for nodes distributed across a network. Its hardware timestamp feature provides greater accuracy than other time synchronization protocols such as the Network Time Protocol (NTP).

Open Shortest Path First (OSPFv3)

You can configure the following basic and advanced Open Shortest Path First version 3 (OSPFv3) features for IPv6 networks:

  • OSPF3 instance
  • OSPFv3 authentication
  • Filter lists
  • Virtual links
  • Stub route
  • Route redistribution

Configuration Synchronization Enhancements

Configuration synchronization improvements for deleting and restoring switch profile configuration were added to the no switch-profile name command.

Predefined SAN Admin User Role

The new SAN admin (san-admin) user role is a noneditable, predefined user role that provides separation between LAN and SAN administrative tasks. Users that have been assigned the SAN admin user role do not have read or write access for Ethernet features unless it is assigned to them through another user role.

Multicast Scaling

You can use the hardware profile multicast max-limit command to set the maximum number of entries in the multicast routing table. The range is from 0 to 8000. In Cisco NX-OS Release 5.2(1)N1(1) only a max-limit of 8000 is supported.


Note A max-limit value above 4096 for this command is valid only on the N55-M160L3-V2 module and N55-D160L3-V2 daughter card.


Dynamic System Reserved VLAN Range

You can change the range of the system-reserved VLANs to any other 80 contiguous VLAN range. Reserving a range frees the range of VLANs that were allocated for internal use by default, and all of those VLANs are available for user configuration except for VLAN 4094. These commands were added:

  • system vlan { start-vlan } reserve
  • no system vlan { start-vlan } reserve
  • show system vlan reserved

Increased Host Route Support

For the Generation 2 Layer 3 module, Cisco NX-OS 5.2(1)N1(X) will:

  • Increase IPv4 host routes to 16,000.
  • Increase IPv6 host routes to 8,000.

IGMP Snoop Limits

You can use the hardware multicast snooping group-limit command to configure the number of groups learned through IGMP Snooping. The range is from 100 to 8000.

Virtual Port Channel Peer Switch

The Virtual Port Channel (vPC) peer switch feature addresses performance concerns around STP convergence. This feature allows a pair of Cisco Nexus 5000 Series devices to appear as a single STP root in the Layer 2 topology. This feature eliminates the need to pin the STP root to the vPC primary switch and improves vPC convergence if the vPC primary switch fails.

To avoid loops, the vPC peer link is excluded from the STP computation. In vPC peer switch mode, STP BPDUs are sent from both vPC peer devices to avoid issues related to STP BPDU timeout on the downstream switches, which can cause traffic disruption.

This feature can be used with the pure peer switch topology in which the devices all belong to the vPC.

Object Tracking Enhancements

The object tracking feature now includes vPC support.

Fabric Path Multiple Topologies

The Cisco Nexus 5000 Series switches support two topologies: the default or base topology (topology 0) and the local VLAN topology (topology 1).

ACL Logging over Management Interface

Access-control list (ACL) logging provides hardware support for ACL logging so that the CPU is not impacted by ACL logging. ACL logging is supported for entries on the mgmt0 interface.

Python Scripting APIs

Python Application Programming Interface (API) support is available on Cisco Nexus 5000 Series switches.

POAP with Python Scripts

Python scripting is fully integrated with Power-On Auto Provisioning (POAP).

New and Changed Hardware Features

This section describes the new hardware features introduced in Cisco NX-OS Release 5.2(1)N1(x). This section includes the following topics:

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(7)

Cisco NX-OS Release 5.2(1)N1(7) does not include new hardware.

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(6)

Cisco NX-OS Release 5.2(1)N1(6) does not include new hardware.

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(5)

Cisco NX-OS Release 5.2(1)N1(5) does not include new hardware.

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(4)

Cisco NX-OS Release 5.2(1)N1(4) now supports the following hardware:

  • New power supplies for Cisco Nexus 5596T switches:
  • Cisco Nexus 1100 Watt AC front-to-back power supply (PID: NXA-PAC-1100W)
  • Cisco Nexus 1100 Watts AC back-to-front power supply (PID: NXA-PAC-1100W-B)
  • Cisco Nexus 1100 Watt DC front-to-back power supply (PID: N55-PDC-1100W)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(3)

Cisco NX-OS Release 5.2(1)N1(3) supports the following new hardware:

  • Cisco Nexus B22 Fabric Extender for Dell (N2K-B22DELL-P)
  • New power supplies for Cisco Nexus 5596UP switches:

Cisco Nexus 1100 Watt DC front-to-back power supply (PID: N55-PDC-1100W)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(2a)

Cisco NX-OS Release 5.2(1)N1(2a) does not include new hardware.

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(2)

Cisco NX-OS Release 5.2(1)N1(2) did not introduce new hardware.

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(1b)

Cisco NX-OS Release 5.2(1)N1(1b) supports the following new hardware:

  • Cisco Nexus 5596T (N5K-C5596T-FA)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(1a)

Cisco NX-OS Release 5.2(1)N1(1a) supports the following new hardware:

  • Cisco Nexus 2232TM-E FEX (N2K-C2232TM-E-10GE)

New Hardware Features in Cisco NX-OS Release 5.2(1)N1(1)

Cisco NX-OS Release 5.2(1)N1(1) supports the following new hardware:

  • 1000BASE-ZX SFP transceiver module for SMF (GLC-ZX-SM)
  • Cisco Nexus B22 Fabric Extender for Fujitsu (N2K-B22FTS-P)

Upgrading or Downgrading to a New Release

This section describes the upgrade and downgrade paths that are supported for Cisco NX-OS Release 5.2(1)N1(1) on the Cisco Nexus 5000 Series switch.

This section includes the following topics:

Upgrade and Downgrade Guidelines

The following guidelines apply to Cisco NX-OS Release 5.2(1)N1(1) for the Cisco Nexus 5000 Series switches:

  • If host interface (HIF) port channels or EvPCs are configured in the system and if the system was already upgraded to NX-OS Release 5.1(3)N1(1) or Release 5.1(3)N1(1a) from any release earlier than Release 5.1(3)N1(1), ensure that the system was reloaded at least once before you upgrade to Release 5.1(3)N2(1a) or Release 5.1(3)N2(1). If the switch was not previously reloaded, reload it and upgrade to Release 5.1(3)N2(1a) or Release 5.1(3)N2(1).
  • When a Layer 3 license is installed, the Cisco Nexus 5500 Platform does not support an ISSU. Hot swapping a Layer 3 module, for example, the Layer 3 GEM (N55-M160L3-V2) or Version 2 Layer 3 daughter card (N55-D160L3-V2), is not supported. You must power down the Cisco Nexus 5000 Series switch before removing or inserting a Layer 3 expansion module.

Supported Upgrade and Downgrade Paths

Table 5 shows the upgrade and downgrade possibilities for Cisco NX-OS Release 5.2(1)N1(7).

 

Table 5 Cisco NX-OS Release 5.2(1)N1(7) Supported Upgrade and Downgrade Paths

Current Cisco NX-OS Release
Upgrade to NX-OS Release 5.2(1)N1(7)
Downgrade from NX-OS Release 5.2(1)N1(7)

5.2(1)N1(6)

Nondisruptive upgrade (ISSU) 2

Disruptive downgrade

5.2(1)N1(5)

Nondisruptive upgrade (ISSU) 2

Disruptive downgrade

5.2(1)N1(4)

Nondisruptive upgrade (ISSU) 2

Disruptive downgrade

5.2(1)N1(3)

Nondisruptive upgrade (ISSU) 2

Disruptive downgrade

5.2(1)N1(2a)
5.2(1)N1(2)
5.2(1)N1(1b)
5.2(1)N1(1a)
5.2(1)N1(1)

Nondisruptive upgrade (ISSU) 2

Disruptive downgrade

5.1(3)N2(1b)8
5.1(3)N2(1a)
5.1(3)N2(1)

Nondisruptive upgrade (ISSU) 2

Disruptive downgrade

5.1(3)N1(1a)
5.1(3)N1(1)

Nondisruptive upgrade (ISSU)9

Disruptive downgrade

5.0(3)N2(2b)
5.0(3)N2(2a)
5.0(3)N2(2)
5.0(3)N2(1)

Nondisruptive upgrade (ISSU)

Disruptive downgrade

5.0(3)N1(1c)

Nondisruptive upgrade (ISSU)

Disruptive downgrade

8.Upgrading and downgrading are both disruptive between releases 5.1(3)N2(1b) and 5.2(1)N1(2) only.

9.If HIF port channels or Enhanced vPCs (EvPC) are configured in the switch, see CSCtz42084 for additional details.

Limitations

This section describes the limitations for Cisco NX-OS Release 5.2(1)N1(1).

  • When performing an ISSU from Cisco NX-OS Release 5.1(3)N1(1) or Cisco NX-OS Release 5.1(3)N2(1) to Cisco NX-OS Release 5.2(1)N1(1), a Forwarding Manager (FWM) core can occur which causes the system to reset. This situation occurs when network interface virtualization (NIV) is enabled. To work around this issue, use the force option in the install command to perform a disruptive upgrade. For details, see CSCty92117.
  • The SAN admin user role (san-admin) is a new predefined user role in Cisco NX-OS Release 5.2(1)N1(1). If you have an existing user role with the name san-admin in Cisco NX-OS Release 5.1(3)N1(1) or Cisco NX-OS Release 5.1(3)N2(1), the new system defined role is removed when you upgrade. To resolve this issue, downgrade to the previous release, rename the user role, and perform the upgrade. For details, see CSCua21425.
  • Bridge and STP traps are displayed in the downgrade incompatibility list when you downgrade from Cisco NX-OS Release 5.2(1)N1(1) to Cisco NX-OS Release 5.0(3)N1(1c). To resolve this issue, reset the STP/Bridge trap configuration to the default settings by entering the no snmp-server enable traps bridge , the no snmp-server enable traps stpx command, and then the copy running-config startup-config command. For details, see CSCua75907.
  • The Server Virtualization Switch (SVS) connection is not deleted during a rollback when NIV is enabled. To resolve this issue, delete the current SVS connection and reapply the original SVS connection. For details, see CSCts17033.
  • If SPAN traffic is rate-limited by entering the switchport monitor rate-limit 1G command, then a maximum transmission unit (MTU) truncation size cannot be used to truncate SPAN packets. For details, see CSCua05799.
  • SPAN incompatibility is displayed in the downgrade incompatibility list when you perform a disruptive downgrade from Cisco NX-OS Release 5.2(1)N1(1) to Cisco NX-OS Release 4.2(1)N2(1b). See Supported Upgrade and Downgrade Paths for the recommended downgrade path. To work around this issue, remove and add the SPAN configuration. For details, see CSCtz39192.
  • Disruptive upgrades from Cisco NX-OS Release 4.2(1)N2(1b) to Cisco NX-OS Release 5.2(1)N1(1) are not supported and result in FC source interfaces from the SPAN sessions being removed. See Supported Upgrade and Downgrade Paths for the recommended upgrade path. For details, see CSCtz65395.
  • 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:
"Configuration not supported - Lacp fast rate is enabled",
"Use \"lacp rate normal\" on those interfaces"
 

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, then autonegotiation does not occur, which is the 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)

For details, see CSCte81998.

  • 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 to the MST region. However, the workaround causes a nondisruptive ISSU to fail because non-edge designated forwarding ports are not allowed 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 port 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 workaround.
  • In large-scale configurations, some Cisco Nexus 2000 Series Fabric Extenders might 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).
  • 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 dot1q 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 - kernel
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 41 - kernel
 

These messages are informational only, and result in no loss of functionality.

  • If you configure Multiple Spanning Tree (MST) on a Cisco Nexus 5000 Series switch, we do not recommend that you partition the network into a large number of regions.
  • A downgrade from Cisco NX-OS Release 5.1(3)N1(1) to any 5.0(3)N1(x) image can cause the Cisco Nexus 5000 Series switch to fail. For details, see CSCty92945.
  • If you upgrade a vPC peer switch from Cisco NX-OS Release 5.0(3)N2(1) to Cisco NX-OS Release 5.1(3)N2(1) or Cisco NX-OS Release 5.2(1)N1(1), and feature-set FabricPath is enabled on the upgraded switch, the vPC Peer-Link enters STP Bridge Assurance Inconsistency which affects all VLANs except VLAN 1 and affects traffic forwarding for vPC ports.

To avoid this issue, upgrade the peer switch that is running Cisco NX-OS Release 5.0(3)N2(1) switch also to Cisco NX-OS Release 5.1(3)N2(1) or higher and then enable feature-set FabricPath on the switch or switches. If you accidentally enable feature-set FabricPath in Cisco NX-OS Release 5.1(3)N2(1) when the peer vPC switch is running Cisco NX-OS Release 5.0(3)N2(1), disable the feature-set FabricPath and the vPC will resume STP forwarding state for all VLANs.

  • By design, vEth interfaces do not share the underlying behavior of a vPC port. As a result, a VLAN does not get suspended when the peer switch suspends it. For example, when you shut a VLAN on a primary switch, the VLAN continues to be up on the secondary switch when the vEth interface is on a FEX. When the VLAN on the primary switch goes down, the VLAN on the vEth interface on the primary is suspended, but the vEth on the secondary switch is up as it is an active VLAN on the secondary switch.
  • RBACL policy enforcement is performed on VLANs on which CTS enforcement is not configured. This situation occurs when there is at least one VLAN in the switch where CTS is enforced. On a VLAN where CTS is not enforced, RBACL policy lookup occurs for ingress packets and the packet is denied or permitted according to the policies in the system. To work around this issue, make sure that all VLANs on which SGT tagged packets ingress enforce CTS.
  • The packet length in the IP GRE header of a packet exiting from the switch is not equal to the MTU value configured in the ERSPAN source session. This is true for SPAN or ERSPAN. This situation can occur whenever the MTU value that is configured in an ERSPAN or SPAN session is smaller than the SPAN packet, such as when the packet is truncated. The IP GRE packet is truncated to a value that differs by -2 to 10 bytes from the expected MTU.
  • When you configure a Layer 3 interface as an ERSPAN source, and configure the ERSPAN termination on a Catalyst 6000 switch or a Cisco Nexus 7000 Series switch, you cannot terminate the Layer 3 interface ERSPAN source on the Cisco Nexus 7000 Series switch or the Catalyst 6000 switch. To work around this issue, configure VLAN 1 to 512 on the Cisco Nexus 7000 Series switch or the Catalyst 6000 switch.
  • Unknown Unicast packets in FabricPath ports are counted as Multicast packets in interface counters. This issue occurs when unknown Unicast packets are sent and received with a reserved Multicast address (that floods to a VLAN) in the outer FabricPath header, and the Cisco Nexus 5000 Series switch increments the interface counter based on the outer FabricPath header. As a result, multicast counters are incremented. In the case of a Cisco Nexus 7000 Series switch, Unicast counters are incremented as they are based on an inner Ethernet header. There is no workaround for this issue.
  • If you configure a speed of 1 G on a base or GEM port and then check for compatibility with a Cisco NX-OS Release 5.0(2) image, no incompatibility is shown. However, because 1 G was not supported in the Cisco NX-OS Release 5.0(2), an incompatibility should be shown. To work around this issue, manually remove the 1 G configuration from the ports before downgrading to Cisco NX-OS Release 5.0(2) or an earlier release.
  • In an emulated switch setup, inband keepalive does not work. The following steps are recommended for peer keepalive over SVI when a switch is in FabricPath mode:

Use a dedicated front panel port as a vPC+ keepalive. The port should be in CE mode.

Use a dedicated VLAN to carry the keepalive interface. The VLAN should be CE VLAN.

Add the management keyword to the corresponding SVI so that the failure of a Layer 3 module will not bring down the SVI interface.

Enter the dual-active exclude interface-vlan keepalive-vlan command to prevent the SVI from going down on the secondary when a peer-link goes down.

  • Fabricpath requires 802.1q tagging of inner Ethernet header of the packet. Native VLAN packets that are sent by a Cisco Nexus 7000 Series switch are not tagged. As a result, a Cisco Nexus 5000 Series switch drops packets due to packet parsing errors. To work around this issue, enable vlan dot1q tag native on the Cisco Nexus 7000 Series switch to force 802.1q tagging of native VLAN packets.
  • SPAN traffic is rate-limited on Cisco Nexus 5500 Series switches platforms to prevent impact to production traffic:

SPAN is rate-limited to 5 Gbps per ASIC (every 8 ports share one ASIC).

SPAN is rate-limited to 0.71 Gbps per monitor source port when the RX traffic on the port exceeds 5 Gbps.

For details, see CSCti94902.

  • Cisco Nexus 5548UP and Cisco Nexus 5598UP switches with a Fibre Channel connection to HP Virtual Connect modules experience link destabilization and packet loss when the speed is set to 8 GB. To work around this issue for the HP VC FlexFabric 10-Gbps 24-port module, upgrade to VC-FF 3.70 or higher firmware. To work around this issue for the HP VC 8-Gbps 24-port Fibre Channel module, upgrade to VC-FC2 1.04 or higher. In the autonegotiation mode, the speed will drop to 4 Gb. The workaround is to manually set the speed to higher than 4 GB. For the HP VC 8-Gbps 20-port Fibre Channel module, leave the speed at 4 GB. For details, see CSCtx52991.

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:

  • 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 error-disabled in 10 seconds to avoid buffer exhaustion. However, if the drain rate is larger than 100 Kbps, the port might not be consistently error-disabled 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.

Beginning with NX-OS release 5.2(1)N1(5), IGMP general queries received on FEX interfaces are dropped thereby preventing a FEX interface from becoming an mrouter port.

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, 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 5500 Platform switch, if the SPAN source is on an access port on the switch port, 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, an 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:

swor28(config-monitor)# show running-config monitor
version 4.0(1a)N2(1)
monitor session 1
source interface Ethernet100/1/1 tx
destination interface Ethernet1/37
no shut
 

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:

swor28(config)# monitor session 2
swor28(config-monitor)# source interface ethernet 100/1/2 tx
ERROR: Eth100/1/2: Ports on a fex can be tx source in one session only
swor28(config-monitor)#
 
  • 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 might 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.
  • Cisco NX-OS Release 5.1(3)N2(1) does not support SPAN on a VM FEX.

Checkpoint and Configuration Rollback Limitation

When FCoE is enabled, the checkpoint and configuration rollback functionality is disabled.

Upgrading and Downgrading Limitations

When upgrading and downgrading between Release 5.1(3)N2(1), Release 5.2(1)N1(1), and Release 5.2(1)N1(1a), you might see the following issues in switch profile mode:

  • switchport command configuration issues

If you previously used the switchport access vlan command, the switchport trunk allowed vlan command, or the switchport trunk native vlan command to configure the switch profile mode, the configurations you created are not visible.


Note This problem is a configuration display issue only, and there is no traffic disruption.


Table 6 lists the situations where you might experience switchport command configuration issues and the workarounds.

 

Table 6 Switchport Command Configuration Upgrade and Downgrade Issues

Path
Workaround

Upgrade from 5.1(3)N2(1) to 5.2(1)N1(1)

Perform the following tasks for all port channels where the configurations you created using the switchport commands are missing from the switch profile mode.

command.

1. Enter the following commands from the switch profile mode:

switch(config-sync-sp)# interface port-channel channel-number

switch(config-sync-sp)# switchport trunk allowed vlan vlan-list

switch(config-sync-sp)# commit

2. If you receive a mutual exclusion error, import the command as follows:

switch(config-sync-sp)# import interface port-channel channel-number

switch(config-sync-sp-import)# commit

Downgrade from 5.2(1)N1(1) to 5.1(3)N2(1)

Same as upgrade from 5.1(3)N2(1) to 5.2(1)N1(1).

Upgrade from 5.1(3)N2(1) to 5.2(1)N1(1a)

Not applicable.

Downgrade from 5.2(1)N1(1a) to 5.1(3)N2(1)

Not applicable.

Upgrade from 5.2(1)N1(1) to 5.2(1)N1(1a)

Same as upgrade from 5.1(3)N2(1) to 5.2(1)N1(1).

Downgrade from 5.2(1)N1(1a) to 5.2(1)N1(1)

Same as upgrade from 5.1(3)N2(1) to 5.2(1)N1(1).

  • fex associate command issues

When in switch profile mode, the following commands are not visible:

fex associate

Table 7 lists the situations where you might experience fex associate command issues and the workarounds.

 

Table 7 Fex Associate Command Upgrade and Downgrade Issues

Path
Workaround

Upgrade from 5.1(3)N2(1) to 5.2(1)N1(1)

In Release 5.1(3)N2(1), the fex associate command is rarely entered in configuration synchronization mode.

If you plan to enter the fex associate command from the configuration synchronization mode, you must remove the command from the config-sync switch profile mode, and add the command from the configure terminal mode before you upgrade.

For example:

switch# configure terminal

switch(config)# interface ethernet

switch(config-if)# interface port-channel channel-number

switch(config-if)# switchport mode fex-fabric

switch(config-if)# fex associate chassis_ID

command before the upgrade, you must import the command manually.

Downgrade from 5.2(1)N1(1) to 5.1(3)N2(1)

If you plan to enter the fex associate command from the configuration synchronization mode, you must remove the command from the config-sync switch profile mode, and add the command from the configure terminal mode before you downgrade.

For example:

switch# configure terminal

switch(config)# interface ethernet

switch(config-if)# interface port-channel channel-number

switch(config-if)# switchport mode fex-fabric

switch(config-if)# fex associate chassis_ID

command before the downgrade, you must import the command manually.

Upgrade from 5.1(3)N2(1) to 5.2(1)N1(1a)

Same as upgrade from 5.1(3)N2(1) to 5.2(1)N1(1).

Downgrade from 5.2(1)N1(1a) to 5.1(3)N2(1)

Same as downgrade from 5.2(1)N1(1) to 5.1(3)N2(1).

Upgrade from 5.2(1)N1(1) to 5.2(1)N1(1a)

Not applicable.

Downgrade from 5.2(1)N1(1a) to 5.2(1)N1(1)

Not applicable.

Upgrade from 5.2(1)N1(3) to 5.2(1)N1(4)

--

Upgrade from 5.2(1)N1(4) to 5.2(1)N1(5)

--

Layer 3 Limitations

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 vPC consistency check does not include Layer 3 parameters.


SVI

When a Layer 3 module goes offline, all non-management SVIs are shut down. An SVI can be configured as a management SVI using the interface vlan command and configuring management . This configuration allows traffic to the management SVIs to not go through the Layer 3 module which maintains connectivity in case of a Layer 3 module failure.

Upgrading and Downgrading

When a Layer 3 license is installed, the Cisco Nexus 5500 platform does not support an ISSU. Layer 3 module hot swaps are not supported.

Cisco Nexus 5548P Daughter Card (N55-D160L3)

Before installing a Layer 3 daughter card (N55-D160L3) into a Cisco Nexus 5548P switch, you must upgrade to Cisco NX-OS Release NX-OS Release 5.0(3)N1(1c) or a later release, and then install the card into the chassis.

Caveats

This section includes the open and resolved caveat record numbers for this release. Links are provided to the Bug Toolkit where you can find details about each caveat.

This section includes the following topics:

Open Caveats

Table 8 lists descriptions of open caveats in Cisco NX-OS Release 5.2(1)N1(x).

The record ID links to the Cisco Bug Toolkit where you can find details about the caveat.

 

Table 8 Cisco NX-OS Release 5.2x Open Caveats

Record Number
Open Caveat Headline

CSCtx84752

The MVR receiver-port output for an AA FEX port displays ACTIVE after a switchover.

CSCtx99080

The FEX temperature does not reflect the correct value.

CSCty43038

After a rollback, the show tech-support ethpm command displays unconfigured VLANs, and FWM forwards unconfigured VLANs.

CSCtz78363

If you change the VLAN mode from FabricPath to Classical Ethernet, then back to FabricPath, some Hot Standby Router Protocol (HSRP) gateway-based traffic might be impacted.

CSCua27097

The no feature private-vlan command does not remove the entire configuration.

CSCuc23124

The Cisco Nexus 5596T does not support a 750W power supply.

CSCuc27069

The Cisco Nexus 5596T counter value is incorrect following a link flap.

CSCuc88331

IGMP snooping flooded on stp blocking after stp change.

CSCuj10676

Static port-security macs on vpc primary change.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(7)

Table 9 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(7). The caveats might be open in previous Cisco NX-OS releases.

 

Table 9 Cisco NX-OS Release 5.2(1)N1(7)

Record Number
Resolved Caveat Headline

CSCth76201

DOM information is not correctly retrieved for Cisco-Finisar SFP.

CSCts72361

Inbound and output ICMP frames on different ports when Layer 3 is enabled.

CSCty86291

MTS buffer exhaustion with sequential add of large VLANs.

CSCuc98155

MAC address table not sync in peers vPC ports.

CSCud45836

Error disabled/STP set port state failure after VLAN is removed by VTP.

CSCue02576

Port profile crash when moving VLAN from non-default to default topology.

CSCug96074

MAC unsync between vPC peers when vPC port is down and recovered.

CSCuh33604

Optimize dot1d SNMP for FEX statistics.

CSCui44640

SNMP memory leak - libport_mgr.so.

CSCui47367

Shut/no shut for VFC crashed device due to FWM hap reset.

CSCuj08855

ARP entry of vip times out on HSRP standby.

CSCuj32483

LACP member ports stuck in I state.

CSCuj59439

vPC hap reset after peer-keepalive link comes up.

CSCuj84269

Switch reloaded due to gatosusd hap reset.

CSCuj86736

Need to optomize DFE tuning in 55xxUP series switches - RX CRC errors.

CSCuj90123

aclmgr crash during sh tech.

CSCul05733

False transceiver warning error messages.

CSCul27511

eth_port_ channel crash.

CSCul27686

Nexus 55xx P Devices: After upgrade interface down and unrecoverable.

CSCul30680

Restart due to monitor process crash when a VLAN is added or removed.

CSCul80812

Port inheritance disappears from interface configuration if a large number of VLANs are used.

CSCum29958

A switch configured for IP directed broadcast causes duplicate packets.

CSCum44722

SNMP crash.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(6)

Table 10 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(6). The caveats might be open in previous Cisco NX-OS releases.

 

Table 10 Cisco NX-OS Release 5.2(1)N1(6)

Record Number
Resolved Caveat Headline

CSCth31107

Not all process cores are managed by sysmgr causing disk space to leak.

CSCtj26673

config-sync import fails for certain implicitly generated Quality of Service configurations.

CSCtq32794

"tacacs source-interface" failed to be parsed after copying configuration to running environment.

CSCtr97385

SNMP crashes due in config-copy MIB missed heartbeats.

CSCtt26423

An error message is displayed when entering DNS related command under management VRF.

CSCtw96661

Not able to suppress Sev5 syslog messages related with connected FEX.

CSCtx52217

NTP crashed when left idle.

CSCtx89902

Able to match more than one CoS for default class-fcoe.

CSCty33679

Crash with show interface eth1/7 transceiver details / mping.

CSCty44132

Peer is not reachable through FabricPath.

CSCtz67585

Service VPC might crash when no MTS buffers are available.

CSCua02062

Ethpm causes high CPU. MTS buffers stuck.

CSCub08667

Some MIBS respond with next object in tree and not with next index.

CSCub50434

VTP packets looping on vpc.

CSCub52503

Need warning in syslog for 750W PS when input voltage exceeded.

CSCub66817

RMON event configuration with large description causes SNMPD crashes and HAP reset.

CSCub80303

FEX crashes when entering the running command "phystats" in command shell.

CSCub88252

Infinite loop in cmd_req_send_recv_common at cmd_frontend.c:2003.

CSCuc24181

Output discards are seen in vfc interface.

CSCuc43023

Unknown unicast forwarding block CLI exposed.

CSCuc54112

DHCP broadcast packets flood/loop with FP enabled.

CSCud33607

Null route is not in RIB after a VRF shut/unshut.

CSCue20224

Nexus VSH crashes when prompted for "enable" password

CSCue65973

Nexus 2248TP: HIF speed not showing the actual link bandwidth.

CSCue74597

Stale SSH sessions are seen if client is not sending close ack.

CSCuf30186

snmpd service crashes due to error table filled with messages.

CSCug26811

Kernel Panic:process hap reset caused by excessive traffic on mgmt port.

CSCug29190

'ethpc' hap reset tied to SFP diagnostics.

CSCug38697

OSPF LSA injection vulnerability.

CSCug79384

PVLAN with port-security and static mac-address disappear.

CSCug97032

COPP - ARP Traffic not classified when arriving on PeerLink.

CSCuh27818

dcos-xinetd core due to segmentation fault in 6.2.2 during netstack reg.

CSCuh57927

FEX hardware type changed after ISSU/ISSD.

CSCuh66598

Private-vlan hap reset after 'default switchport private-vlan mapping'.

CSCuh67647

Many Tacacsd zombie processes can be seen on Cisco Nexus 7000.

CSCuh97211

Removing and re-enalbing device alias can result in fabric waiting.

CSCui08344

Multicast convergence improvements.

CSCui22907

Generating TCAM FIB full syslog when not FIB is not full.

CSCui28946

Cisco Nexus 5596T fails to boot.

CSCui34757

NTP client not in sync with NTP server.

CSCui40707

TACACSd and RADIUSd writing uncompressed cores to var/sysmgr/work.

CSCui52144

Uncompressed cores filling up /var/sysmgr/work.

CSCui79701

Config Sync / Verify Failed / Lock already taken by another session.

CSCui88961

Support static DHCP and port-sec at the same time.

CSCuj07601

"Error: OID not increasing" with SNMPwalk on ciscoStpExtensionsMIB.

CSCuj24129

DHCP offers with unicast bootp flag not relayed.

CSCuj29678

pm-dbr or bfdc thread could cause kernel crash.

CSCuj56227

IGMPv3 proxy reports might loop on the network.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(5)

Table 11 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(5). The caveats might be open in previous Cisco NX-OS releases.

 

Table 11 Cisco NX-OS Release 5.2(1)N1(5) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCtr46317

An NTP crass occurs after an ISSU.

CSCts39876

The NTP authentication key appears in clear text.

CSCtu34118

An OSPF router link is not advertised in Type 1 LSA when the interface comes up.

CSCtx21891

A Cisco Nexus 5020 control plane failure does not bring links down.

CSCtx52991

The Cisco Nexus 5500 is not compliant with FC-PI-4 at 8G FC speed.

CSCtx75226

When you change the STP mode from rapid-pvst to MST, Version 1 HSRP groups are continuously cycling through active, speak, and standby states.

CSCty01353

A MAC learning issue occurs after an expansion module hangs.

CSCtz32233

A vPC crash occurs on the switch as the result of a memory leak.

CSCtz32293

Even though TACACS servers are reachable and configuration is correct, Users are

sometimes unable to authenticate, and logs report that all servers are unreachable.

CSCtz80915

TACACS service crashes on a Nexus NX-OS switch running a 6.0(2) software release.

CSCua39287

The system reloads when a TACACS+ process crashes.

CSCua42827

When a multicast source is connected to only one Cisco Nexus 5000 in a vPC pair, and a multicast bind-vrf is configured, the non-source-connected Nexus 5000 will not create an mroute for the group in question, and will drop all traffic for this group coming across the vPC peer-link due to RPF.

CSCua50255

An ARP entry is not learned over a vPC link between two Cisco Nexus 5000 switches.

CSCua52926

A 5548UP switch with passive Twinax cable flaps an interface when it comes back online after being reloaded.

CSCua82034

The command show fabricpath switch-id does not display all switches.

CSCub15147

An SNMP memory leak occurs on the Cisco Nexus 5000 switch.

CSCub16539

A Cisco Nexus 7000 switch may experience crashes in the SNMPd process. Errors leading up to the crash may indicate an MTS issue with the SAP used by SNMP.

CSCub77319

The description command, which was present in earlier releases, is missing under port-profile in Config sync mode.

CSCub80935

In a Cisco Nexus 5000 switch, when a user with a username other than "admin" the issues command tac-pac, the switch prompts for a password.

CSCub90520

If a 'sh tech < routing_protocol >' command is interrupted, the CLI thread continues to run.

CSCub92274

Ports 127 and 128 are listed on the output of "show vpc orphan-ports."

CSCuc39303

When FEX interfaces are polled with Solarwinds SNMP, hundreds of satctrl heartbeats can be lost.

CSCuc54623

The Show Port Channel command fails.

CSCuc62084

Show accounting log / show log output is missing initial syslogs.

CSCuc88331

After a change in the spanning-tree (for example, the port moves from forward to blocking), IGMP packets may still be flooded on a blocking interface for some time. This causes IGMP traffic to loop on the network.

CSCud02139

The Cisco Nexus7000 cannot be authenticated at random times when using TACACS+ because the TACACS+ server becomes unreachable.

CSCud08015

PTP multicast packets are dropped instead of being forwarded.

CSCud26463

Pre-provisioning should support dynamic string changes and larger commands.

CSCud41492

IGMP does not immediately synchronize with a peer vPC switch after simultaneous leaves and joins.

CSCud97235

The command "show cdp neighbor" truncated the remote port ID from an ASR9K.

CSCue02015

A telnet connection to a non-management SVI breaks following a reload.

CSCue24735

The Cisco Nexus 5000 switch has incorrect virtual-mac-address entries during HSRP state transition.

CSCue36960

A FabricPath ISIS hello message is dropped after a non-disruptive ISSU is performed.

CSCue71612

A Cisco Nexus 5548 switch reloads and resets with the reason given as unknown.

CSCue79881

When SNMP bulk get requests are sent, there is buildup on the MTS queue, and the SNMP process is killed.

CSCue81832

The hardware clock is sometimes out of sync with the software clock, and an ISSU failure can result.

CSCue85990

Login authentication fails and the following message is received: AUTHPRIV-2-SYSTEM_MSG pam_unix(login:auth): auth could not identify.

CSCuf08921

The Cisco Nexus 5000 Layer 2 switch running fabric path does not update its MAC address table when it receives a GARP.

CSCuf21318

A secondary vPC flaps vPC port-channels after a peer-link goes down.

CSCuf38974

When CFS is disabled on a management interface, multicast-routing is not disabled.

CSCuf48422

For the TX power of a Finisar SFP-10G-LR module, a minus value is shown as a plus value in a show int transceiver detail.

CSCuf51541

During an active HSRP reload, vPC/vPC+ HSRP VMAC is removed from the HSRP standby switch.

CSCuf57043

A "sequence timeout" occurs when communicating with the MTS_SAP_ETH_PORT_SEC process.

CSCuf61304

On a turn-around router running NX-OS software, the RPF on mroute incorrectly points to the RP instead of the source for (S,G).

CSCug07482

A memory leak occurs in the Port Profile Manager when the switch profile is configured.

CSCug19662

The show processes memory command does not have a MemLimit field.

CSCug24976

The CLI knob "ip pim register-until-stop" should be available for use.

CSCug39029

IGMP membership reports are sent back to the same host port (HIF) on which they were received.

CSCug42375

The same "match cos" value is shared between an FCoE class and another class.

CSCug69534

A memory leak in the FWM process.

CSCug80833

SVI ping fails following a firewall switchover on the opposite side.

CSCug84290

False transceiver alarm error messages are received on the Cisco Nexus 5000 switch.

CSCug90571

The service "fcdomain" crashes.

CSCug95929

Multiple FEX’s go offline at the same time.

CSCuh07302

A mis-programmed hardware adjacency entry causes device alias distribution to fail.

CSCuh20770

When a Cisco Nexus 5000 switch that is running NX-OS Release 5.2(1)N1(4)is configured for FabricPath, vPC+, and FEX, reloading the switch causes it to reboot continuously.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(4)

Table 12 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(4). The caveats might be open in previous Cisco NX-OS releases.

 

Table 12 Cisco NX-OS Release 5.2(1)N1(4) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCtg20592

The subject line of the Callhome Message has GMT time rather than configured timezone, however it shows correct GMT time.

CSCth06584

The enhancement request filed requesting the "default interface" capability in Cisco Nexus 5000 and 5500 Series switches.

CSCtk37419

The Cisco Nexus 5000 Series Option to Disable feature LLDP - no feature lldp -.

CSCtl73025

The syslog with the message %MCASTFWD-3-NO_SH_MEM: mcastfwd [4482] Transient failure to allocate.

CSCtt00190

vsh process crashes while executing show/copy commands.

CSCtt10736

With auto-recovery configured on a pair of Cisco Nexus 5000 Series switches in a vPC pair, the traffic coming from the peer link might get dropped if the secondary switch is reloaded with the peer-keepalive link disconnected and then restored after bootup.

CSCtx79241

ISSU on the Cisco Nexus 5000 Series switch can fail if the logging level on any process is above 5 during the code upgrade. Running ISSU impact pre-install checks still indicates a non-disruptive upgrade.

CSCty56134

After upgrading the Cisco Nexus 5000 Series switch to NX-OS Release 5.1(3)N1(1a) or later, the VTY IPv4 access-class is converted to IPv6 access-class.

CSCty92420

Configuring VRF in BGP produces malloc errors, and subsequent BGP entries are not populated in RIB.

CSCtw72949

SNMP takes too long to process certain requests in bridge-mib and to drain these request from 'udp socket' recv_q.

CSCtu05113

The fcpc process fails in a Cisco Nexus 5000 Series switch because of a heartbeat failure.

CSCty80885

When trying to write its configuration to the 'ascii-cfg' process after a 'show run' is issued, the vPC process still writes even if it is in a low memory situation and a MALLOCFAIL error occurs. Writing to a null pointer triggers a crash.

CSCty93371

For Nexus 5000 switches, the dot1dBasePortIfIndex returns "No Such Instance" if the switch is configured in MST (Multiple Spanning Tree) mode.

CSCtz12883

Cisco Nexus 5000 switch gets into a reboot loop after upgrading to NX-OS Release 5.1(3) due to the ipqosmgr process crashing.

CSCtz40390

FC-GS-4 is exposing Storage Network Information to host.

CSCua55506

In the Cisco Nexus 5000 and 5500 switches, IPv6 neighbor discovery might fail for IPv6 hosts.

CSCua58514

The Cisco Nexus 5000 Series switch can not ping between SVIs across peer-link after loop.

CSCub38011

A Nexus 5000/5500 switch which has Fibre Channel(FC) license grace-period expired might boot to bash prompt after a reboot/reload/power cycle or a software crash.

CSCub47702

The Cisco Nexus 5000 switch does not print out logs for low/high power alarms.

CSCub66124

A Nexus Fabric Extender might unexpectedly crash with satctrl HAP failure.

CSCub75690

Nexus 5000 FabricPath ISIS metric doesn't change when Portchannel member is down. FabricPath ISIS should compute the metric based on ACTIVE members of the portchannel. But on Nexus 5000, FabricPath ISIS should compute the metric based on configured members. The behavior is inherent in the design and is inconsistent with Nexus 7000.

CSCub88489

The log message: %XMLMA-2-XMLMACRIT: XML master agent: XML subagent session 26110 terminated, may be crashed or killed.

CSCuc66439

Inbound soft reconfiguration is not working on the NX-OS Release 5.2(1)N1(1a).

CSCuc71921

The Cisco Nexus 5000 Series switches in config-sync mode, leak memory in the port-profile manager (ppm) structure when successive adding and removing port-channels were performed, also periodically collecting "show running-config".The switch eventually crashes with messages in the syslog.

CSCud05507

NX-OS RIP ignores the first 3 RIP before installing the RIP learned prefix in it’s routing table.

CSCud05886

System restarted due to HA Reset policy.

CSCud16740

Dynamic neighbor fails to re-establish after a configuration change.

CSCud22845

Unicast traffic loss occurs in a vPC+ FabricPath environment when Multicast IGMP Membership Reports are sent.

CSCud33616

DHCP Relay agent sends DHCPACK messages to destination ip address 0.0.0.0. Although current behavior complies to rfc 2131, some OS systems are not setting 'yiaddr', while DHCP relay agent SHOULD set an IP unicast of DHCPACK to the IP address specified in the 'yiaddr' field.

CSCud51284

Ipqosmgr crashed when doing a "show tech" on the HSRP active switch when it perform the command 'show policy-map interface brief' when service-policy type qos input marking_VoIP is configured on VLAN interface.

CSCud52542

The Cisco Nexus 5000 Series switches handle POST failures more Gracefully.

CSCud54427

The "track <track#>" configuration under "vpc doamin<domain-id>" is unexpectedly removed after system reload. It appears in "show start" but is removed from "show run" after reload.

CSCud64935

Software BIOS: version 1.5.0 loader: version N/A kickstart: version NX-OS Release 5.2(1)N1(2a) switch# fc? fcdomain Fcdomain internal command fcping Ping an N-Port.

CSCud72948

Fabricpath: BPDUs not sent out vPC secondary upon link failure.

CSCud88415

The Cisco Nexus 5000 Series switch may hang during Eagle to FH upgrade due to watchdog disable.

CSCuc97283

After reboot downstream Po moves to forwarding while VPC is down. After a reload, VPC Port-channel toward downstream switches can go into forwarding state while VPC is still down, potentially causing packet loss.

CSCue03528

The CFS lock on one Cisco Nexus 5000 switch in a VPC due to session manager that does not clear.

CSCue14043

Dual-homed FEX goes offline after type-1 inconsistency recovering.

CSCue14786

Carmel-ipfib configured as Aggregation switch which had BGP peering with Norcal crash@ufib_v4prefix_link_next_obj -O2-96- build 380.

CSCue19686

In a Cisco Nexus 5000 or 5500 Series switch, intermittent packet loss is seen.

CSCue24258

The Cisco Nexus 5000 switch always returns a zero value when you try to get "ifOutErrors" MIB.

CSCue25885

A Cisco Nexus 5000 switch may reload due to a crash in the feature manager.

CSCue33958

In a Cisco Nexus 5500 Series switch with layer 3 modules running a NX-OS 5.2 Release, multicast traffic received over vPC bind-vrf VLAN might not get routed to receivers hanging off layer 3 interfaces.

CSCue35880

Link up on FEX ports are some times delayed by as much as a few seconds. This can cause failures if servers are running the linux "service network restart" script and can even cause PXE to fail.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(3)

Table 13 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(3). The caveats might be open in previous Cisco NX-OS releases.

 

Table 13 Cisco NX-OS Release 5.2(1)N1(3) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCtx69526

After a non-disruptive ISSU upgrade from release 5.0(3)N1(1c) or earlier, VTP pruning may get enabled on the Nexus 5000 series if it is enabled on other parts of the network.

CSCtx74521

There is a high CPU found on a vPC pair due to a PIM assert storm. A vPC domain source check is needed.

CSCua65570

Nexus 5596UP and 5548UP switches discovery over UDP from FM or DCMN fails.

CSCub41054

Sending an ARP request on invalid interface loopback0.

CSCub66225

The interlace physical MAC address returns inconsistent values.

CSCub68625

There switch-profile config-sync command does not function correctly after upgrading from the NX-OS release 5.2(1)N1(1) to the 5.2(1)N1(1b) patch release.

CSCuc13077

Any Nexus 5000 series switch without the layer 3 module drop fragmented packets when it pings the SVI.

CSCuc51083

After ISSU upgrade from 5.1(3)N2(1a) to 5.2(1)N1(1b), interfaces on the N2K-C2232TM-10GE which were down before the upgrade do not come until the FEX is reloaded.

CSCuc54814

Cisco Nexus 5000 Series switches configured with vPC+ and peer-gateway enabled, switched packets are sent over the peer-link.

CSCuc73895

HSRP standby learns VIP MAC addresses for the end host in a vPC peer with local proxy ARP configured which breaks connectivity to the host.

CSCuc84658

For the Nexus 5000 series switches there is an incorrect adjacency for the next hop IPv4 and IPv6 address causing traffic to be misrouted.

CSCuc87195

The N5548UP and N5596UP with reversible air fan and power supply report low fan speed errors after NX-OS 5.1(3) N1(1) upgrade and higher.

CSCuc92455

FEX Fabric port integrity improvement on the N2248TP.

CSCuc96551

FWM process cores sub-interface configuration.

CSCub02794

Many FLOGI and FCNs states are not cleared after the neighbors are disconnected.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(2a)

Table 14 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(2a). The caveats might be open in previous Cisco NX-OS releases.

 

Table 14 Cisco NX-OS Release 5.2(1)N1(2a) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCuc80263

ISSU from 5.1(3)N2(1b) to 5.2(1)N1(2) is disruptive.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(2)

Table 15 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(2). The caveats might be open in previous Cisco NX-OS releases.

 

Table 15 Cisco NX-OS Release 5.2(1)N1(2) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCtr62922

Using FEX preprovisioning and configuring a vPC, the vPC number configuration in the two-layer port channel is accepted.

CSCtx88231

A switch reloads occurs when subinterfaces are configured on more than 10 Layer 3 interfaces.

CSCty00140

Internal vPC numbering needs to be optimized on the dual-homed FEX.

CSCtz00583

EIGRP MIBs are missing in Cisco NX-OS release 5.2(1)N1(x).

CSCua06312

The switch does not respond to unicast ARP requests received through the peer link.

CSCua86006

On a Version 2 Layer 3 daughter card (N55-D160L3-V2), when the maximum number of entries in the multicast routing table is greater than 4096, the multicast route programming can exceed the configured hardware limit and impact the allocated space for unicast host routes.

CSCua55155

Following an ISSU, the mode fabricpath VLAN configuration was lost.

CSCua74057

A "Warning: Failed saving command: (Command Parsing Failed)" error displays after a VLAN is added or removed on a trunk.

CSCua93951

Following an ISSU in a vPC setup, an internal failure can occur if a FEX has a PVLAN isolated trunk port.

CSCub01130

In a FabricPath configuration, when GSTP SWID = 0 and the peer switch reloads, no MAC address is flushed upon TCN.

CSCub09466

The value of "dot1dTpFdbStatus" is always shown as 0 in the BRIDGE-MIB.

CSCub56954

The Cisco Nexus 2248TPE FEX reports a power-on self test (POST) failure.

CSCub63985

Unicast ARP requests are dropped by the HSRP active after a session flap.

CSCub77357

The output of the show running switch-profile command does not show the allowed VLAN list.

CSCub82742

DCBX convergence occurs when PFC is set to off.

CSCub99364

A Cisco Nexus 5596 switch with a Layer 3 module and PVLAN configured drops packets on the internal port 15.

CSCub46846

A replacement Cisco Nexus 5000 Switch causes the FEX interfaces to flap.

CSCuc37057

VLAN membership is incorrect after an upgrade to Cisco NX-OS Release 5.2(x).

CSCuc37925

The show environment command displays incorrect PID information for fan modules.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(1b)

Table 16 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(1b). The caveats might be open in previous Cisco NX-OS releases.

 

Table 16 Cisco NX-OS Release 5.2(1)N1(1b) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCtw82571

After a NX-OS upgrade of a Cisco Nexus 5010 or 5020 switch to release 5.1(3)N1(1), the switch does not forward traffic on certain vlans. If the switch uses FCoE, then vFCs fails to come up.

CSCua23762

The Cisco Nexus 5500 monitor session prevents FCoE hosts from completing logins.

CSCua54088

When a new member port from a new ASIC is added to a SAN port channel or the last member from any ASIC of a SAN port channel is flapped, the ingress FC frames are dropped at that member port due to the layer 3 logical interface (LIF) VLAN membership check failure.

CSCub19606

FCoE control plane traffic is impacted after upgrade.

CSCub48265

Cisco Nexus B22HP FEX 10GB host interface port autonegotiates to 1GB during initial server bootup.

CSCub69862

Cisco Nexus 5000 switch may reload due to a netstack crash.

CSCub73455

PVLAN cloned MAC addresses are deleted when a packet with a learned MAC address on a promiscuous port with a primary VLAN gets reflected on a secondary port.

CSCub79135

When checking the config-sync state of the peer using the command show

switch-profile peer detail , a crash of the port-profile manager is displayed.

CSCub96331

FC credits up to a value above 64 can not be configured.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(1a)

Table 17 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(1a). The caveats might be open in previous Cisco NX-OS releases.

 

Table 17 Cisco NX-OS Release 5.2(1)N1(1a) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCua86602

The update license command is no longer hidden.

CSCua17122

Two Cisco Nexus 5000 switches running Cisco NX-OS Release 5.1(3)N1(1a) reloaded unexpectedly. The reason was "port-profile hap reset".

CSCua34584

An ISSU from Cisco NX-OS Release 5.0(3)N1(1) to Cisco NX-OS Release 5.2(1)N1(1) failed with "Maximum downtime exceeded" error.

CSCub38911

IGMP groups that are learned using IGMP snooping on FEX interfaces fail to synchronize when the fabric port fails or is shut down.

CSCua41448

A MAC violation occurs when a virtual MAC address moves from a vPC peer link to a secured port.

CSCua92618

Input/CRC errors are seen on FEX host interfaces on the Cisco Nexus 2232TM Fabric Extender.

Resolved Caveats in Cisco NX-OS Release 5.2(1)N1(1)

Table 18 lists the caveats that are resolved in Cisco NX-OS Release 5.2(1)N1(1). The caveats might be open in previous Cisco NX-OS releases.

Table 18 Cisco NX-OS Release 5.2(1)N1(1) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCtl56428

Solution for vPC failover when all data ports are down and mgmt0 is up.

CSCtl87260

Removing a switch-profile impacts the running configuration.

CSCua51385

An ISSU from Cisco NX-OS Release 5.1(3)N2(1a) to Cisco NX-OS Release 5.2(1)N1(1) causes the Fibre Channel link to go down.

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/en/US/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 deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

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/en/US/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 deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

©2013-2014 Cisco Systems, Inc. All rights reserved