Cisco AP775A - Nexus Converged Network Switch 5010 Instruction Manual

Send documentation comments to nx5000-docfeedbac[email protected]
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Cisco Nexus 5000 Series and Cisco Nexus 2000
Series Release Notes, Release 4.1(3)N1(1)
Current Release: 4.1(3)N1(1) -July 31, 2009
Part Number: OL-16601-01 H0
This document describes the features, caveats, and limitations for Cisco Nexus 5000 Series switches and
the Cisco Necus 2000 Series Fabric Extenders. Use this document in combination with documents listed
in the “Related Documentation” section on page 26.
Note Release notes are sometimes updated with new information about restrictions and caveats. See the
following website for the most recent version of the Cisco Nexus 5000 Series and Cisco Nexus 2000
Series Release Notes:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/release/notes/Nexus_5000_Relea
se_Notes.html
Note Table 1 shows the online change history for this document.
Table 1 Online History Change
Part Number Revision Date Description
OL-16601-01 A0 June 03, 2008 Created release notes.
OL-16601-01 B0 June 16, 2008 Added information for Release 4.0(0)N1(1a).
OL-16601-01 C0 June 30, 2008 Added information for Cisco Fabric Manager Release
3.4(1a).
OL-16601-01 D0 July 22, 2008 Added information for Release 4.0(0)N1(1a).
OL-16601-01 E0 August 13, 2008 Added information for Release 4.0(0)N1(2).
OL-16601-01 F0 September 29,
2008
Added information for Release 4.0(0)N1(2a).

Send documentation comments to nx5000-docfeedbac[email protected]
2
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Contents
Contents
This document includes the following sections:
•Introduction, page 2
•New and Changed Features in Cisco NX-OS Release 4.1(3)N1(1), page 5
•Cisco NX-OS Release 4.1(3) N1(1) Upgrade/Downgrade Issues, page 5
•Limitations, page 7
•Caveats, page 9
•Cisco Fabric Manager, page 23
•Related Documentation, page 26
•Obtaining Documentation and Submitting a Service Request, page 26
Introduction
This section includes the following topics:
•Cisco Nexus 5000 Series Switches, page 2
•Cisco Nexus 2000 Series Fabric Extenders, page 3
Cisco Nexus 5000 Series Switches
The Cisco Nexus 5000 Series switches comprise a family of line-rate, low-latency, lossless 10-Gigabit
Ethernet, Cisco Data Center Ethernet, and Fibre Channel over Ethernet (FCoE) switches for data center
applications. The Cisco Nexus 5000 Series includes the Cisco Nexus 5020 switch and the Cisco Nexus
5010 switch.
The Cisco Nexus 5000 Series switch hardware is described in the following topics:
•Cisco Nexus 5020 Switch, page 3
•Cisco Nexus 5010 Switch, page 3
OL-16601-01 G0 December 03,
2008
Added information for Release 4.0(1a)N1(1).
OL-16601-01 H0 February 26,
2009
Added information for Release 4.0(1a)N2(1).
OL-16601-01 F0 July 26, 2009 Added information for Release 4.1(3)N1(1).
Table 1 Online History Change
Part Number Revision Date Description

