Guest

Cisco Nexus 5000 Series Switches

Cisco Nexus 5500 Series Release Notes, Cisco NX-OS Release 6.02

  • Viewing Options

  • PDF (571.2 KB)
  • EPUB (97.7 KB)
  • MOBI (183.6 KB)
  • Feedback

Table of Contents

Cisco Nexus 5500 Series Release Notes, Release 6.02

Contents

Introduction

Cisco Nexus Devices

Cisco Nexus 2000 Series Fabric Extenders

System Requirements

Hardware Supported

Online Insertion and Removal Support

New and Changed Features

New Software Features in Cisco NX-OS Release 6.0(2)N2(5)

New Software Features in Cisco NX-OS Release 6.0(2)N2(4)

New Software Features in Cisco NX-OS Release 6.0(2)N2(3)

New Software Features in Cisco NX-OS Release 6.0(2)N2(2)

Command Addition: cts role-based batched-programming

New Software Features in Cisco NX-OS Release 6.0(2)N2(1)

Bidirectional Forwarding Detection

Command Update: show lldp system -detail

Default Interface

Embedded Event Manager Support

Network Time Protocol Server

Policy Based Routing

DHCPv4-relay and DHCPv6-relay

FEX Host Interface Storm Control

Scalability Enhancements

SNMP Bridge-MIB and LLDP MIB

vPC Shutdown

vPC+ Routing Protocol Peering

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

802.1x Authentication

FEX NIF Storm Control

IP-Directed Broadcast

iSCSI TLV Configuration

Port Channel Minimum Links

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

Ingress Policing

Glean Throttling

ACL Logging

POAP Enhancement

BGP Enhancement

VRF Route Leaking

FCoE over 10GBASE-T

Open Management Infrastructure

New Hardware Features in Cisco NX-OS Release 6/0(2)N2(5)

New Hardware Features in Cisco NX-OS Release 6.0(2)N2(1b)

New Hardware Features in Cisco NX-OS Release 6.0(2)N2(1)

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

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

Upgrading or Downgrading to a New Release

Upgrade and Downgrade Guidelines

Supported Upgrade and Downgrade Paths

Limitations

Limitations on the Cisco Nexus Device

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 6.0(2)N2(5)

Resolved Caveats in Cisco NX-OS Release 6.0(2)N2(4)

Resolved Caveats in Cisco NX-OS Release 6.0(2)N2(3)

Resolved Caveats in Cisco NX-OS Release6.0(2)N2(2)

Resolved Caveats in Cisco NX-OS Release6.0(2)N2(1)

Resolved Caveats in Cisco NX-OS Release6.0(2)N1(2a)

Resolved Caveats in Cisco NX-OS Release6.0(2)N1(2)

Resolved Caveats in Cisco NX-OS Release6.0(2)N1(1)

MIB Support

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Cisco Nexus 5500 Series Release Notes,
Release 6.02

Release Date: January 31, 2013
Part Number: OL-27874-08 B0
Date Last Modified: July 9, 2014

Current Release: NX-OS Release 6.0(2)N2(5)

 

This document describes the features, caveats, and limitations for the Cisco Nexus 5500 devices and the Cisco Nexus 2000 Series Fabric Extenders. Use this document in combination with documents listed in the “Related Documentation” section.


NoteRelease 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 5500 and Cisco Nexus 2000 Series release notes: 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 5500 and Cisco Nexus 2000 Series release notes: http://www.cisco.com/en/US/docs/switches/datacenter/nexus5500/sw/release/notes/Nexus_5500_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-27874-01

A0

January 31, 2013

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

B0

February 18, 2013

Added information on the maximum IP MTU in the Limitations section.

C0

February 26, 2013

Added CSCtx42727 to the Resolved Caveats in Cisco NX-OS Release 6.0(2)N1(1)section.

D0

February 28, 2013

Updated support for additional software features in the New Software Features in Cisco NX-OS Release 6.0(2)N1(1) section.

OL-27874-02

A0

March 15, 2013

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

B0

May 1, 2013

Added link to the Cisco Nexus 6000 Series MIB Support List in the “MIB Support” section

OL-27874-03

A0

May 22, 2013

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

OL-27874-03

A1

June 3, 2013

Added these items as supported hardware:

QSFP-4x10G-AC7M, QSFP-4x10G-AC10M, QSFP-40G-LR4.

OL-27874-03

A2

July 29, 2013

Created NX-OS Release 6.0(2)N2(1) release notes.

OL-27874-03

A3

August 15, 2013

Added the following item as supported features for the NX-OS Release 6.0(2)N2(1):

  • iSCSI TLV Configuration

Added the following items as supported features for the NX-OS Release 6.0(2)N1(2):

  • FEX NIF Storm Control
  • IP-Directed Broadcast

OL-27874-04

A0

October 4, 2013

Created NX-OS Release 6.0(2)N2(2) release notes.

A1

November 12, 2013

Added CSCul27686 to Open Caveats.

OL-27874-05

A0

December 6, 2013

Created NX-OS Release 6.0(2)N2(1b) release notes.

OL-27874-06

A0

December 20, 2013

Created NX-OS Release 6.0(2)N2(3) release notes.

A1

December 24, 2013

Corrected ISSU path from Disruptive to Nondisruptive.

OL-27874-07

A0

March 5, 2014

Created NX-OS Release 6.0(2)N2(4) release notes.

A1

April 7, 2014

Added CSCug84860 to Open Caveats.

A2

April 15, 2014

Added CSCuj36520 to Resolved Caveats.

A3

May 6, 2014

Removed 5.0(3) from Table 5 - Supported Upgrade and Downgrade Paths.

OL-27874-08

A0

June 30, 2014

Created NX-OS Release 6.0(2)N2(5) release notes.

B0

July 9, 2014

Added CSCuj87061 to 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 5500 Series device and the Cisco Nexus 2000 Series Fabric Extender (FEX) to improve the performance, scalability, and management of the product line. Cisco NX-OS Release 6.0 also supports all hardware and software supported in Cisco NX-OS Release 5.1, Cisco NX-OS Release 5.0.

Cisco Nexus Devices

The Cisco Nexus devices 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 devices for data center applications.

For information about the Cisco Nexus 5500 Series, see the Cisco Nexus 5500 Series 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 5500 Series devices 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 device, which allows zero-touch provisioning and automatic configuration. The FEX provides a single point of management that supports a large number of servers and hosts that can be configured with the same feature set as the parent Cisco Nexus 5500 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 5500 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 devices. Starting with Cisco NX-OS Release 6.0(2)N1(2), the Cisco Nexus 5010 and 5020 switches are not supported. You can find detailed information about supported hardware in the Cisco Nexus 5500 Series Hardware Installation Guide .

Table 2 shows the hardware supported by Cisco NX-OS Release 6.0(x) software.

 

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

