- abort (switch profile)
- auto-recovery
- autostate
- bandwidth (interface)
- buffer-delete
- buffer-move
- channel-group (Ethernet)
- cdp enable
- command (switch profile)
- commit (switch profile)
- config sync
- copy running-config startup-config
- default interface
- delay (interface)
- delay restore
- description (interface)
- downlink delay
- dual-active exclude interface-vlan
- errdisable detect cause
- errdisable recovery cause
- encapsulation dot1Q
- feature interface-vlan
- feature nv overlay
- feature tunnel
- feature vn-segment-vlan-based
- feature vpc
- graceful consistency-check
- hardware profile front portmode
- hardware profile portmode
- import interface
- import running-config
- ingress-replication
- interface ethernet
- interface ethernet (Layer 3)
- interface loopback
- interface nve
- interface port-channel
- interface (switch profile)
- interface tunnel
- interface vlan
- ip address dhcp
- ipv6 nd mac-extract
- l2protocol tunnel
- l2protocol tunnel cos
- l2protocol tunnel drop-threshold
- l2protocol tunnel shutdown-threshold
- lacp min-links
- lacp port-priority
- lacp rate fast
- lacp system-priority
- lldp (interface)
- load-interval
- mac-address
- member vni
- no switchport
- port-channel load-balance ethernet
- peer-config-check-bypass
- peer-gateway
- peer-keepalive
- resync-database
- role
- show consistency-checker l3-interface module
- show consistency-checker link-state module
- show consistency-checker membership port-channels
- show interface brief
- show interface capabilities
- show interface counters
- show interface debounce
- show interface ethernet
- show interface loopback
- show interface port-channel
- show interface mac-address
- show interface nve
- show interface private-vlan mapping
- show interface status err-disabled
- show interface switchport
- show interface transceiver
- show interface tunnel
- show lacp
- show module
- show nve interface nve
- show nve peers
- show nve vni
- show nve vxlan-params
- show port-channel capacity
- show port-channel compatibility-parameters
- show port-channel database
- show port-channel load-balance
- show port-channel summary
- show port-channel traffic
- show port-channel usage
- show resource
- show running-config interface
- show running-config switch-profile
- show running-config vpc
- show startup-config interface
- show startup-config switch-profile
- show startup-config vpc
- show switch-profile
- show switch-profile buffer
- show switch-profile peer
- show switch-profile session-history
- show switch-profile status
- show tech-support port-channel
- show tech-support vpc
- show version
- show vpc
- show vpc brief
- show vpc consistency-parameters
- show vpc orphan-ports
- show vpc peer-keepalive
- show vpc role
- show vpc statistics
- shutdown
- speed (Ethernet)
- switch-profile
- switchport block
- switchport dot1q ethertype
- switchport host
- switchport mode
- switchport mode dot1q-tunnel
- switchport trunk allowed vlan
- switchport trunk native vlan
- sync-peers destination
- system default interface-vlan no autostate
- system default switchport
- system-mac
- system-priority
- tunnel destination
- tunnel mode
- tunnel source
- tunnel use-vrf
- udld (configuration mode)
- udld (Ethernet)
- verify
- vn-segment
- vpc
- vpc domain
- vpc peer-link
- vxlan udp port
Interfaces Commands
This chapter describes the Cisco NX-OS interfaces commands available on Cisco Nexus 3000 Series switches.
abort (switch profile)
To discard the current switch profile configuration, use the abort command.
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command when you want to discard the configuration that is imported to a switch profile.
Examples
This example shows how to discard a configuration on a switch profile named s5010 on switch 1 of the peer:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
auto-recovery
To configure the time to restore the virtual port channel (vPC) peer links, use the auto-recovery command. To revert to the default delay value, use the no form of this command.
auto-recovery [ reload-delay delay_value ]
no auto-recovery [ reload-delay delay_value ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to enable the automatic recovery interval for 240 seconds (the default value) in vPC domain 100:
This example shows how to set the automatic recovery delay period for 300 seconds in vPC domain 200:
Related Commands
|
|
|
|---|---|
autostate
To disable switched virtual interfaces (SVIs) default autostate behavior on VLAN interface, use the no autostate command. To reenable default autostate behavior use the autostate command.
Syntax Description
Command Default
Command Modes
Interface configuration mode SVI only
Command History
|
|
|
|---|---|
Usage Guidelines
Use the autostate command to enable or disable autostate behavior per SVI.
Examples
This example shows how to disable default autostate behavior on a VLAN interface:
Related Commands
|
|
|
|---|---|
Displays information about the traffic on the specified VLAN interface. |
bandwidth (interface)
To set the inherited and received bandwidth values for an interface, use the bandwidth command. To restore the default values, use the no form of this command.
bandwidth { kbps | inherit [ kbps ]}
no bandwidth { kbps | inherit [ kbps ]}
Syntax Description
Informational bandwidth in kilobits per second. Valid values are from 1 to 10000000. |
|
(Optional) Specifies that the bandwidth be inherited from the parent interface. |
Command Default
Command Modes
Interface configuration mode
Subinterface configuration mode
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.
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 will inherit the current bandwidth of the main interface. If you configure a new bandwidth on the main interface, all subinterfaces will 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 will inherit the specified bandwidth.
In all cases, if an interface has an explicit bandwidth setting configured, then that interface will use that setting, regardless of whether the bandwidth inheritance setting is in effect.
Examples
This example shows how to configure the bandwidth for a Layer 2 interface:
This example shows how to configure subinterfaces to inherit the bandwidth from the parent routed interface:
Related Commands
|
|
|
|---|---|
buffer-delete
To delete commands from a switch profile buffer, use the buffer-delete command.
buffer-delete { sequence-no | all }
Syntax Description
ID of the command to be deleted. You can use the hyphen (-) to separate a range of IDs; for example, 10-14. |
|
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command if you want to correct the wrong configuration made to the switch profile or you do not want certain configuration commands to be synchronized with the peer after a software upgrade.
Examples
This example shows how to delete buffered commands from the switch profile named s5010 on switch 2 of the peer:
Related Commands
|
|
|
|---|---|
Corrects the order of commands in the switch profile buffer. |
|
Copies the running configuration to the startup configuration. |
|
buffer-move
To change the order of commands in the switch profile buffer, use the buffer-move command.
buffer-move from-sequence-no to-sequence-no
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command if you want to change the order and precedence of the configuration commands in the switch profile buffer.
Examples
This example shows how to change the order of buffered commands for the switch profile named s5010 on switch 2 of the peer:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
channel-group (Ethernet)
To assign and configure a physical interface to an EtherChannel, 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 }]
Syntax Description
Command Default
Command Modes
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 switch automatically removes the specified port from its present channel group and adds it to the specified channel group.
Use the force keyword to force the addition of the interface into 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. An EtherChannel in the on channel mode is a pure EtherChannel and can aggregate a maximum of eight ports. The EtherChannel does not run LACP.
You cannot change the mode for an existing EtherChannel or any of its interfaces if that EtherChannel is not running LACP; the channel mode remains as on. The system returns an error message if you attempt to change the mode.
Use the no form of this command to remove the physical interface from the EtherChannel. When you delete the last physical interface from an EtherChannel, the EtherChannel remains. To delete the EtherChannel completely, use the no form of the interface port-channel command.
The compatibility check includes the following operational attributes:
- Port mode
- Access VLAN
- Trunk native VLAN
- Tagged or untagged
- Allowed VLAN list
- Switched Port Analyzer (SPAN) (cannot be SPAN source or destination port)
- Storm control
Use the show port-channel compatibility-parameters command to see the full list of compatibility checks that Cisco NX-OS uses.
You can only add interfaces configured with the channel mode set to on for static EtherChannels, that is, without a configured aggregation protocol. You can only add interfaces configured with the channel mode as active or passive to EtherChannels 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 EtherChannel.
When the interface joins an EtherChannel, some of its individual parameters are overridden with the values on the EtherChannel, as follows:
- MAC address
- Spanning Tree Protocol (STP)
- Service policy
- Quality of service (QoS)
- Access control lists (ACLs)
Interface parameters, such as the following, remain unaffected when the interface joins or leaves a EtherChannel:
If interfaces are configured for the EtherChannel interface and a member port is removed from the EtherChannel, the configuration of the EtherChannel interface is not propagated to the member ports.
Any configuration changes that you make in any of the compatibility parameters to the EtherChannel interface are propagated to all interfaces within the same channel group as the EtherChannel (for example, configuration changes are also propagated to the physical interfaces that are not part of the EtherChannel but are part of the channel group).
Examples
This example shows how to add an interface to LACP channel group 5 in active mode:
switch(config)# interface ethernet 1/1
switch(config-if)# channel-group 5 mode active
switch(config-if)#
This example shows how to forcefully add an interface to the channel group 5:
switch(config)# interface ethernet 1/1
switch(config-if)# channel-group 5 force
switch(config-if)#
Related Commands
|
|
|
|---|---|
Displays information about the traffic on the specified EtherChannel interface. |
|
cdp enable
To enable the Cisco Discovery Protocol (CDP) on an Ethernet interface, use the cdp enable command. To disable CDP on the interface, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
Examples
This example shows how to enable CDP on an Ethernet interface:
Related Commands
|
|
|
|---|---|
command (switch profile)
To add or modify commands in a switch profile, use any command that is supported in the switch profile. To remove a command from the switch profile, use the no form of the supported command.
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
After you configure a switch profile on each peer, you can add the interface configuration, quality of service (QoS), and virtual port channel (vPC) commands to the switch profile.
Note
In this release of Cisco NX-OS, FCoE commands are not supported on a switch profile.
The commands that you add or modify are stored in the switch profile buffer until you apply them to the switch configuration using the commit command. Alternatively, you may verify the commands in the buffer (using the verify command) before applying them to the switch configuration. After you commit the configuration, you can continue to add commands to, or remove commands from, a switch profile configuration. When you commit the configuration again, the updated commands are verified and applied to the switch profile configuration, and the configuration is synchronized between the peers.
Commands are executed in the same order in which they are buffered. You can delete commands from the switch profile buffer using the buffer-delete command, or change their order of precedence in the switch profile buffer using the buffer-move command.
Examples
This example shows how to add the interface commands to a switch profile named s5010 on switch 1 of the peer:
This example shows how to add commands to the switch profile named s5010 on switch 2 of the peer:
This example shows how to remove commands from the switch profile named s5010 on switch 2 of the peer:
Related Commands
|
|
|
|---|---|
Corrects the order of commands in the switch profile buffer. |
|
Copies the running configuration to the startup configuration. |
|
commit (switch profile)
To commit the commands in the switch profile buffer and save the configuration in the switch, use the commit command.
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to save the switch profile configuration and synchronize the configuration with the peer switch. If the commit fails, you must manually correct the configuration commands and then commit the configuration again.
When you commit a configuration, the following operations are performed to ensure that the configuration is applied uniformly on the peer switch:
- Verifies the commands for mutual exclusion checks (mutex-check) on both switches if the peer switch is reachable; otherwise, the mutex-check is performed locally.
Note A command that is included in a switch profile cannot be configured outside of the switch profile or on a peer switch. Ensure that the new configuration in the switch profile does not conflict with the configurations that may exist outside the switch profile or inside another switch profile. This feature is called mutual exclusion (mutex) check.
- Creates a checkpoint with a rollback infrastructure.
- Applies the configuration on the local switch and the peer switch.
If there is a commit failure on any of the switches, the configuration is rolled back on both switches.
During commit, the configuration revision of the switch profile is used to determine the synchronization of the configuration in the peer switch as follows:
- If the revision number of the local switch profile is the same as the peer, and there is a locally applied configuration that needs to be synchronized, the configuration is synchronized in the peer.
- If the revision number is the same in both switches, and there is no locally applied configuration that needs to be synchronized with the peer, the synchronization session is terminated immediately.
- If the revision number in the local switch does not match that of the peer switch, the configuration is synchronized in the peer.
After you commit a switch profile configuration, you can continue to add or remove commands from the switch profile. When you commit the configuration again, only the updated commands are used for verification and the configuration is then applied to the switch profile and synchronized with the peer switch.
Examples
This example shows how to apply the changes made to the switch profile named s5010 on switch 1 of the peer:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Displays information about the switch profile and the configuration revision. |
|
config sync
To enter the configuration synchronization mode to create switch profiles, use the config sync command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the config sync command on the local and the peer switch that you want to synchronize.
Before you synchronize the configuration on the switches, you must ensure the following:
- Identify the peer switches.
- Enable Cisco Fabric Services (CFS) distribution over IPv4 on the management interface (mgmt0) of the peer switches.
When you use the configuration synchronization feature, the configurations made on one switch is synchronized and made available on the peer switch.
After using the config sync command, you can create or configure switch profiles on the peer switches.
Examples
This example shows how to enable CFS over IPv4 on a switch in peer configuration, and then enter the configuration synchronization mode on the switch:
Note While importing any configuration related to PO, it is required to run the command resync-database.
Related Commands
|
|
|
|---|---|
copy running-config startup-config
To save the running configuration to the startup configuration file so that all current configuration details are available after a reboot, use the copy running-config startup-config command.
copy running-config startup-config
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To view the changes to the configuration that you have made, use the show startup-config command.
Note Once you enter the copy running-config startup-config command, the running and the startup copies of the configuration are identical.
Examples
This example shows how to save the running configuration to the startup configuration:
Related Commands
|
|
|
|---|---|
default interface
To reset the configuration of an interface to the default configuration, use the default interface command.
default interface type interface-number
Syntax Description
Command Default
Command Modes
Command History
|
|
|
Usage Guidelines
Use this command to return an interface to its default state. All the user configuration under the specified interface(s) is deleted upon the successful completion of the command.
When using this command, you delete the configuration of the specified interfaces
Examples
This example shows how to revert to the default configuration of an interface:
Related Commands
|
|
|
|---|---|
Displays the administrative and operational status of a switching (nonrouting) port. |
delay (interface)
To set a delay value for an interface, use the delay command. To restore the default delay value, use the no form of this command.
Syntax Description
Throughput delay in tens of microseconds. The range is from 1 to 16,777,215. |
Command Default
Command Modes
Interface configuration mode
Subinterface configuration mode
Command History
|
|
|
Examples
This example shows how to set a delay of 30,000 microseconds on an interface:
This example shows how to set a delay of 1000 microseconds on a subinterface:
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 revert to the default delay value, use the no form of this command.
Syntax Description
Number of seconds to delay bringing up the restored vPC peer device. The range is from 1 to 3600. |
Command Default
Command Modes
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.
Examples
This example shows how to configure the delay reload time for a vPC link:
This example shows how to remove the reload time configuration for a vPC link:
Related Commands
|
|
|
|---|---|
description (interface)
To add a description to an interface configuration, use the description command. To remove the description, use the no form of this command.
Syntax Description
String description of the interface configuration. This string is limited to 80 characters. |
Command Default
Command Modes
Interface configuration mode
Subinterface configuration mode
Command History
|
|
|
Usage Guidelines
The description command is meant to provide a reminder in the configuration to describe what certain interfaces are used for. The description appears in the output of the following commands such as show interface and show running-config.
Examples
This example shows how to add a description for an interface:
Related Commands
|
|
|
|---|---|
Displays the contents of the currently running configuration file. |
downlink delay
To enable or disable downlink delay and configure the timeout, use the downlink delay command.
downlink delay enable | disable [timeout time-out]
Syntax Description
Specifies the delay in seconds. The default value is 20 seconds. |
Command Default
Command Modes
Command History
|
|
|
Usage Guidelines
You can configure a timer that during reload enables the downlink RJ-45 ports in hardware only after the specified timeout. This allows the uplink SFP+ ports to be operational first. The timer is enabled in the hardware for only those ports that are admin-enable.
Examples
This example shows how to enable a delay and configure the timeout:
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 on the vPC configuration itself, 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
Syntax Description
Range of VLAN interfaces that you want to exclude from shutting down. The allowed VLAN range is from 1 to 3967 and 4048 to 4093. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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:
This example shows how to restore the default configuration on the vPC peer devices if the peer link fails:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
errdisable detect cause
To enable error-disable detection for a specific cause or for all causes, use the errdisable detect cause command in global configuration mode.
errdisable detect cause {all | link-flap | loopback}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
A cause (such as a link-flap or loopback) is the reason for the error-disabled state. When a cause is detected on an interface, the interface is placed in an error-disabled state, an operational state that is similar to a link-down state.
If you set a recovery mechanism for the cause by entering the errdisable recovery global configuration command, the interface is brought out of the error-disabled state and allowed to retry the operation when all causes have timed out.
Examples
This example shows how to enable error-disabled detection for the link-flap error-disabled cause:
Related Commands
|
|
|
|---|---|
errdisable recovery cause
To enable the error-disabled mechanism to recover from a specific cause, use the errdisable recovery cause command in global configuration mode. To disable recovery of an interface from the error-disabled state, use the no form of this command.
errdisable recovery cause { all | bpduguard | link-flap | loopback | pause-rate-limit | failed-port-state | udld }
no errdisable recovery cause { all | bpduguard | link-flap | loopback | pause-rate-limit | failed-port-state | udld }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
A cause (such as all or BDPU guard) is defined as the reason that the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in the error-disabled state, an operational state similar to link-down state.
If you do not enable the recovery for the cause, the interface stays in the error-disabled state until you enter the shutdown and the no shutdown interface configuration commands. If you enable the recovery for a cause, the interface is brought out of the error-disabled state and allowed to retry the operation again after 300 seconds when all the causes have timed out.
Examples
This example shows how to enable the errdisable recovery for the BPDU guard error-disabled cause:
This example shows how to disable the errdisable recovery for the BPDU guard error-disabled cause:
Related Commands
|
|
|
|---|---|
encapsulation dot1Q
To enable IEEE 802.1Q encapsulation of traffic on a specified subinterface, use the encapsulation dot1q command. To disable encapsulation, use the no form of this command.
no encapsulation dot1Q vlan-id
Syntax Description
VLAN to set when the interface is in access mode; valid values are from 1 to 4093, except for the VLANs reserved for internal switch use. |
Command Default
Command Modes
Subinterface configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
IEEE 802.1Q encapsulation is configurable on Ethernet and EtherChannel 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.
Note This command is not applicable to loopback interfaces.
This command does not require a license but if you want to enable Layer 3 interfaces, you must install the LAN Base Services license.
Examples
This example shows how to enable dot1Q encapsulation on a subinterface for VLAN 30:
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must use the feature interface-vlan command before you can create VLAN interfaces.
Examples
This example shows how to enable the interface VLAN feature:
Related Commands
|
|
|
|---|---|
feature nv overlay
To enable the VXLAN feature, use the feature nv overlay command. To disable the VXLAN feature, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must use the feature nv overlay command before you can enable VLAN to vn-segment mapping.
Examples
This example shows how to enable the interface VLAN feature:
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must use the feature tunnel command before you can create tunnel interfaces.
Examples
This example shows how to enable the interface tunnel feature:
Related Commands
|
|
|
|---|---|
feature vn-segment-vlan-based
To enable VLAN to vn-segment mapping, use the feature vn-segment-vlan-based command. To disable VLAN to vn-segment mapping, use the no form of this command.
no feature vn-segment-vlan-based
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must use the feature nv overlay command before you can enable the VLAN to vn-segment mapping feature.
Examples
This example shows how to enable VLAN to vn-segment mapping:
Related Commands
|
|
|
|---|---|
feature vpc
|
|
|
|---|---|
To enable a virtual port channel (vPC), which allows links that are physically connected to two different Cisco Nexus 3000 Series devices to appear as a single port channel to a third device, use the feature vpc command. To disable vPC on the switch, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
In a vPC configuration, the third device can be a Cisco Nexus 2000 Series Fabric Extender, switch, server, or any other networking device.
Examples
This example shows how to enable vPC on the switch:
Related Commands
|
|
|
|---|---|
graceful consistency-check
To enable the Graceful Type-1 Consistency feature in a virtual port channel (vPC) domain, use the graceful consistency-check command. To disable the Graceful Type-1 Consistency feature, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to enable the Graceful Type-1 Consistency feature in vPC domain 100:
This example shows how to disable the Graceful Type-1 Consistency feature in vPC domain 100:
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the vPC feature is not enabled, the system displays an error when you enter this command. |
hardware profile front portmode
To switch between using the first Quad small form-factor pluggable (QSFP) port and Small form-factor pluggable (SFP+) ports 1 to 4, use the hardware profile front portmode command. To restore the default QSFP port mode, use the no form of this command.
hardware profile front portmode qsfp | sfp-plus
no hardware profile front portmode
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can use this command only on Cisco Nexus 3132 switches. Use this comand only when the ports are in the 10-GbE mode. If the first QSFP port speed is 40 Gbps, this command will run, but the SFP+ ports will not become active until after the speed is changed to 10 Gbps.
Examples
This example shows how to activate the SFP+ ports:
This example shows how to make the QSFP port active:
Related Commands
|
|
|
|---|---|
hardware profile portmode
To configure a Quad small form-factor pluggable (QSFP+) port, use the hardware profile portmode command. To restore the defaults, use the no form of this command.
Note To change the port naming convention from the default 3-tuple mode to 2-tuple mode, use the 2-tuple option. To revert back to the default use the hardware profile portmode command without the 2-tuple option. When you break out a 40-Gigabit Ethernet port into 10-Gigabit Ethernet ports, the resulting ports are numbered using a 3-tuple naming convention. The 2-tuple naming convention is not applicable for these breakout ports.
hardware profile portmode port-mode
Syntax Description
Command Default
The Cisco Nexus 3016 switch—16x40G
The Cisco Nexus 3064 switch—64x10G
The Cisco Nexus 3132 switch—Fixed32x40g
The Cisco Nexus 3172 switch—48x10g+breakout6x40g
Command Modes
Command History
|
|
|
|---|---|
Added 48x10g+breakout6x40g, 48x10g+6x40g, and 72x10g support. |
|
Usage Guidelines
We recommend that you follow this step-by-step procedure to change port mode on a Cisco NX-OS device:
1. Copy the running configuration to bootflash by using the copy running-config command. You can use this file to configure your device later.
2. Remove all the interface configurations by using the write erase command.
3. Reload the Cisco Nexus 3000 Series switch software by using the reload command.
4. Use the hardware profile portmode command to change port mode.
5. Copy the running configuration and startup configuration by using the copy running-config startup-config command.
6. Reload the Cisco Nexus 3000 Series switch software again by using the reload command.
7. Manually apply all the interface configuration. You can refer to the configuration file that you saved on the device earlier.
Note The interface numbering changes if the ports are changed from 40G mode to 4x10G mode or vice-versa.
Examples
This example shows how to change the port mode to 48x10g+4x40g for QSFP+ ports:
WARNING: This command will reboot the system
This example shows how to change the port mode to 48x10g+4x40g for QSFP+ ports and verify the changes:
This example shows how to restore the default port mode for QSFP+ ports:
Related Commands
|
|
|
|---|---|
import interface
To import an interface configuration to a switch profile, use the import interface command.
import interface { ethernet slot / port | port-channel channel-no }
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
When no option is specified with the import command, an empty switch profile is created. You can then selectively add the configuration that is needed to be synchronized with the peer switch.
You can import a switch profile based on the set of commands that you want to import. The following three ways can be used to import commands that were added using the configuration terminal mode:
1. Add selected commands to the switch profile.
2. Add supported commands that were specified for an interface.
3. Add supported system-level commands.
When you import commands to a switch profile, the switch profile buffer must be empty.
Use the commit command to complete the import process and move the configuration into the switch profile. Because configuration changes are not supported during the import process, if new commands are added before entering the commit command, the switch profile remains unsaved and the switch remains in the switch profile import mode (config-sync-sp-import). You can remove the added commands or use the abort command to stop the import. Unsaved configurations are lost if the process is aborted. New commands can be added to the switch profile after the import is complete.
Examples
This example shows how to import the Ethernet interface configuration to a switch profile named s5010 on switch 1 of the peer:
This example shows how to create an empty switch profile named sp100 on switch 1 of the peer and then add the configuration commands:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
import running-config
To import the running configuration to a switch profile, use the import running-config command.
import running-config [ exclude interface ethernet ]
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
The import running-config exclude interface ethernet command discards all physical interface commands in the running configuration during the import operation.
When no option is specified with the import command, an empty switch profile is created. You can then selectively add the configuration that is needed to be synchronized with the peer switch.
You can import a switch profile based on the set of commands that you want to import. The following three ways can be used to import commands that were added using the configuration terminal mode:
1. Add selected commands to the switch profile.
2. Add supported commands that were specified for an interface.
3. Add supported system-level commands.
When you import commands to a switch profile, the switch profile buffer must be empty.
Use the commit command to complete the import process and move the configuration into the switch profile. Because configuration changes are not supported during the import process, if new commands are added before entering the commit command, the switch profile remains unsaved and the switch remains in the switch profile import mode (config-sync-sp-import). You can remove the added commands or use the abort command to stop the import. Unsaved configurations are lost if the process is aborted. New commands can be added to the switch profile after the import is complete.
Examples
This example shows how to import the running configuration to a switch profile named s5010 on switch 1 of the peer:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
ingress-replication
To enable ingress replication for the VXLAN VNI to the specified unicast address, use the ingress-replication command.
ingress-replication ip-address
Syntax Description
Command Default
Command Modes
Command History
|
|
|
Examples
This example shows how to map a VNI to an NVE interface and create a unicast tunnel:
switch(config-if-nve)# member vni 5001
switch(config-if-nve-vni)# ingress-replication 111.1.1.1
Related Commands
|
|
|
|---|---|
interface ethernet
To enter interface configuration mode for an Ethernet IEEE 802.3 interface, use the interface ethernet command.
interface ethernet slot / port
Syntax Description
Port number within a particular slot. The port number is from 1 to 128. |
Command Default
Command Modes
Command History
|
|
|
Examples
This example shows how to enter configuration mode for Ethernet interface 1/4:
switch(config)# interface ethernet 1/4
switch(config-if)#
Related Commands
|
|
|
|---|---|
Displays various parameters of an Ethernet IEEE 802.3 interface. |
|
interface ethernet (Layer 3)
To configure a Layer 3 Ethernet IEEE 802.3 routed interface, use the interface ethernet command.
interface ethernet slot / port [. subintf-port-no ]
Syntax Description
Port number within a particular slot. The port number is from 1 to 128. |
|
(Optional) Port number for the subinterface. The range is from 1 to 48. |
Command Default
Command Modes
Global configuration mode
Interface configuration mode
Command History
|
|
|
Usage Guidelines
You must use the no switchport command in the interface configuration mode to configure the interface as a Layer 3 routed interface. When you configure the interface as a Layer 3 interface, all Layer 2 specific configurations on this interface are deleted.
Use the switchport command to convert a Layer 3 interface into a Layer 2 interface. When you configure the interface as a Layer 2 interface, all Layer 3 specific configurations on this interface are deleted.
Examples
This example shows how to enter configuration mode for a Layer 3 Ethernet interface 1/5:
switch(config)# interface ethernet 1/5
switch(config-if)# no switchport
switch(config-if)# ip address 10.1.1.1/24
switch(config-if)#
This example shows how to configure a Layer 3 subinterface for Ethernet interface 1/5 in the global configuration mode:
switch(config)# interface ethernet 1/5.2
switch(config-if)# no switchport
switch(config-subif)# ip address 10.1.1.1/24
switch(config-subif)#
This example shows how to configure a Layer 3 subinterface in interface configuration mode:
switch(config)# interface ethernet 1/5
switch(config-if)# no switchport
switch(config-if)# interface ethernet 1/5.1
switch(config-subif)# ip address 10.1.1.1/24
switch(config-subif)#
This example shows how to convert a Layer 3 interface to a Layer 2 interface:
switch(config)# interface ethernet 1/5
switch(config-if)# no switchport
switch(config-if)# ip address 10.1.1.1/24
switch(config-if)# switchport
switch(config-if)#
Related Commands
|
|
|
|---|---|
Displays various parameters of an Ethernet IEEE 802.3 interface. |
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.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
Usage Guidelines
Use the interface loopback command to create or modify loopback interfaces.
From the loopback interface configuration mode, the following parameters are available:
- description —Provides a description of the purpose of the interface.
- ip —Configures IP features, such as the IP address for the interface, Address Resolution Protocol (ARP) attributes, load balancing, or Unicast Reverse Path Forwarding (RPF).
- logging —Configures logging of events.
- shutdown —Shuts down traffic on the interface.
Examples
This example shows how to create a loopback interface:
Related Commands
|
|
|
|---|---|
Displays information about the traffic on the specified loopback interface. |
interface nve
To create an NVE interface and enter the NVE interface configuration mode, use the interface nve command. To remove an NVE interface, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
Usage Guidelines
An NVE interface is the overlay interface that terminates VXLAN tunnels. Only 1 NVE interface can be configured on a switch.
Examples
This example shows how to create an NVE interface:
Related Commands
|
|
|
|---|---|
interface port-channel
To create an EtherChannel interface and enter interface configuration mode, use the interface port-channel command. To remove an EtherChannel interface, use the no form of this command.
interface port-channel channel-number [. subintf-channel-no ]
no interface port-channel channel-number [. subintf-channel-no ]
Syntax Description
Channel number that is assigned to this EtherChannel logical interface. The range is from 1 to 4096. |
|
(Optional) Port number of the EtherChannel subinterface. The range is from 1 to 4093. |
Command Default
Command Modes
Global configuration mode
Interface configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
A port can belong to only one channel group.
When you use the interface port-channel command for Layer 2 interfaces, follow these guidelines:
- If you are using the Cisco Discovery Protocol (CDP), you must configure it only on the physical interface and not on the EtherChannel interface.
- The MAC address of the EtherChannel 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.
You must use the no switchport command in the interface configuration mode to configure the EtherChannel interface as a Layer 3 interface. When you configure the interface as a Layer 3 interface, all Layer 2 specific configurations on this interface are deleted.
Use the switchport command to convert a Layer 3 EtherChannel interface into a Layer 2 interface. When you configure the interface as a Layer 2 interface, all Layer 3 specific configurations on this interface are deleted.
You can configure one or more subinterfaces on a port channel made from routed interfaces.
Examples
This example shows how to create an EtherChannel group interface with channel-group number 50:
This example shows how to create a Layer 3 EtherChannel group interface with channel-group number 10:
This example shows how to configure a Layer 3 EtherChannel subinterface with channel-group number 1 in interface configuration mode:
This example shows how to configure a Layer 3 EtherChannel subinterface with channel-group number 20.1 in global configuration mode:
Related Commands
interface (switch profile)
To configure interfaces on a switch profile, use the interface command. To remove the interface configuration, use the no form of this command.
interface { ethernet slot / port | port-channel channel-no }
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
A switch profile configured for an interface type can be applied only to that type of interface. For example, a switch profile created for Ethernet interfaces must be attached onto an Ethernet interface.
Examples
This example shows how to configure an Ethernet interface in a switch profile:
This example shows how to remove the Ethernet interface configuration from a switch profile:
Related Commands
|
|
|
|---|---|
Displays information about the switch profile and the configuration revision. |
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.
Syntax Description
Identifying interface number. The range is from 0 to 4095.
Note |
Defaults
Command Modes
Global configuration mode
Interface configuration mode
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.
Examples
This example shows how to create a tunnel interface:
switch(config)# interface tunnel 50
switch(config-if)#
Related Commands
|
|
|
|---|---|
Displays information about the traffic on the specified tunnel interface. |
interface vlan
To disable the 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.
Note Beginning in Release 7.0(3)I2(1), SVIs are not removed from the Layer 3 interface table after entering no interface vlan. Remove the VLAN itself to remove the SVI.
VLAN to set when the interface is in access mode; valid values are from 1 to 4094, except for the VLANs reserved for the internal switch use. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Before you use this command, enable the interface-vlan feature by using the feature interface-vlan command.
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 IEEE 802.1Q-encapsulated trunk or the VLAN ID that is configured for an access port.
Examples
This example shows how to create a VLAN interface for VLAN 50:
Related Commands
|
|
|
|---|---|
Displays information about the traffic on the specified VLAN interface. |
ip address dhcp
To acquire an IP address on an interface from the DHCP, use the ip address dhcp command in interface configuration mode. To remove any address that was acquired, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The ip | ipv6 address dhcp command allows any interface to dynamically learn its IPv4 or IPv6 address by using the DHCP protocol.
Examples
This example shows how to request the DHCP server for an IP address:
This example shows how to configure an IPv6 address of a DHCP client on a management interface:
ipv6 nd mac-extract
To extract the next-hop MAC address embedded in a next-hop IPv6 address, use the ipv6 nd mac-extract command in interface configuration mode. To disable this function, use the no form of this command.
ipv6 nd mac-extract [exclude nud-phase]
no ipv6 nd mac-extract [exclude nud-phase]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Beginning with Cisco NX-OS Release 6.0(2)U4(1), BGP allows an IPv4 prefix to be carried over an IPv6 next-hop. The IPv6 next-hop is leveraged to remove neighbor discovery (ND) related traffic from the network. To do this, the MAC address is embedded in the IPv6 address. Such an address is called a MAC Embedded IPv6 (MEv6) address. The router extracts the MAC address directly from the MEv6 address instead of going through ND. Local interface and next-hop MAC addresses are extracted from the IPv6 addresses.
On MEv6-enabled IPv6 interfaces, the same MEv6 extracted MAC address is used for IPv4 traffic as well.
Note MEv6 is supported on all Layer 3 capable interfaces except SVIs.
Examples
This example shows how to configure a MAC-embedded IPv6 address with ND mac-extract enabled:
This example shows how to configure a MAC-embedded IPv6 address with ND mac-extract (excluding NUD phase) enabled:
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
(Optional) Enables Cisco Discovery Protocol (CDP) tunneling. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to enable Layer 2 protocol tunneling:
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
Syntax Description
CoS value. The range is from 0 to 7. The default value is 5. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to specify a global CoS value on all Layer 2 protocol tunneling interfaces:
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
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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:
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
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When the number of packets is exceeded, the port is put in error-disabled state.
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:
Related Commands
|
|
|
|---|---|
lacp min-links
To configure port channel min-links and enter the interface configuration mode, use the lacp min-links command. To remove the port channel min-links configuration, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
The min-link feature works only with the Link Aggregation Control Protocol (LACP) port channels.
Examples
This example shows how to configure port channel min-links and enter the interface configuration mode:
This example shows how to remove the port channel min-links configuration:
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.
Syntax Description
Priority for the physical interfaces. The range of valid numbers is from 1 to 65535. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Each port configured to use LACP has an LACP port priority. You can configure a value between 1 and 65535. LACP uses the port priority in combination with the port number to form the port identifier. The port priority is used 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.
Note When setting the priority, note that a higher number means a lower priority.
Examples
This example shows how to set the LACP port priority for the interface to 2000:
Related Commands
|
|
|
|---|---|
lacp rate fast
To configure the rate at which control packets are sent by the Link Aggregation Control Protocol (LACP), use the lacp rate fast command. To restore the rate to 30 seconds, use the no form of this command or the lacp rate normal command.
Note Beginning with release 7.0(3)I2(1), lacp rate fast is allowed only with member interfaces in an admin DOWN state.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must enable LACP before using this command.
The LACP rate fast feature is used to set the rate (once every second) at which the LACP control packets are sent to an LACP-supported interface. The normal rate at which LACP packets are sent is 30 seconds.
Examples
This example shows how to configure the LACP fast rate feature on a specified Ethernet interface:
This example shows how to remove the LACP fast rate configuration from a specified Ethernet interface:
Related Commands
|
|
|
|---|---|
lacp system-priority
To set the system priority of the switch 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.
Syntax Description
Priority for the physical interfaces. The range of valid numbers is from 1 to 65535. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Each device that runs LACP has an LACP system priority value. 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.
When setting the priority, note that a higher number means a lower priority.
Examples
This example shows how to set the LACP system priority for the device to 2500:
Related Commands
|
|
|
|---|---|
lldp (interface)
To enable the reception, or transmission, of Link Layer Discovery Protocol (LLDP) packets on an interface, use the lldp command. To disable the reception or transmission of LLDP packets, use the no form of this command.
no lldp { receive | transmit }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Note LLDP, which is a neighbor discovery protocol that is used for network devices to advertise information about themselves to other devices on the network, is enabled on the switch by default.
Examples
This example shows how to set an interface to transmit LLDP packets:
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 seconds | counter {1 | 2 | 3} seconds
no load-interval seconds | counter {1 | 2 | 3} seconds
Syntax Description
Specifies the interval between sampling statistics on the interface. The range is from 5 seconds to 300 seconds. |
|
Specifies the counter number configured for this load interval. |
Command Default
Command Modes
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:
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.
Examples
This example shows how to set the three sample intervals for the Ethernet port 1/3:
mac-address
To enable the reception, or transmission, of Link Layer Discovery Protocol (LLDP) packets on an interface, use the lldp command. To disable the reception or transmission of LLDP packets, use the no form of this command.
mac-address static router MAC address
no mac-address static router MAC address
Syntax Description
Specifies the new MAC address of the Layer 3 interface. You can enter the MAC address in any one of the four supported formats: |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can configure MAC addresses on SVI, Layer 3 interfaces, port channels, Layer 3 subinterfaces, and tunnel interfaces. You can also configure static MAC addresses on a range of ports and port channels. However, all ports must be in Layer 3. Even if one port in the range of ports is in Layer 2, the command is rejected and an error message appears.
Examples
This example shows how to configure an interface MAC address:
Related Commands
|
|
|
|---|---|
member vni
To map VXLAN VNIs to the NVE interface, use the member vni command.
member vni {vnid | vnid mcast-group multicast-group-addr | vnid- range mcast-group start-addr [end-addr]}
Syntax Description
Specifies the range of VXLAN VNIs to be mapped to the NVE interface. |
|
(Optional) Specifies the ending IP address of the multicast group. |
Command Default
Command Modes
NVE interface configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
Ensure the following before mapping VXLAN VNIs to the NVE interface:
Examples
The following example shows how to map a VNI to an NVE interface and assign it to a multicast group:
The following example shows how to map a VNI to an NVE interface and create a unicast tunnel:
Related Commands
|
|
|
|---|---|
Enables ingress-replication for the VNI to the specified unicast address. |
no switchport
To configure the interface as a Layer 3 Ethernet interface, use the no switchport command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can configure any Ethernet port as a routed interface. When you configure an interface as a Layer 3 interface, any configuration specific to Layer 2 on this interface is deleted.
If you want to configure a Layer 3 interface for Layer 2, enter the switchport command. Then, if you change a Layer 2 interface to a routed interface, enter the no switchport command.
This command requires the LAN Base Services license.
Note Beginning in 7.0(3)I2(1), this command gets an error on breakout interface.
Examples
This example shows how to enable an interface as a Layer 3 routed interface:
This example shows how to configure a Layer 3 interface as a Layer 2 interface:
Related Commands
|
|
|
|---|---|
Saves the running configuration to the startup configuration file. |
|
port-channel load-balance ethernet
To configure the load-balancing method among the interfaces in the channel-group bundle, use the port-channel load-balance ethernet command. To return the system priority to the default value, use the no form of this command.
port-channel load-balance ethernet method hash
no port-channel load-balance ethernet [ method ] [hash]
Syntax Description
Command Default
Loads distribution on the source and destination MAC address.
Command Modes
Global configuration mode
Switch profile configuration mode
Command History
|
|
|
|---|---|
Support for destination-ip-gre, source-destination-ip-gre, and source-ip -gre was introduced. |
|
Usage Guidelines
The valid load-balancing method values are as follows:
- destination-ip —Loads distribution on the destination IP address.
- destination-ip-gre —Loads distribution on the destination IP address using the NVGRE key.
- destination-mac —Loads distribution on the destination MAC address.
- destination-port —Loads distribution on the destination port.
- source-destination-ip —Loads distribution on the source and destination IP address.
- source-destination-ip-gre —Loads distribution on the source and destination IP address using the NVGRE key.
- source-destination-mac —Loads distribution on the source and destination MAC address.
- source-destination-port —Loads distribution on the source and destination port.
- source-ip —Loads distribution on the source IP address.
- source-ip -gre—Loads distribution on the source IP address using the NVGRE key.
- source-mac —Loads distribution on the source MAC address.
- source-port —Loads distribution on the source port.
Use the option that provides the balance criteria with the greatest variety in your configuration. For example, if the traffic on an EtherChannel is going only to a single MAC address and you use the destination MAC address as the basis of EtherChannel load balancing, the EtherChannel always chooses the same link in that EtherChannel; using source addresses or IP addresses might result in better load balancing. When NVGRE traffic is forwarded over a port channel or an Equal Cost Multipath (ECMP), use the source or destination addresses with the NVGRE key.
The load-balancing methods that support symmetric hashing are as follows:
Examples
This example shows how to set the load-balancing method to use the source IP:
switch(config)# port-channel load-balance ethernet source-ip
This example shows how to set the load-balancing method to use the destination IP in a switch profile:
This example shows how to configure symmetric hashing for port channels:
Related Commands
|
|
|
|---|---|
Displays information about the switch profile and the configuration revision. |
|
peer-config-check-bypass
To ignore type checks on the primary vPC device when the multichassis EtherChannel trunk (MCT) is down, use the peer-config-check-bypass command. To stop ignoring type checks, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The peer link, also known as the multichassis EtherChannel trunk (MCT), connects the vPC peer switches. The peer link is always forwarding. The bridge protocol data units (BPDUs) or Link Aggregation Control Protocol (LACP) packets that are received by the secondary vPC peer on a vPC port are forwarded to the primary vPC peer through the peer link for processing.
The peer link is used to synchronize the MAC addresses of the vPC peer switches to provide the necessary transport for multicast traffic. It is also used for forwarding traffic that originates at, or is destined for, orphan ports (that is, a non-vPC port).
Examples
This example shows how to configure the primary vPC device to ignore type checks when the MCT is down:
This example shows how to stop ignoring type checks when the MCT is down:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Displays information about the configuration for the keepalive messages. |
peer-gateway
To enable Layer 3 forwarding for packets destined to the gateway MAC address of the virtual Port Channel (vPC), use the peer-gateway command. To disable Layer 3 forwarding packets, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The vPC peer-gateway functionality allows a vPC switch to act as the active gateway for packets that are addressed to the router MAC address of the vPC peer. This feature enables local forwarding of such packets without the need to cross the vPC peer-link. In this scenario, the feature optimizes use of the peer-link and avoids potential traffic loss.
You must configure the peer-gateway functionality on both vPC peer switches.
Examples
This example shows how to enable the vPC peer gateway:
This example shows how to disable the vPC peer gateway:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
peer-keepalive
To configure the IPv4 address for the remote end of the vPC peer keepalive link that carries the keepalive messages, use the peer-keepalive command. To disassociate the peer keepalive link, use the no form of this command.
peer-keepalive destination ipv4_address [ hold-timeout holdtime_seconds | interval mseconds { timeout seconds } | precedence { prec_value | critical | flash | flash-override | immediate | internet | network | priority | routine } | source ipv4_address | tos { tos_value | max-reliability | max-throughput | min-delay | min-monetary-cost | normal } | tos-byte tos_byte_value | udp-port udp_port | vrf { vrf_name | management }]
no peer-keepalive destination ipv4_address [ hold-timeout holdtime_seconds | interval mseconds { timeout seconds } | precedence { prec_value | critical | flash | flash-override | immediate | internet | network | priority | routine } | source ipv4_address | tos { tos_value | max-reliability | max-throughput | min-delay | min-monetary-cost | normal } | tos-byte tos_byte_value | udp-port udp_port | vrf { vrf_name | management }]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must configure the vPC peer-keepalive link before the system can form the vPC peer link. Ensure that both the source and destination IP addresses used for the peer-keepalive message are unique in your network and these IP addresses are reachable from the VRF associated with the vPC peer-keepalive link.
The Cisco NX-OS software uses the peer-keepalive link between the vPC peers to transmit periodic, configurable keepalive messages. You must have Layer 3 connectivity between the peer devices to transmit these messages. The system cannot bring up the vPC peer link unless the peer-keepalive link is already up and running.
Note We recommend that you configure a separate VRF instance and put a Layer 3 port from each vPC peer device into that VRF for the vPC peer-keepalive link. Do not use the peer link itself to send vPC peer-keepalive messages.
Examples
This example shows how to set up the peer keepalive link connection between the primary and secondary vPC device:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Displays information about the configuration for the keepalive messages. |
resync-database
To resynchronize the switch profile databases, use the resync-database command.
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Examples
This example shows how to resynchronize the switch profile databases:
Related Commands
|
|
|
|---|---|
role
To manually assign a primary or secondary role to a virtual Port Channel (vPC) device, use the role command. To restore the default role priority, use the no form of this command.
Syntax Description
Specifies the priority to define primary or secondary roles in the vPC configuration. |
|
Priority value for the vPC device. The range is from 1 to 65535. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
By default, the Cisco NX-OS software elects a primary and secondary vPC peer device after you configure the vPC domain and both sides of the vPC peer link. However, you may want to elect a specific vPC peer device as the primary device for the vPC. Then, you would manually configure the role value for the vPC peer device that you want as the primary device to be lower than the other vPC peer device.
vPC does not support role preemption. If the primary vPC peer device fails, the secondary vPC peer device takes over to become operationally the vPC primary device. However, the original operational roles are not restored if the formerly primary vPC comes up again.
Examples
This example shows how to configure the role priority of a vPC device:
This example shows how to restore the default role priority of a vPC device:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
show consistency-checker l3-interface module
To trigger the Layer 3 Interface consistency checker for interfaces in a module and display the results, use the show consistency-checker l3-interface module command.
show consistency-checker l3-interface module slot
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command performs a consistency check only on the physical interfaces in a module.
Examples
This example shows how to trigger the Layer 3 Interface consistency checker for a module and display the results:
Related Commands
|
|
|
|---|---|
Triggers the consistency checker on link states in a module and displays the results. |
|
Triggers the consistency checker on all members of a port channel and displays the results. |
show consistency-checker link-state module
To trigger the Link State consistency checker for link states in a module and display the results, use the show consistency-checker link-state module command.
show consistency-checker link-state module slot
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to trigger the Link State consistency checker for a module and display the results:
Related Commands
show consistency-checker membership port-channels
To trigger the Port Channel membership consistency checker for all the members of a port channel and display the results, use the show consistency-checker membership port-channels command.
show consistency-checker membership port-channels
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to trigger the Port Channel membership consistency checker for all members of a port channel and display the results:
Related Commands
|
|
|
|---|---|
Triggers the consistency checker on all interfaces in a module and displays the results. |
|
Triggers the consistency checker on link states in a module and displays the results. |
show interface brief
To display a brief summary of the interface configuration information, use the show interface brief command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the summary configuration information of the all interfaces:
Related Commands
|
|
|
|---|---|
show interface capabilities
To display detailed information about the capabilities of an interface, use the show interface capabilities command.
show interface [ ethernet slot / port ] capabilities
Syntax Description
(Optional) Specifies an Ethernet interface slot number and port number. The slot number is from 1 to 255, and the port number is from 1 to 128. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can use the show interface capabilities command only for physical interfaces.
Examples
This example shows how to display the interface capabilities:
This example shows how to display the interface capabilities for a specific interface:
Related Commands
|
|
|
|---|---|
show interface counters
To display a brief summary of all the counters on all interfaces, use the show interface counters command.
show interface counters [brief | detailed | errors | fc | module | snmp | storm-control]
Syntax Description
(Optional) Displays input and output rates for all interfaces. |
|
(Optional) Displays information about the storm-control counters. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the input and output rates for all interfaces:
This example shows how to display the storm-control counters for all interfaces:
Related Commands
|
|
|
|---|---|
show interface debounce
To display the debounce time information for all interfaces, use the show interface debounce command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the debounce status of all interfaces:
Related Commands
|
|
|
|---|---|
show interface ethernet
To display information about the interface configuration, use the show interface ethernet command.
show interface ethernet slot / port [. subintf-port-no ] [ brief | counters { brief [load-interval-id] | detailed | errors | snmp | storm-control | trunk} | description | status | switchport | transceiver [ details ]]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the detailed configuration of the specified interface:
This example shows how to display the counters configured on a specified interface:
This example shows how to display the storm-control counters for a specific Ethernet interface:
This example shows how to display the switchport information for a specific interface:
This example shows how to display the operational status for a specific interface:
This example shows how to display the calibration information about the transceivers connected to a specified Ethernet interface:
Related Commandsswitch#
|
|
|
|---|---|
show interface loopback
To display information about the loopback interface, use the show interface loopback command.
show interface loopback lo-number [ brief | description ]
Syntax Description
(Optional) Displays a brief summary of the loopback interface information. |
|
(Optional) Displays the description provided for the loopback interface. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the configuration information for a specific loopback interface:
Table 1 describes the significant fields shown in the display.
This example shows how to display the brief information for a specific loopback interface:
Related Commands
|
|
|
|---|---|
show interface port-channel
To display the information about an EtherChannel interface configuration, use the show interface port-channel command.
show interface port-channel number [. subinterface-number ] [ brief | counters {brief | detailed | errors | snmp | storm-control | trunk} | description | status ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the configuration information of a specified EtherChannel interface:
This example shows how to display the storm-control counters for a specific port-channel:
Related Commands
|
|
|
|---|---|
show interface mac-address
To display the information about the MAC address, use the show interface mac-address command.
show interface [ type slot / port | portchannel-no ] mac-address
Syntax Description
Command Default
Command Modes
Command History
|
|
|
Usage Guidelines
If you do not specify an interface, the system displays all the MAC addresses.
Examples
This example shows how to display the information on MAC addresses for the entire switch:
This example shows how to display the MAC address information for a specific port channel:
Related Commands
|
|
|
|---|---|
Adds static entries to the MAC address table or configures a static MAC address with IGMP snooping disabled for that address. |
|
show interface nve
To display all the counters of an NVE interface, use the show interface nve command.
show interface nve id counters
Syntax Description
Specifies the NVE ID. You can configure only 1 NVE interface on a switch. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the counters of an NVE interface:
Related Commands
|
|
|
|---|---|
show interface private-vlan mapping
To display information about private VLAN mapping for primary VLAN interfaces, use the show interface private-vlan mapping command.
show interface private-vlan mapping
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Before you can configure private VLANs, you must enable them by using the feature private-vlan command. The commands for configuring private VLANs are not visible until you enable private VLANs.
This command displays the mapping information between the primary and secondary VLANs that allows both VLANs to share the VLAN interface of the primary VLAN.
Examples
This example shows how to display information about primary and secondary private VLAN mapping:
Related Commands
|
|
|
|---|---|
Displays information about the ports, including those in private VLANs. |
|
Defines the private VLAN association for a promiscuous port. |
show interface status err-disabled
To display the error disabled state of interfaces, use the show interface status err-disabled command.
show interface status err-disabled
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the error disabled state of interfaces:
Related Commands
|
|
|
|---|---|
show interface switchport
To display information about all the switch port interfaces, use the show interface switchport command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to display information for all Ethernet interfaces:
Related Commands
|
|
|
|---|---|
show interface transceiver
To display the information about the transceivers connected to a specific interface, use the show interface transceiver command.
show interface [ ethernet slot / port ] transceiver [ details ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can use the show interface transceiver command only for physical interfaces.
Examples
This example shows how to display the transceivers for all Ethernet interfaces:
This example shows how to display the transceivers connected to a specified Ethernet interface:
This example shows how to display the detailed information about the transceivers connected to a specified Ethernet interface:
Related Commands
|
|
|
|---|---|
Displays detailed information about the capabilities of an interface. |
show interface tunnel
To display information about the tunnel interfaces, use the show interface tunnel command.
Syntax Description
Number of the tunnel interface that you want to display information for. The range is from 0 to 4095. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to display information about tunnel interfaces:
Related Commands
|
|
|
|---|---|
show lacp
To display Link Aggregation Control Protocol (LACP) information, use the show lacp command.
show lacp { counters | interface ethernet slot / port | neighbor [ interface port-channel number ] | port-channel [ interface port-channel number ] | system-identifier }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the show lacp command to troubleshoot problems related to LACP in a network.
Examples
This example shows how to display the LACP system identification:
This example shows how to display the LACP information for a specific interface:
Related Commands
|
|
|
|---|---|
show module
To display module information, use the show module command.
Syntax Description
Module number in the switch chassis. The range is from 1 to 3. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the module information for a specific module:
Related Commands
|
|
|
|---|---|
show nve interface nve
To display the configuration of an NVE interface, use the show nve interface nve command.
Syntax Description
Specifies the NVE ID. You can configure only 1 NVE interface on a switch. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the configuration of an NVE interface:
Related Commands
|
|
|
|---|---|
show nve peers
To display peers of the NVE interface, use the show nve peers command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command is enhanced to display all the VXLAN network identifiers (VNIs) configured for a particular peer. |
|
Examples
This example shows how to display the peers of an NVE interface:
Related Commands
|
|
|
|---|---|
show nve vni
To display the VNI that is mapped to an NVE interface, use the show nve vni command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the VNI that is mapped to an NVE interface for multicast replication:
The following example shows how to display the VNI that is mapped to an NVE interface for ingress replication:
Related Commands
|
|
|
|---|---|
show nve vxlan-params
To display the VXLAN UDP port configured, use the show nve vxlan-params command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the VXLAN UDP port configured:
Related Commands
|
|
|
|---|---|
show port-channel capacity
To display the total number of port channels that are configured, or are still available on the device, use the show port-channel capacity command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the port channels on a device:
Related Commands
|
|
|
|---|---|
Displays Cisco Technical Support information about EtherChannels. |
show port-channel compatibility-parameters
To display the parameters that must be the same among the member ports in order to join an EtherChannel interface, use the show port-channel compatibility-parameters command.
show port-channel compatibility-parameters
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the EtherChannel interface parameters:
Related Commands
|
|
|
|---|---|
Displays Cisco Technical Support information about EtherChannels. |
show port-channel database
To display the aggregation state for one or more EtherChannel interfaces, use the show port-channel database command.
show port-channel database [ interface port-channel number ]
Syntax Description
(Optional) Displays information for an EtherChannel interface. |
|
(Optional) Displays aggregation information for a specific EtherChannel interface. The number range is from 1 to 4096. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the aggregation state of all EtherChannel interfaces:
This example shows how to display the aggregation state for a specific EtherChannel interface:
Related Commands
|
|
|
|---|---|
Displays Cisco Technical Support information about EtherChannels. |
show port-channel load-balance
To display information about EtherChannel load balancing, use the show port-channel load-balance command.
show port-channel load-balance [ forwarding-path interface port-channel number { vlan vlan_ID } [ dst-ip ipv4-addr ] [ dst-ipv6 ipv6-addr ] [ dst-mac dst-mac-addr ] [ l4-dst-port dst-port ] [ l4-src-port src-port ] [ src-ip ipv4-addr ] [ src-ipv6 ipv6-addr ] [ src-mac src-mac-addr ][ ether-type ether-type ][ ip-proto ip-proto ]]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must use the vlan keyword for tagged packets to determine the use of hardware hashing.
Missing parameters are substituted with zero values unless specified in the output of the CLI.
Software hashing resolution is not used in the following scenarios:
- The specified packet contains an unknown unicast destination MAC address.
- The specified packet contains a multicast destination MAC address.
- The specified packet contains a broadcast MAC address.
Ethertype of the packet and the IP protocol type for IP packets are mandatory fields apart from the other inputs corresponding to the field selected.
Examples
This example shows how to display the port channel load balance information:
Related Commands
|
|
|
|---|---|
Configures the load-balancing method among the interfaces in the channel-group bundle. |
show port-channel summary
To display summary information about EtherChannels, use the show port-channel summary command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Before you use this command, you must configure an EtherChannel group using the interface port-channel command.
Examples
This example shows how to display summary information about EtherChannels:
Related Commands
|
|
|
|---|---|
Assigns and configures a physical interface to an EtherChannel. |
|
Creates an EtherChannel interface and enters interface configuration mode. |
show port-channel traffic
To display the traffic statistics for EtherChannels, use the show port-channel traffic command.
show port-channel traffic [ interface port-channel number ]
Syntax Description
(Optional) Displays traffic statistics for a specified interface. |
|
(Optional) Displays information for a specified EtherChannel. The range is from 1 to 4096. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the traffic statistics for all EtherChannels:
This example shows how to display the traffic statistics for a specific EtherChannel:
Related Commands
|
|
|
|---|---|
Displays Cisco Technical Support information about EtherChannels. |
show port-channel usage
To display the range of used and unused EtherChannel numbers, use the show port-channel usage command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the EtherChannel usage information:
Related Commands
|
|
|
|---|---|
Displays Cisco Technical Support information about EtherChannels. |
show resource
To display the number of resources currently available in the system, use the show resource command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the resources available in the system:
Related Commands
|
|
|
|---|---|
show running-config interface
To display the running configuration for a specific port channel, use the show running-config interface command.
show running-config interface [ all | { ethernet { slot / port } [ all ]} | { loopback { number } [ all ]} | { mgmt 0 [ all ]} | port-channel { channel-number } [ membership ]}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the running configuration for port channel 100 on a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
switch(config)# show running-config interface port-channel 100
!Command: show running-config interface port-channel100
!Time: Tue Aug 23 09:25:00 2011
version 5.0(3)U2(1)
interface port-channel100
speed 10000
switch(config)#
Related Commands
|
|
|
|---|---|
show running-config switch-profile
To display the running configuration of a switch profile, use the show running-config switch-profile command.
show running-config switch-profile
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the running configuration of a switch profile named s5010 configured on switch 1 of the peer:
Related Commands
|
|
|
|---|---|
Displays the startup configuration information for the switch profile. |
show running-config vpc
To display the running configuration information for virtual port channels (vPCs), use the show running-config vpc command.
show running-config vpc [ all ]
Syntax Description[
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the running configuration for a vPC on a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
This example shows how to display the configured and default running configuration for a vPC on a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the feature is not enabled, this command returns an error. |
show startup-config interface
To display interface configuration information in the startup configuration, use the show startup-config interface command.
show startup-config interface [ ethernet slot / port | loopback number | mgmt 0 | port-channel { channel-number } [ membership ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the information in the startup configuration for the interface Ethernet 1/1:
Related Commands
|
|
|
|---|---|
show startup-config switch-profile
To display the startup configuration of a switch profile, use the show startup-config switch-profile command.
show startup-config switch-profile
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the startup configuration of a switch profile named s5010 that is configured on switch 1 of the peer:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Displays the running configuration information for a switch profile. |
show startup-config vpc
To display virtual port channel (vPC) configuration information in the startup configuration, use the show startup-config vpc command.
show startup-config vpc [ all ]
Syntax Description
(Optional) Displays startup-configuration information for all vPCs. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the vPC information in the startup configuration:
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
show switch-profile
To display the switch profile configured on the switch, use the show switch-profile command.
show switch-profile [ sw-profile-name ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the switch profile that is configured on switch 1 of the peer:
Table 2 describes the fields shown in the display:
|
|
|
|---|---|
The revision of the switch profile configuration. The revision number is used to synchronize the configuration in the peer switch. |
Related Commands
|
|
|
|---|---|
show switch-profile buffer
To display the switch profile buffer, use the show switch-profile buffer command.
show switch-profile [ sw-profile-name ] buffer
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the buffer for the switch profile named s5010:
Table 3 describes the fields shown in the display:
|
|
|
|---|---|
The sequence number or order of entry of the command in the switch profile buffer. |
|
Related Commands
|
|
|
|---|---|
show switch-profile peer
To display information about the destination peer switch in a switch profile configuration, use the show switch-profile peer command.
show switch-profile [ sw-profile-name ] peer { ip-address [ details ] | details }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the information about a destination peer switch with the IPv4 address 192.168.120.3 added to the switch profile named s5010 on switch 1 of the peer:
This example shows how to display the successful commit information about a destination peer switch with the IPv4 address 192.168.120.3 for the switch profile named s5010 on switch 1 of the peer:
Table 4 describes the fields shown in the display:
Related Commands
|
|
|
|---|---|
Configures the peer switch for configuration synchronization. |
show switch-profile session-history
To display the session history of the switch profile configuration, use the show switch-profile session-history command.
show switch-profile [ sw-profile-name ] session-history
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the session history of the switch profile named s5010 on switch 1 of the peer:
Table 5 describes the fields shown in the display:
Related Commands
|
|
|
|---|---|
show switch-profile status
To display the switch profile configuration status, use the show switch-profile command.
show switch-profile [ sw-profile-name ] status
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the status of the switch profile named s5010 on switch 1 of the peer:
Table 6 describes the fields shown in the display:
Related Commands
|
|
|
|---|---|
show tech-support port-channel
To display troubleshooting information about EtherChannel interfaces, use the show tech-support port-channel command.
show tech-support port-channel
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The output from the show tech-support port-channel command is very long. To better manage this output, you can redirect the output to a file.
Examples
This example shows how to display Cisco technical support information for EtherChannel interfaces:
Related Commands
|
|
|
|---|---|
Configures the load-balancing method among the interfaces in the channel-group bundle. |
|
show tech-support vpc
To display troubleshooting information about the virtual port channel (vPC), use the show tech-support vpc command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the vPC troubleshooting information:
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
show version
To display information about the software and hardware version, use the show version command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the version information of a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
show vpc
To display detailed information about the virtual port channels (vPCs) configured on the switch, use the show vpc command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to display the vPC information:
This example shows how to display information about a specific vPC:
Related Commands
|
|
|
|---|---|
show vpc brief
To display brief information about the virtual port channels (vPCs), use the show vpc brief command.
Syntax Description
(Optional) Displays the brief information for the specified vPC. The range is from 1 to 4096. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The show vpc brief command displays the vPC domain ID, the peer-link status, the keepalive message status, whether the configuration consistency is successful, and whether a peer link formed or failed to form.
This command is not available if you have not enabled the vPC feature. See the feature vpc command for information about enabling vPCs.
You can display the track object if you have configured a tracked object for running vPCs on a single module in the vpc-domain configuration mode.
Examples
This example shows how to display brief information about the vPCs on a switch that runs Cisco NX-OS Release 7.0(3)I2(1) and later:
switch(config)# show vpc brief
(*) - local vPC is down, forwarding via vPC peer-link
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Disabled
Delay-restore status : Timer is off.(timeout = 30s) >>>>>> New Addition
Delay-restore SVI status : Timer is off.(timeout = 10s) >>>>>> New Addition
---------------------------------------------------------------------
-- ---- ------ --------------------------------------------------
----------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
-- ---- ------ ----------- ------ ------------
100 Po110 down* success success -
This example shows how to display brief information about the vPCs on a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
Related Commands
|
|
|
|---|---|
show vpc consistency-parameters
To display the consistency of parameters that must be compatible across the virtual port-channel (vPC) interfaces, use the show vpc consistency-parameters command.
show vpc consistency-parameters { global | interface { ethernet slot / port | port-channel channel-number } | vlans | vpc number }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The show vpc consistency-parameters command displays the configuration of all the vPC Type 1 parameters on both sides of the vPC peer link.
Note All the Type 1 configurations must be identical on both sides of the vPC peer link, or the link will not come up.
The vPC Type 1 configuration parameters are as follows:
- Port-channel mode: on, off, or active
- Link speed per channel
- Duplex mode per channel
- Trunk mode per channel
– Tagging of native VLAN traffic
- Spanning Tree Protocol (STP) mode
- STP region configuration for Multiple Spanning Tree
- Enable/disable state the same per VLAN
- STP global settings
– Port type setting—We recommend that you set all vPC peer link ports as network ports.
This command is not available if you have not enabled the vPC feature. See feature vpc for information on enabling vPCs.
Examples
This example shows how to display the vPC global consistency parameters on a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
This example shows how to display the vPC consistency parameters for the specified port channel on a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
This example shows how to display the vPC consistency parameters for the specified vPC on a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
This example shows how to display the vPC consistency parameters for VLANs on a switch that runs Cisco NX-OS Release 5.0(3)U2(1):
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
|
show vpc orphan-ports
To display ports that are not part of the virtual port channel (vPC) but have common VLANs, use the show vpc orphan-ports command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The show vpc orphan-ports command displays those ports that are not part of the vPC but that share common VLANs with ports that are part of the vPC.
This command is not available if you have not enabled the vPC feature. See the feature vpc command for information about enabling vPCs.
Examples
This example shows how to display vPC orphan ports:
Related Commands
|
|
|
|---|---|
show vpc peer-keepalive
To display the destination IP for the virtual port-channel (vPC) peer keepalive message and the status of the messages, use the show vpc peer-keepalive command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The show vpc peer-keepalive command displays the destination IP of the peer keepalive message for the vPC. The command also displays the send and receive status as well as the last update from the peer in seconds and milliseconds.
Note We recommend that you create a separate VRF on the peer devices to send and receive the vPC peer keepalive messages. Do not use the peer link itself to send the vPC peer-keepalive messages.
This command is not available if you have not enabled the vPC feature. See the feature vpc command for information about enabling vPCs.
Examples
This example shows how to display information about the peer-keepalive message:
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
show vpc role
To display information about the virtual port-channel (vPC) role of the peer device, use the show vpc role command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The show vpc role command displays the following information about the vPC status:
- Status of peer adjacency
- vPC role
- vPC MAC address
- vPC system priority
- MAC address of the device that you are working on
- System priority for the device that you are working on
This command is not available if you have not enabled the vPC feature. See the feature vpc command for information on enabling vPCs.
Examples
This example shows how to display the vPC role information of the device that you are working on:
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
|
show vpc statistics
To display virtual port-channel (vPC) statistics, use the show vpc statistics command.
show vpc statistics { peer-keepalive | peer-link | vpc number }
Syntax Description
Displays statistics about the specified vPC. The range is from 1 to 4096. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The peer-link parameter displays the same information as the show interface port-channel channel number command for the vPC peer-link port channel.
The vpc number parameter displays the same information as the show interface port-channel channel number command for the specified vPC port channel.
This command is not available if you have not enabled the vPC feature. See the feature vpc command for information on enabling vPCs.
Examples
This example shows how to display statistics about the peer-keepalive message:
This example shows how to display statistics about a specific vPC:
Related Commands
|
|
|
|---|---|
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
|
shutdown
To shut down the local traffic on an Ethernet interface or Ethernet port-channel interface, use the shutdown command. To return the interface to its default operational state, use the no form of this command.
Syntax Description
Command Default
Command Modes
Interface configuration mode
Subinterface configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
You can use this command on the following interfaces:
Note Use the no switchport command to configure an interface as a Layer 3 interface.
This command does not require a license but if you want to enable Layer 3 interfaces, you must install the LAN Base Services license.
Examples
This example shows how to shut down, or disable, a Layer 2 interface:
switch(config)# interface ethernet 1/10
switch(config-if)# shutdown
switch(config-if)#
This example shows how to shut down a Layer 3 Ethernet subinterface:
switch(config)# interface ethernet 1/5.1
switch(config-subif)# shutdown
switch(config-subif)#
Related Commands
|
|
|
|---|---|
Displays information on traffic about the specified EtherChannel interface. |
speed (Ethernet)
To configure the transmit and receive speed for an Ethernet interface, use the speed command. To reset to the default speed, use the no form of this command.
speed {10 | 100 | 1000 | 10000 | 40000 |auto }
Syntax Description
Sets the interface speed to 10 Gbps. This is the default speed for Cisco Nexus 3000 Series switches. |
|
Sets the interface speed to 40 Gbps. This is the default speed for Cisco Nexus 3132 switches. |
|
Command Default
Command Modes
Command History
|
|
|
Usage Guidelines
The default interface speed for Cisco Nexus 3000 Series switches is 10-Gigabit. To configure these ports for 1-Gigabit Ethernet, insert a 1-Gigabit Ethernet SFP transceiver into the applicable port and then set its speed with the speed command.
Note If the interface and transceiver speed is mismatched, the SFP validation failed message is displayed when you enter the show interface ethernet slot/port command. For example, if you insert a 1-Gigabit SFP transceiver into a port without configuring the speed 1000 command, you will get this error.
The default interface for Cisco Nexus 3132 switches is 40-Gigabit. When using Cisco Nexus 3132 switches, you can reconfigure interface speeds from 40-Gigabit to 10-Gigabit, and from 10-Gigabit back to 40-Gigabit.
Examples
This example shows how to set the speed for a 1-Gigabit Ethernet port:
switch(config-if)#
This example shows how to set the speed for a 10-Gigabit Ethernet port:
This example shows how to set the speed for a 40-Gigabit Ethernet port:
switch(config-if)#
Related Commands
|
|
|
|---|---|
switch-profile
To create or configure a switch profile, use the switch-profile command. To delete a switch profile, use the no form of this command.
switch-profile sw-profile-name
no switch-profile sw-profile-name { all-config | local-config }
Syntax Description
Command Default
Command Modes
Configuration synchronization mode
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to create a switch profile on each of the peer switches. You must use the same profile name on both the switches in the Cisco Fabric Services (CFS) peer configuration.
Note In this release of Cisco NX-OS, only a pair of switches can be configured as a peer.
You can configure only one active switch profile on each peer switch. If you create or configure a second switch profile, you see the following error message:
The configuration that is made locally on the switch is synchronized and made available on the peer switch only after the connectivity is established between the peer switches and the configuration is verified and committed on the local switch.
You can configure a switch profile to include the interface configuration, quality of service (QoS), and virtual port channel (vPC) commands. Fibre Channel over Ethernet (FCoE) commands are not supported on a switch profile.
When you delete a switch profile, you can choose to delete the local switch profile with the local configurations on the switch or delete the switch profile with the local configurations and configuration information in the peer. The peer becomes unreachable.
Examples
This example shows how to create a switch profile named s5010 on switch 1 of the peer:
This example shows how to create a switch profile named s5010 on switch 2 of the peer:
This example shows how to delete a switch profile named s5010 and its local configuration on switch 1 of the peer:
Related Commands
|
|
|
|---|---|
Displays the switch profile created on the switch and its configuration revision. |
|
Configures the peer switch for configuration synchronization. |
switchport block
To prevent the unknown multicast or unicast packets from being forwarded, use the switchport block command. To allow the unknown multicast or unicast packets to be forwarded, use the no form of this command.
switchport block { multicast | unicast }
no switchport block { multicast | unicast }
Syntax Description
Specifies that the unknown multicast traffic should be blocked. |
|
Specifies that the unknown unicast traffic should be blocked. |
Command Default
Unknown multicast and unicast traffic are not blocked. All traffic with unknown MAC addresses is sent to all ports.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can block the unknown multicast or unicast traffic on the switch ports.
Blocking the unknown multicast or unicast traffic is not automatically enabled on the switch ports; you must explicitly configure it.
Examples
This example shows how to block the unknown multicast traffic on an interface:
Related Commands
|
|
|
|---|---|
Displays the switch port information for a specified interface or all interfaces. |
switchport dot1q ethertype
To set the EtherType used for Q-in-Q encapsulation on an interface, use the switchport dot1q ethertype command. To reset the EtherType to its default value, Use the no form of this command.
switchport dot1q ethertype ethertype
no switchport dot1q ethertype [ ethertype ]
Syntax Description
Value to set for the EtherType. The range is from 0x600 to 0xffff. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You must enter the switchport command without any keywords to configure the Ethernet interface as a Layer 2 interface before you can enter the switchport mode command. This action is required only if you have not entered the switchport command for the interface.
You must set the EtherType only on the egress trunk interface that carries double tagged frames (the trunk interface that connects the service providers). If you change the EtherType on one side of the trunk, you must set the same value on the other end of the trunk (symmetrical configuration).
The EtherType value you set affects all the tagged packets going out on the interface (not just Q-in-Q packets).
Examples
This example shows how to create a 802.1Q tunnel on an interface:
switch(config-if)# switchport dot1q ethertype 0x9100
Related Commands
|
|
|
|---|---|
switchport host
To configure the interface to be an access host port, use the switchport host command. To remove the host port, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Ensure that you are configuring the correct interface. It must be an interface that is connected to an end station.
An access host port handles the Spanning Tree Protocol (STP) like an edge port and immediately moves to the forwarding state without passing through the blocking and learning states. Configuring an interface as an access host port also disables EtherChannel on that interface.
Examples
This example shows how to set an interface as an Ethernet access host port with EtherChannel disabled:
Related Commands
|
|
|
|---|---|
Displays a summary of the interface configuration information. |
|
Displays information on all interfaces configured as switch ports. |
switchport mode
To configure the interface as a nontrunking nontagged single-VLAN Ethernet interface, use the switchport mode command. To remove the configuration and restore the default, use the no form of this command.
switchport mode { access | trunk }
no switchport mode { access | trunk }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
An access port can carry traffic in one VLAN only. By default, an access port carries traffic for VLAN 1. To set the access port to carry traffic for a different VLAN, use the switchport access vlan command.
The VLAN must exist before you can specify that VLAN as an access VLAN. The system shuts down an access port that is assigned to an access VLAN that does not exist.
Examples
This example shows how to set an interface as an Ethernet access port that carries traffic for a specific VLAN only:
Related Commands
|
|
|
|---|---|
Displays information on all interfaces configured as switch ports. |
|
switchport mode dot1q-tunnel
To creates an 802.1Q tunnel on an interface, use the switchport mode dot1q-tunnel command. To disable the 802.1Q tunnel on the interface, use the no form of this command.
no switchport mode dot1q-tunnel
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You must enter the switchport command without any keywords to configure the Ethernet interface as a Layer 2 interface before you can enter the switchport mode command. This action is required only if you have not entered the switchport command for the interface.
The port goes down and reinitializes (port flap) when the interface mode is changed. BPDU filtering is enabled and the Cisco Discovery Protocol (CDP) is disabled on tunnel interfaces.
Examples
This example shows how to create a 802.1Q tunnel on an interface:
switch(config-if)# switchport mode dot1q-tunnel
Related Commands
|
|
|
|---|---|
switchport trunk allowed vlan
To set the list of allowed VLANs on the trunking interface, use the switchport trunk allowed vlan command. To allow all VLANs on the trunking interface, use the no form of this command.
switchport trunk allowed vlan { vlan-list | add vlan-list | all | except vlan-list | none | remove vlan-list }
no switchport trunk allowed vlan
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You must enter the switchport command without any keywords to configure the LAN interface as a Layer 2 interface before you can enter the switchport trunk allowed vlan command. This action is required only if you have not entered the switchport command for the interface.
You can enter the switchport trunk allowed vlan command on interfaces where the Switched Port Analyzer (SPAN) destination port is either a trunk or an access port.
If you remove VLAN 1 from a trunk, the trunk interface continues to send and receive management traffic in VLAN 1.
When you create a switchport trunk, by default it is not a member of any VLAN. You must explicitly add VLANs to the trunk port for traffic on those VLANs to be allowed on the trunk port. To remove all allowed VLANs from a trunk port, use the no form of this command and the trunk port becomes a member of no VLANs.
Examples
This example shows how to add a series of consecutive VLANs to the list of allowed VLANs on a trunking port:
switch(config-if)# switchport trunk allowed vlan add 40-50
Related Commands
|
|
|
|---|---|
Displays the administrative and operational status of a switching (nonrouting) port. |
switchport trunk native vlan
To change the native VLAN ID when the interface is in trunking mode, use the switchport trunk native vlan command. To return the native VLAN ID to VLAN 1, use the no form of this command.
switchport trunk native vlan vlan-id
no switchport trunk native vlan
Syntax Description
Native VLAN for the trunk in 802.1Q trunking mode. The range is from 1 to 4094, except the internally reserved VLANs are 3968 to 4047 and 4094. |
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
You must enter the switchport command without any keywords to configure the LAN interface as a Layer 2 interface before you can enter the switchport trunk native vlan command. This action is required only if you have not entered the switchport command for the interface.
Note See the vlandot1q tag native command for more information about configuring the native VLAN for 802,1Q trunk ports.
Use the no form of the native vlan command to reset the native mode VLAN to the default VLAN1 for the device.
Examples
This example shows how to configure the native VLAN for an interface in trunk mode:
Related Commands
|
|
|
|---|---|
Displays the administrative and operational status of a switching (nonrouting) port. |
sync-peers destination
To add a peer switch to a switch profile, use the sync-peers destination command. To remove a peer from the switch profile, use the no form of this command.
sync-peers destination ipv4-address
no sync-peers destination ipv4-address
Syntax Description
Destination IPv4 address of the peer switch in the format A. B. C. D. |
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to add the peer switch that will be included in the synchronization. You must have the IPv4 address of the peer switch. You can ensure that configuration synchronization is enabled on the peer switch by using the config sync command.
After you add a peer to a switch profile, you can add commands to the switch profile.
Peers maintain a configuration revision of their local configuration as well as the revision. After a network outage, when connectivity is established between the peer switches and the peers are reachable, each peer determines if any configuration in the switch needs to be synchronized with the other peer. Changed configurations will then be synchronized between the peers.
When you remove a peer from the switch profile, all configuration information about the peer is deleted from the local switch.
Examples
This example shows how to add a peer switch with IPv4 address 192.168.1.37 to a switch profile named s5010 on switch 1 of the peer:
This example shows how to add a peer switch with IPv4 address 192.168.120.3 to a switch profile named s5010 on switch 2 of the peer:
This example shows how to delete a peer with IPv4 address 192.168.1.37 from a switch profile named s5010 on switch 1 of the peer:
Related Commands
system default interface-vlan no autostate
To disable the systems default autostate behavior on VLAN interfaces (switched virtual interfaces [SVI]), use the system default interface-vlan no autostate command. To reenable the VLAN interface default feature, use the system default interface-vlan autostate command.
system default interface-vlan no autostate
system default interface-vlan autostate
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must use the feature interface-vlan command before you can create VLAN interfaces.
Examples
This example shows how to disable the systems interface VLAN autostate behavior:
Related Commands
|
|
|
|---|---|
system default switchport
To change the default interface mode for the system from Layer 3 routing to Layer 2 switching, use the system default switchport command. To return the system to Layer 3 routing default interface mode, use the no form of this command.
system default switchport [shutdown]
no system default switchport [shutdown]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The system default switchport command makes all the interfaces Layer 2 access ports.
Examples
This example shows how to configure the system so that all the interfaces are in Layer 2 access mode:
Related Commands
|
|
|
|---|---|
Displays the administrative and operational status of a switching (nonrouting) port. |
system-mac
To manually configure the virtual port channel (vPC) domain MAC address, use the system-mac command. To restore the default vPC system MAC address, use the no form of this command.
Syntax Description
MAC address that you want for the specified vPC domain in the following format aaaa.bbbb.cccc. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When you create a vPC domain, the Cisco NX-OS software automatically creates a vPC system MAC address, which is used for operations that are confined to the link-scope, such as the Link Aggregation Control Protocol (LACP). However, you may choose to configure the vPC domain MAC address manually.
Examples
This example shows how to configure the MAC address for the vPC domain:
This example shows how to remove the MAC address configuration on the vPC domain:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Displays information about the configuration for the keepalive messages. |
system-priority
To manually configure a system priority for the virtual port channel (vPC) domain, use the system-priority command. To restore the default system priority, use the no form of this command.
system-priority priority_value
no system-priority priority_value
Syntax Description
System priority that you want for the specified vPC domain. The range is from 1 to 65535, and the default value is 32667. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
We recommend that you manually configure the vPC system priority when you are running Link Aggregation Control Protocol (LACP) to ensure that the vPC peer devices are the primary devices on LACP. When you manually configure the system priority, ensure that you configure the same priority value on both vPC peer devices. If these values do not match, vPC will not come up.
Examples
This example shows how to configure the system priority for the vPC domain:
This example shows how to remove the system priority configuration for the vPC domain:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
tunnel destination
To configure the destination endpoint for a tunnel, use the tunnel destination command. To remove the tunnel destination, use the no form of this command.
tunnel destination { ip-address | host-name }
no tunnel destination { ip-address | host-name }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the tunnel destinatio n command to configure the destination address for an IP tunnel.
You should not have two tunnels using the same encapsulation mode with the same source and destination address.
Examples
This example shows how to configure the tunnel destination:
switch(config-if)# tunnel destination 192.0.2.120
Related Commands
|
|
|
|---|---|
Displays information about the traffic about the specified tunnel interface. |
tunnel mode
To configure the tunnel encapsulation mode for a tunnel, use the tunnel mode command. To restore the default value, use the no form of this command.
tunnel mode { gre {ip} | ipip {ip | decapsulate-any }}
Syntax Description
Specifies that any number of IP-in-IP tunnels can terminate at one tunnel interface. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the tunnel mode command to configure the tunnel encapsulation mode for a tunnel.
Examples
This example shows how to configure the tunnel mode for IPv4:
switch(config-if)# tunnel mode gre ip
This example shows how to configure the tunnel mode for multi-point IP-in-IP encapsulation:
switch(config-if)# tunnel mode ipip ip
Related Commands
|
|
|
|---|---|
Displays information about the traffic about the specified tunnel interface. |
tunnel source
To configure the source endpoint for a tunnel, use the tunnel source command. To remove the tunnel source, use the no form of this command.
tunnel source { ip-address | interface-type number }
no tunnel source [ ip-address | interface-type number ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the tunnel source command to configure the source address for an IP tunnel.
You should not have two tunnels using the same encapsulation mode with the same source and destination address.
Examples
This example shows how to set the tunnel source:
switch(config-if)# tunnel source 192.0.2.120
Related Commands
|
|
|
|---|---|
Displays information about the traffic about the specified tunnel interface. |
tunnel use-vrf
To specify which virtual routing and forwarding (VRF) instance to use to look up a tunnel destination IP address, use the tunnel use-vrf command. To return to the default, use the no form of this command.
Syntax Description
Name of the VRF in which to look up the tunnel destination IP address. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to specify the VRF in which to look up the tunnel destination IP address:
switch(config-if)# tunnel use-vrf blue
Related Commands
|
|
|
|---|---|
Displays information about the traffic about the specified tunnel interface. |
|
udld (configuration mode)
To configure the Unidirectional Link Detection (UDLD) protocol on the switch, use the udld command. To disable UDLD, use the no form of this command.
udld { aggressive | message-time timer-time | reset }
no udld { aggressive | message-time | reset }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
Usage Guidelines
UDLD aggressive mode is disabled by default. You can configure UDLD aggressive mode only on point-to-point links between network devices that support UDLD aggressive mode. If UDLD aggressive mode is enabled, when a port on a bidirectional link that has a UDLD neighbor relationship established stops receiving UDLD frames, UDLD tries to reestablish the connection with the neighbor. After eight failed retries, the port is disabled.
To prevent spanning tree loops, normal UDLD with the default interval of 15 seconds is fast enough to shut down a unidirectional link before a blocking port transitions to the forwarding state (with default spanning tree parameters).
When you enable the UDLD aggressive mode, the following occurs:
- One side of a link has a port stuck (both transmission and receive)
- One side of a link remains up while the other side of the link is down
In these cases, the UDLD aggressive mode disables one of the ports on the link, which prevents traffic from being discarded.
Examples
This example shows how to enable the aggressive UDLD mode for the switch:
This example shows how to reset all ports that were shut down by UDLD:
Related Commands
|
|
|
|---|---|
udld (Ethernet)
To enable and configure the Unidirectional Link Detection (UDLD) protocol on an Ethernet interface, use the udld command. To disable UDLD, use the no form of this command.
udld { aggressive | disable | enable }
no udld { aggressive | disable | enable }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
Usage Guidelines
You can configure normal or aggressive UDLD modes for an Ethernet interface. Before you can enable a UDLD mode for an interface, you must make sure that UDLD is enabled on the switch. UDLD must also be enabled on the other linked interface and its device.
To use the normal UDLD mode on a link, you must configure one of the ports for normal mode and configure the port on the other end for the normal or aggressive mode. To use the aggressive UDLD mode, you must configure both ends of the link for aggressive mode.
Examples
This example shows how to enable the normal UDLD mode for an Ethernet port:
This example shows how to enable the aggressive UDLD mode for an Ethernet port:
This example shows how to disable UDLD for an Ethernet port:
Related Commands
|
|
|
|---|---|
verify
To verify the buffered configuration of a switch profile, use the verify command.
Syntax Description
Command Default
Command Modes
Switch profile configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
When you use the verify command, the commands in the configuration are verified for mutual exclusion locally on the switch and on the peer switch, and then a merge check occurs on the peer switch to verify that the switch profile configurations are identical on both switches.
Note Only one peer can initiate the verification at a time.
Merge checks are done on the peer switch whenever the switch receives a new configuration. The merge checks ensure that the received configuration does not conflict with the switch profile configuration that already exists on the receiving switch. The merge check occurs during the merge or commit process. Errors are reported as merge failures and must be manually corrected.
A command that is included in a switch profile cannot be configured outside of the switch profile or on a peer switch. Ensure that the new configuration in the switch profile does not conflict with the configurations that might exist outside the switch profile or inside another switch profile. This process is called a mutual exclusion (mutex) check.
The following exceptions apply to mutual exclusion checks:
- Interface configuration—An interface configuration is exempted from mutual exclusion checks because it can exist both inside and outside a switch profile. For example, interface ethernet 1/1 can be present inside and outside the switch profile.
- Port shutdown—For operational or debugging reasons, a port may be shut down only on one of the switches. The shutdown and no shutdown commands are exempted from mutual exclusion checks.
- Port Channel command—When the first member interface is added to a port channel, the port channel inherits certain configurations from the member interface. Mutual exclusion checks are exempted.
- Switchport trunk allowed vlan—The switchport trunk allowed vlan add and switchport trunk allowed vlan remove command modifies a command instead of replacing the command. These commands are exempted from mutual exclusion checks.
If the configuration verification fails, you see the following error message:
Use the show switch-profile status or show switch-profile peer command to view the reason for the mutual check failure, merge failure, or the peer switch status.
Examples
This example shows how to verify a configuration on a switch profile named s5010 on switch 1 of the peer:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
vn-segment
To specify a VXLAN Virtual Network Identifier (VNID), use the vn-segment command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to map a VLAN to a VXLAN VNI:
Related Commands
|
|
|
|---|---|
vpc
To move other port channels into a virtual port channel (vPC) to connect to the downstream device, use the vpc command. To remove the port channels from the vPC, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can use any module in the device for the port channels.
Note We recommend that you attach the vPC domain downstream port channel to two devices for redundancy.
To connect to the downstream device, you create a port channel from the downstream device to the primary vPC peer device, and you create another port channel from the downstream device to the secondary peer device. Finally, working on each vPC peer device, you assign a vPC number to the port channel that connects to the downstream device. You will experience minimal traffic disruption when you are creating vPCs.
Note The port channel number and vPC number can be different, but the vPC number must be the same on both Cisco Nexus 3000 Series switches.
Examples
This example shows how to configure the selected port channel into the vPC to connect to the downstream device:
Related Commands
vpc domain
To create a virtual port channel (vPC) domain and assign a domain ID, use the vpc domain command. To revert to the default vPC configuration, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Before you can create a vPC domain and configure vPC on the switch, you must enable the vPC feature using the feature vpc command.
The vPC domain includes both vPC peer devices, the vPC peer keepalive link, the vPC peer link, and all the port channels in the vPC domain connected to the downstream device. You can have only one vPC domain ID on each device.
When configuring the vPC domain ID, make sure that the ID is different from the ID used by a neighboring vPC-capable device with which you may configure a double-sided vPC. This unique ID is needed because the system ID is derived from the MAC address ID of the switch. For a vPC, this MAC address is derived from the domain ID. As a result, in a peer-to-peer vPC configuration, if the neighboring switches use the same domain ID, a system ID conflict may occur in the LACP negotiation that may cause an unsuccessful LACP negotiation.
Under the vPC domain, make sure to configure the primary vPC device to ignore type checks by using the peer-config-check-bypass command.
Examples
This example shows how to create a vPC domain:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Restores the vPC peer links after a specified period of time. |
|
vpc peer-link
To create a virtual port channel (vPC) peer link by designating the port channel that you want on each device as the peer link for the specified vPC domain, use the vpc peer-link command. To remove the peer link, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
We recommend that you configure the Layer 2 port channels that you are designating as the vPC peer link in trunk mode and that you use two ports on separate modules on each vPC peer device for redundancy.
The Cisco Nexus 3000 Series switch supports 64 hardware port channels. Use the show port-channel capacity command to display the total number of port channels supported by the hardware.
Examples
This example shows how to select the port channel that you want to use as the vPC peer link for this device and configure the selected port channel as the vPC peer link:
This example shows how to remove the vPC peer link:
Related Commands
vxlan udp port
To configure the UDP port number for VXLAN, use the vxlan udp port command.
Syntax Description
Specifies the destination UDP port number for VXLAN encapsulated packets. The default destination UDP port number is 4789.. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The UDP port configuration should be done before the NVE interface is enabled. If the configuration must be changed while the NVE interface is enabled, ensure that you shut down the NVE interface, make the UDP configuration change and then re-enable the NVE interface.
Ensure that the UDP port configuration is done network-wide before the NVE interface is enabled on the network.
Examples
This example shows how to how to create a VXLAN destination UDP port:
Related Commands
|
|
|
|---|---|
Feedback