hit counter script
Cisco Nexus 5000 Series Configuration Manual
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Switch
  5. Nexus 5000 Series
  6. Configuration manual

Cisco Nexus 5000 Series Configuration Manual

Nx-os layer 2 switching configuration guide, release 5.0(3)n1(1)
Hide thumbs Also See for Nexus 5000 Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Configuration Manual
Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration
Guide, Release 5.0(3)N1(1)

Advertisement

Table of Contents
loading

Related Manuals for Cisco Nexus 5000 Series

Summary of Contents for Cisco Nexus 5000 Series

  • Page 1 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 2 HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. http://cisco.com/ Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at go/trademarks .

  • Page 3: Table Of Contents

    C H A P T E R 3 Information About Ethernet Interfaces About the Interface Command Information About Unified Ports About the Unidirectional Link Detection Parameter Default UDLD Configuration UDLD Aggressive and Nonaggressive Modes Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 4 Configuring the Description Parameter Disabling and Restarting Ethernet Interfaces Displaying Interface Information Default Physical Ethernet Settings Configuring VLANs C H A P T E R 4 Information About VLANs Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 5 Configuring a Promiscuous Trunk Port Configuring an Isolated Trunk Port Configuring the Allowed VLANs for PVLAN Trunking Ports Configuring Native 802.1Q VLANs on Private VLANs Verifying Private VLAN Configuration Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 6 LACP-Enabled and Static EtherChannels Differences Configuring Port Channels Creating an EtherChannel Adding a Port to an EtherChannel Configuring Load Balancing Using EtherChannels Configuring Hardware Hashing for Multicast Traffic Enabling LACP Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 7 Auto-Recovery vPC Peer Links vPC Peer Link Overview vPC Number vPC Interactions with Other Features vPC and LACP vPC Peer Links and STP CFSoE vPC Guidelines and Limitations Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 8 Default Settings Configuring Rapid PVST+ C H A P T E R 9 Information About Rapid PVST+ Understanding STP STP Overview Understanding How a Topology is Created Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1) viii...
  • Page 9 Rapid PVST+ Interoperation with 802.1s MST Configuring Rapid PVST+ Enabling Rapid PVST+ Enabling Rapid PVST+ per VLAN Configuring the Root Bridge ID Configuring a Secondary Root Bridge Configuring the Rapid PVST+ Port Priority Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 10 Specifying the MST Configuration Revision Number Specifying the Configuration on an MST Region Mapping and Unmapping VLANs to MST Instances Mapping Secondary VLANs to Same MSTI as Primary VLANs for Private VLANs Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 11 Configuring Spanning Tree Edge Ports on Specified Interfaces Configuring Spanning Tree Network Ports on Specified Interfaces Enabling BPDU Guard Globally Enabling BPDU Guard on Specified Interfaces Enabling BPDU Filtering Globally Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 12 Configuring Traffic Storm Control Verifying Traffic Storm Control Configuration Traffic Storm Control Example Configuration Default Traffic Storm Settings Configuring the Fabric Extender C H A P T E R 1 6 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 13 Disassociating a Fabric Extender From an Interface Configuring Fabric Extender Global Features Enabling the Fabric Extender Locator LED Redistributing the Links Changing the Number of Links Maintaining the Pinning Order Redistributing Host Interfaces Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1) xiii...
  • Page 14 Contents Verifying the Fabric Extender Configuration Verifying the Chassis Management Information Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 15: P R E F A C E Preface

    Preface This preface describes the audience, organization, and conventions of the Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide. It also provides information on how to obtain related documentation. • Audience, page xv • Document Organization, page xv •...

  • Page 16: Document Conventions

    Related Documentation for Nexus 5000 Series NX-OS Software Cisco NX-OS documentation is available at the following URL: http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.htmll The documentation set for the Cisco Nexus 5000 Series NX-OS software includes the following documents: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 17 Configuration Guides • Cisco Nexus 5000 Series NX-OS Configuration Limits for Cisco NX-OS Release 5.0(2)N1(1) • Cisco Nexus 5000 Series NX-OS Configuration Limits for Cisco NX-OS Release 4.2(1)N1(1) and Release 4.2(1)N2(1) • Cisco Nexus 5000 Series NX-OS Multicast Configuration Guide •...

  • Page 18: Obtaining Documentation And Submitting A Service Request

    Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html...

  • Page 19: New And Changed Information

    Series NX-OS Layer 2 Switching Configuration Guide. The latest version of this document is available at the following Cisco website: http://www.cisco.com/en/US/products/ps9670/products_installation_and_configuration_guides_list.html To check for additional information about Cisco NX-OS, see the Cisco Nexus 5000 Series NX-OS Release Notes available at the following Cisco website: http://www.cisco.com/en/US/products/ps9670/prod_release_notes_list.html This table summarizes the new and changed features documented in the Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N2(1), and tells you where they are documented.
  • Page 20 This table summarizes the new and changed features documented in the Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1), and tells you where they are documented. Table 2: New and Changed Layer 2 Switching Features for Cisco NX-OS Release 5.0(3)N1(1)
  • Page 21 Extenders connections. This table summarizes the new and changed features documented in the Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(2)N2(1), and tells you where they are documented. Table 3: New and Changed Layer 2 Switching Features for Cisco NX-OS Release 5.0(2)N2(1)
  • Page 22 Extenders Extenders. This table summarizes the new and changed features documented in the Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(2)N1(1), and tells you where they are documented. Table 4: New and Changed Layer 2 Switching Features for Cisco NX-OS Release 5.0(2)N1(1)
  • Page 23 Extenders Extenders. This table summarizes the new and changed features documented in the Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 4.2(1)N1(1), and tells you where they are documented. Table 6: New and Changed Layer 2 Switching Features for Cisco NX-OS Release 4.2(1)N1(1)

  • Page 24: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Part 2: LAN Switching of the Cisco Nexus 5000 Series CLI Configuration Guide. For a complete list of Nexus 5000 Series document titles, see the list of Related Documentation in the "Preface." Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 25: Overview

    C H A P T E R Overview Cisco Nexus 5000 Series switches support the Layer 2 features that are described in this guide. • Layer 2 Ethernet Switching Overview, page 7 • VLANs, page 7 • Private VLANs, page 8 •...

  • Page 26: Private Vlans

    Note Inter-Switch Link (ISL) trunking is not supported on the NX-OS software for the Cisco Nexus 5000 Series. Private VLANs Private VLANs provide traffic separation and security at the Layer 2 level.

  • Page 27: Rapid Pvst

    Overview Rapid PVST+ Cisco NX-OS for the Cisco Nexus 5000 Series uses the extended system ID and MAC address reduction; Note you cannot disable these features. In addition, Cisco has created some proprietary features to enhance the spanning tree activities.

  • Page 28: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Overview STP Extensions Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 29: Configuring Ethernet Interfaces

    C H A P T E R Configuring Ethernet Interfaces This section describes the configuration of the Ethernet interfaces on a Cisco Nexus 5000 Series switch. It contains the following sections: • Information About Ethernet Interfaces, page 11 • Configuring Ethernet Interfaces, page 17 •...

  • Page 30: Information About Unified Ports

    Beginning in Cisco NX-OS Release 5.0(3)N1(1b), Cisco introduces unified port technology. Cisco Nexus unified ports allow you to configure a physical port on a Cisco Nexus 5500 Platform switch as a 1/10-Gigabit Ethernet, Fibre Channel over Ethernet (FCoE), or 1-, 2-, 4-, 8-Gigabit native Fibre Channel port.

  • Page 31: Default Udld Configuration

    Layer 1. A Cisco Nexus 5000 Series switch periodically transmits UDLD frames to neighbor devices on LAN ports with UDLD enabled. If the frames are echoed back within a specific time frame and they lack a specific acknowledgment (echo), the link is flagged as unidirectional and the LAN port is shut down.

  • Page 32: Udld Aggressive And Nonaggressive Modes

    About Interface Speed A Cisco Nexus 5000 Series switch has a number of fixed 10-Gigabit ports, each equipped with SFP+ interface adapters. The Cisco Nexus 5010 switch has 20 fixed ports, the first 8 of which are switchable 1-Gigabit and 10-Gigabit ports.

  • Page 33: Default Cdp Configuration

    Beginning with Cisco NX-OS Release 5.0(2)N1(1), you can create a port profile that contains many interface commands and apply that port profile to a range of interfaces on the Cisco Nexus 5000 Series switch. Port profiles can be applied to the following interface types: •...

  • Page 34: Guidelines And Limitations

    However, the port profile retains that command in the port profile. • The port profile’s commands take precedence over the default commands on the interface, unless the default command explicitly overrides the port profile command. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 35: About The Debounce Timer Parameters

    About MTU Configuration The Cisco Nexus 5000 Series switch is a Layer 2 device. This means it does not fragment frames. As a result, the switch cannot have two ports in the same Layer 2 domain with different maximum transmission units (MTUs).

  • Page 36: Configuring A Layer 3 Interface On A Cisco Nexus 5500 Platform Switch

    Configuring Unified Ports You can configure a unified port on a Cisco Nexus 5548UP switch, a Cisco Nexus 5596UP switch, or a Cisco Nexus 5548P switch with an installed Cisco N55-M16UP expansion module. Unified ports allow you to configure ports as Ethernet, native Fibre Channel, or Fibre Channel over Ethernet (FCoE) ports.

  • Page 37: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    ERROR: FC range should end on last port of the module On a Cisco Nexus 5548UP switch, the 32 ports of the main slot (slot1) are unified ports. The Ethernet ports start from port 1/1 to port 1/32. The Fibre Channel ports start from port 1/32 backwards to port 1/1.

  • Page 38: Configuring The Udld Mode

    Configuring Ethernet Interfaces Configuring the UDLD Mode This example shows how to configure a unified port on a Cisco Nexus 5548UP switch or Cisco Nexus 5596UP switch: switch# configure terminal switch(config)# slot 1 switch(config-slot)# port 32 type fc switch(config-slot)# copy running-config startup-config...

  • Page 39: Configuring Interface Speed

    Configuring Interface Speed The first 8 ports of a Cisco Nexus 5010 switch and the first 16 ports of a Cisco Nexus 5020 switch are switchable 1-Gigabit and 10-Gigabit ports. The default interface speed is 10-Gigabit. To configure these ports for 1-Gigabit Ethernet, insert a 1-Gigabit Ethernet SFP transceiver into the applicable port and then set its speed with the speed command.

  • Page 40: Configuring The Cdp Characteristics

    10 Gigabits. Configuring the CDP Characteristics You can configure the frequency of Cisco Discovery Protocol (CDP) updates, the amount of time to hold the information before discarding it, and whether or not to send Version-2 advertisements. To configure CDP characteristics for an interface, perform this task: SUMMARY STEPS 1.

  • Page 41: Enabling Or Disabling Cdp

    To enable or disable CDP for an interface, perform this task: SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# interface type slot/port 3. switch(config-if)# cdp enable 4. switch(config-if)# no cdp enable Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 42: Enabling The Error-Disabled Detection

    4. no shutdown 5. show interface status err-disabled 6. copy running-config startup-config DETAILED STEPS Command or Action Purpose Step 1 config t Enters configuration mode. Example: switch# config t switch(config)# Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 43: Enabling The Error-Disabled Recovery

    SUMMARY STEPS 1. config t 2. errdisable recovery cause {all | udld | bpduguard | link-flap | failed-port-state | pause-rate-limit} 3. show interface status err-disabled 4. copy running-config startup-config Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 44: Configuring The Error-Disabled Recovery Interval

    You can use this procedure to configure the err-disabled recovery timer value. The range is from 30 to 65535 seconds. The default is 300 seconds. SUMMARY STEPS 1. config t 2. errdisable recovery interval interval 3. show interface status err-disabled 4. copy running-config startup-config Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 45: Configuring Port Profiles

    This section includes the following topics: Creating a Port Profile You can create a port profile on the switch. Each port profile must have a unique name across interface types and the network. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 46: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    This example shows how to add the interface commands to a port profile named ppEth configured for Ethernet interfaces: switch# configure terminal switch(config)# port-profile ppEth switch(config-port-prof)# switchport mode trunk switch(config-port-prof)# switchport trunk allowed vlan 300-400 switch(config-port-prof)# flowcontrol receive on Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 47: Modifying A Port Profile

    Displays the port profile configuration. Example: switch(config)# show port-profile name Step 5 (Optional) copy running-config startup-config Copies the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 48: Enabling A Specific Port Profile

    Step 3 state enabled name Enables the port profile. Example: switch(config-port-prof)# state enabled switch(config-port-prof)# Step 4 Exits the port profile configuration mode. exit Example: switch(config-port-prof)# exit switch(config)# Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 49: Inheriting A Port Profile

    Enters configuration mode. Example: switch# configure terminal switch(config)# Step 2 port-profile name Enters port profile configuration mode for the specified port profile. Example: switch(config)# port-profile test switch(config-port-prof)# Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 50: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    This example shows how to remove an inherited port profile named ppEth from an existing port profile named test: switch# configure terminal switch(config)# port-profile test Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 51: Removing An Inherited Port Profile

    Step 4 exit Exits the port profile configuration mode. Example: switch(config-port-prof)# exit switch(config)# Step 5 (Optional) show port-profile Displays the port profile configuration. Example: switch(config)# show port-profile name Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 52: Assigning A Port Profile To A Range Of Interfaces

    Example: switch(config)# interface ethernet 7/3-5, 10/2, 11/20-25 switch(config-if)# Step 3 inherit port-profile name Assigns the specified port profile to the selected interfaces. Example: switch(config-if)# inherit port-profile adam switch(config-if)# Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 53: Removing A Port Profile From A Range Of Interfaces

    4. exit 5. (Optional) show port-profile 6. (Optional) copy running-config startup-config DETAILED STEPS Command or Action Purpose Step 1 configure terminal Enters configuration mode. Example: switch# configure terminal switch(config)# Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 54: Configuration Examples For Port Profiles

    !Time: Thu Aug 26 07:01:32 2010 version 5.0(2)N1(1) interface Ethernet1/14 switch(config)# port-profile type ethernet alpha switch(config-port-prof)# switchport mode trunk switch(config-port-prof)# switchport trunk allowed vlan 10-15 switch(config-port-prof)# switch(config-port-prof)# show running-config port-profile alpha Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 55: Configuring The Debounce Timer

    1. switch# configure terminal 2. switch(config)# interface type slot/port 3. switch(config-if)# link debounce time milliseconds DETAILED STEPS Command or Action Purpose Step 1 switch# configure terminal Enters configuration mode. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 56: Configuring The Description Parameter

    Enters configuration mode. Step 2 switch(config)# interface type slot/port Enters interface configuration mode for the specified interface. Step 3 switch(config-if)# description test Specifies the description for the interface. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 57: Disabling And Restarting Ethernet Interfaces

    The following example shows how to restart an Ethernet interface: switch# configure terminal switch(config)# interface ethernet 1/4 switch(config-if)# no shutdown Displaying Interface Information To view configuration information about the defined interfaces, perform one of these tasks: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 58: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    0 underrun 0 if down drop 0 output error 0 collision 0 deferred 0 late collision 0 lost carrier 0 no carrier 0 babble 0 Rx pause 8031547972 Tx pause 0 reset Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 59: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    The following example shows how to display the link debounce status (some of the output has been removed for brevity): switch# show interface debounce -------------------------------------------------------------------------------- Port Debounce time Value(ms) -------------------------------------------------------------------------------- Eth1/1 enable Eth1/2 enable Eth1/3 enable Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 60: Default Physical Ethernet Settings

    N5K-C5020P-BA Eth1/5 Note From Cisco NX-OS Release 4.0(1a)N1(1), the default value of the device ID field for CDP advertisement has been changed from the chassis serial number to the hostname and serial number, as in the example above. Default Physical Ethernet Settings...

  • Page 61: Configuring Vlans

    C H A P T E R Configuring VLANs This chapter describes how to configure VLANs on the Cisco Nexus 5000 Series switch. It contains the following sections: • Information About VLANs, page 43 • Configuring a VLAN, page 47...

  • Page 62: Understanding Vlan Ranges

    VLANs are not passing packets. By default, the VLANs are in the active state and pass traffic. The VLAN Trunking Protocol (VTP) mode is OFF. VTP BPDUs are dropped on all interfaces of a Cisco Note Nexus 5000 Series switch.

  • Page 63: Creating, Deleting, And Modifying Vlans

    VLANs 3968 to 4047 and 4094 are reserved for internal use; these VLANs cannot be changed or used. Cisco NX-OS allocates a group of 80 VLAN numbers for those features, such as multicast and diagnostics, that need to use internal VLANs for their operation. By default, the system allocates VLANs numbered 3968 to 4047 for internal use.

  • Page 64: About The Vlan Trunking Protocol

    Each switch can be in only one VTP domain. Layer 2 trunk interfaces, Layer 2 port channels, and virtual port channels (vPCs) support VTP functionality. Cisco NX-OS Release 5.0(2)N1(1) introduces the support for VTPv1 and VTP2. Beginning in Cisco NX-OS Release 5.0(2)N2(1), you can configure VTP in client or server mode.

  • Page 65: Configuring A Vlan

    Configuring a VLAN • If you enable VTP, you must configure either version 1 or version 2. On the Cisco Nexus 5010 and Nexus 5020 switch, 512 VLANs are supported. If these switches are in a distribution network with other switches, the limit remains the same.

  • Page 66: Entering The Vlan Submode And Configuring The Vlan

    3. switch(config-vlan)# name vlan-name 4. switch(config-vlan)# state {active | suspend} 5. (Optional) switch(config-vlan)# no shutdown DETAILED STEPS Command or Action Purpose Step 1 switch# configure terminal Enters configuration mode. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 67: Adding Ports To A Vlan

    {ethernet slot/port | Specifies the interface to configure, and enters the interface port-channel number} configuration mode. The interface can be a physical Ethernet port or an EtherChannel. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 68: Configuring Vtp

    5 Configuring VTP Beginning with Cisco NX-OS Release 5.0(2)N2(1), you can configure VTP in the client or server mode on Cisco Nexus 5000 Series switches. Before Cisco NX-OS Release 5.0(2)N2(1), VTP worked only in transparent mode.

  • Page 69: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Displays information about VTP advertisement statistics on the device. Example: switch# show vtp counters Step 11 (Optional) show vtp interface Displays the list of VTP enabled interfaces. Example: switch# show vtp interface Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 70: Verifying Vlan Configuration

    [vlan_id | Displays VLAN information. vlan_range] switch# show vlan [brief | id [vlan_id | vlan_range] Displays selected configuration information for the | name name | summary] defined VLAN(s). Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 71: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    The following example shows the VLAN settings summary: switch# show vlan summary Number of existing VLANs Number of existing user VLANs Number of existing extended VLANs : 0 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 72: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Configuring VLANs Verifying VLAN Configuration Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 73: Configuring Private Vlans

    C H A P T E R Configuring Private VLANs This chapter describes how to configure private VLANs on the Cisco Nexus 5000 Series switch. It contains the following sections: • Information About Private VLANs, page 55 • Guidelines and Limitations for Private VLANs, page 60 •...

  • Page 74: Primary And Secondary Vlans In Private Vlans

    VLANs or in any isolated VLANs at the Layer 2 level. Private VLAN Ports The three types of private VLAN ports are as follows: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 75: Primary, Isolated, And Community Private Vlans

    VLANs in a private VLAN domain. The ports within one community can communicate, but these ports cannot communicate with ports in any other community or isolated VLAN in the private VLAN. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 76: Associating Primary And Secondary Vlans

    To allow host ports in secondary VLANs to communicate outside the private VLAN, you associate secondary VLANs to the primary VLAN. If the association is not operational, the host ports (community and isolated ports) in the secondary VLAN are brought down. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 77: Private Vlan Promiscuous Trunks

    VLAN tag. Isolated trunk ports are intended to be connected to host servers. To support isolated private VLAN ports on a Cisco Nexus 2000 Series Fabric Extender, the Cisco Nexus 5000 Series switch must prevent communication between the isolated ports on the Fabric Extender; all forwarding occurs through the Cisco Nexus 5000 Series switch.

  • Page 78: Broadcast Traffic In Private Vlans

    • Enter the private-vlan synchronize command from within the Multiple Spanning Tree (MST) region definition to map the secondary VLANs to the same MST instance as the primary VLAN. • Beginning with Cisco NX-OS Release 5.0(2)N2(1), the number of mappings on a private-vlan trunk port is limited to 16.

  • Page 79: Configuring A Vlan As A Private Vlan

    1. switch# configure terminal 2. switch(config)# vlan {vlan-id | vlan-range} 3. switch(config-vlan)# private-vlan {community | isolated | primary} 4. (Optional) switch(config-vlan)# no private-vlan {community | isolated | primary} Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 80: Associating Secondary Vlans With A Primary Private Vlan

    • Use the remove keyword with a secondary-vlan-list to clear the association between secondary VLANs and a primary VLAN. • You change the association between a secondary and primary VLAN by removing the existing association and then adding the desired association. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 81: Configuring An Interface As A Private Vlan Host Port

    VLANs. Configuring a private VLAN host port involves two steps. First, you define the port as a private VLAN host port and then you configure a host association between the primary and secondary VLANs. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 82: Configuring An Interface As A Private Vlan Promiscuous Port

    In a private VLAN domain, promiscuous ports are part of the primary VLAN. Configuring a promiscuous port involves two steps. First, you define the port as a promiscuous port and then you configure the mapping between a secondary VLAN and the primary VLAN. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 83: Configuring A Promiscuous Trunk Port

    In a private VLAN domain, promiscuous trunks are part of the primary VLAN. Promiscuous trunk ports can carry multiple primary VLANs. Multiple secondary VLANs under a given primary VLAN can be mapped to a promiscuous trunk port. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 84: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    1/1 switch(config-if)# switchport mode private-vlan trunk promiscuous switch(config-if)# switchport private-vlan mapping trunk 5 100 switch(config-if)# switchport private-vlan mapping trunk 5 200 switch(config-if)# switchport private-vlan mapping trunk 6 300 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 85: Configuring An Isolated Trunk Port

    (Optional) association trunk [primary-vlan-id] Removes the private VLAN association from the port. If the primary-vlan-id is not supplied, all private VLAN associations are removed from the port. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 86: Configuring The Allowed Vlans For Pvlan Trunking Ports

    This example shows how to add VLANs to the list of allowed VLANs on an Ethernet private VLAN trunk port: switch# configure terminal switch(config)# interface ethernet 1/3 switch(config-if)# switchport private-vlan trunk allowed vlan 15-20 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 87: Configuring Native 802.1Q Vlans On Private Vlans

    Typically, you configure 802.1Q trunks with a native VLAN ID, which strips tagging from all packets on that VLAN. This configuration allows untagged traffic and control traffic to transit the Cisco Nexus 5000 Series switch. Secondary VLANs cannot be configured with a native VLAN ID on promiscuous trunk ports. Primary VLANs cannot be configured with a native VLAN ID on isolated trunk ports.

  • Page 88: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    The following example shows how to display enabled features (some of the output has been removed for brevity): switch# show feature Feature Name Instance State -------------------- -------- -------- fcsp enabled interface-vlan enabled private-vlan enabled udld disabled Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 89: Chapter 6 Configuring Access And Trunk Interfaces

    VLANs over a single link and allow you to extend VLANs across the network. Note Cisco NX-OS supports only IEEE 802.1Q-type VLAN trunk encapsulation. This chapter describes the configuration of access or trunk ports on Cisco Nexus 5000 Series switches. It includes the following sections: •...

  • Page 90: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    An Ethernet interface can function as either an access port or a trunk port; it cannot function as both port Note types simultaneously. Related Topics Understanding IEEE 802.1Q Encapsulation, on page 73 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 91: Understanding Ieee 802.1Q Encapsulation

    If an access port receives a packet with an 802.1Q tag in the header other than the access VLAN value, that port drops the packet without learning its MAC source address. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 92: Understanding The Native Vlan Id For Trunk Ports

    VLAN. It is also possible for traffic to become part of the native VLAN by sending untagged packets into an 802.1Q trunk port. To address the above issues, the vlan dot1q tag native command performs the following functions: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 93: Configuring Access And Trunk Interfaces

    VLAN ID. This feature is supported on all the directly connected Ethernet and EtherChannel interfaces of the Cisco Nexus 5000 Series switch. It is also supported on all the host interface ports of any attached Cisco Nexus 2000 Series Fabric Extender.

  • Page 94: Configuring Access Host Ports

    Sets the interface to spanning-tree port type edge, turns on bpdu filtering and bpdu guard. Apply this command only to switchports which connect to Note hosts. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 95: Configuring Trunk Ports

    This example shows how to set an interface as an Ethernet trunk port: switch# configure terminal switch(config)# interface ethernet 1/3 switch(config-if)# switchport mode trunk Related Topics Understanding IEEE 802.1Q Encapsulation, on page 73 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 96: Configuring The Native Vlan For 802.1Q Trunking Ports

    1. switch# configure terminal 2. switch(config)# interface {type slot/port | port-channel number} 3. switch(config-if)# switchport trunk allowed vlan {vlan-list all | none [add |except | none | remove {vlan-list}]} Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 97: Configuring Native 802.1Q Vlans

    Typically, you configure 802.1Q trunks with a native VLAN ID, which strips tagging from all packets on that VLAN. This configuration allows all untagged traffic and control traffic to transit the Cisco Nexus 5000 Series switch. Packets that enter the switch with 802.1Q tags that match the native VLAN ID value are similarly stripped of tagging.

  • Page 98: Verifying Interface Configuration

    Displays the interface configuration switch# show interface switchport Displays information for all Ethernet interfaces, including access and trunk interfaces. switch# show interface brief Displays interface configuration information. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 99: Configuring Etherchannels

    C H A P T E R Configuring EtherChannels This chapter describes how to configure EtherChannels and to apply and configure the Link Aggregation Control Protocol (LACP) for more efficient use of EtherChannels in Cisco NX-OS. It contains the following sections: •...

  • Page 100: Compatibility Requirements

    The EtherChannel is operationally down when all member ports are operationally down. Compatibility Requirements When you add an interface to a channel group, Cisco NX-OS checks certain interface attributes to ensure that the interface is compatible with the channel group. Cisco NX-OS also checks a number of operational attributes for an interface before allowing that interface to participate in the port-channel aggregation.

  • Page 101: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    • LACP port priority • Debounce Beginning with Cisco NX-OS Release 5.0(2)N2(1), after you enable forcing a port to be added to a channel group by entering the channel-group force command, the following two conditions occur: • When an interface joins a port channel the following parameters are removed and they are operationally replaced with the values on the port channel;...

  • Page 102: Load Balancing Using Etherchannels

    Load Balancing Using EtherChannels Cisco NX-OS load balances traffic across all operational interfaces in an EtherChannel by reducing part of the binary pattern formed from the addresses in the frame to a numerical value that selects one of the links in the channel.

  • Page 103: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Nexus 5000 Series. The following table shows the criteria used for each configuration: Table 12: EtherChannel Load-Balancing Criteria for the Cisco Nexus 2232 and Cisco Nexus 2248 Fabric Extenders Configuration Layer 2 Criteria...

  • Page 104: Understanding Lacp

    EtherChannel; using source addresses or IP addresses might result in better load balancing. Understanding LACP LACP Overview Note You must enable the LACP feature before you can configure and use LACP functions. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 105: Lacp Id Parameters

    Figure 7: Individual Links Combined into an EtherChannel With LACP, just like with static port-channels, you can bundle up to 16 interfaces in a channel group. When you delete the EtherChannel, Cisco NX-OS automatically deletes the associated channel group. All Note member interfaces revert to their previous configuration.

  • Page 106: Channel Modes

    EtherChannel, based on criteria such as the port speed and the trunking state. The passive mode is useful when you do not know whether the remote system, or partner, supports LACP. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 107: Lacp Marker Responders

    Maximum number of links in channel Configuring Port Channels Creating an EtherChannel You can create an EtherChannel before creating a channel group. Cisco NX-OS automatically creates the associated channel group. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 108: Adding A Port To An Etherchannel

    Adding a Port to an EtherChannel You can add a port to a new channel group or to a channel group that already contains ports. Cisco NX-OS creates the EtherChannel associated with this channel group if the EtherChannel does not already exist.

  • Page 109: Configuring Load Balancing Using Etherchannels

    2. switch(config)# port-channel load-balance ethernet {[destination-ip | destination-mac | destination-port | source-dest-ip | source-dest-mac | source-dest-port | source-ip | source-mac | source-port] crc-poly} 3. (Optional) switch(config)# no port-channel load-balance ethernet 4. (Optional) switch# show port-channel load-balance Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 110: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    (config)# port-channel load-balance ethernet source-ip Before Release 4.0(1a)N1 of Cisco NX-OS, the source-dest-ip, source-dest-mac, and source-dest-port Note keywords were source-destination-ip, source-destination-mac, and source-destination-port, respectively. Related Topics Enabling LACP, on page 93 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 111: Configuring Hardware Hashing For Multicast Traffic

    LACP learns the capabilities of LAN port groups dynamically and informs the other LAN ports. Once LACP identifies correctly matched Ethernet links, it facilitates grouping the links into an EtherChannel. The EtherChannel is then added to the spanning tree as a single bridge port. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 112: Configuring The Channel Mode For A Port

    3. switch(config-if)# channel-group channel-number [force] [mode {on | active | passive}] 4. switch(config-if)# no channel-group number mode DETAILED STEPS Command or Action Purpose Step 1 switch# configure terminal Enters configuration mode. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 113: Configuring The Lacp Fast Timer Rate

    (30 seconds) to the fast rate (1 second). This command is supported only on LACP-enabled interfaces. Before You Begin Ensure that you have enabled the LACP feature. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 114: Configuring The Lacp System Priority And System Id

    Before You Begin Ensure that you have enabled the LACP feature. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# lacp system-priority priority 3. (Optional) switch# show lacp system-identifier Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 115: Configuring The Lacp Port Priority

    Configures the port priority for use with LACP. Valid values are 1 through 65535, and higher numbers have lower priority. The default value is 32768. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 116: Disabling Lacp Graceful Convergence

    Administratively shuts down the port channel. shutdown Example: switch(config-if)# shutdown switch(config-if) # Step 4 no lacp graceful-convergence Disables LACP graceful convergence on the specified port channel. Example: switch(config-if)# no lacp graceful-convergence switch(config-if) # Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 117: Reenabling Lacp Graceful Convergence

    • Ensure that you are in the correct VDC. To switch to the correct VDC, enter the switchto vdc command. SUMMARY STEPS 1. configure terminal 2. interface port-channel number 3. shutdown 4. lacp graceful-convergence 5. no shutdown 6. (Optional) copy running-config startup-config Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 118: Verifying Etherchannel Configuration

    # interface port-channel 1 switch(config-if) # shutdown switch(config-if) # lacp graceful-convergence switch(config-if) # no shutdown switch(config-if) # Verifying EtherChannel Configuration To display EtherChannel configuration information, perform one of the following tasks: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 119: Verifying The Load-Balancing Outgoing Port Id

    Certain traffic flows are not subject to hashing, for example when there is a single port in a port-channel. Note To display the load-balancing outgoing port ID, perform one of the tasks listed in the table below. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 120: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Missing params will be substituted by 0's.Load-balance Algorithm on switch: source-dest-portcrc8_hash: 204 Outgoing port id: Ehernet1/1 Param(s) used to calculate load-balance: dst-port: 1 src-port: 0 dst-ip: 1.225.225.225 src-ip: 1.1.10.10 dst-mac: 0000.0000.0000 src-mac: aabb.ccdd.eeff Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 121: Configuring Virtual Port Channels

    A virtual port channel (vPC) allows links that are physically connected to two different Cisco Nexus 5000 Series switches or Cisco Nexus 2000 Series Fabric Extenders to appear as a single port channel by a third device (see the following figure). The third device can be a switch, server, or any other networking device.

  • Page 122: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    To create a vPC peer link you configure an EtherChannel on one Cisco Nexus 5000 Series switch by using two or more Ethernet ports. On the other switch, you configure another EtherChannel again using two or more Ethernet ports.

  • Page 123: Terminology

    The vPC domain ID must be the same on both switches. • vPC peer-keepalive link—The peer-keepalive link monitors the vitality of a vPC peer Cisco Nexus 5000 Series device. The peer-keepalive link sends configurable, periodic keepalive messages between vPC peer devices.

  • Page 124: Supported Vpc Topologies

    Nexus 5000 series switches or a pair of Nexus 5500 Series switches but you cannot connect a Nexus 5000 Series switch to a Nexus 5500 Series switch in a vPC topology.

  • Page 125: Single Homed Fabric Extender Vpc Topology

    Depending on the FEX model, you may be able to connect one or more network adapter interfaces to each fabric extender. As an example, Figure 10 refers to a topology built with the Cisco Nexus 2148T fabric extender, where a server has one link only to each fabric extender. A topology with Cisco Nexus 2248TP or with Cisco Nexus 2232PP fabric extender could consist of more links from the server to a single fabric extender.

  • Page 126: Dual Homed Fabric Extender Vpc Topology

    Figure 11: Dual Homed Fabric Extender vPC Topology The Cisco Nexus 5000 Series switch can support up to 12 configured dual homed Fabric Extenders with this topology. A maximum of 576 single homed servers can be connected to this configuration.

  • Page 127: Peer-Keepalive Link And Messages

    The peer-keepalive status is checked only when the peer-link goes down. The vPC peer-keepalive can be carried either in the management or default VRF on the Cisco Nexus 5000 Series switch. When you configure the switches to use the management VRF, the source and destination for the keepalive messages are the mgmt 0 interface IP addresses.

  • Page 128: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    • Fabric Extender FEX number configured on an EtherChannel fabric interface; for the Fabric Extender vPC toplogy. If any of these parameters are not enabled or defined on either switch, the vPC consistency check ignores those parameters. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 129: Configuration Parameters That Should Be Identical

    Graceful Type-1 Check Beginning with Cisco NX--OS Release 5.0(2)N2(1), when a consistency check fails, vPCs are brought down only on the secondary vPC switch. The VLANs remain up on the primary switch and Type-1 configurations can be performed without traffic disruption.

  • Page 130: Per-Vlan Consistency Check

    VLANs are not affected. vPC Auto-Recovery Beginning with Cisco NX-OS Release 5.0(2)N2(1), the vPC auto-recovery feature re-enables vPC links in the following scenarios: When both vPC peer switches reload and only one switch reboots, auto-recovery allows that switch to assume the role of the primary switch and the vPC links will be allowed to come up after a predetermined period of time.

  • Page 131: Vpc Number

    When you configure the vPC peer link, the vPC peer switches negotiate that one of the connected switches is the primary switch and the other connected switch is the secondary switch. By default, the Cisco NX-OS software uses the lowest MAC address to elect the primary switch. The software takes different actions on each switch—that is, the primary and secondary—only in certain failover conditions.

  • Page 132: Vpc Interactions With Other Features

    STP process for the vPC interfaces on the secondary vPC peer switch. The primary vPC switch synchronizes the STP state on the vPC secondary peer switch using Cisco Fabric Services over Ethernet (CFSoE).

  • Page 133: Cfsoe

    • You must configure the peer-keepalive link before the system can form the vPC peer link. • You can connect a pair of Cisco Nexus 5000 Series switches or a pair of Cisco Nexus 5500 Series switches in a vPC directly to another switch or to a server. vPC peer switches must be of the same type,...

  • Page 134: Configuring Vpcs

    Disabling vPCs You can disable the vPC feature. Note When you disable the vPC feature, the Cisco Nexus 5000 Series switch clears all the vPC configurations. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 135: Creating A Vpc Domain

    You must configure both switches on either side of the vPC peer link with the following procedure. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# vpc domain domain-id 3. (Optional) switch# show vpc brief 4. (Optional) switch# copy running-config startup-config Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 136: Configuring A Vpc Keepalive Link And Messages

    VRF management and VRF default. The mgmt0 interface and all SVI interfaces reside in VRF management and default. The Cisco NX-OS software uses the peer-keepalive link between the vPC peers to transmit periodic, configurable keepalive messages. You must have Layer 3 connectivity between the peer devices to transmit these messages.

  • Page 137: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    (Optional) Displays information about the configuration for the keepalive messages. Step 6 switch# copy running-config startup-config (Optional) Copies the running configuration to the startup configuration. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 138: Configuring A Keepalive Link When Using A Front-Panel 10-Gigabit Ethernet Port

    64 bytes from 123.1.1.1: icmp_seq=2 ttl=254 time=4.965 ms 64 bytes from 123.1.1.1: icmp_seq=3 ttl=254 time=4.971 ms 64 bytes from 123.1.1.1: icmp_seq=4 ttl=254 time=4.915 ms --- 123.1.1.1 ping statistics --- Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 139: Creating A Vpc Peer Link

    Copies the running configuration to the startup configuration. This example shows how to configure a vPC peer link: switch# configure terminal switch(config)# interface port-channel 20 switch(config-if)# vpc peer-link Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 140: Checking The Configuration Compatibility

    After you have configured the vPC peer link on both vPC peer switches, check that the configurations are consistent on all vPC interfaces. Note Beginning with Cisco NX-OS Release 5.0(2)N1(1), the following QoS parameters support Type 2 consistency checks: • Network QoS—MTU and Pause •...

  • Page 141: Enabling Vpc Auto-Recovery

    This examples shows how to view the status of the auto-recovery feature in vPC domain 10. switch(config-vpc-domain)# show running-config vpc !Command: show running-config vpc !Time: Tue Dec 7 02:38:44 2010 version 5.0(2)N2(1) feature vpc vpc domain 10 peer-keepalive destination 10.193.51.170 auto-recovery Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 142: Configuring The Restore Time Delay

    Configuring the Restore Time Delay Beginning with Cisco NX-OS Release 5.0(3)N1(1), you can configure a restore timer that delays the vPC from coming back up until after the peer adjacency forms and the VLAN interfaces are back up. This feature avoids packet drops when the routing tables may not be converged before the vPC is once again passing traffic.

  • Page 143: Configuring The Vrf Name

    Configuring the VRF Name The services provided by a Cisco Nexus 5000 Series switch, such as ping, ssh, telnet, radius, are VRF aware. The VRF name must be configured in order for the correct routing table to be used.

  • Page 144: Binding A Vrf Instance To A Vpc

    The VLAN ID range is from 1 to 3967, and 4049 to 4093. This example shows how to bind a vPC to the default VRF using VLAN 2: switch(config)# vpc bind-vrf default vlan vlan2 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 145: Enabling Layer 3 Forwarding To The Gateway Mac Address Of The Vpc

    Enabling Layer 3 Forwarding to the Gateway MAC Address of the vPC Beginning with Cisco NX-OS Release 5.0(3)N1(1), this feature applies to Cisco Nexus 5500 Plaform switches. The vPC peer-gateway feature allows a vPC switch to act as the active gateway for packets that are addressed to the router MAC address of the vPC peer.

  • Page 146: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    --------::Going through port database. Please be patient.::-------- VLAN Orphan Ports ------- ------------------------- 1 Po600 2 Po600 3 Po600 4 Po600 5 Po600 6 Po600 7 Po600 8 Po600 9 Po600 10 Po600 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 147: Creating An Etherchannel Host Interface

    14 Po600 Creating an EtherChannel Host Interface To connect to a downstream server from a Cisco Nexus 2000 Series Fabric Extender you can create a EtherChannel host interface. An EtherChannel host interface can have only one host interface as a member depending on the fabric extender model.

  • Page 148: Moving Other Etherchannels Into A Vpc

    The range is from 1 to 4096. The vPC number that you assign to the EtherChannel connecting to the downstream switch from the vPC peer switch must be identical on both vPC peer switches. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 149: Manually Configuring A Vpc Domain Mac Address

    Selects an existing vPC domain on the switch, or creates a new vPC domain, and enters the vpc-domain configuration mode. There is no default domain-id ; the range is from 1 to 1000. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 150: Manually Configuring The System Priority

    Selects an existing vPC domain on the switch, or creates a new vPC domain, and enters the vpc-domain configuration mode. There is no default domain-id ; the range is from 1 to 1000. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 151: Manually Configuring A Vpc Peer Switch Role

    Manually Configuring a vPC Peer Switch Role By default, the Cisco NX-OS software elects a primary and secondary vPC peer switch after you configure the vPC domain and both sides of the vPC peer link. However, you may want to elect a specific vPC peer switch as the primary switch for the vPC.

  • Page 152: Verifying The Vpc Configuration

    Displays the status of those parameters that must be consistent across all vPC interfaces. switch# show vpc peer-keepalive Displays information on the peer-keepalive messages. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 153: Viewing The Graceful Type-1 Check Status

    Note only for the vPC peer device that you are working on. For detailed information about the fields in the output from these commands, see the Cisco Nexus 5000 Series Command Reference. Viewing The Graceful Type-1 Check Status To view the current status of the graceful Type-1 consistency check, enter the show vpc brief command.

  • Page 154: Viewing An Interface-Specific Type-1 Inconsistency

    Enter the show vpc brief command on the secondary switch to view the status of the suspended vPC VLAN: switch(config-if)# show vpc brief Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 10 Peer status : peer adjacency formed ok Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 155: Viewing A Per-Vlan Consistency Status

    This example shows the status of the VLAN in a consistent state before an inconsistency occurs. then, the no spanning-tree vlan 5 command is entered which triggers the inconsistency between the primary and secondary switch. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 156: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    The show vpc brief command on the primary switch also shows the per-VLAN consistency status as Failed. switch(config)# show vpc brief Legend: (*) - local vPC is down, forwarding via vPC peer-link Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 157: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    VLAN Mapping STP Loopguard success 0-4095 STP Bridge Assurance success 0-4095 STP Port Type, Edge success 0-4095 BPDUFilter, Edge BPDUGuard STP MST Simulate PVST success 0-4095 Pass Vlans 0-4,6-4095 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 158: Vpc Example Configurations

    4. Create a Fabric Extender identifier (for example, "100"). 5. Configure the fabric EtherChannel links for the Fabric Extender 100. 6. Configure each host interface port on the Fabric Extender 100 on both Nexus 5000 Series switch as for all the other steps.

  • Page 159: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    NX-5000-1(config-if)# vpc 100 NX-5000-1(config-if)# fex associate 100 NX-5000-1(config-if)# exit Step 6 Configure each host interface port on the Fabric Extender 100 on both Nexus 5000 Series switch as for all the other steps. NX-5000-1(config)# interface ethernet 100/1/1-48 NX-5000-1(config-if)# switchport mode access...

  • Page 160: Single Homed Fabric Extender Vpc Configuration Example

    Extender NX-2000-100. You must repeat these steps on its vPC peer, NX-5000-2, which is connected to the Fabric Extender NX-2000-101. Before You Begin Ensure that the Cisco Nexus 2000 Series Fabric Extenders NX-2000-100 and NX-2000-101 are attached and online. SUMMARY STEPS 1.

  • Page 161: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Configure the fabric EtherChannel links for the Fabric Extender NX-2000-100. NX-5000-1(config)# interface ethernet 1/20-21 NX-5000-1(config-if)# channel-group 100 NX-5000-1(config-if)# exit NX-5000-1(config)# interface port-channel 100 NX-5000-1(config-if)# switchport mode fex-fabric NX-5000-1(config-if)# fex associate 100 NX-5000-1(config-if)# exit Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 162: Vpc Default Settings

    Table 15: Default vPC Parameters Parameters Default vPC system priority 32667 vPC peer-keepalive message Disabled vPC peer-keepalive interval 1 second vPC peer-keepalive timeout 5 seconds vPC peer-keepalive UDP port 3200 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 163: Configuring Rapid Pvst

    Spanning tree is used to refer to IEEE 802.1w and IEEE 802.1s. If the text is discussing the IEEE 802.1D Note Spanning Tree Protocol, 802.1D is stated specifically. This chapter describes the configuration of Rapid PVST+ on Cisco Nexus 5000 Series switches. It includes the following sections: •...

  • Page 164: Understanding How A Topology Is Created

    Each VLAN on each switch has a unique 64-bit bridge ID consisting of a bridge priority value, an extended system ID (IEEE 802.1t), and an STP MAC address allocation. Bridge Priority Value The bridge priority is a 4-bit value when the extended system ID is enabled. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 165: Extended System Id

    Configuring Rapid PVST+ Understanding STP In Cisco NX-OS, the extended system ID is always enabled; you cannot be disable the extended system Note Extended System ID A 12-bit extended system ID field is part of the bridge ID. Figure 14: Bridge ID with Extended System ID The switches always use the 12-bit extended system ID.

  • Page 166: Understanding Bpdus

    A BPDU exchange results in the following: • One switch is elected as the root bridge. • The shortest distance to the root bridge is calculated for each switch based on the path cost. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 167: Election Of The Root Bridge

    The goal is to make the fastest link the root port. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 168: Understanding Rapid Pvst

    • Edge ports—When you configure a port as an edge port on an RSTP switch, the edge port immediately transitions to the forwarding state. (This immediate transition was previously a Cisco-proprietary feature named PortFast.) You should only configure on ports that connect to a single end station as edge ports.

  • Page 169: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    The TCA flag is used only when the switch is interacting with switches that are running legacy 802.1D STP. The proposal and agreement sequence then quickly propagates toward the edge of the network and quickly restores connectivity after a topology change. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 170: Rapid Pvst+ Bpdus

    Another important change is that the Rapid PVST+ BPDU is type 2, version 2, which makes it possible for the switch to detect connected legacy (802.1D) bridges. The BPDU for 802.1D is version 0. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 171: Proposal And Agreement Handshake

    This proposal/agreement handshake is initiated only when a non-edge port moves from the blocking to the forwarding state. The handshaking process then proliferates step-by-step throughout the topology. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 172: Protocol Timers

    LAN segment. A backup port provides another path in the topology to the switch. • Disabled port—Has no role within the operation of the spanning tree. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 173: Port States

    Each LAN port on a software using Rapid PVST+ or MST exists in one of the following four states: • Blocking—The LAN port does not participate in frame forwarding. • Learning—The LAN port prepares to participate in frame forwarding. • Forwarding—The LAN port forwards frames. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 174: Blocking State

    • Receives BPDUs and directs them to the system module. • Receives, processes, and transmits BPDUs received from the system module. • Receives and responds to network management messages. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 175: Forwarding State

    Table 18: Port State Active Topology Operational Status Port State Is Port Included in the Active Topology? Enabled Blocking Enabled Learning Enabled Forwarding Disabled Disabled Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 176: Synchronization Of Port Roles

    If a port receives a superior BPDU, Rapid PVST+ triggers a reconfiguration. If the port is proposed and is selected as the new root port, Rapid PVST+ forces all the other ports to synchronize. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 177: Processing Inferior Bpdu Information

    The STP port path-cost default value is determined from the media speed and path-cost calculation method of a LAN interface. If a loop occurs, STP considers the port cost when selecting a LAN interface to put into the forwarding state. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 178: Port Priority

    When you connect a Cisco switch to a non-Cisco switch through an 802.1Q trunk, the Cisco switch combines the STP instance of the 802.1Q VLAN of the trunk with the STP instance of the non-Cisco 802.1Q switch. However, all per-VLAN STP information that is maintained by Cisco switches is separated by a cloud of non-Cisco 802.1Q switches.

  • Page 179: Rapid Pvst+ Interoperation With Legacy 802.1D Stp

    Configuring Rapid PVST+ Rapid PVST+, which has the 802.1w standard applied to the Rapid PVST+ protocol, is the default STP setting in the software. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 180: Enabling Rapid Pvst

    Rapid PVST+. Enabling Rapid PVST+ per VLAN You can enable or disable Rapid PVST+ on each VLAN. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 181: Configuring The Root Bridge Id

    VLAN. The switch sets the bridge priority for the specified VLANs to 24576 if this value will cause the switch to become the root for the specified VLANs. If any root bridge for the Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 182: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    2 seconds. This example shows how to configure the switch as the root bridge for a VLAN: switch# configure terminal switch(config)# spanning-tree vlan 5 root primary diameter 4 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 183: Configuring A Secondary Root Bridge

    You can assign lower priority values to LAN ports that you want Rapid PVST+ to select first and higher priority values to LAN ports that you want Rapid PVST+ to select last. If all LAN ports have the same priority Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 184: Configuring The Rapid Pvst+ Pathcost Method And Port Cost

    In Rapid PVST+ mode, you can use either the short or long pathcost method, and you can configure the Note method in either the interface or configuration submode.The default pathcost method is short. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 185: Configuring The Rapid Pvst+ Bridge Priority Of A Vlan

    You can configure the Rapid PVST+ bridge priority of a VLAN. Note Be careful when using this configuration. For most situations, we recommend that you configure the primary root and secondary root to modify the bridge priority. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 186: Configuring The Rapid Pvst+ Hello Time For A Vlan

    Configures the hello time of a VLAN. The hello time value hello-time hello-time can be from 1 to 10 seconds. The default is 2 seconds. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 187: Configuring The Rapid Pvst+ Forward Delay Time For A Vlan

    You can configure the maximum age time per VLAN when using Rapid PVST+. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# spanning-tree vlan vlan-range max-age max-age DETAILED STEPS Command or Action Purpose Step 1 switch# configure terminal Enters configuration mode. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 188: Specifying The Link Type

    If the link type is shared, the STP reverts to 802.1D. The default is auto, which sets the link type based on the duplex setting of the interface. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 189: Restarting The Protocol

    Forward Delay 15 sec Interface Role Sts Cost Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Eth1/3 Root FWD 2 128.131 P2p Peer(STP) veth1/1 Desg FWD 2 128.129 Edge P2p Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 190: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Configuring Rapid PVST+ Verifying Rapid PVST+ Configurations Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 191: C H A P T E

    Spanning tree is used to refer to IEEE 802.1w and IEEE 802.1s. If the text is discussing the IEEE 802.1D Note Spanning Tree Protocol, 802.1D is stated specifically. This chapter describes how to configure MST on Cisco Nexus 5000 Series switches. It contains the following sections: •...

  • Page 192: Mst Regions

    Each region has only one MST BPDU, and that BPDU carries an M-record for each MSTI within the region (see the following figure). Only the IST sends BPDUs for the MST region; all M-records are encapsulated in Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 193: Mst Configuration Information

    MST BPDUs contain these three configuration parameters. An MST bridge accepts an MST BPDU into its own region only if these three configuration parameters match exactly. If one configuration attribute differs, the MST bridge considers the BPDU to be from another MST region. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 194: Ist, Cist, And Cst

    During initialization, an MST region might have many subregions, each with its own CIST regional root. As switches receive superior IST information from a neighbor in the same region, they leave their old subregions Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 195: Spanning Tree Operations Between Mst Regions

    BPDU transmission (for example, hello time, forward time, max-age, and max-hops) are configured only on the CST instance but affect all MSTIs. You can configure Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 196: Mst Terminology

    STP bridge or receives an agreement proposal from an MST bridge with a different configuration or a Rapid PVST+ bridge. This definition allows two ports that are internal to a region to share a segment Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 197: Spanning-Tree Dispute Mechanism

    A blocks (or keeps blocking) its port, which prevents the bridging loop. The block is shown as an STP dispute. Figure 24: Detecting a Unidirectional Link Failure Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 198: Port Cost And Port Priority

    MST configuration. MST interoperates with the Cisco prestandard MSTP whenever it receives prestandard MSTP on an MST Note port; no explicit configuration is necessary.

  • Page 199: Interoperability With Rapid Pvst+: Understanding Pvst Simulation

    Changing the spanning tree mode disrupts traffic because all spanning tree instances are stopped for the Caution previous mode and started for the new mode. Also, having two different spanning-tree modes on vPC peer switches is an inconsistency, hence this operation is disruptive. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 200: Entering Mst Configuration Mode

    When you are working in MST configuration mode, note the difference between the exit and abort commands. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 201: Specifying The Mst Name

    You configure a region name on the bridge. For two or more bridges to be in the same MST region, they must have the identical MST name, VLAN-to-instance mapping, and MST revision number. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 202: Specifying The Mst Configuration Revision Number

    Enters MST configuration submode. Step 3 switch(config-mst)# revision version Specifies the revision number for the MST region. The range is from 0 to 65535, and the default value is 0. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 203: Specifying The Configuration On An Mst Region

    To specify a VLAN series, enter a comma; for example, enter the instance 1 vlan 10, 20, 30 command to map VLANs 10, 20, and 30 to MST instance Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 204: Mapping And Unmapping Vlans To Mst Instances

    You cannot disable an MSTI. For two or more bridges to be in the same MST region, they must have the identical MST name, VLAN-to-instance mapping, and MST revision number. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 205: Mapping Secondary Vlans To Same Msti As Primary Vlans For Private Vlans

    When you are working with private VLANs on the system, all secondary VLANs must be in the same MSTI and their associated primary VLAN. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# spanning-tree mst configuration 3. switch(config-mst)# private-vlan synchronize Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 206: Configuring The Root Bridge

    SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# spanning-tree mst instance-id root {primary | secondary} [diameter dia [hello-time hello-time]] 3. (Optional) switch(config)# no spanning-tree mst instance-id root Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 207: Configuring A Secondary Root Bridge

    2. switch(config)# spanning-tree mst instance-id root {primary | secondary} [diameter dia [hello-time hello-time]] 3. (Optional) switch(config)# no spanning-tree mst instance-id root DETAILED STEPS Command or Action Purpose Step 1 switch# configure terminal Enters configuration mode. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 208: Configuring The Port Priority

    {{type slot/port} Specifies an interface to configure, and enters interface configuration | {port-channel number}} mode. Step 3 switch(config-if)# spanning-tree mst Configures the port priority as follows: instance-id port-priority priority Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 209: Configuring The Port Cost

    {{type Specifies an interface to configure, and enters interface configuration mode. slot/port} | {port-channel number}} Step 3 switch(config-if)# spanning-tree mst Configures the cost. instance-id cost [cost | auto] Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 210: Configuring The Switch Priority

    • For instance-id, you can specify a single instance, a range of instances separated by a hyphen, or a series of instances separated by a comma. The range is from 1 to 4094. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 211: Configuring The Hello Time

    These messages mean that the switch is alive. For seconds, the range is from 1 to 10, and the default is 2 seconds. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 212: Configuring The Forwarding-Delay Time

    You set the maximum-aging timer for all MST instances on the switch with one command (the maximum age time only applies to the IST). SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# spanning-tree mst max-age seconds Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 213: Configuring The Maximum-Hop Count

    1 to 255, and the default value is 20 hops. This example shows how to set the maximum hops to 40: switch# configure terminal switch(config)# spanning-tree mst max-hops 40 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 214: Configuring Pvst Simulation Globally

    2. switch(config)# interface {{type slot/port} | {port-channel number}} 3. switch(config-if)# spanning-tree mst simulate pvst disable 4. switch(config-if)# spanning-tree mst simulate pvst 5. switch(config-if)# no spanning-tree mst simulate pvst Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 215: Specifying The Link Type

    If you set the link to shared, STP reverts to 802.1D. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# interface type slot/port 3. switch(config-if)# spanning-tree link-type {auto | point-to-point | shared} Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 216: Restarting The Protocol

    Restarts MST on entire switch or specified [interface-num | port-channel]] interfaces. This example shows how to restart MST on the Ethernet interface on slot 2, port 8: switch# clear spanning-tree detected-protocol interface ethernet 2/8 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 217: Verifying Mst Configurations

    The following example shows how to display current MST configuration: switch# show spanning-tree mst configuration % Switch is not in mst mode Name [mist-attempt] Revision Instances configured 2 Instance Vlans mapped -------- --------------------------------------------------------------------- 1-12,14-41,43-4094 13,42 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 218: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    Configuring Multiple Spanning Tree Verifying MST Configurations Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 219: Chapter 1 1 Configuring Stp Extensions

    About STP Extensions, page 201 About STP Extensions Cisco has added extensions to STP that make convergence more efficient. In some cases, even though similar functionality may be incorporated into the IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) standard, we recommend using these extensions.

  • Page 220: Spanning Tree Network Ports

    When you configure BPDU Guard globally, it is effective only on operational spanning tree edge ports. In a valid configuration, LAN edge interfaces do not receive BPDUs. A BPDU that is received by an edge LAN Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 221: Understanding Bpdu Filtering

    BPDUs, the port returns to the spanning tree normal port state and BPDU Filtering is disabled. Default Enable Disable Disable Default Disable Enabled/Disabled Disable Disable Enabled/Disabled Enabled/Disabled Disable Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 222: Understanding Loop Guard

    When you enable Root Guard on a port, Root Guard does not allow that port to become a root port. If a received BPDU triggers an STP convergence that makes that designated port become a root port, that port is Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 223: Configuring Stp Extensions

    Before You Begin Ensure that STP is configured. Ensure that you are configuring the ports correctly for the type of device to which the interface is connected. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 224: Configuring Spanning Tree Edge Ports On Specified Interfaces

    • spanning-tree port type edge—This command explicitly enables edge behavior on the access port. • spanning-tree port type edge trunk—This command explicitly enables edge behavior on the trunk port. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 225: Configuring Spanning Tree Network Ports On Specified Interfaces

    Configuring Spanning Tree Network Ports on Specified Interfaces You can configure spanning tree network ports on specified interfaces. Bridge Assurance runs only on spanning tree network ports. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 226: Cisco Nexus 5000 Series Nx-Os Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1

    This example shows how to configure the Ethernet interface 1/4 to be a spanning tree network port: switch# configure terminal switch(config)# interface ethernet 1/4 switch(config-if)# spanning-tree port type network Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 227: Enabling Bpdu Guard Globally

    • no spanning-tree bpduguard—Enables BPDU Guard on the interface if it is an operational edge port and if the spanning-tree port type edge bpduguard default command is configured. Before You Begin Ensure that STP is configured. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 228: Enabling Bpdu Filtering Globally

    BPDUs at linkup before they effectively filter outbound BPDUs. If a BPDU is received on an edge port, it immediately loses its operational edge port status and BPDU Filtering is disabled. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 229: Enabling Bpdu Filtering On Specified Interfaces

    • no spanning-tree bpdufilter—Enables BPDU Filtering on the interface if the interface is in operational edge port and if you configure the spanning-tree port type edge bpdufilter default command. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 230: Enabling Loop Guard Globally

    Loop Guard provides additional security in the bridge network. Loop Guard prevents alternate or root ports from becoming the designated port because of a failure that could lead to a unidirectional link. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 231: Enabling Loop Guard Or Root Guard On Specified Interfaces

    Entering the Loop Guard command for the specified interface overrides the global Loop Guard command. Before You Begin Ensure that STP is configured. Ensure that you are configuring Loop Guard on spanning tree normal or network ports. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 232: Verifying Stp Extension Configuration

    [all] Displays the current status of spanning tree on the switch switch# show spanning-tree [options] Displays selected detailed information for the current spanning tree configuration. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 233: Configuring Lldp

    DCBXP parameters are packaged into a specific DCBXP TLV. This TLV is designed to provide an acknowledgement to the received LLDP packet. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 234 Use the system-capabilities option to specify the system capabilities TLV messages. Use the system-description option to specify the system description TLV messages. Use the system-name option to specify the system name TLV messages. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 235: Configuring Interface Lldp Commands

    Step 4 (Optional)switch#show lldp Displays LLDP configurations. This example shows how to set an interface to transmit LLDP packets: switch# configure terminal switch(config)# interface ethernet 1/2 switch(config-if)# lldp transmit Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 236 LLDP Timers holdtime 120 seconds reinit 2 seconds msg_tx_interval 30 seconds This example shows how to display LLDP counters: switch# show lldp traffic LLDP traffic statistics: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 237 Configuring Interface LLDP Commands Total frames out: 8464 Total Entries aged: 6 Total frames in: 6342 Total frames received in error: 2 Total frames discarded: 2 Total TLVs unrecognized: 0 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 238 Configuring LLDP Configuring Interface LLDP Commands Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 239: Configuring The Mac Address Table

    C H A P T E R Configuring the MAC Address Table All Ethernet interfaces on Cisco Nexus 5000 Series switches maintain media access control (MAC) address tables. This chapter describes the configuration of the MAC address tables. It includes the following sections: •...

  • Page 240: Configuring Mac Addresses

    Configuring the Aging Time for the MAC Table You can configure the amount of time that an entry (the packet source MAC address and port that packet ingresses) remain in the MAC table. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 241: Clearing Dynamic Addresses From The Mac Table

    This example shows how to clear the dynamic entries in the MAC address table: switch# clear mac-address-table dynamic Verifying the MAC Address Configuration To display MAC address configuration information, perform one of these tasks: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 242 Eth1/3 001c.b05a.5380 dynamic 200 Eth1/3 Total MAC Addresses: 2 This example shows how to display the current aging time: switch# show mac-address-table aging-time Vlan Aging Time ----- ---------- Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 243: Configuring Igmp Snooping

    By examining (snooping), Internet Group Management Protocol (IGMP) membership report messages from interested hosts, multicast traffic is limited to the subset of VLAN interfaces on which the hosts reside. This chapter describes the configuration of IGMP snooping on Cisco Nexus 5000 Series switches. It includes the following sections: •...

  • Page 244: Igmpv1 And Igmpv2

    IGMPv1 does not provide an explicit IGMP leave message, so the software must rely on the membership message timeout to indicate that no hosts remain that want to receive multicast data for a particular group. Cisco NX-OS ignores the configuration of last member query interval when you enable the fast leave Note feature because it does not check for remaining hosts.

  • Page 245: Igmpv3

    IGMP Forwarding The control plane of the Cisco Nexus 5000 Series switch is able to detect IP addresses but forwarding occurs using the MAC address only. When a host connected to the switch wants to join an IP multicast group, it sends an unsolicited IGMP join message, specifying the IP multicast group to join.

  • Page 246: Configuring Igmp Snooping Parameters

    The interface to the router must be in the selected VLAN. Static group Configures an interface belonging to a VLAN as a static member of a multicast group. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 247 Configures a snooping querier when you do not enable PIM because querier IP-address multicast traffic does not need to be routed. The IP address is used as the source in messages. The default is disabled. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 248: Verifying Igmp Snooping Configuration

    [[vlan] Displays IGMP snooping queriers by VLAN. vlan-id] switch# show ip igmp snooping mrouter [[vlan] Displays multicast router ports by VLAN. vlan-id] Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 249 Switch-querier enabled, address 172.16.24.1, currently running Explicit tracking enabled Fast leave enabled Report suppression enabled Router port detection using PIM Hellos, IGMP Queries Number of router-ports: 1 Number of groups: 1 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 250 Configuring IGMP Snooping Verifying IGMP Snooping Configuration Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 251: Configuring Traffic Storm Control

    C H A P T E R Configuring Traffic Storm Control This chapter describes how to configure traffic storm control on Cisco Nexus 5000 Series switches. It contains the following sections: • Information About Traffic Storm Control, page 233 •...

  • Page 252: Traffic Storm Guidelines And Limitations

    For example, a higher threshold allows more packets to pass through. Traffic storm control on the Cisco Nexus 5000 Series switch is implemented in the hardware. The traffic storm control circuitry monitors packets that pass from an Ethernet interface to the switching bus. Using the...

  • Page 253: Configuring Traffic Storm Control

    The default state is disabled. This example shows how to configure unicast traffic storm control for Ethernet interface 1/4: switch# configure terminal switch(config)# interface ethernet 1/4 switch(config-if)# storm-control unicast level 40 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 254: Verifying Traffic Storm Control Configuration

    Default Traffic Storm Settings The following table lists the default settings for traffic storm control parameters. Table 22: Default Traffic Storm Control Parameters Parameters Default Traffic storm control Disabled Threshold percentage Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 255: C H A P T E

    C H A P T E R Configuring the Fabric Extender This chapter describes how to configure a Cisco Nexus 2000 Series Fabric Extender using the Cisco Nexus 5000 Series device and includes the following sections: • Information About the Cisco Nexus 2000 Series Fabric Extender, page 237 •...

  • Page 256: Fabric Extender Terminology

    Spanning Tree Protocol (STP). Figure 27: Single Management Domain The Cisco Nexus 2000 Series Fabric Extender forwards all traffic to its 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.

  • Page 257: Fabric Extender Features

    • Port channel host interface—A port channel host interface for connection to a server or host system. Fabric Extender Features The Cisco Nexus 2000 Series Fabric Extender allows a single switch—and a single consistent set of switch features—to be supported across a large number of hosts and servers. By supporting a large server-domain under a single management entity, policies can be enforced more efficiently.

  • Page 258: Host Port Channel

    Configuring the Fabric Extender Host Port Channel Ingress and egress packet counters are provided on each host interface. For more information about BPDU Guard and CDP, see the Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide. Host Port Channel...

  • Page 259: Fibre Channel Over Ethernet Support

    See the Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide for configuration details. Protocol Offload To reduce the load on the control plane of the Cisco Nexus 5000 Series device, Cisco NX-OS provides the ability to offload link-level protocol processing to the Fabric Extender CPU. The following protocols are supported: •...

  • Page 260: Access Control Lists

    MTU of all drop classes and the MTU on the no-drop queue is set to the maximum MTU of all no-drop classes. For more information about LLC and quality-of-service, see the Cisco Nexus 5000 Series NX-OS Quality of Service Configuration Guide.

  • Page 261: Fabric Interface Features

    In the case of the Cisco Nexus 2000 Series Fabric Extender, oversubscription, which is a function of the available fabric interfaces to active host interfaces, provides cost-effective scalability and flexibility for Ethernet environments.

  • Page 262: Management Model

    100/1000BASE-T (100-Mb/1-Gigabit) Ethernet host interfaces. It offers similar configurations to the Cisco Nexus 2148T when its host interfaces are running in Gigabit Ethernet mode. The Cisco Nexus 2248TP can easily be run with no oversubscription when its host interfaces are running in 100-Mb mode.

  • Page 263: Forwarding Model

    Connection Model Two methods (the static pinning fabric interface connection and the EtherChannel fabric interface connection) allow the traffic from an end host to the parent switch to be distributed when going through the Cisco Nexus 2000 Series Fabric Extender.

  • Page 264: Static Pinning Fabric Interface Connection

    To guarantee a deterministic and sticky association across a reboot, you can manually redistribute the pinning. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 265: Port Channel Fabric Interface Connection

    FEX are set to the down state. Port Numbering Convention The following port numbering convention is used for the Fabric Extender: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 266: Fabric Extender Image Management

    Fabric Extender. When you enter the install all command, it upgrades the software on the parent Cisco Nexus 5000 Series switch and also upgrades the software on any attached Fabric Extender. To minimize downtime as much as possible, the Fabric Extender remains online while the installation process loads its new software image.

  • Page 267: Information About Associating A Fabric Extender To A Fabric Interface

    4 10-Gigabit Ethernet fabric interfaces with SFP+ interface adapters for its uplink connection to the parent switch. The Cisco Nexus 2248TP-E has all the features of the Cisco Nexus 2248TP with these additional features: ◦ A larger buffer to absorb large bursts.

  • Page 268: Associating A Fabric Extender To An Ethernet Interface

    This example shows how to associate the Fabric Extender to an Ethernet interface on the parent device: switch# configure terminal switch(config)# interface ethernet 1/40 switch(config-if)# switchport mode fex-fabric Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 269: Associating A Fabric Extender To A Port Channel

    Step 1 configure terminal Enters configuration mode. Example: switch# configure terminal switch(config)# Step 2 interface port-channel channel Specifies a port channel to configure. Example: switch(config)# interface port-channel 4 switch(config-if)# Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 270 This example shows how to display the association of the Fabric Extender and the parent device: switch# show interface port-channel 4 fex-intf Fabric Interface Interfaces --------------------------------------------------- Eth101/1/48 Eth101/1/47 Eth101/1/46 Eth101/1/45 Eth101/1/44 Eth101/1/43 Eth101/1/42 Eth101/1/41 Eth101/1/40 Eth101/1/39 Eth101/1/38 Eth101/1/37 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 271: Disassociating A Fabric Extender From An Interface

    Disassociates the Fabric Extender unit attached to the no fex associate interface. Example: switch(config-if)# no fex associate Configuring Fabric Extender Global Features You can configure global features for a Fabric Extender. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 272 • N2148T—48 1000Base-T Ethernet host interfaces and 4 10-Gigabit SFP+ switch(config-fex)# type N2248T Ethernet fabric interfaces module • N2232TP—32 10-Gigabit Base-T Ethernet host interfaces and 8 10-Gigabit SFP+ Ethernet fabric interfaces module Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 273: Enabling The Fabric Extender Locator Led

    • N2232TT—32 10-Gigabit Base-T Ethernet host interfaces and 8 10-Gigabit Base-T Ethernet fabric interfaces module The parent Cisco Nexus 5000 Series switch remembers the type of the Fabric Extender in its binary configuration. When this feature is configured, the Fabric Extender is only allowed to come online if its type matches the configured FEX-type.

  • Page 274: Redistributing The Links

    Configuring the Fabric Extender Redistributing the Links Prior to Cisco NX-OS Release 4.1(3)N1(1), the locator beacon LED was enabled with the beacon FEX Note submode command. SUMMARY STEPS 1. switch# locator-led fex FEX-number 2. (Optional) switch# no locator-led fex FEX-number...

  • Page 275: Maintaining The Pinning Order

    The fex pinning redistribute command disrupts all the host interface ports of the Fabric Extender. Caution Verifying the Fabric Extender Configuration To display configuration information about the defined interfaces on a Fabric Extender, perform one of the following tasks: Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 276 Po100 Eth100/1/7 Po100 Po100 Eth100/1/8 Po100 Po100 Eth100/1/9 Po100 Po100 Eth100/1/10 Po100 Po100 Eth100/1/11 Po100 Po100 Eth100/1/12 Po100 Po100 Eth100/1/13 Po100 Po100 Eth100/1/14 Po100 Po100 Eth100/1/15 Po100 Po100 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 277 Eth1/33 Active N2K-C2232P-10GE JAS12334ABC Eth1/34 Active N2K-C2232P-10GE JAS12334ABC Eth1/35 Active N2K-C2232P-10GE JAS12334ABC Eth1/36 Active N2K-C2232P-10GE JAS12334ABC Eth1/37 Active N2K-C2232P-10GE JAF1333ADDD Eth1/38 Active N2K-C2232P-10GE JAF1333ADDD Eth1/39 Active N2K-C2232P-10GE JAF1333ADDD Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)

  • Page 278: Verifying The Chassis Management Information

    Configuration Examples for Chassis Management This example shows how to display the module information about all connected Fabric Extender units: switch# show module fex FEX Mod Ports Card Type Model Status. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 279 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 Port ------------------------------------------------------------------------ TestFabricPorts: Fabric 1 Port ------------ Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 280 : 160 Block Checksum : 0x1a1e EEPROM Size : 65535 Block Count FRU Major Type : 0x6002 FRU Minor Type : 0x0 OEM String : Cisco Systems, Inc. Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 281 Block Checksum : 0x2cf Feature Bits : 0x0 HW Changes Bits : 0x0 Stackmib OID MAC Addresses : 00-0d-ec-e3-28-00 Number of MACs : 64 OEM Enterprise OEM MIB Offset Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 282 : 12336.12336.12336.12336.12336.12336.12374.12336 H/W Version : 43777.2 Current : 36 RMA Code : 200-32-32-32 Power supply specific block: Block Signature : 0x0 Block Version Block Length Block Checksum : 0x0 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 283 Configuring the Fabric Extender Verifying the Chassis Management Information Feature Bits : 0x0 Current 110v : 36 Current 220v : 36 Stackmib OID Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 284 Configuring the Fabric Extender Verifying the Chassis Management Information Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1)
  • Page 285 98, 99 community ports LACP 98, 99 community VLANs 56, 57 port channels 98, 99 configuration data LACP 98, 99 configuring LACP graceful convergence 98, 99 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1) IN-1...
  • Page 286 Layer 2 switching Ethernet switching LED beacon Link Aggregation Control Protocol oversubscription See also LACP oversubscription ratio Link Failure 159, 178 detecting unidirectional Link Layer Discovery Protocol, See LLDP Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1) IN-2...
  • Page 287 STP root guard RSTP switchport fex-fabric mode 150, 154, 158, 173 active topology switchport saved configuration BPDU processing designated port, defined designated switch, defined proposal-agreement handshake process type Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1) IN-3...
  • Page 288 Index UDLD version compatibility 12, 14 aggressive mode VLANs defined extended range nonaggressive mode reserved range unicast storms vPC topology Unidirectional Link Detection transparent mode Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)N1(1) IN-4...

Table of Contents