[j-nsp] BGP Route Reflector

[jerome fabre]

I meant fully meshing the clients with the RRs. In this case E with A and B.

>From: MPuras at solunet.com
>To: hansito36 at hotmail.com
>CC: juniper-nsp at puck.nether.net
>Subject: RE: [j-nsp] BGP Route Reflector
>Date: Mon, 21 Apr 2003 15:12:38 -0400
>
>I dont believe that fully meshing the clients  (routers C, D and E) will
>solve this problem.  The "no-client-reflect" is configured under the
>peer-group that defines Router C, D and E (i.e. the clients) not Router A.
>So Router B will still advertise the router to router A.  Router A will 
>then
>drop it due to the same cluster-id being configured.  The only fix to this
>given the scenario at present is to change the cluster-id on router A (or
>B).
>
>
>
>
>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: jerome fabre [mailto:hansito36 at hotmail.com]
>Sent: Monday, April 21, 2003 9:59 AM
>To: tcy at pacific.net.sg
>Cc: juniper-nsp at puck.nether.net
>Subject: Re: [j-nsp] BGP Route Reflector
>
>
>Cheeyong,
>
>I concur with Jesper, this is due to the same cluster-id on A and B. You 
>can
>
>fix this situation by either making the cluster-id different on A and B or
>by fully meshing the clients.
>
>Hope this help.
>
>
>
>
>
>
>
>_________________________________________________________________
>Protect your PC - get McAfee.com VirusScan Online
>http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>http://puck.nether.net/mailman/listinfo/juniper-nsp


_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail