[j-nsp] Juniper EX2200 virtual-chassis

[Sachin Rai]

Hey Matt,

we have couple of EX2200 VC running in our infra. JUNOS version 12.3R3.4.

Few things to keep in mind:
1. JUNOS should be same on both switch

2. Make your VC as 'preprovisioned', so that 'you' can decide what part the new member will play in VC.
http://www.juniper.net/techpubs/en_US/junos13.2/topics/task/configuration/virtual-chassis-ex2200-cli.html

3. configure the ethernet ports to act as VC-ports, as 2200 do not have any fixed VCP. It can be the built-in ports or ports from uplink module.
http://www.juniper.net/techpubs/en_US/junos13.2/topics/task/configuration/virtual-chassis-ex2200-setting-vcp.html

Understanding EX2200 VC:
http://www.juniper.net/documentation/en_US/junos12.3/topics/concept/virtual-chassis-ex2200-virtual-chassis-understanding.html

Hope this helps.



________________________________________
From: juniper-nsp <juniper-nsp-bounces at puck.nether.net> on behalf of Raphael Mazelier <raph at futomaki.net>
Sent: Wednesday, February 3, 2016 7:24 PM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Juniper EX2200 virtual-chassis

On Ex2200 a standalone switch is already part of a virtual chassis.
You have to configure two VC ports, and to preprovision the other member
as backup (or linecard), it will boot and join the actual vc, without
interruption.

Be sure to have a backup of the configuration in case of disaster :)

--
Raphael Mazelier


Le 03/02/2016 14:34, Matthew Crocker a écrit :
>
> Hello,
>
>   I have an EX-2200 in production and would like to add another to create a virtual-chassis.     The current production unit will be the master and the new unit will be the backup.    Does creating a virtual-chassis cause a RE reset?   Will my production traffic take a hit?
>
> Thanks
>
> -Matt
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp