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 | SL6 4AA | Phone: +44 
(0)1628 302 007
VAT registration number: GB 180957674 | Company registration number: 08886349
P Please consider the environment - Do you really need to print this email?

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the email and its 
attachments from all computers.
On 25 Jul 2018, 08:27 +0100, Victor Sudakov <v...@mpeks.tomsk.su>, wrote:
> 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
> voila:
>
> > show virtual-chassis
>
> Virtual Chassis ID: 915f.3bb3.ff60
> Virtual Chassis Mode: Enabled
> Mstr Mixed Neighbor List
> Member ID Status Serial No Model prio Role Mode ID Interface
> 0 (FPC 0) Prsnt BM0213317561 ex4200-24t 128 Master* N 1 vcp-0
> 1 (FPC 1) Prsnt BM0217040019 ex4200-24t 128 Backup N 0 vcp-0
>
> Member ID for next new member: 2 (FPC 2)
>
> Looks fine, doesn't it? However, if I later poweroff the Backup switch
> (BM0217040019), the current Master switch (BM0213317561) goes into linecard 
> (sic!)
> mode! And I lose ssh access to it. I can undo the disaster only from the
> serial console.
>
> What am I doing wrong? Or if it's a bug, is there a workaround?
>
> --
> Victor Sudakov, VAS4-RIPE, VAS47-RIPN
> AS43859
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to