Viewing An Interface-Specific Type-1 Inconsistency - Cisco Nexus 3548 Configuration Manual
Nx-os interfaces release 9x
Hide thumbs
Also See for Nexus 3548:
- Command reference manual (556 pages) ,
- Configuration manual (230 pages) ,
- Installation manual (112 pages)
Table of Contents
Advertisement
Viewing an Interface-Specific Type-1 Inconsistency
20
30
Viewing an Interface-Specific Type-1 Inconsistency
When an interface-specific Type-1 inconsistency occurs, the vPC port on the secondary switch is brought
down while the primary switch vPC ports remain up.The following example shows this type of inconsistency
when there is a switchport mode mismatch.
This example shows how to display the status of the suspended vPC VLAN on the secondary switch:
switch(config-if)# show vpc brief
Legend:
vPC domain id
Peer status
vPC keep-alive status
Configuration consistency status: success
Per-vlan consistency status
Type-2 consistency status
vPC role
Number of vPCs configured
Peer Gateway
Dual-active excluded VLANs
Graceful Consistency Check
vPC Peer-link status
---------------------------------------------------------------------
id
--
1
vPC status
----------------------------------------------------------------------------
id
------ ----------- ------ ----------- -------------------------- -----------
20
30
This example shows how to display the inconsistent status (the VLANs on the primary vPC are not suspended)
on the primary switch:
switch(config-if)# show vpc brief
Legend:
vPC domain id
Peer status
vPC keep-alive status
Configuration consistency status: success
Per-vlan consistency status
Type-2 consistency status
vPC role
Number of vPCs configured
Peer Gateway
Dual-active excluded VLANs
Graceful Consistency Check
Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x
70
Po20
up
failed
Po30
up
failed
(*) - local vPC is down, forwarding via vPC peer-link
Port
Status Active vlans
----
------ --------------------------------------------------
Po1
up
1
Port
Status Consistency Reason
Po20
up
success
Po30
down*
failed
(*) - local vPC is down, forwarding via vPC peer-link
Global compat check failed 1-10
Global compat check failed 1-10
: 10
: peer adjacency formed ok
: peer is alive
: success
: success
: secondary
: 2
: Disabled
: -
: Enabled
success
Compatibility check failed -
for port mode
: 10
: peer adjacency formed ok
: peer is alive
: success
: success
: primary
: 2
: Disabled
: -
: Enabled
Configuring Virtual Port Channels
Active vlans
1
Hide quick links:
Advertisement
Table of Contents
