Cisco Nexus 3000 Series Configuration Manual
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Switch
  5. Nexus 3000 series
  6. Configuration manual

Cisco Nexus 3000 Series Configuration Manual

Nx-os layer 2 switching configuration guide, release 6.x
Hide thumbs Also See for Nexus 3000 Series:
Table of Contents

Advertisement

Quick Links

See also: Configuration Manual , Installation Manual
Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration
Guide, Release 6.x
First Published: 2013-04-29
Last Modified: 2018-02-15
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-29545-03

Advertisement

Table of Contents
loading

Related Manuals for Cisco Nexus 3000 Series

Summary of Contents for Cisco Nexus 3000 Series

  • Page 1 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x First Published: 2013-04-29 Last Modified: 2018-02-15 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883...
  • Page 2 Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.

  • Page 3: Table Of Contents

    Adding Ports to a VLAN Triggering the VLAN Membership Consistency Checker Configuring a VLAN as a Routed SVI Configuring a VLAN as a Management SVI Configuring VTP Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 4 Understanding Allowed VLANs Understanding Native 802.1Q VLANs Configuring Access and Trunk Interfaces Configuring a LAN Interface as an Ethernet Access Port Configuring Access Host Ports Configuring Trunk Ports Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 5 Creating the Spanning Tree Topology Understanding Rapid PVST+ Rapid PVST+ Overview Rapid PVST+ BPDUs Proposal and Agreement Handshake Protocol Timers Port Roles Port States Rapid PVST+ Port State Overview Blocking State Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 6 Triggering the VLAN STP State Consistency Checker Configuring Multiple Spanning Tree C H A P T E R 8 Information About MST MST Overview MST Regions MST BPDUs MST Configuration Information Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 7 Configuring the Maximum-Aging Time Configuring the Maximum-Hop Count Configuring PVST Simulation Globally Configuring PVST Simulation Per Port Specifying the Link Type Restarting the Protocol Verifying the MST Configuration Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 8 Information About Global LLDP Commands Configuring LLDP Information About LLDP Management TLV IP Addresses Configuring LLDP Management TLV IP Addresses on an Interface Configuring Interface LLDP MIBs for LLDP Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x viii OL-29545-03...
  • Page 9 Guidelines and Limitations for Traffic Storm Control Default Settings for Traffic Storm Control Configuring Traffic Storm Control Verifying the Traffic Storm Control Configuration Traffic Storm Control Example Configuration Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 10 Contents Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 11: New And Changed Information

    Configuring MAC Action down the port with the lower interface index Move Loop when a MAC address move loop is detected Detection, on page between two ports. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 12 Consistency Checker, on page 13 • Triggering the VLAN STP State Consistency Checker, on page 77 Added for vPC 6.0(2)U1(1) Configuring IGMP Snooping Parameters, on page 138 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 13: Overview

    VLAN must be forwarded through a bridge or a router. All ports are assigned to the default VLAN (VLAN1) when the device comes up. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 14: Private Vlans

    STP protocol. Note Cisco NX-OS uses the extended system ID and MAC address reduction; you cannot disable these features. In addition, Cisco has created some proprietary features to enhance the spanning tree activities. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x...

  • Page 15: Rapid Pvst

    • Root Guard— Root guard prevents a port from becoming a root port or a blocked port. If you configure a port with root guard then the port receives a superior BPDU and it immediately goes to root-inconsistent (blocked) state. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 16 Overview STP Extensions Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 17: Configuring Vlans

    VLAN must be forwarded through a router. The following figure shows VLANs as logical networks. The stations in the engineering department are assigned to one VLAN, Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 18: Vlan Ranges

    VLANs into ranges, and you use each range slightly differently. For information about configuration limits, see the configuration limits documentation for your switch. This table describes the VLAN ranges. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 19: Creating, Deleting, And Modifying Vlans

    Depending on the range of the VLAN, you can configure the following parameters for VLANs (except the default VLAN): • VLAN name • Shutdown or not shutdown Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 20: About The Vlan Trunking Protocol

    • SNMP can perform GET and SET operations on the CISCO-VTP-MIB objects. • VTP server mode and VTP client mode are not supported. The only supported mode is transparent mode, which is the default mode. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 21: Configuring A Vlan

    This example shows how to create a range of VLANs from 15 to 20: switch# configure terminal switch(config)# vlan 15-20 You can also create and delete VLANs in the VLAN configuration submode. Note Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 22: Configuring A Vlan

    VLANs 1006 to 4094. This example shows how to configure optional parameters for VLAN 5: switch# configure terminal switch(config)# vlan 5 switch(config-vlan)# name accounting switch(config-vlan)# state active switch(config-vlan)# no shutdown Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 23: Adding Ports To A Vlan

    2 Checks: Port membership of Vlan Vlan Consistency Check: PASSED Vlan:2, Hardware state consistent for: Ethernet1/18 Ethernet1/20 Ethernet1/29 Ethernet1/30 Ethernet1/31 Ethernet1/32 Ethernet1/33 Ethernet1/34 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 24: Configuring A Vlan As A Routed Svi

    You can configure a VLAN to be a routed switch virtual interface (SVI). Before You Begin • Install the Layer 3 license. For more information, see License and Copyright Information for Cisco NX-OS Software available at the following URL: http://www.cisco.com/en/US/docs/switches/datacenter/ sw/4_0/nx-os/license_agreement/nx-ossw_lisns.html.

  • Page 25: Configuring A Vlan As A Management Svi

    Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Step 2 switch(config)# feature vtp Enables VTP on the device. The default is disabled. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 26 Maximum VLANs supported locally : 1005 Number of existing VLANs : 502 VTP Operating Mode : Transparent VTP Domain Name VTP Pruning Mode : Disabled (Operationally Disabled) VTP V2 Mode : Disabled Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 27: Verifying The Vlan Configuration

    [brief | id [vlan_id | vlan_range] | name name | Displays selected configuration summary ] information for the defined VLAN(s). Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 28 Configuring VLANs Verifying the VLAN Configuration Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 29: Configuring Private Vlans

    VLAN. The secondary VLAN ID differentiates one subdomain from another. The secondary VLANs can either be isolated VLANs or community VLANs. A host on an isolated VLAN can communicate only with Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 30: 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 PVLAN ports are as follows: Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    VLANs in a PVLAN 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 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 32: Associating Primary And Secondary Vlans

    VLAN are brought down. You can associate a secondary VLAN with only one primary VLAN. Note For an association to be operational, the following conditions must be met: Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 33: Broadcast Traffic In Private Vlans

    • Configure interfaces connected to default gateways and selected end stations (for example, backup servers) as promiscuous ports to allow all end stations access to a default gateway. Guidelines and Limitations for Private VLANs When configuring PVLANs, follow these guidelines: Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 34: Configuring A Private Vlan

    Configuring a VLAN as a Private VLAN To create a PVLAN, you first create a VLAN, and then configure that VLAN to be a PVLAN. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    • The secondary-vlan-list parameter can contain multiple community VLAN IDs and one isolated VLAN • Enter a secondary-vlan-list or use the add keyword with a secondary-vlan-list to associate secondary VLANs with a primary VLAN. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    VLANs. Configuring a PVLAN host port involves two steps. First, you define the port as a PVLAN host port and then you configure a host association between the primary and secondary VLANs. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    First, you define the port as a promiscuous port and then you configure the mapping between a secondary VLAN and the primary VLAN. Before You Begin Ensure that the PVLAN feature is enabled. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 38: Configuring A Layer 2 Interface As A Private Vlan Isolated Trunk Port

    You must associate the primary and secondary VLANs before they become operational on the private Note VLAN isolated trunk port. Before You Begin Ensure that the private VLAN feature is enabled. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 39 VLANs to the isolated trunk port, the system switch(config-if)# switchport automatically puts all the primary VLANs into the private-vlan trunk allowed vlan add 1 allowed VLAN list for this port. switch(config-if)# Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 40 VLAN, to pass native VLAN traffic. Do not configure primary VLAN as part Note of allowed VLAN list. Step 7 Enter one of the following commands Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 41 Removes the private private-vlan VLAN association from association trunk the private VLAN [primary-vlan-id isolated trunk port. [secondary-vlan-id]] Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 42 1 switch(config-if)# switchport private-vlan association trunk 10 101 switch(config-if)# switchport private-vlan association trunk 20 201 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 43: Configuring A Layer 2 Interface As A Private Vlan Promiscuous Trunk Port

    Sets the native VLAN for the 802.1Q trunk. Valid values are from 1 to 3968 and 4048 to 4093. The default value is 1. Example: switch(config-if)# switchport private-vlan trunk native vlan 5 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 44 Exits the interface configuration mode. Example: switch(config-if)# exit switch(config)# Step 9 show interface switchport (Optional) Displays information on all interfaces configured as switch ports. Example: switch# show interface switchport Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 45: Configuring Vlan Mapping For Selective Q-In-Q On A Private Vlan Secondary Trunk Port

    The range is from 1 to 4094. You can enter a string of VLAN-IDs. • all—Accepts all the VLAN IDs (C-VLAN) entering the switch from the customer network. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 46: Verifying The Private Vlan Configuration

    Displays the features enabled on the switch. switch# show interface switchport Displays information on all interfaces configured as switch ports. switch# show vlan private-vlan [type] Displays the status of the PVLAN. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 47 This 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 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 48 Configuring Private VLANs Verifying the Private VLAN Configuration Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 49: Chapter 5 Configuring Access And Trunk Interfaces

    • A trunk port can have two or more VLANs configured on the interface; it can carry traffic for several VLANs simultaneously. Cisco NX-OS supports only IEEE 802.1Q-type VLAN trunk encapsulation. Note Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 50: Understanding Ieee 802.1Q Encapsulation

    To correctly deliver the traffic on a trunk port with several VLANs, the device uses the IEEE 802.1Q encapsulation (tagging) method. This tag carries information about the specific VLAN to which the frame Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 51: Understanding Access Vlans

    If you assign an access VLAN that is also a primary VLAN for a private VLAN, all access ports with that Note access VLAN will also receive all the broadcast traffic for the primary VLAN in the private VLAN mode. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    • On the egress side, all traffic is tagged. If traffic belongs to native VLAN it is tagged with the native VLAN ID. This feature is supported on all the directly connected Ethernet and Port Channel interfaces. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 53: Configuring Access And Trunk Interfaces

    Configuring Access and Trunk Interfaces Configuring Access and Trunk Interfaces Cisco NX-OS Release 6.0(2)U2(1) introduces the tx-only option, which allows both tagged and untagged packets at ingress. You can use the vlan dot1q tag native tx-only command to perform the following functions: •...

  • Page 54: Configuring Access Host Ports

    VLAN plus encapsulated, tagged, packets for multiple VLANs. Cisco NX-OS supports only 802.1Q encapsulation. Note Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    You can specify the IDs for the VLANs that are allowed on the specific trunk port. Before you configure the allowed VLANs for the specified trunk ports, ensure that you are configuring the correct interfaces and that the interfaces are trunks. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 56: 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 device. Packets that enter the switch with 802.1Q tags that match the native VLAN ID value are similarly stripped of tagging.

  • Page 57: Verifying The 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 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 58 Configuring Access and Trunk Interfaces Verifying the Interface Configuration Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 59: Configuring Switching Modes

    When store-and-forward switching is enabled, the switch checks each frame for cyclic redundancy check (CRC) errors before forwarding them to the network. Each frame is stored until the entire frame has been received and checked. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 60: Guidelines And Limitations For Switching Modes

    • Packets with frame check sequence (FCS) errors are dropped. • For the Cisco Nexus 3064PQ platform, packets smaller than or equal to 768 bytes are dropped. • For Cisco Nexus 3016, 3064E, 3064X, and 3048 platforms, packets smaller than or equal to 560 bytes are dropped.

  • Page 61: Licensing Requirements For Switching Modes

    Cut-through switching mode and store-and-forward switching modes do not require licenses. Any feature not included in a license package is bundled with the Cisco NX-OS system images and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide.

  • Page 62: Reenabling Cut-Through Switching

    This example shows how to reenable cut-through switching: switch# configure terminal switch(config) # no switching-mode store-forward switch(config) # Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 63: Configuring Rapid Pvst

    STP frames, which are called Bridge Protocol Data Units (BPDUs), at regular intervals. Switches do not forward these frames but use the frames to construct a loop-free path. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 64: Understanding How A Topology Is Created

    Bridge Priority Value The bridge priority is a 4-bit value when the extended system ID is enabled. In Cisco NX-OS, the extended system ID is always enabled; you cannot disable the extended system ID. Note Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x...

  • Page 65: Extended System Id

    4096. Only the following values are possible: • 0 • 4096 • 8192 • 12288 • 16384 • 20480 • 24576 • 28672 • 32768 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 66: Understanding Bpdus

    • A root port is selected. This is the port providing the best path from the bridge to the root bridge. • Ports included in the spanning tree are selected. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 67: Election Of The Root Bridge

    By changing the STP port priority on the fiber-optic port to a higher priority (lower numerical value) than the root port, the fiber-optic port becomes the new root port. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 68: 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 69: 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 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 70: 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 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 71: Protocol Timers

    In a stable topology with consistent port roles throughout the network, Rapid PVST+ ensures that every root port and designated port immediately transition to the forwarding state while all alternate and backup ports Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 72: Port States

    When you enable Rapid PVST+, every port in the software, VLAN, and network goes through the blocking state and the transitory states of learning at power up. If properly configured, each LAN port stabilizes to the forwarding or blocking state. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 73: Blocking State

    A LAN port in the forwarding state forwards frames. The LAN port enters the forwarding state from the learning state. A LAN port in the forwarding state performs as follows: Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 74: Disabled State

    When the switch receives a proposal message on one of its ports and that port is selected as the new root port, Rapid PVST+ forces all other ports to synchronize with the new root information. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 75: Processing Superior Bpdu Information

    Rapid PVST+ sets the port to the blocking state and sends an agreement message. The designated port continues sending BPDUs with the proposal flag set until the forward-delay timer expires. At that time, the port transitions to the forwarding state. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 76: Processing Inferior Bpdu Information

    LAN interface. If a loop occurs, STP considers the port cost when selecting a LAN interface to put into the forwarding state. Table 6: Default Port Cost Bandwidth Short Path-Cost Method of Port Long Path-Cost Method of Port Cost Cost 10 Mbps 2,000,000 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 77: 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 78: Rapid Pvst+ Interoperation With 802.1S Mst

    Once you enable Rapid PVST+ on the switch, you must enable Rapid PVST+ on the specified VLANs. Rapid PVST+ is the default STP mode. You cannot simultaneously run MST and Rapid PVST+. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 79: Enabling Rapid Pvst+ Per Vlan

    2 through 4094 (except reserved VLAN values). Step 3 switch(config)# no (Optional) spanning-tree vlan-range Disables Rapid PVST+ on the specified VLAN. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 80: Configuring The Root Bridge Id

    STP convergence time. You can enter the hello-time keyword to override the automatically calculated hello time. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 81: Configuring A Secondary Root Bridge

    With the switch configured as the root bridge, do not manually configure the hello time, forward-delay Note time, and maximum-age time using the spanning-tree mst hello-time, spanning-tree mst forward-time, and spanning-tree mst max-age global configuration commands. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 82: Configuring The Rapid Pvst+ Port Priority

    This example shows how to configure the access port priority of an Ethernet interface: switch# configure terminal switch(config)# interface ethernet 1/4 switch(config-if)# spanning-tree port-priority 160 You can only apply this command to a physical Ethernet interface. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 83: Configuring The Rapid Pvst+ Path-Cost Method And Port Cost

    You can only apply this command to a physical Ethernet interface. Configuring the Rapid PVST+ Bridge Priority of a VLAN You can configure the Rapid PVST+ bridge priority of a VLAN. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    1 to 10 seconds. The default is 2 seconds. This example shows how to configure the hello time for a VLAN: switch# configure terminal switch(config)# spanning-tree vlan 5 hello-time 7 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    If you have a half-duplex link physically connected point-to-point to a single port on a remote switch, you can override the default setting on the link type and enable rapid transitions. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 86: Restarting The Protocol

    Verifying the Rapid PVST+ Configuration Use the following commands to display Rapid PVST+ configuration information. Command Purpose show running-config spanning-tree [all] Displays the current spanning tree configuration. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 87: Triggering The Vlan Stp State Consistency Checker

    Checks: Spanning tree state Consistency Check: PASSED Vlan:250, Hardware state consistent for: Ethernet1/4 Ethernet1/5 Ethernet1/6 Ethernet1/18 Ethernet1/20 Ethernet1/29 Ethernet1/30 Ethernet1/31 Ethernet1/32 Ethernet1/33 Ethernet1/34 Ethernet1/35 Ethernet1/36 Ethernet1/37 Ethernet1/38 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 88 Configuring Rapid PVST+ Triggering the VLAN STP State Consistency Checker Ethernet1/39 Ethernet1/40 Ethernet1/41 Ethernet1/42 Ethernet1/43 Ethernet1/44 Ethernet1/45 Ethernet1/46 Ethernet1/47 Ethernet1/48 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 89: Configuring Multiple Spanning Tree

    • Rapid per-VLAN spanning tree (Rapid PVST+) IEEE 802.1w defined the Rapid Spanning Tree Protocol (RSTP) and was incorporated into IEEE 802.1D. • IEEE 802.1s defined MST and was incorporated into IEEE 802.1Q. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 90: Mst Regions

    BPDU that the IST sends. Because the MST BPDU carries information for all instances, the number of BPDUs that need to be processed to support MSTIs is significantly reduced. Figure 13: MST BPDU with M-Records for MSTIs Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 91: Mst Configuration Information

    An MSTI is local to the region; for example, MSTI 9 in region A is independent of MSTI 9 in region B, even if regions A and B are interconnected. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 92: Spanning Tree Operation Within An Mst Region

    The root of the subtree is the CIST regional root. The MST region appears as a virtual switch to adjacent STP switches and MST regions. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 93: Mst Terminology

    The MST terminology is as follows: • The CIST root is the root bridge for the CIST, which is the unique instance that spans the whole network. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 94: Hop Count

    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 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 95: Spanning-Tree Dispute Mechanism

    Switch A blocks (or keeps blocking) its port, which prevents the bridging loop. The block is shown as an STP dispute. Figure 16: Detecting a Unidirectional Link Failure Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 96: Port Cost And Port Priority

    MST configuration. MST interoperates with the Cisco prestandard Multiple Spanning Tree Protocol (MSTP) whenever it Note receives prestandard MSTP on an MST port; no explicit configuration is necessary.

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

    You must enable MST; Rapid PVST+ is the default. 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. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 98: Entering Mst Configuration Mode

    Enters MST configuration mode on the system. You must be in mst configuration the MST configuration mode to assign the MST configuration parameters, as follows: • MST name • Instance-to-VLAN mapping Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 99: Specifying The Mst Name

    The default is an empty string. This example shows how to set the name of the MST region: switch# configure terminal switch(config)# spanning-tree mst configuration switch(config-mst)# name accounting Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 100: Specifying The Mst Configuration Revision Number

    Maps VLANs to an MST instance as follows: instance-id vlan vlan-range • For instance-id , the range is from 1 to 4094. • For vlan vlan-range , the range is from 1 to 4094. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 101 1 vlan 10-20 switch(config-mst)# name region1 switch(config-mst)# revision 1 switch(config-mst)# show pending Pending MST configuration Name [region1] Revision Instances configured 2 Instance Vlans Mapped -------- --------------------- 1-9,21-4094 10-20 ------------------------------- Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 102: Mapping And Unmapping Vlans To Mst Instances

    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. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 103: Configuring The Root Bridge

    Step 1 switch# configure terminal Enters global configuration mode. Step 2 switch(config)# spanning-tree Configures a switch as the root bridge as follows: mst instance-id root {primary | Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 104: Configuring A Secondary Root Bridge

    • For hello-time seconds, specify the interval in seconds between the generation of configuration messages by the root bridge. The range is from 1 to 10 seconds; the default is 2 seconds. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 105: Configuring The Port Priority

    This example shows how to set the MST interface port priority for MSTI 3 on Ethernet port 3/1 to 64: switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# spanning-tree mst 3 port-priority 64 You can only apply this command to a physical Ethernet interface. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 106: Configuring The Port Cost

    Configuring the Switch Priority You can configure the switch priority for an MST instance so that it is more likely that the specified switch is chosen as the root bridge. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 107: Configuring The Hello Time

    Enters global configuration mode. Step 2 switch(config)# spanning-tree mst Configures the hello time for all MST instances. The hello hello-time seconds time is the interval between the generation of configuration Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 108: 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). Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 109: Configuring The Maximum-Hop Count

    You can block this automatic feature either globally or per port. You can enter the global command and change the PVST simulation setting for the entire switch while you are in interface command mode. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 110: Configuring Pvst Simulation Per Port

    Sets the interface to the switch-wide MST and Rapid mst simulate pvst PVST+ interoperation that you configured using the spanning-tree mst simulate pvst global command. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 111: Specifying The Link Type

    Enter this command to restart the protocol negotiation (force the renegotiation with neighboring switches) on the entire switch or on specified interfaces. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 112: Verifying The Mst Configuration

    This example shows how to display the 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 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 113: Chapter 9 Configuring Stp Extensions

    Information About STP Extensions Overview Cisco has added extensions to Spanning Tree Protocol (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. All of these extensions can be used with both RPVST+ and Multiple Spanning Tree Protocol (MST).

  • Page 114: Spanning Tree Edge Ports

    Once that port receives a BPDU, it resumes the normal spanning tree transitions. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 115: Understanding Bpdu Guard

    If the port configuration is not set to default BPDU Filtering, the edge configuration does not affect BPDU Filtering. The following table lists all the BPDU Filtering combinations. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 116: Understanding Loop Guard

    Loop Guard is useful only in switched networks where devices are connected by point-to-point links. On a point-to-point link, a designated bridge cannot disappear unless it sends an inferior BPDU or brings the link down. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 117: Understanding Root Guard

    • Loop Guard does not run on spanning tree edge ports. • Enabling Loop Guard on ports that are not connected to a point-to-point link will not work. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 118: Configuring Spanning Tree Port Types Globally

    This example shows how to configure all access and trunk ports connected to hosts as spanning tree edge ports: switch# configure terminal switch(config)# spanning-tree port type edge default Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    Edge ports immediately transition to the forwarding state without passing through the blocking or learning state at linkup. By default, spanning tree ports are normal port types. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    Configures the specified interfaces to be spanning network ports. If you enable Bridge Assurance, it automatically port type network runs on network ports. By default, spanning tree ports are normal port types. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 121: 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. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 122: Enabling Bpdu Filtering Globally

    BPDU Filtering is disabled. Before You Begin Ensure that STP is configured. Ensure that you have configured some spanning tree edge ports. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 123: Enabling Bpdu Filtering On Specified Interfaces

    When you enable BPDU Filtering locally on a port, this feature prevents the device from receiving or Note sending BPDUs on this port. Before You Begin Ensure that STP is configured. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 124: Enabling Loop Guard Globally

    Ensure that you have spanning tree normal ports or have configured some network ports. Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

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

    By default, Root Guard is disabled by default, and Loop Guard on specified ports is also disabled. Note Loop Guard runs only on spanning tree normal and network interfaces. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 126: Verifying The Stp Extension Configuration

    Nexus 3000 Series switches. If the Cisco Nexus 3000 Series switch displays the following message, it indicates that the switch receives frames with the same source MAC address on these two interfaces and that the switch learns the same MAC address on these interfaces at a very high speed.

  • Page 127: Generating Syslog Error Messages

    In order to check if the MAC addresses move, enter the command: # show mac address-table notification mac-move MAC Move Notify Triggers: 1206 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 128 By default, dynamic learning is reenabled after 180 seconds. At that point, any STP disputes or inconsistencies should be resolved. If not, the dynamic learning is disabled again. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 129: Chapter 1 0 Configuring Lldp

    • Management address TLV • Port description TLV • Port VLAN ID TLV (IEEE 802.1 organizationally specific TLVs) • System capabilities TLV • System description TLV • System name TLV Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 130: Configuring Lldp

    Use the port-description option to specify the port description TLV messages. Use the port-vlan option to specify the port VLAN ID TLV messages. Use the system-capabilities option to specify the system capabilities TLV messages. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 131: Information About Lldp Management Tlv Ip Addresses

    LLDP management IPv4 address configured on the port is used in the management TLV of the LLDP protocol data unit (PDU) to be sent. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 132 IPv6 address. This process follows the rules applied while selecting a management address to be sent in the LLDP management TLV for IPv4 and for IPv6. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 133: Configuring Lldp Management Tlv Ip Addresses On An Interface

    0dc3:0dc3:0000:0000:0218:baff:fed8:239d ipv6 This example shows how to specify the VLAN ID in the management TLV: switch# configure terminal switch(config)# interface ethernet 1/8 switch(config-if)# lldp tlv-set vlan 10 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 134: Configuring Interface Lldp

    This example shows how to display the interface details about LLDP neighbors: switch(config-if)# show lldp neighbor interface ethernet 1/4 detail Capability codes: (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 135: Mibs For Lldp

    Total frames received in error: 2 Total frames discarded: 2 Total TLVs unrecognized: 0 MIBs for LLDP MIB Link LLDP-MIB To locate and download MIBs, go to the following URL: http://www.cisco.com/public/sw-center/netmgmt/ cmtk/mibs.shtml Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 136 Configuring LLDP MIBs for LLDP Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 137: Configuring Mac Address Tables

    The switch uses an aging mechanism, defined by a configurable aging timer, so if an address remains inactive for a specified number of seconds, it is removed from the address table. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 138: Guidelines For Configuring The Mac Address Tables

    You can detect and limit the number of times that a MAC address moves from one port to another. This movement of MAC addresses between ports can cause loops. Until Cisco NX-OS Release 6.0(2)U3(1), when a loop was detected between two ports, MAC learning was disabled for 180 seconds. You can now configure the action of bringing down the port with the lower interface index when such a loop is detected by using the mac address-table loop-detect port-down command.

  • Page 139: Configuring The Aging Time For The Mac Table

    MAC table. MAC aging time can be configured in either interface configuration mode or in VLAN configuration mode. If the Cisco Nexus device is used as a Layer 2 or Layer 3 termination switch, Cisco recommends that you Note set the mac-address-table aging-time to 1800 (higher than the default ARP aging time of 1500 seconds) on all VLANs.

  • Page 140: Configuring Mac Move Loop Detection

    Configuring MAC Move Loop Detection When the number of MAC address moves between two ports exceeds a threshold, it forms a loop. Until Cisco NX-OS Release 6.0(2)U3(1), when a loop was detected between two ports, MAC learning was disabled for 180 seconds.

  • Page 141: Clearing Dynamic Addresses From The Mac Table

    Verifying the MAC Address Configuration Note On Cisco Nexus 3000 and Cisco Nexus 3548 Series platforms, the self router MAC or HSRP VMAC are dynamically learned by the switch under the following condition: • When there is a transient loop in the network due to which the switch receives its own packets.

  • Page 142: Triggering The Layer 2 Consistency Checker

    MAC addresses that are configured in the hardware, but not in the software. To manually trigger the Layer 2 consistency checker and display the results, use the following command in any mode: Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 143 Secure NTFY Ports ---------+-----------------+--------+---------+------+----+------------------ 0100.0100.0106 dynamic 0200.0100.0125 static Extra and Discrepant entries in the MAC Table VLAN MAC Address Type Secure NTFY Ports ---------+-----------------+--------+---------+------+----+------------------ 0000.0100.0109 dynamic Eth1/41 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 144 Configuring MAC Address Tables Triggering the Layer 2 Consistency Checker Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 145: C H A P T E

    Layer 2 forwarding decisions. Cisco NX-OS supports IGMPv2 and IGMPv3. IGMPv2 supports IGMPv1, and IGMPv3 supports IGMPv2. Although not all features of an earlier version of IGMP are supported, the features related to membership query and membership report messages are supported for all IGMP versions.

  • Page 146: 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 the last member query interval when you enable the fast leave Note feature because it does not check for remaining hosts.

  • Page 147: Igmpv3

    IGMP Forwarding The control plane of the Cisco Nexus device 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 148: Configuring Igmp Snooping Parameters

    The default is enabled. Multicast router Configures a static connection to a multicast router. The interface to the router must be in the selected VLAN. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 149 Supports IGMPv2 hosts that cannot be explicitly tracked because of the host report suppression mechanism of the snooping fast-leave IGMPv2 protocol. When you enable fast leave, the IGMP Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 150: Verifying The Igmp Snooping Configuration

    [[vlan] vlan-id] Displays IGMP snooping configuration by VLAN. show ip igmp snooping groups [[vlan] vlan-id] Displays IGMP snooping information about groups [detail] by VLAN. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 151 Switch-querier enabled, address 192.0.2.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 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 152 Configuring IGMP Snooping Verifying the IGMP Snooping Configuration Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 153: Chapter 1 3 Configuring Traffic Storm Control

    When the ingress traffic reaches the traffic storm control level that is configured on the port, traffic storm control drops the traffic until the interval ends. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 154 • Shut down—When ingress traffic exceeds the traffic storm control level that is configured on a port, traffic storm control puts the port into the error-disabled state. To reenable this port, you can use either Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 155: Guidelines And Limitations For Traffic Storm Control

    You can control the number of traps generated per minute by using the snmp-server enable traps storm-control trap-rate command. By default, Cisco NX-OS takes no corrective action when traffic exceeds the configured level. Guidelines and Limitations for Traffic Storm Control When configuring the traffic storm control level, follow these guidelines and limitations: •...

  • Page 156: Default Settings For Traffic Storm Control

    This example shows how to configure traffic storm control for port channels 122 and 123: switch# configure terminal switch(config)# interface port-channel 122, port-channel 123 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 157: Verifying The Traffic Storm Control Configuration

    5.23 storm-control multicast level 0.50 storm-control unicast level 1.23 storm-control action shutdown storm-control action trap Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...

  • Page 158: Traffic Storm Control Example Configuration

    40 This example shows how to specify the number of Storm Control traps per minute: switch# configure terminal switch(config)# snmp-server enable traps storm-control trap-rate 100 switch(config)# Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03...
  • Page 159 IEEE 802.1w cut-through mode IGMP licensing snooping parameters, configuring cut-through switching IGMP forwarding 49, 51, 52 default settings IGMP snooping enabling queries information about IGMPv1 IGMPv3 Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03 IN-1...
  • Page 160 RSTP 58, 61, 65, 79 mapping VLANs to MST instance active topology MST region 79, 80, 81, 83 BPDU CIST processing Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x IN-2 OL-29545-03...
  • Page 161 SVIs switchport 29, 33 usable VLANs switchport mode private-vlan trunk allowed vlan switchport mode private-vlan trunk promiscuous mode switchport mode private-vlan trunk secondary Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x OL-29545-03 IN-3...
  • Page 162 Index Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x IN-4 OL-29545-03...

Table of Contents