> -----Original Message----- > From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp- > boun...@puck.nether.net] On Behalf Of alaerte vidali > Sent: Wednesday, April 28, 2010 2:19 PM > To: juniper-nsp@puck.nether.net > Subject: [j-nsp] Two RRs > > Hi, > > When configuring two route reflectors on same clusters for redundancy > purpose, does it matter if the backup reflector is configured inside > the > same group for clients? > > For example: > > group RRclients > type internal > cluster 1.1.1.1 > neighbor "client1" > neighbor "client2" > neighbor "RR2" > > group NonRRclients > type internal > neighbor "client3" > > Or is it mandatory configure the other RR out of the group where > cluster ID > is configured? > > Like this: > > group RRclients > type internal > cluster 1.1.1.1 > neighbor client1" > neighbor "client2" > > group NonRRclients > type internal > neighbor "client3" > neighbor "RR2" > > > I guess my question/confusion is because on Cisco we have explicity > command > to define neighbor as RRclient or notRRclient, and the backup RR is not > configured as client. > > As Juniper does not have so, I need to know if Juniper will consider > the > backup RR as client if I configure it inside the group where "cluster" > command is used.
Either approach will work... I guess the broader question is how you intend on getting this to work since each router will see its own Cluster-ID in the Cluster-ID-List and assume a loop is taking place. In most designs it is considered best practice to use unique Cluster-IDs on each of your Route Reflectors. Stefan Fouant, CISSP, JNCIEx2 www.shortestpathfirst.net GPG Key ID: 0xB5E3803D _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp