03-31-2017 12:54 PM - edited 03-08-2019 10:00 AM
Greetings,
I hoping someone can help clarify this one, I believe I reading this right, but just want to make sure. I've already configured a vPC between two nexus 3845 switches and a keep alive. That is currently working. According to the best practice guide, it recommends to setup object tracking in the event a module goes offline that the traffic from the primary/secondary switch(s) won't "black hole". To prevent this would be to setup object tracking.
I just configured object tracking on the primary and secondary switch. My question is, should tracking only be configured on the primary switch or both primary and secondary and also would it be even necessary here since I'm using two 3548-48 switches instead of modules?
Best Practice
vPC Object Tracking Example Guide
Thanks in advance,
Andrew
Solved! Go to Solution.
03-31-2017 02:00 PM
VPC object tracking should be on both primary and secondary peers.
"The vPC object tracking configuration must be applied on both vPC peer devices. "
Page 37 of 129 -attached document "Best Practice".
N7KA-vdc2# show run vpc !Command: show running-config vpc !Time: Thu Sep 26 19:51:57 2013 version 6.1(4) feature vpc vpc domain 102 peer-keepalive destination 1.1.1.2 source 1.1.1.1 vrf vpc-keepalive peer-gateway track 1 auto-recovery
N7KB-vdc2# show run vpc
!Command: show running-config vpc
!Time: Thu Sep 26 19:53:17 2013
version 6.1(4)
feature vpc
vpc domain 102
peer-keepalive destination 1.1.1.1 source 1.1.1.2 vrf vpc-keepalive
peer-gateway
track 1
auto-recovery
03-31-2017 02:00 PM
VPC object tracking should be on both primary and secondary peers.
"The vPC object tracking configuration must be applied on both vPC peer devices. "
Page 37 of 129 -attached document "Best Practice".
N7KA-vdc2# show run vpc !Command: show running-config vpc !Time: Thu Sep 26 19:51:57 2013 version 6.1(4) feature vpc vpc domain 102 peer-keepalive destination 1.1.1.2 source 1.1.1.1 vrf vpc-keepalive peer-gateway track 1 auto-recovery
N7KB-vdc2# show run vpc
!Command: show running-config vpc
!Time: Thu Sep 26 19:53:17 2013
version 6.1(4)
feature vpc
vpc domain 102
peer-keepalive destination 1.1.1.1 source 1.1.1.2 vrf vpc-keepalive
peer-gateway
track 1
auto-recovery
03-31-2017 02:27 PM
Perfect, that's the way I have it now. Just making sure was all. Thanks again.
03-31-2017 02:33 PM
You're welcome :)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide