Enterprise Lab 1 Data Center Back to Back vPC

In this video, we will deploy back to back vPC.
Lab docs: drive.google.c...

[@mohamedkamal3514]

Excellent 😊

[@ChingizKhalafov]

Your ports in suspended state, because you didn't configured vpc under them. So, from LACP perspective, eg. N9K5 is connected to the two different devices. If you run show lacp neighbor you probably will see different LACP Sistem ID.

[@michaelcastillo4069]

yup

[@mahmoudnabtiti684]

Your materials that mentioned , enough to be do the lab ?

[@Lee-qp2et]

I was wondering why you didn't stick to all your task from thesheet for this lab. Was there a reason you didn't create vlan 20 and 21 on all switches or was this a mistake which was copied and paste from the previous task. Also my show mac address-table dynamic is always empty. maybe it's the code I'm using on the 9k which is nxos.9.2.2.bin

[@forlap574]

Hey Rob, I hope you're doing well. What about spanning tree in back to back vpc? Do we need to use stp here?

[@RobRikerTechChannel]

Yep, bridge assurance should kick in. The STP root needs to be set.

[@forlap574]

@@RobRikerTechChannel Thank you for your answer. On which vpc doman do we need to set stp root?

[@forlap574]

@@RobRikerTechChannel Do you have an example?

[@forlap574]

@@RobRikerTechChannel Bridge assurace needed only on vpc peer-links? Do we need to set this on links between vpc domain?I maen redarding this topology. Could you describe the STP root setup process in more detail?

[@RobRikerTechChannel]

@@forlap574 correct for bridge assurance. Normal STP rules apply. There's some design guides for nexus with b2b vpc, Google for them and review.