Download
Share
Print this page
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Recording Equipment
  5. 7604-RSP720C-R
  6. Configuration manual

Cisco 7604-RSP720C-R Configuration Manual

Nx-os interfaces
Hide thumbs

Advertisement

Quick Links

Download this manual
Table of Contents
S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m
Cisco Nexus 7000 Series NX-OS Interfaces
Configuration Guide, Release 5.x
June 22, 2012
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-23435-03

Advertisement

Table of Contents
loading

  Related Manuals for Cisco 7604-RSP720C-R

  Summary of Contents for Cisco 7604-RSP720C-R

  • Page 1 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...
  • Page 2 OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks.

  • Page 3: Table Of Contents

    C H A P T E R Information About the Basic Interface Parameters Description Beacon MDIX Debounce Timer Error Disabled Rate Mode Speed Mode and Duplex Mode Flow Control Port MTU Size Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 4 Monitoring the Interface Counters 2-54 Displaying Interface Statistics 2-54 Clearing Interface Counters 2-56 Additional References 2-56 Related Documents 2-57 Standards 2-57 Feature History for Configuring Basic Interface Parameters 2-57 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 5 3-24 Standards 3-24 MIBs 3-25 Feature History for Configuring Layer 2 Interfaces 3-25 Configuring Layer 3 Interfaces C H A P T E R Information About Layer 3 Interfaces Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 6 Configuring Bidirectional Forwarding Detection C H A P T E R Information About BFD Asynchronous Mode BFD Detection of Failures Distributed Operation BFD Echo Function Security High Availability Virtualization Support Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 7 High Availability 6-13 Licensing Requirements for Port Channeling 6-14 Prerequisites for Port Channeling 6-14 Guidelines and Limitations 6-14 Default Settings 6-15 Configuring Port Channels 6-15 Creating a Port Channel 6-16 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 8 Peer-Keepalive Link and Messages 7-11 vPC Peer-Gateway 7-12 vPC Domain 7-13 vPC Topology 7-14 Compatibility Parameters for vPC Interfaces 7-15 vPC Number 7-18 Moving Other Port Channels into a vPC 7-18 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x viii OL-23435-03...
  • Page 9 Standards 7-60 MIBs 7-60 Feature History for Configuring vPCs 7-60 Configuring IP Tunnels C H A P T E R Information About IP Tunnels IP Tunnel Overview GRE Tunnels Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 10 Configuring Thresholds for Layer 2 Protocol Tunnel Ports 9-14 Verifying the Q-in-Q Configuration 9-16 Configuration Examples for Q-in-Q and Layer 2 Protocol Tunneling 9-16 Feature History for Q-in-Q Tunnels and Layer 2 Protocol Tunneling 9-17 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 11 IETF RFCs supported by Cisco NX-OS Interfaces A P P E N D I X IPv6 RFCs Configuration Limits for Cisco NX-OS Interfaces A P P E N D I X N D E X Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 12 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 13: New And Changed Information

    Cisco website: http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/interfaces/configuration/guide/if_ cli.html To check for additional information about Cisco NX--OS Release 5.x, see the Cisco Nexus 7000 Series NX-OS Release Notes, Release 5.x. Release notes are available at the following Cisco website: http://www.cisco.com/en/US/products/ps9402/prod_release_notes_list.html Table 1 summarizes the new and changed features for the Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x, and tells you where they are documented.
  • Page 14 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Table 1 New and Changed Features for Cisco NX--OS Release 5.x (continued) Changed in...

  • Page 15: Document Organization

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Preface This preface describes the audience, organization and conventions of the Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x. It also provides information on how to obtain related documentation.

  • Page 16: Document Conventions

    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. Notes contain helpful suggestions or references to material not covered in the Note manual. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 17: Obtaining Documentation And Submitting A Service Request

    Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Subscribe to the What’s New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
  • Page 18 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 19: Information About Interfaces

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m C H A P T E R Overview This chapter provides an overview of the interface types supported by the Cisco NX-OS software. This chapter includes the following sections: Information About Interfaces, page 1-1 •...

  • Page 20: Chapter 1 Overview

    GRE Tunneling Chapter 8, “Configuring IP Tunnels” of this document Security Dot1X, NAC, EOU, port security Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 5.x FCoE Beginning with Cisco NX-OS Cisco NX-OS FCoE Configuration Guide for Release 5.2(1), you can run Fibre...

  • Page 21: Management Interface

    PVLAN promiscuous port, which provides routing functionality to the primary PVLAN. For more information on configuring PVLAN host and PVLAN promiscuous ports and all other PVLAN configurations, see the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x.

  • Page 22: Port-Channel Interfaces

    Chapter 6, “Configuring Port Channels.” vPCs Virtual port channels (vPCs) allow links that are physically connected to two different Cisco Nexus 7000 series devices to appear as a single port channel by a third device. The third device can be a switch, server, or any other networking device.

  • Page 23: Virtualization Interfaces

    Once an interface is allocated to a VDC, you can only configure that interface if you are in the correct VDC. For more information on VDCs, see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 5.x.
  • Page 24 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...
  • Page 25 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m C H A P T E R Configuring Basic Interface Parameters This chapter describes how to configure the basic interface parameters on Cisco NX-OS devices. This chapter includes the following sections: Information About the Basic Interface Parameters, page 2-2 •...

  • Page 26: Information About The Basic Interface Parameters

    By default, this mode is disabled. To identify the physical port for an interface, you can activate the beacon parameter for the interface. For information on configuring the beacon parameter, see the “Configuring the Beacon Mode” section on page 2-17. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 27: C H A P T E R 2 Configuring Basic Interface Parameters

    Use the show interface status err-disabled command to display the reason behind the error. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 28: Rate Mode

    Note All ports in each port group must be part of the same virtual device context (VDC). For more information on VDCs, see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 5.x. Speed Mode and Duplex Mode The speed mode and duplex mode are interrelated for each Ethernet and management interface.

  • Page 29: Flow Control

    If you set one of the flow control states to disabled, flow control is disabled for that transmission direction. To see how the different port flow-control states affect the link flow-control state, see Table 2-3. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 30: Port Mtu Size

    (1500 bytes) unless you specify the new system jumbo MTU size for some or all of those ports. For information on setting the MTU size, see the “Configuring the MTU Size” section on page 2-31. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 31: Bandwidth

    Unidirectional Link Detection Parameter This section includes the following topics: UDLD Overview, page 2-8 • Default UDLD Configuration, page 2-9 • • UDLD Aggressive and Nonaggressive Modes, page 2-9 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 32 Layer 1. The Cisco Nexus 7000 Series device periodically transmits UDLD frames to neighbor devices on LAN ports with UDLD enabled. If the frames are echoed back within a specific time frame and they lack a specific acknowledgment (echo), the link is flagged as unidirectional and the LAN port is shut down.
  • Page 33 This is correct behavior. To restore service after the ISSU has completed, run a shutdown followed by a no shutdown command on the local port. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 34: Carrier Delay

    “Configuring Port Channels.” Port Profiles Beginning with Cisco NX-OS Release 4.2(1) for the Cisco Nexus 7000 Series devices, you can create a port profile that contains many interface commands and apply that port profile to a range of interfaces. Each port profile can be applied only to a specific type of interface; the choices are as follows: •...
  • Page 35 A subset of commands are available under the port-profile configuration mode, depending on which interface type you specify. You cannot use port profiles with Session Manager. See the Cisco Nexus 7000 Series NX-OS System Note Management Configuration Guide, Release 5.x, for information about Session Manager.

  • Page 36: Time Domain Reflectometry Cable Diagnostics

    The basic interface parameters require no 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 37: Guidelines And Limitations

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Guidelines and Limitations Basic interface parameters have the following configuration guidelines and limitations: Fiber-optic Ethernet ports must use Cisco-supported transceivers. To verify that the ports are using • Cisco-supported transceivers, use the show interface transceivers command. Interfaces with Cisco-supported transceivers are listed as functional interfaces.

  • Page 38: Default Settings

    Configuring the MDIX Parameter, page 2-25 • • Configuring the Debounce Timer, page 2-26 • Configuring the Interface Speed and Duplex Mode, page 2-28 • Configuring the Flow Control, page 2-30 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-14 OL-23435-03...

  • Page 39: Specifying The Interfaces To Configure

    2/29.1-2. But you cannot specify the subinterfaces in a range of ports, for example, you cannot enter 2/29.2-2/30.2. You can specify two of the subinterfaces discretely, for example, you can enter 2/29.2, 2/30.2. SUMMARY STEPS configure terminal Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-15 OL-23435-03...

  • Page 40: Configuring The Description

    You can provide textual interface descriptions for the Ethernet and management interfaces. Descriptions can be a maximum of 80 case-sensitive, alphanumeric characters. SUMMARY STEPS configure terminal interface interface description text show interface interface exit copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-16 OL-23435-03...

  • Page 41: Configuring The Beacon Mode

    Configuring the Beacon Mode You can enable the beacon mode for an Ethernet port to flash its LED to confirm its physical location. SUMMARY STEPS configure terminal interface ethernet slot/port Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-17 OL-23435-03...
  • Page 42 This example shows how to disable the beacon mode for the Ethernet port 3/1: switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# no beacon switch(config-if)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-18 OL-23435-03...

  • Page 43: Changing The Bandwidth-Rate Mode

    The example shows how to specify one 3/3, ethernet 3/5, ethernet 3/7 port for the dedicated mode. switch(config-if)# Step 3 Administratively shuts down the ports. shutdown Example: switch(config)# shutdown Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-19 OL-23435-03...
  • Page 44 BEFORE YOU BEGIN All ports in the same group must belong to the same VDC. SUMMARY STEPS configure terminal interface ethernet slot/port Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-20 OL-23435-03...
  • Page 45 Brings the ports administratively up. no shutdown Example: switch(config-if)# no shutdown Step 7 Displays the interface information show interface ethernet slot/port including the current rate mode. Example: switch(config)# show interface ethernet 3/1 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-21 OL-23435-03...

  • Page 46: Configuring The Error-Disabled State

    SUMMARY STEPS configure terminal errdisable detect cause {acl-exception | all | link-flap | loopback} shutdown no shutdown show interface status err-disabled copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-22 OL-23435-03...
  • Page 47 SUMMARY STEPS configure terminal errdisable recovery cause {all | bpdguard | link-flap | psecure-violation | security-violation | storm-control | udld} show interface status err-disabled copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-23 OL-23435-03...
  • Page 48 Configuring the Error-Disabled Recovery Interval You can configure the error-disabled recovery timer value. SUMMARY STEPS configure terminal errdisable recovery interval interval show interface status err-disabled copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-24 OL-23435-03...

  • Page 49: Configuring The Mdix Parameter

    You must enable MDIX for the remote port. SUMMARY STEPS configure terminal interface ethernet slot/port {mdix auto} | {no mdix} show interface ethernet slot/port exit copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-25 OL-23435-03...

  • Page 50: Configuring The Debounce Timer

    (ms), or disable the timer by specifying a debounce time of 0. You can show the debounce times for all of the Ethernet ports by using the show interface debounce command. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-26 OL-23435-03...
  • Page 51 3/1 switch(config-if)# link debounce time 1000 switch(config-if)# This example shows how to disable the debounce timer for the Ethernet port 3/1: switch# configure terminal switch(config)# interface ethernet 3/1 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-27 OL-23435-03...

  • Page 52: Configuring The Interface Speed And Duplex Mode

    {{10 | 100 | 1000 | {auto [10 100 [1000]]}} | {10000 | auto}} duplex {full | half | auto} show interface interface exit copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-28 OL-23435-03...
  • Page 53 This example shows how to set the speed of Ethernet port 1 on the 48-port 10/100/1000 module in slot 3 to 1000 Mb/s and full-duplex mode: Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-29 OL-23435-03...

  • Page 54: Configuring The Flow Control

    SUMMARY STEPS configure terminal interface ethernet slot/port flowcontrol {send | receive} {desired | on | off} show interface ethernet slot/port show interface flowcontrol exit copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-30 OL-23435-03...

  • Page 55: Configuring The Mtu Size

    For Layer 2 interfaces, you can configure the MTU to be either the system default MTU (1500 bytes) or the system jumbo MTU size (which has the default size of 9216 bytes). Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-31...
  • Page 56 MTU value for Layer 2 interfaces, those interfaces will use the system default MTU (1500 bytes). By default, Cisco NX-OS configures Layer 3 parameters. If you want to configure Layer 2 parameters, you need to switch the port mode to Layer 2.
  • Page 57 You can specify an even number between 1500 and 9216. If you do not configure the system jumbo MTU size, it defaults to 9216 bytes. SUMMARY STEPS configure terminal system jumbomtu size show running-config all interface type slot/port mtu size exit copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-33 OL-23435-03...

  • Page 58: Configuring The Bandwidth

    You can configure the bandwidth for Ethernet interfaces. The physical level uses an unchangeable bandwidth of 1 GB, but you can configure a value of 1 to 10,000,000 Kb for Level 3 protocols. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-34...
  • Page 59 This example shows how to configure an informational value of 1,000,000 Kb for the Ethernet slot 3, port 1 interface bandwidth parameter: switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# bandwidth 1000000 switch(config-if)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-35 OL-23435-03...

  • Page 60: Configuring The Throughput Delay

    Exits the interface mode. exit Example: switch(config-if)# exit switch(config)# Step 6 (Optional) Copies the running copy running-config startup-config configuration to the startup Example: configuration. switch(config)# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-36 OL-23435-03...

  • Page 61: Shutting Down And Activating The Interface

    To activate the interface, you must restart the device. SUMMARY STEPS configure terminal interface interface shutdown show interface interface no shutdown show interface interface exit copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-37 OL-23435-03...
  • Page 62 This example shows how to change the administrative status for Ethernet port 3/1 from disabled to enabled: switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# shutdown switch(config-if)# no shutdown switch(config-if)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-38 OL-23435-03...

  • Page 63: Configuring The Udld Mode

    {enable | disable} show udld [ethernet slot/port | global | neighbors} exit copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-39 OL-23435-03...
  • Page 64 Table 2-7 for more details. Step 7 (Optional) Displays the UDLD status. show udld [ethernet slot/port | global | neighbors] Example: switch(config)# show udld switch(config)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-40 OL-23435-03...

  • Page 65: Configuring The Carrier Delay Timer

    When you configure a longer carrier delay time, fewer link-down/link-up events are recorded. When you configure the carrier delay time to 0, the device detects each link-down/link-up event. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-41 OL-23435-03...
  • Page 66 Exits the interface mode. exit Example: switch(config-if)# exit switch(config)# Step 6 (Optional) Copies the running copy running-config startup-config configuration to the startup Example: configuration. switch(config)# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-42 OL-23435-03...

  • Page 67: Configuring Port Profiles

    You can create a port profile on the device. Each port profile must have a unique name across types and the network. SUMMARY STEPS configure terminal port-profile [type {ethernet | interface-vlan | loopback | port channel | tunnel}] name exit show port-profile copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-43 OL-23435-03...

  • Page 68: Entering Port-Profile Configuration Mode And Modifying A Port Profile

    SUMMARY STEPS configure terminal port-profile [type {ethernet | interface-vlan | loopback | port channel | tunnel}] name exit show port-profile copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-44 OL-23435-03...

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

    SUMMARY STEPS configure terminal interface [ethernet slot/port | interface-vlan vlan-id | loopback number | port-channel number | tunnel number] inherit port-profile name exit show port-profile copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-45 OL-23435-03...

  • Page 70: Enabling A Specific Port Profile

    If you inherit one or more port profiles onto an original port profile, only the last inherited port profile must be enabled; the system assumes that the underlying port profiles are enabled. You must be in the port-profile configuration mode to enable or disable port profiles. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-46 OL-23435-03...

  • Page 71: Inheriting A Port Profile

    Inheriting a Port Profile You can inherit a port profile onto an existing port profile. The system supports four levels of inheritance. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-47 OL-23435-03...

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

    You can remove a port profile from some or all of the interfaces to which you have applied the profile. You do this in the interfaces configuration mode. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-48 OL-23435-03...
  • Page 73 This example shows how to remove the port profile named adam from Ethernet interfaces 7/3 to 7/5, 10/2, and 11/20 to 11/25: switch# configure terminal switch(config)# interface ethernet 7/3-5, 10/2, 11/20-25 switch(config-if)# no inherit port-profile adam switch(config-if)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-49 OL-23435-03...

  • Page 74: Removing An Inherited Port Profile

    This example shows how to remove the inherited port profile named adam from the port profile named test: switch# configure terminal switch(config)# port-profile test switch(config-ppm)# no inherit port-profile adam switch(config-ppm)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-50 OL-23435-03...

  • Page 75: Performing Tdr Cable Diagnostics

    3/12 is a good cable and connection. switch(config)# interface ethernet 3/1-12 switch(config-if-range)# shutdown switch# test cable-diagnostics tdr interface ethernet 3/1 switch# test cable-diagnostics tdr interface ethernet 3/12 switch# show interface ethernet 3/1 cable-diagnostics-tdr Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-51 OL-23435-03...

  • Page 76: Configuring Rate Limits For Packets That Reach The Supervisor

    Terminated Configuring Rate Limits for Packets that Reach the Supervisor Beginning with Cisco NX-OS Release 5.1, you can configure rate limits globally on the device for Note packets that reach the supervisor module. For more information, see the Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 5.x.
  • Page 77 Packet rate limiter (Out/In): 1000 pps / 1000 pps Average packet rates(1min/5min/15min/EWMA): Packet statistics: Tx: Unicast 0, Multicast 528 Broadcast 0 Rx: Unicast 0, Multicast 0 Broadcast 0 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-53 OL-23435-03...

  • Page 78: Verifying The Basic Interface Parameters

    For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Interfaces Command Reference, Release 5.x. Monitoring the Interface Counters You can display and clear interface counters using Cisco NX-OS.
  • Page 79 This example shows how to set the three sample intervals for the Ethernet port 3/1: switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# load-interval counter 1 60 switch(config-if)# load-interval counter 2 135 switch(config-if)# load-interval counter 3 225 switch(config-if)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-55 OL-23435-03...

  • Page 80: Clearing Interface Counters

    For additional information related to implementing Feature-1, see the following sections: Related Documents, page 2-57 • Standards, page 2-57 • • Feature History for Configuring Basic Interface Parameters, page 2-57 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-56 OL-23435-03...

  • Page 81: Related Documents

    Feature Name Releases Feature Information Port profiles 4.2(1) Allows you to apply several configurations to a range of interfaces at once. Basic interface settings 4.0(1) These features were introduced. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 2-57 OL-23435-03...
  • Page 82 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 83: Chapter 3 Configuring Layer 2 Interfaces

    This chapter describes how to configure Layer 2 switching ports as access or trunk ports on Cisco NX-OS devices. Beginning with Cisco NX-OS Release 5.1, a Layer 2 port can function as either one of the following: Note A trunk port •...

  • Page 84: Information About Access And Trunk Interfaces

    Note information on VLANs, MAC address tables, private VLANs, and the Spanning Tree Protocol. A Layer 2 port can function as either a trunk port, an access port, or a private VLAN port. See the Cisco Note Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more information on private VLANs.

  • Page 85: Information About Access And Trunk Interfaces

    To configure the port as a Layer 2 port using the CLI, use the switchport command, All ports in one trunk must be in the same virtual device context (VDC). See the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 5.x, for information on VDCs.

  • Page 86: Ieee 802.1Q Encapsulation

    When you change a Layer 2 interface back to a Layer 3 interface, that interface loses all the Layer 2 configuration and resumes the default VLAN configurations. IEEE 802.1Q Encapsulation For information about VLANs, see the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Note Guide, Release 5.x.

  • Page 87: Access Vlans

    VLAN will also receive all the broadcast traffic for the primary VLAN in the private VLAN mode. See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for Note complete information on private VLANs.

  • Page 88: Native Vlan Ids For Trunk Ports

    Tagging Native VLAN Traffic The Cisco software supports the IEEE 802.1Q standard on trunk ports. In order to pass untagged traffic through the trunk ports, you must create a VLAN that does not tag any packets (or you can use the default VLAN).

  • Page 89: High Availability

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Beginning with Cisco Release 5.2, you can change the block of VLANs reserved for internal use. See Note the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more...

  • Page 90: Licensing Requirements For Layer 2 Port Modes

    Layer 2 port modes require no 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 91: Default Settings

    802.1Q cloud that separates the Cisco devices is treated as a single broadcast segment between all devices connected to the non-Cisco 802.1Q cloud through 802.1Q trunks. Make certain that the native VLAN is the same on all of the 802.1Q trunks that connect the Cisco •...

  • Page 92: Guidelines For Configuring Access And Trunk Interfaces

    Changing the System Default Port Mode to Layer 2, page 3-21 • Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use. Guidelines for Configuring Access and Trunk Interfaces All VLANs on a trunk must be in the same VDC.

  • Page 93: Configuring Access Host Ports

    5 switch(config-if)# Configuring Access Host Ports Note You should apply the switchport host command only to interfaces connected to an end station. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-11 OL-23435-03...
  • Page 94 Example: switch(config-if)# switchport host Apply this command only to end stations. Note Step 4 Exits the interface mode. exit Example: switch(config-if)# exit switch(config)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-12 OL-23435-03...

  • Page 95: Configuring Trunk Ports

    Before you configure a trunk port, ensure that you are configuring a Layer 2 interface. SUMMARY STEPS configure terminal interface {type slot/port | port-channel number} switchport mode {access | trunk} exit (Optional) show interface (Optional) copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-13 OL-23435-03...

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

    You can configure the native VLAN for 802.1Q trunk ports. If you do not configure this parameter, the trunk port uses the default VLAN as the native VLAN ID. You cannot configure an FCoE VLAN as a native VLAN for an Ethernet interface. Note Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-14 OL-23435-03...
  • Page 97 This example shows how to set the native VLAN for the Ethernet 3/1, Layer 2 trunk port to VLAN 5: switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# switchport trunk native vlan 5 switch(config-if)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-15 OL-23435-03...

  • Page 98: Configuring The Allowed Vlans For Trunking Ports

    Before you configure the allowed VLANs for the specified trunk ports, ensure that you are configuring the correct interfaces and that the interfaces are trunks. Beginning with Cisco Release 5.2, you can change the block of VLANs reserved for internal use. See Note the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more...

  • Page 99: Configuring A Default Interface

    The default interface feature is not supported for management interfaces because the device could go to Note an unreachable state. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-17 OL-23435-03...

  • Page 100: Configuring Svi Autostate Exclude

    You can use the Autostate Exclude option to enable or disable the port from bringing up or down the SVI calculation and applying it to all VLANs that are enabled on the selected port. SUMMARY STEPS configure terminal interface {{type slot/port} | {port-channel number}} Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-18 OL-23435-03...
  • Page 101 Example: switch(config)# copy running-config startup-config This example shows how to exclude a port from the VLAN interface link-up calculation on the Cisco NX-OS device: switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# switchport switch(config-if)# switchport autostate exclude Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 102: Configuring The Device To Tag Native Vlan Traffic

    IDs in different VDCs, so you must confirm that you are working in the correct VDC. SUMMARY STEPS configure terminal vlan dot1q tag native exit (Optional) show vlan (Optional) copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-20 OL-23435-03...

  • Page 103: Changing The System Default Port Mode To Layer 2

    You can set the system default port mode to Layer 2 access ports. See the Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 for information on setting the system default port mode to Fibre Channel in storage VDCs.

  • Page 104: Verifying The Interface Configuration

    Layer 2 interfaces. show interface trunk [module module-number | Displays trunk configuration information. vlan vlan-id] show interface capabilities Displays information on the capabilities of the interfaces. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-22 OL-23435-03...

  • Page 105: Monitoring The Layer 2 Interfaces

    Displays configuration information about the slot/port specified port-channel interface. For detailed information about these commands, see the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Command Reference, Release 5.x. Monitoring the Layer 2 Interfaces Use the following commands to display layer 2 interfaces:...

  • Page 106: Additional References

    Cisco Nexus 7000 Series NX-OS Release Notes, Release 5.x Standards Standards Title No new or modified standards are supported by this — feature, and support for existing standards has not been modified by this feature. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-24 OL-23435-03...

  • Page 107: Mibs

    SVI autostate exclude 5.2(1) Added the switchport autostate exclude command to prevent a port’s state from affecting the up or down state of the SVI. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 3-25 OL-23435-03...
  • Page 108 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 109: Information About Layer 3 Interfaces

    Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 for information on shared interfaces. Beginning with Cisco Release 5.2(1), you can configure a Fabric Extender (FEX) port as a Layer 3 interface for host connectivity, but not for routing. See the Configuring the Cisco Nexus 2000 Series Fabric Extender for more information on fabric extenders.

  • Page 110: Chapter 4 Configuring Layer 3 Interface

    Beginning with Cisco Release 4.2(1), you can assign a static MAC address to a Layer 3 interface. By default, the MAC address for the Layer 3 interfaces is the MAC address of the VDC it is assigned to.

  • Page 111: Vlan Interfaces

    VLAN that you want to route traffic to and assigning an IP address on the VLAN interface. For more information on IP addresses and IP routing, see the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x.

  • Page 112: Loopback Interfaces

    Tunnel Interfaces Cisco NX-OS supports tunnel interfaces as IP tunnels. IP tunnels can encapsulate a same-layer or higher layer protocol and transport the result over IP through a tunnel created between two routers. See Chapter 8, “Configuring IP Tunnels,”...

  • Page 113: Virtualization Support

    Layer 3 interfaces require no 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 114: Default Settings

    • Layer 3 router interfaces and sub-interfaces can not be configured on an F1 I/O module. If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature Note might differ from the Cisco IOS commands that you would use.
  • Page 115 Use the medium command to set the interface medium to either point to point or broadcast. Command Purpose Configures the interface medium as either point to medium {broadcast | p2p} point or broadcast. Example: switch(config-if)# medium p2p Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 116: Configuring A Subinterface

    Ensure that you are in the correct VDC (or use the switchto vdc command). SUMMARY STEPS configure terminal interface ethernet slot/port.number ip address ip-address/length ipv6 address ipv6-address/length encapsulation dot1q vlan-id (Optional) show interfaces (Optional) copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 117: Configuring The Bandwidth On An Interface

    You can configure the bandwidth on a subinterface with one of the following methods: Explicit—Set the bandwidth value for the subinterface directly. • Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 118: Configuring A Vlan Interface

    You can create VLAN interfaces to provide inter-VLAN routing. BEFORE YOU BEGIN Ensure that you are in the correct VDC (or use the switchto vdc command). SUMMARY STEPS configure terminal feature interface-vlan interface vlan number Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 4-10 OL-23435-03...
  • Page 119 This example shows how to create a VLAN interface: switch# configure terminal switch(config)# feature interface-vlan switch(config)# interface vlan 10 switch(config-if)# ip address 192.0.2.1/8 switch(config-if)# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 4-11 OL-23435-03...

  • Page 120: Configuring Inband Management In The Nexus Chassis

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Configuring Inband Management in the Nexus Chassis You can a create VLAN interface for inband management in the Cisco Nexus 7000 Series switches when there are only F1 Series modules in the chassis.
  • Page 121 (Optional) Saves this configuration change. copy running-config startup-config Example: switch(config-if)# copy running-config startup-config This example shows how to create an inband management in the Cisco Nexus 7000 chassis: switch# configure terminal switch(config)# feature interface-vlan switch(config)# interface vlan 5 switch(config)# no shutdown switch(config)# management switch(config-if)# ip address 192.0.2.1/8...

  • Page 122: Configuring A Loopback Interface

    Example: switch(config)# interface loopback 0 switch(config-if)# Step 3 Configures an IP address for this interface. See the Cisco ip address ip-address/length Nexus 7000 Series NX-OS Unicast Routing Configuration Example: Guide, Release 5.x, for more information on IP addresses.

  • Page 123: Assigning An Interface To A Vrf

    Configures an IP address for this interface. You must ip address ip-prefix/length do this step after you assign this interface to a VRF. Example: switch(config-if)# ip address 192.0.2.1/16 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 4-15 OL-23435-03...

  • Page 124: Verifying The Layer 3 Interfaces Configuration

    Displays the loopback interface configuration, status, and counters. show interface loopback number brief Displays the loopback interface operational status. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 4-16 OL-23435-03...

  • Page 125: Monitoring Layer 3 Interfaces

    Displays the port-channel subinterface statistics counters (unicast, multicast, and broadcast). show interface loopback number counters Displays the loopback interface input and output counters (unicast, multicast, and broadcast). Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 4-17 OL-23435-03...

  • Page 126: Configuration Examples For Layer 3 Interfaces

    Displays the VLAN interface counters reported by SNMP MIBs. You cannot clear these counters. See the Cisco Nexus 7000 Series NX-OS Interfaces Command Reference, Release 5.x, for information on these commands. Configuration Examples for Layer 3 Interfaces This example shows how to configure Ethernet subinterfaces: interface ethernet 2/1.10...

  • Page 127: Related Documents

    Document Title command syntax Cisco Nexus 7000 Series NX-OS Interfaces Command Reference, Release 5.x “Configuring IP” chapter in the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x VLANs “Configuring VLANs” chapter in the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x...
  • Page 128 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 129: Information About Bfd

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m C H A P T E R Configuring Bidirectional Forwarding Detection This chapter describes how to configure Bidirectional Forwarding Detection (BFD) on Cisco NX-OS devices. This chapter includes the following sections: Information About BFD, page 5-1 •...

  • Page 130: C H A P T E R 5 Configuring Bidirectional Forwarding Detection

    • Asynchronous Mode Cisco NX-OS supports the BFD asynchronous mode, which sends BFD control packets between two adjacent devices to activate and maintain BFD neighbor sessions between the devices. You configure BFD on both devices (or BFD neighbors). Once BFD has been enabled on the interfaces and on the appropriate protocols, Cisco NX-OS creates a BFD session, negotiates BFD session parameters, and begins to send BFD control packets to each BFD neighbor at the negotiated interval.

  • Page 131: Distributed Operation

    Router B Distributed Operation Cisco NX-OS can distribute the BFD operation to compatible modules that support BFD. This process offloads the CPU load for BFD packet processing to the individual modules that connect to the BFD neighbors. All BFD session traffic occurs on the module CPU. The module informs the supervisor when a BFD failure is detected.

  • Page 132: Security

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Security Cisco NX-OS uses the packet Time to Live (TTL) value to verify that the BFD packets came from an adjacent BFD peer. For all asynchronous and echo request packets, the BFD neighbor sets the TTL value to 255 and the local BFD process verifies the TTL value as 255 before processing the incoming packet.

  • Page 133: Guidelines And Limitations

    If you enable BFD at the router level (for example, from OSPF), any BFD sessions over a N7K-F132XL-15 linecard will not come-up. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x for information about OSPF and other routing protocols.

  • Page 134: Default Settings

    • HSRP for IPv4 is supported with BFD. HSRP for IPv6 is not supported with BFD. BFD packets generated by supported the Cisco NX-OS device linecards are sent with COS 6/DSCP • CS6. The DSCP/COS values for BFD packets are not user configurable.

  • Page 135: Configuration Hierarchy

    Ensure that you are in the correct VDC (or use the switchto vdc command). SUMMARY STEPS configure terminal feature bfd (Optional) show feature | include bfd (Optional) copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 136: Configuring Global Bfd Parameters

    Enable the BFD feature. See the “Enabling the BFD Feature” section on page 5-7. SUMMARY STEPS configure terminal bfd interval mintx min_rx msec multiplier value bfd slow-timer [interval] (Optional) show running-config bfd Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 137: Configuring Bfd On An Interface

    BEFORE YOU BEGIN Ensure that you are in the correct VDC (or use the switchto vdc command). Enable the BFD feature. See the “Enabling the BFD Feature” section on page 5-7. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 138 (Optional) Displays the BFD running configuration. show running-config bfd Example: switch(config-if)# show running-config Step 6 (Optional) Saves this configuration change. copy running-config startup-config Example: switch(config-if)# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 5-10 OL-23435-03...

  • Page 139: Configuring Bfd On A Port Channel

    Example: switch(config)# interface port-channel 2 switch(config-if)# Step 3 Configures the BFD sessions for each link in the port bfd per-link channel. Example: switch(config-if)# bfd per-link Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 5-11 OL-23435-03...

  • Page 140: Configuring Bfd Echo Function

    Ensure that the IP packet verification check for identical IP source and destination addresses is disabled. Use the no hardware ip verify address identical command in the default VDC. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for more information on this command.

  • Page 141: Optimizing Bfd On Subinterfaces

    BFD session parameters of the parent interface. The remaining subinterfaces use the slow timer. If the optimized subinterface session detects an error, BFD marks all subinterfaces on that physical interface as down. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 5-13 OL-23435-03...

  • Page 142: Configuring Bfd Support For Routing Protocols

    “Configuring Global BFD Parameters” section on page 5-8 or the “Configuring BFD on an Interface” section on page 5-9. Ensure that these subinterfaces connect to another Cisco NX-OS device. This feature is supported on Cisco NX-OS only. SUMMARY STEPS configure terminal interface int-if...
  • Page 143 5-8 or the “Configuring BFD on an Interface” section on page 5-9. Enable the BGP feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for more information. SUMMARY STEPS configure terminal router bgp as-number...

  • Page 144: Configuring Bfd On Eigrp

    5-8 or the “Configuring BFD on an Interface” section on page 5-9. Enable the EIGRP feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for more information. SUMMARY STEPS configure terminal router eigrp instance-tag Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...
  • Page 145 32 characters. Example: switch(config-if)# show ip eigrp Step 7 (Optional) Saves this configuration change. copy running-config startup-config Example: switch(config-if)# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 5-17 OL-23435-03...

  • Page 146: Configuring Bfd On Ospf

    5-8 or the “Configuring BFD on an Interface” section on page 5-9. Enable the OSPF feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for more information. SUMMARY STEPS configure terminal router ospf instance-tag...

  • Page 147: Configuring Bfd On Is-Is

    5-8 or the “Configuring BFD on an Interface” section on page 5-9. Enable the IS-IS feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for more information. SUMMARY STEPS configure terminal router isis instance-tag...

  • Page 148: Configuring Bfd On Hsrp

    5-8 or the “Configuring BFD on an Interface” section on page 5-9. Enable the HSRP feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for more information. SUMMARY STEPS configure terminal hsrp bfd all-interfaces...

  • Page 149: Configuring Bfd On Vrrp

    5-8 or the “Configuring BFD on an Interface” section on page 5-9. Enable the VRRP feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for more information. SUMMARY STEPS configure terminal Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 150: Configuring Bfd On Pim

    Ensure that you are in the correct VDC (or use the switchto vdc command). Enable the BFD feature. See the “Enabling the BFD Feature” section on page 5-7. Enable the PIM feature. See the Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide, Release 5.x, for more information. SUMMARY STEPS configure terminal...

  • Page 151: Configuring Bfd On Static Routes

    (Optional) vrf context vrf-name ip route route interface if {nh-address | nh-prefix} ip route static bfd interface {nh-address | nh-prefix} (Optional) show ip route static [vrf vrf-name] Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 5-23 OL-23435-03...

  • Page 152: Configuring Bfd On Mpls Te Fast Reroute

    BFD for MPLS TE fast reroute is configured automatically when you enable the fast reroute on a tunnel. “See the Configuring MPLS TE Fast Reroute Link and Node Protection” chapter in the Cisco Nexus 7000 Series NX-OS Multiprotocol Label Switching Configuration Guide, Release 5.x for more information.

  • Page 153: Verifying The Bfd Configuration

    Displays the BFD configuration that will be applied on the next system startup. For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Interfaces Command Reference, Release 5.x. Monitoring BFD...

  • Page 154: Configuration Examples For Bfd

    Additional References For additional information related to implementing BFD, see the following sections: Related Documents, page 5-27 • RFCs, page 5-27 • • Feature History for BFD, page 5-27 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 5-26 OL-23435-03...

  • Page 155: Related Documents

    Feature Information BFD Authentication 5.2(1) Keyed SHA-1 authentication is supported on BFD packets. BFD for VRRP 5.2(1) Added support for BFD in VRRP. 5.0(2) This feature was introduced. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 5-27 OL-23435-03...
  • Page 156 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 157: Information About Port Channels

    The port channel stays operational as long as at least one physical interface within the port channel is operational. Beginning with Cisco NX-OS Release 5.1, you can bundle up to 16 active links into a port channel on Note the F Series module.
  • Page 158 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m You cannot configure a shared interface to be part of a port channel. See the Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 for more information on shared interfaces.

  • Page 159: Chapter 6 Configuring Port Channel

    Beginning with Cisco NX-OS Release 5.1, you can bundle up to 16 active ports simultaneously into a Note port channel on the F Series module.

  • Page 160: Basic Settings

    Beginning with Cisco NX-OS Release 4.2(1), you can configure a Layer 3 port channel with a static MAC address. If you do not configure this value, the Layer 3 port channel uses the router MAC of the first channel member to come up.

  • Page 161: Compatibility Requirements

    For example, you cannot add a Layer 3 interface to a Layer 2 channel group. The Cisco DC-OS software also checks a number of operational attributes for an interface before allowing that interface to participate in the port-channel aggregation.

  • Page 162: Load Balancing Using Port Channels

    Load Balancing Using Port Channels The Cisco DC-OS software load balances traffic across all operational interfaces in a port channel by hashing the addresses in the frame to a numerical value that selects one of the links in the channel. Port channels provide load balancing by default.
  • Page 163 • Multicast traffic with Layer 4 information—Source IP address, source port, destination IP address, destination port Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 164: Lacp

    Non-IP multicast traffic—Source MAC address, destination MAC address • Devices that run Cisco IOS were able to optimize the behavior of the member ports ASICs if a failure Note of a single member occurred by running the port-channel hash-distribution command. The Cisco Nexus 7000 Series device performs this optimization by default and does not require or support this command.
  • Page 165 8 interfaces, the remaining interfaces are in hot standby for the port channel associated with this channel group on the M Series modules. Beginning with Cisco NX-OS Release 5.1, you can bundle up to 16 active links into a port channel on the F Series module.

  • Page 166: Lacp Id Parameters

    MAC address to form the system ID and also uses the system priority during negotiation with other devices. A higher system priority value means a lower priority. The system ID is different for each VDC. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-10 OL-23435-03...

  • Page 167: Lacp Marker Responders

    LACP enabled and static port channels. Table 6-2 Port Channels with LACP Enabled and Static Port Channels Configurations Port Channels with LACP Enabled Static Port Channels Protocol applied Enable globally Not applicable Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-11 OL-23435-03...

  • Page 168: Lacp Compatibility Enhancements

    LACP protocol convergence. When the Cisco Nexus 7000 Series device is connected to a non-Nexus peer, its graceful failover defaults may delay the time taken for a disabled port to be brought down or cause traffic from the peer to be lost.

  • Page 169: Virtualization Support

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m LACP Offload to Fabric Extenders To reduce the load on the control plane of the Cisco Nexus 7000 Series device, Cisco NX-OS provides the ability to offload link-level protocol processing to the Fabric Extender CPU. This is supported by LACP by default as soon as there is at least one LACP port-channel configured on a fabric extender.

  • Page 170: Licensing Requirements For Port Channeling

    License Requirement Cisco NX-OS Port channeling requires no 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 NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide.

  • Page 171: Default Settings

    You cannot configure the ports from a F1 and an M1 series linecard in the same port channel because the ports will fail to meet the compatibility requirements. • Beginning with Cisco NX-OS Release 5.1, you can bundle up to 16 active links into a port channel on the F1 series linecard. Default Settings Table 6-3 lists the default settings for port-channel parameters.

  • Page 172: Creating A Port Channel

    IPv4 and IPv6 addresses on the port-channel interface. If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature Note might differ from the Cisco IOS commands that you would use.

  • Page 173: Adding A Layer 2 Port To A Port Channel

    The software creates the port channel associated with this channel group if the port channel does not already exist. BEFORE YOU BEGIN Enable LACP if you want LACP-based port channels. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-17 OL-23435-03...
  • Page 174 Step 5 (Optional) Configures necessary parameters for a switchport trunk {allowed vlan vlan-id | native vlan-id} Layer 2 trunk port. Example: switch(config-if)# switchport trunk native 3 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-18 OL-23435-03...

  • Page 175: Adding A Layer 3 Port To A Port Channel

    After you create a Layer 3 port channel, you can assign an IP address to the port-channel interface. You can also add subinterfaces to an existing Layer 3 port channel. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-19...
  • Page 176 (Optional) Forces an interface with some incompatible Example: configurations to join the channel. The forced interface switch(config-if)# channel-group 5 force must have the same speed, duplex, and flow control settings as the channel group. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-20 OL-23435-03...

  • Page 177: Configuring The Bandwidth And Delay For Informational Purposes

    You configure the bandwidth and delay on port-channel interfaces for informational purposes. SUMMARY STEPS configure terminal interface port-channel channel-number bandwidth value delay value exit show interface port-channel channel-number copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-21 OL-23435-03...

  • Page 178: Shutting Down And Restarting The Port-Channel Interface

    Shutting Down and Restarting the Port-Channel Interface You can shut down and restart the port-channel interface. When you shut down a port-channel interface, no traffic passes and the interface is administratively down. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-22 OL-23435-03...
  • Page 179 This example shows how to bring up the interface for port channel 2: switch# configure terminal switch (config)# interface port-channel 2 switch(config-if)# no shutdown Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-23 OL-23435-03...

  • Page 180: Configuring A Port-Channel Description

    Example: switch(config)# copy running-config startup-config This example shows how to add a description to port channel 2: switch# configure terminal switch (config)# interface port-channel 2 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-24 OL-23435-03...

  • Page 181: Configuring The Speed And Duplex Settings For A Port-Channel Interface

    {auto | full | half} default is auto for autonegotiation. Example: switch(config-if)# speed auto switch(config-if)# Step 5 Exits the interface mode and returns to the exit configuration mode. Example: switch(config-if)# exit switch(config)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-25 OL-23435-03...

  • Page 182: Configuring Flow Control

    The settings have to match at both the local and remote ends of the link so that flow control can work properly. SUMMARY STEPS configure terminal interface port-channel channel-number flowcontrol receive send desired exit show interface port-channel channel-number copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-26 OL-23435-03...

  • Page 183: Configuring Load Balancing Using Port Channels

    VDC association. Module-based load balancing takes precedence over device-based load balancing. BEFORE YOU BEGIN Enable LACP if you want LACP-based port channels. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-27 OL-23435-03...
  • Page 184 Example: switch(config)# copy running-config startup-config Use the no port-channel load-balance to restore the default load-balancing algorithm of source-dest-mac for non-IP traffic and source-dest-ip for IP traffic. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-28 OL-23435-03...

  • Page 185: Enabling Lacp

    Ensure that you are in the correct VDC (or use the switchto vdc command). SUMMARY STEPS configure terminal feature lacp copy running-config startup-config DETAILED STEPS Command Purpose Step 1 Enters configuration mode. configure terminal Example: switch# configure terminal switch(config)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-29 OL-23435-03...

  • Page 186: Configuring Lacp Port-Channel Port Modes

    Example: switch# configure terminal switch(config)# Step 2 Specifies the interface to configure, and enters the interface type slot/port interface configuration mode. Example: switch(config)# interface ethernet 1/4 switch(config-if) Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-30 OL-23435-03...

  • Page 187: Configuring Lacp Port-Channel Minlinks

    5 mode active Configuring LACP Port-Channel MinLinks With Cisco NX-OS Release 5.1, you can configure the LACP minlinks feature. Although minlinks and maxbundles work only in LACP, you can enter the CLI commands for these features for non-LACP port channels, but these commands are nonoperational.

  • Page 188: Configuring The Lacp Port-Channel Maxbundle

    (config)# lacp min-links 3 Configuring the LACP Port-Channel MaxBundle With Cisco NX-OS Release 5.1, you can configure the LACP minlinks feature. Although minlinks and maxbundles work only in LACP, you can enter the CLI commands for these features for non-LACP port channels, but these commands are nonoperational.
  • Page 189 Example: switch(config)# no lacp max-bundle This example shows how to configure the port channel interface max-bundle on module 3: switch# configure terminal switch (config)# lacp max-bundle 3 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-33 OL-23435-03...

  • Page 190: Configuring The Lacp Fast Timer Rate

    (config)# interface ethernet 1/4 switch(config-if)# no lacp rate fast Configuring the LACP System Priority The LACP system ID is the combination of the LACP system priority value and the MAC address. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-34 OL-23435-03...

  • Page 191: Configuring The Lacp Port Priority

    2500 Configuring the LACP Port Priority When you enable LACP, you can configure each link in the LACP port channel for the port priority. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-35 OL-23435-03...

  • Page 192: Disabling Lacp Graceful Convergence

    The port channel has to be in the administratively down state before the command can be run. Note Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-36 OL-23435-03...
  • Page 193 Example: switch(config-if)# copy running-config startup-config This example shows how to disable LACP graceful convergence on a port channel: switch# configure terminal switch (config)# interface port-channel 1 switch(config-if)# shutdown Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-37 OL-23435-03...

  • Page 194: Reenabling Lacp Graceful Convergence

    Brings the port channel administratively up. no shutdown Example: switch(config-if) no shutdown Step 6 (Optional) Copies the running configuration to the copy running-config startup-config startup configuration. Example: switch(config-if)# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-38 OL-23435-03...

  • Page 195: Disabling Lacp Suspend Individual

    Specifies the port channel interface to configure, and interface port-channel number enters the interface configuration mode. Example: switch(config)# interface port-channel 1 switch(config-if) Step 3 Administratively shuts down the port channel. shutdown Example: switch(config-if) shutdown Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-39 OL-23435-03...

  • Page 196: Reenabling Lacp Suspend Individual

    Step 2 Specifies the port channel interface to configure, and interface port-channel number enters the interface configuration mode. Example: switch(config)# interface port-channel 1 switch(config-if) Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-40 OL-23435-03...
  • Page 197 This example shows how to reenable the LACP individual port suspension on a port channel: switch# configure terminal switch (config)# interface port-channel 1 switch(config-if)# shutdown switch(config-if)# lacp suspend-individual switch(config-if)# no shutdown Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-41 OL-23435-03...

  • Page 198: Verifying The Port-Channel Configuration

    Displays information on the running channel-number configuration of the port-channel. For more information about these commands, see the Cisco Nexus 7000 Series NX-OS Interfaces Command Reference, Release 5.x. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-42...

  • Page 199: Monitoring The Port-Channel Interface Configuration

    1/7 switch(config-if)# switchport switch(config-if)# channel-group 5 mode The following example shows how to add two Layer 3 interfaces to a channel group. The Cisco DC-OS software automatically creates the port channel: switch# configure terminal switch (config)# interface ethernet 1/5...

  • Page 200: Additional References

    (config)# interface port-channel 6 switch(config-if)# ip address 192.0.2.1/8 Additional References For additional information related to implementing port channels, see the following sections: Related Documents, page 6-45 • MIBs, page 6-45 • Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-44 OL-23435-03...

  • Page 201: Related Documents

    Support increased to 528 port channels. Minlinks and Maxbundle 5.1(1) This feature was introduced. Port channels 4.2(1) Support increased to 256 port channels. Port channels 4.0(1) This feature was introduced. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-45 OL-23435-03...
  • Page 202 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 203: Configuring Vpcs

    You cannot configure shared interfaces to be part of a vPC. See the Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 for more information on shared interfaces.

  • Page 204: Chapter 7 Configuring Vpc

    High Availability, page 7-28 • vPC Overview A virtual port channel (vPC) allows links that are physically connected to two different Cisco Nexus 7000 Series devices to appear as a single port channel by a third device (see Figure 7-1). The third device can be a switch, server, or any other networking device that supports port channels.
  • Page 205 You can create a vPC peer link by configuring a port channel on one Cisco Nexus 7000 Series chassis by using two or more 10-Gigabit Ethernet ports in dedicated mode. To ensure that you have the correct hardware to enable and run vPC beginning with Cisco NX-OS Release 4.1(5), enter the show hardware...
  • Page 206 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m the two linked Cisco Nexus devices appear as one device to a third device. The third device, or downstream device, can be a switch, server, or any other networking device that uses a regular port channel to connect to the vPC.

  • Page 207: Vpc Terminology

    Port channel Catalyst Catalyst Series 6500 switch Series 6500 switch For more information on VDCs, see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 5.x. vPC Terminology The terminology used in vPCs is as follows: •...

  • Page 208: Vpc Peer Links

    Forwards data packets to the vPC peer switch, when the local vPC is down. • A single vPC domain between two VDCs on the same physical Cisco Nexus 7000 device is not supported. This section describes the vPC peer link and includes the following topics: •...
  • Page 209 F1 I/O module M1 I/O module M1 I/O module Figure 7-4 Supported—Two F1 I/O Modules on Either Side of a vPC Peer Link vPC Primary vPC Secondary vPC Peer-link Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 210 You can have only two devices as vPC peers; each device can serve as a vPC peer to only one other vPC peer. The vPC peer devices can also have non-vPC links to other devices. Figure 7-8 for invalid vPC peer configurations. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 211 “Configuring vPCs” section on page 7-30). The Cisco NX-OS software uses the lowest MAC address to elect the primary device. The software takes different actions on each device—that is, the primary and secondary—only in certain failover conditions. If the primary device fails, the secondary device becomes the new primary device when the system recovers, and the previously primary device is now the secondary device.
  • Page 212 (see Chapter 6, “Configuring Port Channels,” for information on load balancing). Configuration information flows across the vPC peer links using the Cisco Fabric Service over Ethernet (CFSoE) protocol. (See the “CFSoE” section on page 7-26 for more information about CFSoE.) All MAC addresses for those VLANs configured on both devices are synchronized between vPC peer devices.

  • Page 213: Peer-Keepalive Link And Messages

    If a vPC peer link fails, the system brings down associated VLAN interfaces on the secondary vPC peer device. Beginning with Cisco NX-OS Release 4.2(1), you can ensure that specified VLAN interfaces do not go down on the vPC secondary device when the vPC peer link fails.

  • Page 214: Vpc Peer-Gateway

    Peer-Gateway Beginning with Cisco NX-OS Release 4.2(1), you can configure vPC peer devices to act as the gateway even for packets that are destined to the vPC peer device’s MAC address.

  • Page 215: Vpc Domain

    Such devices may reply to traffic using the MAC address of the sender Cisco Nexus 7000 Series device rather than the common HSRP gateway. Such behavior is non-complaint with some basic Ethernet RFC standards.

  • Page 216: Vpc Topology

    “CFSoE” section on page 7-26 for more information on displaying the vPC MAC table. After you create a vPC domain, the Cisco NX-OS software creates a system priority for the vPC domain. You can also configure a specific system priority for the vPC domain.

  • Page 217: Compatibility Parameters For Vpc Interfaces

    P0200 vPC200 In the figure, each FEX is single-homed (straight-through FEX topology) with a Cisco Nexus 7000 Series Switch. The host interfaces on this FEX are configured as port channels and those port channels are configured as vPCs. Eth100/1/1 and Eth102/1/5 are configured as members of PO200, and PO200 is configured for vPC 200.
  • Page 218 Enable/disable state per VLAN • STP global settings: • Bridge Assurance setting – Port type setting – Loop Guard settings – • STP interface settings: – Port type setting Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-16 OL-23435-03...
  • Page 219 Internet Group Management Protocol (IGMP) snooping • Hot Standby Routing Protocol (HSRP) • Protocol Independent Multicast (PIM) • Gateway Load-Balancing Protocol (GLBP) • All routing protocol configurations • Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-17 OL-23435-03...

  • Page 220: Vpc Number

    We recommend that you configure the ports on the downstream devices that connect to a host or a network device that is not functioning as a switch or a bridge as STP edge ports. See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more information on STP port types.

  • Page 221: Configuring Vpc Peer Links And Links To The Core On A Single Module

    For the best resiliency scenario, use at least two modules. Beginning with Cisco NX-OS Release 4.2, if you must configure all the vPC peer links and core-facing interfaces on a single module, you should configure, using the command line interface, a track object and a track list that is associated with the Layer 3 link to the core and on all vPC peer links on both vPC peer devices.

  • Page 222: Vpc Interactions With Other Features

    Peer Switch, page 7-23 • vPC and ARP or ND, page 7-23 • vPC Multicast—PIM, IGMP, and IGMP Snooping, page 7-23 • vPC Peer Links and Routing, page 7-25 • Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-20 OL-23435-03...
  • Page 223 When you are running both MST and Rapid PVST+, ensure that the PVST simulation feature is correctly configured. See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for information on STP enhancement features and PVST simulation.
  • Page 224 STP process for the vPC interfaces on the secondary vPC peer device. The primary vPC device synchronizes the STP state on the vPC secondary peer device using Cisco Fabric Services over Ethernet (CFSoE). See the “CFSoE”...
  • Page 225 We recommend that you configure the ports on the downstream devices as STP edge ports. You should Note configure all host ports connected to a switch as STP edge ports. (See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more information on STP port types.) vPC Peer Switch The vPC peer switch feature was added to Cisco NX-OS Release 5.0(2) to address performance concerns...
  • Page 226 (they communicate through PIM joins). In the Cisco NX-OS vPC implementation (in non-F2 mode), PIM works in Dual designated router (DR) mode. That is, if a vPC device is a DR on a vPC SVI OIF, its peer automatically assumes the proxy DR role.
  • Page 227 The primary FHRP device responds to ARP requests, even though the secondary vPC device forwards the data traffic. To simplify initial configuration verification and vPC/HSRP troubleshooting, you can configure the primary vPC peer device with the FHRP active router highest priority. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-25 OL-23435-03...
  • Page 228 When you are configuring custom MAC addresses, you must configure the same MAC address on both vPC peer devices. Beginning with Cisco NX-OS Release 4.2(1), you can configure a restore timer that will delay the vPC coming back up until after the peer adjacency forms and the VLAN interfaces are back up. This feature avoids packet drops when the routing tables may not be converged before the vPC is once again passing traffic.

  • Page 229: Vpc Recovery After An Outage

    Recovery After an Outage In a data center outage, both of the Cisco Nexus 7000 Series devices that comprise a vPC get reloaded. Occasionally only one of the peers can be restored. With no functioning peer-keepalive or peer link, the vPC cannot function normally, but depending on your Cisco NX-OS release, a method may be available to allow vPC services using only the local ports of the functional peer.

  • Page 230: High Availability

    If at timer expiration no peer-keepalive or peer link up packets were received, the Cisco NX-OS software assumes the primary STP role and the primary LACP role. The software reinitializes the vPCs, bringing up its local ports.

  • Page 231: Licensing Requirements For Vpcs

    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 232: Configuring Vpcs

    BFD for HSRP is not supported in a vPC environment. • The STP port cost is fixed to 200 in a vPC environment. • A single vPC domain between two VDCs on the same physical Cisco Nexus 7000 device is not • supported. Default Settings Table 7-2 lists the default settings for vPC parameters.

  • Page 233: Enabling Vpcs

    Configuring the vPC Peer Switch, page 7-53 • Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use. Enabling vPCs You must enable the vPC functionality before you can configure and use vPCs.

  • Page 234: Disabling Vpcs

    Ensure that you are in the correct VDC (or use the switchto vdc command). SUMMARY STEPS configure terminal no feature vpc exit (Optional) show feature (Optional) copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-32 OL-23435-03...

  • Page 235: Creating A Vpc Domain And Entering The Vpc-Domain Mode

    Ensure that you have enabled the vPC feature. Ensure that you are in the correct VDC (or use the switchto vdc command). SUMMARY STEPS configure terminal vpc domain domain-id exit (Optional) show vpc brief Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-33 OL-23435-03...

  • Page 236: Configuring The Vpc Keepalive Link And Messages

    Layer 3 port from each vPC peer device into that VRF for the vPC peer-keepalive link. Do not use the peer link itself to send vPC peer-keepalive messages. For information on creating and configuring VRFs, Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-34...
  • Page 237 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m see the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x.

  • Page 238: Creating The Vpc Peer Link

    Example: switch# copy running-config startup-config For more information on configuring VRFs, see the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x. This example shows how to configure the destination and source IP address and VRF for the...
  • Page 239 Configures the selected port channel as the vPC peer vpc peer-link link, and enters the vpc-domain configuration mode. Example: switch(config-if)# vpc peer-link switch(config-vpc-domain)# Step 6 Exits the vpc-domain configuration mode. exit Example: switch(config-vpc-domain)# exit switch(config)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-37 OL-23435-03...

  • Page 240: Configuring The Vpc Peer-Gateway

    Configuring the vPC Peer-Gateway Beginning with Cisco NX-OS Release 4.2(1) and later releases, you can configure vPC peer devices to act as the gateway for packets that are destined to the vPC peer device's MAC address. When you attach a Layer 3 device to a vPC domain, the peering of routing protocols using a VLAN also Note carried on the vPC peer-link is not supported.

  • Page 241: Configuring A Graceful Consistency Check

    Configuring a Graceful Consistency Check Beginning with Cisco NX-OS Release 5.2(1), you can configure the graceful consistency check feature, which is enabled by default. Unless this feature is enabled, the vPC is completely suspended when a mismatch in a mandatory compatibility parameter is introduced in a working vPC.

  • Page 242: Checking The Configuration Compatibility On A Vpc Peer Link

    “Compatibility Parameters for vPC Interfaces” section on page 7-15 for information on consistent configurations on the vPCs. SUMMARY STEPS configure terminal (Optional) show vpc consistency-parameters {global | interface port-channel channel-number} Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-40 OL-23435-03...

  • Page 243: Moving Other Port Channels Into A Vpc

    Ensure that you are using a Layer 2 port channel. Ensure that you are in the correct VDC (or use the switchto vdc command). SUMMARY STEPS configure terminal interface port-channel channel-number vpc number exit Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-41 OL-23435-03...

  • Page 244: Manually Configuring A Vpc Domain Mac Address

    Manually Configuring a vPC Domain MAC Address When you create a vPC domain, the Cisco NX-OS software automatically creates a vPC system MAC address, which is used for operations that are confined to the link-scope, such as LACP. However, you may choose to configure the vPC domain MAC address manually.
  • Page 245 Example: switch# copy running-config startup-config This example shows how to manually configure the vPC domain MAC address: switch# configure terminal switch(config)# vpc domain 5 switch(config-vpc-domain)# system-mac 13gb.4ab5.4c4e Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-43 OL-23435-03...

  • Page 246: Manually Configuring The System Priority

    The range of values is from 1 Example: to 65535. The default value is 32667. switch(config-vpc-domain)# system-priority 4000 switch(config-vpc-domain)# Step 4 Exits the vpc-domain configuration mode. exit Example: switch(config-vpc-domain)# exit switch(config)# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-44 OL-23435-03...

  • Page 247: Manually Configuring The Vpc Peer Device Role

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

  • Page 248: Configuring The Tracking Feature On A Single-Module Vpc

    Configuring the Tracking Feature on a Single-Module vPC Beginning with Cisco NX-OS Release 4.2, if you must configure all the vPC peer links and core-facing interfaces on a single module, you should configure a track object and a track list that is associated with the Layer 3 link to the core and on all the links on the vPC peer link on both primary vPC peer devices.
  • Page 249 Example: switch# show vpc brief Step 6 (Optional) Copies the running configuration to the copy running-config startup-config startup configuration. Example: switch# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-47 OL-23435-03...

  • Page 250: Configuring For Recovery After An Outage

    In the event of an outage, vPC waits for peer adjacency to form on a switch reload. This situation can result in an unacceptably long service disruption. You can configure the Cisco Nexus 7000 Series device to restore vPC services when its peer fails to come on line.
  • Page 251 Enables restoring of vPCs in a peer-detached state after reload, will wait for 240 seconds (by default) to determine if peer is un-reachable switch(config-vpc-domain)# exit switch(config)# exit switch# copy running-config startup-config switch# show running-config vpc Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-49 OL-23435-03...
  • Page 252 1-3967,4048-4093 Local suspended VLANs Configuring Autorecovery Beginning with Cisco NX-OS Release 5.2(1), you can configure the Cisco Nexus 7000 Series device to restore vPC services when its peer fails to come online by using the auto-recovery command. BEFORE YOU BEGIN Ensure that you have enabled the vPC feature.
  • Page 253 Enables restoring of vPCs in a peer-detached state after reload, will wait for 240 seconds to determine if peer is un-reachable switch(config-vpc-domain)# exit switch(config)# exit switch# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-51 OL-23435-03...

  • Page 254: Configuring The Suspension Of Orphan Ports

    When a device that is not vPC-capable connects to each peer, the connected ports are known as orphan ports because they are not members of a vPC. Beginning with Cisco NX-OS Release 5.2(1), you can explicitly declare phyiscal interfaces as orphan ports to be suspended (shut down) by the secondary peer when it suspends its vPC ports in response to a peer link or peer-keepalive failure.

  • Page 255: Configuring The Vpc Peer Switch

    Configuring the vPC Peer Switch You can configure the Cisco Nexus 7000 Series device to make a pair of vPC devices appear as a single STP root in the Layer 2 topology. This section includes the following topics: Configuring a Pure vPC Peer Switch Topology, page 7-53 •...
  • Page 256 Please make sure to configure spanning tree "bridge" priority as per recommended guidelines to make vPC peer-switch operational. switch(config-vpc-domain)# exit switch(config)# spanning-tree vlan 1 priority 8192 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-54 OL-23435-03...
  • Page 257 You can configure a hybrid vPC and non-vPC peer switch topology by using the spanning-tree pseudo-information command (see the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Command Reference, Release 5.x.) to change the designated bridge ID so that it meets the STP VLAN-based load-balancing criteria and then change the root bridge ID priority to a value that is better than the best bridge priority.

  • Page 258: Verifying The Vpc Configuration

    Displays how many port channels are configured and how many are still available on the device. show vpc statistics Displays statistics on the vPCs. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-56 OL-23435-03...

  • Page 259: Monitoring Vpcs

    MAC address and system priority, and the MAC address and priority for the local vPC device. For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Interfaces Command Reference, Release 5.x. Monitoring vPCs Use the show vpc statistics command to display vPC statistics.
  • Page 260 1 switch(config-vpc-domain)# peer-keepalive destination 172.23.145.217 source 172.23.145.218 vrf pkal switch(config-vpc-domain)# exit Configure the vPC peer link. Step 8 switch(config)# interface port-channel 20 switch(config-if)# switchport mode trunk Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-58 OL-23435-03...

  • Page 261: Additional References

    If you configure the port channel first, ensure that it is a Layer 2 port channel. Note Additional References For additional information related to implementing vPC, see the following sections: Related Documents, page 7-60 • Standards, page 7-60 • MIBs, page 7-60 • Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-59 OL-23435-03...

  • Page 262: Feature History For Configuring Vpcs

    5.2(1) Added per-VLAN consistency checking so that only those VLANs with inconsistent configuration are suspended. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-60 OL-23435-03...
  • Page 263 Added the delay restore command to delay the bringup of the vPC secondary device after reload until the routing table can converge. vPCs 4.1(4) Support increased to 192 vPCs. vPCs 4.1(2) These features were introduced. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-61 OL-23435-03...
  • Page 264 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 265: Information About Ip Tunnels

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m C H A P T E R Configuring IP Tunnels This chapter describes how to configure IP tunnels using Generic Route Encapsulation (GRE) on Cisco NX-OS devices. This chapter includes the following sections: Information About IP Tunnels, page 8-1 •...

  • Page 266: Chapter 8 Configuring Ip Tunnel

    Release 5.x, for information on roll backs and checkpoints. Beginning with Cisco NX-OS Release 4.2, a tunnel configured in one VDC is isolated from a tunnel with the same number configured in another VDC. For example, Tunnel 0 in VDC 1 is independent of tunnel 0 in VDC 2.

  • Page 267: Path Mtu Discovery

    Routing and Forwarding (VRF) instance. Beginning with Cisco NX-OS Release 4.2, you can configure a tunnel interface as a member of a Virtual Routing and Forwarding (VRF) instance and as a member of any VDC. By default, Cisco NX-OS places you in the default VDC and default VRF unless you specifically configure another VDC and VRF.

  • Page 268: Prerequisites For Ip Tunnels

    Guidelines and Limitations IP tunnels have the following configuration guidelines and limitations: Cisco NX-OS supports the GRE Header defined in IETF RFC 2784. Cisco NX-OS does not support • tunnel keys and other options from IETF RFC 1701. Beginning with Cisco NX-OS Release 5.2(5) and for later 5.2(x) releases, you can configure the •...

  • Page 269: Enabling Tunneling

    S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature Note might differ from the Cisco IOS commands that you would use.
  • Page 270 Use the no interface tunnel command to remove the tunnel interface and all associated configuration. Command Purpose Deletes the tunnel interface and the associated no interface tunnel number configuration. Example: switch(config)# no interface tunnel 1 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 271: Configuring A Gre Tunnel

    BEFORE YOU BEGIN Ensure that you have enabled the tunneling feature. SUMMARY STEPS configure terminal interface tunnel number tunnel mode gre ip show interfaces tunnel number copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 272: Enabling Path Mtu Discovery

    MTU recognized. The • range is from 92 to 65535. The default is 92. Assigning VRF Membership to a Tunnel Interface You can add a tunnel interface to a VRF. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 273 [vrf-name] interface interface-type number Example: switch(config-vrf)# show vrf Enterprise interface tunnel 0 Step 6 (Optional) Saves this configuration change. copy running-config startup-config Example: switch(config)# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 274: Verifying The Ip Tunnel Configuration

    192.0.2.55/8 router B: feature tunnel interface tunnel 0 ip address 209.165.20.1/8 tunnel source ethernet2/1 tunnel destination 192.0.2.55 tunnel mode gre ip interface ethernet 2/1 ip address 192.0.2.2/8 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 8-10 OL-23435-03...

  • Page 275: Feature History For Configuring Ip Tunnels

    VRFs for M1 series I/O modules only and for later 5.2(x) releases. IP tunnels in VDC and VRF other than default 4.2(1) This feature was introduced. IP tunnels 4.0(1) This features was introduced. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 8-11 OL-23435-03...
  • Page 276 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

  • Page 277: Information About Q-In-Q Tunnels

    Assigning a unique range of VLAN IDs to each customer would restrict customer configurations and could easily exceed the VLAN limit of 4096 of the 802.1Q specification. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 278 VLAN IDs, are encapsulated with another layer of an 802.1Q tag that contains a VLAN ID unique to the customer. The original 802.1Q tag from the customer is preserved in the encapsulated packet. Therefore, packets that enter the service-provider infrastructure are double-tagged. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 279: Chapter 9 Configuring Q-In-Q Vlan Tunnel

    VLAN 40. Because the access VLAN of the tunnel port (VLAN 40) is the same as the native VLAN of the edge-switch trunk port (VLAN 40), the 802.1Q tag is not added to tagged packets Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 280: Information About Layer 2 Protocol Tunneling

    The spanning Tree Protocol (STP) must run properly, and every VLAN should build a proper spanning tree that includes the Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 281 Cisco Discovery Protocol (CDP) must be able to discover neighboring Cisco devices from local and remote sites, and the VLAN Trunking Protocol (VTP) must provide consistent VLAN configuration throughout all sites in the customer network.
  • Page 282 BPDU tunneling is not enabled. Figure 9-5 Virtual Network Topology Without BPDU Tunneling Customer A virtual network VLANs 1 to 100 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...

  • Page 283: Licensing Requirements For Q-In-Q Tunnels

    • effect on some Cisco Nexus devices. Configuring Q-in-Q Tunnels and Layer 2 Protocol Tunneling This section describes how to configure Q-in-Q tunnels and Layer 2 protocol tunneling on Cisco Nexus 7000 Series devices. This section includes the following topics: Creating a 802.1Q Tunnel Port, page 9-8...

  • Page 284: Creating A 802.1Q Tunnel Port

    Configuring Thresholds for Layer 2 Protocol Tunnel Ports, page 9-14 • If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature Note might differ from the Cisco IOS commands that you would use.

  • Page 285: Changing The Ethertype For Q-In-Q

    Changing the EtherType for Q-in-Q You can change the 802.1Q EtherType value to be used for Q-in-Q encapsulation. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03...
  • Page 286 0x9100 Step 5 (Optional) Resets the EtherType on the port to the no switchport dot1q ethertype default value of 0x8100. Example: switch(config-if)# no switchport dot1q ethertype Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-10 OL-23435-03...

  • Page 287: Enabling The Layer 2 Protocol Tunnel

    Enters global configuration mode. configure terminal Example: switch# configure terminal Step 2 Specifies an interface to configure, and enters interface ethernet slot/port interface configuration mode. Example: switch(config)# interface ethernet 7/1 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-11 OL-23435-03...

  • Page 288: Configuring Global Cos For L2 Protocol Tunnel Ports

    You can specify a Class of Service (CoS) value globally so that ingress BPDUs on the tunnel ports are encapsulated with the specified class. SUMMARY STEPS configure terminal l2protocol tunnel cos value no l2protocol tunnel cos exit copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-12 OL-23435-03...

  • Page 289: Configuring The Rate Limit For Layer 2 Protocol Tunnel Ports

    STP errors on the customer’s network. SUMMARY STEPS configure terminal hardware rate-limiter layer-2 l2pt packets-per-sec no hardware rate-limiter layer-2 l2pt Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-13 OL-23435-03...

  • Page 290: Configuring Thresholds For Layer 2 Protocol Tunnel Ports

    Enters global configuration mode. configure terminal Example: switch# configure terminal Step 2 Specifies an interface to configure, and enters interface ethernet slot/port interface configuration mode. Example: switch(config)# interface ethernet 7/1 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-14 OL-23435-03...
  • Page 291 Step 9 Exits configuration mode. exit Example: switch(config)# exit Step 10 (Optional) Copies the running configuration to the copy running-config startup-config startup configuration. Example: switch# copy running-config startup-config Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-15 OL-23435-03...

  • Page 292: Verifying The Q-In-Q Configuration

    10 switch(config-if)# spanning-tree port type edge switch(config-if)# l2protocol tunnel stp switch(config-if)# no shutdown switch(config-if)# exit switch(config)# exit switch# Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-16 OL-23435-03...

  • Page 293: Feature History For Q-In-Q Tunnels And Layer 2 Protocol Tunneling

    Feature History for Q-in-Q Tunnels and Layer 2 Protocol Tunneling Feature Name Releases Feature Information Q-in-Q VLAN Tunnels 5.0(2) This feature was introduced. L2 Protocol Tunneling 5.0(2) This feature was introduced. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-17 OL-23435-03...
  • Page 294 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...
  • Page 295 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m A P P E N D I X IETF RFCs supported by Cisco NX-OS Interfaces This appendix lists the IETF RFCs for interfaces supported by Cisco NX-OS interfaces Nexus 7000 Series NX-OS Release 5.x. IPv6 RFCs...
  • Page 296 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...
  • Page 297 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m A P P E N D I X Configuration Limits for Cisco NX-OS Interfaces The configuration limits are documented in the Cisco Nexus 7000 Series NX-OS Verified Scalability Guide. Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...
  • Page 298 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...
  • Page 299 6-29, 6-30 configuring authentication 5-10, 5-11 active mode 6-10 configuring for BGP 5-15 configuring 6-30 configuring for EIGRP 5-16 default setting 6-10 configuring for HSRP 5-20 LACP Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-1 OL-23435-03...
  • Page 300 3-3, 3-4 LACP 6-43 IEEE 802.3ad port channels 6-43 LACP trunk ports 3-23 Interfaces routed interfaces access port 3-10 fabric extender administrative status Layer 3 support configuring 2-37 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-2 OL-23435-03...
  • Page 301 9-9, 9-10, 9-11, 9-13, 9-14 jumbo MTU, configuring tunnels 2-33 LACP types, specifying 2-15 Layer 2 UDLD loopback configuring 2-39 loopback, configuring defined 4-14 management verifying 3-22 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-3 OL-23435-03...
  • Page 302 VDCs port channels vPCs 7-10 port priority 6-35 loopback statistics 6-43 configuring 4-14 suspend individual 6-39 interfaces, default settings system ID 6-10, 6-11, 6-34 system priority 6-10, 6-34 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-4 OL-23435-03...
  • Page 303 Layer 2 port channels unsupported layer 2 port channels PAgP, unsupported Layer 3 port channel, adding a port 6-19 Port Aggregation Protocol. See PAgP. Layer 3 port channels 6-1, 6-2 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-5 OL-23435-03...
  • Page 304 Time Domain Reflectometry. See TDR. Layer 2 transceivers multiple VLANs using Cisco supported transceivers 2-13 setup script troubleshooting port channels 7-1, 7-11 vPC peer link Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-6 OL-23435-03...
  • Page 305 7-28 vPCs 7-11 number of links Unidirectional Link Detection. See UDLD. primary and secondary configuration 7-17, 7-45 synchronize configurations 7-57 traffic pattern 7-10 troubleshooting 7-3, 7-9 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-7 OL-23435-03...
  • Page 306 7-23 vPC domain ID 7-13, 7-33 number of vPC number 7-18 on single module 7-4, 7-19 vPC role overview vPC system priority 7-14 peer devices 7-5, 7-8 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-8 OL-23435-03...
  • Page 307 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m configuring 7-44, 7-57 vPC Wizard 7-57 VRF recommended VRRP 7-25 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x IN-9 OL-23435-03...
  • Page 308 S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x...

This manual is also suitable for:

7606-2sup720xl-2ps7609s-rsp720cxl-rC7140-2fe/vpn/k9 - 7140 routerC7400vpn/k9 - 7400 routerCisco7120-4t1 - 7120 routerCisco7120-at3 - 7120 router ... Show all