[j-nsp] BGP Route Reflector

[MPuras at solunet.com]

I think the issue here is the fact that A and B have the same cluster ID.
When router B learns a route from its client (router E), on reflecting the
route, it attaches the clusterID to the route and sends it to other clients
and Router A.  However, when router A gets the route it sees that it came
from the same clusterID therefore it drops it.  You can verify this by
looking at routes you are advertising to Router A from B.  Also check
whether A is even installing it into the routing table.  I would suspect
that it is not due to router A thinking that the route it just received is
looped and discarding it before it is even processed into the RIB-IN-ADJ
table.  You can also overcome this issue (if in fact it is the issue) by
changing the cluster-id on Router A.  Please let me know the outcome.
Thanks.




Thanks, 

Mario Puras 
SoluNet Technical Support
Mailto: mpuras at solunet.com
Direct: (321) 309-1410  
888.449.5766 (USA) / 888.SOLUNET (Canada) 



-----Original Message-----
From: Tay Chee Yong [mailto:tcy at pacific.net.sg]
Sent: Monday, April 21, 2003 5:11 AM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] BGP Route Reflector


Hi all,

I have 2 route reflectors (Router A and Router B).
2 RR clients (C and D)

Both C and D are the clients of A and B
A and B are full mesh

Both A and B are using the same cluster id, 1.1.1.1

I then add router E to be client of B only, with some routes filtering.

Strangely, router A is not selecting the better route from B learned from
E, instead router A is registering the better route from its learned eBGP
peer.

Why aren't B propagating the better route learned from E to router A?

Regards,
Cheeyong

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp