[j-nsp] EX4200 VC Cabling

[ryanL]

we've got around 20 racks of vc stuff nowadays. some in 4 switch, most in 2
switch, a mix of ex4200 and now ex4300, ranging from 11.4R2.14 to newer
13.2X51-D25.2. the trick for me has always been to get one working and
configured as you like (including slice alternate), set auto-sw-update with
the image of choice, and then attach one switch at a time, allowing each
one to join the virtual chassis before adding another. once done, i always
snapshot slice alternate once more just for fun(?).

after that, really, it's been quite stable for my environment. purely layer
2, mind you, and i haven't tried an ISSU yet (no need).

oldest:

$ ssh -A fsaa-rs1 show system uptime | grep days
12:45AM  up 777 days, 18:51, 0 users, load averages: 0.58, 0.48, 0.41
12:45AM  up 788 days, 56 mins, 0 users, load averages: 0.00, 0.01, 0.00

On Tue, Sep 30, 2014 at 5:20 PM, Mike Gonnason <gonnason at gmail.com> wrote:

> I have 4 VC stacks of 2x EX4200 in X ring, with no issues. I am running
>  11.4R1, 11.4R2, 11.4R5, (they have deployed overtime, and have not had a
> reason to schedule downtime yet).
>
> Some are auto-config, others are pre-provisioned.
>
> -Mike Gonnason
>
> On Tue, Sep 30, 2014 at 5:01 PM, Skeeve Stevens <
> skeeve+junipernsp at eintellegonetworks.com> wrote:
>
> > Awesome.. thanks.
> >
> >
> > ...Skeeve
> >
> > *Skeeve Stevens - *eintellego Networks Pty Ltd
> > skeeve at eintellegonetworks.com ; www.eintellegonetworks.com
> >
> > Phone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeve
> >
> > facebook.com/eintellegonetworks ;  <http://twitter.com/networkceoau>
> > linkedin.com/in/skeeve
> >
> > twitter.com/theispguy ; blog: www.theispguy.com
> >
> >
> > The Experts Who The Experts Call
> > Juniper - Cisco - Cloud - Consulting - IPv4 Brokering
> >
> > On 1 October 2014 09:33, Ben Dale <bdale at comlinx.com.au> wrote:
> >
> > > I've never had any issues doing it either way.  It'll auto-detect the
> > > topology, even if you have only a single link.
> > >
> > > What I have seen though is a bunch of units (at least a couple of
> months
> > > back) coming out of the factory booting form the backup image (like the
> > > build image was corrupt), so it may have nothing to do with your VC
> build
> > > at all.
> > >
> > > Just upgrade to JTAC preferred, snapshot all members (and read a long
> > > novel while you wait for that to finish) and then reboot the whole
> > chassis.
> > >
> > >
> > > On 1 Oct 2014, at 9:23 am, Skeeve Stevens <
> > > skeeve+junipernsp at eintellegonetworks.com> wrote:
> > >
> > > > Hi all,
> > > >
> > > > We're doing a bunch of 2 x EX4200 in VC.
> > > >
> > > > Once we connect the VC cables, one of the Junos seems to be
> corrupted.
> > > >
> > > > We're currently using the ring X cabling.. but I have seen another
> > option
> > > > for a 2 member stack of | |
> > > >
> > > > Anyone got any thoughts?
> > > >
> > > > *********************************************************************
> > > > **
>  **
> > > > **  WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE
> **
> > > > **
>  **
> > > > **  It is possible that the primary copy of JUNOS failed to boot up
> **
> > > > **  properly, and so this device has booted from the backup copy.
> **
> > > > **
>  **
> > > > **  Please re-install JUNOS to recover the primary copy in case
> **
> > > > **  it has been corrupted and if auto-snapshot feature is not
> **
> > > > **  enabled.
>  **
> > > > **
> > > >
> > > > ...Skeeve
> > > >
> > > > *Skeeve Stevens - *eintellego Networks Pty Ltd
> > > > skeeve at eintellegonetworks.com ; www.eintellegonetworks.com
> > > >
> > > > Phone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeve
> > > >
> > > > facebook.com/eintellegonetworks ;  <http://twitter.com/networkceoau>
> > > > linkedin.com/in/skeeve
> > > >
> > > > twitter.com/theispguy ; blog: www.theispguy.com
> > > >
> > > >
> > > > The Experts Who The Experts Call
> > > > Juniper - Cisco - Cloud - Consulting - IPv4 Brokering
> > > > _______________________________________________
> > > > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > > > https://puck.nether.net/mailman/listinfo/juniper-nsp
> > >
> > >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>