[j-nsp] EX4200 resilience (VC vs 10GB cross-connect)
martin.levin at molndal.se
Wed Jan 13 16:12:18 EST 2010
No, it is currently not possible to upgrade a VC stack one member at a
time. I have told my Juniper contacts that this is an important feature
for us but so far no luck!
IT-strategy & planning
Från:Joe Hughes <joeyconcrete at gmail.com>
Till:<juniper-nsp at puck.nether.net>
Ärende:[j-nsp] EX4200 resilience (VC vs 10GB cross-connect)
Take the following scenario;
Several racks - each with a pair of EX3200 switches (cross-connected) -
with separate L3 uplinks back to a pair of aggregation layer EX4200s
from each rack switch), all running OSPF. I'm trying to understand if
are any drawbacks in making the two aggregation layer EX4200s a VC -
whether a simple L3 cross-connect using a LAG or the 10Gbps ports makes
sense, factoring in things like resilience, ease of upgrades etc.
If you go on the basis the two EX4200s are two distinct switches with a
path between them, it is easy for me to visualise how the network will
behave and (hopefully) understand how failover scenarios will play out.
obvious disadvantage of this is you are using up vital 10Gbps ports
could be used elsewhere, and it does seem non-sensical given the
speed VC ports (+ the other VC advantages).
I've read the VC Best practice guide and in all their examples, they
two sets of 2-switch VCs at the aggregation layer - which is making me
wonder if a single VC (of two switches) and treated as one switch poses
of a risk than simply two distinct switches. I'm guessing if you have
links back from each rack - each to a different member of the VC, then
'risks' are pretty much the same as having two separate switches? In
of software upgrades - is it possible to upgrade one member at a time
you would in a non-VC setup) so as to not interrupt connectivity from
access\rack switches? Are there any other situations\operations on a VC
would take both switches offline - further making it more sense to
have two switches, or two sets of 2 members VCs?
juniper-nsp mailing list juniper-nsp at puck.nether.net
More information about the juniper-nsp