Cisco NX-OS Release Support
Hardware
Part Number
6.0(2)N2(5)
6.0(2)N2(4)
6.0(2)N2(3)
6.0(2)N2(1b)
6.0(2)N2(2)
6.0(2)N2(1)
6.0(2)N1(2)
6.0(2)N1(1)
Cisco Nexus 5500 Series

 

 

 

Cisco Nexus 5596T switch1

N5K-C5596T-FA

X

X

Cisco Nexus 5596UP switch

N5K-C5596UP-FA

X

X

Cisco Nexus 5548UP switch

N5K-C5548UP-FA

X

X

Cisco Nexus 5548P switch

N5K-C5548P-FA

X

X

Cisco Nexus 2000 Series

 

 

 

Cisco Nexus B22DELL FEX2

N2K-B22DELL-P

X

X

Cisco Nexus B22IBM FEX3 4

N2K-B22IBM-P

X

X

Cisco Nexus 2248PQ FEX5

N2K-C2248PQ-10GE

X

X

Cisco Nexus 2232TM-E FEX6

N2K-C2232TM-E-
10GE

X

X

Cisco Nexus B22F FEX

N2K-B22FTS-P

X

X

Cisco Nexus B22HP FEX7

N2K-B22HP-P

X

X

Cisco Nexus 2232TM FEX

N2K-C2232TM-
10GE

X

X

Cisco Nexus 2232PP FEX

N2K-C2232PP-10GE

X

X

Cisco Nexus 2248TP-E FEX

N2K-C2248TP-E-
1GE

X

X

Cisco Nexus 2248TP FEX

N2K-C2248TP-1GE

X

X

Cisco Nexus 2224TP FEX

N2K-C2224TP-1GE

X

X

Cisco Nexus 2148T FEX

N2K-C2148T-1GE

8

9

Expansion Modules

 

 

 

4-port QSFP+ 10GBE GEM

N55-M4Q

X

X

12-port 10GBASE-T GEM10

N55-M12T

X

X

16-port Universal GEM

N55-M16UP(=)

X

X

N5596 Layer 3 GEM

N55-M160L3(=)

X

X

N5548 Layer 3 daughter card

N55-D160L3(=)

X

X

Layer 3 GEM

N55-M160L3-V2

X

X

Version 2 Layer 3 daughter card

N55-D160L3-V2

X

X

16-port SFP+ Ethernet

N55-M16P(=)

X

X

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

N55-M8P8FP(=)

X

X

Transceivers

 

 

 

Fabric Extender Transceivers

 

 

 

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

FET-10G(=)

X

X

SFP+ Optical

 

 

 

Cisco 40GBASE-LR4 QSFP+ Module for SMF

QSFP-40GE-LR4

6.0(2)N1(2) only

6.0(2)N1(2) only

4x10-Gigabit QSFP module

QSFP-4SFP10G-
CU1M

X

X

4x10-Gigabit QSFP module

QSFP-4SFP10G-
CU3M

X

X

4x10-Gigabit QSFP module

QSFP-4SFP10G-
CU5M

X

X

4x10-Gigabit QSFP module

QSFP-4SFP10G-
ACu7M

X

X

4x10-Gigabit QSFP module

QSFP-4SFP10G-
ACu10M

X

X

Cisco 40GBASE-CR4 QSFP+ to 4 10GBASE-CU SFP+ direct-attach breakout 7-meter cable, active

QSFP-4X10G-AC7M

6.0(2)N1(2) only

6.0(2)N1(2) only

Cisco 40GBASE-CR4 QSFP+ to 4 10GBASE-CU SFP+ direct-attach breakout 10-meter cable, active

QSFP-4X10G-
AC10M

6.0(2)N1(2) only

6.0(2)N1(2) only

Gigabit Ethernet SFP, LX transceiver11

GLC-LX-SMD

X

X

Gigabit Ethernet SFP, EX transceiver12

GLC-EX-SMD

X

X

1000BASE-ZX SFP transceiver module for SMF

GLC-ZX-SM(=)

X

X

10-Gigabit Ethernet—short range SFP+ module

SFP-10G-SR(=)

X

X

10-Gigabit Ethernet—long range SFP+ module

SFP-10G-LR(=)

X

X

10-Gigabit Ethernet—extended range SFP+ module

SFP-10G-ER(=)

X

X

1000BASE-T standard

GLC-T(=)

X

X

Gigabit Ethernet SFP, LC connector SX transceiver (MMF)

GLC-SX-MM

X

X

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

GLC-SX-MMD

X

X

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

GLC-LH-SM

X

X

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

GLC-LH-SMD

X

X

SFP+ Copper

 

 

 

10GBASE-CU SFP+ Cable (1 meter)

SFP-H10GB-
CU1M(=)

X

X

10GBASE-CU SFP+ Cable (3 meters)

SFP-H10GB-
CU3M(=)

X

X

10GBASE-CU SFP+ Cable (5 meters)

SFP-H10GB-
CU5M(=)

X

X

10GBASE-CU SFP+ Cable (7 meters)

SFP-H10GB-
ACU7M(=)

X

X

10GBASE-CU SFP+ Cable (10 meters)

SFP-H10GB-
ACU10M(=)

X

X

10GBASE CU SFP+ cable13

SFP-H10GB-CU1.5M

X

X

10GBASE CU SFP+ cable14

SFP-H10GB-CU2M

X

X

10GBASE CU SFP+ cable15

SFP-H10GB-CU2.5M

X

X

Fibre Channel

 

 

 

8-Gbps Fibre Channel—short wavelength

DS-SFP-FC8G-
SW(=)

X

X

8-Gbps Fibre Channel—long wavelength

DS-SFP-FC8G-
LW(=)

X

X

4-Gbps Fibre Channel—short wavelength

4DS-SFP-FC4G-
SW(=)

X

X

4-Gbps Fibre Channel—long wavelength

4DS-SFP-FC4G-
LW(=)

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

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

SFP-GE-S(=)

X

X

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

SFP-GE-L(=)

X

X

Converged Network Adapters

 

X

X

Generation-1 (Pre-FIP) CNAs16

 

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 B22IBM FEX is supported with Cisco NX-OS Release 6.0(2)N2(1b)

4.The Cisco Nexus B22IBM FEX is not supported with Cisco NX-OS Release 6.0(2)N2(2)

5.The Cisco Nexus 2248PQ FEX does not support Gen1 cables.

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

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

8.Starting with Cisco NX-OS Release 6.0(2)N1(1), 2148T FEX is not supported on Cisco Nexus 5500 series devices.

9.Starting with Cisco NX-OS Release 6.0(2)N1(1), 2148T FEX is not supported on Cisco Nexus 5500 series devices.

10.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).

11.Added support for Gibabit Ethernet SFP LX transceiver starting with Cisco NX-OS Release 6.0(2)N1(2).

12.Added support for Gibabit Ethernet SFP EX transceiver starting with Cisco NX-OS Release 6.0(2)N1(2).

