For a good explanation of

gavin han · ‎06-24-2015

in a topology where vPC is used, what happens in split brain situation in case of vPC? how spanning-tree loops are avoided?

sean_evershed · ‎06-24-2015

For a good explanation of that scenario see the following link fo detials:

https://supportforums.cisco.com/document/102781/vpc-auto-recovery-feature-nexus-7000

"the vPC secondary peer device brings down all its vPC member ports due to dual active detection."

vPC secondary peer device brings down all its vPC member ports due to dual active detection - See more at: https://supportforums.cisco.com/document/102781/vpc-auto-recovery-feature-nexus-7000#sthash.SorQKkW7.dpuf

gavin han · ‎06-26-2015

what happens when peer-keepalive goes down 1st and then peerlink goes down, this situation will cause dual active scenario and so split brain, right? in this case, secondary peer device won't bring down all its vPC member ports, right?

InayathUlla Sharieff · ‎06-29-2015

When your keepalive goes down nothing much will happen as your CFS will be communicating between the devices.

Now what happens when Peer-link goes down when you have keepalive already down?

AnsweR: you are right on it that now you will have dual active scenaorio and both the switches will be active and secondary peer will not bring down the vpc member ports because there is no one to communicate between the switches about the peer-link is down hence both will be active.

hth