Как очистить ошибки на порту cisco

Table Of Contents

Cisco NX-OS Interfaces Commands

attach fex

auto-recovery

bandwidth (interface)

beacon

bfd

bfd authentication

bfd echo

bfd echo-interface

bfd interval

bfd ipv4

bfd optimize subinterfaces

bfd per-link

bfd slow-timer

carrier-delay

channel-group

clear counters interface

clear l2protocol tunnel counters

clear lacp counters

clear vpc statistics

default interface

delay

delay restore

delay restore interface-vlan

description

description (fex)

dual-active exclude interface-vlan

duplex

encapsulation dot1Q

errdisable detect cause

errdisable recovery cause

errdisable recovery interval

feature bfd

feature interface-vlan

feature lacp

feature-set fex

feature tunnel

feature udld

feature vpc

fex

fex associate

flowcontrol

graceful consistency-check

hsrp bfd

inherit port-profile

install feature-set fex

interface cmp-mgmt module

interface ethernet

interface loopback

interface mgmt

interface port-channel

interface tunnel

interface vlan

ip eigrp bfd

ip ospf bfd

ip pim bfd

ip pim bfd-instance

ip route static bfd

ipv6 eigrp bfd

isis bfd

fabricpath switch-id

l2protocol tunnel

l2protocol tunnel cos

l2protocol tunnel drop-threshold

l2protocol tunnel shutdown-threshold

lacp max-bundle

lacp min-links

lacp port-priority

lacp rate

lacp system-priority

link debounce

load-interval

max-ports

mdix auto

medium

mtu

peer-gateway

peer-keepalive destination

peer-switch

port-channel load-balance

port-profile

rate-mode dedicated

rate-mode shared

reload fex

reload restore

role priority

serial

show bfd neighbors

show environment fex

show fex

show fex detail

show fex transceiver

show fex version

show interface

show interface brief

show interface capabilities

show interface counters

show interface counters errors

show interface counters storm-control

show interface counters trunk

show interface debounce

show interface description

show interface ethernet

show interface flowcontrol

show interface mgmt

show interface port-channel

show interface port-channel counters

show interface transceiver fex-fabric

show interface status

show interface switchport

show interface transceiver

show interface trunk

show interface tunnel

show inventory fex

show ip dhcp snooping statistics

show lacp counters

show lacp interface

show lacp neighbor

show lacp port-channel

show lacp system-identifier

show logging level fex

show module fex

show port-channel capacity

show port-channel compatibility-parameters

show port-channel database

show port-channel load-balance

show port-channel rbh-distribution

show port-channel summary

show port-channel traffic

show port-channel usage

show port-profile

show running-config fex

show running-config interface

show running-config interface mgmt

show running-config vpc

show sprom fex

show startup-config interface

show startup-config vpc

show system reset-reason fex

show tech fex all

show tech-support fex

show udld

show vdc

show version fex

show vpc brief

show vpc consistency-parameters

show vpc orphan-ports

show vpc peer-keepalive

show vpc role

show vpc statistics

shutdown

speed

state enabled

switchport

switchport access vlan

switchport autostate exclude

switchport dot1q ethertype

switchport host

switchport mode

switchport mode dot1q-tunnel

switchport mode fex-fabric

switchport trunk allowed vlan

switchport trunk native vlan

system default switchport

system jumbomtu

system-mac

system-priority

track

tunnel destination

tunnel mode

tunnel path-mtu-discovery

tunnel source

tunnel use-vrf

tunnel ttl

type

udld

udld aggressive

udld message-time

udld reset

vlan dot1q tag native

vpc

vpc domain

vpc orphan-ports suspend

vpc peer-link

Cisco NX-OS Interfaces Commands

This chapter describes the Cisco NX-OS interfaces commands.

attach fex

To access the command-line interface (CLI) of a connected Fabric Extender to run diagnostic commands, use the attach fex command.

attach fex chassis-id

Syntax Description

Defaults

None

Command Modes

EXEC mode

Command History

Usage Guidelines

Use the attach fex command to access the CLI on a connected Fabric Extender and perform diagnostic commands. We recommend that you use this command only by following the directions from Cisco technical support personnel.

This command does not require a license.

Examples

This example shows how to access the command-line interface (CLI) of a connected Fabric Extender to run diagnostic commands:

switch(config)# attach fex 101

To exit type 'exit', to abort type '$.'

Bad terminal type: "ansi". Will assume vt100.

Related Commands

auto-recovery

To configure the virtual port channel (vPC) for auto recovery if its peer is presumed nonoperational, use the auto-recovery command. To reset the vPC to the standard behavior, use the no form of this command.

auto-recovery reload-delay time-out-value

no auto-recovery reload-delay time-out-value

Syntax Description

Defaults

None

Command Modes

VPC domain configuration mode (config-vpc-domain)

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to display the vPC status in brief:

switch# configure terminal

switch(config)# vpc domain 1

switch(config-vpc-domain)# auto-recovery reload-delay 350

 Enables restoring of vPCs in a peer-detached state after reload, will wait for

350 seconds to determine if peer is un-reachable

switch(config-vpc-domain)#

This example shows how to revert the vPC to the standard behavior:

switch# configure terminal

switch(config)# vpc domain 1

switch(config-vpc-domain)# no auto-recovery reload-delay 350

switch(config-vpc-domain)#

Related Commands

bandwidth (interface)

To set the inherited and received bandwidth values for an interface, use the bandwidth command in interface configuration mode. To restore the default values, use the no form of this command.

bandwidth {kbps | inherit [kbps]}

no bandwidth {kbps | inherit [kbps]}

Syntax Description

Defaults

1000000 kbps

Command Modes

Interface configuration

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

The bandwidth command sets an informational parameter to communicate only the current bandwidth to the higher-level protocols; you cannot adjust the actual bandwidth of an interface using this command.

Note This is a routing parameter only. It does not affect the physical interface.

The bandwidth inherit command controls how a subinterface inherits the bandwidth of its main interface.

The no bandwidth inherit command enables all subinterfaces to inherit the default bandwidth of the main interface, regardless of the configured bandwidth. If a bandwidth is not configured on a subinterface, and you use the bandwidth inherit command, all subinterfaces inherit the current bandwidth of the main interface. If you configure a new bandwidth on the main interface, all subinterfaces use this new value.

If you do not configure a bandwidth on the subinterface and you configure the bandwidth inherit command on the main interface, the subinterfaces inherit the specified bandwidth.

In all cases, if an interface has an explicit bandwidth setting configured, that interface uses that setting, regardless of whether the bandwidth inheritance setting is in effect.

This command does not require a license.

Examples

This example shows how to configure all subinterfaces off this main interface to inherit the configured bandwidth:

switch(config-if)# bandwidth inherit 30000

Related Commands

beacon

To enable the beacon mode for an interface, use the beacon command. To disable the beacon mode for an interface, use the no form of this command.

beacon

no beacon

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

The beacon mode allows you to identify a physical port by flashing its link-state LED with a green light. To identify the physical port for an interface, you activate the beacon parameter for the interface.

This command does not require a license.

Examples

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

switch(config)# interface ethernet 3/1

switch(config-if)# beacon

Related Commands

bfd

To enable Bidirectional Forwarding Detection (BFD) for a protocol, use the bfd command. To disable BFD for a protocol, use the no form of this command.

bfd

no bfd

Syntax Description

This command has no arguments or keywords.

Defaults

BFD is not enabled on the protocol.

Command Modes

Router configuration
Neighbor configuration

Command History

Usage Guidelines

There are two methods to configure protocols to use BFD for failure detection. To enable BFD for all neighbors or interfaces of a protocol, enter the bfd command in router configuration mode for the Enhanced Interior Gateway Routing Protocol (EIGRP), Open Shortest Path First (OSPFv2), and Intermediate-System-to-Intermediate-System (IS-IS) or in neighbor configuration mode for the Border Gateway Protocol (BGP). If you do not want to enable BFD on all interfaces, see the interface-level BFD enable commands in the Related Commands section.

Examples

This example shows how to enable BFD for all EIGRP neighbors:

switch# configure terminal

switch(config)# router eigrp Test1

switch(config-router)# bfd 

This example shows how to enable BFD for all BGP neighbors:

switch# configure terminal

switch(config)# router bgp 1.1

switch(config-router)# neighbor 192.0.2.1 remote-as 1.0

switch(config-router-neighbor)# bfd

Related Commands

bfd authentication

To configure SHA-1 authentication for all bidirectional forwarding detection (BFD) sessions on the interface, use the bfd authentication command. To remove the SHA-1 authentication configuration, use the no form of this command.

bfd authentication keyed-SHA1 key-id id hex-key key ascii-key

no bfd authentication keyed-SHA1 key-id id key ascii-key

Syntax Description

Defaults

None

Command Modes