Send documentation comments to nx5000-docfeedbac[email protected]
3
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Introduction
Cisco Nexus 5020 Switch
The Cisco Nexus 5020 is a 56-port switch. It is a two rack unit (2 RU), 10-Gigabit Ethernet, Cisco Data
Center Ethernet, FCoE, and Fibre Channel switch that provides 1.04 terabits per second (Tbps)
throughput with very low latency.
It has the following features:
•Forty fixed 10-Gigabit Ethernet, Cisco Data Center Ethernet, and FCoE Small Form Factor
Pluggable Plus (SFP+) ports. Sixteen of the forty fixed ports support both Gigabit Ethernet and
10-Gigabit Ethernet. The default is 10-Gigabit Ethernet.
•Two expansion module slots that can be configured to support up to 12 additional 10-Gigabit
Ethernet, Cisco Data Center Ethernet, and FCoE SFP+ ports, up to 16 Fibre Channel switch ports,
or a combination of both.
•Serial console port and an out-of-band 10/100/1000-Mbps Ethernet management port.
•1+1 redundant, hot-pluggable power supplies.
•4+1 redundant, hot-pluggable fan modules to provide highly reliable front-to-back cooling.
For additional information about the Cisco Nexus 5020 switch, see the Cisco Nexus 5000 Series
Hardware Installation Guide.
Cisco Nexus 5010 Switch
The Cisco Nexus 5010 is a 28-port switch. It is a 1 RU, 10-Gigabit Ethernet, Cisco Data Center Ethernet,
FCoE, and Fibre Channel switch that provides more than 500-Gbps throughput with very low latency. It
has the following features:
•Twenty fixed 10-Gigabit Ethernet, Cisco Data Center Ethernet, and FCoE SFP+ ports. Eight of the
twenty fixed ports support Gigabit Ethernet and 10-Gigabit Ethernet speed.
•One expansion module slot that can be configured to support up to 6 additional 10-Gigabit Ethernet,
Cisco Data Center Ethernet, and FCoE SFP+ ports, up to 8 Fibre Channel switch ports, or a
combination of 4 additional 10-Gigabit Ethernet, Cisco Data Center Ethernet, and FCoE SFP+ ports
with 4 additional Fibre Channel switch ports.
•Serial console port and an out-of-band 10/100/1000-Mbps Ethernet management port.
•1+1 redundant, hot-pluggable power supplies.
•1+1 redundant, hot-pluggable fan modules to provide highly reliable front-to-back cooling.
For additional information about the Cisco Nexus 5010 switch, see the Cisco Nexus 5000 Series
Hardware Installation Guide.
Note The Cisco Nexus 5020 switch and the N5K-M1404 and N5K-M1600 gatos expansion modules (GEMs)
use a release 4.0(0)N1(1) or later image. The Cisco 5010 switch and the N5K-M1008 GEM use a release
4.0(1a)N1(1) or later image.
Cisco Nexus 2000 Series Fabric Extenders
The Cisco Nexus 2000 Series Fabric Extender was first released in Release 4.0(1a)N2(1). It is a highly
scalable and flexible server networking solution that works with the Cisco Nexus 5000 Series switches
to provide high-density and low-cost connectivity for server aggregation.

Send documentation comments to nx5000-docfeedbac[email protected]
4
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Introduction
Scaling across a multitude of 1-Gigabit Ethernet, 10-Gigabit Ethernet, unified fabric, rack, and blade
server environments, the Fabric Extender is designed to simplify data center architecture and operations.
The Fabric Extender integrates with its parent switch, allowing zero-touch provisioning as well as
automatic configuration. This integration allows large numbers of servers and hosts to be supported
using the same feature set as the parent Nexus 5000 Series switch, including security and quality of
service (QoS) configuration parameters, with a single point of management as shown in Figure 1-1.
Spanning Tree Protocol (STP) is not required between the Fabric Extender and its parent switch, because
the Fabric Extender an its parent switch allow you to enable a large multi-path, loop-free, active-active
topology.
Since the Fabric Extender is designed to connect to servers directly, by default, all Fabric Extender host
ports are edge ports. In addition, BPDU guard and BPDU filters are also enabled on Fabric Extender
host ports by default.
Figure 1-1 Single Management Domain
This section describes the 2148T Fabric Extender. It includes the following topic:
•Cisco Nexus 2148T Fabric Extender, page 4
Cisco Nexus 2148T Fabric Extender
The first product in the Cisco Nexus 2000 Series is the Nexus 2148T Fabric Extender, a 1 RU chassis
designed for rack mounting. The chassis supports redundant hot-swappable fans and power supplies.