13.Added support for 10GBASE CU SFP+ cable starting with Cisco NX-OS Release 6.0(2)N1(2).

14.Added support for 10GBASE CU SFP+ cable starting with Cisco NX-OS Release 6.0(2)N1(2).

15.Added support for 10GBASE CU SFP+ cable starting with Cisco NX-OS Release 6.0(2)N1(2).

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

 

Table 3 Hardware Supported by Cisco NX-OS Release 6.0(x) Software

Cisco NX-OS Release Support
Hardware
Part Number
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(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)
Cisco Nexus 5500 Series

 

 

 

 

 

 

 

Cisco Nexus 5596T switch17

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

Cisco Nexus 2000 Series

 

 

 

 

 

 

 

Cisco Nexus B22DELL FEX18

N2K-B22DELL-P

X

Cisco Nexus 2248PQ FEX19

N2K-C2248PQ-10GE

Cisco Nexus 2232TM-E FEX20

N2K-C2232TM-E-
10GE

X

Cisco Nexus B22F FEX

N2K-B22FTS-P

X

Cisco Nexus B22HP FEX21

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

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

Cisco Nexus 2224TP FEX

N2K-C2224TP-1GE

X

X

X

X

X

X

Cisco Nexus 2148T FEX

N2K-C2148T-1GE

X

X

X

X

X

X

Expansion Modules

 

 

 

 

 

 

 

4-port QSFP+ 10GBE GEM

N55-M4Q

12-port 10GBASE-T GEM22

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

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

N55-M8P8FP(=)

X

X

X

X

X

X

Transceivers

 

 

 

 

 

 

 

Fabric Extender Transceivers

 

 

 

 

 

 

 

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

FET-10G(=)

X

X

X

X

X

X

SFP+ Optical

 

 

 

 

 

 

 

Cisco 40GBASE-LR4 QSFP+ Module for SMF

QSFP-40GE-LR4

 

 

 

 

 

 

4x10-Gigabit QSFP module

QSFP-4SFP10G-
CU1M

 

 

 

 

 

 

4x10-Gigabit QSFP module

QSFP-4SFP10G-
CU3M

 

 

 

 

 

 

4x10-Gigabit QSFP module

QSFP-4SFP10G-
CU5M

 

 

 

 

 

 

4x10-Gigabit QSFP module

QSFP-4SFP10G-
ACu7M

 

 

 

 

 

 

4x10-Gigabit QSFP module

QSFP-4SFP10G-
ACu10M

 

 

 

 

 

 

Cisco 40GBASE-CR4 QSFP+ to 4 10GBASE-CU SFP+ direct-attach breakout 7-meter cable, active

QSFP-4X10G-AC7M

 

 

 

 

 

 

Cisco 40GBASE-CR4 QSFP+ to 4 10GBASE-CU SFP+ direct-attach breakout 10-meter cable, active

QSFP-4X10G-
AC10M

 

 

 

 

 

 

Gigabit Ethernet SFP, LX transceiver23

GLC-LX-SMD

 

 

 

 

 

 

Gigabit Ethernet SFP, EX transceiver24

GLC-EX-SMD

 

 

 

 

 

 

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

10-Gigabit Ethernet—long range SFP+ module

SFP-10G-LR(=)

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

X

Gigabit Ethernet SFP, LC connector SX transceiver (MMF)

GLC-SX-MM

X

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

X

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

GLC-LH-SM

X

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

X

SFP+ Copper

 

 

 

 

 

 

 

10GBASE-CU SFP+ Cable (1 meter)

SFP-H10GB-
CU1M(=)

X

X

X

X

X

X

10GBASE-CU SFP+ Cable (3 meters)

SFP-H10GB-
CU3M(=)

X

X

X

X

X

X

10GBASE-CU SFP+ Cable (5 meters)

SFP-H10GB-
CU5M(=)

X

X

X

X

X

X

10GBASE-CU SFP+ Cable (7 meters)

SFP-H10GB-
ACU7M(=)

X

X

X

X

X

X

10GBASE-CU SFP+ Cable (10 meters)

SFP-H10GB-
ACU10M(=)

X

X

X

X

X

X

10GBASE CU SFP+ cable25

SFP-H10GB-CU1.5M

 

 

 

 

 

 

10GBASE CU SFP+ cable26

SFP-H10GB-CU2M

 

 

 

 

 

 

10GBASE CU SFP+ cable27

SFP-H10GB-CU2.5M

 

 

 

 

 

 

Fibre Channel

 

 

 

 

 

 

 

8-Gbps Fibre Channel—short wavelength

DS-SFP-FC8G-
SW(=)

X

X

X

X

X

X

8-Gbps Fibre Channel—long wavelength

DS-SFP-FC8G-
LW(=)

X

X

X

X

X

X

4-Gbps Fibre Channel—short wavelength

4DS-SFP-FC4G-
SW(=)

X

X

X

X

X

X

4-Gbps Fibre Channel—long wavelength

4DS-SFP-FC4G-
LW(=)

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

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

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

SFP-GE-L(=)

X

X

X

X

X

X

Converged Network Adapters

 

 

 

 

 

 

 

Generation-1 (Pre-FIP) CNAs28

 

X

X

X

X

X

X

17.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).

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

19.The Cisco Nexus 2248PQ FEX does not support Gen1 cables.

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

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

22.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).

23.Added support for Gibabit Ethernet SFP LX transceiver starting with Cisco NX-OS Release 6.0(2)N1(2).

24.Added support for Gibabit Ethernet SFP EX transceiver starting with Cisco NX-OS Release 6.0(2)N1(2).

25.Added support for 10GBASE CU SFP+ cable starting with Cisco NX-OS Release 6.0(2)N1(2).

26.Added support for 10GBASE CU SFP+ cable starting with Cisco NX-OS Release 6.0(2)N1(2).

27.Added support for 10GBASE CU SFP+ cable starting with Cisco NX-OS Release 6.0(2)N1(2).

28.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 4 shows the hardware and Cisco NX-OS Release 6.x software that supports online insertion and removal (OIR).

Table 4 Online Insertion and Removable Support by Cisco NX-OS Release 6.x Software

Hardware
Part Number
Cisco NX-OS Release Support
6.0(2)N2(5)
6.0(2)N2(4)
6.0(2)N2(3)
6.0(2)N2(1b)
6.0(2)N2(2)
6.0(2)N2(1)
6.0(2)N1(2)
6.0(2)N1(1)
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(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)
Cisco Nexus 5500 Series
 

 

 

 

 

 

 

 

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

Expansion Modules

 

 

 

 

 

 

 

 

16-port Universal GEM

N55-M16UP(=)

X

X

X

X

X

X

Layer 3 GEM 1

N55-M160L3-V229

Version 2 Layer 3 daughter card 1

N55-D160L3-V2 1

16-port SFP+ Ethernet

N55-M16P(=)

X

X

X

X

X

X

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

N55-M8P8FPL(=)