Interface configuration (config-if)

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to configure SHA-1 authentication for all BFD sessions on the interface:

switch# configure terminal

switch(config)# interface ethernet 3/1

switch(config-if)# bfd authentication keyed-SHA1 key-id 23 key cisco123

This example shows how to disable SHA-1 authentication on the interface:

switch(config-if)# no bfd authentication keyed-SHA1 key-id 23 key cisco123

Related Commands

bfd echo

To enable Bidirectional Forwarding Detection (BFD) echo mode, use the bfd echo command. To disable BFD echo mode, use the no form of this command.

bfd echo

no bfd echo

Syntax Description

This command has no arguments or keywords.

Defaults

BFD echo mode is enabled by default.

Command Modes

Interface configuration

Command History

Usage Guidelines

When echo mode is enabled, the required minimum receive interval value is taken from the BFD slow-timer setting.

Note Before using BFD echo mode, you must disable the IP packet verification check for identical IP source and destination addresses by entering the no hardware ip verify address identical command in the default virtual device context (VDC).

Note Before using BFD echo mode, you must disable the sending of Internet Control Message Protocol (ICMP) redirect messages by entering the no ip redirects command.

Use the no bfd echo command to stop sending echo packets and signify that the device is unwilling to forward echo packets that are received from BFD neighbors. The RequiredMinEchoRx BFD session parameter is set to zero when echo mode is disabled.

This command does not require a license.

Examples

This example shows how to configure echo mode between BFD neighbors:

switch(config)# interface Ethernet 1/1

switch(config-if)# bfd echo

This example shows that the BFD session neighbor is up and using BFD echo mode. The relevant command output is shown in bold in the output:

switch# show bfd neighbors details

OurAddr       NeighAddr      LD/RD  RH/RS    Holdown(mult)State    Int

172.16.1.2    172.16.1.1     1/6    Up       0    (3 )    Up       Fa0/1

Session state is UP and using echo function with 50 ms interval.

Local Diag: 0, Demand mode: 0, Poll bit: 0

MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3

Received MinRxInt: 1000000, Received Multiplier: 3

Holdown (hits): 3000(0), Hello (hits): 1000(337)

Rx Count: 341, Rx Interval (ms) min/max/avg: 1/1008/882 last: 364 ms ago

Tx Count: 339, Tx Interval (ms) min/max/avg: 1/1016/886 last: 632 ms ago

Registered protocols: EIGRP

Last packet: Version: 1            - Diagnostic: 0

             State bit: Up         - Demand bit: 0

             Poll bit: 0           - Final bit: 0

             Multiplier: 3         - Length: 24

             My Discr.: 6          - Your Discr.: 1

             Min tx interval: 1000000    - Min rx interval: 1000000

Related Commands

bfd echo-interface

To configure the IP address on the loopback interface, use the bfd echo-interface command. To revert the source address of the echo frames to that of the interface, use the no form of this command.

bfd echo-interface loopback interface number

no bfd echo-interface loopback interface number

Syntax Description

Defaults

The source ip address for echo packets is set to the same as configured on the interface. This command

changes the source address for the echo packets to the one configured on the specified loopback

interface.

Command Modes

Global Configuration mode

Command History

Usage Guidelines

This command does not use the loopback interface directly but uses the ip address configured on the loopback interface.

This command does not require a license.

Examples

This example shows how to configure interface used for BFD echo frames:

switch(config)# bfd echo-interface loopback 1

This example shows how to disable interface used for BFD echo frames:

switch(config)# no bfd echo-interface loopback 1

Related Commands

bfd interval

To configure the Bidirectional Forwarding Detection (BFD) session parameters, use the bfd interval command. To return to the default setting, use the no form of this command.

bfd interval mintx min_rx msec multiplier value

no bfd interval mintx min_rx msec multiplier value

Syntax Description

Defaults

BFD interval: 50 milliseconds
min_rx: 50 milliseconds
multiplier: 3

Command Modes

Global configuration
Interface configuration

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

BFD session parameters configured at the interface level take precedence over the globally configured BFD session parameters.

This command does not require a license.

Examples

This example shows how to set the BFD session parameters for Ethernet interface 3/1:

switch# configure terminal

switch(config)# interface ethernet 3/1

switch(config-if)# bfd interval 50 min_rx 20 multiplier 3

Related Commands

bfd ipv4

To disable the Bidirectional Forwarding Detection (BFD) IPV4 sessions on the interface, use the bfd ipv4 command. To revert to the default settings, use the no form of this command.

bfd ipv4

no bfd ipv4

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Interface configuration

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to disable the IPV4 sessions:

switch# configure terminal

switch(config)# interface ethernet 1/1

switch(config-if)# bfd ipv4

Related Commands

bfd optimize subinterfaces

To optimize subinterfaces on a physical interface for Bidirectional Forwarding Detection (BFD), use the bfd optimize subinterfaces command. To return to the default setting, use the no form of this command.

bfd optimize subinterfaces

no bfd optimize subinterfaces

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

You can optimize subinterfaces, because BFD creates sessions for all configured subinterfaces. BFD sets the subinterface with the lowest configured VLAN ID as the master subinterface and that subinterface uses the BFD session parameters of the parent interface. The remaining subinterfaces use the slow timer. If the master subinterface session detects an error, BFD marks all subinterfaces on that physical interface as down.

This command does not require a license.

Examples

This example shows how to enable subinterface optimization:

switch(config)# interface Ethernet 1/1

switch(config-if)# bfd optimize subinterfaces

Related Commands

bfd per-link

To enable Bidirectional Forwarding Detection (BFD) for all links in a port channel, use the bfd per-link command. To disable BFD for a port channel, use the no form of this command.

bfd per-link

no bfd per-link

Syntax Description

This command has no arguments or keywords.

Defaults

BFD is not enabled on the port channel.

Command Modes

Port channel configuration

Command History

Usage Guidelines

Us the bfd per-link command to enable BFD on each link in a port channel. BFD creates a session for each link in the port channel and provides an aggregate result to client protocols. For example, if the BFD session for one link on a port channel is up, BFD informs client protocols such as open shortest path (OSPF) that the port channel is up. The BFD session parameters are negotiated between the BFD peers in a three-way handshake.

This command does not require a license.

Examples

This example shows how to enable BFD for port channel 3:

switch# configure terminal

switch(config)# interface port-channel 3

switch(config-if)# bfd per-link

This example shows how to configure the BFD session parameters for a port channel:

switch# configure terminal

switch(config)# interface port-channel 3

switch(config-if)# bfd interval 50 min_rx 50 multiplier 3 

Related Commands

bfd slow-timer

To configure the Bidirectional Forwarding Detection (BFD) slow timer value, use the bfd slow-timer command. To return to the default setting, use the no form of this command.

bfd slow-timer milliseconds

no bfd slow-timer milliseconds

Syntax Description

Defaults

The default BFD slow timer value is 2000 milliseconds.

Command Modes

Global configuration
Interface configuration

Command History

Usage Guidelines

Use the bfd slow-timer command to configure how fast a BFD session comes up. This value also sets the RequiredMinRx (or min_rx) value when echo mode is enabled.

This command does not require a license.

Examples

This example shows that the BFD slow timer value is configured to 14,000 milliseconds:

switch(config)# bfd slow-timer 14000

This example shows that the BFD slow timer value of 14,000 milliseconds has been implemented. The values for the MinTxInt and MinRxInt correspond to the configured value for the BFD slow timer. The relevant command output is shown in bold.

switch# show bfd neighbors details

OurAddr       NeighAddr     LD/RD  RH/RS   Holdown(mult)  State     Int

172.16.10.1   172.16.10.2   1/1    Up      0    (3 )      Up        Et2/0

Session state is UP and using echo function with 50 ms interval.

Local Diag: 0, Demand mode: 0, Poll bit: 0

MinTxInt: 14000, MinRxInt: 14000, Multiplier: 3

Received MinRxInt: 10000, Received Multiplier: 3

Holdown (hits): 3600(0), Hello (hits): 1200(418)

Rx Count: 422, Rx Interval (ms) min/max/avg: 1/1480/1087 last: 112 ms ago

Tx Count: 420, Tx Interval (ms) min/max/avg: 1/2088/1090 last: 872 ms ago

Registered protocols: OSPF

Last packet: Version: 1            - Diagnostic: 0

             State bit: Up         - Demand bit: 0

             Poll bit: 0           - Final bit: 0

             Multiplier: 3         - Length: 24

             My Discr.: 1          - Your Discr.: 1

             Min tx interval: 14000 - Min rx interval: 14000

Related Commands

carrier-delay

To set the carrier delay on an interface, use the carrier-delay command. To return to the default carrier delay value, use the no form of this command.

carrier-delay {sec | {msec value}}

no carrier-delay

Syntax Description

Defaults

The default is 100 milliseconds.

Command Modes

Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Note You must enable the VLAN interface feature, using the feature interface-vlan command, before you can use this command.

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.

Note The carrier-delay command is supported only on the VLAN interface mode; no other interface modes support this command.

In most environments, a lower carrier delay time is better than a higher one. The 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 churn in your routing tables. However, if you 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.

This command does not require a license.

Examples

This example shows how to set the carrier delay timer to 20 minutes for VLAN 6:

switch(config)# interface vlan 6

switch(config-if)# carrier-delay 20

Related Commands

channel-group

To assign and configure a physical interface to a port-channel group, use the channel-group command. To remove the channel-group configuration from the interface, use the no form of this command.

channel-group number [force] [mode {active | on | passive}]

no channel-group [number]

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Use this command to create a channel group that includes the interface that you are working on and to add or remove specific interfaces from the channel group. Use this command to move a port from one channel group to another. You enter the channel group that you want the port to move to; the device automatically removes the specified port from its present channel group and adds that port to the specified channel group.

After you enable LACP globally by using the feature lacp command, you enable LACP on each channel by configuring the channel mode as either active or passive. A port channel in the on channel mode is a pure port channel and can aggregate a maximum of eight ports. It does not run LACP.

You cannot change the mode for an existing port channel or any of its interfaces if that port channel is not running LACP; the channel mode remains as on. The system returns an error message if you try.

All ports in one port channel must be in the same virtual device context (VDC). With LACP enabled, this requirement applies to the possible eight active ports and the possible eight standby ports. The port channels can originate in one VDC (with all ports in that channel in the same VDC) and partner with a port channel in another VDC (again, all ports in that channel must be in that VDC).

Use the no form of this command to remove the physical interface from the port channel. When you delete the last physical interface from a port channel, the port channel remains. To delete the port channel completely, use the no form of this interface port-channel command.

The compatibility check includes the following operational attributes:

•Network layer

•(Link) speed capability

•Speed configuration

•Duplex capability

•Duplex configuration

•Port mode

•Access VLAN

•Trunk native VLAN

•Tagged or untagged

•Allowed VLAN list

•MTU size

•SPAN—Cannot be SPAN source or destination port

•Layer 3 Ports —Cannot have subinterfaces

•Storm control

•Flow control capability

•Flow control configuration

Use the show port-channel compatibility-parameters command to see the full list of compatibility checks that the Cisco NX-OS uses.

You can only add interfaces configured with the channel mode set to on to static port channels, that is without a configured aggregation protocol and you can only add interfaces configured with the channel mode as active or passive to port channels that are running LACP.

You can configure these attributes on an individual member port. If you configure a member port with an incompatible attribute, Cisco NX-OS suspends that port in the port channel.

Alternatively, you can force ports with incompatible parameters to join the port channel as long the following parameters are the same:

•(Link) speed capability

•Speed configuration

•Duplex capability

•Duplex configuration

•Flow control capability

•Flow control configuration

When the interface joins a port channel, some of its individual parameters are removed and replaced with the values on the port channel as follows:

•Bandwidth

•Delay

•Extended Authentication Protocol over UDP

•VRF

•IP address (v4 and v6)

•MAC address

•Spanning Tree Protocol

•NAC

•Service policy

•Quality of Service (QoS)

•ACLs

Many of the following interface parameters remain unaffected with the interface joins or leaves a port channel:

•Beacon

•Description

•CDP

•LACP port priority

•Debounce

•UDLD

•MDIX

•Rate mode

•Shutdown

•SNMP trap

If subinterfaces are configured for the port-channel interface and a member port is removed from the port channel, the configuration of the port-channel subinterface is not propagated to the member ports.

Any configuration changes that you make in any of the compatibility parameters to the port-channel interface are propagated to all interfaces within the same channel group as the port channel (for example, configuration changes are also propagated to the physical interfaces that are not part of the port channel but are part of the channel group).

You do not have to create a port-channel interface before you assign a physical interface to a channel group. A port-channel interface is created automatically when the channel group gets its first physical interface, if it is not already created.

You can create either a Layer 2 or a Layer 3 port channel by entering the interface port-channel command or when the channel group gets its first physical interface assignment. The port channels are not created at run time or dynamically.

Note The number of ports allowed in a port-channel (for ON mode) is different between M1 modules and F1 modules (D1) only VDCs. The number is 8 for M1 modules or M1-F1 VDCs and 16 for F1 modules.

This command does not require a license.

Examples

This example shows how to add an interface to LACP channel group 5 in active mode:

switch(config-if)# channel-group 5 mode active

Related Commands

clear counters interface

To clear the interface counters, use the clear counters interface command.

clear counters interface {all | ethernet slot/port | loopback number | mgmt number | port-channel channel-number | tunnel tunnel-number | vlan vlan-number}

Syntax Description

Defaults

None

Command Modes

Any command mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Examples

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

switch# clear counters interface ethernet 5/5

Related Commands

clear l2protocol tunnel counters

To clear the Layer 2 protocol tunnel statistics counters, use the clear l2protocol tunnel counters command.

clear l2protocol tunnel counters [interface if-range]

Syntax Description

Defaults

None

Command Modes

Any command mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

If no interfaces are specified, the Layer 2 protocol tunnel statistics are cleared for all interfaces.

This command does not require a license.

Examples

This example shows how to clear the Layer 2 protocol tunnel statistics counters:

switch# clear l2protocol tunnel counters 

Related Commands

clear lacp counters

To clear the statistics for all interfaces for Link Aggregation Control Protocol (LACP) groups, use the clear lacp counters command.

clear lacp counters [interface port-channel channel-number]

Syntax Description

Defaults

None

Command Modes

Any command mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

If you enter this command for a static port-channel group without enabling the aggregation protocol, the device ignores the command.

If you do not specify a channel number, the LACP counters for all LACP port groups are cleared.

This command does not require a license.

Examples

This example shows how to clear all LACP counters:

switch(config)# clear lacp counters

This example shows how to clear all LACP counters for the LACP port-channel group 20:

switch(config)# clear lacp counters interface port-channel 20

Related Commands

clear vpc statistics

To clear virtual port-channel (vPC) statistics, use the clear vpc statistics command.

clear vpc statistics {all | peer-keepalive | peer-link | vpc number}

Syntax Description

Defaults

None

Command Modes

Any command mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Use the clear vpc statistics command to clear the vPC statistics. If the feature is not enabled, this command is unavailable.

The clear vpc statistics peer-link and clear vpc statistics vpc number commands are redirected to the appropriate port channel and the clear statistics port-channel channel-number command.

This command does not require a license.

Examples

This example shows how to clear the statistics for vPC 10:

switch(config)# clear vpc statistics vpc 10

Related Commands

default interface

To create a checkpoint of the running configuration for rollback purposes, use the default interface command.

default interface if [checkpoint name]

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use this command to return an interface to it’s default state. All the user configuration under the specified interface(s) is deleted upon the successful completion of the command. You can optionally create a checkpoint before deleting the interface configuration, so that you can later choose roll back to the original configuration.

Caution
When using this command, you delete the configuration of the specified interfaces unless you enter the checkpoint keyword. The optional checkpoint keyword allows you to create a checkpoint of the interface configuration to that you can later roll back to the original configuration.

This command does not require a license.

Examples

This example shows how to create a checkpoint of the running configuration for rollback purposes:

switch(config)# default interface ethernet 2/1 checkpoint test

Related Commands

delay

To configure the interface throughput delay for Ethernet interfaces, use the delay command. To remove the configured throughput delay, use the no form of this command.

delay value

no delay

Syntax Description

Defaults

10 microseconds for all interfaces except loopback ports

5000 microseconds for loopback ports

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Beginning with Cisco NX-OS Release 4.2(1) for the Cisco Nexus 7000 Series devices, the default delay values are changed. Prior to this release, all the default delay value for all interfaces was 100 microseconds.

After upgrading from an older release, when you enter the show running command on a VLAN interface, the display shows an additional configuration of «delay 100». If you want to revert the delay value to the new default, enter the no delay command for that VLAN interface.

Specifying a value for the throughput delay provides a value for use by Layer 3 protocols; it does not change the actual throughput delay of an interface.

This command does not require a license.

Examples

This example shows how to configure the throughput-delay time to 100,000 microseconds for the slot 3 port 1 Ethernet interface:

switch(config)# interface ethernet 3/1

switch(config-if)# delay 10000

Related Commands

delay restore

To delay the virtual port channel (vPC) from coming up on the restored vPC peer device after a reload when the peer adjacency is already established, use the delay restore command. To return to the default value, use the no form of this command.

delay restore seconds

no delay restore seconds

Syntax Description

Defaults

30 seconds

Command Modes

vpc-domain command mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the delay restore command to avoid upstream traffic from the access device to the core from being dropped when you restore the vPC peer devices. If the restored vPCs come up before the routing tables are converged, you might see packet drops.

This command does not require a license.

Examples

This example shows how to configure the delay reload:

switch# configure terminal 

switch(config)# vpc domain 5

switch(config-vpc-domain)# delay restore 40

Related Commands

delay restore interface-vlan

To allow Layer 3 routing protocols to converge and Forwarding Information Base (FIB) programming to complete for a more graceful restoration of switched virtual interfaces (SVI) on the restored virtual port channel (vPC) after the delay of the vPC from coming up on the restored vPC peer device, use the delay restore interface-vlan command. To return to the default value, use the no form of this command.

delay restore interface-vlan seconds

no delay restore interface-vlan seconds

Syntax Description

Defaults

10 seconds

Command Modes

vpc-domain command mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the delay restore command to avoid upstream traffic from the access device to the core from being dropped when you restore the vPC peer devices. If the restored vPCs come up before the routing tables are converged, you might see packet drops.

This command does not require a license.

Examples

This example shows how to configure the delay reload:

switch(config)# vpc domain 1

switch(config-vpc-domain)# delay restore 60

switch(config-vpc-domain)# delay restore interface-vlan 30

switch(config-vpc-domain)#

Related Commands

description

To provide textual interface descriptions for the Ethernet and management interfaces, use the description command. To remove the description, use the no form of this command.

description text

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

You use the description command to provide textual interface descriptions.

This command does not require a license.

Examples

This example shows how to add the description server1 to the Ethernet interface on slot 5, port 2:

switch(config)# interface ethernet 5/1

switch(config-if)# description server1

Related Commands

description (fex)

To specify a description for a Fabric Extender, use the description command. To revert to the default description, use the no form of this command.

description description

no description

Syntax Description

Defaults

None

Command Modes

Fabric Extender configuration mode

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to specify a description for a Fabric Extender:

switch# configure terminal 

switch(config-fex)# description Rack16_FEX101 

This example shows how to revert to the default description for a Fabric Extender:

switch# configure terminal 

switch(config-fex)# no description 

Related Commands

dual-active exclude interface-vlan

To ensure that certain VLAN interfaces are not shut down on the virtual port-channel (vPC) secondary peer device when the vPC peer link fails for those VLANs carried on the vPC peer link but not by the vPC configuration, use the dual-active exclude interface-vlan command. To return to the default value, use the no form of this command.

dual-active exclude interface-vlan {range}

no dual-active exclude interface-vlan {range}

Syntax Description

Defaults

None

Command Modes

vpc-domain configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the dual-active exclude interface-vlan command to ensure that those VLAN interfaces on the vPC secondary peer device that are carried on the vPC peer link but not by the vPC configuration do not go down if the vPC peer link fails. The VLAN interfaces must have already been configured.

Caution
We do not recommend that you configure an interface-VLAN exclude for a VLAN carried on a vPC because this action might cause packet losses on dual-active devices if the interface-VLAN still captures Layer 3 traffic while the vPC primary device and the vPC peer link are down.

This command does not require a license.

Examples

This example shows how to configure the device to keep the VLAN interfaces up on the vPC peer devices if the peer link fails:

switch(config)# vpc-domain 5

switch(config-vpc-domain)# dual-active exclude interface-vlan 10

Related Commands

duplex

To specify the duplex mode as full, half, or autonegotiate, use the duplex command. To return the system to default mode, use the no form of this command.

duplex {full | half | auto}

no duplex {full | half | auto}

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

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-Mbps speed, the port is automatically configured to use half-duplex mode, but you can specify full-duplex mode instead. Gigabit Ethernet is full duplex only. You cannot change the duplex mode on Gigabit Ethernet ports or on a 10/100/1000-Mbps port that is set for Gigabit Ethernet.

See the Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x, for more information on interface speed and duplex settings.

This command does not require a license.

Examples

This example shows how to specify the duplex mode for full duplex:

switch(config-if)# duplex full

Related Commands

encapsulation dot1Q

To enable IEEE 802.1Q encapsulation of traffic on a specified subinterface in a virtual LAN (VLAN), use the encapsulation dot1q command. To disable encapsulation, use the no form of this command.

encapsulation dot1Q vlan-id

no encapsulation dot1Q vlan-id

Syntax Description

Defaults

No encapsulation

Command Modes

Subinterface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

IEEE 802.1Q encapsulation is configurable on Ethernet interfaces. IEEE 802.1Q is a standard protocol for interconnecting multiple switches and routers and for defining VLAN topologies.

Use the encapsulation dot1q command in subinterface range configuration mode to apply a VLAN ID to the subinterface.

This command does not require a license.

Examples

This example shows how to enable dot1Q encapsulation on a subinterface for VLAN 30:

switch(config-subif)# encapsulation dot1q 30

Related Commands

errdisable detect cause

To enable error-disabled (errdisable) detection for an application, use the errdisable detect cause command. To return to the default setting, use the no form of this command.

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

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

Syntax Description

Defaults

Disabled

Command Modes

Global configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the errdisable detect cause command to enable error detection for an application.

A cause is defined as the reason why the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in an error-disabled state. This error-disabled state is an operational state that is similar to the link-down state. You must enter the shutdown command and then the no shutdown command to recover an interface manually from the error-disabled state.

This command does not require a license.

Examples

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

switch(config)# errdisable detect cause all

Related Commands

errdisable recovery cause

To enable an automatic recovery from the error-disabled (errdisable) state for an application, use the errdisable recovery cause command. To return to the default setting, use the no form of this command.

errdisable recovery cause {all | bpduguard | link-flap | failed-port-state | psecure-violation | security-violation | storm-control | udld | vpc-peerlink}

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

Syntax Description

Defaults

Disabled

Command Modes

Global configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the errdisable recovery cause command to enable an automatic recovery on the interface from the error-disabled state for an application. This command tries to bring the interface out of the error-disabled state and retry operation once all the causes have timed out. The interface automatically tries to come up again after 300 seconds. To change this interval, use the errdisable recovery interval command.

This command does not require a license.

Examples

This example shows how to automatically recover from the error-disabled state for link flapping after you have enabled the recovery timer:

switch(config)# errdisable recovery cause link-flap

Related Commands

errdisable recovery interval

To enable the recovery timer, use the errdisable recovery interval command.

errdisable recovery interval interval

Syntax Description

Defaults

300 seconds

Command Modes

Global configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the errdisable recovery interval command to configure the recovery timer.

This command does not require a license.

Examples

This example shows how to configure the recovery timer:

switch(config)# errdisable recovery interval 32

Related Commands

feature bfd

To enable Bidirectional Forwarding Detection (BFD), use the feature bfd command. To return to the default setting, use the no form of this command.

feature bfd

no feature bfd

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

You must use the feature bfd command to enable the BFD functionality.

Note The device does not display any BFD commands until you enable the feature.

This command does not require a license.

Examples

This example shows how to enable BFD functionality on the device:

switch(config)# feature bfd

Related Commands

feature interface-vlan

To enable the creation of VLAN interfaces (switched virtual interfaces [SVI]), use the feature interface-vlan command. To disable the VLAN interface feature, use the no form of this command.

feature interface-vlan

no feature interface-vlan

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

You must use the feature interface-vlan command before you can create VLAN interfaces.

This command does not require a license.

Examples

This example shows how to enable the interface VLAN feature:

switch(config)# feature interface-vlan

Related Commands

feature lacp

To enable Link Aggregation Control Protocol (LACP) port channeling on the device, use the feature lacp command. To disable LACP on the device, use the no form of this command.

feature lacp

no feature lacp

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

You must remove all the LACP configuration parameters from all port channels on the device before you can disable LACP. You cannot disable LACP while LACP configurations remain on the device.

Even after you enable LACP globally, you do not have to run LACP on all port channels on the device. You enable LACP on each channel mode using the channel-group mode command.

When you enter the no form of this command, the system removes all the LACP configuration from the device.

This command does not require a license.

Examples

This example shows how to enable LACP port channeling on the device:

switch(config)# feature lacp

Related Commands

feature-set fex

To enable the Fabric Extender (FEX) feature set, use the feature-set fex command.

feature-set fex

Syntax Description

This command has no arguments or keywords.

Defaults

None

Command Modes

Global configuration mode

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to enable a FEX feature set:

switch(config)# feature-set fex

Related Commands

feature tunnel

To enable the creation of tunnel interfaces, use the feature tunnel command. To disable the tunnel interface feature, use the no form of this command.

feature tunnel

no feature tunnel

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

You must use the feature tunnel command before you can create tunnel interfaces.

This command requires the Enterprise license.

Examples

This example shows how to enable the interface tunnel feature:

switch(config)# feature tunnel

Related Commands

feature udld

To enable Unidirectional Link Detection (UDLD) globally on the device, use the feature udld command. To disable UDLD globally on the device, use the no form of this command.

feature udld

no feature udld

Syntax Description

