Nexus 5548UP - HSRP and vPC, tracking required?

zykobot · ‎09-16-2013

Hi,

We've got two Nexus 5548UPs that are vPC and HSRP peers.

I've had some feedback that I should incorporate the tracking function to close the vPC down in the case of a layer 3 problem, the thing is I'm not sure it's required. I can see in this article it recommends implementing tracking when your L2 peer-link and L3 interfaces are on the same module (which it is in my case).. http://www.cisco.com/en/US/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf

Any one got any real world experience and can offer some feedback.. I don't mind putting it in just want to understand why.

Thanks,

Nick.

Marwan ALshawi · ‎09-21-2013

Hi Nick

there is two tracking can be use din nexus enviroment

HSRP tracking and vPC tracking

for using one line card for the vPC peer link vPC tracking is recomnded

HSRP tracking is used to track L3 uplinks to the core

Using vPC with HSRP/VRRP object tracking may leads to traffic blackholing in case object tracking is triggered

its better to use separate L3 inter switch link instead of using HSRP tracking

hope this help