Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.1(3)N2(1)

Transcription

1 Cisco Nexus 5000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.1(3)N2(1) First Published: March 09, 2012 Last Modified: April 18, 2012 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax: Text Part Number: OL

2 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 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: 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. (1110R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental Cisco Systems, Inc. All rights reserved.

3 CONTENTS Preface Preface xvii Audience xvii Document Conventions xvii Related Documentation xviii Obtaining Documentation and Submitting a Service Request xx CHAPTER 1 New and Changed Information 1 New and Changed Information for this Release 1 CHAPTER 2 Overview 3 Layer 2 Ethernet Switching Overview 3 VLANs 3 Private VLANs 4 Spanning Tree 4 STP Overview 4 Rapid PVST+ 5 MST 5 STP Extensions 5 CHAPTER 3 Configuring Ethernet Interfaces 7 Information About Ethernet Interfaces 7 About the Interface Command 7 Information About Unified Ports 8 About the Unidirectional Link Detection Parameter 8 Default UDLD Configuration 9 UDLD Aggressive and Nonaggressive Modes 10 About Interface Speed 10 OL iii

4 Contents About the Cisco Discovery Protocol 10 Default CDP Configuration 10 About the Error-Disabled State 11 About Port Profiles 11 Guidelines and Limitations for Port Profiles 12 About the Debounce Timer Parameters 13 About MTU Configuration 13 Configuring Ethernet Interfaces 13 Configuring a Layer 3 Interface on a Cisco Nexus 5500 Platform Switch 13 Configuring Unified Ports 14 Configuring the UDLD Mode 16 Configuring Interface Speed 17 Disabling Link Negotiation 18 Configuring the CDP Characteristics 19 Enabling or Disabling CDP 20 Enabling the Error-Disabled Detection 20 Enabling the Error-Disabled Recovery 21 Configuring the Error-Disabled Recovery Interval 22 Port Profiles 23 Creating a Port Profile 23 Modifying a Port Profile 24 Enabling a Specific Port Profile 25 Inheriting a Port Profile 26 Removing an Inherited Port Profile 28 Assigning a Port Profile to a Range of Interfaces 29 Removing a Port Profile from a Range of Interfaces 30 Configuration Examples for Port Profiles 31 Configuring the Debounce Timer 31 Configuring the Description Parameter 32 Disabling and Restarting Ethernet Interfaces 33 Displaying Interface Information 33 Default Physical Ethernet Settings 36 CHAPTER 4 Configuring VLANs 37 Information About VLANs 37 iv OL

5 Contents Understanding VLANs 37 Understanding VLAN Ranges 39 Creating, Deleting, and Modifying VLANs 40 About the VLAN Trunking Protocol 40 Guidelines and Limitations for VTP 41 Configuring a VLAN 41 Creating and Deleting a VLAN 41 Configuring a VLAN 42 Adding Ports to a VLAN 43 Configuring VTP 44 Verifying VLAN Configuration 46 CHAPTER 5 Configuring Private VLANs 47 Information About Private VLANs 47 Primary and Secondary VLANs in Private VLANs 48 Private VLAN Ports 48 Primary, Isolated, and Community Private VLANs 49 Associating Primary and Secondary VLANs 50 Private VLAN Promiscuous Trunks 51 Private VLAN Isolated Trunks 51 Broadcast Traffic in Private VLANs 52 Private VLAN Port Isolation 52 Guidelines and Limitations for Private VLANs 52 Configuring a Private VLAN 53 Enabling Private VLANs 53 Configuring a VLAN as a Private VLAN 53 Associating Secondary VLANs with a Primary Private VLAN 54 Configuring an Interface as a Private VLAN Host Port 55 Configuring an Interface as a Private VLAN Promiscuous Port 56 Configuring a Promiscuous Trunk Port 57 Configuring an Isolated Trunk Port 58 Configuring Private VLANs on FEX Trunk Ports 59 Configuring the Allowed VLANs for PVLAN Trunking Ports 60 Configuring Native 802.1Q VLANs on Private VLANs 60 Verifying the Private VLAN Configuration 61 OL v

6 Contents CHAPTER 6 Configuring Access and Trunk Interfaces 63 Information About Access and Trunk Interfaces 63 Understanding Access and Trunk Interfaces 63 Understanding IEEE 802.1Q Encapsulation 64 Understanding Access VLANs 65 Understanding the Native VLAN ID for Trunk Ports 66 Understanding Allowed VLANs 66 Understanding Native 802.1Q VLANs 66 Configuring Access and Trunk Interfaces 67 Configuring a LAN Interface as an Ethernet Access Port 67 Configuring Access Host Ports 68 Configuring Trunk Ports 68 Configuring the Native VLAN for 802.1Q Trunking Ports 69 Configuring the Allowed VLANs for Trunking Ports 69 Configuring Native 802.1Q VLANs 70 Verifying Interface Configuration 71 CHAPTER 7 Configuring Port Channels 73 Information About Port Channels 73 Understanding Port Channels 73 Guidelines and Limitations for Port Channel Configuration 74 Compatibility Requirements 75 Load Balancing Using Port Channels 76 Understanding LACP 79 LACP Overview 79 LACP ID Parameters 80 Channel Modes 80 LACP Marker Responders 81 LACP-Enabled and Static Port Channel Differences 82 Configuring Port Channels 82 Creating a Port Channel 82 Adding a Port to a Port Channel 83 Configuring Load Balancing Using Port Channels 83 Configuring Hardware Hashing for Multicast Traffic 85 vi OL

7 Contents Enabling LACP 85 Configuring the Channel Mode for a Port 86 Configuring the LACP Fast Timer Rate 87 Configuring the LACP System Priority and System ID 88 Configuring the LACP Port Priority 88 Disabling LACP Graceful Convergence 89 Reenabling LACP Graceful Convergence 90 Verifying Port Channel Configuration 91 Verifying the Load-Balancing Outgoing Port ID 92 CHAPTER 8 Configuring Virtual Port Channels 95 Information About vpcs 95 vpc Overview 95 Terminology 97 vpc Terminology 97 Fabric Extender Terminology 97 Supported vpc Topologies 98 Cisco Nexus 5000 Series Switch vpc Topology 98 Single Homed Fabric Extender vpc Topology 99 Dual Homed Fabric Extender vpc Topology 100 vpc Domain 100 Peer-Keepalive Link and Messages 101 Compatibility Parameters for vpc Peer Links 101 Configuration Parameters That Must Be Identical 101 Configuration Parameters That Should Be Identical 103 Graceful Type-1 Check 103 Per-VLAN Consistency Check 104 vpc Auto-Recovery 104 vpc Peer Links 104 vpc Peer Link Overview 104 vpc Number 105 vpc Interactions with Other Features 106 vpc and LACP 106 vpc Peer Links and STP 106 vpc and ARP 107 OL vii

8 Contents CFSoE 107 Guidelines and Limitations for vpcs 107 Configuring vpcs 108 Enabling vpcs 108 Disabling vpcs 108 Creating a vpc Domain 109 Configuring a vpc Keepalive Link and Messages 110 Creating a vpc Peer Link 112 Checking the Configuration Compatibility 113 Enabling vpc Auto-Recovery 114 Configuring the Restore Time Delay 115 Excluding VLAN Interfaces From Shutdown When vpc Peer Link Fails 116 Configuring the VRF Name 116 Binding a VRF Instance to a vpc 117 Enabling Layer 3 Forwarding to the Gateway MAC Address of the vpc 118 Suspending Orphan Ports on a Secondary Switch in a vpc Topology 118 Creating an EtherChannel Host Interface 119 Moving Other Port Channels into a vpc 120 Manually Configuring a vpc Domain MAC Address 121 Manually Configuring the System Priority 122 Manually Configuring a vpc Peer Switch Role 123 Verifying the vpc Configuration 124 Viewing The Graceful Type-1 Check Status 125 Viewing A Global Type-1 Inconsistency 125 Viewing An Interface-Specific Type-1 Inconsistency 126 Viewing a Per-VLAN Consistency Status 127 vpc Example Configurations 129 Dual Homed Fabric Extender vpc Configuration Example 129 Single Homed Fabric Extender vpc Configuration Example 131 vpc Default Settings 133 CHAPTER 9 Configuring Enhanced Virtual Port Channels 135 Information About Enhanced vpcs 135 Enhanced Virtual Port Channels Overview 135 Supported Platforms and Topologies 136 viii OL

9 Contents Enhanced vpc Scalability 137 Enhanced vpc Failure Response 137 Licensing Requirements for Enhanced vpc 138 Configuring Enhanced vpcs 138 Overview of Configuration Steps for Enhanced vpc 138 Verifying Enhanced vpcs 139 Verifying the Enhanced vpc Configuration 139 Verifying the Consistency of Port Channel Numbers 139 Verifying Common Port Channel Members 141 Verifying Interface Level Consistency for Enhanced vpc 142 Enhanced vpc Example Configuration 142 CHAPTER 10 Configuring Rapid PVST+ 145 Information About Rapid PVST+ 145 Understanding STP 145 STP Overview 145 Understanding How a Topology is Created 146 Understanding the Bridge ID 146 Bridge Priority Value 146 Extended System ID 147 STP MAC Address Allocation 147 Understanding BPDUs 148 Election of the Root Bridge 149 Creating the Spanning Tree Topology 149 Understanding Rapid PVST+ 150 Rapid PVST+ Overview 150 Rapid PVST+ BPDUs 151 Proposal and Agreement Handshake 152 Protocol Timers 153 Port Roles 153 Port States 154 Rapid PVST+ Port State Overview 154 Blocking State 155 Learning State 155 Forwarding State 155 OL ix

10 Contents Disabled State 156 Summary of Port States 156 Synchronization of Port Roles 156 Processing Superior BPDU Information 157 Processing Inferior BPDU Information 158 Spanning-Tree Dispute Mechanism 158 Port Cost 158 Port Priority 159 Rapid PVST+ and IEEE 802.1Q Trunks 159 Rapid PVST+ Interoperation with Legacy 802.1D STP 159 Rapid PVST+ Interoperation with 802.1s MST 160 Configuring Rapid PVST+ 160 Enabling Rapid PVST+ 160 Enabling Rapid PVST+ per VLAN 161 Configuring the Root Bridge ID 162 Configuring a Secondary Root Bridge 163 Configuring the Rapid PVST+ Port Priority 164 Configuring the Rapid PVST+ Pathcost Method and Port Cost 165 Configuring the Rapid PVST+ Bridge Priority of a VLAN 165 Configuring the Rapid PVST+ Hello Time for a VLAN 166 Configuring the Rapid PVST+ Forward Delay Time for a VLAN 167 Configuring the Rapid PVST+ Maximum Age Time for a VLAN 167 Specifying the Link Type 167 Restarting the Protocol 168 Verifying Rapid PVST+ Configurations 168 CHAPTER 11 Configuring Multiple Spanning Tree 171 Information About MST 171 MST Overview 171 MST Regions 172 MST BPDUs 172 MST Configuration Information 173 IST, CIST, and CST 173 IST, CIST, and CST Overview 173 Spanning Tree Operation Within an MST Region 174 x OL

11 Contents Spanning Tree Operations Between MST Regions 174 MST Terminology 175 Hop Count 176 Boundary Ports 176 Spanning-Tree Dispute Mechanism 177 Port Cost and Port Priority 178 Interoperability with IEEE 802.1D 178 Interoperability with Rapid PVST+: Understanding PVST Simulation 179 Configuring MST 179 MST Configuration Guidelines 179 Enabling MST 179 Entering MST Configuration Mode 180 Specifying the MST Name 181 Specifying the MST Configuration Revision Number 182 Specifying the Configuration on an MST Region 182 Mapping and Unmapping VLANs to MST Instances 184 Mapping Secondary VLANs to Same MSTI as Primary VLANs for Private VLANs 184 Configuring the Root Bridge 185 Configuring a Secondary Root Bridge 186 Configuring the Port Priority 187 Configuring the Port Cost 188 Configuring the Switch Priority 188 Configuring the Hello Time 189 Configuring the Forwarding-Delay Time 190 Configuring the Maximum-Aging Time 190 Configuring the Maximum-Hop Count 191 Configuring PVST Simulation Globally 191 Configuring PVST Simulation Per Port 192 Specifying the Link Type 193 Restarting the Protocol 193 Verifying MST Configurations 194 CHAPTER 12 Configuring STP Extensions 195 About STP Extensions 195 Information About STP Extensions 195 OL xi

12 Contents Understanding STP Port Types 195 Spanning Tree Edge Ports 195 Spanning Tree Network Ports 196 Spanning Tree Normal Ports 196 Understanding Bridge Assurance 196 Understanding BPDU Guard 196 Understanding BPDU Filtering 197 Understanding Loop Guard 198 Understanding Root Guard 198 Configuring STP Extensions 199 STP Extensions Configuration Guidelines 199 Configuring Spanning Tree Port Types Globally 199 Configuring Spanning Tree Edge Ports on Specified Interfaces 200 Configuring Spanning Tree Network Ports on Specified Interfaces 201 Enabling BPDU Guard Globally 202 Enabling BPDU Guard on Specified Interfaces 203 Enabling BPDU Filtering Globally 204 Enabling BPDU Filtering on Specified Interfaces 205 Enabling Loop Guard Globally 206 Enabling Loop Guard or Root Guard on Specified Interfaces 206 Verifying STP Extension Configuration 207 CHAPTER 13 Configuring Flex Links 209 Information About Flex Links 209 Guidelines and Limitations for Flex Link 210 Default Settings for Flex Link 211 Configuring Flex Links 212 Configuring Flex Link Preemption 213 Verifying Flex Link Configuration 214 Flex Link Configuration Examples 215 CHAPTER 14 Configuring LLDP 217 Configuring Global LLDP Commands 217 Configuring Interface LLDP Commands 219 xii OL

13 Contents CHAPTER 15 Configuring the MAC Address Table 221 Information About MAC Addresses 221 Configuring MAC Addresses 221 Configuring a Static MAC Address 221 Configuring the Aging Time for the MAC Table 222 Clearing Dynamic Addresses from the MAC Table 223 Verifying the MAC Address Configuration 223 CHAPTER 16 Configuring IGMP Snooping 225 Information About IGMP Snooping 225 IGMPv1 and IGMPv2 226 IGMPv3 227 IGMP Snooping Querier 227 IGMP Forwarding 227 Configuring IGMP Snooping Parameters 228 Verifying IGMP Snooping Configuration 231 CHAPTER 17 Configuring MVR 233 Information About MVR 233 MVR Overview 233 MVR Interoperation with Other Features 234 Licensing Requirements for MVR 234 Guidelines and Limitations for MVR 234 Default MVR Settings 235 Configuring MVR 235 Configuring MVR Global Parameters 235 Configuring MVR Interfaces 237 Verifying the MVR Configuration 238 CHAPTER 18 Configuring Traffic Storm Control 241 Information About Traffic Storm Control 241 Traffic Storm Guidelines and Limitations 242 Configuring Traffic Storm Control 243 Verifying Traffic Storm Control Configuration 243 OL xiii

14 Contents Traffic Storm Control Example Configuration 244 Default Traffic Storm Settings 244 CHAPTER 19 Configuring the Fabric Extender 245 About the Cisco Nexus 2000 Series Fabric Extender 245 Fabric Extender Terminology 246 Fabric Extender Features 247 Layer 2 Host Interfaces 247 Host Port Channel 248 VLANs and Private VLANs 248 Virtual Port Channels 248 Fibre Channel over Ethernet Support 249 Protocol Offload 250 Quality of Service 250 Access Control Lists 250 IGMP Snooping 251 Switched Port Analyzer 251 Fabric Interface Features 251 Oversubscription 252 Management Model 253 Forwarding Model 253 Connection Model 254 Static Pinning Fabric Interface Connection 254 Port Channel Fabric Interface Connection 255 Port Numbering Convention 256 Fabric Extender Image Management 256 Fabric Extender Hardware 257 Chassis 257 Ethernet Interfaces 257 Information About Associating a Fabric Extender to a Fabric Interface 258 Associating a Fabric Extender to an Ethernet Interface 258 Associating a Fabric Extender to a Port Channel 259 Disassociating a Fabric Extender From an Interface 261 Configuring Fabric Extender Global Features 262 Enabling the Fabric Extender Locator LED 264 xiv OL

15 Contents Redistributing the Links 264 Changing the Number of Links 264 Maintaining the Pinning Order 264 Redistributing Host Interfaces 265 Verifying the Fabric Extender Configuration 266 Verifying the Chassis Management Information 268 Configuring the Cisco Nexus N2248TP-E Fabric Extender 273 Configuring the Shared Buffer 273 Configuring the Queue-Limit at the Global Level 274 Configuring the Queue-Limit at the Port Level 275 Configuring Uplink Distance 276 CHAPTER 20 Configuring VM-FEX 279 Information About VM-FEX 279 VM-FEX Overview 279 VM-FEX Components 279 VM-FEX Terminology 280 Licensing Requirements for VM-FEX 281 Default Settings for VM-FEX 281 Configuring VM-FEX 282 Overview of the VM-FEX Configuration Steps 282 Enabling Features Required for VM-FEX 283 Configuring the Fixed Static Interfaces 285 Configuring a Port Profile for the Dynamic Interfaces 288 Configuring an SVS Connection to the vcenter Server 289 Activating an SVS Connection to the vcenter Server 291 Verifying the VM-FEX Configuration 292 Verifying the Status of the Virtual Interfaces 292 Verifying the Connection to the vcenter Server 294 OL xv

16 Contents xvi OL

17 Preface This preface contains the following sections: Audience, page xvii Document Conventions, page xvii Related Documentation, page xviii Obtaining Documentation and Submitting a Service Request, page xx Audience This publication is for experienced network administrators who configure and maintain Cisco Nexus Series devices and Cisco Nexus 2000 Series Fabric Extenders. Document Conventions Command descriptions use the following conventions: Convention bold Italic [x] [x y] {x y} Description Bold text indicates the commands and keywords that you enter literally as shown. Italic text indicates arguments for which the user supplies the values. Square brackets enclose an optional element(keyword or argument). Square brackets enclosing keywords or arguments separated by a vertical bar indicate an optional choice. Braces enclosing keywords or arguments separated by a vertical bar indicate a required choice. OL xvii

18 Related Documentation Preface Convention [x {y z}] variable string Description Nested set of square brackets or braces indicate optional or required choices within optional or required elements. Braces and a vertical bar within square brackets indicate a required choice within an optional element. Indicates a variable for which you supply values, in context where italics cannot be used. A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks. Examples use the following conventions: Convention screen font boldface screen font italic screen font < > [ ]!, # Description Terminal sessions and information the switch displays are in screen font. Information you must enter is in boldface screen font. Arguments for which you supply values are in italic screen font. Nonprinting characters, such as passwords, are in angle brackets. Default responses to system prompts are in square brackets. An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line. This document uses the following conventions: Means reader take note. s contain helpful suggestions or references to material not covered in the manual. Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Related Documentation The entire Cisco NX-OS 5000 Series documentation set is available at the following URL: xviii OL

19 Preface Related Documentation Release s The release notes are available at the following URL: Configuration Guides These guides are available at the following URL: The documents in this category include: Adapter-FEX Configuration Guide Cisco Fabric Manager Configuration Guide Cisco Nexus 5000 Series NX-OS Software Configuration Guide Configuration Limits for Cisco NX-OS FabricPath Configuration Guide Fibre Channel over Ethernet Configuration Guide Layer 2 Switching Configuration Guide Multicast Routing Configuration Guide Operations Guide SAN Switching Configuration Guide Quality of Service Configuration Guide Security Configuration Guide System Management Configuration Guide Unicast Routing Configuration Guide Maintain and Operate Guides Cisco Nexus 5000 Series NX-OS Operations Guides for various features are available at en/us/products/ps9670/prod_maintenance_guides_list.html. Installation and Upgrade Guides These guides are available at the following URL: The documents in this category include: FabricPath Command Reference Software Upgrade and Downgrade Guides Regulatory Compliance and Safety Information OL xix

20 Obtaining Documentation and Submitting a Service Request Preface Licensing Guide The License and Copyright Information for Cisco NX-OS Software is available at US/docs/switches/datacenter/sw/4_0/nx-os/license_agreement/nx-ossw_lisns.html. Command References These guides are available at the following URL: The documents in this category include: Command Reference Master Index Fabric Extender Command Reference FabricPath Command Reference Fibre Channel Command Reference Fundamentals Command Reference Layer 2 Interfaces Command Reference Multicast Routing Command Reference QoS Command Reference Security Command Reference System Management Command Reference TrustSec Command Reference Unicast Routing Command Reference vpc Command Reference Technical References The Cisco Nexus 5000 and Cisco Nexus 2000 MIBs Reference is available at docs/switches/datacenter/nexus5000/sw/mib/reference/nx5000_mibref.html. Error and System Messages The Nexus 5000 Series NX-OS System Message Reference is available at switches/datacenter/nexus5000/sw/system_messages/reference/sl_nxos_book.html. Troubleshooting Guide The Cisco Nexus 5000 Series Troubleshooting Guide is available at datacenter/nexus5000/sw/troubleshooting/guide/n5k_troubleshooting_guide.html. Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: xx OL

21 Preface Obtaining Documentation and Submitting a Service Request Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0. OL xxi

22 Obtaining Documentation and Submitting a Service Request Preface xxii OL

23 CHAPTER 1 New and Changed Information This chapter contains the following sections: New and Changed Information for this Release, page 1 New and Changed Information for this Release The following table provides an overview of the significant changes to this guide for this current release. The table does not provide an exhaustive list of all changes made to the configuration guides or of the new features in this release. Table 1: New Features Feature PVLAN over FEX Ports Description Enables configuration of PVLAN on FEX ports. Where Documented Configuring Private VLANs, on page 47 OL

24 New and Changed Information for this Release New and Changed Information 2 OL

25 CHAPTER 2 Overview This chapter contains the following sections: Layer 2 Ethernet Switching Overview, page 3 VLANs, page 3 Private VLANs, page 4 Spanning Tree, page 4 Layer 2 Ethernet Switching Overview The device supports simultaneous, parallel connections between Layer 2 Ethernet segments. Switched connections between Ethernet segments last only for the duration of the packet. New connections can be made between different segments for the next packet. The device solves congestion problems caused by high-bandwidth devices and a large number of users by assigning each device (for example, a server) to its own 10-, 100-, 1000-Mbps, or 10-Gigabit collision domain. Because each LAN port connects to a separate Ethernet collision domain, servers in a switched environment achieve full access to the bandwidth. Because collisions cause significant congestion in Ethernet networks, an effective solution is full-duplex communication. Typically, 10/100-Mbps Ethernet operates in half-duplex mode, which means that stations can either receive or transmit. In full-duplex mode, which is configurable on these interfaces, two stations can transmit and receive at the same time. When packets can flow in both directions simultaneously, the effective Ethernet bandwidth doubles. 1/10-Gigabit Ethernet operates in full-duplex only. VLANs A VLAN is a switched network that is logically segmented by function, project team, or application, without regard to the physical locations of the users. VLANs have the same attributes as physical LANs, but you can group end stations even if they are not physically located on the same LAN segment. Any switch port can belong to a VLAN, and unicast, broadcast, and multicast packets are forwarded and flooded only to end stations in that VLAN. Each VLAN is considered as a logical network, and packets destined for stations that do not belong to the VLAN must be forwarded through a bridge or a router. OL

26 Private VLANs Overview All ports, including the management port, are assigned to the default VLAN (VLAN1) when the device first comes up. A VLAN interface, or switched virtual interface (SVI), is a Layer 3 interface that is created to provide communication between VLANs. The devices support 4094 VLANs in accordance with the IEEE 802.1Q standard. These VLANs are organized into several ranges, and you use each range slightly differently. Some of these VLANs are reserved for internal use by the device and are not available for configuration. Inter-Switch Link (ISL) trunking is not supported on the NX-OS software for the Cisco Nexus 5000 Series. Private VLANs Spanning Tree STP Overview Private VLANs provide traffic separation and security at the Layer 2 level. A private VLAN is one or more pairs of a primary VLAN and a secondary VLAN, all with the same primary VLAN. The two types of secondary VLANs are isolated and community VLANs. Hosts on isolated VLANs communicate only with hosts in the primary VLAN. Hosts in a community VLAN can communicate only among themselves and with hosts in the primary VLAN but not with hosts in isolated VLANs or in other community VLANs. Regardless of the combination of isolated and community secondary VLANs, all interfaces within the primary VLAN comprise one Layer 2 domain, and therefore, require only one IP subnet. This section discusses the implementation of the Spanning Tree Protocol (STP). Spanning tree is used to refer to IEEE 802.1w and IEEE 802.1s. When the IEEE 802.1D Spanning Tree Protocol is referred to in the publication, 802.1D is stated specifically. STP provides a loop-free network at the Layer 2 level. Layer 2 LAN ports send and receive STP frames, which are called Bridge Protocol Data Units (BPDUs), at regular intervals. Network devices do not forward these frames but use the frames to construct a loop-free path D is the original standard for STP, and many improvements have enhanced the basic loop-free STP. You can create a separate loop-free path for each VLAN, which is named Per VLAN Spanning Tree (PVST+). Additionally, the entire standard was reworked to make the loop-free convergence process faster to keep up with the faster equipment. This STP standard with faster convergence is the 802.1w standard, which is known as Rapid Spanning Tree (RSTP). Finally, the 802.1s standard, Multiple Spanning Trees (MST), allows you to map multiple VLANs into a single spanning tree instance. Each instance runs an independent spanning tree topology. Although the software can interoperate with legacy 802.1D systems, the system runs Rapid PVST+ and MST. You can use either Rapid PVST+ or MST in a given VDC;; you cannot mix both in one VDC. Rapid PVST+ is the default STP protocol for Cisco NX-OS for the Cisco Nexus 5000 Series. 4 OL

27 Overview Rapid PVST+ Cisco NX-OS for the Cisco Nexus 5000 Series 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. Rapid PVST+ Rapid PVST+ is the default spanning tree mode for the software and is enabled by default on the default VLAN and all newly created VLANs. A single instance, or topology, of RSTP runs on each configured VLAN, and each Rapid PVST+ instance on a VLAN has a single root device. You can enable and disable STP on a per-vlan basis when you are running Rapid PVST+. MST The software also supports MST. The multiple independent spanning tree topologies enabled by MST provide multiple forwarding paths for data traffic, enable load balancing, and reduce the number of STP instances required to support a large number of VLANs. MST incorporates RSTP, so it also allows rapid convergence. MST improves the fault tolerance of the network because a failure in one instance (forwarding path) does not affect other instances (forwarding paths). Changing the spanning tree mode disrupts the traffic because all spanning tree instances are stopped for the previous mode and started for the new mode. You can force specified interfaces to send prestandard, rather than standard, MST messages using the command-line interface. STP Extensions The software supports the following Cisco proprietary features: Spanning tree port types The default spanning tree port type is normal. You can configure interfaces connected to Layer 2 hosts as edge ports and interfaces connected to Layer 2 switches or bridges as network ports. Bridge Assurance Once you configure a port as a network port, Bridge Assurance sends BPDUs on all ports and moves a port into the blocking state if it no longer receives BPDUs. This enhancement is available only when you are running Rapid PVST+ or MST. BPDU Guard BPDU Guard shuts down the port if that port receives a BPDU. BPDU Filter BPDU Filter suppresses sending and receiving BPDUs on the port. Loop Guard Loop Guard prevents the nondesignated ports from transitioning to the STP forwarding state, which prevents loops in the network. Root Guard Root Guard prevents the port from becoming the root in an STP topology. OL

28 STP Extensions Overview 6 OL

29 CHAPTER 3 Configuring Ethernet Interfaces This chapter contains the following sections: Information About Ethernet Interfaces, page 7 Configuring Ethernet Interfaces, page 13 Displaying Interface Information, page 33 Default Physical Ethernet Settings, page 36 Information About Ethernet Interfaces The Ethernet ports can operate as standard Ethernet interfaces connected to servers or to a LAN. The Ethernet interfaces also support Fibre Channel over Ethernet (FCoE). FCoE allows the physical Ethernet link to carry both Ethernet and Fibre Channel traffic. On a Cisco Nexus 5000 Series switch, the Ethernet interfaces are enabled by default. About the Interface Command You can enable the various capabilities of the Ethernet interfaces on a per-interface basis using the interface command. When you enter the interface command, you specify the following information: Interface type All physical Ethernet interfaces use the ethernet keyword. Slot number Slot 1 includes all the fixed ports. Slot 2 includes the ports on the upper expansion module (if populated). Slot 3 includes the ports on the lower expansion module (if populated). Port number Port number within the group. OL

30 Information About Unified Ports Configuring Ethernet Interfaces The interface numbering convention is extended to support use with a Cisco Nexus 2000 Series Fabric Extender as follows: switch(config)# interface ethernet [chassis/]slot/port Chassis ID is an optional entry to address the ports of a connected Fabric Extender. The chassis ID is configured on a physical Ethernet or EtherChannel interface on the switch to identify the Fabric Extender discovered via the interface. The chassis ID ranges from 100 to 199. Information About Unified Ports Beginning in Cisco NX-OS Release 5.0(3)N1(1b), Cisco introduces unified port technology. Cisco Nexus unified ports allow you to configure a physical port on a Cisco Nexus 5500 Platform switch as a 1/10-Gigabit Ethernet, Fibre Channel over Ethernet (FCoE), or 1-, 2-, 4-, 8-Gigabit native Fibre Channel port. Currently, most networks have two types of switches for different types of networks. For example, LAN switches carry Ethernet traffic up to Catalyst switches and SAN switches carry FC traffic from servers to MDS switches. With unified port technology, you can deploy a unified platform, unified device, and unified wire approach. Unified ports allow you to move from an existing segregated platform approach where you choose LAN and SAN port options to transition to a single, unified fabric that is transparent and consistent with existing practices and management software. A unified fabric includes the following: Unified platform Uses the same hardware platform and the same software code level and certifies it once for your LAN and SAN environments. Unified device Runs LAN and SAN services on the same platform switch. The unified device allows you to connect your Ethernet and Fibre Channel cables to the same device. Unified wire Converges LAN and SAN networks on a single converged network adapter (CNA) and connects them to your server. A unified fabric allows you to manage Ethernet and FCoE features independently with existing Cisco tools. The new Cisco Nexus 5548UP switch and the Cisco Nexus 5596UP switch provides built-in unified port technology. In addition, a new unified port expansion module and two Layer 3 modules increase the benefits of a deployed unified fabric. For information on the new Cisco Unified Port switches and modules, see the Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release s for Cisco NX-OS Release 5.0(3)N1(1b) and NX-OS Release 5.0(3)N1(1c) and the Cisco Nexus 5000 Series Hardware Installation Guide. About the Unidirectional Link Detection Parameter The Cisco-proprietary Unidirectional Link Detection (UDLD) protocol allows ports that are connected through fiber optics or copper (for example, Category 5 cabling) Ethernet cables to monitor the physical configuration of the cables and detect when a unidirectional link exists. When the switch detects a unidirectional link, UDLD shuts down the affected LAN port and alerts the user. Unidirectional links can cause a variety of problems, including spanning tree topology loops. UDLD is a Layer 2 protocol that works with the Layer 1 protocols to determine the physical status of a link. At Layer 1, autonegotiation takes care of physical signaling and fault detection. UDLD performs tasks that autonegotiation cannot perform, such as detecting the identities of neighbors and shutting down misconnected LAN ports. When you enable both autonegotiation and UDLD,Layer 1 and Layer 2 detections work together to prevent physical and logical unidirectional connections and the malfunctioning of other protocols. 8 OL

31 Configuring Ethernet Interfaces About the Unidirectional Link Detection Parameter A unidirectional link occurs whenever traffic transmitted by the local device over a link is received by the neighbor but traffic transmitted from the neighbor is not received by the local device. If one of the fiber strands in a pair is disconnected, as long as autonegotiation is active, the link does not stay up. In this case, the logical link is undetermined, and UDLD does not take any action. If both fibers are working normally at Layer 1, then UDLD at Layer 2 determines whether those fibers are connected correctly and whether traffic is flowing bidirectionally between the correct neighbors. This check cannot be performed by autonegotiation, because autonegotiation operates at Layer 1. A Cisco Nexus 5000 Series switch periodically transmits UDLD frames to neighbor devices on LAN ports with UDLD enabled. If the frames are echoed back within a specific time frame and they lack a specific acknowledgment (echo), the link is flagged as unidirectional and the LAN port is shut down. Devices on both ends of the link must support UDLD in order for the protocol to successfully identify and disable unidirectional links. By default, UDLD is locally disabled on copper LAN ports to avoid sending unnecessary control traffic on this type of media. The following figure shows an example of a unidirectional link condition. Device B successfully receives traffic from Device A on the port. However, Device A does not receive traffic from Device B on the same port. UDLD detects the problem and disables the port. Figure 1: Unidirectional Link Default UDLD Configuration The following table shows the default UDLD configuration. Table 2: UDLD Default Configuration Feature UDLD global enable state UDLD aggressive mode UDLD per-port enable state for fiber-optic media UDLD per-port enable state for twisted-pair (copper) media Default Value Globally disabled Disabled Enabled on all Ethernet fiber-optic LAN ports Disabled on all Ethernet 10/100 and 1000BASE-TX LAN ports OL

32 About Interface Speed Configuring Ethernet Interfaces UDLD Aggressive and Nonaggressive Modes UDLD aggressive mode is disabled by default. You can configure UDLD aggressive mode only on point-to-point links between network devices that support UDLD aggressive mode. If UDLD aggressive mode is enabled, when a port on a bidirectional link that has a UDLD neighbor relationship established stops receiving UDLD frames, UDLD tries to reestablish the connection with the neighbor. After eight failed retries, the port is disabled. To prevent spanning tree loops, nonaggressive UDLD with the default interval of 15 seconds is fast enough to shut down a unidirectional link before a blocking port transitions to the forwarding state (with default spanning tree parameters). When you enable the UDLD aggressive mode, the following occurs: One side of a link has a port stuck (both transmission and receive) One side of a link remains up while the other side of the link is down In these cases, the UDLD aggressive mode disables one of the ports on the link, which prevents traffic from being discarded. About Interface Speed A Cisco Nexus 5000 Series switchhas a number of fixed 10-Gigabit ports, each equipped with SFP+ interface adapters. The Cisco Nexus 5010 switch has 20 fixed ports, the first 8 of which are switchable 1-Gigabit and 10-Gigabit ports. The Cisco Nexus 5020 switch has 40 fixed ports, the first 16 of which are switchable 1-Gigabit and 10-Gigabit ports. About the Cisco Discovery Protocol The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over Layer 2 (the data link layer) on all Cisco-manufactured devices (routers, bridges, access servers, and switches) and allows network management applications to discover Cisco devices that are neighbors of already known devices. With CDP, network management applications can learn the device type and the Simple Network Management Protocol (SNMP) agent address of neighboring devices running lower-layer, transparent protocols. This feature enables applications to send SNMP queries to neighboring devices. CDP runs on all media that support Subnetwork Access Protocol (SNAP). Because CDP runs over the data-link layer only, two systems that support different network-layer protocols can learn about each other. Each CDP-configured device sends periodic messages to a multicast address, advertising at least one address at which it can receive SNMP messages. The advertisements also contain time-to-live, or holdtime information, which is the length of time a receiving device holds CDP information before discarding it. Each device also listens to the messages sent by other devices to learn about neighboring devices. The switch supports both CDP Version 1 and Version 2. Default CDP Configuration The following table shows the default CDP configuration. 10 OL

33 Configuring Ethernet Interfaces About the Error-Disabled State Table 3: Default CDP Configuration Feature CDP interface state CDP timer (packet update frequency) CDP holdtime (before discarding) CDP Version-2 advertisements Default Setting Enabled 60 seconds 180 seconds Enabled About the Error-Disabled State An interface is in the error-disabled (err-disabled) state when the inteface is enabled administratively (using the no shutdown command) but disabled at runtime by any process. For example, if UDLD detects a unidirectional link, the interface is shut down at runtime. However, because the interface is administratively enabled, the interface status displays as err-disabled. Once an interface goes into the err-disabled state, you must manually reenable it or you can configure an automatic timeout recovery value. The err-disabled detection is enabled by default for all causes. The automatic recovery is not configured by default. When an interface is in the err-disabled state, use the errdisable detect cause command to find information about the error. You can configure the automatic err-disabled recovery timeout for a particular err-disabled cause by changing the time variable. The errdisable recovery cause command provides automatic recovery after 300 seconds. To change the recovery period, use the errdisable recovery interval command to specify the timeout period. You can specify 30 to seconds. If you do not enable the err-disabled recovery for the cause, the interface stays in the err-disabled state until you enter the shutdown and no shutdown commands. If the recovery is enabled for a cause, the interface is brought out of the err-disabled state and allowed to retry operation once all the causes have timed out. Use the show interface status err-disabled command to display the reason behind the error. About Port Profiles You can create a port profile that contains many interface commands and apply that port profile to a range of interfaces on the Cisco Nexus 5000 Series switch. Port profiles can be applied to the following interface types: Ethernet VLAN network interface Port channel A command that is included in a port profile can be configured outside of the port profile. If the new configuration in the port profile conflicts with the configurations that exist outside the port profile, the commands configured for an interface in configuration terminal mode have higher priority than the commands OL

34 About Port Profiles Configuring Ethernet Interfaces in the port profile. If changes are made to the interface configuration after a port profile is attached to it, and the configuration conflicts with that in the port profile, the configurations in the interface will be given priority. You inherit the port profile when you attach the port profile to an interface or range of interfaces, When you attach, or inherit, a port profile to an interface or range of interfaces, the switch applies all the commands in that port profile to the interfaces. You can have one port profile inherit the settings from another port profile. Inheriting another port profile allows the initial port profile to assume all of the commands of the second, inherited, port profile that do not conflict with the initial port profile. Four levels of inheritance are supported. The same port profile can be inherited by any number of port profiles. To apply the port profile configurations to the interfaces, you must enable the specific port profile. You can configure and inherit a port profile onto a range of interfaces prior to enabling the port profile;; you then enable that port profile for the configurations to take effect on the specified interfaces. When you remove a port profile from a range of interfaces, the switch undoes the configuration from the interfaces first and then removes the port profile link itself. When you remove a port profile, the switch checks the interface configuration and either skips the port profile commands that have been overridden by directly entered interface commands or returns the command to the default value. If you want to delete a port profile that has been inherited by other port profiles, you must remove the inheritance before you can delete the port profile. You can choose a subset of interfaces from which to remove a port profile from among that group of interfaces that you originally applied the profile. For example, if you configured a port profile and configured ten interfaces to inherit that port profile, you can remove the port profile from just some of the specified ten interfaces. The port profile continues to operate on the remaining interfaces to which it is applied. If you delete a specific configuration for a specified range of interfaces using the interface configuration mode, that configuration is also deleted from the port profile for that range of interfaces only. For example, if you have a channel group inside a port profile and you are in the interface configuration mode and you delete that port channel, the specified port channel is also deleted from the port profile as well. After you inherit a port profile on an interface or range of interfaces and you delete a specific configuration value, that port profile configuration will not operate on the specified interfaces. If you attempt to apply a port profile to the wrong type of interface, the switch returns an error. When you attempt to enable, inherit, or modify a port profile, the switch creates a checkpoint. If the port profile configuration fails, the switch rolls back to the prior configuration and returns an error. A port profile is never only partially applied. Guidelines and Limitations for Port Profiles Port profiles have the following configuration guidelines and limitations: Each port profile must have a unique name across interface types and the network. Commands that you enter under the interface mode take precedence over the port profile s commands if there is a conflict. However, the port profile retains that command in the port profile. The port profile s commands take precedence over the default commands on the interface, unless the default command explicitly overrides the port profile command. After you inherit a port profile onto an interface or range of interfaces, you can override individual configuration values by entering the new value at the interface configuration level. If you remove the 12 OL

35 Configuring Ethernet Interfaces About the Debounce Timer Parameters individual configuration values at the interface configuration level, the interface uses the values in the port profile again. There are no default configurations associated with a port profile. A subset of commands are available under the port profile configuration mode, depending on which interface type that you specify. You cannot use port profiles with Session Manager. About the Debounce Timer Parameters The port debounce time is the amount of time that an interface waits to notify the supervisor of a link going down. During this time, the interface waits to see if the link comes back up. The wait period is a time when traffic is stopped. You can enable the debounce timer for each interface and specify the delay time in milliseconds. Caution When you enable the port debounce timer the link up and link down detections are delayed, resulting in a loss of traffic during the debounce period. This situation might affect the convergence and reconvergence of some protocols. About MTU Configuration The Cisco Nexus 5000 Series switch does not fragment frames. As a result, the switch cannot have two ports in the same Layer 2 domain with different maximum transmission units (MTUs). A per-physical Ethernet interface MTU is not supported. Instead, the MTU is set according to the QoS classes. You modify the MTU by setting Class and Policy maps. When you show the interface settings, a default MTU of 1500 is displayed for physical Ethernet interfaces and a receive data field size of 2112 is displayed for Fibre Channel interfaces. Configuring Ethernet Interfaces The section includes the following topics: Configuring a Layer 3 Interface on a Cisco Nexus 5500 Platform Switch Beginning with NX-OS Release 5.0(3)N1(1), on Cisco Nexus 5000 Platform switches, you can configure a Layer 3 interface. You can change a Layer 3 interface into a Layer 2 interface by using the switchport command. You can change a Layer 2 interface into a Layer 3 interface by using the no switchport command. OL