Symptom

Leaf is unable to assume a vPC role, without assuming a role, the VPC interfaces will remain down. show vpc brief: Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 225 Peer status : peer link is down vPC keep-alive status : Disabled Configuration consistency status : failed Per-vlan consistency status : success Configuration inconsistency reason: Type-2 consistency status : failed Type-2 inconsistency reason : vPC role : none established <<<--- Should be Primary Number of vPCs configured : 32 Peer Gateway : Disabled Dual-active excluded VLANs : - Graceful Consistency Check : Enabled Auto-recovery status : Enabled (timeout = 240 seconds) Operational Layer3 Peer : Disabled

Conditions

A Single Leaf switch in a configured VPC pair, where the VPC peer is down fails to assume a role, after upgrade which causes the interfaces to stay in port-channel-members-down state.

Workaround

Since there is only one leaf in this vpc domain, removing the VPC Configuration will address this issue.

Further Problem Description