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

Cisco Nexus 3548 Configuration Manual

Nx-os interfaces release 9x
Hide thumbs Also See for Nexus 3548:
Table of Contents

Advertisement

Quick Links

See also: Configuration Manual , Installation Manual
Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide,
Release 9x
First Published: 2018-07-16
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883

Advertisement

Table of Contents
loading

Related Manuals for Cisco Nexus 3548

Summary of Contents for Cisco Nexus 3548

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

  • Page 3: Table Of Contents

    Default CDP Configuration Error-Disabled State MTU Configuration Debounce Timer Parameters Guidelines and Limitations for Layer 2 Interfaces Configuring Ethernet Interfaces Configuring the UDLD Mode Configuring the Interface Speed Configuring 40-Gigabit Interface Speed Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 4 Configuring a VLAN Interface Configuring a Loopback Interface Assigning an Interface to a VRF Verifying the Layer 3 Interfaces Configuration Monitoring Layer 3 Interfaces Configuration Examples for Layer 3 Interfaces Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 5 Verifying Port Channel Configuration Verifying the Load-Balancing Outgoing Port ID C H A P T E R 5 Configuring Virtual Port Channels Information About vPCs vPC Overview Terminology vPC Terminology Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 6 Creating a vPC Peer Link Checking the Configuration Compatibility Enabling vPC Auto-Recovery Configuring the Restore Time Delay Excluding VLAN Interfaces from Shutting Down a vPC Peer Link Fails Configuring the VRF Name Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 7 Verifying the Static NAT Configuration Configuring Dynamic NAT Configuring Dynamic Translation and Translation Timeouts Configuring Dynamic NAT Pool Configuring Source Lists Configuring Dynamic Twice NAT for an Inside Source Address Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 8 Suppress Threshold Half-Life Period Reuse Threshold Maximum Suppress Time Affected Components Route Types Supported Protocols How to Configure IP Event Dampening Enabling IP Event Dampening Verifying IP Event Dampening Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x viii...

  • Page 9: Preface

    • Documentation Feedback, on page x Audience This publication is for network administrators who configure and maintain Cisco Nexus devices. Document Conventions Note As part of our constant endeavor to remodel our documents to meet our customers' requirements, we have modified the manner in which we document configuration tasks.

  • Page 10: Documentation Feedback

    Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Documentation Feedback To provide technical feedback on this document, or to report an error or omission, please send your comments to: . We appreciate your feedback. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 11: New And Changed Information

    Feature Description Added or Changed in Where Documented Release NAT Statistics Added support for NAT 9.2(1) Verifying NAT Statistics, statistics to display the on page 116 various NAT software statistics. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 12 New and Changed Information New and Changed Information Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 13: Configuring Layer 2 Interfaces

    • Slot 4 includes the ports on the lower expansion module (if populated). • Port number— Port number within the group. The interface numbering convention is extended to support use with a Cisco Nexus Fabric Extender as follows: switch(config)# interface ethernet [chassis/]slot/port...

  • Page 14: About 40-Gbps Interface Speed

    This check cannot be performed by autonegotiation, because autonegotiation operates at Layer 1. A Cisco Nexus 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 15: Default Udld Configuration

    VLAN in the device. By default, when a VLAN interface has multiple ports in the VLAN, the SVI goes to the down state when all the ports in the VLAN go down. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 16: Cisco Discovery Protocol

    MAC of the SVI. Cisco Discovery Protocol The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over Layer 2 (the data link layer) on all Cisco-manufactured devices (routers, bridges, access servers, and switches) and allows network management applications to discover Cisco devices that are neighbors of already known devices.

  • Page 17: Error-Disabled State

    MTU Configuration The Cisco Nexus device switch does not fragment frames. As a result, the switch cannot have two ports in the same Layer 2 domain with different maximum transmission units (MTUs). A per-physical Ethernet interface MTU is not supported.

  • Page 18: Debounce Timer Parameters

    To use the aggressive UDLD mode, you must configure both ports for the aggressive mode. Note Before you begin, UDLD must be enabled for the other linked port and its device. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 19 This example shows how to enable the aggressive UDLD mode for an Ethernet port: switch# configure terminal switch(config)# interface ethernet 1/4 switch(config-if)# udld aggressive This example shows how to disable UDLD for an Ethernet port: Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 20: Configuring The Interface Speed

    This command can only be applied to a physical Ethernet interface. The speed argument can be set to one of the following: • 10 Mbps • 100 Mbps • 1 Gbps • 10 Gbps • automatic Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 21: Configuring 40-Gigabit Interface Speed

    All four adjacent ports must have 10-Gbps Ethernet SFP transceivers installed. Step 6 switch(config-if)# speed 40000 Sets the speed on the interface for 40 Gbps. Step 7 switch(config-if)# no shut Brings up the range of interfaces. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 22: Disabling Link Negotiation

    1-Gigabit ports and disabled on 10-Gigabit ports. The no negotiate auto command is supported on 100M port with full duplex setting. This command is equivalent to the Cisco IOS speed non-negotiate command. Note Auto negotiation configuration is not applicable on 10-Gigabit ports. When auto-negotiation is configured on...

  • Page 23: Disabling Svi Autostate

    Step 5 (Optional) switch(config-if)# [no] autostate Enables or disables Autostate behavior per SVI. Step 6 (Optional) switch(config)# show interface-vlan Displays the enabled or disabled Autostate behavior of the interface-vlan SVI. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 24: Configuring The Cdp Characteristics

    MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec Configuring the CDP Characteristics You can configure the frequency of Cisco Discovery Protocol (CDP) updates, the amount of time to hold the information before discarding it, and whether or not to send Version-2 advertisements.

  • Page 25: Enabling Or Disabling Cdp

    Enters interface configuration mode for the specified interface. Step 3 switch(config-if)# cdp enable Enables CDP for the interface. To work correctly, this parameter must be enabled for both interfaces on the same link. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 26: Enabling The Error-Disabled Detection

    Displays information about err-disabled interfaces. Step 6 (Optional) switch(config)# copy running-config Saves the change persistently through reboots and restarts startup-config by copying the running configuration to the startup configuration. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 27: Enabling The Error-Disabled Recovery

    Example This example shows how to enable err-disabled recovery under all conditions: switch# configure terminal switch(config)# errdisable recovery cause loopback switch(config)# show interface status err-disabled switch(config)# copy running-config startup-config Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 28: Configuring The Error-Disabled Recovery Interval

    Configuring the Description Parameter You can provide textual interface descriptions for the Ethernet ports. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# interface type slot/port 3. switch(config-if)# description test Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 29: Disabling And Restarting Ethernet Interfaces

    Disables the interface. Step 4 switch(config-if)# no shutdown Restarts the interface. Example This example shows how to disable an Ethernet port: switch# configure terminal switch(config)# interface ethernet 1/4 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 30: Configuring The Debounce Timer

    This example shows how to enable the debounce timer and set the debounce time to 1000 ms for an Ethernet interface: switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# link debounce time 1000 This example shows how to disable the debounce timer for an Ethernet interface: Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 31: Verifying The Layer 2 Interfaces Configuration

    1/1 Ethernet1/1 is up Hardware is 1000/10000 Ethernet, address is 000d.eca3.5f08 (bia 000d.eca3.5f08) MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 190/255, rxload 192/255 Encapsulation ARPA Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 32 10300 MBits/sec Link length supported for 50/125mm fiber is 82 m(s) Link length supported for 62.5/125mm fiber is 26 m(s) cisco id is -- cisco extended id number is 4 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 33: Default Physical Ethernet Settings

    Default Setting Duplex Auto (full-duplex) Encapsulation ARPA 1500 bytes Port Mode Access Speed Auto (10000) MTU cannot be changed per-physical Ethernet interface. You modify MTU by selecting maps of QoS classes. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 34: Mibs For Layer 2 Interfaces

    Objects: • ifMauType (Read-only) GET • ifMauAutoNegSupported (Read-only) GET • ifMauTypeListBits (Read-only) GET • ifMauDefaultType (Read-write) GET-SET • ifMauAutoNegAdminStatus (Read-write) GET-SET • ifMauAutoNegCapabilityBits (Read-only) GET • ifMauAutoNegAdvertisedBits (Read-write) GET-SET Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 35: Configuring Layer 3 Interfaces

    You can assign an IP address to the port, enable routing, and assign routing protocol characteristics to this routed interface. You can also create a Layer 3 port channel from routed interfaces. Routed interfaces and subinterfaces support exponentially decayed rate counters. Cisco NX-OS tracks the following statistics with these averaging counters: • Input packets/sec...

  • Page 36: Subinterfaces

    Ethernet interface 2/1 named Ethernet 2/1.1 where .1 indicates the subinterface. Cisco NX-OS enables subinterfaces when the parent interface is enabled. You can shut down a subinterface independent of shutting down the parent interface. If you shut down the parent interface, Cisco NX-OS shuts down all associated subinterfaces as well.

  • Page 37: Loopback Interfaces

    Licensing Requirements for Layer 3 Interfaces This feature does not require a license. Any feature not included in a license package is bundled with the Cisco NX-OS system images and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide.

  • Page 38: Default Settings For Layer 3 Interfaces

    Configuring Layer 3 Interfaces Default Settings for Layer 3 Interfaces • If you change a Layer 2 interface to a Layer 3 interface, Cisco NX-OS shuts down the interface, reenables the interface, and deletes all configuration specific to Layer 2.

  • Page 39: Configuring A Subinterface

    Configures IEEE 802.1Q VLAN encapsulation on the subinterface. The range for the vlan-id is from 2 to 4093. Step 5 (Optional) switch(config-if)# show interfaces Displays the Layer 3 interface statistics. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 40: Configuring The Bandwidth On An Interface

    (if a value is not specified). Step 4 (Optional) switch(config-if)# copy running-config Saves the change persistently through reboots and restarts startup-config by copying the running configuration to the startup configuration. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 41: Configuring A Vlan Interface

    Saves the change persistently through reboots and restarts startup-config by copying the running configuration to the startup configuration. Example This example shows how to create a VLAN interface: switch# configure terminal switch(config)# feature interface-vlan Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 42: Configuring A Loopback Interface

    Example This example shows how to create a loopback interface: switch# configure terminal switch(config)# interface loopback 0 switch(config-if)# ip address 192.0.2.100/8 switch(config-if)# copy running-config startup-config Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 43: Assigning An Interface To A Vrf

    This example shows how to add a Layer 3 interface to the VRF: switch# configure terminal switch(config)# interface loopback 0 switch(config-if)# vrf member RemoteOfficeVRF switch(config-if)# ip address 209.0.2.1/16 switch(config-if)# copy running-config startup-config Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 44: Verifying The Layer 3 Interfaces Configuration

    Displays the VLAN interface operational status. show interface vlan number description Displays the VLAN interface description. show interface vlan number status Displays the VLAN interface administrative status and protocol status. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 45: Monitoring Layer 3 Interfaces

    Displays the VLAN interface counters reported by SNMP MIBs. You cannot clear these counters. Configuration Examples for Layer 3 Interfaces This example shows how to configure Ethernet subinterfaces: Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 46: Related Documents For Layer 3 Interfaces

    3548 Switch NX-OS Layer 2 Switching Configuration Guide MIBs for Layer 3 Interfaces MIB Link IF-MIB To locate and download MIBs, go to the following URL: CISCO-IF-EXTENSION-MIB http://www.cisco.com/public/sw-center/netmgmt/ cmtk/mibs.shtml ETHERLIKE-MIB Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 47: Standards For Layer 3 Interfaces

    Standards for Layer 3 Interfaces Standards for Layer 3 Interfaces No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 48 Configuring Layer 3 Interfaces Standards for Layer 3 Interfaces Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 49: Configuring Port Channels

    Overview, on page 43 Understanding Port Channels Using port channels, Cisco NX-OS provides wider bandwidth, redundancy, and load balancing across the channels. You can collect ports into a static port channel or you can enable the Link Aggregation Control Protocol (LACP).

  • Page 50: Compatibility Requirements

    Cisco NX-OS creates a matching port channel automatically if the port channel does not already exist. You can also create the port channel first. In this instance, Cisco NX-OS creates an empty channel group with the same channel number as the port channel and takes the default configuration.
  • Page 51 • When an interface joins or leaves a port channel, the following parameters remain unaffected: • Beacon • Description • CDP • LACP port priority • Debounce • UDLD • Shutdown Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 52: Load Balancing Using Port Channels

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

  • Page 53: Understanding Lacp

    Figure 4: Individual Links Combined into a Port Channel With LACP, just like with static port channels, you can bundle up to 16 interfaces in a channel group. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 54: Lacp Id Parameters

    Configuring Port Channels LACP ID Parameters Note When you delete the port channel, Cisco NX-OS automatically deletes the associated channel group. All member interfaces revert to their previous configuration. You cannot disable LACP while any LACP configurations are present. LACP ID Parameters LACP uses the following parameters: •...

  • Page 55: Lacp Marker Responders

    Table 5: 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 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 56: Lacp Port Channel Minlinks

    Configuring Port Channels Creating a Port Channel You can create a port channel before creating a channel group. Cisco NX-OS automatically creates the associated channel group. Note If you want LACP-based port channels, you need to enable LACP.

  • Page 57: Adding A Port To A Port Channel

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

  • Page 58: Configuring Load Balancing Using Port Channels

    | source-dest-ip | source-dest-mac | source-dest-port | source-ip | source-mac | source-port] | crc-poly} 3. (Optional) switch(config)# no port-channel load-balance ethernet 4. (Optional) switch# show port-channel load-balance DETAILED STEPS Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 59: Enabling Lacp

    Enables LACP on the switch. Step 3 (Optional) switch(config)# show feature Displays enabled features. Example This example shows how to enable LACP: switch# configure terminal switch(config)# feature lacp Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 60: Configuring The Channel Mode For A Port

    When you run port channels with no associated protocol, the channel mode is always on. Step 4 switch(config-if)# no channel-group number mode Returns the port mode to on for the specified interface. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 61: Configuring Lacp Port Channel Minlinks

    The default value for number is 1. The range is from 1 to Use the no form of this command to disable this feature. Step 4 (Optional) switch(config)# show running-config interface Displays the port channel MinLinks configuration. port-channel number Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 62: Configuring The Lacp Fast Timer Rate

    1/4 switch(config-if)# lacp rate fast This example shows how to restore the LACP default rate (30 seconds) on Ethernet interface 1/4. switch# configure terminal Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

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

    You can configure each link in the LACP port channel for the port priority. Before you begin Ensure that you have enabled the LACP feature. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# interface type slot/port 3. switch(config-if)# lacp port-priority priority Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 64: Verifying Port Channel Configuration

    Displays the traffic statistics for port channels. Displays the range of used and unused channel numbers. show port-channel usage show port-channel database Displays information on current running of the port channel feature. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

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

    0 src-port: 0 dst-ip: 1.225.225.225 src-ip: 1.1.10.10 dst-mac: 0000.0000.0000 src-mac: aabb.ccdd.eeff Example This example shows the output of the port-channel load-balance command while the device is in warp mode: Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 66 Load-balance Algorithm on switch: source-dest-ip Outgoing port id (no cache hit): Ethernet1/29 Outgoing port id (cache hit): Ethernet1/32 Param(s) used to calculate load-balance: dst-ip: 2.2.2.2 src-ip: 1.1.1.1 dst-mac: 0000.0000.0000 src-mac: 0000.0000.0000 VLAN: 1 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 67: Configuring Virtual Port Channels

    A virtual port channel (vPC) allows links that are physically connected to two different Cisco Nexus devices or Cisco Nexus Fabric Extenders to appear as a single port channel by a third device (see the following figure). The third device can be a switch, server, or any other networking device. You can configure vPCs in topologies that include Cisco Nexus devices connected to Cisco Nexus Fabric Extenders.

  • Page 68: Terminology

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

  • Page 69: Peer-Keepalive Link And Messages

    ID. After you create a vPC domain, the Cisco NX-OS software automatically creates a system priority for the vPC domain. You can also manually configure a specific system priority for the vPC domain.

  • Page 70: Compatibility Parameters For Vpc Peer Links

    Compatibility Parameters for vPC Peer Links Note We recommend that you configure the vPC peer-keepalive link on the Cisco Nexus device to run in the management VRF using the mgmt 0 interfaces. If you configure the default VRF, ensure that the vPC peer link is not used to carry the vPC peer-keepalive messages.

  • Page 71: Configuration Parameters That Must Be Identical

    Note To ensure that none of the vPC interfaces are in the suspend mode, enter the show vpc brief and show vpc consistency-parameters commands and check the syslog messages. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 72: Configuration Parameters That Should Be Identical

    Viewing Type-1 Inconsistency Check After you have configured the Virtual Port Channels (vPC) peer link on both vPC peer switches, check that the configurations are consistent on all vPC interfaces. Cisco NX-OS Release 9.x supports vPC in warp mode. Note You must ensure that both the vPC peers are in the same forwarding mode.

  • Page 73: Per-Vlan Consistency Check

    A vPC peer link is the link that is used to synchronize the states between the vPC peer devices. Note You must configure the peer-keepalive link before you configure the vPC peer link or the peer link will not come up. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 74: Vpc Peer Link Overview

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

  • Page 75: Vpc Number

    STP enhancement features on VPC peer links. You must configure a list of parameters to be identical on the vPC peer switches on both sides of the vPC peer link. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 76: Cfsoe

    The vPC peer switch feature was added to address performance concerns around STP convergence. This feature allows a pair of Cisco Nexus 3500 Series switches to appear as a single STP root in the Layer 2 topology. This eliminates the need to pin the STP root to the vPC primary switch and improves vPC convergence if the vPC primary switch fails.

  • Page 77: Guidelines And Limitations For Vpcs

    • vPC is not qualified with IPv6. • VPC is now supported in Warp mode on the Cisco Nexus 3500 Series platform. • You must enable the vPC feature before you can configure vPC peer-link and vPC interfaces.

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

    Note vPC peer device that you are working on. For information about the switch output, see the Command Reference for your Cisco Nexus Series switch. Viewing the Graceful Type-1 Check Status This example shows how to display the current status of the graceful Type-1 consistency check:...
  • Page 79 Graceful Consistency Check : Enabled vPC Peer-link status --------------------------------------------------------------------- Port Status Active vlans ---- ------ -------------------------------------------------- 1-10 vPC status ---------------------------------------------------------------------------- Port Status Consistency Reason Active vlans ------ ----------- ------ ----------- -------------------------- ----------- Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

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

    Per-vlan consistency status : success Type-2 consistency status : success vPC role : primary Number of vPCs configured Peer Gateway : Disabled Dual-active excluded VLANs Graceful Consistency Check : Enabled Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 81: Viewing A Per-Vlan Consistency Status

    ------ ----------- ------ ----------- -------------------------- ----------- Po20 success success 1-10 Po30 success success 1-10 Entering no spanning-tree vlan 5 command triggers the inconsistency on the primary and secondary VLANs: switch(config)# no spanning-tree vlan 5 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 82 ---------------------------------------------------------------------------- Port Status Consistency Reason Active vlans ------ ----------- ------ ----------- -------------------------- ----------- Po20 success success 1-4,6-10 Po30 success success 1-4,6-10 This example shows the inconsistency as STP Disabled: Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 83: Vpc Default Settings

    Enabling vPCs You must enable the vPC feature before you can configure and use vPCs. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# feature vpc 3. (Optional) switch# show feature Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 84: Disabling Vpcs

    Disabling vPCs You can disable the vPC feature. Note When you disable the vPC feature, the Cisco Nexus device clears all the vPC configurations. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# no feature vpc 3. (Optional) switch# show feature 4.

  • Page 85: Creating A Vpc Domain

    Step 4 (Optional) switch# show vpc brief Displays brief information about each vPC domain. Step 5 (Optional) switch# copy running-config startup-config Copies the running configuration to the startup configuration. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 86: Configuring A Vpc Keepalive Link And Messages

    You can configure the destination IP for the peer-keepalive link that carries the keepalive messages. Optionally, you can configure other parameters for the keepalive messages. The Cisco NX-OS software uses the peer-keepalive link between the vPC peers to transmit periodic, configurable keepalive messages. You must have Layer 3 connectivity between the peer devices to transmit these messages.
  • Page 87 (Optional) switch# copy running-config startup-config Copies the running configuration to the startup configuration. Example This example shows how to configure the destination IP address for the vPC-peer-keepalive link: switch# configure terminal Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 88 64 bytes from 123.1.1.1: icmp_seq=3 ttl=254 time=4.971 ms 64 bytes from 123.1.1.1: icmp_seq=4 ttl=254 time=4.915 ms --- 123.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0.00% packet loss round-trip min/avg/max = 3.234/4.603/4.971 ms Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 89: Creating A Vpc Peer Link

    (Optional) switch# copy running-config startup-config Copies the running configuration to the startup configuration. Example This example shows how to configure a vPC peer link: switch# configure terminal switch(config)# interface port-channel 20 switch(config-if)# vpc peer-link Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 90: Checking The Configuration Compatibility

    STP Disabled None None STP MST Region Name "" "" STP MST Region Revision STP MST Region Instance to VLAN Mapping STP Loopguard Disabled Disabled STP Bridge Assurance Enabled Enabled Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 91: Enabling Vpc Auto-Recovery

    This example shows how to view the status of the auto-recovery feature in vPC domain 10: switch(config-vpc-domain)# show running-config vpc !Command: show running-config vpc !Time: Tue Dec 7 02:38:44 2010 feature vpc vpc domain 10 peer-keepalive destination 10.193.51.170 auto-recovery Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 92: Configuring The Restore Time Delay

    When a vPC peer-link is lost, the vPC secondary switch suspends its vPC member ports and its switch virtual interface (SVI) interfaces. All Layer 3 forwarding is disabled for all VLANs on the vPC secondary switch. You can exclude specific SVI interfaces so that they are not suspended. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 93: Configuring The Vrf Name

    The switch services, such as ping, ssh, telnet, radius, are VRF aware. You must configure the VRF name in order for the correct routing table to be used. You can specify the VRF name. SUMMARY STEPS 1. switch# ping ipaddress vrf vrf-name Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 94: Moving Other Port Channels Into A Vpc

    Enters global configuration mode. Step 2 switch(config)# interface port-channel channel-number Selects the port channel that you want to put into the vPC to connect to the downstream switch, and enters interface configuration mode. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 95: Manually Configuring A Vpc Domain Mac Address

    You must configure both switches on either side of the vPC peer link. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# vpc domain domain-id 3. switch(config-vpc-domain)# system-mac mac-address 4. (Optional) switch# show vpc role 5. (Optional) switch# copy running-config startup-config Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 96: Manually Configuring The System Priority

    You must configure both switches on either side of the vPC peer link. SUMMARY STEPS 1. switch# configure terminal 2. switch(config)# vpc domain domain-id 3. switch(config-vpc-domain)# system-priority priority 4. (Optional) switch# show vpc brief 5. (Optional) switch# copy running-config startup-config Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 97: Manually Configuring A Vpc Peer Switch Role

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

  • Page 98: Configuring Layer 3 Over Vpc

    Before you begin Cisco NX-OS supports configuring 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 carried out on the vPC peer-link is supported with the following requirements: •...
  • Page 99 2 switch(config-vpc-domain)# peer-gateway switch(config-vpc-domain)# layer3 peer-router switch(config-vpc-domain)# exit switch(config)# The following example shows how to verify if the Layer 3 over vPC is configured: Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 100 ------------------------------------------------------ Port Status Consistency Reason Active vlans ------------------------------------------------------ Po400 success success Po500 success success Po401 success success Po402 success success Po403 success success Po501 success success Po502 success success switch(config)# Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 101: Configuring Static And Dynamic Nat Translation

    When a packet enters the domain, NAT translates the globally unique destination IP address into a local IP address. If more than one exit point exists, NAT configured at each point must have the same translation table. NAT is described in RFC 1631. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 102: Information About Static Nat

    It allows both IP addresses and port number translations from the inside to the outside traffic and the outside to the inside traffic. The Cisco Nexus device supports Hitless NAT, which means that you can add or remove a NAT translation in the NAT configuration without affecting the existing NAT traffic flows.

  • Page 103: Dynamic Nat Overview

    IP address by using different ports. Your NAT configuration can have multiple dynamic NAT translations with same or different ACLs. However, for a given ACL, only one interface can be specified. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 104: Timeout Mechanisms

    After dynamic NAT translations are created, they must be cleared when not in use so that newer translations can be created, especially because the number of TCAM entries is limited. Cisco NX-OS Release 7.x supports syn-timeout and finrst-timeout. The following NAT translation timeout timers are supported on the switch: •...

  • Page 105: Nat Inside And Outside Addresses

    NAT and static NAT is that static NAT allows a remote host to initiate a connection to a translated host if an access list exists that allows it, while dynamic NAT does not. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 106: Static And Dynamic Twice Nat Overview

    Static NAT requires a LAN Base license and an Algo Boost license. For a complete explanation NX-OS of the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide. Make sure the LAN Base Services license is installed on the switch to enable Layer Note 3 interfaces.

  • Page 107: Guidelines And Limitations For Static Nat

    • NAT supports up to 1024 translations which include both static and dynamic NAT. • Cisco Nexus 3500 Series switches do not support static and dynamic NAT on vPC topology. • The Cisco Nexus device supports NAT on the following interface types: •...

  • Page 108: Restrictions For Dynamic Nat

    • If the translated IP is part of the outside interface subnet, then use the ip local-proxy-arp command on the NAT outside interface. • When creating a new translation on a Cisco Nexus 3548 Series switch, the flow is software forwarded until the translation is programmed in the hardware, which might take a few seconds. During this period, there is no translation entry for the inside global address.

  • Page 109: Configuring Static Nat

    TCAM space. • NAT is ECMP aware and it supports a maximum of 24 ECMP paths. • Cisco NX-OS Release 9.x supports Network Address Translation (NAT) statistics on Cisco Nexus 3548 switches. • Traceroute is not supported on static and dynamic NAT...

  • Page 110: Enabling Static Nat For An Inside Source Address

    IP address gets translated back to the inside local IP address. Note When the Cisco Nexus device is configured to translate an inside source IP address (Src:ip1) to an outside source IP address (newSrc:ip2), the Cisco Nexus device implicitly adds a translation for an outside destination IP address (Dst: ip2) to an inside destination IP address (newDst: ip1).

  • Page 111: Enabling Static Nat For An Outside Source Address

    Example This example show how to configure static NAT for an outside source address: switch# configure terminal switch(config)# ip nat outside source static 2.2.2.2 6.6.6.6 switch(config)# copy running-config startup-config Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 112: Configuring Static Pat For An Inside Source Address

    1. switch# configure terminal 2. switch(config)# ip nat outside source static {outside-global-address outside-local-address | {tcp | udp} outside-global-address {global-tcp-port | global-udp-port} outside-local-address {global-tcp-port | global-udp-port}}group group-id add-route 3. (Optional) switch(config)# copy running-config startup-config Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 113: Configuring Static Twice Nat

    [group group-id] [add-route] interface type number ip address ip-address mask ip nat inside exit interface type number ip address ip-address mask ip nat outside 12. end Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 114 Configures an interface and enters interface configuration mode. Example: switch(config)# interface ethernet 1/1 Step 10 ip address ip-address mask Sets a primary IP address for an interface. Example: Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 115: Configuration Example For Static Nat And Pat

    Switch(config)# ip nat inside source static 10.1.1.1 192.168.34.4 group 4 Switch(config)# ip nat outside source static 209.165.201.1 10.3.2.42 group 4 Switch(config)# interface ethernet 1/2 Switch(config-if)# ip address 10.2.4.1 255.255.255.0 Switch(config-if)# ip nat inside Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 116: Verifying The Static Nat Configuration

    Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 117 Switch(config-acl)# deny udp 10.111.11.100/32 any matching the criteria mentioned in the deny rule are forwarded without NAT translation. Step 6 exit Exits access-list configuration mode and returns to global configuration mode. Example: Switch(config-acl)# exit Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 118 Example: • Dynamically created NAT translations are cleared Switch(config)# ip nat translation tcp-timeout when the configured timeout limit is reached. All 50000 configured timeouts are triggered after the timeout Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 119 The default value is 60 seconds. The never keyword specifies that the FIN or RST timer will not be run. Step 22 Exits global configuration mode and returns to privileged EXEC mode. Example: Switch(config)# end Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 120: Configuring Dynamic Nat Pool

    This example shows how to create a NAT pool and define the range of global IP addresses using the ip nat pool and address commands: switch# configure terminal switch(config)# ip nat pool pool7 netmask 255.255.0.0 switch(config-ipnat-pool)# address 40.1.1.1 40.1.1.5 switch(config-ipnat-pool)# Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 121: Configuring Source Lists

    This example shows how to create a NAT outside source list with pool without overloading: switch# configure terminal switch(config)# ip nat outside source list list3 pool pool3 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 122: Configuring Dynamic Twice Nat For An Inside Source Address

    The IP addresses are filtered by using either a prefix length {prefix prefix-length | netmask network-mask} or a network mask. Step 5 switch(config)# interface type slot/port Configures an interface and enters interface configuration mode. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 123: Configuring Dynamic Twice Nat For An Outside Source Address

    4. switch(config)# ip nat pool pool-name [startip endip] {prefix prefix-length | netmask network-mask} 5. switch(config)# interface type slot/port 6. switch(config-if)# ip nat outside 7. switch(config-if)# exit 8. switch(config)# interface type slot/port 9. switch(config-if)# ip nat inside Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 124: Clearing Dynamic Nat Translations

    4.4.4.4 4.4.4.10 prefix-length 24 switch(config)# interface Ethernet1/6 switch(config-if)# ip nat outside switch(config-if)# exit switch(config)# interface Ethernet1/11 switch(config-if)# ip nat inside Clearing Dynamic NAT Translations To clear dynamic translations, perform the following task: Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 125: Verifying Dynamic Nat Configuration

    30.1.1.1 30.1.1.2 prefix-length 24 ip nat pool pool2 10.1.1.1 10.1.1.2 netmask 255.0.255.0 ip nat pool pool3 30.1.1.1 30.1.1.8 prefix-length 24 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 126: Verifying Nat Statistics

    Group_id:0 VRF: red Format(H:M:S) Time-left:12:0:11 Verifying NAT Statistics To display Network Address Translation (NAT) statistics, perform the following task: Command Purpose show ip nat statistics Display Network Address Translation (NAT) statistics. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 127 NAT Inside Interfaces: Ethernet1/1 NAT Outside Interfaces: 1 Ethernet1/3 ---------------------------------------------------- Inside source list: ++++++++++++++++++++ Access list: ACL1 RefCount: 0 Pool: pool1 Overload Total addresses: 200 Allocated: 0 percentage: 0% Missed: 0 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 128: Clearing Nat Statistics

    The following example shows how to configure dynamic overload Network Address Translation (NAT) by specifying an access list: Switch> enable Switch# configure terminal Switch(config)# ip access-list acl1 Switch(config-acl)# permit ip 10.111.11.0/24 any Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 129: Information About Vrf Aware Nat

    3. switch(config)# [no] ip nat inside | outside source static LOCAL IP GLOBAL IP | [tcp | udp LOCAL IP LOCAL PORT GLOBAL IP GLOBAL PORT ] [group group-id] [dynamic] [ vrf <vrf-name> [match-in-vrf] ] 4. switch(config)# interface type slot/port [ vrf <vrf-name ip nat inside | outside Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 130 Group_id:0 VRF: red Format(H:M:S) Time-left:12:0:9 udp 101.1.0.1:65383 101.0.0.1:63 102.1.0.1:63 102.1.0.1:63 Flags:0x82 Entry-id:103 State:0x3 Group_id:0 VRF: red Format(H:M:S) Time-left:12:0:9 tcp 101.1.0.1:64549 101.0.0.1:8809 102.1.0.1:9087 102.1.0.1:9087 Flags:0x82 Entry-id:102 State:0x1 Group_id:0 VRF: red Format(H:M:S) Time-left:12:0:9 syn:0:1:9 fin-rst:12:0:9 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 131: Configuring Ip Event Dampening

    An unstable interface that flaps excessively can cause other devices in the network to Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 132: Interface State Change Events

    The maximum suppress time can be configured from 1 to 255 seconds. The maximum penalty is truncated to maximum 20000 unit. The maximum value of the accumulated penalty is calculated based on the maximum suppress time, reuse threshold, and half-life period. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 133: Affected Components

    0. If the interface has been dampened, the accumulated penalty will fall into the reuse threshold range, and the dampened interface will be made available to the network. The flap counts, however, are retained. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...

  • Page 134: Verifying Ip Event Dampening

    2. show interface dampening DETAILED STEPS Command or Action Purpose Step 1 show dampening interface Displays dampened interfaces. Step 2 show interface dampening Displays dampened interfaces on the local router. Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x...
  • Page 135 39, 43, 44, 45, 46, 49, 51 LACP Ethernet interfaces configuring default settings marker responders Layer 3 interfaces port channel, minlinks 46, 51 Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x IN-1...
  • Page 136 Layer 3 interfaces monitoring security Layer 3 interfaces static NAT standards Layer 3 interfaces static nat 96, 105 configuration example verifying licensing 92, 99, 106 static NAT enabling interface, configuring security Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x IN-2...
  • Page 137 VLAN interfaces layer 2 configuring svi autostate, disabling vPC terminology layer 2 vPCs moving port channels into assigning an interface to 4, 5 UDLD aggressive mode Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x IN-3...
  • Page 138 INDEX Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x IN-4...

Table of Contents