Send documentation comments to nx5000-docfeedbac[email protected]
5
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
New and Changed Features in Cisco NX-OS Release 4.1(3)N1(1)
The Cisco Nexus 2148T Fabric Extender forwards all traffic to a parent Cisco Nexus 5000 Series switch
over 10-Gigabit Ethernet fabric uplinks, allowing all traffic to be inspected by policies established on
the Cisco Nexus 5000 Series switch. No software is included with the Nexus 2148T. Software is
downloaded and upgraded from its parent Cisco Nexus 5000 Series switch.
The Nexus 2148T has 48 1-Gigabit Ethernet host interfaces for its downlink connection to servers or
hosts and 4 10-Gigabit Ethernet fabric interfaces with SFP+ interface adapters for its uplink connection
to the parent switch.
New and Changed Features in Cisco NX-OS Release 4.1(3)N1(1)
This release includes the following new or changed features:
•750 Watt power supply
•NxOS 4.1.3 parity features
•Virtual Port Channels (VPC)
•N2K Active-Active over VPC
•EtherChannel Enhancements
– 16-Port Etherchannel
– 16 Etherchannels
– Etherchannel load balancing commands
•N2K connectivity over Expansion modules
•ACL For N2K ports over FEX-fabric Port-Channel
•PVLAN Isolated and Promiscuous Trunk
•Support for 512 VLANs (512 minus number of VSANs configured)
•Native 802.1q VLAN tag
•ACL based QoS classification and Marking
•FCoE: Support for T11 based FIP
•CEE DCBX
•FCoE co-existence with VPC
•Support for SMI-S
•DCNM Support
For more information about the features listed, see the Cisco Nexus 5000 Series and the Cisco Nexus
2000 Series documentation listed in the“Related Documentation” section on page 26.
Cisco NX-OS Release 4.1(3) N1(1) Upgrade/Downgrade Issues
This section describes issues you may encounter when you upgrade to or downgrade from the Cisco
NXOS 4.1(3) N1(1) release on the Cisco Nexus 5000 Series switch.
This section includes the following topics:
•Upgrading from Cisco NX-OS 4.0(1a)N1-Based Releases to 4.1(3)N1-Based Releases, page 6
•Downgrading from Cisco NX-OS 4.1(3)N-Based Releases, page 6

Send documentation comments to nx5000-docfeedbac[email protected]
6
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Cisco NX-OS Release 4.1(3) N1(1) Upgrade/Downgrade Issues
Upgrading from Cisco NX-OS 4.0(1a)N1-Based Releases to 4.1(3)N1-Based
Releases
When you upgrade your Cisco Nexus 5000 Series switch from Cisco NX-OS 4.0(1a)N1-Based Releases
to 4.1(3)N1-Based Releases, the following occurs:
•QoS configuration will be automatically converted to the new syntax
•If an ACL has more than 549 ACEs then the ACL fails to get applied. This is due to a new limit on
the number of ACEs in an ACL
•The Interface fcoe mode on command is deprecated.
Alternatively, you can contact Cisco Customer Support for help with upgrading and converting your
configuration to the new format.
Downgrading from Cisco NX-OS 4.1(3)N-Based Releases
•Downgrade is only supported for the following releases:
– Cisco NX-OS 4.0(1a)N1(1) release
– Cisco NX-OS 4.0(1a)N1(1a) release
– Cisco NX-OS 4.0(1a)N2(1) release
– Cisco NX-OS 4.0(1a)N2(1a) release
•Install all will warn of all configurations that need be undone before proceeding.
Note Not all QoS configurations will be converted properly on downgrade. It is recommended that the QoS
configuration be verified and re-applied after a downgrade.
QoS Upgrade and Downgrade
During an upgrade from 4.0(1a)N1-Based Releases to 4.1(3)N1-Based Releases, the class-maps,
policy-maps, and service-policies with a particular name will be split up into multiple instances, each
with a different type and associated match conditions/actions.
During a downgrade from 4.1(3)N1-Based Release, to 4.0(1a)N1-Based Release , the following will
occur:
•Checks will occur during the install all before reboot, alerting you to delete any new CLI in this
release.
•The class-maps, policy-maps, and service-policies of different types but sharing the same name are
combined into a single instance.
– For policy-maps, if the resulting entity cannot be attached onto an interface in 4.0(1a)N1-Based
Releases, the attachment for the whole policy-map will fail