This command has no arguments or keywords.

Defaults

None

Command Modes

Global configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the feature udld command to enable UDLD globally on the device. UDLD must be also enabled on the other linked interface and its device. After enabling the devices, it is possible to enable a UDLD mode for an interface.

Use the no feature udld command to disable UDLD globally for Ethernet interfaces on the device.

This command does not require a license.

Examples

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

switch(config)# feature udld

This example shows how to disable UDLD for a device:

switch(config)# no feature udld

Related Commands

feature vpc

To enable virtual port channels (vPCs), use the feature vpc command. To return to the default setting, use the no form of this command.

feature vpc

no feature vpc

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

You must use the feature vpc command to enable the vPC functionality. You must enable vPCs before you can configure them.

Note When you disable vPC, the device clears all the vPC configurations.

This command does not require a license.

Examples

This example shows how to enable vPC functionality on the device:

switch(config)# feature vpc

Related Commands

fex

To create a Fabric Extender and enter fabric extender configuration mode, use the fex command. To delete the Fabric Extender configuration, use the no form of this command.

fex chassis-id

no fex chassis-id

Syntax Description

Defaults

None

Command Modes

Global configuration mode

Command History

Usage Guidelines

You must create and configure the Fabric Extender before you can connect and associate it to an interface on the parent switch. Once you associate the Fabric Extender to the switch, the configuration that you created is transferred over to the Fabric Extender and applied.

This command does not require a license.

Examples

This example shows how to enter Fabric Extender configuration mode:

switch# configure terminal 

This example shows how to delete the Fabric Extender configuration:

switch(config-fex)# no fex 101

Related Commands

fex associate

To associate a Fabric Extender to a fabric interface, use the fex associate command. To disassociate the Fabric Extender, use the no form of this command.

fex associate chassis-id

no fex associate chassis-id

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Command History

Usage Guidelines

Before you can associate an interface on the parent switch to the Fabric Extender, you must first make the interface into a fabric interface by entering the switchport mode fex-fabric command.

This command does not require a license.

Examples

This example shows how to associate the Fabric Extender to an Ethernet interface:

switch# configure terminal 

switch(config)# interface ethernet 1/40 

switch(config-if)# switchport mode fex-fabric 

switch(config-if)# fex associate 101 

This example shows how to associate the Fabric Extender to an EtherChannel interface:

switch# configure terminal 

switch(config)# interface port-channel 4 

switch(config-if)# switchport mode fex-fabric 

switch(config-if)# fex associate 10

Related Commands

flowcontrol

To enable or disable the ability of the Ethernet port to send and receive flow-control pause frames, use the flowcontrol command. To return to the default flow-control settings, use the no form of this command.

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

no flowcontrol {send | receive}

Syntax Description

Defaults

1-Gb/s interfaces—Off for receive and send

10-Gb/s interfaces—Off for receive and send

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

If the traffic between two F1 ports is routed and the sending port have Link flow control enabled, PAUSE frames will not be send if the receiving port is congested by the sending interface. While if the traffic is bridged between two F1 ports and sending port have a link flow control enabled, PAUSE frames will be send if the receiving port is congested by the sending interface.

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, the remote port has a receive parameter set to on or desired. If you want the local port to receive flow-control frames, you must 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.

For Ethernet ports that run at 1 Gbps or faster speed, 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 Gbps, 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 ports 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 Gbps, you cannot use the desired state for the send or receive parameter.

To see how the different port flow-control states affect the link flow-control state, see Table 1.

This command does not require a license.

Examples

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

switch(config)# interface ethernet 3/1

switch(config-if)# flowcontrol send on

Related Commands

graceful consistency-check

To enable a graceful type-1 consistency check on per VLAN basis, use the graceful consistency-check command. To disable the graceful consistency check, use the no form of this command.

graceful consistency-check

no graceful consistency-check

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

VPC domain configuration (config-vpc-domain)

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to enable the graceful type-1 consistency check:

switch# configure terminal

switch(config)# vpc domain 1

switch(config-vpc-domain)# graceful consistency-check

switch(config-vpc-domain)#

This example shows how to disable the graceful type-1 consistency check:

switch# configure terminal

switch(config)# vpc domain 1

switch(config-vpc-domain)# no graceful consistency-check

switch(config-vpc-domain)#

Related Commands

hsrp bfd

To enable Bidirectional Forwarding Detection (BFD) on a Hot Standby Router Protocol (HSRP) interface, use the hsrp bfd command. To return to the default setting, use the no form of this command.

hsrp bfd

no hsrp bfd

Syntax Description

This command has no keywords or arguments.

Defaults

None

Command Modes

Interface configuration mode

Command History

Usage Guidelines

Use the hsrp bfd command to enable BFD on an HSRP interface.

This command does not require a license.

Examples

This example shows how to enable BFD for an HSRP interface:

switch# configure terminal

switch(config)# interface ethernet 2/1

switch(config-if)# hsrp bfd

Related Commands

inherit port-profile

To assign a port profile to an interface or range of interfaces and to inherit an additional port profile onto an existing port profile, use the inherit port-profile command. To remove an inherited port profile or to remove a port profile from specified interfaces, use the no form of this command.

inherit port-profile name

no inherit port-profile name

Syntax Description

Defaults

None

Command Modes

Interface configuration mode
Port-profile configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the inherit port-profile command to do the following:

•Assign the port profile to a specified interface or range of specified interfaces. You do this action in the interface configuration mode. The maximum number of interfaces that can inherit a single profile is 512.

•Inherit configuration parameters from another port profile onto an existing port profile. You do this action in the port-profile mode, using the name of the port profile that you want to inherit configurations into. Only port profiles of the same type can be inherited by another port profile. The device supports four levels of inheritance except for the switchport private-vlan mapping and the private-vlan mapping commands, which support only one inheritance level. The same port profile can be inherited by any number of port profiles. In a port-profile inheritance hierarchy, all the profiles must have the same switchport configuration.

See the port-profile command and the state-enabled command for information about creating, configuring, and enabling port profiles.

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

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. Also, when you remove a port profile, the system checks the interface configuration and either skips port-profile commands that have been overridden by directly entered interface commands or returns the command to the default value.

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

You use the port-profile configuration mode to remove an inherited port profile from an original port profile.

This command does not require a license.

Examples

This example shows how to assign a specified port profile to a range of interfaces:

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

switch(config-if)# port-profile test

This example shows how to inherit the configuration parameters from the port profile named switch onto the port profile named test:

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

Related Commands

install feature-set fex

To install a Fabric Extender (FEX) feature set, use the install feature-set fex command.

install feature-set fex

Syntax Description

This command has no arguments or keywords.

Defaults

None

Command Modes

Global configuration mode

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to install a FEX feature set:

switch(config)# install feature-set fex

Related Commands

interface cmp-mgmt module

To create a Connectivity Management Processor (CMP) management interface and enter interface configuration mode, use the interface cmp-mgmt module command.

interface cmp-mgmt module number

Syntax Description

Defaults

None

Command Modes

Global configuration mode
Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the interface cmp-mgmt module command to create a CMP management interface.

This command does not require a license.

Examples

This example shows how to create a CMP management interface:

switch(config)# interface cmp-mgmt module 9

interface ethernet

To configure an Ethernet interface and enter interface configuration mode, use the interface ethernet command.

interface ethernet slot/port

Syntax Description

Defaults

None

Command Modes

Global configuration mode
Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the interface ethernet command to enter the interface configuration mode for the specified interface or range of interfaces.

This command does not require a license.

Examples

This example shows how to enter the interface command mode for the Ethernet interface on slot 2, port 1:

switch(config)# interface ethernet 2/1

Related Commands

interface loopback

To create a loopback interface and enter interface configuration mode, use the interface loopback command. To remove a loopback interface, use the no form of this command.

interface loopback number

no interface loopback number

Syntax Description

Defaults

None

Command Modes

Global configuration mode
Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Use the interface loopback command to create or modify loopback interfaces.

This command does not require a license.

Examples

This example shows how to create a loopback interface:

switch(config)# interface loopback 50

Related Commands

interface mgmt

To configure the management interface and enter interface configuration mode, use the interface mgmt command.

interface mgmt number

Syntax Description

Defaults

None

Command Modes

Global configuration mode
Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Use the interface mgmt command to configure the management interface and to enter the interface configuration mode.

This command does not require a license.

Examples

This example shows how to enter the interface configuration mode to configure the management interface:

switch(config)# interface mgmt

Related Commands

interface port-channel

To create a port-channel interface and enter interface configuration mode, use the interface port-channel command. To remove a logical port-channel interface or subinterface, use the no form of this command.

interface port-channel channel-number

no interface port-channel channel-number

Syntax Description

Defaults

None

Command Modes

Global configuration mode
Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Use the interface port-channel command to create or delete port-channel groups and to enter the interface configuration mode for the port channel.

You can create port channels implicitly using the attach fex command or explicitly using the feature-set fex command.

A port can belong to only one channel group.

You can create subinterfaces on a Layer 3 port-channel interface. However, you cannot add a Layer 3 interface that has existing subinterfaces to a port channel.

Note The Layer 3 port-channel interface is the routed interface.

The Link Aggregation Control Protocol (LACP) system ID is unique for each virtual device context (VDC), and channel-group numbers and names can be reused in different VDCs.

When you use the interface port-channel command, follow these guidelines:

•If you are using Cisco Discovery Protocol (CDP), you must configure it only on the physical interface and not on the port-channel interface.

•If you do not assign a static MAC address on the port-channel interface, a MAC address is automatically assigned. If you assign a static MAC address and then later remove it, the MAC address is automatically assigned.

•The MAC address of the port channel is the address of the first operational port added to the channel group. If this first-added port is removed from the channel, the MAC address comes from the next operational port added, if there is one.

This command does not require a license.

Examples

This example shows how to create a port-channel group interface with channel-group number 50:

switch(config)# interface port-channel 50

Related Commands

interface tunnel

To create a tunnel interface and enter interface configuration mode, use the interface tunnel command. To remove a tunnel interface, use the no form of this command.

interface tunnel number

no interface tunnel number

Syntax Description

Defaults

None

Command Modes

Global configuration mode
Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Use the interface tunnel command to create or modify tunnel interfaces.

Cisco NX-OS supports the generic routing encapsulation (GRE) header defined in IETF RFC 2784. Cisco NX-OS does not support tunnel keys and other options from IETF RFC 1701.

You can configure IP tunnels only in the default virtual device context (VDC).

This command requires the Enterprise license.

Examples

This example shows how to create a tunnel interface:

switch(config)# interface tunnel 50

Related Commands

interface vlan

To create a VLAN interface and enter interface configuration mode, use the interface vlan command. To remove a VLAN interface, use the no form of this command.

interface vlan vlan-id

no interface vlan vlan-id

Syntax Description

Defaults

None

Command Modes

Global configuration mode
Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Use the interface vlan command to create or modify VLAN interfaces.

The VLAN interface is created the first time that you enter the interface vlan command for a particular VLAN. The vlan-id argument corresponds to the VLAN tag that is associated with the data frames on an Inter-Switch Link (ISL), the IEEE 802.1Q-encapsulated trunk, or the VLAN ID that is configured for an access port.

This command does not require a license.

Examples

This example shows how to create a VLAN interface for VLAN 50:

switch(config)# interface vlan 50

Related Commands

ip eigrp bfd

To enable Bidirectional Forwarding Detection (BFD) on an Enhanced Interior Gateway Routing Protocol (EIGRP) interface, use the ip eigrp bfd command. To return to the default setting, use the no form of this command.

ip eigrp instance-tag bfd

no ip eigrp instance-tag bfd

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Command History

Usage Guidelines

Use the ip eigrp bfd command to enable BFD on an EIGRP interface. This command takes precedence over the bfd command in router configuration mode.

This command does not require a license.

Examples

This example shows how to enable BFD for an EIGRP interface:

switch# configure terminal

switch(config)# interface ethernet 2/1

switch(config-if)# ip eigrp Test1 bfd

Related Commands

ip ospf bfd

To enable Bidirectional Forwarding Detection (BFD) on an Open Shortest Path First version 2 (OSPFv2) interface, use the ip ospf bfd command. To return to the default setting, use the no form of this command.

ip ospf bfd

no ip ospf bfd

Syntax Description

This command has no keywords or arguments.

Defaults

None

Command Modes

Interface configuration mode

Command History

Usage Guidelines

Use the ip ospf bfd command to enable BFD on an OSPFv2 interface. This command takes precedence over the bfd command in router configuration mode.

This command does not require a license.

Examples

This example shows how to enable BFD for an OSPF interface:

switch# configure terminal

switch(config)# interface ethernet 2/1

switch(config-if)# ip ospf bfd

Related Commands

ip pim bfd

To enable Bidirectional Forwarding Detection (BFD) for Protocol Independent Multicast (PIM), use the ip pim bfd command. To return to the default setting, use the no form of this command.

ip pim bfd

no ip pim bfd

Syntax Description

This command has no keywords or arguments.

Defaults

None

Command Modes

Global configuration mode

Command History

Usage Guidelines

Use the ip pim bfd command to enable BFD for PIM.

This command does not require a license.

Examples

This example shows how to enable BFD for PIM:

switch# configure terminal

switch(config)# ip pim bfd

Related Commands

ip pim bfd-instance

To enable Bidirectional Forwarding Detection (BFD) for Protocol Independent Multicast (PIM) on an interface, use the ip pim bfd-instance command. To return to the default setting, use the no form of this command.

ip pim bfd-instance [disable]

no ip pim bfd-instance [disable]

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Command History

Usage Guidelines

Use the ip pim bfd-instance command to enable BFD for PIM on an interface. This configuration (with or without the disable keyword) overrides the BFD configuration for PIM at the global or VRF configuration level.

This command does not require a license.

Examples

This example shows how to disable BFD for PIM on interface ethernet 2/1 when BFD is enabled globally for PIM:

switch# configure terminal

switch(config)# ip pim bfd

switch(config)# interface ethernet 2/1

switch(config-if)# ip pim bfd-instance disable

Related Commands

ip route static bfd

To enable Bidirectional Forwarding Detection (BFD) on a static route, use the ip route static bfd command. To return to the default setting, use the no form of this command.

ip route static bfd interface {nh-address | nh-prefix}

no ip route static bfd interface {nh-address | nh-prefix}

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Command History

Usage Guidelines

Use the ip route static bfd command to enable BFD on a static route.

This command does not require a license.

Examples

This example shows how to enable BFD for a static route:

switch# configure terminal

switch(config)# interface ethernet 2/1

switch(config-if)# ip route static bfd ethernet 2/1 192.0.2.4

Related Commands

ipv6 eigrp bfd

To enable Bidirectional Forwarding Detection (BFD) on an Enhanced Interior Gateway Routing Protocol (EIGRP) interface, use the ipv6 eigrp bfd command. To return to the default setting, use the no form of this command.

ipv6 eigrp instance-tag bfd

no ipv6 eigrp instance-tag bfd

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Command History

Usage Guidelines

Use the ipv6 eigrp bfd command to enable BFD on an EIGRP interface. This command takes precedence over the bfd command in router configuration mode.

This command does not require a license.

Examples

This example shows how to enable BFD for an EIGRP interface:

switch# configure terminal

switch(config)# interface ethernet 2/1

switch(config-if)# ipv6 eigrp Test1 bfd

Related Commands

isis bfd

To enable Bidirectional Forwarding Detection (BFD) on an Intermediate System-to-Intermediate System (IS-IS) interface, use the isis bfd command. To return to the default setting, use the no form of this command.

isis bfd

no isis bfd

Syntax Description

This command has no keywords or arguments.

Defaults

None

Command Modes

Interface configuration mode

Command History

Usage Guidelines

Use the isis bfd command to enable BFD on an IS-IS interface. This command takes precedence over the bfd command in router configuration mode.

This command does not require a license.

Examples

This example shows how to enable BFD for an IS-IS interface:

switch# configure terminal

switch(config)# interface ethernet 2/1

switch(config-if)# isis bfd

Related Commands

fabricpath switch-id

To configure an emulated switch ID, use the fabricpath switch-id command. To return to the default setting, use the no form of this command.

fabricpath switch-id switch-id

no fabricpath switch-id switch-id

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to configure an emulated switch ID:

switch(config)# vpc domain 1

switch(config-vpc-domain)# fabricpath switch-id 4

Configuring fabricpath switch id will flap vPCs. Continue (yes/no)? [no] yes

--------:: Re-init of peer-link and vPCs started  ::--------

switch(config-vpc-domain)#

This example shows how to set the default ID value:

switch(config)# vpc domain 1

switch(config-vpc-domain)# no fabricpath switch-id 4

Deconfiguring fabricpath switch id will flap vPCs. Continue (yes/no)? [no] yes

--------:: Re-init of peer-link and vPCs started  ::--------

switch(config-vpc-domain)#

Related Commands

l2protocol tunnel

To enable Layer 2 protocol tunneling, use the l2protocol tunnel command. To disable protocol tunneling, use the no form of this command.

l2protocol tunnel [cdp | stp | vtp]

no l2protocol tunnel [cdp | stp | vtp]

Syntax Description

Defaults

Layer 2 protocol tunneling is disabled.

Command Modes

Interface configuration mode

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to enable Layer 2 protocol tunneling:

switch(config-if)# l2protocol tunnel cdp 

Related Commands

l2protocol tunnel cos

