Cisco Nexus 6000 Series Switches

Table Of Contents

Cisco Nexus 6000 Series Release Notes,
Cisco NX-OS Release 6.0(2)

Contents

Introduction

Cisco Nexus 6000 Series 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)N1(2)

802.1x Authentication

FEX NIF Storm Control

Support for DELL FEX

Port-channel Minimum Links

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

Upgrading or Downgrading to a New Release

Upgrade and Downgrade Guidelines

Supported Upgrade and Downgrade Paths

Limitations

Limitations on the Cisco Nexus 6000

SPAN Limitations on Fabric Extender Ports

Layer 3 Limitations

Asymmetric Configuration

SVI

Caveats

Open Caveats

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

MIB Support

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Cisco Nexus 6000 Series Release Notes,
Cisco NX-OS Release 6.0(2)

---

Release Date: May 1, 2013
Part Number: OL-27905-02 B0

Current Release: NX-OS Release 6.0(2)N1(2)

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

---

Note Release notes are sometimes updated with new information about restrictions and caveats. See the following website for the most recent version of the Cisco Cisco Nexus 6000 and Cisco Nexus 2000 Series release notes: http://www.cisco.com/en/US/docs/switches/datacenter/nexus6000/sw/release/notes/Nexus_6000_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-27905-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	March 7, 2013	Added the Resolved Caveats in Cisco NX-OS Release 6.0(2)N1(2) and Upgrading or Downgrading to a New Release sections.
OL-27905-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.

---

Contents

This document includes the following sections:

•Introduction

•System Requirements

•New and Changed Features

•Online Insertion and Removal Support

•Upgrading or Downgrading to a New Release

•Limitations

•Caveats

•MIB Support

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

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 NX-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 6000 Series device and the Cisco Nexus 2000 Series Fabric Extender (FEX) to improve the performance, scalability, and management of the product line.

Cisco Nexus 6000 Series Devices

The Cisco Nexus 6000 Series includes 10 and 40 Gigabit Ethernet density in energy-efficient compact form factor switches. The Cisco Nexus 6000 Series Layer 2 and Layer 3 set allow for multiple scenarios such as: direct-attach 10 and 40 Gigabit Ethernet access and high-density Cisco Fabric Extender (FEX) aggregation deployments, leaf and spine architectures, or compact aggregation to build scalable Cisco Unified Fabric in the data centers.

Cisco Nexus 6000 Series products use the same set of Cisco application-specific integrated circuits (ASICs) and a single software image across the products within the family, thereby offering feature consistency and operational simplicity. Cisco Nexus 6000 Series switches support robust Layer 2 and Layer 3 functions, industry-leading FEX architecture with Cisco Nexus 2000 and Cisco Nexus B22 Blade FEX, In-Service Software Upgrade (ISSU), and Cisco FabricPath. Operational efficiency and programmability are enhanced on the Cisco Nexus 6000 Series through advanced analytics, PowerOn Auto Provisioning (POAP), and Python/Tool Command Language (Tcl) scripting.

For information about the Cisco Nexus 6000 Series, see the Cisco Nexus 6000 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 6000 Series devices to provide high-density and low-cost connectivity for server aggregation. Scaling across 1-Gigabit Ethernet, 10-Gigabit Ethernet, and 40-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 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 6000 Series Layer 2 Switching Configuration Guide.

System Requirements

This section includes the following topics:

•Hardware Supported

•Online Insertion and Removal Support

Hardware Supported

