Symptom

The vpc failure is not reported when there is a configuration mismatch between 2 vpc port-channels, where one side has "no lacp suspend-individual pxe" while the other does not. When such an inconsistency happens, vPC primary leg will show status as up, and consistency reason failed. #show vpc br vPC status ---------------------------------------------------------------------------- Id Port Status Consistency Reason Active vlans -- ------------ ------ ----------- ------ --------------- 100 Po100 up failed 10 vPC secondary leg will be down and failed #show vpc br vPC status ---------------------------------------------------------------------------- Id Port Status Consistency Reason Active vlans -- ------------ ------ ----------- ------ --------------- 100 Po100 down* failed The reason for the failure is not shown here. However, the show vpc consistency-parameters output will show the inconsistency: show vpc consistency-parameters vpc 100 Legend: Type 1 : vPC will be suspended in case of mismatch Name Type Local Value Peer Value ------------- ---- ---------------------- ----------------------- delayed-lacp 1 disabled disabled lacp suspend disable 1 pxe-disabled enabled >>> inconsistency shown here mode 1 active active

Conditions

vPC configuration mismatch on 2 vpc port-channel legs. One has "no lacp suspend-individual pxe", and other does not. There is no functionality impact.

Workaround

The configuration inconsistency reason is not displayed in "show vpc brief", but it is reported in "show vpc consistency-parameters vpc

Further Problem Description