VPC Priority for a dual sided Active Active setup?

[CiscoBrownBelt]

So I have a setup of 2 9k as cores  in a VPC domain and both VPC configs on each of these switches are configured with same priority 100, however one switch is the primary role and I would like it to be the other switch. Should I configure the other switch with a higher priority?

Also, connecting to these Core 9k are a couple more 92k as access switches in VPC domains as well. I want these in VPC as well because servers will be dual connected to be in Active Active mode with same priorites. Is this a good setup? Should I only do VPC at the access layer?

[Reza Sharifi]

So I have a setup of 2 9k as cores  in a VPC domain and both VPC configs on each of these switches are configured with same priority 100, however one switch is the primary role and I would like it to be the other switch. Should I configure the other switch with a higher priority?

You can configure the other switch with higher priority but the VPC role will not switch until you reboot the current primary chassis or break the VPC connection between the 2 switches (sh and no sh on the VPC peer-link). 

Also, connecting to these Core 9k are a couple more 92k as access switches in VPC domains as well. I want these in VPC as well because servers will be dual connected to be in Active Active mode with same priorites. Is this a good setup? Should I only do VPC at the access layer?

Yes, you can connect each access switch to both 9k core switches and build a vPC for each.

HTH

[CiscoBrownBelt]

Ok so I did reboot one Core and now Core 2 is the primary VPC. To make Core 1 primary again I would have to reboot the secondary (Primary VPC)?
Also, on the cores I am tracking the interface on each core that goes to a single edge device.
From the access VPC switches, should I track the links to the Cores (each access switch has 1 link to Core 1 and 2)?
How is it done, do you usually just do a track object for interface to Primary core?

[Reza Sharifi]

Ok so I did reboot one Core and now Core 2 is the primary VPC. To make Core 1 primary again I would have to reboot the secondary (Primary VPC)?

That is correct.

How is it done, do you usually just do a track object for interface to Primary core?

I am not sure what is this tracking for. What are you trying to do?

HTH

[CiscoBrownBelt]

Want to track the interface to the primary core so in case that link goes down, switch knows to send the traffic to Core 2.

[Reza Sharifi]

No need for that at all. Usually, both links to core switches are in a Portchannel and when one link goes down the other link continues to operate and forward traffic. 

HTH

[CiscoBrownBelt]

Ok good I did not feel like doing all that :)

So tracking to edge device from Cores should be good.

[CiscoBrownBelt]

Should peer-switch and peer=gateway command not only be configured on the Core VPC switches but the Access VPC switches as well?

[Reza Sharifi]

These 2 commands are global under the vpc domain

vpc domain x

peer-switch

HTH

[CiscoBrownBelt]

Yes but should I configure peer switch and the peer gateway on the Cores and Access VPC domains?