Usual method is to perform a normal upgrade and the VC will manage the other member upgrades 1 by 1 until the entire VC is upgraded.
If you upgrade manually each member you will have non-operational devices in your VC. Rules are to have the same version on all VC members. If not it won't forward traffic or participate in the VC. Michael Gehrmann Hosting Support Specialist - Networks Macquarie Telecom -----Original Message----- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of R LAS Sent: Thursday, 27 November 2014 11:38 PM To: Bouzemarene, Farid ATS; 'juniper-nsp@puck.nether.net' Subject: Re: [j-nsp] Virtual Chassis Fabric question How does sw upgrade works on the VC fabric ? Can I upgrade one switch per time ? > From: farid.bouzemar...@avnet.com > To: dim0...@hotmail.com; juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] Virtual Chassis Fabric question > Date: Thu, 27 Nov 2014 11:51:40 +0000 > > Next release will support 32 members > I think it will be Released publicly very soon > > ----- Message d'origine ----- > De : R LAS [mailto:dim0...@hotmail.com] Envoyé : Thursday, November > 27, 2014 11:09 AM W. Europe Standard Time À : > juniper-nsp@puck.nether.net <juniper-nsp@puck.nether.net> Objet : > [j-nsp] Virtual Chassis Fabric question > > Today VC fabric is limited to 20 nodes, does anybody know if the is in > roadmap the support of more than 20 swtiches ? > > Best regards > > _______________________________________________ > 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 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