The Cisco NX-OS software supports the Cisco Nexus 6000 Series switch. You can find detailed information about supported hardware in the Cisco Nexus 6000 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)N1(1)	6.0(2)N1(2)
Cisco Nexus 6000 Series
Cisco Nexus 6001 switch	N6K-6001-	—	X
Cisco Nexus 6004 switch	N6K-6004-96Q	X	X
Cisco Nexus 2000 Series
Cisco Nexus B22 DELL FEX	N2K-B22DELL-P	—	X
Cisco Nexus 2232TM-E FEX	N2K-C2232TM-E-10GE	X	X
Cisco Nexus B22F FEX	N2K-B22FTS-P	X	X
Cisco Nexus B22HP FEX	N2K-B22HP-P	—	—
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 2248PQ FEX1	N2K-C2248PQ-10GE	X	X
Cisco Nexus 2224TP FEX	N2K-C2224TP-1GE	X	X
Cisco Nexus 2148T FEX	N2K-C2148T-1GE	—	—
Expansion Modules
12Q 40-Gigabit Ethernet FCoE ports	N6K-C6004-M12Q	X	X
Transceivers
QSFP Transceivers
SFP+ Optical
4x10-Gigabit module	QSFP-4SFP10G-CU1M	—	X
4x10-Gigabit module	QSFP-4SFP10G-CU3M	—	X
4x10-Gigabit module	QSFP-4SFP10G-CU5M	—	X
QSPFP 40-Gigabit module	QSFP-40G-SR4	X	X
QSFP 40-Gigabit module	QSFP-40G-CSR4	X	X
QSFP 10-Gigabit module	QSFP-4SFP10G-ACu7M	X	X
QSFP 10-Gigabit module	QSFP-4SFP10G-ACu10M	X	X
Gigabit Ethernet SFP, LX transceiver	GLC-LX-SMD	—	X
Gigabit Ethernet SFP, EX transceiver	GLC-EX-SMD	—	X
40-Gigabit CU QSFP module	QSFP-H40G-CU1M	X	X
40-Gigabit CU QSFP module	QSFP-H40G-CU3M	X	X
40-Gigabit CU QSFP module	QSFP-H40G-CU5M	X	X
40-Gigabit CU QSFP module	QSFP-H40G-ACu7M	X	X
40-Gigabit CU QSFP module	QSFP-H40G-ACu10M	X	X
SFP+ Copper
10GBASE CU SFP+ cable	SFP-H10GB-CU1.5M	—	X
10GBASE CU SFP+ cable	SFP-H10GB-CU2M	—	X
10GBASE CU SFP+ cable	SFP-H10GB-CU2.5M	—	X

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

Online Insertion and Removal Support

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

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

Hardware	Part Number	Cisco NX-OS Release Support	Cisco NX-OS Release Support
		6.0(2)N1(1)	6.0(2)N1(2)
Cisco Nexus 6000 Series
Cisco Nexus 6001 switch	N6K-6001-	—	X
Cisco Nexus 6004 switch	N6K-6004-96Q	X	X
Expansion Modules
Nexus 6004 module 12Q 40-Gigabit Ethernet/FCoE, spare	N6K-6004-M12Q	X	X

New and Changed Features

This section describes the new features introduced in Cisco NX-OS Release 6.0(2)N1(2). This section includes the following topics:

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

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

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

•FEX NIF Storm Control

•Support for DELL FEX

•Port-channel Minimum Links

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 if 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. The user will also see another syslog message when the Storm stops.

Support for DELL FEX

Added support for the Cisco Nexus B22 DELL fabric extender.

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 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:

•Cisco Nexus 6001 switch

•RAF power suppy for the Cisco Nexus 6004 switch.

•New transceivers:

–QSFP-40G-LR4

–QSFP-4SFP10G-CU1M

–QSFP-4SFP10G-CU3M

–QSFP-4SFP10G-CU5M

–SFP-H10GB-CU1.5M

–SFP-H10GB-CU2M

–SFP-H10GB-CU2.5M

–GLC-LX-SMD

–GLC-EX-SMD

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)N1(2) on the Cisco Nexus device.

This section includes the following topics:

•Upgrade and Downgrade Guidelines

•Supported Upgrade and Downgrade Paths

Upgrade and Downgrade Guidelines

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

Supported Upgrade and Downgrade Paths

Table 4 shows the upgrade and downgrade possibilities for Cisco NX-OS Release 6.0(2)N1(2).

Table 4 Cisco NX-OS Release 6.0(2)N1(2) Supported Upgrade and Downgrade Paths 

Current Cisco NX-OS Release	Upgrade to NX-OS Release 6.0(2)N1(2)	Downgrade from NX-OS Release 6.0(2)N1(2)
6.0(2)N1(1a) 6.0(2)N1(1)	Nondisruptive upgrade 1	Disruptive downgrade

1 Disruptive upgrade when operating in 10G fabric mode.

Limitations

This section describes the limitations for Cisco NX-OS Release 6.0(2)N1(2).

•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 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.

•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 6000 Series switch, and all host-facing ports are connected and each host-facing interface has a large configuration (that supports the maximum permissible ACEs per interface).

•The Cisco Nexus 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 configure Multiple Spanning Tree (MST) on a Cisco Nexus 6000 Series switch, we do not recommend that you partition the network into a large number of regions.

•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.

•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. The Cisco Nexus 6000 switch terminates in multiples of 16 bytes. If MTU is configured as 100 bytes then the actual truncated packets is 96 bytes.

