Nexus vPC and Object Tracking

[Andrew Hernandez]

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

http://www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf

vPC Object Tracking Example Guide

http://www.cisco.com/c/en/us/support/docs/switches/nexus-7000-series-switches/200996-vPC-Object-Tracking.html#anc3

Thanks in advance,

Andrew

[Austin Sabio · Accepted solution]

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

[Andrew Hernandez]

Perfect, that's the way I have it now. Just making sure was all.  Thanks again.

[Austin Sabio]

You're welcome :)