To specify a global class of service (CoS) value on all Layer 2 protocol tunneling interfaces, use the l2protocol tunnel cos command. To reset the global CoS value to its default, use the no form of this command.

l2protocol tunnel cos cos-value

no l2protocol tunnel cos

Syntax Description

Defaults

CoS value is 5.

Command Modes

Global configuration mode

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to specify a global CoS value on all Layer 2 protocol tunneling interfaces:

switch(config)# l2protocol tunnel cos 7 

Related Commands

l2protocol tunnel drop-threshold

To specify the maximum number of packets that can be processed on a Layer 2 protocol tunneling interface before being dropped, use the l2protocol tunnel drop-threshold command. To reset the values to 0 and disable the drop threshold, use the no form of this command.

l2protocol tunnel drop-threshold [cdp | stp | vtp] packets-per-sec

no l2protocol tunnel drop-threshold [cdp | stp | vtp]

Syntax Description

Defaults

The drop threshold is disabled.

Command Modes

Interface configuration mode

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to specify the maximum number of CDP packets that can be processed on an Layer 2 protocol tunneling interface before being dropped:

switch(config-if)# l2protocol tunnel drop-threshold cdp 1024 

Related Commands

l2protocol tunnel shutdown-threshold

To specify the maximum number of packets that can be processed on a Layer 2 protocol tunneling interface, use the l2protocol tunnel shutdown-threshold command. To reset the values to 0 and disable the shutdown threshold, use the no form of this command

l2protocol tunnel shutdown-threshold [cdp | stp | vtp] packets-per-sec

no l2protocol tunnel shutdown-threshold [cdp | stp | vtp]

Syntax Description

Defaults

The shutdown threshold is disabled.

Command Modes

Interface configuration mode

Command History

Usage Guidelines

When the number of packets is exceeded, the port is put in error-disabled state.

This command does not require a license.

Examples

This example shows how to specify the maximum number of packets that can be processed on an Layer 2 protocol tunneling interface before the port is put in error-disabled state:

switch(config-if)# l2protocol tunnel shutdown-threshold 2048 

Related Commands

lacp max-bundle

To configure a port channel maximum bundle, use the lacp max-bundle command. To return to the default setting, use the no form of this command.

lacp max-bundle max-bundle-number

no lacp mac-bundle max-bundle-number

Syntax Description

Command Default

The default for the port channel max-bundle is 16.

The allowed range is from 1 to 16.

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Note Even if the default value is 16, the number of active members in a port channel is the minimum number of the maximum bundle configured and the maximum active members that are allowed in the portchannel.

Examples

This example shows how to configure port channel maximum bundles:

switch(config)# interface port-channel 1

switch(config-if)# lacp max-bundle 2

Related Commands

lacp min-links

To configure the minimum links for a port channel, use the lacp min-links command. To return to the default setting, use the no form of this command.

lacp min-links number

no lacp min-links number

Syntax Description

Defaults

The default for the port channel minimum link is 1.

The allowed range is from 1 to 16.

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to configure the minimum link for a port channel:

switch(config)# interface port-channel 1

switch(config-if)# lacp min-links 3

Related Commands

lacp port-priority

To set the priority for the physical interfaces for the Link Aggregation Control Protocol (LACP), use the lacp port-priority command. To return the port priority to the default value, use the no form of this command.

lacp port-priority priority

no lacp port-priority

Syntax Description

Defaults

32768

Command Modes

Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Each port configured to use LACP has an LACP port priority. You can accept the default value of 32768 for the LACP port priority, or you can configure a value between 1 and 65535. LACP uses the port priority with the port number to form the port identifier. . The port priority is used to decide which ports should be put into standby mode when there is a hardware limitation that prevents all compatible ports from aggregating or when you have more than eight ports configured for the channel group.

When setting the priority, note that a higher number means a lower priority.

This command does not require a license.

Examples

This example shows how to set the LACP port priority for the interface to 2000:

switch(config-if)# lacp port-priority 2000

Related Commands

lacp rate

To set the rate at which the Link Aggregation Control Protocol (LACP) sends LACP control packets to an LACP-supported interface, use the lacp rate command. To reset the rate to its default, use the no form of this command.

lacp rate {fast | normal}

no lacp rate {fast | normal}

Syntax Description

Defaults

30 seconds

Command Modes

Interface configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

You can change the LACP timer rate to modify the duration of the LACP timeout. Use the lacp rate command to set the rate at which LACP control packets are sent to an LACP-supported interface. You can change the timeout rate from the default rate (30 seconds) to the fast rate (1 second).

This command is supported only on LACP-enabled interfaces.

This command does not require a license.

Examples

This example shows how to configure the LACP fast rate on Ethernet interface 1/4:

switch# configure terminal 

switch (config)# interface ethernet 1/4 

switch(config-if)# lacp rate fast 

Related Commands

lacp system-priority

To set the system priority of the device for the Link Aggregation Control Protocol (LACP), use the lacp system-priority command. To return the system priority to the default value, use the no form of this command.

lacp system-priority priority

no lacp system-priority

Syntax Description

Defaults

32768

Command Modes

Global configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Each device that runs LACP has an LACP system priority value. You can accept the default value of 32768 for this parameter, or you can configure a value between 1 and 65535. LACP uses the system priority with the MAC address to form the system ID and also during negotiation with other systems. The system ID is unique for each virtual device context (VDC).

When setting the priority, note that a higher number means a lower priority.

This command does not require a license.

Examples

This example shows how to set the LACP system priority for the device to 2500:

switch(config)# lacp system-priority 2500

Related Commands

link debounce

To enable the debounce timer for Ethernet ports and specify a debounce time, use the link debounce command. To disable the timer, use the no form of this command.

link debounce [time milliseconds]

no link debounce

Syntax Description

Defaults

Enabled

300 milliseconds

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the link debounce command to enable the debounce timer for Ethernet ports and set it for a specified amount of time in milliseconds. The default debounce time applies when you enter the link debounce command with no arguments.

The range of time is from 1 to 5000 ms. The debounce timer is disabled if you specify the time to 0 ms.

This command does not require a license.

Examples

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

switch(config)# interface ethernet 3/1

switch(config-if)# link debounce time 1000

This example shows how to disable the debounce timer for the Ethernet port 3/1:

switch(config)# interface ethernet 3/1

switch(config-if)# no link debounce

Related Commands

load-interval

To change the sampling interval for statistics collections on interfaces, use the load-interval command. To return to the default sampling interval, use the no form of this command.

load-interval [counter {1 | 2 | 3}] seconds

no load-interval [counter {1 | 2 | 3}] [seconds]

Syntax Description

Defaults

1—30 seconds; 60 seconds for VLAN network interface

2—300 seconds

3—not configured

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the load-interval command to obtain bit-rate and packet-rate statistics for three different durations.

You can set the statistics collection intervals on the following types of interfaces:

•Ethernet interfaces

•Port-channel interfaces

•VLAN network interfaces

You cannot use this command on the management interface or subinterfaces.

This command sets the sampling interval for such statistics as packet rate and bit rate on the specified interface.

This command does not require a license.

Examples

This example shows how to set the three sample intervals for the Ethernet port 3/1:

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

Related Commands

max-ports

To assign a maximum possible number of interfaces that a port profile can inherit, use the max-ports command. To return to the default value, use the no form of this command.

max-ports number

no max-ports number

Syntax Description

Defaults

None

Command Modes

Port-profile configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

You must be in the port-profile configuration mode in order to use this command.

You must enable each specific port profile by using the state-enabled command.

This command does not require a license.

Examples

This example shows how to enter the port-profile configuration mode and to configure the maximum possible number of interfaces that a port profile can inherit:

switch(config)# port-profile type ethernet type test

switch(config-ppm)# max-ports 500

Related Commands

mdix auto

To enable automatic medium-dependent independent crossover (MDIX) detection for the interface, use the mdix auto command. To turn automatic detection off, use the no form of this command.

mdix auto

no mdix

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the mdix auto command to enable automatic MDIX detection for the port. Use the no mdix command to disable MDIX detection for the port.

This command is only available on copper Ethernet ports. To detect the type of connection (crossover or straight) with another copper Ethernet port, enable the MDIX parameter for the local port. Before you begin, MDIX must be enabled on the remote port.

This command does not require a license.

Examples

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

switch(config)# interface ethernet 3/1

switch(config-if)# mdix auto

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

switch(config)# interface ethernet 3/1

switch(config-if)# no mdix

Related Commands

medium

To set the medium mode for an interface, use the medium command. To remove the entry, use the no form of this command.

medium {broadcast | p2p}

no medium {broadcast | p2p}

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

The medium command is used to configure the interface as broadcast or point to point.

This command does not require a license.

Examples

This example shows how to configure the interface for point-to-point medium:

switch(config-if)# medium p2p

mtu

To configure the maximum transmission unit (MTU) size for Layer 2 and Layer 3 Ethernet interfaces, use the mtu command. To return to the default value, use the no form of this command.

