[prev in list] [next in list] [prev in thread] [next in thread] 

List:       toasters
Subject:    SV: Having trouble with VIFs and VLANs
From:       "Karlsson Ulf Ibrahim :ULK" <ulk () forsmark ! vattenfall ! se>
Date:       2010-08-05 11:33:17
Message-ID: 6DB2631F05FDEF4D9F6F633E2FC8C7CF0F379AC3 () PMSX1M ! fka ! forsmark ! vattenfall ! se
[Download RAW message or body]

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
> 
> 
> 


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic