Cisco AJ732A - MDS 9134 Fabric Switch Instruction Manual

Send documentation comments to [email protected]
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
CiscoNexus5000SeriesReleaseNotes,Release
4.0(1a)N1(1a)
Current Release: 4.0(1a)N1(1a) -April 23, 2009
Part Number: OL-16601-01 G0
This document describes the features, caveats, and limitations for Nexus 5000 Series switches. 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 Nexus 5000 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).
OL-16601-01 G0 December 03,
2008 Added information for Release 4.0(1a)N1(1).
OL-16601-01 H0 April 23, 2009 Added information for Release 4.0(1a)N1(1a).

Send documentation comments to [email protected]
2
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) OL-16601-01
Contents
Contents
This document includes the following sections:
•Introduction, page 2
•New and Changed Features in Cisco NX-OS Release 4.0(1a)N1(1a), page 3
•Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues, page 4
•Changes to the FCoE Model and Related Configuration, page 8
•Limitations, page 10
•Caveats, page 12
•Cisco Fabric Manager, page 24
•Related Documentation, page 26
•Obtaining Documentation and Submitting a Service Request, page 26
Introduction
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 switch hardware is described in the following topics:
•Cisco Nexus 5020 Switch, page 2
•Cisco Nexus 5010 Switch, page 3
Cisco Nexus 5020 Switch
The Cisco Nexus 5020 is a 56-port switch. It is a two rack unit (2RU), 10-Gigabit Ethernet, Cisco Data
Center Ethernet, FCoE and Fibre Channel switch built to provide 1.04 terabit 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 GE and 10GE. The default
is 10GE.
•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.

Send documentation comments to [email protected]
3
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
OL-16601-01
New and Changed Features in Cisco NX-OS Release 4.0(1a)N1(1a)
Cisco Nexus 5010 Switch
The Cisco Nexus 5010 is a 28-port switch. It is a 1RU, 10-Gigabit Ethernet, Cisco Data Center Ethernet,
FCoE, and Fibre Channel switch providing 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 GE and 10GE 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 1/2/4-Gbps 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.
New and Changed Features in Cisco NX-OS Release
4.0(1a)N1(1a)
The new or changed features for this release are described in the following topics:
•The shutdown lan Command, page 3
•The errdisable recovery cause pause-rate-limit Command, page 4
•Kickstart Break Sequence, page 4
The shutdown lan Command
The DCBX protocol provides a capability to signal LAN Logical Link Status (LLS) to a CNA that is
connected to the Cisco Nexus 5000 switch over an Ethernet interface. This signaling can be used by the
bonding driver in the host to perform a failover to the standby link to the LAN.
The shutdown lan command provides the LAN administrator with the capability to trigger an
LLS-Down to the CNA. This operation can be performed without any impact to the SAN traffic on the
Ethernet interface. When the shutdown lan command is configured on an Ethernet interface, all VLANs
that are not enabled for FCoE are brought down on the interface. This in turn triggers the LLS-Down
signal. If non-FCoE VLANs are brought down by other means (like vlan shutdown) they trigger
LLS-Down signaling if the only VLANs active on an Ethernet interface are enabled for FCoE.
switch(config)# interface Ethernet 1/1
switch(config-if)# shutdown ?
<CR>
force Enable/disable an interface
lan Shut all LAN VLANs on interface
switch(config-if)# [no] shutdown lan

Send documentation comments to [email protected]
4
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) OL-16601-01
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues
The errdisable recovery cause pause-rate-limit Command
switch(config)# errdisable recovery cause ?
pause-rate-limit Enable timer to recover from pause rate limit error
disabled state
switch(config)# [no] errdisable recovery cause pause-rate-limit
When an Ethernet port experiences severe congestion due to a large amount of flow control (pause)
frames received from the peer for an extended duration of time (10s), the port is placed in an error
disabled state. The errdisable recovery cause pause-rate-limit command enables an automatic
recovery of the port after a pre-defined interval of recovery time (if the port was error-disabled as a result
of the pause-rate-limiting function). By default, this recovery mechanism is not enabled.
The following command allows configuration of the timeout value for automatic recovery. The default
value is 300 seconds.
switch(config)# errdisable recovery interval ?
<30-65535> Timer-interval (sec)
Kickstart Break Sequence
Press the Ctrl-] key sequence from the console port session when the switch begins the Cisco NX-OS
software boot sequence to enter the boot prompt mode.
Ctrl-]
switch(boot)#
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues
This section describes issues that you may encounter when you upgrade or downgrade the Cisco NX-OS
software release on the Cisco Nexus 5000 Series switch. It provides examples of configuration syntax
differences for some of these changes.
Upgrade and downgrade is supported between the following versions of the Cisco NX-OS software on
the Cisco Nexus 5000 Series switches:
•4.0(0)N1(2a)
•4.0(1a)N1(1)
•4.0(1a)N1(1a)
Upgrade and downgrade is not supported between the following versions of the Cisco NX-OS software
on the Cisco Nexus 5000 Series switches:
•4.0(1a)N1(1a)
•4.0(1a)N2(1)
All the documented behavior for upgrade and downgrade between 4.0(0)N1 based releases and
4.0(1a)N1(1) also applies to upgrade and downgrade between 4.0(0)N1 based releases and
4.0(1a)N1(1a).
The following upgrade and downgrade issues occur as a result of CSCsy37432, CSCsy53275,
CSCsy09062, CSCsy08516 (For details see, Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1a),
page 18 and Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1), page 19):

Send documentation comments to [email protected]
5
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
OL-16601-01
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues
•If the startup-config has an RBAC role configured with more than 35 rules, then after a downgrade
to the 4.0(0)N1(2a) release, the show running-config command causes the vshd process to core
dump. This is due to a caveat (CSCsy37432). The workaround is to remove rules from the roles
configuration in a way that a role does not have more than 35 rules before downgrading to the
4.0(0)N1(2a) release.
•If the startup-config has an RBAC role configured with more than 20 roles with 20 rules each, then
after a downgrade to the 4.0(0)N1(2a) release, show running-config will make the roles feature
work incorrectly. This is due to caveat CSCsy53275. The workaround is, before you downgrade to
the 4.0(0)N1(2a) release, remove rules from the roles configuration to limit the configuration so it
does not exceed the previously mentioned numbers.
•After an upgrade or downgrade, if the show startup security command is issued before performing
copy running-config startup-config, the security process could crash. This is due to caveat
CSCsy09062. You can avoid a core dump by issuing a copy running-config startup-config
command after an upgrade or downgrade and before issuing the show startup <feature> command.
•After an upgrade or downgrade, when the system comes up users are assigned a default role of
network-operator. This is due to caveat CSCsy08516. To avoid the problem, reload the switch after
an upgrade or a downgrade and after the system comes up. You can then perform a copy
running-config startup-config to save the correct configuration.
For more information about the features listed, refer to the documentation set listed in the“Related
Documentation” section on page 26.
This section includes the following topics:
•EtherChannel® Upgrade/Downgrade Changes, page 5
•Fibre Channel Port Shutdown, page 7
•Switched Port Analyzer (SPAN), page 7
•Example of Virtual Interface Configuration Changes, page 9
•Upgrading from Cisco NX-OS 4.0(0)-Based Releases, page 10
•Downgrading to Cisco NX-OS 4.0(0)-Based Releases, page 10
EtherChannel® Upgrade/Downgrade Changes
The following table describes the changes to the security ACLs for EtherChannel members.
4.0(0)-based
releases Configuration is allowed on member ports (but not used while the port is a member of the EtherChannel).
4.0(1a)N1(1a) No configuration is allowed on member ports. All member ports follow the
configuration on the EtherChannel.
Upgrade Member port ACL configuration, if any, is lost; EtherChannel configuration is
preserved. No impact on the functional behavior while the port is a member of the
EtherChannel.
When the member port leaves the EtherChannel, you have to recreate the ACL
configuration on the physical interface.
Downgrade No issue.

Send documentation comments to [email protected]
6
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) OL-16601-01
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues
The following table describes the changes to the interface level QoS service policy,
The following table describes the changes to the priority flow control configuration.
The following table describes the changes to the syntax of the Ethernet load-balancing commands.
4.0(0)-based
releases Interface level QoS service policy is not aware of the EtherChannel. QoS strictly follows a per-member port configuration. The only service policy supported on the
interface level is egress queue scheduling.
4.0(1a)N1(1a) No configuration is allowed on member ports. All member ports follow the
configuration on the EtherChannel.
Upgrade If any member port has a modified egress scheduling policy and the EtherChannel is
explicitly configured, then the egress scheduling configuration for the port is lost. A
EtherChannel has a default egress scheduling policy.
Downgrade This capability needs to be reconfigured after the downgrade. Otherwise, egress
queue scheduling configuration on the EtherChannel will be lost after the downgrade.
4.0(0)-based
releases Priority flow control is an interface level configuration. This CLI option is used to override results of DCBX negotiation. Priority flow control function is not aware of
the EtherChannel. It strictly follows a per-member port configuration.
4.0(1a)N1(1a) No configuration allowed on member ports. All member ports follow the
configuration on the EtherChannel.
Upgrade If a member port has modified priority flow control configuration and the
EtherChannel is explicitly configured, then port configuration is lost. The
EtherChannel has default priority flow control configuration.
Downgrade This capability needs to be reconfigured after the downgrade. Otherwise, the priority
flow control configuration on the EtherChannel will be lost.
4.0(0)-based
releases The following command is used to set the load-balancing method in a channel-group bundle:
switch(config)# port-channel load-balance ethernet source-destination-?
source-destination-ip Source & Destination IP address
source-destination-mac Source & Destination MAC address
source-destination-port Source & Destination TCP/UDP port
Note The keyword source-destination is used in this release.
4.0(1a)N1(1a) The following command is used to set the load-balancing method in a channel-group
bundle:
switch(config)# port-channel load-balance ethernet source-dest-?
source-dest-ip Source & Destination IP address
source-dest-mac Source & Destination MAC address
source-dest-port Source & Destination TCP/UDP port
Note The keyword source-dest is used in this release.
Upgrade The load-balancing configuration is lost.
Downgrade This capability needs to be reconfigured after the downgrade. Otherwise, the
load-balancing configuration on the EtherChannel will be lost.

Send documentation comments to [email protected]
7
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
OL-16601-01
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues
When an Ethernet interface joins a EtherChannel, the following interface level parameters are disabled:
bandwidth Set bandwidth informational parameter
delay Specify interface throughput delay
duplex Enter the port duplex mode
flowcontrol Configure interface flowcontrol
ip Configure IP features
ipv6 Configure IPv6 features
mac MAC configuration commands
priority-flow-control Configure interface priority-flowcontrol
service-policy Configure QoS service policy
spanning-tree Spanning Tree Subsystem
speed Enter the port speed
storm-control Configure Interface storm control
Fibre Channel Port Shutdown
The following table describes the changes to the interface shutdown command syntax.
Switched Port Analyzer (SPAN)
The following table describes the changes to SPAN sessions.
4.0(0)-based
releases The system default switchport shutdown command causes all Fibre Channel ports, virtual or physical, to default to shutdown.
4.0(1a)N1(1a) The system default switchport shutdown command now configures the
administrative state for all Ethernet ports as down. To configure the Fibre Channel
ports to shutdown state, use the system default switchport shutdown san command.
Upgrade Ethernet ports will default to shutdown instead of Fibre Channel ports.
Downgrade This capability needs to be reconfigured after the downgrade. Otherwise, the switch
will flag the system default switchport shutdown san command as invalid.
4.0(0)-based
releases The default is to keep session in an open state. To shut a session, use the following command:
switch(config)# monitor session session-number suspend
4.0(1a)N1(1a) The default is to keep session state shut. To open a session, use the following
command:
switch(config)# no monitor session session-number shut
Note The syntax of the command has also changed. The suspend keyword has been
changed to shut.
Upgrade SPAN session will be in shut state after the upgrade.
Downgrade If you do not execute a specific shut or no-shut command on the SPAN session, the
SPAN session will be in a no suspend state after the downgrade.

Send documentation comments to [email protected]
8
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) OL-16601-01
Changes to the FCoE Modeland Related Configuration
Changes to the FCoE Model and Related Configuration
In the previous Cisco NX-OS 4.0(0)-based releases, the FCoE model allowed Ethernet and FCoE to
co-exist on the interface. The virtual interfaces, virtual Ethernet and virtual Fibre Channel (VFC), did
not affect each other. For example, if the virtual Ethernet interface was errdisabled, the VFC interface
could still be up.
With Cisco NX-OS Release 4.0(1a)N1(1), the CLI implementation was changed to provide forward
compatibility with the forthcoming T11 FCoE Initialization Protocol (FIP). In this new FCoE model, the
following is changed:
•FCoE traffic is passed over Ethernet; the Ethernet STP controls port status.
•FCoE traffic for a VSAN is transported over a single dedicated FCoE-enabled VLAN.
Although the CLI implementation requires a VLAN-to-VSAN mapping, the FCoE frames are
expected to be untagged or priority-tagged. The FCoE VLAN is not expected to be carried in the
FCoE frames. This will change in a future release once FIP-based FCoE is supported.
The changes to the virtual interfaces are described in the following topics:
•Virtual Interface Groups, page 8
•Virtual Ethernet Interfaces, page 8
•Virtual Fibre Channel Interfaces, page 8
•VSAN-to-VLAN Mapping, page 9
Virtual Interface Groups
In previous Cisco NX-OS 4.0(0)-based releases, a virtual interface group allowed you to bind virtual
interfaces to a physical Ethernet interface, as shown in the following example:
switch# configure terminal
switch(config)# interface vig 1
switch(config-if)# bind interface ethernet 1/1
Virtual interface groups have been deprecated in release 4.0(1a)N1(1a).
Virtual Ethernet Interfaces
Cisco NX-OS Release 4.0(1a)N1(1a) does not support virtual Ethernet interfaces. All Ethernet features
previously configured at the virtual Ethernet interface now need to be configured at the bound Ethernet
interface.
The following configuration statements must be explicitly configured on the Ethernet interface to keep
behavior the same as virtual Ethernet interface:
spanning-tree bpduguard enable
spanning-tree port type edge trunk
All other features (for example, ACLs, SPAN etc.) that were previously configured at the virtual Ethernet
interface would need to be applied to the bound Ethernet interface.
Virtual Fibre Channel Interfaces
In previous Cisco NX-OS 4.0(0)-based releases, a virtual Fibre Channel interface was attached to a
virtual interface group, which then bound it to the physical Ethernet interface.

Send documentation comments to [email protected]
9
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
OL-16601-01
Changes to the FCoE Model and Related Configuration
Each virtual Fibre Channel interface is bound directly to an FCoE-enabled physical Ethernet interface
in Release 4.0(1a)N1(1a). This change simplifies the interface vfc command as shown in the following
example:
switch# configure terminal
switch(config)# interface vfc 1
switch(config-if)# bind interface ethernet 1/1
The Ethernet interface that you bind the virtual Fibre Channel interface to mustbe configured as follows:
•It must be a trunk port (use the switchport mode trunk command).
•The FCoE VLAN that corresponds to virtual Fibre Channel’s VSAN must be in the allowed VLAN
list.
•FCoE VLAN must not be configured as the native VLAN of the trunk port.
•The Ethernet interface must be configured as PortFast (use the spanning-tree port type edge trunk
command).
VSAN-to-VLAN Mapping
In previous Cisco NX-OS 4.0(0)-based releases, FCoE had no dependence on the VLANs defined on the
switch.
In Release 4.0(1a)N1(1a), each virtual Fibre Channel interface is associated with only one VSAN. Any
VSAN with associated virtual Fibre Channel interfaces must be mapped to a dedicated FCOE-enabled
VLAN as shown in the following example:
switch# configure terminal
switch(config)# vlan 200
switch(config-vlan)# fcoe vsan 2
switch(config-vlan)# exit
switch(config)# interface ethernet 1/1
switch(config-if)# switchport mode trunk
switch(config-if)# switchport trunk native vlan 1
switch(config-if)# switchport trunk allowed vlan 1,200
switch(config-if)# exit
switch(config)# interface vfc 1
switch(config-if)# bind interface ethernet 1/1
switch(config-if)# exit
switch(config)# vsan database
switch(config-vsan)# vsan 2 interface vfc 1
Note The FCoE VLAN must be exclusively reserved for FCoE traffic; it must not be used for non-FCoE
Ethernet forwarding.
Example of Virtual Interface Configuration Changes
Cisco NX-OS 4.0(0)-based Release Configuration
interface vig 1
bind interface Ethernet 1/1
interface vethernet 1/1
switchport access vlan 2

Send documentation comments to [email protected]
10
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) OL-16601-01
Limitations
interface vfc 1/1
no shutdown
vsan database
vsan 1 interface vfc 1/1
Release 4.0(1a)N1(1a) Converted Configuration
vlan 101
fcoe vsan 1
interface Ethernet 1/1
switchport mode trunk
switchport trunk native vlan 2
switchport trunk allowed vlan 2,101
spanning-tree bpduguard enable
spanning-tree port type edge trunk
interface vfc 1
no shutdown
vsan database
vsan 1 interface vfc 1
Upgrading from Cisco NX-OS 4.0(0)-Based Releases
When you upgrade your Cisco Nexus 5000 Series switch from Cisco NX-OS 4.0(0)-based releases, all
virtual Fibre Channel and virtual Ethernet interface configuration will be lost because the applicable CLI
is incompatible with the previous releases. We recommend that you backup your startup-config file prior
to performing the upgrade. If your switch has an FCoE configuration you will need to reconfigure FCoE
using the new FCoE CLI. Alternatively, you can contact Cisco Customer Support for help with
upgrading and converting your configuration to the new format.
Downgrading to Cisco NX-OS 4.0(0)-Based Releases
Your FCoE configuration will be lost on downgrade. We recommend that you backup your original
configuration prior to upgrading to Cisco NX-OS Release 4.0(1a)N1(1a). The backed up startup-config
can be used to restore your original configuration after a downgrade.
Limitations
This section describes the limitations in Nexus 5000 Series switches, Release 4.0(1a)N1(1a).
•The untagged cos command is not supported in this release.
•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.