The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS vPC commands available on Cisco Nexus 5000 Series switches.
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.
peer-config-check-bypass
no peer-config-check-bypass
This command has no arguments or keywords.
None
vPC domain configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
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).
This example shows how to configure the primary vPC device to ignore type checks when the MCT is down:
switch(config-vpc-domain)# peer-config-check-bypass
switch(config-vpc-domain)#
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}]
Management port and VRF
vPC domain configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
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 Virtual Routing and Forwarding (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.
This example shows how to set up the peer keepalive link connection between the primary and secondary vPC device:
switch(config)# vpc domain 100
switch(config-vpc-domain)# peer-keepalive destination 192.168.2.2 source 192.168.2.1
Note:
--------:: Management VRF will be used as the default VRF ::--------
switch(config-vpc-domain)#
To manually assign a primary or secondary role to a vPC device, use the role command. To restore the default role priority, use the no form of this command.
role priority priority_value
no role priority priority_value
priority |
Specifies the priority to define primary or secondary roles in the vPC configuration. |
priority_value |
Priority value for the vPC device. The range is from 1 to 65535. |
None
vPC domain configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
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.
This example shows how to configure the role priority of a vPC device:
switch(config-vpc-domain)# role priority 100
switch(config-vpc-domain)#
To display the status of features on a switch, use the show feature command.
show feature
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the state of all features on a switch:
switch# show feature
Feature Name Instance State
-------------------- -------- --------
cimserver 1 disabled
fabric-binding 1 disabled
fc-port-security 1 disabled
fcoe 1 enabled
fcsp 1 disabled
fex 1 enabled
fport-channel-trunk 1 disabled
http-server 1 enabled
interface-vlan 1 enabled
lacp 1 enabled
lldp 1 enabled
npiv 1 enabled
npv 1 disabled
port_track 1 disabled
private-vlan 1 disabled
sshServer 1 enabled
tacacs 1 enabled
telnetServer 1 enabled
udld 1 enabled
vpc 1 enabled
vtp 1 disabled
switch#
|
|
---|---|
feature |
Enables or disables a feature on the switch. |
To display module information, use the show module command.
show module module_num
module_num |
Module number in the switch chassis. The range is from 1 to 3. |
Display information of all modules
EXEC mode
|
|
---|---|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the module information for a specific module:
switch# show module 1
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ---------------------- ------------
1 40 40x10GE/Supervisor N5K-C5020P-BF-SUP active *
Mod Sw Hw World-Wide-Name(s) (WWN)
--- -------------- ------ --------------------------------------------------
1 4.2(1u)N1(1u) 1.3 --
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 0005.9b78.6e48 to 0005.9b78.6e6f JAF1413ADCS
switch#
|
|
---|---|
show hardware inventory |
Displays information about the physical hardware. |
show inventory |
Displays hardware inventory information. |
To display the number of port channels that are configured, or are still available on the device, use the show port-channel capacity command.
show port-channel capacity
This command has no arguments or keywords.
None
EXEC mode
This example shows how to display the port channels on a device:
switch# show port-channel capacity
Port-channel resources
768 total 120 used 648 free 15% used
switch#
|
|
---|---|
show vpc brief |
Displays brief information about the vPCs. |
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]} | expand-port-profile | {loopback {number} [all]} | {mgmt 0 [all]} | {port-channel {channel-number} [membership]} | {tunnel {number} [all]} | {vlan {vlan-id} [all]}
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
This example shows how to display the running configuration for port channel 10:
switch(config)#
show running-config interface port-channel 10
version 4.0(1)
interface port-channel10
switchport
switchport mode trunk
switch(config)#
|
|
---|---|
show running-config |
Displays the running configuration on the device. |
To display the running configuration information for virtual port channels (vPCs), use the show running-config vpc command.
show running-config vpc [all]
all |
(Optional) Displays the running configuration for a vPC with defaults. |
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
This example shows how to display the running configuration for a vPC:
switch# show running-config vpc
!Command: show running-config vpc
!Time: Wed Mar 31 06:11:52 2010
version 4.2(1)N1(1)
feature vpc
vpc domain 1000
role priority 2000
peer-keepalive destination 192.168.183.52 source 192.168.76.51 vrf management
peer-config-check-bypass
interface port-channel1
vpc peer-link
interface port-channel3
vpc 4096
interface port-channel5
vpc 4001
interface port-channel12
vpc 4000
interface port-channel24
vpc 2000
interface port-channel41
vpc 41
interface port-channel48
vpc 48
--More--
switch#
|
|
---|---|
show vpc brief |
Displays information about vPCs. If the feature is not enabled, this command returns an error. |
To display interface configuration information in the startup configuration, use the show startup-config interface command.
show startup-config interface [ethernet slot/port | expand-port-profile | loopback number | mgmt 0 | port-channel {channel-number} [membership] | tunnel number | {vlan vlan-id}
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
This example shows how to display the information in the startup configuration for the interface Ethernet 7/1:
switch(config)# show startup-config interface ethernet 7/1
version 4.1(2)
interface Ethernet7/1
ip pim sparse-mode
switch(config)#
|
|
---|---|
show interface |
Displays information about the specified interface. |
To display virtual port channel (vPC) configuration information in the startup configuration, use the show startup-config vpc command.
show startup-config vpc [all]
all |
(Optional) Displays startup-configuration information for all vPCs. |
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
This example shows how to display the vPC information in the startup configuration:
switch(config)# show startup-config vpc
version 4.1(2)
feature vpc
vpc domain 1
interface port-channel10
vpc peer-link
interface port-channel20
vpc 100
switch(config)#
|
|
---|---|
show vpc brief |
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
To display troubleshooting information about the virtual port channel (vPC), use the show tech-support vpc command.
show tech-support vpc
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
This example shows how to display the vPC troubleshooting information:
switch# show tech-support vpc
`show version`
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS: version 1.3.0
loader: version N/A
kickstart: version 4.2(1)N1(1) [build 4.2(1)N1(0.329)]
system: version 4.2(1)N1(1) [build 4.2(1)N1(0.329)]
power-seq: version v1.2
BIOS compile time: 09/08/09
kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.latest.bin
kickstart compile time: 4/18/2010 8:00:00 [04/18/2010 15:03:44]
system image file is: bootflash:/n5000-uk9.4.2.1.N1.latest.bin
system compile time: 4/18/2010 8:00:00 [04/18/2010 16:08:18]
Hardware
cisco Nexus5020 Chassis ("40x10GE/Supervisor")
Intel(R) Celeron(R) M CPU with 2074284 kB of memory.
Processor Board ID JAF1413ADCS
Device name: d14-switch-2
bootflash: 1003520 kB
Kernel uptime is 0 day(s), 2 hour(s), 25 minute(s), 26 second(s)
Last reset at 414529 usecs after Mon Apr 19 05:59:19 2010
Reason: Disruptive upgrade
System version: 4.2(1u)N1(1u)
Service:
plugin
Core Plugin, Ethernet Plugin, Fc Plugin
`show module`
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ---------------------- ------------
1 40 40x10GE/Supervisor N5K-C5020P-BF-SUP active *
2 8 8x1/2/4G FC Module N5K-M1008 ok
3 6 6x10GE Ethernet Module N5K-M1600 ok
Mod Sw Hw World-Wide-Name(s) (WWN)
--- -------------- ------ --------------------------------------------------
1 4.2(1)N1(1) 1.3 --
2 4.2(1)N1(1) 0.200 20:41:00:05:9b:78:6e:40 to 20:48:00:05:9b:78:6e:40
3 4.2(1)N1(1) 0.100 --
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 0005.9b78.6e48 to 0005.9b78.6e6f JAF1413ADCS
2 0005.9b78.6e70 to 0005.9b78.6e77 JAB1228016M
3 0005.9b78.6e78 to 0005.9b78.6e7f JAB12310214
`show vpc brief`
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 1000
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status: success
vPC role : secondary
Number of vPCs configured : 150
Peer Gateway : Disabled
Dual-active excluded VLANs : -
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po1 up 1-330,335,338-447,1000-1023,2000-2018
vPC status
----------------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
------ ----------- ------ ----------- -------------------------- -----------
41 Po41 down* failed Consistency Check Not -
Performed
48 Po48 down* failed Consistency Check Not -
Performed
2000 Po24 down success success -
4000 Po12 down success success -
4001 Po5 down success success -
4096 Po3 down success success -
101376 Eth100/1/1 down* failed Consistency Check Not -
Performed
101377 Eth100/1/2 down* failed Consistency Check Not -
Performed
101378 Eth100/1/3 down* failed Consistency Check Not -
Performed
101379 Eth100/1/4 down* failed Consistency Check Not -
Performed
101380 Eth100/1/5 down* failed Consistency Check Not -
--More--
switch#
|
|
---|---|
show vpc brief |
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
To display detailed information about the virtual port channels (vPCs) configured on the switch, use the show vpc command.
show vpc [vpc-number]
vpc-number |
(Optional) vPC number. The range is from 1 to 4096. |
None
EXEC mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
This example shows how to display the vPC information:
switch# show vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 10
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status: success
Type-2 consistency reason : Consistency Check Not Performed
vPC role : secondary
Number of vPCs configured : 1
Peer Gateway : Disabled
Dual-active excluded VLANs : -
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po4000 up 1,3001-3500
vPC status
----------------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
------ ----------- ------ ----------- -------------------------- -----------
10 Po10 up success success 3001-3200
switch#
This example shows how to display information about a specific vPC:
switch# show vpc 10
vPC status
----------------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
------ ----------- ------ ----------- -------------------------- -----------
10 Po10 up success success 3001-3200
switch#
|
|
---|---|
show vpc brief |
Displays vPC information in a brief summary. |
vpc |
Configures vPC features on the switch. |
To display brief information about the virtual port channels (vPCs), use the show vpc brief command.
show vpc brief [vpc number]
vpc number |
(Optional) Displays the brief information for the specified vPC. The range is from 1 to 4096. |
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
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.
This example shows how to display brief information about the vPCs:
switch(config)# show vpc brief
Legend:
(*) - local vpc is down, forwarding via vPC peer-link
vPC domain id : 10
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status: success
vPC role : primary
Number of vPC configured : 1
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po10 up 1-100
vPC status
----------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
-- ---- ------ ----------- -------------------------- ------------
20 Po20 up success success 1-100
switch(config)#
This example shows how to display brief information about the vPCs. In this example, the port channel failed the consistency check, and the device displays the reason for the failure:
switch(config)# show vpc brief
Legend:
(*) - local vpc is down, forwarding via vPC peer-link
vPC domain id : 10
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status: failed
Configuration consistency reason: vPC type-1 configuration incompatible - STP interface port type inconsistent
vPC role : secondary
Number of vPC configured : 1
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po10 up 1-100
vPC status
----------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
-- ---- ------ ----------- -------------------------- ------------
20 Po20 up failed vPC type-1 configuration -
incompatible - STP
interface port type
inconsistent
switch(config)#
This example shows how to display information about the tracked objects in the vPCs:
switch(config)# show vpc brief
Legend:
(*) - local vpc is down, forwarding via vPC peer-link
vPC domain id : 1
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status: success
vPC role : secondary
Number of vPC configured : 3
Track object : 12
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po10 up 1-100
switch(config)#
|
|
---|---|
feature vpc |
Enables vPCs on the device. |
show port channel summary |
Displays information about port channels. |
vpc |
Configures vPC domains and peers. |
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 port-channel channel-number | vpc number}
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
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
–Native VLAN
–VLANs allowed on trunk
–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
–Bridge Assurance setting
–Port type setting—We recommend that you set all vPC peer link ports as network ports.
–Loop Guard settings
•STP interface settings:
–Port type setting
–Loop Guard
–Root Guard
•Maximum transmission unit (MTU)
•Allowed VLAN bit set
This command is not available if you have not enabled the vPC feature. See feature vpc for information on enabling vPCs.
This example shows how to display the vPC consistency parameters for the specified port channel:
switch(config)# show vpc consistency-parameters global
Legend:
Type 1 : vPC will be suspended in case of mismatch
Name Type Local Value Peer Value
------------- ---- ---------------------- -----------------------
QoS 1 ([], [3], [0], [1-2], ([], [3], [0], [1-2],
[4-5], [6]) [4-5], [6])
Network QoS (MTU) 1 (1538, 2240, 5038, (1538, 2240, 5038,
4038, 9216, 9216) 4038, 9216, 9216)
Network Qos (Pause) 1 (F, T, F, F, F, F) (F, T, F, F, F, F)
Input Queuing (Bandwidth) 1 (5, 10, 20, 0, 20, 40) (5, 10, 20, 0, 20, 40)
Input Queuing (Absolute 1 (F, F, F, T, F, F) (F, F, F, T, F, F)
Priority)
Output Queuing (Bandwidth) 1 (5, 10, 20, 0, 20, 40) (5, 10, 20, 0, 20, 40)
Output Queuing (Absolute 1 (F, F, F, T, F, F) (F, F, F, T, F, F)
Priority)
STP Mode 1 Rapid-PVST Rapid-PVST
STP Disabled 1 None None
STP MST Region Name 1 "" ""
STP MST Region Revision 1 0 0
STP MST Region Instance to 1
VLAN Mapping
STP Loopguard 1 Disabled Disabled
STP Bridge Assurance 1 Enabled Enabled
STP Port Type, Edge 1 Normal, Disabled, Normal, Disabled,
BPDUFilter, Edge BPDUGuard Disabled Disabled
STP MST Simulate PVST 1 Enabled Enabled
Allowed VLANs - 1-330,335,338-450,1000 1-330,333-447,1000-102
-1023,2000-2023 8,2000-2018
Local suspended VLANs - 331-334,336-337,448-45 -
0,2019-2023
switch(config)#
This example shows how to display the vPC consistency parameters for the specified port channel:
switch(config)# show vpc consistency-parameters interface port-channel 20
Legend:
Type 1 : vPC will be suspended in case of mismatch
Name Type Local Value Peer Value
------------- ---- ------------------------ --------------------------
STP Port Type 1 Default Default
STP Port 1 None None
Guard
mode 1 on on
Speed 1 10 Gb/s 10 Gb/s
Duplex 1 full full
Port Mode 1 trunk trunk
Native Vlan 1 1 1
MTU 1 1500 1500
Allowed VLAN - 1-100 1-100
bitset
switch(config)#
To display ports that are not part of the virtual port channel (vPC) but have common VLANs, use the show vpc orphan-ports command.
show vpc orphan-ports
This command has no arguments or keywords.
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
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.
This example shows how to display vPC orphan ports:
switch(config)# show vpc orphan-ports
Note:
--------::Going through port database. Please be patient.::--------
VLAN Orphan Ports
------- -------------------------
1 Po600
2 Po600
3 Po600
4 Po600
5 Po600
6 Po600
7 Po600
8 Po600
9 Po600
10 Po600
11 Po600
12 Po600
13 Po600
14 Po600
--More--
switch(config)#
|
|
---|---|
feature vpc |
Enables vPCs on the device. |
show vpc brief |
Displays brief information about vPCs. |
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.
show vpc peer-keepalive
This command has no arguments or keywords.
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
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.
This example shows how to display information about the peer-keepalive message:
switch(config)# show vpc peer-keepalive
vPC keep-alive status : peer is alive
--Send status : Success
--Last send at : 2008.05.17 18:23:53 986 ms
--Sent on interface : Eth7/16
--Receive status : Success
--Last receive at : 2008.05.17 18:23:54 99 ms
--Received on interface : Eth7/16
--Last update from peer : (0) seconds, (486) msec
vPC Keep-alive parameters
--Destination : 192.168.145.213
--Keepalive interval : 1000 msec
--Keepalive timeout : 5 seconds
--Keepalive hold timeout : 3 seconds
--Keepalive vrf : pkal
--Keepalive udp port : 3200
--Keepalive tos : 192
switch(config)#
|
|
---|---|
show vpc brief |
Displays information about vPCs. If the feature is not enabled, the system displays an error when you enter this command. |
To display information about the virtual port-channel (vPC) role of the peer device, use the show vpc role command.
show vpc role
This command has no arguments or keywords.
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
The show vpc role command displays the following information about the vPC status:
•Status of peer adjacency
•vPC role of the VDC that you are working on
•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.
This example shows how to display the vPC role information of the device that you are working on:
switch(config)# show vpc role
Primary:
vPC Role status
----------------------------------------------------
vPC role : primary
Dual Active Detection Status : 0
vPC system-mac : 00:23:04:ee:be:01
vPC system-priority : 32667
vPC local system-mac : 00:22:55:79:ea:c1
vPC local role-priority : 32667
Secondary:
vPC Role status
----------------------------------------------------
vPC role : secondary
Dual Active Detection Status : 0
vPC system-mac : 00:23:04:ee:be:01
vPC system-priority : 32667
vPC local system-mac : 00:22:55:79:de:41
vPC local role-priority : 32667
switch(config)#
When you reload the primary vPC peer device, the secondary vPC peer device assumes the role of the primary device. This example shows how the vPC role displays then on the new primary device:
switch(config)# show vpc role
vPC Role status
----------------------------------------------------
vPC role : secondary, operational primary
Dual Active Detection Status : 0
vPC system-mac : 00:23:04:ee:be:64
vPC system-priority : 32667
vPC local system-mac : 00:22:55:79:de:41
vPC local role-priority : 32667
switch(config)#
To display virtual port-channel (vPC) statistics, use the show vpc statistics command.
show vpc statistics {peer-keepalive | peer-link | vpc number}
None
Any command mode
|
|
---|---|
4.1(3)N1(1) |
This command was introduced. |
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.
This example shows how to display statistics about the peer-keepalive message:
switch# show vpc statistics peer-keepalive
vPC keep-alive status : peer is alive
VPC keep-alive statistics
----------------------------------------------------
peer-keepalive tx count: 1036
peer-keepalive rx count: 1028
average interval for peer rx: 995
Count of peer state changes: 1
switch(config)#
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.
system-mac mac_address
no system-mac mac_address
mac_address |
MAC address that you want for the specified vPC domain in the following format aaaa.bbbb.cccc. |
None
vPC domain configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
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.
This example shows how to configure the MAC address for the vPC domain:
switch(config-vpc-domain)# system-mac 23fb.4ab5.4c4e
switch(config-vpc-domain)#
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
priority_value |
System priority that you want for the specified vPC domain. The range is from 1 to 65535, and the default value is 32667. |
The default for the system priority is 32667.
vPC domain configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
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.
This example shows how to configure the system priority for the vPC domain:
switch(config-vpc-domain)# system-priority 3000
switch(config-vpc-domain)#
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.
vpc number
no vpc number
None
Interface configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
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 5000 Series switches.
This example shows how to configure the selected port channel into the vPC to connect to the downstream device:
switch(config)# interface port-channel 20
switch(config-if)# vpc 5
switch(config-if)#
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.
vpc domain domain_id
no vpc domain domain_id
domain_id |
vPC domain ID. The range is from 1 to 1000. |
None
Global configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
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.
This example shows how to create a vPC domain:
switch# configure terminal
switch(config)# vpc domain 5
switch(config-vpc-domain)#
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.
vpc peer-link
no vpc peer-link
This command has no arguments or keywords.
None
Interface configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
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 5000 Series switch supports 768 hardware port channels. Use the show port-channel capacity command to display the total number of port channels supported by the hardware.
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:
switch(config)# interface port-channel 20
switch(config-if)# vpc peer-link
switch(config-vpc-domain)#