Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Multimode VIF with LACP between netapp filer and juniper switch.
2010-07-21
10:37 AM
6,111 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a FAS 2050 setup with 4 nics in a multimode LACP config. We are using vlan tagging load balance ISCSI, NFS traffic. We had the system setup and working properly using Cisco switches. We recently upgraded to Juniper ex4200 switches. We have been unable to connect to the filers with the new switches.
Each netapp filer has 4 1gb NICs. They are setup in a single multimode vif using vlan tagging to isolate ISCSI and NFS traffic.
The juniper switches are using the below config to trunk the ports the filers plug into. Anyone have any ideas of what we maybe missing?
version 10.0S6.1;
…
interfaces {
ge-0/0/0 {
ether-options {
802.3ad ae0;
}
}
ge-0/0/1 {
ether-options {
802.3ad ae0;
}
}
…
ge-1/0/0 {
ether-options {
802.3ad ae0;
}
}
ge-1/0/1 {
ether-options {
802.3ad ae0;
}
}
…
ae0 {
description "LACP VIF for NetApp";
aggregated-ether-options {
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ iscsi nfs snapmirrir_and_nfs ];
}
native-vlan-id default;
}
}
}
vlan {
unit 0 {
family inet {
address 10.10.11.1/24;
}
}
unit 1 {
family inet {
address 10.10.20.1/24;
}
}
unit 2 {
family inet {
address 10.10.30.1/24;
}
}
unit 3 {
family inet {
address 10.10.40.1/24;
}
}
}
}
}
vlans {
default {
vlan-id 4094;
l3-interface vlan.0;
}
iscsi {
vlan-id 20;
l3-interface vlan.1;
}
nfs {
vlan-id 30;
l3-interface vlan.2;
}
snapmirrir_and_nfs {
vlan-id 40;
l3-interface vlan.3;
}
}
4 REPLIES 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
change your VIF configuration to lacp (vice multimode). i think the juniper part is setup right. I have a similar configuration that works, except its dual 10G in an LACP vif. But I'm not vlan trunking.
How do you configure the vif side to recognize the vlans? do you just use alias IPs on the appropriate networks?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The filer vif was created as lacp (as near as I can remember). See below for the vif status output. I am assuming that VIF Type 'lacp' verifies that the VIF is indeed set to lacp.
Yes we are using alias IP addresses for each vlan network. As I said, we had the lacp configuration up and running on previous cisco switches.
vif status vif0
default: transmit 'IP Load balancing', VIF Type 'multi_mode', fail 'log'
vif0: 4 links, transmit 'IP Load balancing', VIF Type 'lacp' fail 'default'
VIF Status Up Addr_set
up:
e0a: state up, since 20Jul2010 15:48:03 (1+00:27:27)
mediatype: auto-1000t-fd-up
flags: enabled
active aggr, aggr port: e0b
input packets 35498, input bytes 4529386
input lacp packets 35253, output lacp packets 88116
output packets 88827, output bytes 11014091
up indications 2, broken indications 0
drops (if) 0, drops (link) 0
indication: up at 20Jul2010 15:48:03
consecutive 0, transitions 3
e1a: state up, since 20Jul2010 15:47:49 (1+00:27:41)
mediatype: auto-1000t-fd-up
flags: enabled
active aggr, aggr port: e0b
input packets 35282, input bytes 4516023
input lacp packets 35263, output lacp packets 88138
output packets 88189, output bytes 10931306
up indications 3, broken indications 1
drops (if) 0, drops (link) 0
indication: up at 20Jul2010 15:47:49
consecutive 0, transitions 4
e1b: state up, since 20Jul2010 15:47:49 (1+00:27:41)
mediatype: auto-1000t-fd-up
flags: enabled
active aggr, aggr port: e0b
input packets 125849, input bytes 10673512
input lacp packets 35263, output lacp packets 88139
output packets 88208, output bytes 10933374
up indications 3, broken indications 1
drops (if) 0, drops (link) 0
indication: up at 20Jul2010 15:47:49
consecutive 0, transitions 4
e0b: state up, since 20Jul2010 15:47:42 (1+00:27:48)
mediatype: auto-1000t-fd-up
flags: enabled
active aggr, aggr port: e0b
input packets 45802, input bytes 5230864
input lacp packets 35262, output lacp packets 88137
output packets 90731, output bytes 11210498
up indications 2, broken indications 0
drops (if) 0, drops (link) 0
indication: up at 20Jul2010 15:47:42
consecutive 0, transitions 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you reconfigure the switches to merge the iscsi/nfs/snapmirror_and_nfs vlans just for the moment? To see if that fixes the connectivity issue? Next I'd probably open a ticket with Juniper (or complain to your Juniper sales engineer) that Juniper equipment can't do something Cisco can. My only remaining concern is how are you setting which alias IP goes to which vlan? Might want to get into the weeds with NetApp regarding how vif's handle vlan trunking. Maybe their method isn't compatible with Junipers?
Wish I could be of more help.
-Ed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Anyone know how to verify what the default VLAN id is set to on the filer?
