It’s an unfortunate fact that even though Junipers have a great stacking feature (I think that’s how you classify the virtual chassis) there really is no documentation on how to use it with an EqualLogic SAN. There is one document published here
Of course this only shows a lag configuration.
Ok, I’m not a Juniper-even-close to expert. Don’t try this at home. Don’t trust these settings at all. But anyways, this is what I have come up with. A juniper consultant did look at the virtual chassis setup and gave his blessing for all that’s worth 🙂
—
So to start off I harassed ‘an reddit user’ who looked like he knew what was up with juniper and equallogic. I asked him for some tips, his response:
In all reality there isn’t much to configure differently.
Storm Control, LLDP, LLDP-MED, RSTP, igmp-snooping, Jumbo Frames (all based on environment). Otherwise it is all just like a regular switch.
—
I was finally able to get Juniper to recommend
I could find that if the VC is going to be with 2 members. If the two members loses the connectivity to each other, then both members will fall into linecard state and could create an outage. Thus to avoid this situation, we recommend to configure with “no-split-detection” as they will fall into Master to avoid network outage.
Please find more details under following link:
http://kb.juniper.net/InfoCenter/index?page=content&id=KB13879
—
Also randomly enough I ran into this page: http://kb.juniper.net/InfoCenter/index?page=content&id=KB12879
This is a neat trick that if you have a VC it will auto sync across both for you. It’s nice.
—
Ok, on to the much awaited config. Oh yeah there is also a VLAN and I turned on graceful-switchover.
## Last changed: 2014-10-09 12:12:58 UTC
version 12.3R7.7;
system {
services {
ssh {
protocol-version v2;
}
telnet;
netconf {
ssh;
}
web-management {
http;
}
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
commit synchronize;
}
chassis {
redundancy {
graceful-switchover;
}
alarm {
management-ethernet {
link-down ignore;
}
}
}
interfaces {
interface-range iscsi {
member-range xe-0/0/0 to xe-0/0/7;
member-range xe-1/0/0 to xe-1/0/7;
mtu 9216;
ether-options {
flow-control;
}
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members iscsi;
}
}
}
}
ge-0/0/0 {
unit 0 {
family ethernet-switching;
}
}
vlan {
unit 0 {
family inet {
address 131.107.2.35/16;
}
}
unit 15;
}
}
routing-options {
static {
route 0.0.0.0/0 next-hop 131.107.5.1;
}
}
protocols {
igmp-snooping {
vlan all;
}
rstp {
interface xe-0/0/0.0 {
edge;
}
interface xe-0/0/1.0 {
edge;
}
interface xe-0/0/2.0 {
edge;
}
interface xe-0/0/3.0 {
edge;
}
interface xe-0/0/4.0 {
edge;
}
interface xe-0/0/5.0 {
edge;
}
interface xe-0/0/6.0 {
edge;
}
interface xe-0/0/7.0 {
edge;
}
interface xe-1/0/0.0 {
edge;
}
interface xe-1/0/1.0 {
edge;
}
interface xe-1/0/2.0 {
edge;
}
interface xe-1/0/3.0 {
edge;
}
interface xe-1/0/4.0 {
edge;
}
interface xe-1/0/5.0 {
edge;
}
interface xe-1/0/6.0 {
edge;
}
interface xe-1/0/7.0 {
edge;
}
}
lldp {
interface all;
}
lldp-med {
interface all;
}
}
ethernet-switching-options {
voip;
storm-control {
interface all;
}
}
vlans {
default {
l3-interface vlan.0;
}
iscsi {
vlan-id 15;
interface {
xe-0/0/0.0;
xe-0/0/1.0;
xe-0/0/2.0;
xe-0/0/3.0;
xe-0/0/4.0;
xe-0/0/5.0;
xe-0/0/6.0;
xe-0/0/7.0;
xe-1/0/0.0;
xe-1/0/1.0;
xe-1/0/2.0;
xe-1/0/3.0;
xe-1/0/4.0;
xe-1/0/5.0;
xe-1/0/6.0;
xe-1/0/7.0;
}
l3-interface vlan.15;
}
}
virtual-chassis {
no-split-detection;
}
Michael Ellerbeck 