EMAIL SUPPORT

dclessons@dclessons.com

LOCATION

US

VPC Consistency Check and failover Scenarios

VPC Consistency Check and failover Scenarios

Cisco Fabric Services (CFS) Protocol:

Cisco Fabric Services CFS is the reliable protocol performs the following functions:

  • Configure validation and comparison (VPC consistency check)
  • Synchronization of MAC addresses for vPC member ports
  • vPC member port status advertisement
  • Spanning Tree Protocol management
  • Synchronization of HSRP and IGMP snooping

Cisco fabric Service is enabled by default as soon as vPC feature is turned on. CFS message are encapsulated in Ethernet frame and is tagged with COS 4 for reliable communication.

You can check the CFS for vPC

7K1# sh cfs application
----------------------------------------------
Application     Enabled       Scope
----------------------------------------------
arp                   Yes          Physical-eth
pim                  Yes          Physical-eth
stp                   Yes          Physical-eth
vpc                  Yes          Physical-eth
igmp                Yes          Physical-eth
l2fm                 Yes          Physical-eth

vPC consistency check Configuration

As soon as vPC feature is enabled, CFS starts working and after configuration is done then via CFS protocol it check and validates the configuration at both Peer device. Based on configuration Validation and comparison CFS divides the configuration and its error in to two types:

There are two types of VPC consistency checks:

  • Type 1 - Puts peer device or interface into a suspended state to prevent invalid packet forwarding behaviour. With vPC Graceful Consistency check, suspension occurs only on the secondary peer device.
  • Type 2 - Peer device or Interface still forward traffic. However they are subject to undesired packet forwarding behaviour.

Type 1 and Type 2 consistency check apply both for global configuration and for vPC interface configuration.

Type-1 VPC Consistency Check:

Once CFS starts running on both peer-devices, the CFS protocols provide a copy of the configuration on the local vPC peer device to remote vPC device. The per-interface parameters must be consistent per interface, and the global parameters must be consistent globally.

When Type 1 inconsistency is detected then following action is taken:

  • For global configuration type 1 inconsistency check, all vPC member ports are set to down state.
  • For vPC interface configuration type 1 inconsistency check, the misconfigured vPC is set to down state.

Use the following command to check and display the global configuration and vPC

Show vpc consistency-parameters global

Below lists global configuration parameters that are taken into account for type-1 consistency check.

Below lists the per vPC interface parameters that are taken into account for type-1 consistency check.

Use the following command to check and display the interface configuration and vPC

Show vpc consistency-parameters interface port-channel < Id >

Type-2 VPC Consistency Check

When the Type-2 inconsistency check is detected, moderate action or no action is taken. 

For global configuration type 2 inconsistency check, all vPC member ports remain in up state and vPC systems trigger to protective actions.

GENERAL FAQ

vPC Consistency Check ensures that both vPC peer switches have matching and compatible configurations. This prevents traffic loops, blackholing, and unpredictable forwarding behavior.

If a configuration mismatch is detected, corrective action is taken based on whether it is a Type-1 or Type-2 inconsistency. This validation is automatically performed through Cisco Fabric Services (CFS) once the vPC feature is enabled.

Cisco Fabric Services (CFS) is responsible for distributing and synchronizing configuration information between vPC peer switches.

It performs the following key functions:

• Configuration validation and comparison (vPC consistency check)

• MAC address synchronization for vPC member ports

• vPC member port status advertisement

• Spanning Tree coordination

• HSRP and IGMP snooping synchronization

Because of CFS, the vPC Consistency Check runs automatically, ensuring both switches remain aligned during normal operation and during vPC failover scenarios.

• Type-1 inconsistency: This is a critical mismatch. It results in suspension of the affected vPC or all vPC member ports (depending on whether the mismatch is global or interface-level). This prevents incorrect packet forwarding behavior.

• Type-2 inconsistency: This is a non-critical mismatch. Traffic forwarding continues, but the system may apply protective mechanisms to prevent instability.

In simple terms, Type-1 is strict and protective, while Type-2 allows forwarding but still requires correction.

If a Type-1 mismatch is detected:

• Global configuration mismatch: All vPC member ports are brought down.

• Interface-level mismatch: Only the affected vPC (port-channel) is brought down.

This strict action ensures that incorrect packet forwarding does not occur and protects the network from loops and traffic blackholing.

You can use the following operational commands to verify consistency parameters:

• show vpc consistency-parameters global

• show vpc consistency-parameters interface port-channel <id>

These commands help quickly identify configuration mismatches and are extremely useful while troubleshooting vPC failover scenarios.

No. In a Type-2 mismatch, vPC member ports generally remain in the up state, and traffic continues to be forward.

However, the switch may apply protective mechanisms to avoid instability. Even though forwarding continues, administrators should correct Type-2 mismatches to ensure stable and predictable vPC behavior, especially during failover conditions.

Comment

  • RS

    Super Duper Like


  • AB

    Awesome


LEAVE A COMMENT

Please login here to comment.