hit counter script
Cisco Nexus 6000 Series Configuration Manual

Cisco Nexus 6000 Series Configuration Manual

Nx-os layer 2 guide
Hide thumbs Also See for Nexus 6000 Series:
Table of Contents

Advertisement

Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration
Guide, Release 7.x
First Published: 2014-01-15
Last Modified: 2016-01-28
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

Advertisement

Table of Contents
loading

Summary of Contents for Cisco Nexus 6000 Series

  • Page 1 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x First Published: 2014-01-15 Last Modified: 2016-01-28 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

    C H A P T E R 3 Information About VLANs Understanding VLANs Understanding VLAN Ranges Creating, Deleting, and Modifying VLANs About the VLAN Trunking Protocol Guidelines and Limitations for VTP Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 4 Configuring an Interface as a Private VLAN Promiscuous Port 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 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 5 Processing Superior BPDU Information Processing Inferior BPDU Information Spanning-Tree Dispute Mechanism Port Cost Port Priority Rapid PVST+ and IEEE 802.1Q Trunks Rapid PVST+ Interoperation with Legacy 802.1D STP Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 6 Hop Count Boundary Ports Spanning-Tree Dispute Mechanism Port Cost and Port Priority Interoperability with IEEE 802.1D Interoperability with Rapid PVST+: Understanding PVST Simulation Configuring MST MST Configuration Guidelines Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 7 Spanning Tree Edge Ports Spanning Tree Network Ports Spanning Tree Normal Ports Understanding Bridge Assurance Understanding BPDU Guard Understanding BPDU Filtering Understanding Loop Guard Understanding Root Guard Configuring STP Extensions Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 8 Verifying RMAC Learning Feature Configuring IGMP Snooping C H A P T E R 1 0 Information About IGMP Snooping IGMPv1 and IGMPv2 IGMPv3 IGMP Snooping Querier IGMP Forwarding Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x viii...
  • Page 9 Guidelines and Limitations for Traffic Storm Control Configuring Traffic Storm Control Verifying the Traffic Storm Control Configuration Traffic Storm Control Example Configuration Default Settings for Traffic Storm Control Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 10 Associating a Fabric Extender to an Ethernet Interface Associating a Fabric Extender to a Port Channel Disassociating a Fabric Extender from an Interface Configuring Fabric Extender Global Features Enabling the Fabric Extender Locator LED Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 11 Configuring an SVS Connection to the vCenter Server Activating an SVS Connection to the vCenter Server Verifying the VM-FEX Configuration Verifying the Status of the Virtual Interfaces Verifying the Connection to the vCenter Server Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 12 Enabling VN-Segment Configuring VN-Segment for a VLAN Configuring VN-Segment for VLAN in Configure Sync Configuring VN-Segment in Transit Mode Configuring VN-Segment in Non-Transit Mode Disabling VN-Segment Verifying VN-Segment Configuration Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 13: Preface

    Obtaining Documentation and Submitting a Service Request, page xvii Audience This publication is for network administrators who configure and maintain Cisco Nexus devices. Document Conventions As part of our constant endeavor to remodel our documents to meet our customers' requirements, we have Note modified the manner in which we document configuration tasks.
  • Page 14 Means reader take note. Notes contain helpful suggestions or references to material not covered in the Note manual. Means reader be careful. In this situation, you might do something that could result in equipment damage Caution or loss of data. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 15: Related Documentation For Cisco Nexus 6000 Series Nx-Os Software

    Related Documentation for Cisco Nexus 6000 Series NX-OS Software Related Documentation for Cisco Nexus 6000 Series NX-OS Software The entire Cisco NX-OS 6000 Series documentation set is available at the following URL: http://www.cisco.com/en/US/products/ps12806/tsd_products_support_series_home.html Release Notes The release notes are available at the following URL: http://www.cisco.com/c/en/us/support/switches/nexus-6000-series-switches/products-release-notes-list.html...
  • Page 16: Documentation Feedback

    The Cisco Nexus 6000 Series NX-OS MIB Reference is available at http://www.cisco.com/en/US/docs/switches/ datacenter/nexus6000/sw/mib/reference/NX6000_MIBRef.html. Error and System Messages The Cisco Nexus 6000 Series NX-OS System Message Guide is available at http://www.cisco.com/c/en/us/td/ docs/switches/datacenter/nexus6000/sw/system_messages/reference/sl_nxos_book.html. Troubleshooting Guide The Cisco Nexus 6000 Series NX-OS Troubleshooting Guide is available at http://www.cisco.com/c/en/us/...
  • Page 17: Obtaining Documentation And Submitting A Service Request

    What's New in Cisco Product Documentation. To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.
  • Page 18 Preface Obtaining Documentation and Submitting a Service Request Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x xviii...
  • Page 19: New And Changed Information

    7.1(0)N1(1) Cisco Nexus VLAN Translation Configuring 5500, 5600, and VLANs 6000 Series Switches 7.3(0)N1(1) Cisco Nexus VLAN Long Name support Configuring 5500, 5600, and VLANs 6000 Series Switches Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 20 New and Changed Information New and Changed Information Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 21: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 22: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 23: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 24 Overview STP Extensions Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 25: Configuring Vlans

    VLAN. Each VLAN is considered a logical network. If a packet destination address does not belong to the VLAN, it must be forwarded through a router. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 26: Understanding Vlan Ranges

    This process has the effect of partitioning VTP domains if other switches have VTP turned on. Understanding VLAN Ranges The Cisco Nexus device supports VLAN numbers 1 to 4094 in accordance with the IEEE 802.1Q standard. These VLANs are organized into ranges. The switch is physically limited in the number of VLANs it can support.
  • Page 27: Creating, Deleting, And Modifying Vlans

    You cannot configure the internally allocated VLANs (reserved VLANs). Note Cisco NX-OS allocates a group of 82 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 4049 for internal use.
  • Page 28: About The Vlan Trunking Protocol

    • The show running-configuration command does not show VLAN or VTP configuration information for VLANs 1 to 1000. • Private VLANs (PVLANs) are supported only when the switch is in transparent mode. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 29: About Vlan Translation

    This is a scenario where VLAN translation would be useful to merge the two Layer 2 domains without actually changing their VLAN number. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 30 About VLAN Translation This document describes the functionality of the VLAN translation feature on NX-OS and its interaction with other features on the Cisco Nexus device. The following diagram shows a possible datacenter application for VLAN translation. Figure 2: DC VLAN Translation The first datacenter on the left has an engineering VLAN with number 100 and a marketing VLAN with number 200.
  • Page 31: Guidelines And Limitations For Configuring Vlans

    About VLAN Translation machines in the first datacenter, the core Cisco Nexus device in the second datacenter must translate the VLAN ID in the ingress packets on the trunk port from the ingress VLAN 100 to the local VLAN 101. The local VLAN tag is a function of the port on which the traffic arrives and the ingress VLAN tag on which it arrives.
  • Page 32 TLV VLAN should be mapped to translate VLAN and check for consistency. Spanning tree instance 101 of SW1 is merged with spanning tree instance 202 of SW2. The same process is Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 33: Configuring A Vlan

    {vlan-id | vlan-range} or the internally allocated VLANs. This example shows how to create a range of VLANs from 15 to 20: switch# configure terminal switch(config)# vlan 15-20 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 34: Configuring Vlan Long-Name

    VTP, see the Configuring VTP chapter. Beginning with Cisco NX-OS Release 7.3(0)N1(1), the length of VLAN name that you can configure is increased from 32 to 128 characters. In the earlier release version, you could configure the length of VLAN name up to 32 characters.
  • Page 35: Changing The Range Of Reserved Vlans

    To change the range of reserved VLANs, you must be in global configuration mode. After entering this command, you must do the following tasks: • Enter the copy running-config startup-config command • Reload the device Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 36 This requires copy running-config to startup-config before switch reload. Creating VLANs within this range is not allowed. switch(config)# You must reload the device for this change to take effect. Note Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 37: Configuring A Vlan

    (Optional) shutdown Enables the VLAN. The default value is no shutdown (or enabled). You cannot shut down the default VLAN, VLAN1, or VLANs 1006 to 4094. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 38: Adding Ports To A Vlan

    Enables VTP on the device. The default is disabled. Step 3 switch(config)# vtp domain Specifies the name of the VTP domain that you want this device to join. The default is blank. domain-name Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 39 ---------------------- VTP Version : 2 (capable) Configuration Revision Maximum VLANs supported locally : 1005 Number of existing VLANs : 502 VTP Operating Mode : Transparent VTP Domain Name Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 40: Configuring Vlan Translation On A Trunk Port

    VLAN ID gets mapped to the original VLAN ID before leaving the switch port. This method of VLAN mapping is a two-way mapping. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 41: Configuring Vlan Translation With A Fex

    The vlan-list must include the translated VLANs that need to be translated on a FEX trunk interface. Note Before You Begin • Ensure that all operational FEX interfaces are configured as Layer 2 trunk ports. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 42 This example shows how to configure VLAN translation with a FEX. switch# configure terminal switch(config)# interface ethernet1/1 switch(config-if)# channel-group 100 switch(config-if)# exit switch(config)# interface Po100 switch(config-if)# switchport mode fex-fabric switch(config-if)# switchport vlan map 10 20 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 43: Verifying The Vlan Configuration

    VLAN(s). Feature History for Configuring VLANs This table lists the release history for this feature. The feature history table is added/updated in this guide from Cisco Nexus Release 7.3(0)N1(1) Note onwards. Table 2: Feature History for Configuring VLANs...
  • Page 44 Configuring VLANs Feature History for Configuring VLANs Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 45: Configuring Private Vlans

    VLAN is deleted and re-created. Note that this earlier association cannot be removed by using the no private-vlan association command. It can be removed only by performing either of the following tasks: ◦ Disable the PVLAN feature. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 46: Information About Private Vlans

    A private VLAN domain has only one primary VLAN. Each port in a private VLAN domain is a member of the primary VLAN; the primary VLAN is the entire private VLAN domain. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 47: Associating Secondary Vlans With A Primary Private Vlan

    VLANs or in any isolated VLANs at the Layer 2 level. Baseboard Ports and HIF Ports The following figure shows the baseboard and host interface (HIF) ports on a Cisco Nexus switch. Baseboard ports are ports on a baseboard module in a Cisco Nexus switch.
  • Page 48: Private Vlan Ports

    VLAN. Each promiscuous port can have several secondary VLANs or no secondary VLANs that are associated to that port. You can associate a secondary VLAN Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 49: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 50: Associating Primary And Secondary Vlans

    To allow host ports in secondary VLANs to communicate outside the PVLAN, 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 51: Private Vlan Promiscuous Trunks

    VLAN tag. Isolated trunk ports are intended to be connected to host servers. To support isolated PVLAN ports on a Cisco Nexus Fabric Extender, the Cisco Nexus device must prevent communication between the isolated ports on the FEX; all forwarding occurs through the switch.
  • Page 52: Broadcast Traffic In Private Vlans

    The PVLAN commands do not appear until you enable the PVLAN feature. Note Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Step 2 switch(config)# feature private-vlan Enables the PVLAN feature on the switch. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 53: Configuring A Vlan As A Private Vlan

    The following example shows how to assign VLAN 100 to a PVLAN as a community VLAN: switch# configure terminal switch(config)# vlan 100 switch(config-vlan)# private-vlan community Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 54: Configuring An Interface As A Private Vlan Host Port

    This example shows how to configure Ethernet port 1/12 as a host port for a PVLAN and associate it to primary VLAN 5 and secondary VLAN 101: switch# configure terminal switch(config)# interface ethernet 1/12 switch(config-if)# switchport switch(config-if)# switchport mode private-vlan host switch(config-if)# switchport private-vlan host-association 5 101 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 55: Configuring An Interface As A Private Vlan Promiscuous Port

    The following example shows how to configure Ethernet interface 1/4 as a promiscuous port associated with primary VLAN 5 and secondary VLAN 200: switch# configure terminal switch(config)# interface ethernet 1/4 switch(config-if)# switchport Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 56: Configuring A Promiscuous Trunk Port

    Maps the trunk port with the primary and secondary VLANs of a PVLAN. The secondary VLAN can be either an isolated private-vlan mapping trunk {primary-vlan-id} or community VLAN. {secondary-vlan-id} Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 57: Configuring An Isolated Trunk Port

    Configures the port as a secondary trunk port for a PVLAN. private-vlan trunk [secondary] Note The secondary keyword is assumed if it is not present. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 58: Configuring The Allowed Vlans For Pvlan Trunking Ports

    The primary VLANs do not need to be explicitly added to the allowed VLAN list. They are added automatically once there is a mapping between primary and secondary VLANs. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 59: Configuring Native 802.1Q Vlans On Private Vlans

    VLAN 1. private-vlan trunk native {vlan vlan-id} Step 5 switch(config-if)# no switchport (Optional) private-vlan trunk native {vlan Removes the native VLAN ID from the PVLAN trunk. vlan-id} Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 60: Verifying The Private Vlan Configuration

    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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 61: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 62: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 63: Extended System Id

    4096. Only the following values are possible: • 0 • 4096 • 8192 • 12288 • 16384 • 20480 • 24576 • 28672 • 32768 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 64: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 65: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 66: 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 67: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 68: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 69: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 70: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 71: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 72: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 73: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 74: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 75: 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 76: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 77: Enabling Rapid Pvst+ Per Vlan

    Enables Rapid PVST+ (default STP) on a per VLAN basis. The spanning-tree vlan-range vlan-range value can be 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 78: Configuring The Root Bridge Id

    STP convergence time. You can enter the hello-time keyword to override the automatically calculated hello time. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 79: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 80: Configuring The Rapid Pvst+ Port Priority

    The default value is 128. 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 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 81: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 82: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 83: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 84: Restarting The Protocol

    This example shows how to restart Rapid PVST+ on an Ethernet interface: switch# clear spanning-tree detected-protocol interface ethernet 1/8 Verifying the Rapid PVST+ Configuration Use the following commands to display Rapid PVST+ configuration information. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 85 Hello Time Max Age 20 sec Forward Delay 15 sec Interface Role Sts Cost Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Eth1/3 Root FWD 2 128.131 P2p Peer(STP) Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 86 Configuring Rapid PVST+ Verifying the Rapid PVST+ Configuration Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 87: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 88: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 89: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 90: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 91: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 92: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 93: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 94: 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 95: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 96: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 97: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 98: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 99 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 100: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 101: Configuring The Root Bridge

    Purpose 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 102: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 103: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 104: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 105: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 106: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 107: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 108: Configuring Pvst Simulation Per Port

    By default, all interfaces on the switch operate seamlessly between Rapid PVST+ and MST. Step 4 switch(config-if)# spanning-tree mst Reenables the seamless operation between MST and Rapid PVST+ on specified interfaces. simulate pvst Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 109: Specifying The Link Type

    This example shows how to configure the link type as point to point: switch# configure terminal switch (config)# interface ethernet 1/4 switch(config-if)# spanning-tree link-type point-to-point Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 110: Restarting The Protocol

    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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 111: Chapter 7 Configuring Stp Extensions

    Overview, page 93 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 112: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 113: Understanding Bpdu Filtering

    EnabledThe port transmits at least 10 BPDUs. If this port receives any BPDUs, the port returns to the spanning tree normal port state and BPDU Filtering is disabled. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 114: Understanding Loop Guard

    You can enable Loop Guard on a per-port basis. When you enable Loop Guard on a port, it is automatically applied to all of the active instances or VLANs to which that port belongs. When you disable Loop Guard, it is disabled for the specified ports. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 115: Understanding Root Guard

    These ports can be connected to any type of device. You can configure the port type either globally or per interface. By default, the spanning tree port type is normal. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 116: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 117: Configuring Spanning Tree Network Ports On Specified Interfaces

    • spanning-tree port type network—This command explicitly configures the port as a network port. If you enable Bridge Assurance globally, it automatically runs on a spanning tree network port. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 118: Enabling Bpdu Guard Globally

    You can enable BPDU Guard globally by default. In this condition, the system shuts down an edge port that receives a BPDU. We recommend that you enable BPDU Guard on all edge ports. Note Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 119: Enabling Bpdu Guard On Specified Interfaces

    Specifies the interface to configure, and enters the interface slot/port configuration mode. If this is a 10G breakout port, the slot/port syntax Note is QSFP-module/port. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 120: Enabling Bpdu Filtering Globally

    Ensure that STP is configured. Ensure that you have configured some spanning tree edge ports. Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 121: Enabling Bpdu Filtering On Specified Interfaces

    Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Step 2 switch(config)# interface type Specifies the interface to configure, and enters the interface slot/port configuration mode. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 122: Enabling Loop Guard Globally

    Enters global configuration mode. Step 2 switch(config)# spanning-tree Enables Loop Guard by default on all spanning tree loopguard default normal and network ports. By default, global Loop Guard is disabled. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 123: Enabling Loop Guard Or Root Guard On Specified Interfaces

    You can configure the number of seconds between generation of the config Bridge Protocol Data Units (BPDUs) for FEX ports when they are connected to Cisco Nexus devices. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 124: Verifying The Stp Extension Configuration

    Configuring STP Extensions Verifying the STP Extension Configuration Before You Begin Enter the spanning-tree bpdufilter disable command if the FEX ports are connected to a Cisco Nexus device. Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode.
  • Page 125: Chapter 8 Configuring Lldp

    The default is enabled to send and receive all TLVs. Use the dcbxp option to specify the Data Center Ethernet Parameter Exchange (DCBXP) TLV messages. Use the management-address option to specify the management address TLV messages. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 126: Configuring Interface Lldp

    Step 3 switch(config-if)# [no] lldp {receive | Sets the selected interface to either receive or transmit} transmit. The no form of the command disables the LLDP transmit or receive. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 127 LLDP TLV type:END of LLDPDU LLDP TLV Length: 0 This example shows how to display the system details about LLDP neighbors: switch# sh lldp neighbors system-detail Capability codes: Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 128 LLDP traffic statistics: 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 129: Configuring Mac Address Tables

    RMAC Learning Starting with Cisco NX-OS Release 7.2(0)N1(1), the RMAC Learning feature is supported on Cisco Nexus 5600 and 6000 series switches. This feature allows the default MAC address (RMAC) of a VLAN interface to be dynamically learned on another VLAN over a bridged interface on the switch.
  • Page 130: Configuring Mac Addresses

    Enters global configuration mode. Step 2 switch(config)# mac Specifies the time before an entry ages out and is discarded from the MAC address table. address-table aging-time seconds [vlan vlan_id] Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 131: 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. From Cisco NX-OS release 6.0(2)N2(1), you can 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 132: Clearing Dynamic Addresses From The Mac Table

    Displays the MAC address aging time for all VLANs defined in the switch. show mac address-table Displays the contents of the MAC address table. Note IGMP snooping learned MAC addresses are not displayed. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 133: Verifying Rmac Learning Feature

    * - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC age - seconds since last seen,+ - primary entry using vPC Peer-Link VLAN MAC Address Type Secure NTFY Ports/SWID.SSID.LID ---------+-----------------+--------+---------+------+----+------------------ 002a.6aca.b6bc dynamic Eth1/33 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 134 Configuring MAC Address Tables Verifying RMAC Learning Feature Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 135: 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 136: 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 137: Igmp Snooping Querier

    IGMP Forwarding The Cisco Nexus device supports snooping based on (S,G)/(*,G) IP addresses. Multicast MAC aliasing does not apply for Cisco Nexus devices and the snooped entries are programmed in the FIB tables and not in MAC table. 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 138: Configuring Igmp Snooping Parameters

    IGMP reports are sent as is to multicast-capable routers. 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 139 IGMPv2 protocol. When you enable fast leave, the IGMP software assumes that no more than one host is present on each VLAN port. The default is disabled for all VLANs. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 140: Verifying The Igmp Snooping Configuration

    1/10 switch(config-vlan)# ip igmp snooping static-group 230.0.0.1 interface ethernet 1/10 switch(config-vlan)# end Verifying the IGMP Snooping Configuration Use the following commands to verify the IGMP snooping configuration. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 141 Uptime Last-Join Expires Reports */225.1.1.69 Eth1/43 10.1.1.2 00:00:02 00:00:02 00:04:17 */225.1.1.70 Eth1/43 10.1.1.2 00:00:02 00:00:02 00:04:17 */225.1.1.71 Eth1/43 10.1.1.2 00:00:02 00:00:02 00:04:17 */225.1.1.72 Eth1/43 10.1.1.2 00:00:02 00:00:02 00:04:17 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 142 00:00:02 00:00:02 00:04:17 */225.1.1.75 Eth1/43 10.1.1.2 00:00:02 00:00:02 00:04:17 */225.1.1.76 Eth1/43 10.1.1.2 00:00:02 00:00:02 00:04:17 */225.1.1.77 Eth1/43 10.1.1.2 00:00:02 00:00:02 00:04:17 */225.1.1.78 Eth1/43 10.1.1.2 00:00:02 00:00:02 00:04:17 switch#: Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 143: Configuring Mvr

    IGMP join and leave messages. IGMP leave messages from an MVR group are handled according to the IGMP configuration of the VLAN on which the leave message is received. If IGMP fast leave is enabled Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 144: Mvr Interoperation With Other Features

    This feature does not require a license. 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 145: Default Mvr Settings

    Step 4 switch(config)# [no] Adds a multicast group at the specified IPv4 address and mvr-group addr[/mask] [count (optional) netmask length to the global default MVR VLAN. groups] [vlan vlan-id] Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 146 228.1.2.240/28 vlan 101 switch(config-mvr)# mvr-group 235.1.1.6 vlan 340 switch(config-mvr)# end switch# show mvr MVR Status : enabled Global MVR VLAN : 100 Number of MVR VLANs switch# copy running-config startup-config Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 147: Configuring Mvr Interfaces

    MVR VLAN The IP address is entered in the format a.b.c.d/m, where m is the number of bits in the netmask, from 1 to 31. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 148: Verifying The Mvr Configuration

    If this is a 10G breakout port, the slot/port Note syntax is QSFP-module/port. show mvr members [count] Displays the number and details of all MVR receiver members. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 149 100-101,340 Po208 RECEIVER ACTIVE 2000-2001 Eth1/9 SOURCE ACTIVE Eth1/10 RECEIVER ACTIVE 100-101,340 Eth2/2 RECEIVER ACTIVE 100-101,340 Eth102/1/1 RECEIVER ACTIVE 100-101,340 Eth102/1/2 RECEIVER INACTIVE 100-101,340 Eth103/1/1 RECEIVER ACTIVE 100-101,340 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 150 ACTIVE This example shows how to display all MVR source ports on all interfaces: switch# show mvr source-ports Port MVR-VLAN Status ------------ -------- -------- Po10 ACTIVE Eth1/9 ACTIVE Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 151: C H A P T E

    VLAN traffic from being sent to a device. An extension of VTP called VTP pruning has been defined to limit the scope of broadcast traffic and save bandwidth. Beginning with Release 5.1(1), the Cisco NX-OS software supports VTP pruning.
  • Page 152: Vtp V3 Modes

    • Off— Behaves similarly to the transparent mode but does not forward any VTP packets. The off mode allows you to monitor VLANs by using the CISCO-VTP-MIB without having to run VTP. On Cisco Nexus 7000 Series devices, because VTP is a conditional service, its MIB is loaded only when the corresponding feature is enabled.
  • Page 153: Vtp V3 Pruning

    This table lists the default settings for VTP parameters. Table 10: Default VTP Parameters Parameters Default Disabled VTP Mode Transparent VTP Domain blank VTP Version VTP Pruning Disabled Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 154: Configuring Vtp V3

    • The overlapping of system reserved VLANs between Cisco Nexus 6000 Series Switches and Cisco Nexus 5000 Series Switches causes interoperability issues. When a Cisco Catalyst 6000 Switch sends a VLAN reserved in the Cisco Nexus switch, it causes the Cisco Nexus 5000 and 6000 Series Switches to move to VTP Transparent Mode.
  • Page 155 This command is applicable for VTPv3 Note only. Step 11 switch# show vtp status (Optional) Displays information about the VTP configuration on the device, such as the version, mode, and revision number. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 156: Configuring Vtp V3 Pruning

    2 switch(config)# vtp mode transparent switch(config)# exit switch# Configuring VTP V3 Pruning Follow the steps given below to configure VTP V3 Pruning. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 157 Returns to privileged EXEC mode. Step 8 switch# show vtp counters (Optional) Displays VTP pruning information and counters. Step 9 switch# clear vtp counters (Optional) Resets all the VTP pruning counter values. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 158 Configuring VTP V3 Configuring VTP V3 Pruning Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 159: Information About 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 160 10-microsecond interval, traffic storm control drops all exceeding multicast traffic until the end of the interval. By default, Cisco NX-OS takes no corrective action when traffic exceeds the configured level. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 161: Chapter 1 3 Configuring Traffic Storm Control

    The result of the command is partial success in some cases. • In the Cisco Nexus 5000 switch, storm-control does not distinguish between IP, non-IP, registered, or unregistered multicast traffic. All multicast traffic is subject to a single-multicast storm control policer when configured.
  • Page 162: Verifying The Traffic Storm Control Configuration

    An additional syslog message is generated when the storm event ends and the packet are no longer dropped. Traffic Storm Control Example Configuration This example shows how to configure traffic storm control: Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 163: Default Settings For Traffic Storm Control

    Default Settings for Traffic Storm Control The following table lists the default settings for traffic storm control parameters. Table 11: Default Traffic Storm Control Parameters Parameters Default Traffic storm control Disabled Threshold percentage Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 164 Configuring Traffic Storm Control Default Settings for Traffic Storm Control Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 165: C H A P T E

    • Verifying the Chassis Management Information, page 174 • Configuring the Cisco Nexus N2248TP-E Fabric Extender, page 177 • Configuring the Cisco Nexus N2248PQ Fabric Extender, page 181 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 166: Information About The Cisco Nexus 2000 Series Fabric Extender

    Information About the Cisco Nexus 2000 Series Fabric Extender The Cisco Nexus 2000 Series Fabric Extender, also known as FEX, is a highly scalable and flexible server networking solution that works with Cisco Nexus Series devices to provide high-density, low-cost connectivity for server aggregation.
  • Page 167: Fabric Extender Terminology

    • 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 168: Layer 2 Host Interfaces

    • You can connect only virtual switches that leverages a link redundancy mechanism not dependent on spanning tree such as Cisco FlexLink or vPC (with the BPDU Filter enabled) to a Fabric Extender host interface. Because spanning tree is not used to eliminate loops, you should ensure a loop-free topology below the Fabric Extender host interfaces.
  • Page 169: Vlans And Private Vlans

    The vPC can provide multipath connections, which allow you to create redundancy between the nodes on your network. A port channel between two FEXs that are connected to the same Cisco Nexus device is not supported. Note Virtual port channels (vPCs) cannot span two different FEXs when connected to the same Cisco Nexus device.
  • Page 170 Figure 21: Dual Homed Fabric Extender vPC Topology This configuration is also called an Active-Active topology. Port channels between two Fabric Extenders connected to the same Cisco Nexus device is not supported Note vPCs cannot span two different Fabric Extenders that are connected to the same physical Cisco Nexus device.
  • Page 171: Fibre Channel Over Ethernet Support

    /www.cisco.com/en/US/products/ps9670/products_installation_and_configuration_guides_list.html. Protocol Offload To reduce the load on the control plane of the Cisco Nexus Series device, Cisco NX-OS allows you to offload link-level protocol processing to the Fabric Extender CPU. The following protocols are supported: • Link Layer Discovery Protocol (LLDP) •...
  • Page 172: Access Control Lists

    • The FEX performs a local check on the uplink SFP+ transceiver. If it fails the security check, the LED flashes but the link is still allowed to come up. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 173: Oversubscription

    (100-Mb/1-Gigabit) Ethernet host interfaces. When its host interfaces are running in Gigabit Ethernet mode, it offers similar configurations to the Cisco Nexus 2148T. The Cisco Nexus 2248TP can be run with no oversubscription when its host interfaces are running in 100-Mb mode.
  • Page 174: Management Model

    (24 host interfaces for two fabric interfaces) or higher. The Cisco Nexus B22 Fabric Extender for HP (NB22HP) has 8 10-Gigabit Ethernet fabric interfaces and 16 1G/10-Gigabit Ethernet host interfaces. All host interfaces use all of the available fabric interfaces. Static pinning and port-channel mode are supported.
  • Page 175: Forwarding Model

    Connection Model Two methods (the static pinning fabric interface connection and the Port Channel 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 176: Static Pinning Fabric Interface Connection

    Configuring the Fabric Extender Static Pinning Fabric Interface Connection The Cisco Nexus 2248PQ Fabric Extender does not support the static pinning fabric interface connection. Note Static Pinning Fabric Interface Connection To provide a deterministic relationship between the host interfaces and the parent switch, you can configure the Fabric Extender to use individual fabric interface connections.
  • Page 177: Port Channel Fabric Interface Connection

    If all links in the fabric port channel go down, all host interfaces on the FEX are set to the down state. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 178: Port Numbering Convention

    Fabric Extender. When you enter the install all command, it upgrades the software on the parent Cisco Nexus 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 179: Chassis

    Configuring the Fabric Extender Chassis Chassis The Cisco Nexus 2000 Series Fabric Extender is a 1 RU chassis that is designed for rack mounting. The chassis supports redundant hot-swappable fans and power supplies. Ethernet Interfaces There are 8 models of the Cisco Nexus 2000 Series Fabric Extender: •...
  • Page 180: Speed And Duplex Mode

    Configuring the Fabric Extender Speed and Duplex Mode • The Cisco Nexus B22 Fabric Extender for IBM (NB22IBM) has 14 1G/10-Gigabit Ethernet host interfaces. All host interfaces use all of the available fabric interfaces. Speed and Duplex Mode The table listed below shows the autonegotiation matrix for N2K-C2348TQ-10GE and N2K-C2332TQ-10GE fabric extenders.
  • Page 181 Full duplex Full duplex maximum capability of NIC is 10000 Mbps, Full duplex AUTO 10000 Mbps, Full UP, 10000 Mbps, UP, 10000 Mbps, — duplex Full duplex Full duplex Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 182: Example: Configuring The Interface Speed Parameters

    101/1/1 switch(config-if)# speed 1000 Configuration: 10G Configuring speed as 10000 Mbps (This has autoneg enabled with 10000 Mbps) switch(config)# interface ethernet 101/1/1 switch(config-if)# speed 10000 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 183: Associating A Fabric Extender To A Fabric Interface

    Associates the FEX number to the Fabric Extender unit attached to the interface. The range of the FEX number is from 100 to 199. Example: switch(config-if)# fex associate 101 switch# Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 184: Associating A Fabric Extender To A Port Channel

    Enters global configuration mode. configure terminal 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 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 185 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 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 186: Disassociating A Fabric Extender From An Interface

    Configuring Fabric Extender Global Features You can configure global features on the Fabric Extender. Before You Begin Ensure that you have enabled the Fabric Extender feature set. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 187 • N2248PQ—48 10-Gigabit SFP+ Ethernet host interfaces and 16 10-Gigabit SFP+ Ethernet fabric interfaces module. • NB22HP—16 1G/10-Gigabit SFP+ Ethernet host interfaces and 8 10-Gigabit SFP+ Ethernet fabric interfaces module Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 188: Enabling The Fabric Extender Locator Led

    The locator beacon LED on the Fabric Extender allows you to locate a specific Fabric Extender in a rack. Procedure Command or Action Purpose Step 1 locator-led fex FEX-number Turns on the locator beacon LED for a specific Fabric Extender. Example: switch# locator-led fex 101 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 189: Redistributing The Links

    • A change in the max-links configuration. • If you need to maintain the pinning order of host interfaces to fabric interfaces. The Cisco Nexus 2248PQ Fabric Extender does not support the static pinning fabric interface connection. Note Changing the Number of Links If you initially configured a specific port on the parent switch, for example port 33, as your only fabric interface, all 48 host interfaces are pinned to this port.
  • Page 190: Redistributing Host Interfaces

    Step 2 fex pinning redistribute FEX-number Redistributes the host connections. The range of the FEX-number is from 100 to 199. Example: switch(config) # fex pinning redistribute switch(config) # Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 191: Verifying The Fabric Extender Configuration

    CISCO-MOLEX INC part number is 74752-9026 revision is A0 serial number is MOC13321057 nominal bitrate is 12000 MBits/sec Link length supported for 50/125mm fiber is 0 m(s) Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 192: Verifying The Chassis Management Information

    101 Temperature Fex 101: ----------------------------------------------------------------- Module Sensor MajorThresh MinorThres CurTemp Status (Celsius) (Celsius) (Celsius) ----------------------------------------------------------------- Outlet-1 Outlet-2 Inlet-1 Die-1 Fan Fex: 101: ------------------------------------------------------ Model Status Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 193 Block Signature : 0x6002 Block Version Block Length : 103 Block Checksum : 0x2686 Feature Bits : 0x0 HW Changes Bits : 0x0 Card Index : 11016 MAC Addresses : 00-00-00-00-00-00 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 194 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 195: Configuring The Cisco Nexus N2248Tp-E Fabric Extender

    Stackmib OID Configuring the Cisco Nexus N2248TP-E Fabric Extender The Cisco Nexus 2248TP-E Fabric Extender supports all of the CLI commands of the Cisco Nexus 2248TP Fabric Extender with additional commands to configure the following: • Shared buffer (FEX global level) •...
  • Page 196: Configuring The Shared Buffer

    25392 KB. This example shows how to configure the shared buffer. switch# configure terminal switch(config)# fex 100 switch(config-fex)# hardware N2248TP-E shared-buffer-size 25000 switch(config-fex)# Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 197: Configuring The Queue Limit At The Global Level

    This example shows how to configure the queue limit. switch# configure terminal switch(config)# fex 100 switch(config-fex)# hardware N2248TP-E queue-limit 83000 tx switch(config-fex)# Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 198: Configuring The Queue Limit At The Port Level

    Configuring the Uplink Distance The Cisco Nexus N2248TP-E FEX supports a pause no-drop class up to a distance of 3000 meters between the FEX and the switch. The default cable length between the FEX and the switch is 300 meters.
  • Page 199: Configuring The Cisco Nexus N2248Pq Fabric Extender

    Configuring the Cisco Nexus N2248PQ Fabric Extender The Cisco Nexus 2248PQ Fabric Extender supports all of the CLI commands of the Cisco Nexus 2248TP Fabric Extender with additional commands to configure the following: • Shared buffer (FEX global level) •...
  • Page 200: Configuring The Uplink Distance

    Configuring the Uplink Distance The Cisco Nexus N2248PQ FEX supports a pause no-drop class up to a distance of 3000 meters between the FEX and the switch. The default cable length between the FEX and the switch is 300 meters.
  • Page 201: Configuring Slow Drain

    The value of fex is the PID of the configured FEX. The range of val is from 200ms to 1000ms. The default value is 1000 ms. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 202: Load-Balancing Queues At The Fex Global Level

    N2232P switch(config-fex)# hardware N2232P slow-port-error-disable-time 500 Load-balancing queues at the FEX global level The Cisco Nexus 2248PQ provides 8 load balancing queues. These load balancing queues are designed to resolve port congestion. Procedure Command or Action...
  • Page 203: Chapter 1 5 Configuring Vm-Fex

    Information About VM-FEX VM-FEX Overview Based on the (prestandard) IEEE 802.1Qbh port extender technology, Cisco Virtual Machine Fabric Extender (VM-FEX) extends the fabric from the switch chassis to the Virtual Machine (VM). Each VM is associated with a network adapter vNIC, which is associated with a virtual Ethernet (vEthernet or vEth) port on the parent switch.
  • Page 204: Vm-Fex Terminology

    PCIe adapter that supports static or dynamic virtualized interfaces, including up to 128 virtual network interface cards (vNICs). The configuration of the VIC and its vNICs is performed using the CIMC interface on the Cisco UCS C-Series servers. The physical ports of the server can be connected directly to the switch or to a fabric extender (FEX) connected to the switch.
  • Page 205: Licensing Requirements For Vm-Fex

    Product License Requirement Cisco NX-OS A VM-FEX license is required for each Cisco Nexus device. The license package name is VMFEX_ FEATURE_PKG. A grace period of 120 days starts when you first configure the licensed feature. For a complete explanation of the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.
  • Page 206: Configuring Vm-Fex

    Switch: Enable vPC and register the vPC system to the vCenter as a distributed virtual switch (DVS). Configuring an SVS Connection to the vCenter Server, on page 194. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 207: Enabling Features Required For Vm-Fex

    This feature is not required if the fixed vEthernet interfaces are statically configured. Step 8 (Optional) feature fcoe Enables Fibre Channel over Ethernet (FCoE) on the switch. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 208: Configuring The Fixed Static Interfaces

    Enters global configuration mode. Step 2 interface ethernet slot/port Enters interface configuration mode for the first Ethernet port. If this is a 10G breakout port, the slot/port syntax Note is QSFP-module/port. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 209 Step 16 no shutdown Enables local traffic on the interface. Step 17 interface vethernet Enters configuration mode for the second virtual interface interface-number for the second Ethernet port. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 210 4 switch-1(config-if)# bind interface ethernet 1/18 channel 11 switch-1(config-if)# no shutdown switch-1(config-if)# interface ethernet 1/17 switch-1(config-if)# no shutdown switch-1(config-if)# interface ethernet 1/18 switch-1(config-if)# no shutdown switch-1(config-if)# Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 211: Configuring A Port Profile For The Dynamic Interfaces

    This example configures a port profile for dynamic virtual interfaces: switch-1# configure terminal switch-1(config)# port-profile type vethernet vm-fex-vlan-60 switch-1(config-port-prof)# switchport mode access switch-1(config-port-prof)# switchport access vlan 60 switch-1(config-port-prof)# dvs-name all switch-1(config-port-prof)# port-binding dynamic switch-1(config-port-prof)# state enabled Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 212: Configuring An Svs Connection To The Vcenter Server

    Configures the extension key to be used to connect to the vCenter Server. With redundant switches, perform this step only Note on the primary switch. The key is automatically synchronized with the secondary switch. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 213: Activating An Svs Connection To The Vcenter Server

    The switch connects to the vCenter and becomes a DVS. This example shows how to connect to a vCenter Server: switch-1# configure terminal switch-1(config)# svs connection 2VC Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 214: Verifying The Vm-Fex Configuration

    0 output packets 0 bytes 0 flood packets 0 output packet drops switch-1# show interface vethernet 1 detail vif_index: 20 -------------------------- veth is bound to interface Ethernet1/17 (0x1a010000) Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 215 Interface Interface DV-Port Profile Address Name ------------------------------------------------------------------------- Veth32769 Eth1/20 sample Veth32770 Eth1/20 sample Veth32771 Eth1/20 sample Veth32772 Eth1/20 sample Veth32773 Eth1/20 sample Veth32774 Eth1/20 sample Veth32775 Eth1/20 sample Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 216: Verifying The Connection To The Vcenter Server

    DC1 dvs name: Pod1 DVS uuid: cd 05 25 50 6d a9 a5 c4-eb 9c 8f 6b fa 51 b1 aa config status: Disabled operational status: Connected switch-1(config)# Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 217: Configuring Mac/Arp Hardware Resource Carving Template

    MAC entries. HRT is the part of the host table that holds ARP, IPv6 ND, and /32 host routes. The STM/HRT template profile feature is specific to the Cisco Nexus device. This feature provides you with a flexibility to carve STM &...
  • Page 218: Configuring The Mac/Arp Hardware Resource Template

    This example shows how to configure the hrt-96-stm-160 template: switch# configure terminal switch(config)# hardware profile route resource service-template hrt-96-stm-160 switch(config)# copy running-config startup-config Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 219: Applying The Default Template

    Displays the details of a specific pre-defined template. show hardware profile route resource template template-name show hardware profile route resource template Displays the details of the default template. default Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 220 When entering the copy running-config startup-config command, the currently applied non-default stm/hrt template is displayed. If the default template is applied, nothing is displayed. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 221: Chapter 1 7 Configuring Vn-Segment

    VLAN tag. This feature uses a 24-bit tag also referred to as a Virtual Network Identifier (VNI). CE links (access and trunk) carry traditional VLAN tagged/untagged frames. These are the VN-Segment Edge ports. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 222 Figure 25: VN-Segment and FabricPath The previous figure shows a typical Cisco FabricPath network. Switches S1 and S2 are the spine switches. Switches S3 and S4 are the leaf switches and are connected to the spines over FabricPath interfaces. The VN-Segment feature is enabled on all leaf switches.
  • Page 223: Guidelines And Limitations For Vn-Segment

    Installs the FabricPath feature set on the switch. fabricpath Step 3 switch(config)# feature-set fabricpath Enables the FabricPath feature set on the switch. Step 4 switch(config)# feature Enables the VN-Segment feature on the switch. vn-segment-vlan-based Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 224: Configuring Vn-Segment For A Vlan

    This example shows how to configure VN-Segment for VLAN: switch# configure terminal switch(config)# vlan 100 switch(config-vlan)# mode fabricpath switch(config-vlan)# vn-segment 4096 Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 225: Configuring Vn-Segment For Vlan In Configure Sync

    Step 1 switch# configure terminal Enters global configuration mode. Step 2 switch(config)# fabricpath mode Enables transit mode. You need to save the configuration and reload the spine. transit Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 226: Configuring Vn-Segment In Non-Transit Mode

    This example shows how to configure VN-Segment in non-transit mode: switch# configure terminal switch(config)# feature vn-segment-vlan-based switch(config)# vni 16896 Disabling VN-Segment Before You Begin VN-Segment configurations must be removed manually prior to disabling the feature. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 227: Verifying Vn-Segment Configuration

    Displays information on the number of VLANs and VN-Segment mappings on each VPC switch to help determine any mismatches. show vpc consistency-parameters vlans Displays information to identify the VLAN and VN-Segment configuration mismatches. Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 228 Configuring VN-Segment Verifying VN-Segment Configuration Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x...
  • Page 229 Cisco Nexus B22 Fabric Extender for Fujitsu (NB22FTS) extended range VLANs Cisco Nexus B22 Fabric Extender for HP (NB22HP) Cisco Nexus B22 Fabric Extender for IBM (NB22IBM) CIST regional root CIST root Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x IN-1...
  • Page 230 125, 126, 127, 129, 130 LED beacon configuring global parameters licensing 126, 187 configuring interfaces default settings VM-FEX guidelines and limitations Link Aggregation Control Protocol, See LACP interoperation with IGMP snooping Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x IN-2...
  • Page 231 SPROM promiscuous ports show transceiver status single homed fabric extender vPC topology small form-factor pluggable transceiver snooping parameters, configuring IGMP SPAN restrictions quality-of-service, See SPAN source ports Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x IN-3...
  • Page 232 180, 182 terminology configuring 180, 182 verifying interface status verifying vCenter connection interoperation with MVR vPC topology Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x IN-4...

Table of Contents

Save PDF