Send documentation comments to nx5000-docfeedbac[email protected]
7
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Limitations
Limitations
This section describes the limitations in Nexus 5000 Series switches and the Cisco Nexus 2000 Series
Fabric Extenders, Release 4.1(3)N1(1).
•In large scale configurations some Cisco Nexus 2000 Series Fabric Extenders may take up to 3
minutes to appear online after a reload command is issued. A configuration can be termed large
scale when the maximum permissible Cisco Nexus 2000 Series Fabric Extenders are connected to a
Cisco Nexus 5000 Series switch, all host facing ports are connected and each host facing interface
has large configuration ( supporting the maximum permissible ACEs per interface).
•The Cisco Nexus 2000 Fabric Extender does not support PVLANs over VLAN trunks used to
connect to another switch. The PVLAN trunks are only used on inter-switch links but the FEX ports
are only meant to connect to servers. Since it is not a valid configuration to have an isolated
secondary VLAN as part of a Fabric Extender port configured as a VLAN trunk, all frames on
isolated secondary VLANs are pruned from going out to a FEX.
•Egress scheduling is not supported across 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.
•Traffic going out the Ethernet SPAN destination is always tagged. The SPAN destination can be in
the access or trunk mode and frames on the SPAN source port can be tagged or untagged. Frames
are always tagged internally as they travel through the system. Information about whether the frame
was originally tagged or untagged, as it appeared in the SPAN source, is not preserved in the SPAN
destination. The spanned traffic exiting the SPAN destination port always has the VLAN tag on it.
The correct VLAN tag is applied on the frame as it goes out the SPAN destination. The only
exception is if frames ingress on a SPAN source port on an invalid VLAN. In this case, vlan 0 will
be applied on a spanned frame.
•Spanned Fibre Channel over Ethernet (FCoE) frames do not preserve original SMAC and DMAC
fields. The Ethernet header gets modified as the frame is spanned to the destination. The modified
header fields are displayed when monitored on the SPAN destination.
•The CoS value in spanned Fibre Channel over Ethernet (FCoE) frames on the Ethernet SPAN
destination port does not match with the CoS value in the SPAN FCoE source frame. The CoS value
on the captured SPAN FCoE frame should be ignored.
•The class-fcoe cannot be removed even if Fibre Channel is not enabled on a switch.

Send documentation comments to nx5000-docfeedbac[email protected]
8
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Limitations
•VACLs of more than one type on a single VLAN are unsupported. 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 gets 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 overcome this situation, use IP ACLs to apply
access control to IP traffic instead of using a MAC ACL that matches the Ethertype to Ipv4 or Ipv6.
•If a port drains traffic at a rate less than 100 Kbps, it is errdisabled in 10 seconds to avoid buffer
exhaustion. However, if the drain rate is larger than 100 Kbps, the port may not be consistently
errdisabled within 10 seconds. This could cause ingress buffers to be exhausted leading to frames
being discarded. Use the shut command to disable the slow-draining port.
•The multicast storm control functionality in the Cisco Nexus 5000 Series hardware does not
distinguish between IP, non-IP, registered, or unregistered multicast traffic. All multicast traffic is
subject to a single multicast storm control policer when configured.
•Multiple boot kickstart statements in the configuration are not supported.
•If you remove an expansion module with Fibre Channel ports, and the cable is still attached, the
following FCP_ERRFCP_PORT errors are displayed:
2008 May 14 15:55:43 switch %KERN-3-SYSTEM_MSG: FCP_ERRFCP_PORT:
gat_fcp_isr_ip_fcmac_sync_intr@424, jiffies = 0x7add9a:Unknown intr src_id 42 - kernel
2008 May 14 15:55:43 switch %KERN-3-SYSTEM_MSG: FCP_ERRFCP_PORT:
gat_fcp_isr_ip_fcmac_sync_intr@424, jiffies = 0x7add9a:Unknown intr src_id 41 - kernel
These messages are informational only, and result in no loss of functionality.
SPAN Limitations on Fabric Extender Ports
•Ports on a Fabric Extender (FEX) can be configured as a tx-source in one sesssion only.
If two ports on the same FEX are enabled to be tx-source, the ports need to be in the same session.
If you configure a FEX port as a tx-source and another port belonging to the same FEX is already
configured as a tx-source on a different SPAN session, then a error is displayed on the CLI.
In the following example, and Interface Ethernet100/1/1 on a FEX 100 is already configuredas a
tx-source on SPAN sesssion-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 aan 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, will be SPAN-ed. 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

