Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Netapp: toasters

Having trouble with VIFs and VLANs

 

 

Netapp toasters RSS feed   Index | Next | Previous | View Threaded


scl at sasha

Aug 4, 2010, 4:44 AM

Post #1 of 18 (9581 views)
Permalink
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 [at] virginia phone: 434-924-0640

University of Virginia ITC Unix Support


tmacmd at gmail

Aug 4, 2010, 5:31 AM

Post #2 of 18 (9465 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

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 [at] sasha> 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 [at] virginia    phone: 434-924-0640
>
> University of Virginia               ITC Unix Support
>
>
>


Peter.Learmonth at netapp

Aug 4, 2010, 8:01 AM

Post #3 of 18 (9451 views)
Permalink
RE: Having trouble with VIFs and VLANs [In reply to]

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 [at] netapp
http://blogs.netapp.com/getvirtical/


-----Original Message-----
From: Steve Losen [mailto:scl [at] sasha]
Sent: Wednesday, August 04, 2010 4:44 AM
To: toasters [at] mathworks
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 [at] virginia phone: 434-924-0640

University of Virginia ITC Unix Support


scl at sasha

Aug 4, 2010, 9:53 AM

Post #4 of 18 (9457 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

Thanks to everyone for all the helpful suggestions.

Through experimentation we discovered that we cannot mix LACP
and VLAN tagging. We don't know if it's the switch or ONTAP
and we haven't seen any documentation or bug reports.

The switch is a stack of two Nortel units. Didn't note the model,
but each unit has 48 ports each 1Gbit.

So we reconfigured the switch for "multi" trunking and VLAN
tagging and all is working as expected:

First head:

vif create multi vifb -b ip e0b e6b
vif create multi 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

Second head:

vif create multi vifb -b ip e0b e6b
vif create multi 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


Steve Losen scl [at] virginia phone: 434-924-0640

University of Virginia ITC Unix Support


tmacmd at gmail

Aug 4, 2010, 10:05 AM

Post #5 of 18 (9459 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

I am successfully doing LACP and VLAN tagging on:
Cisco 4948-10G
Cisco 4900M

I was unable to get it to work on a Cisco 3750.


On Wed, Aug 4, 2010 at 12:53 PM, Steve Losen <scl [at] sasha> wrote:
>
> Thanks to everyone for all the helpful suggestions.
>
> Through experimentation we discovered that we cannot mix LACP
> and VLAN tagging.   We don't know if it's the switch or ONTAP
> and we haven't seen any documentation or bug reports.
>
> The switch is a stack of two Nortel units.  Didn't note the model,
> but each unit has 48 ports each 1Gbit.
>
> So we reconfigured the switch for "multi" trunking and VLAN
> tagging and all is working as expected:
>
> First head:
>
> vif create multi vifb -b ip e0b e6b
> vif create multi 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
>
> Second head:
>
> vif create multi vifb -b ip e0b e6b
> vif create multi 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
>
>
> Steve Losen   scl [at] virginia    phone: 434-924-0640
>
> University of Virginia               ITC Unix Support
>
>
>


scl at sasha

Aug 4, 2010, 10:10 AM

Post #6 of 18 (9458 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

> I am successfully doing LACP and VLAN tagging on:
> Cisco 4948-10G
> Cisco 4900M
>
> I was unable to get it to work on a Cisco 3750.
>

LACP worked on our Nortel stack without VLAN tagging.

Steve Losen scl [at] virginia phone: 434-924-0640

University of Virginia ITC Unix Support


scl at sasha

Aug 4, 2010, 10:28 AM

Post #7 of 18 (9449 views)
Permalink
RE: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster


scl at sasha

Aug 4, 2010, 10:43 AM

Post #8 of 18 (9456 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster


Jeffrey.Steiner at netapp

Aug 4, 2010, 11:26 AM

Post #9 of 18 (9460 views)
Permalink
RE: Having trouble with VIFs and VLANs [In reply to]

ONTAP itself does LACP with VLAN tagging fine. I've used it on a lot of
different Cisco configurations, but Nortel always was a pain to
configure. It took them ages to support LACP at all. I also remember an
annoying behavior where changes in VLANs would silently result in
changes to the IP ranges permitted on various subnets, so you could
easily end up with a properly configured trunk and properly configured
VLANs, but the actual IP ranges permitted on those VLANs by the switch
prevented anything from working right.

>-----Original Message-----
>From: Steve Losen [mailto:scl [at] sasha]
>Sent: Wednesday, August 04, 2010 6:53 AM
>To: toasters [at] mathworks
>Subject: Re: Having trouble with VIFs and VLANs
>
>
>Thanks to everyone for all the helpful suggestions.
>
>Through experimentation we discovered that we cannot mix LACP
>and VLAN tagging. We don't know if it's the switch or ONTAP
>and we haven't seen any documentation or bug reports.
>
>The switch is a stack of two Nortel units. Didn't note the model,
>but each unit has 48 ports each 1Gbit.
>
>So we reconfigured the switch for "multi" trunking and VLAN
>tagging and all is working as expected:
>
>First head:
>
>vif create multi vifb -b ip e0b e6b
>vif create multi 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
>
>Second head:
>
>vif create multi vifb -b ip e0b e6b
>vif create multi 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
>
>
>Steve Losen scl [at] virginia phone: 434-924-0640
>
>University of Virginia ITC Unix Support
>


scl at sasha

Aug 4, 2010, 3:17 PM

Post #10 of 18 (9446 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster


tmacmd at gmail

Aug 4, 2010, 5:24 PM

Post #11 of 18 (9435 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster


lists at up-south

Aug 4, 2010, 5:41 PM

Post #12 of 18 (9443 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

Anybody else getting these spam messages ?

Or is it just me


scl at sasha

Aug 4, 2010, 11:45 PM

Post #13 of 18 (9422 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster


scl at sasha

Aug 5, 2010, 2:09 AM

Post #14 of 18 (9415 views)
Permalink
RE: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster


Jeffrey.Steiner at netapp

Aug 5, 2010, 2:30 AM

Post #15 of 18 (9415 views)
Permalink
RE: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster


ulk at forsmark

Aug 5, 2010, 4:33 AM

Post #16 of 18 (9424 views)
Permalink
SV: Having trouble with VIFs and VLANs [In reply to]

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 [at] mathworks
> [mailto:owner-toasters [at] mathworks] För Steve Losen
> Skickat: den 4 augusti 2010 13:44
> Till: toasters [at] mathworks
> Ä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 [at] virginia phone: 434-924-0640
>
> University of Virginia ITC Unix Support
>
>
>


scl at sasha

Aug 5, 2010, 4:46 AM

Post #17 of 18 (9417 views)
Permalink
RE: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster


tmacmd at gmail

Aug 5, 2010, 4:50 AM

Post #18 of 18 (9414 views)
Permalink
Re: Having trouble with VIFs and VLANs [In reply to]

Dear Sir/Madam,

Your email was unable reach the intended person that you were sending it to.
For more information on our business please click on the following link:
http://www.downwind.com.au/avdir/rd.php?id=7564"]Click here for our website
We look forward to your continued business in the future.

Regards,
Webmaster

Netapp toasters RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.