•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 6000 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.

•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 6000 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.

•The limit of the table that holds the Router MAC and Virtual MAC entries for determining packet routing or switching is 500 entries. The Virtual MAC entries (MAC used for HSRP/VRRP which is also programmed in this table) in this table can be shared across multiple Layer 3 interfaces. If SVIs 1-100 all have the same group number configured, then just 1 entry needs to be programmed in this table. It is recommended that the same "group ID" is configured across all or multiple Layer 3 interfaces/SVIs. If multiple group IDs are configured on an Layer 3 interface, then it is recommended that the same set of group IDs are configured across all or multiple Layer 3 interfaces. If configured this way HSRP/VRRP can be supported on more interfaces.

•The maximum IP MTU that can be set on Layer 3 interfaces on which Layer 3 protocols are running is 9192, because of the internal header used inside the switch. The network-qos policy must be set to 9216.

Limitations on the Cisco Nexus 6000

The limitations on the Cisco Nexus 6000 switch is as follows:

•SPAN Limitations on Fabric Extender Ports

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

Layer 3 Limitations

Asymmetric Configuration

In a vPC topology, two Cisco Nexus 6000 devices 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.

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

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

Open Caveats

Table 5 lists descriptions of open caveats in Cisco NX-OS Release 6.0(2)N1(2)

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

Table 5 Cisco NX-OS Release 6.0x Open Caveats 

Record Number	Open Caveat Headline
CSCuc12211	While copying files to running-config some channel-group commands fail.
CSCuc25187	Config-sync is unable to remove VLAN QoS policy and offset configuration.
CSCuc43503	The IGMP vPC optimization knob does not work when the feature-set virtualization is configured.
CSCud43962	CDPv6 shows address of different interfaces and not the connected interfaces.
CSCud48710	Layer 2 multicast traffic can be lost up to 1 to 2 minsutes upon unshut of the fabric PO in AA topology. This happens only under the following conditions: •AA topology. •The group is downgraded to V2 of a V3 receiver. •Fex fabric port is shut on one side. •When the fabric port is unshut, Layer 2 multicast traffic loss may be seen until the next join comes in.
CSCud53059	DAI is blocking traffic for HIF ports.
CSCud72942	When all the fex's are reloaded at the same time, layer 2 multicast traffic may not recover on one of the HIF ports.
CSCue22038	Unable to power on the module after powering off the module.
CSCue33173	IPSG blocks traffic for private VLAN isolated trunk ports, even when valid DHCP snooping binding entry exists.
CSCud73169	The policer stats are not enabled if police action is added after apply to interface configuration.

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

Table 6 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 6 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.
CSCue22023	The system hap-resets with fcoe_mgr process core.
CSCue03528	The CFS locks on a Cisco Nexus 6000 device in a vPC due to the session manager not clearing.
CSCue34723	After changing the gloabal MAC aging timer value to a non default value, the value resets to the default after ISSU.
CSCue35880	Link up on FEX ports are 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 non-default 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 versions 6.1(0.174)S0, 5.2(3.30)S0 and above.
CSCue39246	In CiscoNX-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.

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 6000 Series switch.

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

ftp://ftp.cisco.com/pub/mibs/supportlists/nexus6000/Nexus6000MIBSupportList.html

Related Documentation

Documentation for the Cisco Nexus 6000 Series Switch is available at the following URL:

http://www.cisco.com/en/US/products/ps12806/tsd_products_support_series_home.html

The documentation set is divided into the following categories:

Release Notes

The release notes are available at the following URL:

http://www.cisco.com/en/US/products/ps12806/prod_release_notes_list.html

Installation and Upgrade Guides

The installation and upgrade guides are available at the following URL:

http://www.cisco.com/en/US/products/ps12806/prod_installation_guides_list.html

Command References

The command references are available at the following URL:

http://www.cisco.com/en/US/products/ps12806/prod_command_reference_list.html

Technical References

The technical references are available at the following URL:

http://www.cisco.com/en/US/products/ps12806/prod_technical_reference_list.html

Configuration Guides

The configuration guides are available at the following URL:

http://www.cisco.com/en/US/products/ps12806/products_installation_and_configuration_guides_list.html

Error and System Messages

The system message reference guide is available at the following URL:

http://www.cisco.com/en/US/products/ps12806/products_system_message_guides_list.html

Documentation Feedback

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

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, 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.

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)

©2012 Cisco Systems, Inc. All rights reserved