Cisco 7206 - VXR Router Configuration Manual

Download

Page 1

Send document comments to nexus7k-docfeedback@cisco.com

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

September 5, 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

Page 2

Send document comments to nexus7k-docfeedback@cisco.com

HE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

Page 3

Send document comments to nexus7k-docfeedback@cisco.com

CONTENTS

New and Changed Information -xiii

Preface xv

Audience xv

Document Organization xv

Document Conventions -xvi

Obtaining Documentation and Submitting a Service Request xvii

xvii

CHAPTER

1 Overview 1-1

Information About Interfaces 1-1

Ethernet Interfaces 1-2 Management Interface 1-3 Port-Channel Interfaces 1-4 vPCs 1-4 Subinterfaces 1-4 VLAN Network Interfaces 1-4 Loopback Interfaces 1-4 Tunnel Interfaces 1-4

Virtualization Interfaces 1-5

High Availability for Interfaces 1-5

Licensing Requirements for Interfaces 1-5

2 Configuring Basic Interface Parameters 2-1

Information About the Basic Interface Parameters 2-2

Description 2-2 Beacon 2-2 MDIX 2-3 Debounce Timer 2-3 Error Disabled 2-3 Rate Mode 2-4 Speed Mode and Duplex Mode 2-4 Flow Control 2-5 Port MTU Size 2-6

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

iii

Page 4

Contents

Send document comments to nexus7k-docfeedback@cisco.com

Bandwidth 2-7 Throughput Delay 2-7 Administrative Status 2-7 Unidirectional Link Detection Parameter 2-7 Carrier Delay 2-10 Port-Channel Parameters 2-10 Port Profiles 2-10 Time Domain Reflectometry Cable Diagnostics 2-12

Licensing Requirements 2-12

Guidelines and Limitations 2-13

Default Settings 2-14

Configuring the Basic Interface Parameters 2-14

Specifying the Interfaces to Configure 2-15 Configuring the Description 2-16 Configuring the Beacon Mode 2-17 Changing the Bandwidth-Rate Mode 2-19 Configuring the Error-Disabled State 2-22 Configuring the MDIX Parameter 2-25 Configuring the Debounce Timer 2-26 Configuring the Interface Speed and Duplex Mode 2-28 Configuring the Flow Control 2-30 Configuring the MTU Size 2-31 Configuring the Bandwidth 2-34 Configuring the Throughput Delay 2-36 Shutting Down and Activating the Interface 2-37 Configuring the UDLD Mode 2-39 Configuring the Carrier Delay Timer 2-41 Configuring Port Profiles 2-43 Performing TDR Cable Diagnostics 2-51 Configuring Rate Limits for Packets that Reach the Supervisor 2-52

Verifying the Basic Interface Parameters 2-54

Monitoring the Interface Counters 2-54

Displaying Interface Statistics 2-54 Clearing Interface Counters 2-56

Additional References 2-56

related documentation.

Audience

This publication is for experienced network administrators who configure and maintain Cisco NX-OS devices.

Document Organization

This document is organized into the following chapters:

Chapter Description

Chapter 1, “Overview” Provides an overview of the Cisco NX-OS

Chapter 2, “Configuring Basic Interface Parameters”

Chapter 3, “Configuring Layer 2 Interfaces” Describes how to configure Layer 2 switching

Chapter 4, “Configuring Layer 3 Interfaces” Describes how to configure Layer 3 interfaces.

Chapter 5, “Configuring Bidirectional Forwarding Detection”

Chapter 6, “Configuring Port Channels” Describes how to configure port channels and to

Chapter 7, “Configuring vPCs” Describes how to configure virtual port channels

interfaces.

Describes how you can configure the basic parameters shared by Layer 2 and Layer 3 interfaces.

ports as access or trunk ports.

Describes how to configure Bidirectional Forwarding Detection (BFD) to provide fast forwarding-path failure detection times for media types, encapsulations, topologies, and routing protocols..

apply and configure the Link Aggregation Control Protocol (LACP) for a more efficient use of port channels.

(vPCs).

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

Page 16

Preface

Document Conventions

Send document comments to nexus7k-docfeedback@cisco.com

Chapter Description

Chapter 8, “Configuring IP Tunnels” Describes how to configure IP tunnels using

Generic Route Encapsulation (GRE) on the device.

Chapter 9, “Configuring Q-in-Q VLAN Tunnels” Describes how to configure IEEE 802.1Q-in-Q

(Q-in-Q) VLAN tunnels and Layer 2 protocol tunneling.

Chapter A, “IETF RFCs supported by Cisco NX-OS Interfaces”

Chapter B, “Configuration Limits for Cisco NX-OS Interfaces”

lists the IETF RFCs for interfaces supported in Cisco NX-OS Release 4.x

Lists the Cisco verified limits and maximum limits for devices running NX-OS Release 4.x.

Document Conventions

Command descriptions use these conventions:

Convention Description

boldface font Commands and keywords are in boldface.

italic font Arguments for which you supply values are in italics.

[ ] Elements in square brackets are optional.

[ x | y | z ] Optional alternative keywords are grouped in brackets and separated by vertical

bars.

string A nonquoted set of characters. Do not use quotation marks around the string or

the string will include the quotation marks.

Screen examples use these conventions:

screen font

boldface screen font

italic screen font

Terminal sessions and information that the switch displays are in screen font.

Information that you must enter is in boldface screen font.

Arguments for which you supply values are in italic screen font.

< > Nonprinting characters, such as passwords, are in angle brackets.

[ ] Default responses to system prompts are in square brackets.

!, # An exclamation point (!) or a pound sign (#) at the beginning of a line of code

indicates a comment line.

This document uses the following conventions:

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the

manual.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

xvi

OL-23435-03

Page 17

Preface

Document Conventions

Send document comments to nexus7k-docfeedback@cisco.com

Caution Means reader be careful. In this situation, you might do something that could result in equipment

damage or loss of data.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

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.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

xvii

Page 18

Preface

Document Conventions

Send document comments to nexus7k-docfeedback@cisco.com

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

xviii

OL-23435-03

Page 19

Send document comments to nexus7k-docfeedback@cisco.com

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

• Virtualization Interfaces, page 1-5

• High Availability for Interfaces, page 1-5

• Licensing Requirements for Interfaces, page 1-5

Information About Interfaces

Cisco NX-OS supports multiple configuration parameters for each of the interface types supported. Most of these parameters are covered in this guide but some are described in other documents.

Tabl e 1-1 shows where to get further information on the parameters you can configure for an interface.

CHAPTER

Table 1-1 Interface Parameters

Feature Parameters Further Information

Basic parameters

Layer 2 Layer 2 access and trunk port

description, duplex, error disable, flow control, MTU, beacon

settings

Layer 2 MAC, VLANs, private VLANs, Rapid PVST+, Multiple Spanning Tree, Spanning Tree Extensions

Port security Cisco Nexus 7000 Series NX-OS Security

Chapter 2, “Configuring Basic Interface Parameters” of this document

Chapter 3, “Configuring Layer 2 Interfaces” of

this document

Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x

Configuration Guide, Release 5.x

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

1-1

Page 20

Chapter 1 Overview

Information About Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Table 1-1 Interface Parameters (continued)

Feature Parameters Further Information

Layer 3 medium, IPv4 and IPv6

addresses

bandwidth, delay, IP routing, VRFs

Port Channels channel group, LACP Chapter 6, “Configuring Port Channels” of this

vPCs Virtual port channels Chapter 7, “Configuring vPCs” of this document

Tunnels GRE Tunneling Chapter 8, “Configuring IP Tunnels” of this

Security Dot1X, NAC, EOU, port security Cisco Nexus 7000 Series NX-OS Security

FCoE Beginning with Cisco NX-OS

Release 5.2(1), you can run Fibre Channel over Ethernet (FCoE) on the Cisco Nexus 7000 Series Switch

Chapter 4, “Configuring Layer 3 Interfaces” of

this document

Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x

Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide, Release 5.x

document

Configuration Guide, Release 5.x

Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500

This section includes the following topics:

• Ethernet Interfaces, page 1-2

• Management Interface, page 1-3

• Port-Channel Interfaces, page 1-4

• vPCs, page 1-4

• Subinterfaces, page 1-4

• VLAN Network Interfaces, page 1-4

• Loopback Interfaces, page 1-4

• Tunnel Interfaces, page 1-4

Ethernet Interfaces

Ethernet interfaces include access ports, trunk ports, private VLAN hosts and promiscuous ports, and routed ports.

This section includes the following topics:

• Access Ports, page 1-3

• Trunk Ports, page 1-3

• Private VLAN Hosts and Promiscuous Ports, page 1-3

• Routed Ports, page 1-3

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

1-2

OL-23435-03

Page 21

Chapter 1 Overview

Information About Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Access Ports

An access port carries traffic for one VLAN. This type of port is a Layer 2 interface only. For more information about access-port interfaces, see Chapter 3, “Configuring Layer 2 Interfaces.”

Trunk Ports

A trunk port carries traffic for two or more VLANs. This type of port is a Layer 2 interface only. For more information about trunk-port interfaces, see Chapter 3, “Configuring Layer 2 Interfaces.”

Private VLAN Hosts and Promiscuous Ports

Private VLANs (PVLANs) provide traffic separation and security at the Layer 2 level. A PVLAN is one or more pairs of a primary VLAN and a secondary VLAN, all with the same primary VLAN. The two types of secondary VLANs are called isolated and community VLANs.

In an isolated VLAN, PVLAN hosts communicate only with hosts in the primary VLAN. In a community VLAN, PVLAN hosts communicate only among themselves and with hosts in the primary VLAN but not with hosts in isolated VLANs or in other community VLANs. Community VLANs use promiscuous ports to communicate outside the PVLAN. Regardless of the combination of isolated and community secondary VLANs, all interfaces within the primary VLAN comprise one Layer 2 domain and require only one IP subnet.

You can configure a Layer 3 VLAN network interface, or switched virtual interface (SVI), on the 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.

Routed Ports

A routed port is a physical port that can route IP traffic to another device. A routed port is a Layer 3 interface only and does not support Layer 2 protocols, such as Spanning Tree Protocol (STP). For more information on routed ports, see the “Routed Interfaces” section on page 4-2.

Management Interface

You can use the management Ethernet interface to connect the device to a network for remote management using a Telnet client, the Simple Network Management Protocol (SNMP), or other management agents. The management port (mgmt0) is autosensing and operates in full-duplex mode at a speed of 10/100/1000 Mb/s.

For more information on the management interface, see the Cisco Nexus 7000 Series NX-OS Fundamentals Configuration Guide, Release 5.x. You will also find information on configuring the IP address and default IP routing for the management interface in this document.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

1-3

Page 22

Chapter 1 Overview

Information About Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Port-Channel Interfaces

A port channel is a logical interface that is an aggregation of multiple physical interfaces. You can bundle up to 8 individual links to physical ports into a port channel to improve bandwidth and redundancy. You can also use port channeling to load balance traffic across these channeled physical interfaces. For more information about port-channel interfaces, see 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. You can configure a total of 768 vPCs on each device. vPCs provide Layer 2 multipathing. For more information about vPCs, see Chapter 7, “Configuring vPCs.”

Subinterfaces

You can create virtual subinterfaces on a parent interface configured as a Layer 3 interface. A parent interface can be a physical port or a port channel. Subinterfaces divide the parent interface into two or more virtual interfaces on which you can assign unique Layer 3 parameters such as IP addresses and dynamic routing protocols. For more information on subinterfaces, see the “Subinterfaces” section on

page 4-2.

VLAN Network Interfaces

A VLAN network interface is a virtual routed interface that connects a VLAN on the device to the Layer 3 router engine on the same device. You can route across VLAN network interfaces to provide Layer 3 inter-VLAN routing. For more information on VLAN network interfaces, see the “VLAN Interfaces”

section on page 4-3.

Loopback Interfaces

A virtual loopback interface is a virtual interface with a single endpoint that is always up. Any packet that is transmitted over a virtual loopback interface is immediately received by that interface. Loopback interfaces emulate a physical interface. For more information on subinterfaces, see the “Loopback

Interfaces” section on page 4-4.

Tunnel Interfaces

Tunneling allows you to encapsulate arbitrary packets inside a transport protocol. This feature is implemented as a virtual interface to provide a simple interface for configuration. The tunnel interface provides the services necessary to implement any standard point-to-point encapsulation scheme. You can configure a separate tunnel for each link. For more information, see Chapter 8, “Configuring IP

Tunnels.”

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

1-4

OL-23435-03

Page 23

Chapter 1 Overview

Virtualization Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Virtualization Interfaces

You can create multiple virtual device contexts (VDCs). Each VDC is an independent logical device to which you can allocate 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.

High Availability for Interfaces

Interfaces support stateful and stateless restarts. A stateful restart occurs on a supervisor switchover. After the switchover, Cisco NX-OS applies the runtime configuration after the switchover.

Licensing Requirements for Interfaces

IP tunnels and vPCs require the Enterprise Services license. You must install this license on every system that enables IP tunnels. All other interfaces do not require a license.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

1-5

Page 24

Chapter 1 Overview

Licensing Requirements for Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

1-6

OL-23435-03

Page 25

Send document comments to nexus7k-docfeedback@cisco.com

CHAPTER

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

• Licensing Requirements, page 2-12

• Guidelines and Limitations, page 2-13

• Default Settings, page 2-14

• Configuring the Basic Interface Parameters, page 2-14

• Verifying the Basic Interface Parameters, page 2-54

• Monitoring the Interface Counters, page 2-54

• Feature History for Configuring Basic Interface Parameters, page 2-57

Note To configure the parameters that are specifically used for Layer 2 interfaces (access or trunking

interfaces), see Chapter 3, “Configuring Layer 2 Interfaces.” To configure parameters that are specifically used for Layer 3 interfaces (routed interfaces, subinterfaces, VLAN interfaces, loopback interfaces, and IP tunnels), see Chapter 4, “Configuring Layer 3 Interfaces.”

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-1

Page 26

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Information About the Basic Interface Parameters

This section includes the following topics:

• Description, page 2-2

• Beacon, page 2-2

• MDIX, page 2-3

• Debounce Timer, page 2-3

• Error Disabled, page 2-3

• Rate Mode, page 2-4

• Speed Mode and Duplex Mode, page 2-4

• Flow Control, page 2-5

• Port MTU Size, page 2-6

• Bandwidth, page 2-7

• Throughput Delay, page 2-7

Description

Beacon

• Administrative Status, page 2-7

• Unidirectional Link Detection Parameter, page 2-7

• Carrier Delay, page 2-10

• Port-Channel Parameters, page 2-10

• Port Profiles, page 2-10

• Time Domain Reflectometry Cable Diagnostics, page 2-12

For the Ethernet and management interfaces, you can configure the description parameter to provide a recognizable name for the interface. Using a unique name for each interface allows you to quickly identify the interface when you are looking at a listing of multiple interfaces.

For information on setting the description parameter for port-channel interfaces, see the “Configuring a

Port-Channel Description” section on page 6-24. For information on configuring this parameter for other

interfaces, see the “Configuring the Description” section on page 2-16.

The beacon mode allows you to identify a physical port by flashing its link state LED with a green light. 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

2-2

OL-23435-03

Page 27

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

MDIX

The medium dependent interface crossover (MDIX) parameter enables or disables the detection of a crossover connection between devices. This parameter applies only to copper interfaces. By default, this parameter is enabled.

For information on configuring the MDIX parameter, see the “Configuring the MDIX Parameter” section

on page 2-25.

Debounce Timer

The debounce timer delays notification of a link change, which can decrease traffic loss due to network reconfiguration. You can configure the debounce timer separately for each Ethernet port and specify the delay time in milliseconds. By default, this parameter is set for 100 milliseconds.

Caution Enabling the debounce timer causes the link-down detections to be delayed, which results in a loss of

traffic during the debounce period. This situation might affect the convergence and reconvergence of some Layer 2 and Layer 3 protocols.

Error Disabled

For information on configuring the debounce-timer parameters, see the “Configuring the Debounce

Timer” section on page 2-26.

A port is in the error-disabled (err-disabled) state when the port is enabled administratively (using the no shutdown command) but disabled at runtime by any process. For example, if UDLD detects a unidirectional link, the port is shut down at runtime. However, because the port is administratively enabled, the port status displays as err-disable. Once a port goes into the err-disable state, you must manually reenable it or you can configure a timeout value that provides an automatic recovery. By default, the automatic recovery is not configured, and by default the err-disable detection is enabled for all causes.

When an interface is in the err-disabled state, use the errdisable detect cause command to find information about the error.

You can configure the automatic error-disabled recovery timeout for a particular error-disabled cause and configure the recovery period.

The errdisable recovery cause command provides an automatic recovery after 300 seconds.

You can use the errdisable recovery interval command to change the recovery period within a range of 30 to 65535 seconds. You can also configure the recovery timeout for a particular err-disable cause

If you do not enable the error-disabled recovery for the cause, the interface stays in the error-disabled state until you enter the shutdown and no shutdown commands. If the recovery is enabled for a cause, the interface is brought out of the error-disabled state and allowed to retry operation once all the causes have timed out. Use the show interface status err-disabled command to display the reason behind the error.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-3

Page 28

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Rate Mode

On a 32-port 10-Gigabit Ethernet module, each set of four ports can handle 10 gigabits per second (Gb/s) of bandwidth. You can use the rate-mode parameter to dedicate that bandwidth to the first port in the set of four ports or share the bandwidth across all four ports.

Tabl e 2-1 identifies the ports that are grouped together to share each 10 Gb/s of bandwidth and which

port in the group can be dedicated to utilize the entire bandwidth.

Table 2-1 Dedicated and Shared Ports

Ports that Can be Ports Groups that Can Share Bandwidth

1, 3, 5, 7 1

2, 4, 6, 8 2

9, 11, 13, 15 9

10, 12, 14, 16 10

17, 19, 21, 23 17

18, 20, 22, 24 18

25, 27, 29, 31 25

26, 28, 30, 32 26

Dedicated to Each

10-Gigabit Ethernet

of Bandwidth

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. By default, each of these interfaces autonegotiates its speed and duplex mode with the other interface, but you can change these settings. If you change the settings, be sure to use the same speed and duplex mode setting on both interfaces, or use autonegotiation for at least one of the interfaces. Tab le 2-2 shows the settings that work for each type of Ethernet and management interface.

Table 2-2 Speed- and Duplex-Mode Settings Used for Ethernet and Management Interfaces

Module Type

N7K-M132XP-12 32-port 10-Gigabit Ethernet

N7K-M108X2-12L 8-port 10-Gigabit Ethernet

Speed Mode Setting

Auto

Duplex Mode Setting

Auto

Operational Speed (Mb/s)

Operational Duplex Mode

10,000 Full

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-4

OL-23435-03

Page 29

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Table 2-2 Speed- and Duplex-Mode Settings Used for Ethernet and Management Interfaces

Speed Mode

Module Type

N7K-M148GS-11

Setting

Auto N7K-M148GS-11L 48-port 1-Gigabit Ethernet

N7K-M148GT-11

Auto 48-port 10/100/1000 Ethernet

1000 Auto

100 Auto

10 Auto

Management Auto

1000 Auto

100 Auto

10 Auto

1. Default setting

Duplex Mode Setting

Auto

Operational Speed (Mb/s)

Operational Duplex Mode

1000 Full

10 or 100 Half

or full 1000 Full

or half 100 Half

Full 100 Full

or half 10 Half

Full 10 Full

Auto

1000 Full

10 or 100 Half

or full 1000 Full

or half 100 Half

Full 100 Full

or half 10 Half

Full 10 Full

Flow Control

For information on setting the speed mode and duplex mode for port-channel interfaces, see the

“Configuring the Speed and Duplex Settings for a Port-Channel Interface” section on page 6-25. For

information on setting the speed and duplex speed for other interfaces, see the “Configuring the Interface

Speed and Duplex Mode” section on page 2-28.

When the receive buffer for an Ethernet port that runs 1 Gb/s or faster fills, flow control enables that port to send an IEEE 802.3x pause frame to the transmitting port to request it to stop transmitting data for a specified amount of time. Transmitting ports, running at any speed, can receive the pause frames to stop their transmission of data.

To allow flow control to work between two ports, you must set the corresponding receive and send flow control parameters for both ports as enabled or desired. When you set the parameter to enabled, the send or receive flow-control function is activated regardless of the setting of the other port. When you set the parameter to desired, the send or receive flow-control function is activated if you set the corresponding flow-control state of the other port to enabled or desired. 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 .

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-5

Page 30

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Table 2-3 Port Flow-Control Influences on Link Flow Control

Port Flow Control States

Port Receiving Data (Sends Pause Frames)

Port Transmitting Data (Receives Pause Frames)

Enabled Enabled Enabled

Enabled Desired Enabled

Enabled Disabled Disabled

Desired Enabled Enabled

Desired Desired Enabled

Desired Disabled Disabled

Disabled Enabled Disabled

Disabled Desired Disabled

Disabled Disabled Disabled

Link Flow Control State

Port MTU Size

Note The global LAN port MTU size applies to the traffic through a Layer 3 Ethernet LAN port that is

For information on setting the flow-control parameters, see the “Configuring the Flow Control” section

on page 2-30.

The maximum transmission unit (MTU) size specifies the maximum frame size that an Ethernet port can process. For transmissions to occur between two ports, you must configure the same MTU size for both ports. A port drops any frames that exceed its MTU size.

By default, each port has an MTU of 1500 bytes, which is the IEEE 802.3 standard for Ethernet frames. Larger MTU sizes are possible for more efficient processing of data with less overhead. The larger frames, called jumbo frames, can be up to 9216 bytes in size, which is also the default system jumbo MTU size.

On a Layer 3 interface, you can configure an MTU size between 576 and 9216 bytes. You can configure up to 64 MTU settings for each I/O module.

configured with a nondefault MTU size.

For a Layer 2 port, you can configure an MTU size that is either the system default (1500 bytes) or the system jumbo MTU size (initially 9216 bytes).

Note If you change the system jumbo MTU size, Layer 2 ports automatically use the system default 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

2-6

OL-23435-03

Page 31

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Bandwidth

Ethernet ports have a fixed bandwidth of 1,000,000 Kb at the physical level. Layer 3 protocols use a bandwidth value that you can set for calculating their internal metrics. The value that you set is used for informational purposes only by the Layer 3 protocols—it does not change the fixed bandwidth at the physical level. For example, the Interior Gateway Routing Protocol (IGRP) uses the minimum path bandwidth to determine a routing metric, but the bandwidth at the physical level remains at 1,000,000 Kb.

For information on configuring the bandwidth parameter for port-channel interfaces, see the

“Configuring the Bandwidth and Delay for Informational Purposes” section on page 6-21. For

information on configuring the bandwidth parameter for other interfaces, see the “Configuring the

Bandwidth” section on page 2-34.

Throughput Delay

Specifying a value for the throughput-delay parameter provides a value used by Layer 3 protocols; it does not change the actual throughput delay of an interface. The Layer 3 protocols can use this value to make operating decisions. For example, EIGRP can use the delay setting to set a preference for one Ethernet link over another, if other parameters such as link speed are equal. The delay value that you set is in the tens of microseconds.

For information on configuring the bandwidth parameter for port-channel interfaces, see the

“Configuring the Bandwidth and Delay for Informational Purposes” section on page 6-21. For

information on configuring the throughput-delay parameter for other interfaces, see the “Configuring the

Throughput Delay” section on page 2-36.

Administrative Status

The administrative-status parameter determines whether an interface is up or down. When an interface is administratively down, it is disabled and unable to transmit data. When an interface is administratively up, it is enabled and able to transmit data.

For information on configuring the administrative status parameter for port-channel interfaces, see the

“Shutting Down and Restarting the Port-Channel Interface” section on page 6-22. For information on

configuring the administrative-status parameter for other interfaces, see the “Shutting Down and

Activating the Interface” section on page 2-37.

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

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-7

Page 32

Chapter 2 Configuring Basic Interface Parameters

Device A

Device B

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

UDLD Overview

The Cisco-proprietary Unidirectional Link Detection (UDLD) protocol allows devices that are connected through fiber-optic or copper (for example, Category 5 cabling) Ethernet cables to monitor the physical configuration of the cables and detect when a unidirectional link exists. When a device detects a unidirectional link, UDLD shuts down the affected LAN port and alerts the user. Unidirectional links can cause a variety of problems, including spanning tree topology loops.

UDLD is a Layer 2 protocol that works with the Layer 1 protocols to determine the physical status of a link. At Layer 1, autonegotiation takes care of physical signaling and fault detection. UDLD performs tasks that autonegotiation cannot perform, such as detecting the identities of neighbors and shutting down misconnected LAN ports. When you enable both autonegotiation and UDLD, Layer 1 and Layer 2 detections work together to prevent physical and logical unidirectional connections and the malfunctioning of other protocols.

A unidirectional link occurs whenever traffic transmitted by the local device over a link is received by the neighbor but traffic transmitted from the neighbor is not received by the local device. If one of the fiber strands in a pair is disconnected, as long as autonegotiation is active, the link does not stay up. In this case, the logical link is undetermined, and UDLD does not take any action. If both fibers are working normally at Layer 1, then UDLD at Layer 2 determines whether those fibers are connected correctly and whether traffic is flowing bidirectionally between the correct neighbors. This check cannot be performed by autonegotiation, because autonegotiation operates at Layer 1.

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. Devices on both ends of the link must support UDLD in order for the protocol to successfully identify and disable unidirectional links. You can configure the transmission interval for the UDLD frames, either globally or for the specified interfaces.

Note By default, UDLD is locally disabled on copper LAN ports to avoid sending unnecessary control traffic

on this type of media.

Figure 2-1 shows an example of a unidirectional link condition. Device B successfully receives traffic

from device A on the port. However, device A does not receive traffic from device B on the same port. UDLD detects the problem and disables the port.

Figure 2-1 Unidirectional Link

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-8

OL-23435-03

Page 33

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Default UDLD Configuration

Tabl e 2-4 shows the default UDLD configuration.

Table 2-4 UDLD Default Configuration

Feature Default Value

UDLD global enable state Globally disabled

UDLD per-port enable state for fiber-optic media

UDLD per-port enable state for twisted-pair (copper) media

UDLD aggressive mode Disabled

UDLD message interval

For information on configuring the UDLD for the device and its port, see the “Configuring the UDLD

Mode” section on page 2-39.

Enabled on all Ethernet fiber-optic LAN ports

Disabled on all Ethernet 10/100 and 1000BASE-TX LAN ports

15 seconds

UDLD Aggressive and Nonaggressive Modes

UDLD aggressive mode is disabled by default. You can configure UDLD aggressive mode only on point-to-point links between network devices that support UDLD aggressive mode. If UDLD aggressive mode is enabled, when a port on a bidirectional link that has a UDLD neighbor relationship established stops receiving UDLD frame, UDLD tries to reestablish the connection with the neighbor. After eight failed retries, the port is disabled.

To prevent spanning tree loops, nonaggressive UDLD with the default interval of 15 seconds is fast enough to shut down a unidirectional link before a blocking port transitions to the forwarding state (with default spanning tree parameters).

When you enable the UDLD aggressive mode, the following occurs:

• One side of a link has a port stuck (both transmission and receive)

• One side of a link remains up while the other side of the link is down

In these cases, the UDLD aggressive mode disables one of the ports on the link, which prevents traffic from being discarded.

Note You enable the UDLD aggressive mode globally to enable that mode on all the fiber ports. You must

enable the UDLD aggressive mode on copper ports on specified interfaces.

Tip When a line card upgrade is being performed during an in-service software upgrade (ISSU) and some of

the ports on the line card are members of a Layer 2 port channel and are configured with UDLD aggressive mode. If one of the remote ports is shutdown, UDLD puts the corresponding port on the local device into error disabled state. 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.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-9

Page 34

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Carrier Delay

Note You can configure the carrier delay timer only on VLAN network interfaces. It does not apply for

physical ethernet interfaces , port channels and loopback interfaces. See Chapter 4, “Configuring Layer

3 Interfaces,” for information on configuring VLAN network interfaces.

If a link goes down and comes back up before the carrier delay timer expires, the down state is effectively filtered, and the rest of the software on the device is not aware that a link-down event occurred. A large carrier delay timer results in fewer link-up/link-down events being detected. When you set the carrier delay time to 0, the device detects each link-up/link-down event that occurs.

In most environments, a lower carrier delay time is better than a higher one. The exact value that you choose depends on the nature of the link outages and how long you expect these linkages to last in your network. If your data links are subject to short outages (especially if those outages last less time than it takes for your IP routing to converge), you should set a long carrier delay value to prevent these short outages from causing unnecessary problems in your routing tables. However, if your outages tend to be longer, then you may want to set a shorter carrier delay time so that the outages are detected sooner, and the IP route convergence begins and ends sooner.

