We are trying to use best practices for setting up a CF pair of FAS6040s on a VMWARE data network, but are having problems. Nothing on the data network can ping the netapp heads nor can the heads ping each other over the data network.
The switch administrator has verified that the switch stack is configured correctly. He says the switch reports that the netapps have not negotiated LACP yet.
I want to run by our netapp config commands to verify that I haven't missed any commands or done them in the wrong order.
The switch is a stack of two units. One head is supposed to favor one unit and the other head is supposed to favor the other unit.
Here are the rc commands.
vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 1 vif favor vifb vlan create vif0 201 202 ifconfig vif0-201 192.168.5.6 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.6 netmask 255.255.255.0 partner vif0-202
On the other head I have this:
vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 2 vif favor vifc vlan create vif0 201 202 ifconfig vif0-201 192.168.5.8 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.8 netmask 255.255.255.0 partner vif0-202
We are running ONTAP 7.3.2. Does this look correct?
ifconfig -a shows that all the physical interfaces have negotiated auto-1000t-fd-up full duplex
ping 192.168.15.8 (from 192.168.15.6) fails and vice versa.
To troubleshoot this, I think I will delete all the vifs, create vifc again, and put the VLANs on it and put the IPs on vifc-201 and vifc-202 and see what that gets me.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
Steve, what are the switches invlved here?
I actually had issues with a cisco 3750 recently that would refuse to do a proper LACP to ONTAP 7.3.3. I ultimately used the Cisco4948-10g next to it and it worked fine.
--tmac
On Wed, Aug 4, 2010 at 7:44 AM, Steve Losen scl@sasha.acc.virginia.edu wrote:
We are trying to use best practices for setting up a CF pair of FAS6040s on a VMWARE data network, but are having problems. Nothing on the data network can ping the netapp heads nor can the heads ping each other over the data network.
The switch administrator has verified that the switch stack is configured correctly. He says the switch reports that the netapps have not negotiated LACP yet.
I want to run by our netapp config commands to verify that I haven't missed any commands or done them in the wrong order.
The switch is a stack of two units. One head is supposed to favor one unit and the other head is supposed to favor the other unit.
Here are the rc commands.
vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 1 vif favor vifb vlan create vif0 201 202 ifconfig vif0-201 192.168.5.6 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.6 netmask 255.255.255.0 partner vif0-202
On the other head I have this:
vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 2 vif favor vifc vlan create vif0 201 202 ifconfig vif0-201 192.168.5.8 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.8 netmask 255.255.255.0 partner vif0-202
We are running ONTAP 7.3.2. Does this look correct?
ifconfig -a shows that all the physical interfaces have negotiated auto-1000t-fd-up full duplex
ping 192.168.15.8 (from 192.168.15.6) fails and vice versa.
To troubleshoot this, I think I will delete all the vifs, create vifc again, and put the VLANs on it and put the IPs on vifc-201 and vifc-202 and see what that gets me.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
I think tmac is on the right track looking at the switches. Your idea to troubleshoot with one VIF is sound, too. Please share how this goes.
You said the switch is a stack of two units, right? What switches? Do they support CrossStack Etherchannel, Multichassis EtherChannel (MEC), VPCs, SMLT/DMLT, DLAG or something similar? (Every vendor has a different name and not all "stackable" switches support this specific feature.) Are they configured correctly for such stacking? (All the right stack cables connected correctly. Any settings and/or licenses to enable the feature.)
If they DO support CrossStack EtherChannel, you should be using one LACP or multimode vif with all 4 ports.
If the switches don't support any of the above, make sure the ports of each first layer vif are on the same switch.
Share and enjoy!
Peter Learmonth Virtualization Solutions Architect
NetApp
peterl@netapp.com http://blogs.netapp.com/getvirtical/
-----Original Message----- From: Steve Losen [mailto:scl@sasha.acc.virginia.edu] Sent: Wednesday, August 04, 2010 4:44 AM To: toasters@mathworks.com Subject: Having trouble with VIFs and VLANs
We are trying to use best practices for setting up a CF pair of FAS6040s on a VMWARE data network, but are having problems. Nothing on the data network can ping the netapp heads nor can the heads ping each other over the data network.
The switch administrator has verified that the switch stack is configured correctly. He says the switch reports that the netapps have not negotiated LACP yet.
I want to run by our netapp config commands to verify that I haven't missed any commands or done them in the wrong order.
The switch is a stack of two units. One head is supposed to favor one unit and the other head is supposed to favor the other unit.
Here are the rc commands.
vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 1 vif favor vifb vlan create vif0 201 202 ifconfig vif0-201 192.168.5.6 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.6 netmask 255.255.255.0 partner vif0-202
On the other head I have this:
vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 2 vif favor vifc vlan create vif0 201 202 ifconfig vif0-201 192.168.5.8 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.8 netmask 255.255.255.0 partner vif0-202
We are running ONTAP 7.3.2. Does this look correct?
ifconfig -a shows that all the physical interfaces have negotiated auto-1000t-fd-up full duplex
ping 192.168.15.8 (from 192.168.15.6) fails and vice versa.
To troubleshoot this, I think I will delete all the vifs, create vifc again, and put the VLANs on it and put the IPs on vifc-201 and vifc-202 and see what that gets me.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
Hi
Were having trouble with Nortel Switches and LACP with our FAS3140's. Tried to use a stack of Nortel ERS5510, but the LACP trunks just wouldn't negotiate. I changed the swithes to Nortel ERS4548GT switches, worked immideatly without problems, using VLans and LACP.
/Uffe
-----Ursprungligt meddelande----- Från: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] För Steve Losen Skickat: den 4 augusti 2010 13:44 Till: toasters@mathworks.com Ämne: Having trouble with VIFs and VLANs
We are trying to use best practices for setting up a CF pair of FAS6040s on a VMWARE data network, but are having problems. Nothing on the data network can ping the netapp heads nor can the heads ping each other over the data network.
The switch administrator has verified that the switch stack is configured correctly. He says the switch reports that the netapps have not negotiated LACP yet.
I want to run by our netapp config commands to verify that I haven't missed any commands or done them in the wrong order.
The switch is a stack of two units. One head is supposed to favor one unit and the other head is supposed to favor the other unit.
Here are the rc commands.
vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 1 vif favor vifb vlan create vif0 201 202 ifconfig vif0-201 192.168.5.6 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.6 netmask 255.255.255.0 partner vif0-202
On the other head I have this:
vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 2 vif favor vifc vlan create vif0 201 202 ifconfig vif0-201 192.168.5.8 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.8 netmask 255.255.255.0 partner vif0-202
We are running ONTAP 7.3.2. Does this look correct?
ifconfig -a shows that all the physical interfaces have negotiated auto-1000t-fd-up full duplex
ping 192.168.15.8 (from 192.168.15.6) fails and vice versa.
To troubleshoot this, I think I will delete all the vifs, create vifc again, and put the VLANs on it and put the IPs on vifc-201 and vifc-202 and see what that gets me.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
-
Karlsson Ulf Ibrahim :ULK -
Learmonth, Peter -
Steve Losen -
tmac