X

X

X

X

X

X

N5596 Layer 3 GEM 1

N55-M160L3(=) 1

N5548 Layer 3 daughter card 1

N55-D160L3(=) 1

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

New and Changed Features

This section describes the new features introduced in Cisco NX-OS Release 6.x. This section includes the following topics:

New Software Features in Cisco NX-OS Release 6.0(2)N2(5)

There are no new software features in this release.

New Software Features in Cisco NX-OS Release 6.0(2)N2(4)

There are no new software features in this release.

New Software Features in Cisco NX-OS Release 6.0(2)N2(3)

There are no new software features in this release.

New Software Features in Cisco NX-OS Release 6.0(2)N2(2)

Cisco NX-OS Release 6.0(2)N2(2) is a maintenance release that includes bug fixes and the following software features and enhancements:

Command Addition: cts role-based batched-programming

Enabling CTS Batch Programming by entering the cts role-based batched-programming command enables faster programming on SGACLs associated with large numbers of SGT,DGT pairs.

Bidirectional Forwarding Detection

Bidirectional Forwarding Detection (BFD) is a detection protocol designed to provide fast forwarding-path failure detection times for media types, encapsulations, topologies, and routing protocols. Starting with Release 6.0(2)N2(1), the Cisco Nexus 5500 supports BFD for BGP, EIGRP, OSPF, PIM, HSRP, VRRP, and static routes.

Command Update: show lldp system -detail

The show lldp command now includes an optional keyword for displaying system details.

Default Interface

You can use the default interface command to clear the existing configuration of multiple interfaces and return them to default settings. The command can be used for interfaces such as Ethernet, loopback, VLAN network, port-channel, and tunnel interfaces. You can use the checkpoint keyword with the command to create a copy of the interface configuration before clearing it so that you can restore it later.

Embedded Event Manager Support

The Embedded Event Manager (EEM) monitors events that occur on your device and takes action to recover from or troubleshoot these events, based on your configuration. You can use EEM to create policies that consist of a set of actions to be taken in response to a specific event. EEM can be controlled through CLI commands or Vsh scripts.

Network Time Protocol Server

A Cisco Nexus 5500 switch can use the Network Time Protocol (NTP) to synchronize the network. Other devices can be configured to use the switch as an NTP time server. In an isolated network, the switch can be configured as an authoritative NTP clock source.

An NTP server usually receives its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server, and then distributes this time across the network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize two devices to within a millisecond of each other.

Policy Based Routing

The Cisco Nexus 5500 now supports policy-based routing (PBR). PBR allows you to configure a defined policy for IPv4 and IPv6 traffic flows, lessening reliance on routes derived from routing protocols.

DHCPv4-relay and DHCPv6-relay

Up to 32 DHCP server addresses can now be configured on an interface. Previously, the maximum number of configurable server addresses was 16.

FEX Host Interface Storm Control

HIF Storm control allows ingress traffic suppression for unknown multicast, broadcast, and unknown unicast traffic on Fabric Extender (FEX) Host Interface (HIF) ports and port channels.

Scalability Enhancements

As documented in the release specific Verified Scalability for Cisco Nexus 5500 Series documents, configuration limits (verified scalability) for several Layer 2 switching functions has increased. Verified and maximum limits have changed for some features, including:

  • Channels/vPCs
  • EtherChannels
  • IGMP Snooping groups
  • Logical interfaces (PVs)
  • Number of FEX ports
  • Number of switchports

SNMP Bridge-MIB and LLDP MIB

SNMP Bridge and LLDP MIBs have been published.

vPC Shutdown

You can use the vPC shutdown command to isolate a switch from the vPC complex. The switch can then be debugged, reloaded, or removed physically, without affecting the vPC traffic going through the nonisolated switch.

vPC+ Routing Protocol Peering

Added support for routing unicast and multicast protocol over vPC+.

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

Cisco NX-OS Release 6.0(2)N1(2) is a maintenance release that includes bug fixes and the following software features and enhancements:

802.1x Authentication

Support added for the IEEE 802.1X, which provides a client-server-based access control and authentication protocol that restricts unauthorized devices from connecting to a LAN through publicly accessible ports. The authentication server authenticates each client connected to a switch port before making available any services offered by the switch or the LAN.

FEX NIF Storm Control

The NIF Storm Control feature allows configuration on a Satellite Fabric port to all the pinned FEX HIF ports regardless of whether it is a logical or a physical HIF. In addition, a new syslog message informs the user when a switch port that has a Storm Control configuration is starting to see a storm of broadcast, multicast, or unicast when it starts dropping packets. You see another syslog message when the storm stops.

IP-Directed Broadcast

You can use an IP-directed broadcast to send a broadcast from a device that is not directly connected to the destination IP subnet. An ACL name can be specified for the broadcast. (This resolves caveat CSCuh1963.)

iSCSI TLV Configuration

As documented in the Cisco Nexus 5500 Series NX-OS SAN Switching Configuration Guide, Release 6.x, NICs and converged network adapters connected to a Cisco Nexus 5500 Series switch can use iSCSI as a storage protocol and can be programmed to accept the configuration values sent by the switch leveraging data center bridging exchange protocol (DCBX). DCBX negotiates configuration and settings between the switch and the adapter through a variety of type-length-values (TLV) and sub-TLVs. This process allows the switch to distribute configuration values to all attached adapters from a centralized location instead of having to manually program CoS markings on each individual server and adapter.

Port Channel Minimum Links

Added support to configure a minimum number of links for the port channel so that when a certain number of port-channel member ports go down, the host-facing interfaces are suspended.

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

Cisco NX-OS Release 6.0(2)N1(1) includes bug fixes and the following software features and enhancements:

Ingress Policing

Policing allows you to monitor the data rates for a particular class of traffic. When the data rate exceeds user-configured values, the switch drops packets immediately. Because policing does not buffer the traffic, transmission delays are not affected. When traffic exceeds the data rate, you instruct the system to drop the packets. You can define single-rate and two-color ingress policing.

Glean Throttling

When forwarding an incoming IP packet in a line card, if the Address Resolution Protocol (ARP) request for the next hop is not resolved, the line card forwards the packets to the supervisor, referred to as glean throttling. The supervisor resolves the MAC address for the next hop and programs the hardware.

The Cisco Nexus 5500 Series device hardware has glean rate limiters to protect the supervisor from the glean traffic. If the maximum number of entries is exceeded, the packets for which the ARP request is not resolved continues to be processed in the software instead of getting dropped in the hardware.

When an ARP request is sent, the software adds a /32 drop adjacency in the hardware to prevent the packets to the same next-hop IP address from being forwarded to the supervisor. When the ARP entry is resolved, the hardware entry is updated with the correct MAC address. If the ARP entry is not resolved before a timeout period, the entry is removed from the hardware.

ACL Logging

The ACL logging feature allows the logging of packets that hit the IPv4 ACLs. The log messages are displayed on a flow basis. The flow is identified using a combination of the IP source address, destination address, L4 protocol, and the L4 source/destination ports on an interface. The log message is generated under the following conditions:

  • INFO message—When a new flow is created
  • WARNING message—When the packet threshold is reached for a flow
  • Configurable INFO message—At the end of a periodic interval containing information on the number of packets to hit the flow. The interval default is 5 minutes.

NoteWhen the number of flows exceed a threshold in the given interval, a warning message is logged, and that flow is not added to the logging cache. When the number of flows exceed a threshold in the given interval, a warning message is logged, and that flow is not added to the logging cache.


POAP Enhancement

POAP enhancements include hostname- and MAC address-based configuration file selection, TCL or Python script logging, and a remote syslog facility.

BGP Enhancement

BGP enhancements include BGP Allow-AS-in, local-AS, prefix-peering, AS-path relax, and remove-private-AS.

VRF Route Leaking

Support for VRF route leaking enables the sharing of routes that were previously visible and available only in segmented networks.

FCoE over 10GBASE-T

FCoE configuration is supported over 10GBASE-T using Cat6a and Cat7 cables up to a distance of 30 m.

Open Management Infrastructure

The Open Management Infrastructure (OMI) agent is a web server that runs on the Cisco Nexus switch. It is based on the Common Infrastructure Model (CIM) standard, which is an open standard that defines a schema for representing managed resources (for example, CPUs, disks, networks, processes, and so on.). The OMI agent enables you to perform the following operations:

New Hardware Features in Cisco NX-OS Release 6/0(2)N2(5)

Cisco NX-OS Release 6.0(2)N2(5) supports the following new hardware:

  • QSA Optics with 10G SR

New Hardware Features in Cisco NX-OS Release 6.0(2)N2(1b)

Cisco NX-OS Release 6.0(2)N2(1b) supports the following new hardware:

  • N2K-B22IBM-P—Cisco Nexus B22 Fabric Extender for IBM

New Hardware Features in Cisco NX-OS Release 6.0(2)N2(1)

No new hardware features have been introduced with this release.

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

Cisco NX-OS Release 6.0(2)N1(2) supports the following new hardware:

  • 4-port QSFP+ Nexus N55-M4Q GEM
  • New power supplies for Cisco Nexus 5596T and Cisco Nexus 5596UP switches:

Cisco Nexus 1100 W AC front-to-back power supply (PID: NXA-PAC-1100W)

Cisco Nexus 1100 W AC back-to-front power supply (PID: NXA-PAC-1100W-B)

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

  • New transceivers:

QSFP-4X10G-AC7M

QSFP-4X10G-AC10M

QSFP-40G-LR4

SFP-H10GB-CU1.5M

SFP-H10GB-CU2M

SFP-H10GB-CU2.5M

GLC-LH-SMD

GLC-EX-SMD

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

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

  • Cisco Nexus 2248PQ 10-Gigabit FEX

Upgrading or Downgrading to a New Release

This section describes the upgrade and downgrade paths that are supported for Cisco NX-OS Release 6.0(2)N2(5) on the Cisco Nexus device.

The section includes the following topics:

Upgrade and Downgrade Guidelines

The following guidelines apply to Cisco NX-OS Release 6.0(2)N2(5) for Cisco Nexus devices:

  • 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 device 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 6.0(2)N2(5). For more information, see the Cisco Nexus 5500 Series NX-OS Software Upgrade and Downgrade Guide, Release 6.0.

 

Table 5 Cisco NX-OS Release 6.0(2)N2(5) Supported Upgrade and Downgrade Paths

Current Cisco NX-OS Release
Upgrade to NX-OS Release 6.0(2)N2(5)
Downgrade from NX-OS Release 6.0(2)N2(5)

6.0(2)N2(1b)

Disruptive upgrade (ISSU)

Disruptive downgrade

6.0(2)N2(4)
6.0(2)N2(3)
6.0(2)N2(2)
6.0(2)N2(1)
6.0(2)N1(2a)
6.0(2)N1(2)
6.0(2)N1(1a)
6.0(2)N1(1)

Nondisruptive upgrade (ISSU)

Disruptive downgrade

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)

Nondisruptive upgrade (ISSU) 2

Disruptive downgrade

5.1(3)N2(1c)
5.1(3)N2(1b)30
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)31

Disruptive downgrade

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

31.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 6.0(2)N1(5).

  • Ingress inter-VLAN-routed Layer3 multicast packets are treated as “unknown multicast” by the storm-control feature. This is due to the Layer 3 forwarding design in the Cisco Nexus 5500 Series switch. For details, see CSCuh34068.
  • 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.
  • When an FC SPAN destination port is changed from SD to F mode and back to SD mode on an 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 an 802.3x pause.

speed 100 —Does not autonegotiate; pause cannot be advertised. The peer must be set to not autonegotiate and to 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 goes 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 nonedge designated forwarding ports are not allowed for an ISSU. For additional information, see CSCtf51577. For information about topologies that support a nondisruptive upgrade, see the Cisco Nexus 5500 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, 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 the traffic. For details, see CSCtf94558.

  • 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 device, 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 appear:
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 device, we recommend that you avoid partitioning 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 device 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) to Cisco NX-OS Release 5.1(3)N2(1) or later release 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 the 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 because it is an active VLAN on the secondary switch.
  • Rol-based Access Control List (RBACL) policy enforcement is performed on VLANs on which Cisco Trusted Security (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 5500 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 5500 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 device 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 switch virtual interface (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 a 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 the 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 device drops packets due to packet parsing errors. To work around this issue, enter the vlan dot1q tag native command 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 devices 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 devices 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, leave the speed set to 4 GB. For details, see CSCtx52991.
  • A nondisruptive ISSU is not supported when ingress policing is configured.
  • The maximum IP MTU that can be set on Layer 3 interfaces on which Layer 3 protocols are running is 9196, because of the internal header used inside the switch. The network-qos policy must be set to 9216.

Limitations on the Cisco Nexus Device

The limitations on the Cisco Nexus device 5500 Series devices are as follows:

SPAN Limitations on Fabric Extender Ports

The SPAN limitations on Fabric Extender ports are as follows:

  • On a Cisco Nexus device, if the SPAN source is a FEX port, the frames will always be tagged when leaving the SPAN destination.
  • 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 following error appears:

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), 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.

Note Each affected switchport command configuration must be entered separately. The example uses the switchport trunk allowed vlan 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

Note If you did not add the fex associate 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

Note If you did not add the fex associate 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.

Layer 3 Limitations

Asymmetric Configuration

In a vPC topology, two Cisco Nexus devices configured as vPC peer switches need to be configured symmetrically for Layer 3 configurations such as SVIs, the peer gateway, routing protocol and policies, and RACLs.


NoteThe vPC consistency check does not include Layer 3 parameters. The 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 by entering 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 6.0(2)N2(2).

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

 

Table 8 Cisco NX-OS Release 6.0x 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 and then back to FabricPath, some Hot Standby Router Protocol (HSRP) gateway-based traffic may be affected.

CSCu84860g

Software sends wrong FCF-MAC causing Nexus 4000 server adapters ports to go down.

CSCua27097

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

CSCuc12211

While copying files to the running configuration, some channel-group commands fail.

CSCuc25187

The config-sync process does not remove the VLAN QoS policy and offset configuration.

CSCuc43503

The IGMP vPC optimization knob does not work when feature-set virtualization is configured.

CSCud43962

CDPv6 shows the address of different interfaces, not the connected interfaces.

CSCud48710

Layer 2 Multicast traffic can be lost for one to two minutes on an unshut of the fabric PO in an AA topology. This happens only under the following conditions:

  • AA topology
  • The group is downgraded to V2 of a V3 receiver.
  • The FEX fabric port is shut on one side.
  • When the fabric port is unshut, Layer 2 multicast traffic loss might be seen until the next join comes in.

CSCud53059

DAI is blocking traffic for FEX HIF ports.

CSCud72942

When all FEXes are reloaded at the same time, Layer 2 Multicast traffic may not recover on one of the FEX HIF ports.

CSCue22038

After a module is powered off, a timeout occurs for the line card removal sequence. As a result, the slot becomes unusable and must be reloaded.

CSCue33173

IPSG blocks traffic for private VLAN isolated trunk ports, even when a valid DHCP snooping binding entry exists.

CSCuf16457

On a Cisco Nexus 5500 switch, applying policy maps fails with the error %RPM-2-PPF_SES_VERIFY.

CSCuf47724

On a Cisco Nexus 5500 switch, SVI Counters show incorrect results.

CSCuf52331

The minimum suppression value needs to be handled properly in switch/HIF/NIF storm-control.

CSCuf82183

In some scenarios, policy statistics are not enabled when a service policy is applied to ports.

CSCug72465

A test harness does not properly treat closing of the TCP flow.

CSCug90859

On the Cisco Nexus 5500 switch, PBR does not work on a PVLAN SVI.

CSCug98105

Cisco Nexus 5500-BGP v6 peering is not coming up if the same address in a different VRF uses MD5.

CSCuh04973

The default-interface command is not resetting the speed command on an HIF port-channel interface.

CSCuh17828

On a Cisco Nexus 5500 switch, when the command sequence copy file start is used, copying the saved configuration to the running configuration takes too long.

CSCuh25992

A Cisco Nexus 5500 switch running BFD over a Layer 3 port-channel may be reset by a kernel crash if the port-channel has more than 10 members.

CSCuh26111

N64P- Some mroutes are not removed from the last hop router following an admin shut of the SVI.

CSCuh30885

RBACL update and programming fails in certain scenarios.

CSCuh34068

Ingress inter-VLAN-routed Layer 3 multicast packets are treated as “unknown multicast” by the storm-control feature.

CSCuh36797

PIM process restart CLI is visible but not supported on the Cisco Nexus 5500.

CSCuh36961

A QoS policy with qos-group 1 cannot be applied on a non-FCoE class.

CSCuh44777

Support should be available to log enabled IP ACL as a class-map match.

CSCui94565

Service not responding under certain CTS scale scenarios.

CSCuj87061

Port mode FC lost after upgrading to 6.x.

CSCul27686

Interfaces might go down after upgrade and cannot be recovered.

Resolved Caveats in Cisco NX-OS Release 6.0(2)N2(5)

 

Table 9 Cisco NX-OS Release 6.0(2)N2(5) Resolved Caveats

Record Number
Resolved Caveat Headline

Nexus 5000 not able to suppress Sev5 syslog messages related with connected FEX.

CSCud07967

Sysmgr service "fcoe_mgr" crashed.

Nexus 5000 might experience unexpected reboot when issuing show tech (tac-pac)

CSCue71612

Nexus 5548 Silent Reload with i2c code 0x0100.

CSCue80077

FEX: Port flap request from SAP: MTS_SAP_SATMGR.

Nexus 5596 ethpm hap reset.

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

CSCuh56328

Netstack panic when closing the socket with sbuff lock acquired.

Cannot get counters of if-mib for SVI.

mts recv_q SNMP Response SAP - stp+dot1dBridge+qBridge.

OpenSSH LoginGraceTime denial of service vulnerability.

Unable to configure bbcredit values more than 64.

Nexus switch crash in SNMPd w/ RMON traps Configured.

Snmpwalk: stpxRSTPPortRoleValue in the CISCO-STP-EXTENSIONS MIB broken.

CSCuj42061

VLAN in suspended mode after adding to FabricPath.

DHCP offers might not get relayed in FabricPath topologies.

aclmgr crash during sh tech.

False positive transceiver warnings on Nexus 5000

CSCul52253

VPC+ allocates ftag-1 and ftag-2 as active.

HIF stays down when blade server moved into new slot.

Multiple tacacsd processes running causing authentication failures.

CSCum13332

Changes to input voltage logging.

Nexus 5000 kernel panic crash usd_mts_kthread.

Tacacs+ per CLI authorization failure upon entering CLI > 64 char.

Cisco NX-OS software TACACS+ command authorization vulnerability.

Add STP-edge port config to "mac address-table loop-detect port-down".

Peer-link STP inconsistency due to corrupt BPDU does not clear.

CSCum79187

Core due to AAA process hap reset.

Not able to pass traffic over Eth ports with FC and Fabricpath config

CSCum90179

Fabricpath ECMP issue with packet forwarding.

Packets discarded on ingress.

Zone hap reset.

CSCun67627

LACP Hap Reset while executing the show lacp interface command.

Nexus 5000 VPC incorrect SVI type-2 inconsistency syslog.

CSCun97052

RBACL policies not correctly programmed in TCAM.

Network-operator role can view sensitive configuration.

Nexus 55xx DCBX negotiating to CIN mode.

CSCuo18604

CTS change of any-any policy not effective after the first download.

CSCuo20517

Unexpected reboot on Nexus after enabling IPv6 DHCP relay.

CSCuo41201

Netstack buffer leaking with IPv6 feature running.

Resolved Caveats in Cisco NX-OS Release 6.0(2)N2(4)

 

Table 10 Cisco NX-OS Release 6.0(2)N2(4) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCud45836

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

CSCue55816

ppm core file size should be set properly to avoid truncation.

CSCue76773

ip routing multicast software-replicate.

CSCuh67647

Many Tacacsd zombie processes can be seen.

CSCuj36520

Reload due to PIM process crash.

CSCuj48079

Unable to ping VM to and from switch via VDP - non default vrf TF.

CSCuj85007

vPC+ mac not synced when one switch comes back online from reload

CSCul62250

Link debounce time not working as expected.

CSCul89905

Layer 2 control packets dropped on CTS links with SGT encapsulation.

CSCul90150

FWM HAP reset causing both switches in vPC to crash.

CSCum29831

VSHD_SYSLOG_EOL_ERR when entering the show version command.

CSCum62719

fcoe_mgr crashes when entering the show platform software fcoe_mgr info global command.

Resolved Caveats in Cisco NX-OS Release 6.0(2)N2(3)

 

Table 11 Cisco NX-OS Release 6.0(2)N2(3) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCuf90644

STP BPDUs sent with different MAC with peer-switch after upgrade.

CSCuh33604

MAC learning issue

CSCui47367

"shut/no shut" for vfc crashed device due to FWM hap reset.

CSCui79701

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

CSCuj32483

LACP member ports stuck in I state.

CSCuj40011

Unexpectedly reloaded due to dhcp_snoop hap reset.

CSCuj56227

IGMP proxy reports might loop on the network.

CSCuj59439

vPC hap reset after peer-keepalive link comes up.

CSCuj92481

ISSU 6.0.2.N1.1 to 6.0.2.N2.2 free space below threshold.

CSCul05896

When switching from HSRP standby deletes HSRP VMAC from hardware.

CSCul20086

The snmpd process crash on Nexus tied to user permissions.

CSCul27686

After Upgrade Interface Down & Unrecoverable.

Resolved Caveats in Cisco NX-OS Release 6.0(2)N2(2)

 

Table 12 Cisco NX-OS Release 6.0(2)N2(2) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCty33679

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

CSCud33607

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

CSCue65973

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

CSCug79384

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

CSCuh31035

IP-MIB returns length of ipaddress as part of snmp instance.

CSCuh57927

FEX hardware type changed after ISSU/ISSD.

CSCui08344

Multicast convergence improvements.

CSCuj29678

pm-dbr or bfdc thread could cause kernel crash.

Resolved Caveats in Cisco NX-OS Release 6.0(2)N2(1)

Table 13 lists the caveats that are resolved in Cisco NX-OS Release 6.0(2)N2(1).

 

Table 13 Cisco NX-OS Release 6.0(2)N2(1) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCug32189

A BGP process fails when a socket cannot be created due to a bad file descriptor.

CSCub50434

VTP packets loop on vPC.

CSCuf61304

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

CSCuf21318

On a Cisco Nexus 5000 Series switch running vPC when the vPC peer-link goes down, the secondary vPC switch flaps its vPC port-channels for a short period before bringing them down permanently.

CSCud03634

RIP keeps advertising a route even though the original advertising source is down.

CSCue24735

A Cisco Nexus 5000 Series switch router has a MAC-address entry for a virtual MAC with an incorrect outgoing interface during HSRP state transition.

CSCub73193

BGP bestpath run stalls due to a bug in the BGP-ULIB flow control logic.

CSCuc62084

DCNM rediscovers a Cisco Nexus device continuously even when logs are not wrapped.

CSCuc35483

Activation of a zoneset in a VSAN in Interop Mode 1 fails.

CSCuf08921

A Cisco Nexus 5000 Series switch does not refresh a FabricPath MAC entry when a GARP is received on the FabricPath.

CSCuc84457

A BGP password cannot be added or removed without a process restart.

CSCud69928

When duplicate DBD packets are received, a Cisco Nexus switch may increment sequence numbers incorrectly.

CSCua97463

In an OSPF process, a default-information originate configuration behaves inconsistently.

CSCuc16550

Crashes occur due to a memory leak in ipqosmgr .

CSCuc55910

A memory leak occurs in an EIGRP process.

CSCuc91171

The NX-OS operating system fails to save the running configuration, and the following error message is displayed: Service "fcns" failed to save its configuration.

CSCug38090

An snmpd process crashes.

CSCug42375

The same CoS value is matched between class-fcoe and any other class, which may prevent QoS policies from being downloaded.

CSCug69534

A memory leak in the FWM process causes the process to crash.

CSCug98056

An IGMP table fails to update correctly when an IGMP join occurs.

CSCuh00696

IGMP reports are not forwarded out of non-core Mrouter ports.

CSCua42827

For sources connected across vPC, mroutes are not created.

CSCua69620

When a vPC peer link goes down, it does not delete MAC entries on the vPC secondary.

CSCua94509

After a fabric port is moved, trying to unconfigure a FEX configuration causes an error.

CSCub44349

Restart FP causes transient traffic outages.

CSCub48277

Frames are flooded while the switch is in the POAP discovery phase.

CSCub48506

When the channel-group command is used over an LACP port channel to change a port from passive to active or vice versa, the command appears to work but does not change the configuration.

CSCub55990

After executing the default address-family ipv4 unicast command under a BGP neighbor definition, the prefixes from that neighbor disappear from the BGP table.

CSCub77319

In Config sync mode, the port profile is missing a description command.

CSCub80303

A FEX attached to a Cisco Nexus 5000 Series switch crashes when the command phystats 1 1 is executed in a FEX command shell.

CSCub99717

When the redistribute static route-map < > command is used under RIP to redistribute specific prefixes, it leaks the default route in RIP.

CSCuc17458

For a VSAN that is in Enhance mode and configured for Interop mode, an active zoneset was deactivated following an ISSU.

CSCuc20817

A trunk port allows allocation of system-reserved VLANs after an ISSU upgrade.

CSCuc26101

When the auto-recovery timer is changed to any other value, error messages still indicate the timer value as the default (240 seconds).

CSCuc39303

When FEX interfaces are polled, satctrl hearbeats are lost.

CSCuc56790

An invalid path in two VRFs constantly triggers bestpath selection.

CSCuc72018

Static routes that are added while a VRF is shut down are not added to the RIB.

CSCuc73943

OSPF does not install all ECMP paths in the RIB.

CSCuc84599

A port-channel downstream from the Cisco Nexus 2000 is suspended by a vPC after interface changes are made with config-sync to nonrelated interfaces off the same FEX.

CSCuc92186

When several Peer-Templates have a common Peer-Session, and the Peer-Session is modified, the BGP adjacencies that use the Peer-Templates shut down and remain in this state.

CSCuc94629

If eBGP adjacency is formed through the disable-connected-check command instead of the ebgp-multihop command for eBGP peers that are not directly connected, creating a new Layer 3 interface bounces the eBGP session.

CSCuc93084

When the first prefix to send is rejected by the prefix lists, a BGP error is logged.

CSCuc95308

An M6RIB process crash occurs on the Cisco Nexus 5500 switch.

CSCuc97808

The NX-OS operating system does not set a BGP community or extended community when redistributing and connected to BGP under VRF.

CSCuc98282

A rollback fails for a FEX when NIF has defaulted.

CSCud00524

More specific PIM ASM RP configuration settings do not override a PIM bidir RP configuration.

CSCud04681

The FabricPath l2gstp peer-info table requires improvement.

CSCud08015

Cisco Nexus 5000 Series switch PTP multicast packets are dropped rather than forwarded.

CSCud25824

An OSPF dead timer is not maintained following a reload.

CSCud26463

Preprovision dynamic string changes and support for large commands are required.

CSCud41492

IGMP is not in sync with a peer vPC switch following simultaneous join and leaves.

CSCud59785

An intra-area summary route is not readvertised if a summary route exists.

CSCud61168

The IF counters for a FEX interface fall back frequently for one polling cycle.

CSCud87482

When the allowed VLAN list is changed in the port profile, it is not applied to all the port-channels where this port-profile is inherited.

CSCud90103

The Cisco Nexus 5500 switch changes the source address recorded in the IGMP v3 join message and reports an invalid group record message.

CSCue02015

Telnet to a nonmanagement SVI breaks following a reload.

CSCue21399

The 'Hot Standby' link on the vPC secondary does not become active after the vPC primary switch fails when MC-lag failover is used.

CSCue79907

A CLI command is needed to isolate a switch from the vPC complex.

CSCue81832

A hardware clock is out of sync prior to an ISSU and may cause the ISSU to fail.

CSCuf51541

On a VPC/VPC+ peer, if the HSRP active switch is reloaded, the HSRP standby removes the HSRP VMAC from its MAC address table.

CSCuf77723

The license grace period for certain features such as BGP does not work properly.

CSCug24976

The CLI control for ip pim register-until-stop is needed in Cisco Nexus 5500 and Cisco Nexus 5500 Series switches.

CSCtx21891

The control plane loses convergence across many protocols.

CSCug39029

An IGMP report floods back to the same HIF port on which it was received.

CSCtz85854

OSPF neighborship is not brought down, even when hello intervals are mismatched.

CSCua22284

SNMP walk does not display the power supply type for the FEX.

CSCug77133

The Cisco Nexus 5000 Series switch incorrectly programs the SPAN source port.

CSCug80833

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

CSCug90571

The service fcdomain crashes.

CSCug95929

Multiple FEXes go offline at the same time.

CSCug97032

ARP Traffic that arrives on a peer link is not classified.

CSCua23418

A Cisco Nexus 5000 Series switch does not update the serial number of a FEX power supply.

CSCua32166

In a Cisco Nexus 5000 Series switch, the IGMP Optimized Multicast Flood (OMF) feature is enabled by default, but the output of the show ip igmp snooping vlan command shows the feature as disabled for the VLAN.

CSCuh34674

Auto-negotiated speed does not appear correctly in the output for a show interface status up command.

CSCua50422

Call Home indicates a message has been sent successfully when no message is sent.

CSCtz70343

The CLI process crashes if the command line length is greater than 471 characters.

CSCub57655

A Cisco Nexus 5500 switch erroneously sends BGP community and route dates following a topology change.

CSCuc92190

When a Cisco Nexus 5500 switch redistributes the default route into BGP, the route shows up as invalid, which prevents the default route from being selected to a BGP bestpath.

CSCto98401

A Cisco Nexus switch is not able to flush the type 4 LSA.

CSCuc04285

The show ip ospf command shows an incorrect number of stubs/nssa areas after an HA trigger .

CSCuc23163

IGMP general queries are suppressed for prolonged periods, which could result in multicast packet loss.

CSCtx62151

The way accounting logs display config sync changes needs to be improved.

CSCug28099

The Cisco Nexus 5000 Series switch needs CLI control to disable ports after a loop is detected.

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

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

 

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

Record Number
Resolved Caveat Headline

CSCtw72949

There is a slow drain of UDP sock MTS buffers for some bulk requests in bridge-mib.

CSCud08015

N5K / PTP multicast packets are dropped instead of forwarded.

CSCue79881

SNMP crashes on SNMP bulk get query.

CSCuf17575

A /32 route has multiple ECMP next hops although only one is programmed in hardware.

CSCuf61304

NX-OS RPF on mroute incorrectly points to the RP for (S, G).

CSCug07482

Memory leak occurs at ppm with switch profile configured.

CSCug46504

DHCP relay does not work when the Bootp flag is set (Broadcast.)

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

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

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

Record Number
Resolved Caveat Headline

CSCtz62596

Receive error messages that repeat every 10 minutes. If you see the message for any other time interval or just one time, then it is not this bug. These messages do not affect the operation of the switch. It just does not allow the switch to get the power/input/voltage characteristics of the SFP on a port to show in the “show interface x/y transceiver details” output and you will see an error of “unknown error” at the end of the transceiver details output.

CSCud73169

The policer stats are not enabled if police action is added after apply to interface configuration.

CSCue22023

The system hap-resets with fcoe_mgr process core.

CSCue03528

The CFS locks on a Cisco Nexus 5500 device in a vPC due to the session manager not clearing.

CSCue34723

After changing the global MAC aging timer value to a nondefault value, the value resets to the default after ISSU.

CSCue35880

Link up on FEX ports is sometimes 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.

CSCue35996

After changing the per VLAN MAC aging timer to a nondefault value, reverting the timer value to the default value does not take effect in the running-configuration output.

CSCue36348

LACP-enabled FabricPath port-channel links do not come up between the Cisco Nexus 6000 and Cisco Nexus 7000 releases 6.1(0.174)S0, 5.2(3.30)S0 and later releases.

CSCue39246

In Cisco NX-OS Release 6.0(2)N1(1), the ethanalyzer detail output prints internal Nexus 5000 Series protocol headers. If ethanalyzer output is written as a .pcap file, Wireshark cannot open this .pcap file because it does not understand the headers.

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

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

 

Table 16 Cisco NX-OS Release 6.0(2)N1(1) Resolved Caveats

Record Number
Resolved Caveat Headline

CSCtt10736

With auto-recovery configured on a pair of Cisco Nexus devices 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.

CSCua23762

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

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.

MIB Support

The Cisco Management Information Base (MIB) list includes Cisco proprietary MIBs and many other Internet Engineering Task Force (IETF) standard MIBs. These standard MIBs are defined in Requests for Comments (RFCs). To find specific MIB information, you must examine the Cisco proprietary MIB structure and related IETF-standard MIBs supported by the Cisco Nexus 5500 Series switch.

The MIB Support List is available at the following FTP site:

ftp://ftp.cisco.com/pub/mibs/supportlists/nexus5000/Nexus5000MIBSupportList.html

Related Documentation

Documentation for Cisco Nexus 5500 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 documentation set includes the following types of documents:

  • Licensing Information Guide
  • Release Notes
  • Installation and Upgrade Guides
  • Configuration Guides
  • Configuration Examples and TechNotes
  • Programming Guides
  • Operations Guides
  • Error and System Message Guides
  • Field Notices
  • Security Advisories, Responses and Notices
  • Troubleshooting Guide
  • Command References
  • MIB Reference Guide

Documentation Feedback

To provide technical feedback on this document or to report an error or ommission, please send your comments to nexus5k-docfeedback@cisco.com . We appreciate your feedback.

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 deliver 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)