Wes,

There is good news and bad news.

All the Vifs have to be tagged, the problem you will find that is that on all switches the native vlan is always untagged.

You will need to create vifs for all the vlans you want to use including Vlan1, which is usually the native vlan (in the cisco world at least)

You then will need to change the native vlan on the switch ports that are connected to the filer, I have had trouble with some cisco switches (3750G) as the commands to be entered in a specific order.

So in the case of out filer, we have 3 interfaces

Vif0-1 Vif0-21 Vif0-22

And on the switch side we have Vlan99 as the native vlan. For the ports and trunks connected to the filer

The easiest way I have found of setting all this up on the filer, is change the required files and reboot it.

Hope this helps

Matt

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Wes Hardin Sent: 13 July 2007 19:18 To: toasters@mathworks.com Subject: Adding VLANs to a vif

I have a FAS3020 with all four onboard gig-e ports trunked as vif0. I am wanting to add a VLAN interface to my current vif for my backup network.

Will the following lines in /etc/rc work? (Sorry for the wrapping)

vif create multi vif0 -b ip e0a e0c e0b e0d vlan create -g off vif0 4093 ifconfig vif0 `hostname`-vif0 mediatype auto netmask 255.255.248.0 partner vif0 ifconfig vif0-4093 `hostname`-backup netmask 255.255.0.0 partner vif0-4093

I still want vif0 to act as it does now, sending and receiving untagged frames, but the new interface, vif0-4093, sending tagged frames.

I tried to simulate this with the ONTAP simulator, but it wasn't supported on my setup and all the documentation I can find doesn't mention the original interface again after creating the VLAN.

Thanks,