Hoogen,
Okay.. Earlier task required while accepting routes from peer to tag
them with a community and prepend them with as number 65412 twice...
I notice that when I deactivate that.. It works.. So obviously R3 is
considering the routes received from R1 with prepend of 65412 for
all P1 routes to be some sort of as loop... So I guess there is
something wrong about it..
Page 568 of the JNCIP books...
> I guess for the solution to work we need to have
>
> autonomous-system 65001 loops 3;
>
> This would make sure we get those routes.
>
it would, but I don't remember having to set as-loops when I worked
through the JNCIP book. And I double-checked your initial email to find
you might have a typo:
l...@r1# run show route advertising-protocol bgp 10.0.3.3
>>
>> inet.0: 65 destinations, 69 routes (63 active, 0 holddown, 4 hidden)
>> Prefix Nexthop MED Lclpref AS
path
>> * 3.4.0.0/20 10.0.5.254 100 65412
>> 65412 1492 I
You prepend 65412 65412, where it should be 64512 64512
There's also a typo in at least r1 & r3 configs:
confederation 65412 members [ 65000 65001 65002 ];
your problems may be coming from those typos - if you consistently
mistyped 64512 through your whole setup, it's probably ok, but I'd
double-check all routers.
Note that stuff like this will mess you up badly in the actual lab -
double-check every number you type, it saves time in the long run :)
Kind regards,
Felix
--
Felix Schüren
Head of Network
-----------------------------------------------------------------------
Host Europe GmbH - http://www.hosteurope.de
Welserstraße 14 - 51149 Köln - Germany
Telefon: 0800 467 8387 - Fax: +49 180 5 66 3233 (*)
HRB 28495 Amtsgericht Köln - USt-IdNr.: DE187370678
Geschäftsführer:
Uwe Braun - Alex Collins - Mark Joseph - Patrick Pulvermüller
(*) 0,14 EUR/Min. aus dem dt. Festnetz, Mobilfunkpreise ggf. abweichend
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
