Thanks all for your tips. When we have both nodes with the same priority 255, will there be any change in the mastership when both nodes powered off and powered on together?
Further, is it mandatory to enable the "no-split-detection" in this case? Thanks. On Thu, Oct 4, 2012 at 8:03 AM, Luca Salvatore <l...@ninefold.com> wrote: > I always configure my VC-EX switches all with priority 255. > If they have different priorities you can't manually failover and as > mentioned other weird stuff happens. > > Luca > > > -----Original Message----- > From: juniper-nsp-boun...@puck.nether.net [mailto: > juniper-nsp-boun...@puck.nether.net] On Behalf Of Eugeniu Patrascu > Sent: Thursday, 4 October 2012 3:46 AM > To: Muruganandham M > Cc: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] GRES on EX-Virtual chassis > > On Wed, Oct 3, 2012 at 8:51 AM, Muruganandham M <sedhuan...@gmail.com> > wrote: > > Hello, > > > > I am referring the following link. > > > > http://www.juniper.net/techpubs/en_US/junos10.3/topics/task/configurat > > ion/virtual-chassis-gres-cli.html > > > > Is it mandatory to configure the mastership-priority to 255 to enable > > GRES on the VC ? > > IIRC, when you have a two switch EX4200 VC, it's mandatory to set the > priority manually to 255 on both members, otherwise weird stuff might > happen. I run a pair like this and it's been stable for more than a year > now. > > Eugeniu > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- *Thanks* *Muruganandham M* _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
