--> so then in a 2node VC one node is Master one node is backup
> If they split the master will go down but the backup should survive as it
> is
> still half of the original cluster
>
> So this means you should make the part you want to survive to be the
> backup-RE and not the master-RE
>
> ---
Alexander Marhold wrote:
> Therefore if you want to put one node out of a 2 node VC you need to put the
> Master down not the backup
> Sounds strange but this is according to the rules stated below
Interesting twist :-)
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
AS43859
Tobias Heister wrote:
> >
> > Yes, no-split-detection did help.
>
> I would like to add to that. My point of view is that you do not
> always disable split-detection in a two member VC. You can do so if
> you know what that implies.
>
> The reasoning for the remaining node going into LC mode
Alexander Marhold
Gesendet: Donnerstag, 26. Juli 2018 09:52
An: 'Tobias Heister'; 'Victor Sudakov'; 'Pavel Lunin'
Cc: 'juniper-nsp'
Betreff: Re: [j-nsp] EX4200 virtual chassis problem, master going into
linecard mode
Hi
According to the documentation there should be the following behavior
[j-nsp] EX4200 virtual chassis problem, master going into
linecard mode
Hi,
On 26.07.2018 09:06, Victor Sudakov wrote:
>>> I don't like to explain what others say but I think yes. It's been known
>>> behavior since always: in a two-member VC always disable
split-detectio
Hi,
On 26.07.2018 09:06, Victor Sudakov wrote:
I don't like to explain what others say but I think yes. It's been known
behavior since always: in a two-member VC always disable split-detection.
You can google for other threads on this in this list.
It's always been kind of poorly documented.
Victor Sudakov wrote:
> Pavel Lunin wrote:
> > > > in a virtual chassis you could add:
> > > >
> > > > set virtual-chassis no-split-detection
> > > >
> > > > This will ensure that if both VC ports go down, the master routing
> > > engine carries on working.
> > >
> > > Are you referring to
Pavel Lunin wrote:
> > > in a virtual chassis you could add:
> > >
> > > set virtual-chassis no-split-detection
> > >
> > > This will ensure that if both VC ports go down, the master routing
> > engine carries on working.
> >
> > Are you referring to "Scenario B" in
> >
> > in a virtual chassis you could add:
> >
> > set virtual-chassis no-split-detection
> >
> > This will ensure that if both VC ports go down, the master routing
> engine carries on working.
>
> Are you referring to "Scenario B" in
> https://kb.juniper.net/InfoCenter/index?page=content=KB13879 ?
>
Catalin Dominte wrote:
>
>
> >
> > I've encountered an odd problem with adding EX4200s (running 12.3R6.6)
> > to Virtual Chassis with a nonprovisioned configuration file.
[dd]
> >
> > Looks fine, doesn't it? However, if I later poweroff the Backup switch
> > (BM0217040019), the current Master
If you only have 2 members in a virtual chassis you could add:
set virtual-chassis no-split-detection
This will ensure that if both VC ports go down, the master routing engine
carries on working.
Catalin Dominte | Senior Network Consultant
Nocsult Ltd | 11 Castle Hill | Maidenhead | Berkshire
Dear Colleagues,
I've encountered an odd problem with adding EX4200s (running 12.3R6.6)
to Virtual Chassis with a nonprovisioned configuration file.
According to documentation, I zeroize the second switch, power it off,
connect to the running switch and power it on. Some magic happens, and
12 matches
Mail list logo
