[j-nsp] BGP Route Reflector
hansito36 at hotmail.com
Mon Apr 21 20:46:16 EDT 2003
But even then if you loose one link from one of the clients to the RRs, you
are back to square one. So you're still better off with changing the
cluster-id on the RRs.
>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
>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
>SoluNet Technical Support
>Mailto: mpuras at solunet.com
>Direct: (321) 309-1410
>888.449.5766 (USA) / 888.SOLUNET (Canada)
>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
>I concur with Jesper, this is due to the same cluster-id on A and B. You
>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
>juniper-nsp mailing list juniper-nsp at puck.nether.net
Add photos to your messages with MSN 8. Get 2 months FREE*.
More information about the juniper-nsp