The default carrier-delay time is 2 seconds or 50 milliseconds.

Port-Channel Parameters

A port channel is an aggregation of physical interfaces that comprise a logical interface. You can bundle up to eight individual interfaces into a port channel to provide increased bandwidth and redundancy. Port channeling also load balances traffic across these physical interfaces. The port channel stays operational if at least one physical interface within the port channel is operational.

You can create a Layer 2 port channel by bundling compatible Layer 2 interfaces, or you can create Layer 3 port channels by bundling compatible Layer 3 interfaces. You cannot combine Layer 2 and Layer 3 interfaces in the same port channel.

Any configuration changes that you apply to the port channel are applied to each interface member of that port channel.

For information on port channels and for information on configuring port channels, see Chapter 6,

“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:

• Ethernet

• VLAN network interface

• Loopback

• Port channel

• Tunnel

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-10

OL-23435-03

Page 35

Chapter 2 Configuring Basic Interface Parameters

Information About the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Note When you choose Ethernet or port channel as the interface type, the port profile is in the default mode

which is Layer 3. Enter the switchport command to change the port profile to Layer 2 mode.

You inherit the port profile when you attach the port profile to an interface or range of interfaces, When you attach, or inherit, a port profile to an interface or range of interfaces, the system applies all the commands in that port profile to the interfaces. Additionally, you can have one port profile inherit the settings from another port profile. Inheriting another port profile allows the initial port profile to assume all of the commands of the second, inherited, port profile that do not conflict with the initial port profile. Four levels of inheritance are supported. The same port profile can be inherited by any number of port profiles.

The system applies the commands inherited by the interface or range of interfaces according to the following guidelines:

• Commands that you enter under the interface mode take precedence over the port profile’s

commands if there is a conflict. However, the port profile retains that command in the port profile.

• The port profile’s commands take precedence over the default commands on the interface, unless the

port-profile command is explicitly overridden by the default command.

• When a range of interfaces inherits a second port profile, the commands of the initial port profile

override the commands of the second port profile if there is a conflict.

• After you inherit a port profile onto an interface or range of interfaces, you can override individual

configuration values by enter the new value at the interface configuration level. If you remove the individual configuration values at the interface configuration level, the interface uses the values in the port profile again.

• There are no default configurations associated with a port profile.

A subset of commands are available under the port-profile configuration mode, depending on which interface type you specify.

Note You cannot use port profiles with Session Manager. See the Cisco Nexus 7000 Series NX-OS System

Management Configuration Guide, Release 5.x, for information about Session Manager.

To apply the port-profile configurations to the interfaces, you must enable the specific port profile. You can configure and inherit a port profile onto a range of interfaces prior to enabling the port profile; you would then enable that port profile for the configurations to take effect on the specified interfaces.

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.

When you remove a port profile from a range of interfaces, the system undoes the configuration from the interfaces first and then removes the port-profile link itself. Also, when you remove a port profile, the system checks the interface configuration and either skips the port-profile commands that have been overridden by directly entered interface commands or returns the command to the default value.

If you want to delete a port profile that has been inherited by other port profiles, you must remove the inheritance before you can delete the port profile.

You can also choose a subset of interfaces from which to remove a port profile from among that group of interfaces that you originally applied the profile. For example, if you configured a port profile and configured ten interfaces to inherit that port profile, you can remove the port profile from just some of the specified ten interfaces. The port profile will continue to operate on the remaining interfaces to which it is applied.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-11

Page 36

Chapter 2 Configuring Basic Interface Parameters

Licensing Requirements

Send document comments to nexus7k-docfeedback@cisco.com

If you delete a specific configuration for a specified range of interfaces using the interface configuration mode, that configuration is also deleted from the port profile for that range of interfaces only. For example, if you have a channel group inside a port profile and you are in the interface configuration mode and you delete that port channel, the specified port channel is also deleted from the port profile as well.

Just as in the device, you can enter a configuration for an object in port profiles without that object being applied to interfaces yet. For example, you can configure a virtual routing and forward instance (VRF) without it being applied to the system. If you then delete that VRF and attendant configurations from the port profile, the system is unaffected.

After you inherit a port profile on an interface or range of interfaces and you delete a specific configuration value, that port-profile configuration will not be operative on the specified interfaces.

If you attempt to apply a port profile to the wrong type of interface, the system returns an error.

When you attempt to enable, inherit, or modify a port profile, the system creates a checkpoint. If the port-profile configuration fails, the system rolls back to the prior configuration and returns an error. A port profile is never only partially applied.

Time Domain Reflectometry Cable Diagnostics

Beginning with Cisco NX-OS Release 5.0(2) for the Cisco Nexus 7000 Series devices and the introduction of the latest generation of line cards, you can perform cable diagnostics without the use of expensive third party equipment. With the cable diagnostic capabilities embedded directly in the line cards, you no longer need to unplug cables and connect cable testers to diagnose a link fault. Each port on the line card can independently detect cabling issues and report them to the switch software using a new technology called Time Domain Reflectometry (TDR).

TDR is a technique used to analyze a conductor by transmitting a pulsed waveform signal into it then examining the polarity, amplitude, and round trip time of the reflected waveform.

By estimating the speed of propagation of the signal in the cable and by measuring the time it takes for its reflection to travel back to the source, it is possible to measure the distance to the reflecting point. Also, by comparing the polarity and amplitude of the original pulse with its reflection it is possible to distinguish between different types of faults, for example, open or shorted pairs.

Being able to remotely diagnose a cable failure, you can now identify the root cause of a problem more quickly and more effectively, providing your users with a prompt response to connectivity issues.

Licensing Requirements

The following table shows the licensing requirements for this feature:

Product License Requirement

Cisco NX-OS 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.

Note Using VDCs requires an Advanced Services license.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-12

OL-23435-03

Page 37

Chapter 2 Configuring Basic Interface Parameters

Guidelines and Limitations

Send document comments to nexus7k-docfeedback@cisco.com

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.

• A port can be either a Layer 2 or a Layer 3 interface; it cannot be both simultaneously.

By default, each port is a Layer 3 interface.

You can change a Layer 3 interface into a Layer 2 interface by using the switchport command. You can change a Layer 2 interface into a Layer 3 interface by using the no switchport command.

• When configuring flow control for a local port, consider the following:

–

To receive pause frames when you do not know how the remote port send parameter is configured, set the local port receive parameter to desired.

–

To receive pause frames when you know that the remote port send parameter is enabled or desired, set the local port receive parameter to enabled.

–

To ignore received pause frames, set the local port receive parameter to disabled.

–

To send pause frames when you do not know how the remote port receive parameter is configured, set the local port send parameter to desired.

–

To send pause frames when you know that the remote port receive parameter is enabled or desired, set the local port send parameter to enabled.

–

To prevent the sending of pause frames, set the local port send parameter to disabled.

• You usually configure Ethernet port speed and duplex mode parameters to auto to allow the system

to negotiate the speed and duplex mode between ports. If you decide to configure the port speed and duplex modes manually for these ports, consider the following:

–

Before you configure the speed and duplex mode for an Ethernet or management interface, see

Table 2-2 on page 2-4 for the combinations of speeds and duplex modes that can be configured

at the same time.

–

If you set the Ethernet port speed to auto, the device automatically sets the duplex mode to auto.

–

If you enter the no speed command, the device automatically sets both the speed and duplex parameters to auto (the no speed command produces the same results as the speed auto command).

–

If you configure an Ethernet port speed to a value other than auto (for example, 10, 100, or 1000 Mb/s), you must configure the connecting port to match. Do not configure the connecting port to negotiate the speed.

Note The device cannot automatically negotiate the Ethernet port speed and duplex mode if the

connecting port is configured to a value other than auto.

Caution Changing the Ethernet port speed and duplex mode configuration might shut down and reenable the

interface.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-13

Page 38

Chapter 2 Configuring Basic Interface Parameters

Default Settings

Send document comments to nexus7k-docfeedback@cisco.com

Default Settings

Tabl e 2-5 lists the default settings for the basic interface parameters.

Table 2-5 Default Basic Interface Parameter Settings

Parameters Default

Description Blank

Beacon Disabled

Debounce timer 100 milliseconds

Bandwidth Data rate of interface

Throughput delay 100 microseconds

Administrative status Shutdown

MTU 1500 bytes

UDLD global Globally disabled

UDLD per-port enable state for fiber-optic media Enabled on all Ethernet fiber-optic LAN ports

UDLD per-port enable state for copper media Disabled on all Ethernet 10/100 and

1000BASE-TX LAN ports

UDLD message interval Disabled

UDLD aggressive mode Disabled

Carrier delay 2 seconds or 50 milliseconds

Error disable Disabled

Error disable recovery Disabled

Error disable recovery interval 300 seconds

Link debounce Enabled

Port profile Disabled

Configuring the Basic Interface Parameters

When you configure an interface, you must specify the interface before you can configure its parameters.

The following sections explain how to specify the interface and configure each of its basic parameters:

• Specifying the Interfaces to Configure, page 2-15

• Configuring the Description, page 2-16

• Configuring the Beacon Mode, page 2-17

• Changing the Bandwidth-Rate Mode, page 2-19

• Configuring the Error-Disabled State, page 2-22

• 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

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

• Configuring the MTU Size, page 2-31

• Configuring the Bandwidth, page 2-34

• Configuring the Throughput Delay, page 2-36

• Shutting Down and Activating the Interface, page 2-37

• Configuring the UDLD Mode, page 2-39

• Configuring the Carrier Delay Timer, page 2-41

• Configuring Port Profiles, page 2-43

• Performing TDR Cable Diagnostics, page 2-51

• Configuring Rate Limits for Packets that Reach the Supervisor, page 2-52

Specifying the Interfaces to Configure

Before you can configure the parameters for one or more interfaces of the same type, you must specify the type and the identities of the interfaces.

Tabl e 2-6 shows the interface types and identities that you should use for specifying the Ethernet and

management interfaces.

Table 2-6 Information Needed to Identify an Interface for Configurations

Interface Type Identity

Ethernet I/O module slot numbers and port numbers on the module

Management 0 (for port 0)

The interface range configuration mode allows you to configure multiple interfaces with the same configuration parameters. After you enter the interface range configuration mode, all command parameters you enter are attributed to all interfaces within that range until you exit out of the interface range configuration mode.

You enter a range of interfaces using dashes (-) and commas (,). Dashes separate contiguous interfaces and commas separate noncontiguous interfaces. When you enter noncontiguous interfaces, you must enter the media type for each interface.

The following example shows how to configure a contiguous interface range:

switch(config)# interface ethernet 2/29-30 switch(config-if-range)#

The following example shows how to configure a noncontiguous interface range:

switch(config)# interface ethernet 2/29, ethernet 2/33, ethernet 2/35 switch(config-if-range)#

You can specify subinterfaces in a range only when the subinterfaces are on the same port, for example, 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

1. configure terminal

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-15

Page 40

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

2. interface interface

DETAILED STEPS

Command Purpose

Step 1

Step 2

configure terminal

Example: switch# configure terminal switch(config)#

interface interface

Example 1:

switch(config)# interface ethernet 2/1 switch(config-if)#

Example 2:

switch(config)# interface mgmt0 switch(config-if)#

Enters the global configuration mode.

Specifies the interface that you are configuring. You can specify the interface type and identity. For an Ethernet port, use “ethernet slot/port.” For the management interface, use “mgmt0.”

Example 1 shows how to specify the slot 2, port 1 Ethernet interface.

Example 2 shows how to specify the management interface.

Note You do not need to add a space between the interface type and identity (port or slot/port number)

For example, for the Ethernet slot 4, port 5 interface, you can specify either “ethernet 4/5” or “ethernet4/5.” The management interface is either “mgmt0” or “mgmt 0.”

When you are in the interface configuration mode, the commands that you enter configure the interface that you specified for this mode.

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

1. configure terminal

2. interface interface

3. description text

4. show interface interface

5. exit

6. copy running-config startup-config

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-16

OL-23435-03

Page 41

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

interface interface

Example:

switch(config)# interface ethernet 2/1 switch(config-if)#

switch(config)# interface mgmt0 switch(config-if)#

description text

Example:

switch(config-if)# description Ethernet port 3 on module 1. switch(config-if)#

show interface interface

Example:

switch(config)# show interface ethernet 2/1

exit

Enters the global configuration mode.

Specifies the interface that you are configuring. You can specify the interface type and identity. For an Ethernet port, use “ethernet slot/port.” For the management interface, use “mgmt0.”

Example 1 shows how to specify the slot 2 port, 1 Ethernet interface.

Example 2 shows how to specify the management interface.

Specifies the description for the interface. The description is a maximum of 80 characters.

Displays the interface status, which includes the description parameter.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 6

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to set the interface description to Ethernet port 24 on module 3:

switch# configure terminal switch(config)# interface ethernet 3/24 switch(config-if)# description server1 switch(config-if)#

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

1. configure terminal

2. interface ethernet slot/port

(Optional) Copies the running configuration to the startup configuration.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-17

Page 42

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

3. {beacon | no beacon}

4. show interface ethernet slot/port

5. exit

6. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

{beacon | no beacon}

Example:

switch(config-if)# beacon switch(config-if)#

show interface ethernet slot/port

Example:

switch(config)# show interface ethernet 2/1

exit

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Enables the beacon mode or disables the beacon mode. The default mode is disabled.

Displays the interface status, which includes the beacon mode state.

Exits the interface mode.

Step 6

Example:

switch(config-if)# exit switch(config)#

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

(Optional) Copies the running configuration to the startup configuration.

This example shows how to enable the beacon mode for the Ethernet port 3/1:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# beacon switch(config-if)#

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

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Changing the Bandwidth-Rate Mode

You can specify whether each 10 Gb of bandwidth on a 32-port 10-Gigabit Ethernet module is dedicated to one port or shared by four ports in the same port group.

This section includes the following topics:

• Creating a Port Profile, page 2-43

• Sharing the Bandwidth Among a Port Group, page 2-20

Dedicating Bandwidth to One Port

When you dedicate the bandwidth to one port, you must first administratively shut down the four ports in the group, change the rate mode to dedicated, and then bring the dedicated port administratively up.

SUMMARY STEPS

1. configure terminal

2. interface ethernet slot/port, ethernet slot/port, ethernet slot/port, ethernet slot/port

3. shutdown

4. interface ethernet slot/port

DETAILED STEPS

Step 1

Step 2

Step 3

5. rate-mode dedicated

6. no shutdown

7. show interface ethernet slot/port capabilities

8. exit

9. copy running-config startup-config

Command Purpose

configure terminal

Example:

switch# configure terminal switch(config)#

interface ethernet slot/port, ethernet slot/port, ethernet slot/port, ethernet slot/port

Example:

switch(config)# interface ethernet 3/1, ethernet 3/3, ethernet 3/5, ethernet 3/7 switch(config-if)#

shutdown

Enters configuration mode.

Specifies an Ethernet interface to configure, and enters interface configuration mode.

The example shows how to specify one port for the dedicated mode.

Administratively shuts down the ports.

Example:

switch(config)# shutdown

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-19

Page 44

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Command Purpose

Step 4

Step 5

Step 6

Step 7

Step 8

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config)#

rate-mode dedicated

Example:

switch(config-if)# rate-mode dedicated switch(config-if)#

no shutdown

Example:

switch(config-if)# no shutdown

show interface ethernet slot/port capabilities

Example:

switch(config)# show interface ethernet 3/1

exit

Specifies the first Ethernet interface in a group of interfaces.

Dedicates the full bandwidth of 10 Gb to one port. When you dedicate the bandwidth, all subsequent commands for the port are for dedicated mode.

Brings the port administratively up.

Displays the interface information including the current rate mode.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 9

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to configure the dedicated mode for Ethernet port 4/17 in the group that includes ports 4/17, 4/19, 4/21, and 4/23:

switch# configure terminal switch(config)# interface ethernet 4/17, ethernet 4/19, ethernet 4/21, ethernet 4/23 switch(config-if)# shutdown switch(config-if)# interface ethernet 4/17 switch(config-if)# rate-mode dedicated switch(config-if)# no shutdown switch(config-if)#

Sharing the Bandwidth Among a Port Group

You can share 10 Gb of bandwidth among a group of ports (four ports) on a 32-port 10-Gigabit Ethernet module. To share the bandwidth, you must bring the dedicated port administratively down, specify the ports that are to share the bandwidth, change the rate mode to shared, and then bring the ports administratively up.

(Optional) Copies the running configuration to the startup configuration.

BEFORE YOU BEGIN

All ports in the same group must belong to the same VDC.

SUMMARY STEPS

1. configure terminal

2. interface ethernet slot/port

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-20

OL-23435-03

Page 45

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

3. shutdown

4. interface ethernet slot/port, ethernet slot/port, ethernet slot/port, ethernet slot/port

5. rate-mode shared

6. no shutdown

7. show interface ethernet slot/port

8. exit

9. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

configure terminal

Example:

switch# configure terminal switch(config)#

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config)#

shutdown

Enters configuration mode.

Specifies the first Ethernet interface in a group of interfaces.

Brings the port administratively down.

Step 4

Step 5

Step 6

Step 7

Example:

switch(config-if)# shutdown

interface ethernet slot/port, ethernet slot/port, ethernet slot/port, ethernet slot/port

Example:

switch(config)# interface ethernet 3/1, ethernet 3/3, ethernet 3/5, ethernet 3/7 switch(config-if)#

rate-mode shared

Example:

switch(config-if)# rate-mode shared switch(config-if)#

no shutdown

Example:

switch(config-if)# no shutdown

show interface ethernet slot/port

Example:

switch(config)# show interface ethernet 3/1

Specifies four Ethernet interfaces to configure (they must be part of the same port group), and enters interface configuration mode.

The example shows how to specify one port for the dedicated mode.

Sets the shared rate mode for the specified ports.

The example shows how to configure the shared mode.

Brings the ports administratively up.

Displays the interface information including the current rate mode.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-21

Page 46

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Command Purpose

Step 8

Step 9

exit

Example:

switch(config-if)# exit switch(config)#

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Exits the interface mode.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to configure the shared mode for Ethernet port 4/17 in the group that includes ports 4/17, 4/19, 4/21, and 4/23:

switch# configure terminal switch(config)# interface ethernet 4/17 switch(config-if)# shutdown switch(config)# interface ethernet 4/17, ethernet 4/19, ethernet 4/21, ethernet 4/23 switch(config-if)# rate-mode shared switch(config-if)# no shutdown switch(config-if)#

Configuring the Error-Disabled State

You can view the reason an interface moves to the error-disabled state and configure automatic recovery.

This section includes the following topics:

• Enabling the Error Disable Detection, page 2-22

• Enabling the Error-Disabled Recovery, page 2-23

• Configuring the Error-Disabled Recovery Interval, page 2-24

Enabling the Error Disable Detection

You can enable error-disable detection in an application. As a result, when a cause is detected on an interface, the interface is placed in an error-disabled state, which is an operational state that is similar to the link-down state.

SUMMARY STEPS

1. configure terminal

2. errdisable detect cause {acl-exception | all | link-flap | loopback}

3. shutdown

4. no shutdown

5. show interface status err-disabled

6. copy running-config startup-config

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-22

OL-23435-03

Page 47

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

configure terminal

Example:

switch# configure terminal switch(config)#

errdisable detect cause {acl-exception | all | link-flap | loopback}

Example:

switch(config)# errdisable detect cause all switch(config)#

shutdown

Example:

switch(config)# shutdown switch(config)#

no shutdown

Example:

switch(config)# no shutdown switch(config)#

show interface status err-disabled

Example:

switch(config)# show interface status err-disabled

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Enters configuration mode.

Specifies a condition under which to place the interface in an error-disabled state. The default is enabled.

Brings the interface down administratively. To manually recover the interface from the error-disabled state, enter this command first.

Brings the interface up administratively and enables the interface to recover manually from the error-disabled state.

Displays information about error-disabled interfaces.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to enable the error-disabled detection in all cases:

switch(config)# errdisable detect cause all switch(config)#

Enabling the Error-Disabled Recovery

You can specify the application to bring the interface out of the error-disabled state and retry coming up. It retries after 300 seconds, unless you configure the recovery timer (see the errdisable recovery interval command).

SUMMARY STEPS

1. configure terminal

2. errdisable recovery cause {all | bpdguard | link-flap | psecure-violation | security-violation |

storm-control | udld}

3. show interface status err-disabled

4. copy running-config startup-config

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-23

Page 48

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

configure terminal

Example:

switch# configure terminal switch(config)#

errdisable recovery cause {all | bpduguard | link-flap | psecure-violation | security-violation | storm-control | udld}

Example:

switch(config)# errdisable recovery cause all switch(config-if)#

show interface status err-disabled

Example:

switch(config)# show interface status err-disabled

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Enters configuration mode.

Specifies a condition under which the interface automatically recovers from the error-disabled state, and the device retries bringing the interface up. The device waits 300 seconds to retry. The default is disabled.

Displays information about error-disabled interfaces.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to enable error-disabled recovery under all conditions:

switch(config)# errdisable recovery cause all switch(config)#

Configuring the Error-Disabled Recovery Interval

You can configure the error-disabled recovery timer value.

SUMMARY STEPS

1. configure terminal

2. errdisable recovery interval interval

3. show interface status err-disabled

4. copy running-config startup-config

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-24

OL-23435-03

Page 49

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

configure terminal

Example:

switch# configure terminal switch(config)#

errdisable recovery interval interval

Example:

switch(config)# errdisable recovery interval 32 switch(config-if)#

show interface status err-disabled

Example:

switch(config)# show interface status err-disabled

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Enters configuration mode.

Specifies the interval for the interface to recover from the error-disabled state. The range is from 30 to 65535 seconds, and the default is 300 seconds.

Displays information about error-disabled interfaces.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to configure the error-disabled recovery timer to set the interval for recovery to 32 seconds:

switch(config)# errdisable recovery interval 32 switch(config)#

Configuring the MDIX Parameter

If you need to detect the type of connection (crossover or straight) with another copper Ethernet port, enable the medium dependent independent crossover (MDIX) parameter for the local port. By default, this parameter is enabled.

BEFORE YOU BEGIN

You must enable MDIX for the remote port.

SUMMARY STEPS

1. configure terminal

2. interface ethernet slot/port

3. {mdix auto} | {no mdix}

4. show interface ethernet slot/port

5. exit

6. copy running-config startup-config

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-25

Page 50

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

{mdix auto | no mdix}

Example:

switch(config-if)# mdix auto switch(config-if)#

show interface ethernet slot/port

Example:

switch(config)# show interface ethernet 3/1 switch(config-if)#

exit

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Specifies whether to enable or disable MDIX detection for the port.

Displays the interface status, which includes the MDIX status.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 6

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to enable MDIX for Ethernet port 3/1:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# mdix auto switch(config-if)#

This example shows how to disable MDIX for Ethernet port 3/1:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# no mdix switch(config-if)#

Configuring the Debounce Timer

You can enable the debounce timer for Ethernet ports by specifying a debounce time, in milliseconds (ms), or disable the timer by specifying a debounce time of 0.

(Optional) Copies the running configuration to the startup configuration.

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

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

SUMMARY STEPS

1. configure terminal

2. interface ethernet slot/port

3. link debounce time milliseconds

4. show interface debounce

5. exit

6. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

link debounce time milliseconds

Example:

switch(config-if)# link debounce time 1000 switch(config-if)#

show interface debounce

Example:

switch(config)# show interface debounce switch(config-if)#

exit

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Enables the debounce timer for the amount of time (0 to 5000 ms) specified.

Disables the debounce timer if you specify 0 milliseconds.

Shows the link debounce time for all of the Ethernet interfaces.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 6

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to enable the debounce timer and set the debounce time to 1000 ms for the Ethernet port 3/1:

switch# configure terminal switch(config)# interface ethernet 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

OL-23435-03

(Optional) Copies the running configuration to the startup configuration.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-27

Page 52

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

switch(config-if)# link debounce time 0 switch(config-if)#

Configuring the Interface Speed and Duplex Mode

The interface speed and duplex mode are interrelated, so you should configure both of their parameters at the same time.

To see which speeds and duplex modes you can configure together for Ethernet and management interfaces, see Table 2-2 on page 2-4.

Note The interface speed that you specify can affect the duplex mode used for an interface, so you should set

the speed before setting the duplex mode. If you set the speed for autonegotiation, the duplex mode is automatically set to be autonegotiated. If you specify 10- or 100-Mb/s speed, the port is automatically configured to use half-duplex mode, but you can specify full-duplex mode instead. If you specify a speed of 1000 Mb/s (1 Gb/s) or faster, full duplex is automatically used.

BEFORE YOU BEGIN

SUMMARY STEPS

Make sure that the remote port has a speed setting that supports your changes for the local port. If you want to set the local port to use a specific speed, you must set the remote port for the same speed or set the local port to autonegotiate the speed.

1. configure terminal

2. interface interface

3. speed {{10 | 100 | 1000 | {auto [10 100 [1000]]}} | {10000 | auto}}

4. duplex {full | half | auto}

5. show interface interface

6. exit

7. copy running-config startup-config

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-28

OL-23435-03

Page 53

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

configure terminal

Example:

switch# configure terminal switch(config)#

interface interface

Example 1:

switch(config)# interface ethernet 2/1 switch(config-if)#

Example 2:

switch(config)# interface mgmt0 switch(config-if)#

speed {{10 | 100 | 1000 | {auto [10 100 [1000]]}} | {10000 | auto}}

Example:

switch(config-if)# speed 1000 switch(config-if)#

Enters the global configuration mode.

Specifies the interface that you are configuring. You can specify the interface type and identity. For an Ethernet port, use “ethernet slot/port.” For the management interface, use “mgmt0.”

Example 1 shows how to specify the slot 2 port 1 Ethernet interface.

Example 2 shows how to specify the management interface.

For Ethernet ports on the 48-port 10/100/1000 modules, sets the speed at 10 Mb/s, 100 Mb/s, or 1000 Mb/s, or sets the port to autonegotiate its speed with the other 10/100/1000 port on the same link.

For Ethernet ports on the 32-port 10-Gigabit Ethernet modules, sets the speed at 10,000 Mb/s (10 Gb/s) or sets the port to autonegotiate its speed with the other 10-Gigabit Ethernet port on the link.

Step 4

Step 5

Step 6

Step 7

For management interfaces, sets the speed as 1000 Mb/s or sets the port to autonegotiate its speed.

duplex {full | half | auto}

Example:

switch(config-if)# duplex full

show interface interface

Example:

switch(config)# show interface mgmt0

exit

Example:

switch(config-if)# exit switch(config)#

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Specifies the duplex mode as full, half, or autonegotiate.

Displays the interface status, which includes the speed and duplex mode parameters.

Exits the interface mode.

(Optional) Copies the running configuration to the startup configuration.

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:

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-29

Page 54

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# speed 1000 switch(config-if)# duplex full switch(config-if)#

Configuring the Flow Control

For Ethernet ports that run at 1 Gb/s or faster, you can enable or disable the port’s ability to send and receive flow-control pause frames. For Ethernet ports that run slower than 1 Gb/s, you can enable or disable only the port’s ability to receive pause frames.

When enabling flow control for the local port, you either fully enable the local port to send or receive frames regardless of the flow-control setting of the remote port, or you set the local port to use the desired setting used by the remote port. If you enable both the local and remote port for flow control, or set the desired flow control of the other port, or set a combination of those two states, flow control is enabled for those ports.

Note For ports that run at 10 Gb/s, you cannot use the desired state for the send or receive parameter.

BEFORE YOU BEGIN

SUMMARY STEPS

Make sure that the remote port has the corresponding setting for the flow control that you need. If you want the local port to send flow-control pause frames, make sure that the remote port has a receive parameter set to on or desired. If you want the local port to receive flow-control frames, make sure that the remote port has a send parameter set to on or desired. If you do not want to use flow control, you can set the remote port’s send and receive parameters to off.

1. configure terminal

2. interface ethernet slot/port

3. flowcontrol {send | receive} {desired | on | off}

4. show interface ethernet slot/port

5. show interface flowcontrol

6. exit

7. copy running-config startup-config

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-30

OL-23435-03

Page 55

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

configure terminal

Example:

switch# config terminal switch(config)#

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

flowcontrol {send | receive} {desired | on | off}

Example:

switch(config-if)# flowcontrol send on switch(config)-if#

show interface ethernet slot/port

Example:

switch(config)# show interface ethernet 3/1 switch(config)

show interface flowcontrol

Example:

switch(config)# show interface flowcontrol switch(config)

exit

Enters configuration mode.

Specifies an Ethernet interface to configure by its slot number and port number, and enters the interface configuration mode.

Specifies the flow-control setting for ports. You can set the send setting for only the ports running at 1000 Mb/s or faster. You can set the receive setting for ports running at any speed.

Displays the interface status, which include the flow control parameters.

Displays the flow control status for all Ethernet ports.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 7

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to set Ethernet port 3/1 to send flow control pause frames:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# flowcontrol send on switch(config-if)#

Configuring the MTU Size

You can configure the maximum transmission unit (MTU) size for Layer 2 and Layer 3 Ethernet interfaces. For Layer 3 interfaces, you can configure the MTU to be between 576 and 9216 bytes (even values are required). 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).

(Optional) Copies the running configuration to the startup configuration.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-31

Page 56

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Note You can change the system jumbo MTU size, but if you change that value, you should also update the

Layer 2 interfaces that use that value so that they use the new system jumbo MTU value. If you do not update the 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.

You can change the port mode by using the switchport command.

After changing the port mode to Layer 2, you can return to configuring Layer 3 interfaces by changing the port mode again, by using the no switchport command.

This section includes the following topics:

• Configuring the Interface MTU Size, page 2-32

• Configuring the System Jumbo MTU Size, page 2-33

Configuring the Interface MTU Size

SUMMARY STEPS

DETAILED STEPS

Step 1

For Layer 3 interfaces, you can configure an MTU size that is between 576 and 9216 bytes.

For Layer 2 interfaces, you can configure all Layer 2 interfaces to use either the default MTU size (1500 bytes) or the system jumbo MTU size (default size of 9216 bytes).

If you need to use a different system jumbo MTU size for Layer 2 interfaces, see the “Configuring the

System Jumbo MTU Size” section on page 2-33.

1. configure terminal

2. interface ethernet slot/port

3. {switchport | no switchport}

4. mtu size

5. show interface ethernet slot/port

6. exit

7. copy running-config startup-config

Command Purpose

configure terminal

Enters configuration mode.

Example:

switch# configure terminal switch(config)#

Step 2

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

2-32

Specifies an Ethernet interface to configure, and enters interface configuration mode.

OL-23435-03

Page 57

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Command Purpose

Step 3

Step 4

Step 5

Step 6

Step 7

{switchport | no switchport}

Example:

switch(config-if)# no switchport switch(config-if)#

mtu size

Example:

switch(config-if)# mtu 9216 switch(config-if)#

show interface ethernet slot/port

Example:

switch(config)# show interface ethernet 2/1

exit

Example:

switch(config-if)# exit switch(config)#

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Specifies to use Layer 2 or Layer 3.

For a Layer 2 interface, specifies either the default MTU size (1500) or the system jumbo MTU size (9216 unless you have changed the system jumbo MTU size).

For a Layer 3 interface, specifies any even number between 576 and 9216.

Displays the interface status, which includes the MTU size.

Exits the interface mode.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to configure the Layer 2 Ethernet port 3/1 with the default MTU size (1500):

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# switchport switch(config-if)# mtu 1500 switch(config-if)#

Configuring the System Jumbo MTU Size

You can configure the system jumbo MTU size, which can be used to specify the MTU size for Layer 2 interfaces. 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

1. configure terminal

2. system jumbomtu size

3. show running-config all

4. interface type slot/port

5. mtu size

6. exit

7. copy running-config startup-config

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-33

Page 58

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

configure terminal

Example:

switch# configure terminal switch(config)#

system jumbomtu size

Example:

switch(config)# system jumbomtu 8000 switch(config)#

show running-config all

Example:

switch(config)# show running-config all | include jumbomtu

interface type slot/port

Example:

switch(config)# interface ethernet 2/1 switch(config-if)#

mtu size

Example:

switch(config-if)# mtu 1500 switch(config-if)#

exit

Enters configuration mode.

Specifies the system jumbo MTU size. Use an even number between 1500 and 9216.

Displays the current operating configuration, which includes the system jumbo MTU size.

Specifies an interface to configure and enters the interface configuration mode.

For a Layer 2 interface, specifies either the default MTU size (1500) or the system jumbo MTU size that you specified earlier.

For a Layer 3 interface, specifies any even size between 576 and 9216.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 7

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to configure the system jumbo MTU as 8000 bytes and how to change the MTU specification for an interface that was configured with the previous jumbo MTU size:

switch# configure terminal switch(config)# system jumbomtu 8000 switch(config)# show running-config switch(config)# interface ethernet 2/2 switch(config-if)# switchport switch(config-if)# mtu 4608 switch(config-if)#

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.

(Optional) Copies the running configuration to the startup configuration.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-34

OL-23435-03

Page 59

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

SUMMARY STEPS

1. configure terminal

2. interface ethernet slot/port

3. bandwidth kbps

4. show interface ethernet slot/port

5. exit

6. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

bandwidth kbps

Example:

switch(config-if)# bandwidth 1000000 switch(config-if)#

show interface ethernet slot/port

Example:

switch(config)# show interface ethernet 2/1

exit

Enters configuration mode.

Specifies an Ethernet interface to configure, and enters interface configuration mode.

Specifies the bandwidth as an informational-only value between 1 and 10,000,000.

Displays the interface status, which includes the bandwidth value.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 6

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

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)#

OL-23435-03

(Optional) Copies the running configuration to the startup configuration.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-35

Page 60

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Configuring the Throughput Delay

You can configure the interface throughput delay for Ethernet interfaces. The actual delay time does not change, but you can set an informational value between 1 and 16777215, where the value represents the number of tens of microseconds.

SUMMARY STEPS

1. configure terminal

2. interface ethernet slot/port

3. delay value

4. show interface ethernet slot/port

5. exit

6. copy running-config startup-config

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Command Purpose

configure terminal

Example:

switch# configure terminal switch(config)#

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

delay value

Example:

switch(config-if)# delay 10000 switch(config-if)#

show interface ethernet slot/port

Example:

switch(config)# show interface ethernet 3/1 switch(config-if)#

exit

Example:

switch(config-if)# exit switch(config)#

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Specifies the delay time in tens of microseconds. You can set an informational value range between 1 and 16777215 tens of microseconds.

Displays the interface status, which includes the throughput-delay time.

Exits the interface mode.

(Optional) Copies the running configuration to the startup configuration.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-36

OL-23435-03

Page 61

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

This example shows how to configure the throughput-delay time so that one interface is preferred over another. A lower delay value is preferred over a higher value. In this example, Ethernet 7/48 is preferred over 7/47. The default delay for 7/48 is less than the configured value on 7/47, which is set for the highest value (16777215):

switch# configure terminal switch(config)# interface ethernet 7/47 switch(config-if)# delay 16777215 switch(config-if)# ip address 192.168.10.1/24 switch(config-if)# ip router eigrp 10 switch(config-if)# no shutdown switch(config-if)# exit switch(config)# interface ethernet 7/48 switch(config-if)# ip address 192.168.11.1/24 switch(config-if)# ip router eigrp 10 switch(config-if)# no shutdown switch(config-if)#

Note You must first ensure the EIGRP feature is enabled by running the feature eigrp command.

Shutting Down and Activating the Interface

You can shut down and restart Ethernet or management interfaces. When you shut down interfaces, they become disabled and all monitoring displays show them as being down. This information is communicated to other network servers through all dynamic routing protocols. When the interfaces are shut down, the interface is not included in any routing updates. To activate the interface, you must restart the device.

SUMMARY STEPS

1. configure terminal

2. interface interface

3. shutdown

4. show interface interface

5. no shutdown

6. show interface interface

7. exit

8. copy running-config startup-config

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-37

Page 62

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

configure terminal

Example:

switch# configure terminal switch(config)#

interface interface

Example:

switch(config)# interface ethernet 2/1 switch(config-if)#

switch(config)# interface mgmt0 switch(config-if)#

shutdown

Enters the global configuration mode.

Specifies the interface that you are configuring. You can specify the interface type and identity. For an Ethernet port, use “ethernet slot/port.” For the management interface, use “mgmt0.”

Example 1 shows how to specify the slot 2, port 1 Ethernet interface.

Example 2 shows how to specify the management interface.

Disables the interface.

Step 4

Step 5

Step 6

Step 7

Step 8

Example:

switch(config-if)# shutdown switch(config-if)#

show interface interface

Example:

switch(config-if)# show interface ethernet 2/1 switch(config-if)#

no shutdown

Example:

switch(config-if)# no shutdown switch(config-if)#

show interface interface

Example:

switch(config-if)# show interface ethernet 2/1 switch(config-if)#

exit

Example:

switch(config-if)# exit switch(config)#

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Displays the interface status, which includes the administrative status.

Reenables the interface.

Displays the interface status, which includes the administrative status.

Exits the interface mode.

(Optional) Copies the running configuration to the startup configuration.

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

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Configuring the UDLD Mode

You can configure normal or aggressive unidirectional link detection (UDLD) modes for Ethernet interfaces on devices configured to run UDLD. Before you can enable a UDLD mode for an interface, you must make sure that UDLD is already enabled on the device that includes the interface. UDLD must also be enabled on the other linked interface and its device.

Tabl e 2-7 lists CLI details to enable and disable UDLD on different interfaces.

Table 2-7 CLI Details to Enable or Disable UDLD on Different Interfaces

Description Fiber port Copper or Non-fiber port

Default setting Enabled Disabled

Enable UDLD command no udld disable udld enable

Disable UDLD command udld disable no udld enable

To use the normal UDLD mode, you must configure one of the ports for normal mode and configure the other port for the normal or aggressive mode. To use the aggressive UDLD mode, you must configure both ports for the aggressive mode.

By default, UDLD is disabled for the 48-port, 10/100/1000 Ethernet module ports but the normal UDLD mode is enabled for the 32-port, 10-Gigabit Ethernet module ports.

BEFORE YOU BEGIN

SUMMARY STEPS

You must enable UDLD for the other linked port and its device.

1. configure terminal

2. feature udld

no feature udld

3. udld message-time seconds

4. udld aggressive

5. interface ethernet slot/port

6. udld {enable | disable}

7. show udld [ethernet slot/port | global | neighbors}

8. exit

9. copy running-config startup-config

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-39

Page 64

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

configure terminal

Example:

switch# configure terminal switch(config)#

feature udld

Example:

switch(config)# feature udld switch(config)#

no feature udld

Example:

switch(config)# no feature udld switch(config)#

udld message-time seconds

Example:

switch(config)# udld message-time 30 switch(config)#

udld aggressive

Example:

switch(config)# udld aggressive switch(config)#

interface ethernet slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

udld {enable | disable}

Example:

switch(config-if)# udld enable switch(config-if)#

show udld [ethernet slot/port | global | neighbors]

Enters configuration mode.

Enables UDLD for the device.

Disables UDLD for the device.

(Optional) Specifies the interval between sending UDLD messages. The range is 7 to 90 seconds, and the default is 15 seconds.

(Optional) Specifies UDLD mode to be aggressive.

Note For copper interfaces, you

enter the interface command mode for those interfaces you want to configure for UDLD aggressive mode and issue this command in interface command model.

(Optional) Specifies an interface to configure, and enters interface configuration mode.

(Optional) Enables UDLD on the specified copper port or disables UDLD on the specified fiber port.

To enable UDLD on copper ports. the command is udld enable. To enable UDLD on fiber ports, the command is no udld disable.

See Table 2 -7 for more details.

(Optional) Displays the UDLD status.

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

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Command Purpose

Step 8

Step 9

exit

Example:

switch(config-if-range)# exit switch(config)#

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Exits the interface mode.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to enable the UDLD for the device:

switch# configure terminal switch(config)# feature udld switch(config)#

This example shows how to set the UDLD message interval to 30 seconds:

switch# configure terminal switch(config)# feature udld switch(config)# udld message-time 30 switch(config)#

This example shows how to enable the aggressive UDLD mode for fiber interfaces:

switch# configure terminal switch(config)# feature udld switch(config)# udld aggressive switch(config)#

This example shows how to enable the aggressive UDLD mode for the copper interface Ethernet 3/1:

switch# configure terminal switch(config)# feature udld switch(config)# udld aggressive switch(config)# interface ethernet 3/1 switch(config-if-range)# udld enable switch(config-if-range)#

This example shows how to disable UDLD for Ethernet port 3/1:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if-range)# no udld enable switch(config-if-range)# exit

This example shows how to disable UDLD for the device:

switch# configure terminal switch(config)# no feature udld switch(config)# exit

Configuring the Carrier Delay Timer

The carrier delay timer sets a time during which all link-down/link-up events are not detected by any of the other software on the device. 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.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-41

Page 66

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Note You can configure the carrier delay timer only on VLAN network interfaces; you cannot configure this

timer in any other interface modes.

BEFORE YOU BEGIN

Ensure that you are in VLAN interface mode. You cannot configure the carrier delay timer in any other interface mode.

SUMMARY STEPS

1. configure terminal

2. interface vlan vlan-id

3. carrier-delay {sec | msec number}

4. show interface vlan vlan-id

5. exit

6. copy running-config startup-config

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

Step 5

Command Purpose

configure terminal

Example:

switch# configure terminal switch(config)#

interface vlan-id

Example:

switch(config)# interface vlan 5 switch(config-if)#

carrier-delay {sec | msec number}

Example:

switch(config-if)# carrier-delay 20 switch(config-if)#

show interface vlan-id

Example:

switch(config-if)# show interface vlan 5 switch(config-if)#

exit

Enters configuration mode.

Enters the VLAN interface mode.

Sets the carrier delay timer. You can set the time between 0 to 60 seconds or 0 to 1000 milliseconds. The default is 2 seconds or 50 milliseconds.

Displays the interface status.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 6

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

2-42

(Optional) Copies the running configuration to the startup configuration.

OL-23435-03

Page 67

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

This example shows how to set the carrier delay timer to 20 seconds for VLAN 5:

switch# configure terminal switch(config)# interface vlan 5 switch(config-if)# carrier-delay 20 switch(config-if)#

Configuring Port Profiles

You can apply several configuration parameters to a range of interfaces simultaneously. All the interfaces in the range must be the same type. You can also inherit the configurations from one port profile into another port profile. The system supports four levels of inheritance.

This section includes the following topics:

• Creating a Port Profile, page 2-43

• Entering Port-Profile Configuration Mode and Modifying a Port Profile, page 2-44

• Assigning a Port Profile to a Range of Interfaces, page 2-45

• Enabling a Specific Port Profile, page 2-46

• Inheriting a Port Profile, page 2-47

• Removing a Port Profile from a Range of Interfaces, page 2-48

• Removing an Inherited Port Profile, page 2-50

Creating a Port Profile

You can create a port profile on the device. Each port profile must have a unique name across types and the network.

SUMMARY STEPS

1. configure terminal

2. port-profile [type {ethernet | interface-vlan | loopback | port channel | tunnel}] name

3. exit

4. show port-profile

5. copy running-config startup-config

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-43

Page 68

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

port-profile [type {ethernet | interface-vlan | loopback | port channel | tunnel}] name

Example:

switch(config)# port-profile type tunnel test switch(config-ppm)#

exit

Example:

switch(config-ppm)# exit switch(config)#

show port-profile

Example:

switch(config)# show port-profile

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Enters configuration mode.

Creates and names a port profile for the specified type of interface and enters the port-profile configuration mode.

Exits the port-profile configuration mode.

(Optional) Displays the port-profile configuration.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to create a port profile named test for tunnel interfaces:

switch# configure terminal switch(config)# port-profile type tunnel test switch(config-ppm)#

Entering Port-Profile Configuration Mode and Modifying a Port Profile

You can enter the port-profile configuration mode and modify a port profile. To modify the port profile, you must be in the port-profile configuration mode.

SUMMARY STEPS

1. configure terminal

2. port-profile [type {ethernet | interface-vlan | loopback | port channel | tunnel}] name

3. exit

4. show port-profile

5. copy running-config startup-config

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-44

OL-23435-03

Page 69

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

port-profile [type {ethernet | interface-vlan | loopback | port channel | tunnel}] name

Example:

switch(config)# port-profile type tunnel test switch(config-ppm)# no shutdown switch(config-ppm)#

exit

Example:

switch(config-ppm)# exit switch(config)#

show port-profile

Example:

switch(config)# show port-profile

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Enters configuration mode.

Enters the port-profile configuration mode for the specified port profile and allows you to add or remove configurations to the profile.

Exits the port-profile configuration mode.

(Optional) Displays the port-profile configuration.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to enter the port-profile configuration mode for the specified port profile and bring all the interfaces administratively up:

switch# configure terminal switch(config)# port-profile type tunnel test switch(config-ppm)# no shutdown switch(config-ppm)#

Assigning a Port Profile to a Range of Interfaces

You can assign a port profile to an interface or to a range of interfaces. All the interfaces must be the same type.

SUMMARY STEPS

1. configure terminal

2. interface [ethernet slot/port | interface-vlan vlan-id | loopback number | port-channel number |

tunnel number]

3. inherit port-profile name

4. exit

5. show port-profile

6. copy running-config startup-config

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-45

Page 70

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

configure terminal

Example:

switch# configure terminal switch(config)#

interface [ethernet slot/port | interface-vlan vlan-id | loopback number | port channel number |

tunnel number]

Example:

switch(config)# interface ethernet 7/3-5, 10/2, 11/20-25 switch(config-if)#

inherit port-profile name

Example:

switch(config-if)# inherit port-profile adam switch(config-if)#

exit

Enters configuration mode.

Selects the range of interfaces.

Assigns the specified port profile to the selected interfaces.

Exits the port-profile configuration mode.

Example:

switch(config-ppm)# exit switch(config)#

Step 5

Step 6

show port-profile

Example:

switch(config)# show port-profile

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to assign the port profile named adam to 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)# inherit port-profile adam switch(config-if)#

Enabling a Specific Port Profile

To apply the port-profile configurations to the interfaces, you must enable the specific port profile. You can configure and inherit a port profile onto a range of interfaces before you enable that port profile. You would then enable that port profile for the configurations to take effect on the specified interfaces.

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.

(Optional) Displays the port-profile configuration.

(Optional) Copies the running configuration to the startup configuration.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-46

OL-23435-03

Page 71

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

SUMMARY STEPS

1. configure terminal

2. port-profile [type {ethernet | interface-vlan | loopback | port channel | tunnel}] name

3. state enabled

4. exit

5. show port-profile

6. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

configure terminal

Example:

switch# configure terminal switch(config)#

port-profile [type {ethernet | interface-vlan | loopback | port channel | tunnel}] name

Example:

switch(config)# port-profile type tunnel test switch(config-ppm)# no shutdown switch(config-ppm)#

state enabled

Enters configuration mode.

Enters the port-profile configuration mode for the specified port profile.

Enables that port profile.

Example:

switch(config-ppm)# state enabled switch(config)#

Step 4

Step 5

Step 6

exit

Example:

switch(config-ppm)# exit switch(config)#

show port-profile

Example:

switch(config)# show port-profile

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to enter the port-profile configuration mode and enable the port profile:

switch# configure terminal switch(config)# port-profile type tunnel test switch(config-ppm)# state enabled switch(config-ppm)#

Inheriting a Port Profile

Exits the port-profile configuration mode.

(Optional) Displays the port-profile configuration.

(Optional) Copies the running configuration to the startup configuration.

You can inherit a port profile onto an existing port profile. The system supports four levels of inheritance.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-47

Page 72

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

SUMMARY STEPS

1. configure terminal

2. port-profile name

3. inherit port-profile name

4. exit

5. show port-profile

6. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

configure terminal

Example:

switch# configure terminal switch(config)#

port-profile name

Example:

switch(config)# port-profile test switch(config-ppm)#

inherit port-profile name

Example:

switch(config-ppm)# inherit port-profile adam switch(config-ppm)#

exit

Enters configuration mode.

Enters the port-profile configuration mode for the specified port profile.

Inherits another port profile onto the existing one. The original port profile assumes all the configurations of the inherited port profile.

Exits the port-profile configuration mode.

Example:

switch(config-ppm)# exit switch(config)#

Step 5

Step 6

show port-profile

Example:

switch(config)# show port-profile

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to inherit the port profile named adam onto the port profile named test:

switch# configure terminal switch(config)# port-profile test switch(config-ppm)# inherit port-profile adam switch(config-ppm)#

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.

(Optional) Displays the port-profile configuration.

(Optional) Copies the running configuration to the startup configuration.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-48

OL-23435-03

Page 73

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

SUMMARY STEPS

1. configure terminal

2. interface [ethernet slot/port | interface-vlan vlan-id | loopback number | port-channel number |

tunnel number]

3. no inherit port-profile name

4. exit

5. show port-profile

6. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

configure terminal

Example:

switch# configure terminal switch(config)#

interface [ethernet slot/port | interface-vlan vlan-id | loopback number | port channel number | tunnel number]

Enters configuration mode.

Selects the range of interfaces.

Step 3

Step 4

Step 5

Step 6

Example:

switch(config)# interface ethernet 7/3-5, 10/2, 11/20-25 switch(config-if)#

no inherit port-profile name

Example:

switch(config-if)# no inherit port-profile adam switch(config-if)#

exit

Example:

switch(config-ppm)# exit switch(config)#

show port-profile

Example:

switch(config)# show port-profile

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Removes the specified port profile from the selected interfaces.

Exits the port-profile configuration mode.

(Optional) Displays the port-profile configuration.

(Optional) Copies the running configuration to the startup configuration.

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)#

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-49

Page 74

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Removing an Inherited Port Profile

You can remove an inherited port profile. You do this in the port-profile mode.

SUMMARY STEPS

1. configure terminal

2. port-profile name

3. no inherit port-profile name

4. exit

5. show port-profile

6. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

configure terminal

Enters configuration mode.

Step 2

Step 3

Step 4

Step 5

Step 6

Example:

switch# configure terminal switch(config)#

port-profile name

Example:

switch(config)# port-profile test switch(config-ppm)#

no inherit port-profile name

Example:

switch(config-ppm)# no inherit port-profile adam switch(config-ppm)#

exit

Example:

switch(config-ppm)# exit switch(config)#

show port-profile

Example:

switch(config)# show port-profile

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Enters the port-profile configuration mode for the specified port profile.

Removes an inherited port profile from this port profile.

Exits the port-profile configuration mode.

(Optional) Displays the port-profile configuration.

(Optional) Copies the running configuration to the startup configuration.

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

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Performing TDR Cable Diagnostics

You can perform cable diagnostics without the use of expensive third party equipment. Each port on the line card can independently detect cabling issues and report them to the switch software using TDR diagnostics.

BEFORE YOU BEGIN

The TDR test guidelines are as follows:

• TDR can test cables up to a maximum length of 115 meters.

• Do not start the test at the same time on both ends of the cable. Starting the test at both ends of the

cable at the same time can lead to false test results.

• Do not change the port configuration during any cable diagnostics test. This action may result in

incorrect test results.

• The all ports in the associated port group must be shut down before running the TDR test.

SUMMARY STEPS

DETAILED STEPS

Step 1

Step 2

1. test cable-diagnostics tdr interface number

2. show interface number cable-diagnostics-tdr

Command Purpose

test cable-diagnostics tdr interface number Example: switch# test cable-diagnostics tdr interface ethernet 7/1

show interface number cable-diagnostics-tdr Example: switch(config)# show interface ethernet 7/1 cable-diagnostics-tdr

Starts the TDR test on the specified interface. You must have previously run the shutdown command on the interface.

Shows the TDR test results for the specified interface.

This example shows how to perform a TDR test on a specific interface. In this example, ethernet 3/1 has a missing cable, and ethernet 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

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-51

Page 76

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

-------------------------------------------------------------------------------Interface Speed Pair Cable Length Distance to fault Channel Pair Status

-------------- ----- ---- -------------- ------------------- ------- ----------Eth3/1 auto --- N/A 1 +/- 2 m Pair A Open

--- N/A 1 +/- 2 m Pair B Open

--- N/A 1 +/- 2 m Pair C Open

--- N/A 1 +/- 2 m Pair D Open

n7000# show interface ethernet 3/12 cable-diagnostics-tdr

--------------------------------------------------------------------------------

Interface Speed Pair Cable Length Distance to fault Channel Pair Status

-------------- ----- ---- -------------- ------------------- ------- -----------

Eth3/12 1000 --- N/A N/A Pair A Terminated

--- N/A N/A Pair B Terminated

--- N/A N/A Pair C Terminated

--- N/A N/A Pair D Terminated

Configuring Rate Limits for Packets that Reach the Supervisor

Note Beginning with Cisco NX-OS Release 5.1, you can configure rate limits globally on the device for

packets that reach the supervisor module. For more information, see the Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 5.x.

You can configure rate limits for packets that reach the supervisor module on a particular interface.

SUMMARY STEPS

1. configure terminal

2. [no] rate-limit cpu direction {input | output | both} pps packets action log

3. (Optional) exit

4. (Optional) show system internal pktmgr interface ethernet slot/port

5. (Optional) copy running-config startup-config

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-52

OL-23435-03

Page 77

Chapter 2 Configuring Basic Interface Parameters

Configuring the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

[no] rate-limit cpu direction {input|output|both} pps packets action

log

Example:

switch(config)# interface ethernet 1/1 switch(config-if)# rate-limit cpu direction both pps 1000 action log

exit

Example:

switch(config-if)# exit switch(config)#

show system internal pktmgr interface ethernet slot/port

Example:

switch# show system internal pktmgr interface ethernet 4/1

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Enters configuration mode.

Configures the rate limits for packets that reach the supervisor module on a particular interface. If the rate of incoming or outgoing packets exceeds the configured rate limit, the device logs a system message but does not drop any packets. The range is from 1 to

100000. The default rate is 10000.

(Optional) Exits the interface mode.

(Optional) Displays the inbound and outbound rate limit configuration for packets that reach the supervisor module on a specific interface.

(Optional) Copies the running configuration to the startup configuration.

OL-23435-03

Note If the rate of incoming or outgoing packets exceeds the configured rate limit, the device logs a system

message, the device logs a system message but does not drop any packets.

This example shows how to configure the rate limits for packets that reach the supervisor module on a specific interface:

switch# rate-limit cpu direction both pps 1000 action log switch# show system internal pktmgr interface ethernet 4/9 Ethernet4/9, ordinal: 44 SUP-traffic statistics: (sent/received) Packets: 528 / 0 Bytes: 121968 / 0 Instant packet rate: 0 pps / 0 pps 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

Page 78

Chapter 2 Configuring Basic Interface Parameters

Verifying the Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Verifying the Basic Interface Parameters

You can verify the basic interface parameters by displaying their values. You can also clear the counters listed when you display the parameter values.

Note The system displays only those ports that are allocated to the VDC that you are working in.

DETAILED STEPS

To display basic interface configuration information, perform one of the following tasks:

Command Purpose

show cdp Displays the CDP status.

show interface interface Displays the configured states of one or all

interfaces.

show interface interface Displays the configured states of one or all

interfaces.

show interface brief Displays a table of interface states.

show interface switchport Displays the status of Layer 2 ports.

show interface status err-disabled Displays information about error-disabled

interfaces.

show vdc Displays the status of the existing VDCs.

show udld interface Displays the UDLD status for the current

interface or all interfaces.

show udld-global Displays the UDLD status for the current device.

show port-profile Displays information about the port profiles.

show system internal pktmgr internal ethernet

slot/port

Displays the inbound and outbound rate limit configuration for packets that reach the supervisor module on a specific interface.

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. This section discusses the following topics:

• Displaying Interface Statistics, page 2-54

• Clearing Interface Counters, page 2-56

Displaying Interface Statistics

You can set up to three sampling intervals for statistics collections on interfaces.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-54

OL-23435-03

Page 79

Chapter 2 Configuring Basic Interface Parameters

Monitoring the Interface Counters

Send document comments to nexus7k-docfeedback@cisco.com

SUMMARY STEPS

1. configure terminal

2. load-interval counters {{1 | 2| 3} seconds}

3. show interface interface

4. exit

5. copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

configure terminal

Example:

switch# configure terminal switch#

load-interval counters {{1 | 2 | 3} seconds}

Example:

switch(config)# load-interval counters 1 100 switch(config)#

show interface interface

Enters the configuration mode.

Sets up to three sampling intervals to collect bit-rate and packet-rate statistics. The default values for each counter is as follows:

1—30 seconds; 60 seconds for VLAN network interface

2—300 seconds

3—not configured

Displays the interface status, which includes the counters.

Step 4

Step 5

Example:

switch(config)# show interface vlan 10 switch#

exit

Example:

switch(config)# exit switch#

copy running-config startup-config

Example:

switch# copy running-config startup-config

Exits the configuration mode.

(Optional) Copies the running configuration to the startup configuration.

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)#

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-55

Page 80

Chapter 2 Configuring Basic Interface Parameters

Additional References

Send document comments to nexus7k-docfeedback@cisco.com

Clearing Interface Counters

You can clear the Ethernet and management interface counters using the clear counters command. You can perform this task from the configuration mode or interface configuration mode.

SUMMARY STEPS

1. clear counters interface

2. show interface

DETAILED STEPS

Command Purpose

Step 1

Step 2

clear counters interface

Example:

switch# clear counters ethernet 2/1 switch#

show interface interface

Clears the interface counters.

Displays the interface status, which includes the counters.

Example:

switch# show interface vlan 10 switch#

This example shows how to clear and reset the counters on Ethernet port 5/5:

switch# clear counters ethernet 5/5 switch#

Additional References

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

Chapter 2 Configuring Basic Interface Parameters

Feature History for Configuring Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Related Topic Document Title

Command reference Cisco Nexus 7000 Series NX-OS Interfaces Command Reference,

Release 5.x

Layer 2 switching Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration

Guide, Release 5.x

CDP Cisco Nexus 7000 Series NX-OS System Management Command

Reference, 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.

—

Feature History for Configuring Basic Interface Parameters

Tabl e 2-8 lists the release history for this feature.

Table 2-8 Feature History for Configuring Basic Interface Parameters

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.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-57

Page 82

Chapter 2 Configuring Basic Interface Parameters

Feature History for Configuring Basic Interface Parameters

Send document comments to nexus7k-docfeedback@cisco.com

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

2-58

OL-23435-03

Page 83

Send document comments to nexus7k-docfeedback@cisco.com

CHAPTER

Configuring Layer 2 Interfaces

Note Beginning with Cisco Release 5.2, the Cisco Nexus 7000 Series devices support FabricPath Layer 2

interfaces. See the Cisco Nexus 7000 Series NX-OS FabricPath Command Reference, Release 5.x for complete information about the FabricPath feature and interfaces.

This chapter describes how to configure Layer 2 switching ports as access or trunk ports on Cisco NX-OS devices.

Note Beginning with Cisco NX-OS Release 5.1, a Layer 2 port can function as either one of the following:

• A trunk port

• An access port

• A private VLAN port (see the Cisco DCNM Layer 2 Switching Configuration Guide, Release 5.x,

for more information on private VLANs)

• A FabricPath port (see the Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide,

Release 5.x, and the Cisco DCNM FabricPath Configuration Guide, Release 5.x, for information on

FabricPath)

Beginning with Cisco NX-OS Release 5.2(1), a Layer 2 port can also function as a shared interface. You cannot configure an access interface as a shared interface. See the Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 for information on shared interfaces.

Note See the Cisco DCNM FabricPath Configuration Guide, Release 5.x, for more information on configuring

the FabricPath feature.

Note A Layer 2 port can function as either a trunk port, an access port, or a private VLAN port.

This chapter includes the following sections:

• Information About Access and Trunk Interfaces, page 3-2

• Licensing Requirements for Layer 2 Port Modes, page 3-8

• Prerequisites for Layer 2 Interfaces, page 3-8

• Guidelines and Limitations, page 3-8

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-1

Page 84

Chapter 3 Configuring Layer 2 Interfaces

Information About Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

• Default Settings, page 3-9

• Configuring Access and Trunk Interfaces, page 3-9

• Verifying the Interface Configuration, page 3-22

• Monitoring the Layer 2 Interfaces, page 3-23

• Example Configurations for Access and Trunk Ports, page 3-23

• Additional References, page 3-24

• Feature History for Configuring Layer 2 Interfaces, page 3-25

Note See the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 5.x, for

information on configuring a SPAN destination interface.

You can configure Layer 2 switching ports as access or trunk ports. Trunks carry the traffic of multiple VLANs over a single link and allow you to extend VLANs across an entire network. All Layer 2 switching ports maintain media access control (MAC) address tables.

Note See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for

information on VLANs, MAC address tables, private VLANs, and the Spanning Tree Protocol.

Note A Layer 2 port can function as either a trunk port, an access port, or a private VLAN port. See the Cisco

Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more information on

private VLANs.

Information About Access and Trunk Interfaces

Note See the Cisco Nexus 7000 Series NX-OS High Availability and Redundancy Guide, Release 5.x, for

complete information on high-availability features.

This section includes the following topics:

• Information About Access and Trunk Interfaces, page 3-3

• IEEE 802.1Q Encapsulation, page 3-4

• Access VLANs, page 3-5

• Native VLAN IDs for Trunk Ports, page 3-6

• Tagging Native VLAN Traffic, page 3-6

• Allowed VLANs, page 3-6

• High Availability, page 3-7

• Virtualization Support, page 3-7

• Default Interfaces, page 3-7

• SVI Autostate Exclude, page 3-7

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-2

OL-23435-03

Page 85

Chapter 3 Configuring Layer 2 Interfaces

VLAN 1 VLAN 2 VLAN 3

Access Access Trunk Trunk

Ethemet 1/1 Ethemet 1/2 Ethemet 2/1 Ethemet 2/2

186703

Information About Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Note The device supports only IEEE 802.1Q-type VLAN trunk encapsulation.

Information About Access and Trunk Interfaces

A Layer 2 port can be configured as an access or a trunk port as follows:

• An access port can have only one VLAN configured on that port; it can carry traffic for only one

VLAN.

• A trunk port can have two or more VLANs configured on that port; it can carry traffic for several

VLANs simultaneously.

By default, all ports on the device are Layer 3 ports.

You can make all ports Layer 2 ports using the setup script or by entering the system default switchport command. See the Cisco Nexus 7000 Series NX-OS Fundamentals Configuration Guide, Release 5.x, for information on using the setup script. 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.

All ports in the same trunk must be in the same VDC, and trunk ports cannot carry VLANs from different VDCs.

Figure 3-1 shows how you can use trunk ports in the network. The trunk port carries traffic for two or

more VLANs.

Figure 3-1 Trunk and Access Ports and VLAN Traffic

Note See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for

information on VLANs.

In order to correctly deliver the traffic on a trunk port with several VLANs, the device uses the IEEE

802.1Q encapsulation, or tagging, method (see the “IEEE 802.1Q Encapsulation” section on page 3-4 for more information).

Note See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for

information on subinterfaces on Layer 3 interfaces.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-3

Page 86

Chapter 3 Configuring Layer 2 Interfaces

Information About Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

To optimize the performance on access ports, you can configure the port as a host port. Once the port is configured as a host port, it is automatically set as an access port, and channel grouping is disabled. Use the host designation to decrease the time that it takes the designated port to begin to forward packets.

Only an end station can be set as a host port; you will receive an error message if you attempt to configure other ports as hosts.

If an access port receives a packet with an 802.1Q tag in the header other than the access VLAN value, that port drops the packet without learning its MAC source address.

A Layer 2 interface can function as either an access port or a trunk port; it cannot function as both port types simultaneously.

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

Note For information about VLANs, see the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration

Guide, Release 5.x.

A trunk is a point-to-point link between the switch and another networking device. Trunks carry the traffic of multiple VLANs over a single link and allow you to extend VLANs across an entire network.

To correctly deliver the traffic on a trunk port with several VLANs, the device uses the IEEE 802.1Q encapsulation, or tagging, method that uses a tag that is inserted into the frame header (see Figure 3-2). This tag carries information about the specific VLAN to which the frame and packet belong. This

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-4

OL-23435-03

Page 87

Chapter 3 Configuring Layer 2 Interfaces

Preamble

(7 -bytes)

Start

Frame

Delimiter

(1 -byte)

Dest.

MAC

Address

(6 -

bytes)

Source

MAC

Address

(6 -

bytes)

Length

/ Type

(2 -

bytes)

MAC Client Data

(0 -n bytes)

Pad

(0 -p

bytes)

Frame

Check

Sequence

(4 -bytes)

Preamble (7-bytes)

Start

Frame

Delimiter

(1-byte)

Dest.

MAC

Address

(6-bytes) (6-bytes)

Source

MAC

Address

Length/Type

= 802.1Q

Tag Type

(2-byte)

Tag

Control

Information

(2-bytes)

Length

/Type

(2-

bytes)

MAC Client

Data

(0-n bytes)

Pad (0-p

bytes)

Frame Check

Sequence

(4-bytes)

3 bits = User Priority field

1 bit = Canonical Format Identifier (CFI)

12 bits – VLAN Identifier (VLAN ID)

Information About Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

method allows packets that are encapsulated for several different VLANs to traverse the same port and maintain traffic separation between the VLANs. Also, the encapsulated VLAN tag allows the trunk to move traffic end-to-end through the network on the same VLAN.

Figure 3-2 Header Without and With 802.1Q Tag

Access VLANs

Note If you assign an access VLAN that is also a primary VLAN for a private VLAN, all access ports with

Note See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for

that access VLAN will also receive all the broadcast traffic for the primary VLAN in the private VLAN mode.

complete information on private VLANs.

When you configure a port in access mode, you can specify which VLAN will carry the traffic for that interface. If you do not configure the VLAN for a port in access mode, or an access port, the interface carries traffic for the default VLAN (VLAN1).

You can change the access port membership in a VLAN by specifying the new VLAN. You must create the VLAN before you can assign it as an access VLAN for an access port. If you change the access VLAN on an access port to a VLAN that is not yet created, the system shuts that access port down.

If an access port receives a packet with an 802.1Q tag in the header other than the access VLAN value, that port drops the packet without learning its MAC source address.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-5

Page 88

Chapter 3 Configuring Layer 2 Interfaces

Information About Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Native VLAN IDs for Trunk Ports

A trunk port can carry nontagged packets simultaneously with the 802.1Q tagged packets. When you assign a default port VLAN ID to the trunk port, all untagged traffic travels on the default port VLAN ID for the trunk port, and all untagged traffic is assumed to belong to this VLAN. This VLAN is referred to as the native VLAN ID for a trunk port. That is, the native VLAN ID is the VLAN that carries untagged traffic on trunk ports.

Note Native VLAN ID numbers must match on both ends of the trunk.

The trunk port sends an egressing packet with a VLAN that is equal to the default port VLAN ID as untagged; all the other egressing packets are tagged by the trunk port. If you do not configure a native VLAN ID, the trunk port uses the default VLAN.

Note You cannot use an FCoE VLAN as a native VLAN for an Ethernet trunk switchport.

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). Untagged packets can pass through trunk ports and access ports.

However, all packets that enter the device with an 802.1Q tag that matches the value of the native VLAN on the trunk are stripped of any tagging and egress the trunk port as untagged packets. This situation can cause problems because you may want to retain the tagging on packets on the native VLAN for the trunk port.

You can configure the device to drop all untagged packets on the trunk ports and to retain the tagging of packets entering the device with 802.1Q values that are equal to that of the native VLAN ID. All control traffic still passes on the native VLAN. This configuration is global; trunk ports on the device either do or do not retain the tagging for the native VLAN.

Allowed VLANs

By default, a trunk port sends traffic to and receives traffic from all VLANs. All VLAN IDs are allowed on each trunk. However, you can remove VLANs from this inclusive list to prevent traffic from the specified VLANs from passing over the trunk. Later, you can add any specific VLANs that you may want the trunk to carry traffic for back to the list.

To partition the Spanning Tree Protocol (STP) topology for the default VLAN, you can remove VLAN1 from the list of allowed VLANs. Otherwise, VLAN1, which is enabled on all ports by default, will have a very big STP topology, which can result in problems during STP convergence. When you remove VLAN1, all data traffic for VLAN1 on this port is blocked, but the control traffic continues to move on the port.

Note See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more

information about STP.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-6

OL-23435-03

Page 89

Chapter 3 Configuring Layer 2 Interfaces

Information About Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Note Beginning with Cisco Release 5.2, you can change the block of VLANs reserved for internal use. See

the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more information about changing the reserved VLANs.

High Availability

The software supports high availability for Layer 2 ports.

Note See the Cisco Nexus 7000 Series NX-OS High Availability and Redundancy Guide, Release 5.x, for

complete information on high availability features.

Virtualization Support

The device supports virtual device contexts (VDCs).

All ports in the same trunk must be in the same VDC, and trunk ports cannot carry VLANs from different VDCs.

Note See the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 5.x, for

complete information on VDCs and assigning resources.

Default Interfaces

You can use the default interface feature to clear the configured parameters for both physical and logical interfaces such as the Ethernet, loopback, VLAN network, tunnel, and the port-channel interface.

Note A maximum of 8 ports can be selected for the default interface. The default interfaces feature is not

supported for management interfaces because the device could go to an unreachable state.

SVI Autostate Exclude

Ordinarily, when a VLAN interface has multiple ports in the VLAN, the SVI will go to the down state when all the ports in the VLAN go down. You can use the SVI Autostate Exclude feature to exclude specific ports and port channels while defining the status of the SVI (up or down) even if it belongs to the same VLAN. For example, even if the excluded port or port channel is in the up state and other ports are in the down state in the VLAN, the SVI state is changed to down.

Note You can use the SVI Autostate Exclude feature only for switched physical Ethernet ports and port

channels.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-7

Page 90

Chapter 3 Configuring Layer 2 Interfaces

Licensing Requirements for Layer 2 Port Modes

Send document comments to nexus7k-docfeedback@cisco.com

Licensing Requirements for Layer 2 Port Modes

The following table shows the licensing requirements for this feature:

Product License Requirement

Cisco NX-OS 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.

Note Using VDCs requires an Advanced Services license.

Prerequisites for Layer 2 Interfaces

Layer 2 interfaces have the following prerequisites:

• You are logged onto the device.

• You must configure the port as a Layer 2 port before you can use the switchport mode command.

By default, all ports on the device are Layer 3 ports.

Guidelines and Limitations

VLAN trunking has the following configuration guidelines and limitations:

• A port can be either a Layer 2 or a Layer 3 interface; it cannot be both simultaneously.

• When you change a Layer 3 port to a Layer 2 port or a Layer 2 port to a Layer 3 port, all

layer-dependent configuration is lost. When you change an access or trunk port to a Layer 3 port, all information about the access VLAN, native VLAN, allowed VLANs, and so forth, is lost.

• Do not connect devices with access links because access links may partition a VLAN.

• When connecting Cisco devices through an 802.1Q trunk, make sure that the native VLAN for an

802.1Q trunk is the same on both ends of the trunk link. If the native VLAN on one end of the trunk is different from the native VLAN on the other end, spanning tree loops might result.

• Disabling spanning tree on the native VLAN of an 802.1Q trunk without disabling spanning tree on

every VLAN in the network can cause spanning tree loops. You must leave spanning tree enabled on the native VLAN of an 802.1Q trunk. If you cannot leave spanning tree enabled, you must disable spanning tree on every VLAN in the network. Make sure that your network has no physical loops before you disable spanning tree.

• When you connect two Cisco devices through 802.1Q trunks, the devices exchange spanning tree

bridge protocol data units (BPDUs) on each VLAN allowed on the trunks. The BPDUs on the native VLAN of the trunk are sent untagged to the reserved IEEE 802.1D spanning tree multicast MAC address (01-80-C2-00-00-00). The BPDUs on all other VLANs on the trunk are sent tagged to the reserved Cisco Shared Spanning Tree (SSTP) multicast MAC address (01-00-0c-cc-cc-cd).

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-8

OL-23435-03

Page 91

Chapter 3 Configuring Layer 2 Interfaces

Default Settings

Send document comments to nexus7k-docfeedback@cisco.com

• Non-Cisco 802.1Q devices maintain only a single instance of spanning tree (the Mono Spanning

Tree) that defines the spanning tree topology for all VLANs. When you connect a Cisco switch to a non-Cisco switch through an 802.1Q trunk, the Mono Spanning Tree of the non-Cisco switch and the native VLAN spanning tree of the Cisco switch combine to form a single spanning tree topology known as the Common Spanning Tree (CST).

• Because Cisco devices transmit BPDUs to the SSTP multicast MAC address on VLANs other than

the native VLAN of the trunk, non-Cisco devices do not recognize these frames as BPDUs and flood them on all ports in the corresponding VLAN. Other Cisco devices connected to the non-Cisco

802.1Q cloud receive these flooded BPDUs. This BPDU reception allows Cisco switches to maintain a per-VLAN spanning tree topology across a cloud of non-Cisco 802.1Q devices. The non-Cisco 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

devices to the non-Cisco 802.1Q cloud.

• If you are connecting multiple Cisco devices to a non-Cisco 802.1Q cloud, all of the connections

must be through 802.1Q trunks. You cannot connect Cisco devices to a non-Cisco 802.1Q cloud through access ports because doing so places the access port on the Cisco device into the spanning tree “port inconsistent” state and no traffic will pass through the port.

• You can group trunk ports into port-channel groups, but all trunks in the group must have the same

configuration. When a group is first created, all ports follow the parameters set for the first port to be added to the group. If you change the configuration of one of these parameters, the device propagates that setting to all ports in the group, such as the allowed VLANs and the trunk status. For example, if one port in a port group ceases to be a trunk, all ports cease to be trunks.

• If you try to enable 802.1X on a trunk port, an error message appears, and 802.1X is not enabled. If

you try to change the mode of an 802.1X-enabled port to trunk, the port mode is not changed.

Default Settings

Tabl e 3-1 lists the default settings for device access and trunk port mode parameters.

Table 3-1 Default Access and Trunk Port Mode Parameters

Parameters Default

Switchport mode Access

Allowed VLANs 1 to 3967, 4048 to 4094

Access VLAN ID VLAN1

Native VLAN ID VLAN1

Native VLAN ID tagging Disabled

Administrative state Shut

Configuring Access and Trunk Interfaces

This section includes the following topics:

• Guidelines for Configuring Access and Trunk Interfaces, page 3-10

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-9

Page 92

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

• Configuring a LAN Interface as a Layer 2 Access Port, page 3-10

• Configuring Access Host Ports, page 3-11

• Configuring Trunk Ports, page 3-13

• Configuring the Native VLAN for 802.1Q Trunking Ports, page 3-14

• Configuring the Allowed VLANs for Trunking Ports, page 3-16

• Configuring a Default Interface, page 3-17

• Configuring SVI Autostate Exclude, page 3-18

• Configuring the Device to Tag Native VLAN Traffic, page 3-20

• 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.

Configuring a LAN Interface as a Layer 2 Access Port

You can configure a Layer 2 port as an access port. An access port transmits packets on only one, untagged VLAN. You specify which VLAN traffic that the interface carries, which becomes the access VLAN. If you do not specify a VLAN for an access port, that interface carries traffic only on the default VLAN. The default VLAN is VLAN1.

The VLAN must exist before you can specify that VLAN as an access VLAN. The system shuts down an access port that is assigned to an access VLAN that does not exist.

BEFORE YOU BEGIN

Ensure that you are configuring a Layer 2 interface.

SUMMARY STEPS

1. configure terminal

2. interface {{type slot/port} | {port-channel number}}

3. switchport mode {access | trunk}

4. switchport access vlan vlan-id

5. exit

6. (Optional) show interface

7. (Optional) copy running-config startup-config

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-10

OL-23435-03

Page 93

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

Step 5

configure terminal

Example:

switch# configure terminal switch(config)#

interface {{type slot/port} | {port-channel number}}

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

switchport mode {access | trunk}

Example:

switch(config-if)# switchport mode access

switchport access vlan vlan-id

Example:

switch(config-if)# switchport access vlan 5

exit

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Sets the interface as a nontrunking nontagged, single-VLAN Layer 2 interface. An access port can carry traffic in one VLAN only. By default, an access port carries traffic for VLAN1; to set the access port to carry traffic for a different VLAN, use the switchport access vlan command.

Specifies the VLAN for which this access port will carry traffic. If you do not enter this command, the access port carries traffic on VLAN1 only; use this command to change the VLAN for which the access port carries traffic.

Exits the configuration mode.

Example:

switch(config-if)# exit switch(config)#

Step 6

Step 7

show interface

Example:

switch# show interface

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

This example shows how to set Ethernet 3/1 as a Layer 2 access port that carries traffic for VLAN 5 only:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# switchport mode access switch(config-if)# switchport access vlan 5 switch(config-if)#

Configuring Access Host Ports

Note You should apply the switchport host command only to interfaces connected to an end station.

(Optional) Displays the interface status and information.

(Optional) Copies the running configuration to the startup configuration.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-11

Page 94

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

You can optimize the performance of access ports that are connected to end stations by simultaneously setting that port as an access port. An access host port handles the STP like an edge port and immediately moves to the forwarding state without passing through the blocking and learning states. Configuring an interface as an access host port also disables port channeling on that interface.

Note See Chapter 6, “Configuring Port Channels,” for information on port-channel interfaces and the Cisco

Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x. For complete

information on the Spanning Tree Protocol.

BEFORE YOU BEGIN

Ensure that you are configuring the correct interface to an interface that is an end station.

SUMMARY STEPS

1. configure terminal

2. interface type slot/port

3. switchport host

4. exit

DETAILED STEPS

Step 1

Step 2

Step 3

Step 4

5. (Optional) show interface

6. (Optional) copy running-config startup-config

Command Purpose

configure terminal

Example:

switch# configure terminal switch(config)#

interface type slot/port

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

switchport host

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Sets the interface to be an access host port, which immediately moves to the spanning tree forwarding

Example:

switch(config-if)# switchport host

exit

Example:

switch(config-if)# exit switch(config)#

state and disables port channeling on this interface.

Note Apply this command only to end stations.

Exits the interface mode.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-12

OL-23435-03

Page 95

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Command Purpose

Step 5

Step 6

show interface

Example:

switch# show interface

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

(Optional) Displays the interface status and information.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to set Ethernet 3/1 as a Layer 2 access port with PortFast enabled and port channel disabled:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# switchport host switch(config-if)#

Configuring Trunk Ports

Note The device supports 802.1Q encapsulation only.

BEFORE YOU BEGIN

SUMMARY STEPS

You can configure a Layer 2 port as a trunk port. A trunk port transmits untagged packets for one VLAN plus encapsulated, tagged, packets for multiple VLANs. (See the “IEEE 802.1Q Encapsulation” section

on page 3-4 for information about encapsulation.)

Before you configure a trunk port, ensure that you are configuring a Layer 2 interface.

1. configure terminal

2. interface {type slot/port | port-channel number}

3. switchport mode {access | trunk}

4. exit

5. (Optional) show interface

6. (Optional) copy running-config startup-config

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-13

Page 96

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

configure terminal

Example:

switch# configure terminal switch(config)#

interface {type slot/port | port-channel number}

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

switchport mode {access | trunk}

Example:

switch(config-if)# switchport mode trunk

exit

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Sets the interface as a Layer 2 trunk port. A trunk port can carry traffic in one or more VLANs on the same physical link (VLANs are based on the trunk-allowed VLANs list). By default, a trunk interface can carry traffic for all VLANs. To specify that only certain VLANs are allowed on the specified trunk, use the switchport trunk allowed vlan command.

Exits the interface mode.

Example:

switch(config-if)# exit switch(config)#

Step 5

Step 6

show interface

Example:

switch# show interface

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

(Optional) Displays the interface status and information.

(Optional Copies the running configuration to the startup configuration.

This example shows how to set Ethernet 3/1 as a Layer 2 trunk port:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# switchport mode trunk switch(config-if)#

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.

Note You cannot configure an FCoE VLAN as a native VLAN for an Ethernet interface.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-14

OL-23435-03

Page 97

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

SUMMARY STEPS

1. configure terminal

2. interface {type slot/port | port-channel number}

3. switchport trunk native vlan vlan-id

4. exit

5. (Optional) show vlan

6. (Optional) copy running-config startup-config

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

Step 4

configure terminal

Example:

switch# configure terminal switch(config)#

interface {type slot/port | port-channel number}

Example:

switch(config)# interface ethernet 3/1 switch(config-if)#

switchport trunk native vlan vlan-id

Example:

switch(config-if)# switchport trunk native vlan 5

exit

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Sets the native VLAN for the 802.1Q trunk. Valid values are from 1 to 4094, except those VLANs reserved for internal use. The default value is VLAN1.

Exits the interface mode.

OL-23435-03

Step 5

Step 6

Example:

switch(config-if)# exit switch(config)#

show vlan

Example:

switch# show vlan

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

(Optional) Displays the status and information of VLANs.

(Optional) Copies the running configuration to the startup configuration.

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

Page 98

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Configuring the Allowed VLANs for Trunking Ports

You can specify the IDs for the VLANs that are allowed on the specific trunk port.

Note The switchport trunk allowed vlan vlan-list command replaces the current VLAN list on the specified

port with the new list. Consequently you are prompted for confirmation before the new list is applied.

As a side effect, if you are doing copy and paste of a large configuration then you may see some failures as the CLI is waiting for a confirmation before accepting other commands. To avoid this you can disable prompting using the terminal dont-ask command before you paste the configuration.

BEFORE YOU BEGIN

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.

Note Beginning with Cisco Release 5.2, you can change the block of VLANs reserved for internal use. See

the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more information about changing the reserved VLANs.

SUMMARY STEPS

DETAILED STEPS

Step 1

Step 2

1. configure terminal

2. interface {ethernet slot/port | port-channel number}

3. switchport trunk allowed vlan {vlan-list | add vlan-list | all | except vlan-list | none | remove

vlan-list}

4. exit

5. (Optional) show vlan

6. (Optional) copy running-config startup-config

Command Purpose

configure terminal

Example:

switch# configure terminal switch(config)#

interface {ethernet slot/port | port-channel number

Example:

switch(config)# interface ethernet 3/1

}

Enters configuration mode.

Specifies an interface to configure, and enters interface configuration mode.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-16

OL-23435-03

Page 99

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

Command Purpose

Step 3

Step 4

Step 5

Step 6

switchport trunk allowed vlan {vlan-list add vlan-list | all |except vlan-list | none | remove vlan-list}

Example:

switch(config-if)# switchport trunk allowed vlan add 15-20#

exit

Example:

switch(config-if)# exit switch(config)#

show vlan

Example:

switch# show vlan

copy running-config startup-config

Example:

switch(config)# copy running-config startup-config

Sets the allowed VLANs for the trunk interface. The default is to allow all VLANs on the trunk interface: 1 to 3967 and 4048 to 4094. VLANs 3968 to 4047 are the default VLANs reserved for internal use by default. By default, all VLANs are allowed on all trunk interfaces. Beginning with Cisco Release 5.2(1), the default reserved VLANs are 3968 to 4094, and you can change the block of reserved VLANs. See the Cisco Nexus

7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more information.

Note You cannot add internally allocated VLANs as

allowed VLANs on trunk ports. The system returns a message if you attempt to list an internally allocated VLAN as an allowed VLAN.

Exits the interface mode.

(Optional) Displays the status and information for VLANs.

(Optional) Copies the running configuration to the startup configuration.

This example shows how to add VLANs 15 to 20 to the list of allowed VLANs on the Ethernet 3/1, Layer 2 trunk port:

switch# configure terminal switch(config)# interface ethernet 3/1 switch(config-if)# switchport trunk allowed vlan 15-20 switch(config-if)#

Configuring a Default Interface

The default interface feature allows you to clear the existing configuration of multiple interfaces such as Ethernet, loopback, VLAN network, port-channel, and tunnel interfaces. All user configuration under a specified interface will be deleted. You can optionally create a checkpoint before clearing the interface configuration so that you can later restore the deleted configuration.

Note The default interface feature is not supported for management interfaces because the device could go to

an unreachable state.

OL-23435-03

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-17

Page 100

Chapter 3 Configuring Layer 2 Interfaces

Configuring Access and Trunk Interfaces

Send document comments to nexus7k-docfeedback@cisco.com

SUMMARY STEPS

1. configure terminal

2. default interface int-if [checkpoint name]

3. exit

4. (Optional) show interface

DETAILED STEPS

Command Purpose

Step 1

Step 2

Step 3

configure terminal

Example:

switch# configure terminal switch(config)#

default interface int-if [checkpoint name]

Example:

switch(config)# default interface ethernet 3/1 checkpoint test8

exit

Enters configuration mode.

Deletes the configuration of the interface and restores the default configuration. Use the ? keyword to display the supported interfaces.

Use the checkpoint keyword to store a copy of the running configuration of the interface before clearing the configuration.

Exits the configuration mode.

Example:

switch(config)# exit switch#

Step 4

show interface

Example:

switch# show interface

This example shows how to delete the configuration of an Ethernet interface while saving a checkpoint of the running configuration for rollback purposes:

switch# configure terminal switch(config)# default interface ethernet 3/1 checkpoint test8

.......Done

switch(config)#

Configuring SVI Autostate Exclude

You can configure the SVI Autostate Exclude feature on an Ethernet interface or a port channel.

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

1. configure terminal

2. interface {{type slot/port} | {port-channel number}}

(Optional) Displays the interface status and information.

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x

3-18

OL-23435-03

Cisco 7206 - VXR Router Configuration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual