> Saku Ytti
> Sent: Thursday, March 17, 2016 3:19 PM
>
> On 17 March 2016 at 16:59, Mark Tinka <[email protected]> wrote:
> > Play with RT's.
> >
> > Use an RT on each spoke that imports only the routes from the hub.
> > That RT should not be used for export by any other spoke to the hub.
>
> This approach relies on no IP lookup at hub PE, if hub PE does IP lookup it'll
> bridge the spokes. I would recommend Charlies's approach and explicitly use
> different VRF for ingress and egress.
> On many platforms it may be hard to reason when IP lookup happens on PE.
>
And what if you'd advertise just default/summary down to spokes.
And you'd advertise the default with per next-hop/per prefix label.
adam
Adam Vitkovsky
IP Engineer
T: 0333 006 5936
E: [email protected]
W: www.gamma.co.uk
This is an email from Gamma Telecom Ltd, trading as “Gamma”. The contents of
this email are confidential to the ordinary user of the email address to which
it was addressed. This email is not intended to create any legal relationship.
No one else may place any reliance upon it, or copy or forward all or any of it
in any form (unless otherwise notified). If you receive this email in error,
please accept our apologies, we would be obliged if you would telephone our
postmaster on +44 (0) 808 178 9652 or email [email protected]
Gamma Telecom Limited, a company incorporated in England and Wales, with
limited liability, with registered number 04340834, and whose registered office
is at 5 Fleet Place London EC4M 7RD and whose principal place of business is at
Kings House, Kings Road West, Newbury, Berkshire, RG14 5BY.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