mtu size

no mtu

Syntax Description

Defaults

1500 bytes

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the mtu size command to configure the 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).

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 use the system default MTU (1500 bytes).

This command does not require a license.

Examples

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

switch(config)# interface ethernet 3/1

switch(config-if)# mtu 1500

Related Commands

peer-gateway

To configure the device to send virtual port-channel (vPC) packets to the device’s MAC address, use the peer-gateway command. To return to the default value, use the no form of this command.

peer-gateway

no peer-gateway

Syntax Description

This command has no arguments or keywords.

Defaults

None

Command Modes

vpc-domain configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the peer-gateway command to have a vPC peer device act as the gateway even for packets that are sent to the vPC peer device’s MAC address.

This command does not require a license.

Examples

This example shows how to configure the device to use the switch gateway even for the packets that are sent the vPC:

switch(config)# vpc-domain 5

switch(config-vpc-domain)# peer-gateway

Related Commands

peer-keepalive destination

To configure the virtual port-channel (vPC) peer-keepalive link and message between vPC peer devices, use the peer-keepalive destination command.

peer-keepalive destination ipaddress [hold-timeout secs] [interval msecs {timeout secs}[{precedence {prec-value | network | internet | critical | flash-override | flash | immediate | priority | routine}} | {tos {tos-value | max-reliability | max-throughput | min-delay | min-monetary-cost | normal}} | tos-byte tos-byte-value][source ipaddress][udp-port number] [vrf {name | management | vpc-keepalive}]

Syntax Description

Defaults

Peer-keepalive is disabled.

Hold-timeout is 3 seconds.

Interval is 1000 milliseconds.

Timeout is 5 seconds.

Precedence is default, with a level of 6 (internet).

UDP port is 3200.

VRF is management VRF.

Command Modes

vpc-domain configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

You must enable the vPC feature before you can configure the peer-keepalive parameters. The vPC keepalive messages notify the system if one of the vPC peer devices goes down.

You must configure the peer-keepalive messages on each of the vPC peer devices to enable the functionality.

Although the keepalive messages can transmit over any Layer 3 topology, we recommend that you create and configure a separate VRF with Layer 3 ports on each vPC peer device as the source and destination for the vPC keepalive messages. The default ports and VRF for the peer-alive link are the management ports and the management VRF. Do not use the peer link itself for the vPC peer-keepalive messages.

Ensure that both the source and destination IP addresses used for the peer-keepalive messages are unique in your network.

The vPC keepalive messages are IP/UDP messages.

This command accepts only IPv4 addresses.

The device assumes that its vPC peer device is down when the device does not receive any messages from the peer during the timeout period. We recommend that you configure the timeout value to be three times the interval value.

You can configure either the precedence, tos, or tos-byte value to ensure throughput for the vPC peer-keepalive message.

Note We recommend that you create a separate VRF and assign a Layer 3 port on each vPC peer device for the peer-keepalive link.

This command does not require a license.

Examples

This example shows how to configure the IP address of the remote vPC peer device for the fault-tolerant link:

switch(config-vpc-domain)# peer-keepalive destination 172.28.231.85

Related Commands

peer-switch

To enable the virtual port channel (vPC) switch pair to appear as a single Spanning Tree Protocol (STP) root in the Layer 2 topology, use the peer-switch command. To disable the peer switch vPC topology, use the no form of this command.

peer-switch

no peer-switch

Syntax Description

This command has no arguments or keywords.

Defaults

Peer switch Layer 2 topology is disabled.

Command Modes

vPC domain configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

This command does not require a license.

Examples

This example shows how to enable the vPC switch pair to appear as a single STP root in the Layer 2 topology:

switch(config)# vpc domain 5 

switch(config-vpc-domain)# peer-switch 

2010 Apr 28 14:44:44 switch %STP-2-VPC_PEERSWITCH_CONFIG_ENABLED: vPC peer-switch 
configuration is enabled. Please make sure to configure spanning tree "bridge" priority as 
per recommended guidelines to make vPC peer-switch operational. 

Related Commands

port-channel load-balance

To set the load-balancing method among the interfaces in the channel-group bundle, use the port-channel load-balance command. To return the system priority to the default value, use the no form of this command.

port-channel load-balance method [module slot]

no port-channel load-balance [method [module slot]]

Syntax Description

Defaults

Layer 2 packets—src-dst-mac

Layer 3 packets—src-dst-ip

Command Modes

Global configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

When you do not specify a module, you are configuring load balancing for the entire device. When you use the module parameter, you are configuring load balancing for the specified modules

Valid method values are as follows:

•dst-ip—Loads distribution on the destination IP address.

•dst-mac—Loads distribution on the destination MAC address.

•dst-port—Loads distribution on the destination port.

•src-dst-ip—Loads distribution on the source XOR-destination IP address.

•src-dst-mac—Loads distribution on the source XOR-destination MAC address.

•src-dst-port—Loads distribution on the source XOR-destination port.

•src-ip—Loads distribution on the source IP address.

•src-mac—Loads distribution on the source MAC address.

•src-port—Loads distribution on the source port.

Note You cannot configure load balancing using port channels per virtual device context (VDC0. You must be in the default VDC to configure this feature; if you attempt to configure this feature from another VDC, the system returns an error.

Use the module keyword to configure the module independently for port-channeling and load-balancing mode. The remaining module use the current load-balancing method configured for the entire device or the default method if you have not configured a method for the entire device. When you enter the no with the module keyword, the load-balancing method for the specified module takes the current load-balancing method that is in use for the entire device. If you configured a load-balancing method for the entire device, the specified module uses that configured method rather than the default src-dst-ip/src-dst-mac. The per module configuration takes precedence over the load-balancing method configured for the entire device.

You can configure one load-balancing mode for the entire device, a different mode for specified modules, and another mode for other specified modules. The per-module configuration takes precedence over the load-balancing configuration for the entire device.

Use the option that provides the balance criteria with the greatest variety in your configuration. For example, if the traffic on a port channel is going only to a single MAC address and you use the destination MAC address as the basis of port channel load balancing, the port channel always chooses the same link in that port channel; using source addresses or IP addresses might result in better load balancing.

This command does not require a license.

Examples

This example shows how to set the load-balancing method for the entire device to use the source port:

switch(config)# port-channel load-balance src-port

Related Commands

port-profile

To create a port profile and enter the port-profile configuration mode or to enter into the port-profile configuration mode of a previously created port profile, use the port-profile command. To remove the port profile, use the no form of this command.

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

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

Syntax Description

Defaults

None

Command Modes

Interface configuration mode

Port-profile configuration mode

Supported User Roles

network-admin

vdc-admin

Command History

Usage Guidelines

Use the port-profile command to group configuration commands and apply them to several interfaces simultaneously. All interfaces in the range must be the same type. The maximum number of interfaces that can inherit a single port profile is 512.

The port-profile name must be globally unique across types and networks.

Each port profile can be applied only to a specific type of interface; the choices are as follows:

•Ethernet

•VLAN network interface

•Port channel

Note When you choose ethernet 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.

A subset of commands are available under the port-profile configuration mode, depending on which interface type you specify. Layer 3 and CTS commands are not supported by port profiles.

You can configure the following port-profile operations:

•Create port profiles

•Delete port profiles

•Add commands to and delete commands from port profiles

•Inherit port profiles at interfaces

•Enable and disable port profiles

•Inherit between port profiles

•Configure maximum number of ports that a profile can inherit

You inherit the port profile when you attach the port profile to an interface or range of interfaces. The maximum number of interfaces that can inherit a single profile is 512. 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 another port profile, which 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 except for the switchport private-vlan mapping and private-vlan mapping commands, which support only one level of inheritance. See the inherit port-profile command for information about inheriting an additional port profile and assigning port profiles to specified interfaces.

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 default commands on the interface, unless it 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 those 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 entering the new value at the interface configuration level. If you then remove the individual configuration values at the interface configuration level, the interface again uses the values in the port profile again.

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

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 on Session Manager.

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. For example, you can configure a VRF instance without it being applied to the system. If you then delete that VRF and its 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 does not operate on the specified interfaces.

You must enable each specific port profile using the state-enabled command.

This command does not require a license.

Examples

This example shows how to configure, name a port profile, and enter the port-profile configuration mode:

switch(config)# port-profile type ethernet test

Related Commands

rate-mode dedicated

To set the dedicated rate mode for the specified ports, use the rate-mode dedicated command.

rate-mode dedicated

no rate-mode

Syntax Description

This command has no arguments or keywords.

Defaults

Shared rate mode is the default.

Command Modes

Interface configuration mode

Supported User Roles

network-admin
vdc-admin

Command History

Usage Guidelines

Use the rate-mode dedicated command to set the dedicated rate mode for the specified ports.

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.

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

Table 2 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.