Send documentation comments to nx5000-docfeedbac[email protected]
9
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Caveats
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 mutlicast 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. This is due to a design limitation.
•When a FEX port is configured as both SPAN rx-source and tx-source, the broadcast, non-IGMP
layer-2 multicast, and unknown unicast frames originating from that port may be seen twice on the
SPAN destination, once on the ingress and once on the egress path. On the egress path, the frames
are filtered by the FEX to prevent them from going out on the same port on which they were
received. For example, if FEX Port 100/1/1 is configured on VLAN 11, and is also configured as
SPAN rx-source and tx-source and a broadcast frame is received on that port, the SPAN destination
recognizes two copies of the frame, even though the frame is not sent back on port 100/1/1.
•A FEX port can not be configured as a SPAN destination. Only a switch port can be configured and
used as a SPAN destination.
Caveats
This section includes the following topics:
•Open Caveats, page 9
•Resolved Caveats—Cisco NX-OS Release 4.1(3)N1(1), page 17
•Resolved Caveats—Cisco NX-OS Release 4.0(1a)N2(1), page 20
•Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1), page 21
•Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2a), page 22
•Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2), page 23
•Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1a), page 25
•Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1), page 25
Open Caveats
This section lists the open caveats for this release.
•CSCsz93815
Symptom: After you downgrade from release 4.1(3)N1, the QoS configuration is not restored if the
class-map name is dfferent for type qos, network-qos,or queuing policy-maps.
Workaround: Make sure the class-names between different policy types are the same before you
begin downgrade.
•CSCsz82199
Symptom: You cannot enable std.pause on a port-channel interface connected between two Cisco
Nexus 5000 Series switches. Enable std.pause between two Cisco Nexus 5000 Series switches and
configure std.pause in the hardware.
Workaround: None

Send documentation comments to nx5000-docfeedbac[email protected]
10
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Caveats
•CSCta00231
Symptom: After a downgrade, the interface policy may silently get added to the system level
without a warning message. This may change the entire qos queuing policy.
Workaround: Remove the system policy BW/SPQ parameters, configure the queuing policy and
add the parameters again to the interfaces.
•CSCsv39939
Symptom: Incorrect values are displayed for interface capabilities for ports for Cisco Nexus 2000
Series Fabric extenders connected to a Cisco Nexus 5000 Series switch. In particular, the number
of input and output queues for the ports are displayed as zero instead of two.
Workaround: This is a display issue and does not impact functionality.
•CSCsz81365
Symptom: SPAN session should stop reflecting packets as soon as mapping is removed.
Workaround: None.
•CSCta04383
Symptom: When you install a new image from one of two vPC switches, the vPC switch gets
upgraded. Also, each of the connected Fabric Extenders update their firmware with the new version,
but continue to run the current version and stay connected to the other vPC switch. When you reload
the upgraded switch, but revert back to the older version of software on the switch, both the vPC
switches and all the Fabric Extenders run the older version of software. However, the Fabric
Extenders have the more recent version of software in the firmware. When the Fabric Extenders
reload there is loss of connectivity with the hosts.
Workaround: Re-install the older version of software from either of the two switches while the
Fabric Extenders are connected to that switch.
•CSCta13997
Symptom: When vpc peer-link is down on Cisco Nexus 5000 Series switches, ports fail to come up
on a Cisco Nexus 2000 Fabric Extender that is dual homed to the Nexus 5000 Series switches with
vPC.
Workaround: Restore the peer-link before making new connections to the Cisco Nexus 2000 Fabric
Extender.
•CSCsx35870
Symptom: The CLI times out when a large number of VLANs are created and deleted followed by
PVLAN creation and deletion. The system indicates that the Ethernet Port Manager (ethpm) has
timed out to communicate with the SPAN manager or PVLAN manager. As a result, some of the
PVLAN interfacse will be error disabled.
Workaround: Perform shut and no shut on the error disabled interfaces.
•CSCsx59489
Symptom: Call home notifications for events generated when both a switch and a Fabric Extender
are rebooting may contain a timestamp of January 1 1970 as shown in the following example:
System Notification from sample-system - environment:minor - 1970-01-01 00:00:00
GMT+0000
The most likely scenario where this would occur is after a power failure or after issuing the reload
all command. The event is generated before the Fabric Extender connects with the switch and before
the local time is updated for the Fabric Extender.
Workaround: None.