[c-nsp] Nexus 7K vPC with Object Tracking

[Yham]

Thank you Oliver,

If N7K switches have more than 100 vrfs and each vrf have more than one
vlans then means it is required to run equal numbers of routing processes.
In this case what you think which is best take: routing protocol per vrf or
enabling tracking? There may be better option other than these.

Regards


On Fri, Jan 17, 2014 at 1:55 PM, Oliver Garraux <oliver at g.garraux.net>wrote:

> You might consider putting a L3 network in place between the two N7K's for
> routing, so that they can re-route upstream traffic through the core link
> on the other N7K during a failure rather than bringing the physical links
> down. It can just be a VLAN w/ SVI's trunked over the VPC peer link.
>
> -------------------------------------
>
> Oliver Garraux
> Check out my blog:  blog.garraux.net
> Follow me on Twitter:  twitter.com/olivergarraux
>
>
> On Fri, Jan 17, 2014 at 7:48 AM, Yham <yhameed81 at gmail.com> wrote:
>
>> Hi Folks,
>>
>> Topology is something like two N7K have two downstream N5K running dual
>> vPC. Each N7K is single homed with core. So since each N7K learns remote
>> networks for that only core link so if the link goes down the traffic
>> black
>> hole because both N7K are not exchange routes.
>> I want to configure object tracking under vpc so if uplink core link goes
>> down, tracking bring down the downlinks toward N5K.
>>
>> Is anybody using object tracking ? are there any drawbacks/limitations or
>> any design consideration.
>>
>> Please share your thoughts.
>>
>> Thanks & Regards
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
>