I also have the same release running in VMware Fusion on Snow Leopard 10.6.5.
Tagged VLANs on vmnet interfaces are problematic on OSX. I couldn't get them to work reliably. My work around in duplicating our production config where VLANs are used extensively was to add vmnet interfaces and map the VLANs untagged 1-to-1 with the tmm interfaces.
To do this on Fusion 3.1.x the UI is of no value. You will need to edit /Library/Application\ Support/VMware\ Fusion/locations. Don't bother editing /Library/Application\ Support/VMware\ Fusion/networking - it is generated from locations anyway.
Edit locations to look something like this (I have 5 vmnets - one for management and 4 mapped to VLANs on the BIG-IP. VNET_8 is the built-in default NAT vmnet):
----------------------------------------------------------------------------------------------
remove_answer VNET_0_HOSTONLY_HOSTADDR
remove_answer VNET_0_HOSTONLY_NETMASK
answer VNET_0_HOSTONLY_HOSTADDR 10.99.200.253
answer VNET_0_HOSTONLY_NETMASK 255.255.255.0
remove_answer VNET_0_NAT
answer VNET_0_NAT yes
remove_answer VNET_0_DHCP
answer VNET_0_DHCP no
remove_answer VNET_1_HOSTONLY_HOSTADDR
remove_answer VNET_1_HOSTONLY_NETMASK
answer VNET_1_HOSTONLY_HOSTADDR 10.99.99.254
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
remove_answer VNET_1_NAT
answer VNET_1_NAT no
remove_answer VNET_1_DHCP
answer VNET_1_DHCP no
remove_answer VNET_2_HOSTONLY_HOSTADDR
remove_answer VNET_2_HOSTONLY_NETMASK
answer VNET_2_HOSTONLY_HOSTADDR 10.99.0.254
answer VNET_2_HOSTONLY_NETMASK 255.255.255.0
remove_answer VNET_2_NAT
answer VNET_2_NAT no
remove_answer VNET_2_DHCP
answer VNET_2_DHCP no
remove_answer VNET_3_HOSTONLY_HOSTADDR
remove_answer VNET_3_HOSTONLY_NETMASK
answer VNET_3_HOSTONLY_HOSTADDR 10.99.1.254
answer VNET_3_HOSTONLY_NETMASK 255.255.255.0
remove_answer VNET_3_NAT
answer VNET_3_NAT no
remove_answer VNET_3_DHCP
answer VNET_3_DHCP no
remove_answer VNET_4_HOSTONLY_HOSTADDR
remove_answer VNET_4_HOSTONLY_NETMASK
answer VNET_4_HOSTONLY_HOSTADDR 10.99.2.254
answer VNET_4_HOSTONLY_NETMASK 255.255.255.0
remove_answer VNET_4_NAT
answer VNET_4_NAT no
remove_answer VNET_4_DHCP
answer VNET_4_DHCP no
remove_answer VNET_5_HOSTONLY_HOSTADDR
remove_answer VNET_5_HOSTONLY_NETMASK
answer VNET_5_HOSTONLY_HOSTADDR 10.99.3.254
answer VNET_5_HOSTONLY_NETMASK 255.255.255.0
remove_answer VNET_5_NAT
answer VNET_5_NAT no
remove_answer VNET_5_DHCP
answer VNET_5_DHCP no
remove_answer VNET_8_HOSTONLY_HOSTADDR
remove_answer VNET_8_HOSTONLY_NETMASK
answer VNET_8_HOSTONLY_HOSTADDR 192.168.200.1
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
remove_answer VNET_8_NAT
answer VNET_8_NAT yes
remove_answer VNET_8_DHCP
answer VNET_8_DHCP yes
----------------------------------------------------------------------------------------------
Then run:
sudo /Library/Application\ Support/VMware\ Fusion/vmnet-cli -c; sudo /Library/Application\ Support/VMware\ Fusion/vmnet-cli --start
You're config will now be persistent across restarts.
Now edit your VMX that shipped with LTM VE. Mine, corresponding to the VMNET config above looks like this (as you can see I renamed the VM and its disk etc):
----------------------------------------------------------------------------------------------
.encoding = "UTF-8"
cleanShutdown = "FALSE"
config.version = "8"
displayName = "dmzlb (10.1.0.3341.1084)"
ethernet0.addressType = "generated"
ethernet0.connectionType = "custom"
ethernet0.generatedAddress = "00:0c:29:9e:3e:a8"
ethernet0.generatedAddressOffset = "0"
ethernet0.pciSlotNumber = "16"
ethernet0.present = "true"
ethernet0.startConnected = "true"
ethernet0.virtualDev = "vlance"
ethernet0.vnet = "vmnet0"
ethernet1.addressType = "generated"
ethernet1.connectionType = "custom"
ethernet1.generatedAddress = "00:0c:29:9e:3e:b2"
ethernet1.generatedAddressOffset = "10"
ethernet1.pciSlotNumber = "17"
ethernet1.present = "true"
ethernet1.startConnected = "true"
ethernet1.virtualDev = "e1000"
ethernet1.vnet = "vmnet1"
ethernet2.addressType = "generated"
ethernet2.connectionType = "custom"
ethernet2.generatedAddress = "00:0c:29:9e:3e:bc"
ethernet2.generatedAddressOffset = "20"
ethernet2.pciSlotNumber = "18"
ethernet2.present = "true"
ethernet2.startConnected = "true"
ethernet2.virtualDev = "e1000"
ethernet2.vnet = "vmnet2"
ethernet3.addressType = "generated"
ethernet3.connectionType = "custom"
ethernet3.generatedAddress = "00:0c:29:9e:3e:c6"
ethernet3.generatedAddressOffset = "30"
ethernet3.pciSlotNumber = "19"
ethernet3.present = "true"
ethernet3.startConnected = "true"
ethernet3.virtualDev = "e1000"
ethernet3.vnet = "vmnet5"
ethernet4.present = "FALSE"
extendedConfigFile = "dmzlb-10.1.0.3341.1084.vmxf"
floppy0.present = "FALSE"
guestOS = "other"
guestOSAltName = "BIGIP-10.1.0.3341.1084"
ide0:0.fileName = "dmzlb-10.1.0.3341.1084.vmdk"
ide0:0.mode = "persistent"
ide0:0.present = "true"
ide0:0.redo = ""
ide0:0.startConnected = "true"
ide0:0.writeThrough = "true"
memsize = "1024"
numvcpus = "1"
nvram = "luxor.nvram"
replay.filename = ""
replay.supported = "FALSE"
tools.remindInstall = "false"
tools.syncTime = "false"
tools.upgrade.policy = "manual"
uuid.bios = "56 4d 2a 5c fe 1c d4 81-ec 0b 8c 9e f1 9e 3e a8"
uuid.location = "56 4d 5d e8 c3 c6 fc 40-bf 2f 44 47 d5 82 7c 8d"
virtualHW.productCompatibility = "hosted"
virtualHW.version = "7"
vmotion.checkpointFBSize = "65536000"
----------------------------------------------------------------------------------------------
Adding interfaces to the BIG-IP is as simple as adding vmnets in the locations file above and adding interfaces to your VMX. It should be clear from the examples what you need to do. Pay attention to the generatedAddressOffset and use it to calculate your MACs correctly.
Dave