MacBook Pro Maverick Vmware Fusion F5-BIG-VE-LAB

I also experienced this error. I noticed that the OVA file was saved as an OVF when I downloaded it. I changed the file extension back to OVA and the Import function in Fusion worked as expected.

maybe it posted weirdly, the link is very much still alive:

Laptop Load Balancing with BIG-IP VE

from terminal:

cd /Library/Preferences/VMware\ Fusion/
sudo vi networking

then I went to the last line of vmnet1 and hit the o key, which will insert an open line, then I just pasted everything in my post from above with vmnet2 through vmnet7. When that's there, hit the escape key, then the : key, then keys w, q, and ! and hit enter. After updating that file, restart vmware fusion and you should be good to go. you can use another editor like emacs, or even open it in the GUI textpad app if vi is not comfortable for you.

yep, here's my additions to that file, MC (just slipped them in between vnet1 and vnet8):

answer VNET_2_DCHP no
answer VNET_2_HOSTONLY_NETMASK 255.255.255.0
answer VNET_2_HOSTONLY_SUBNET 192.168.102.0
answer VNET_2_VIRTUAL_ADAPTER yes
answer VNET_2_VIRTUAL_ADAPTER_ADDR 192.168.102.1
answer VNET_3_DCHP no
answer VNET_3_HOSTONLY_NETMASK 255.255.255.0
answer VNET_3_HOSTONLY_SUBNET 192.168.103.0
answer VNET_3_VIRTUAL_ADAPTER yes
answer VNET_3_VIRTUAL_ADAPTER_ADDR 192.168.103.1
answer VNET_4_DCHP no
answer VNET_4_HOSTONLY_NETMASK 255.255.255.0
answer VNET_4_HOSTONLY_SUBNET 192.168.104.0
answer VNET_4_VIRTUAL_ADAPTER yes
answer VNET_4_VIRTUAL_ADAPTER_ADDR 192.168.104.1
answer VNET_5_DCHP no
answer VNET_5_HOSTONLY_NETMASK 255.255.255.0
answer VNET_5_HOSTONLY_SUBNET 192.168.105.0
answer VNET_5_VIRTUAL_ADAPTER yes
answer VNET_5_VIRTUAL_ADAPTER_ADDR 192.168.105.1
answer VNET_6_DCHP no
answer VNET_6_HOSTONLY_NETMASK 255.255.255.0
answer VNET_6_HOSTONLY_SUBNET 192.168.106.0
answer VNET_6_VIRTUAL_ADAPTER yes
answer VNET_6_VIRTUAL_ADAPTER_ADDR 192.168.106.1
answer VNET_7_DCHP no
answer VNET_7_HOSTONLY_NETMASK 255.255.255.0
answer VNET_7_HOSTONLY_SUBNET 192.168.107.0
answer VNET_7_VIRTUAL_ADAPTER yes
answer VNET_7_VIRTUAL_ADAPTER_ADDR 192.168.107.1
`

after a restart of vmware fusion, you should be good to go to build out your lab in a more flexible way. you can confirm by hitting ifconfig:

`jasonmac:VMware Fusion jrahm$ ifconfig | grep vmnet
vmnet1: flags=8863 mtu 1500
vmnet2: flags=8863 mtu 1500
vmnet3: flags=8863 mtu 1500
vmnet4: flags=8863 mtu 1500
vmnet5: flags=8863 mtu 1500
vmnet6: flags=8863 mtu 1500
vmnet7: flags=8863 mtu 1500
vmnet8: flags=8863 mtu 1500

Grr... Apologies for the multiple post... There's no feedback from here any more when you hit the post button...

Fusion can (At least the version I was using could) be configured by editing the config files directly. There's no fancy GUI to do most of it (Not sure why they dumb it down for Mac users), but the product is essentially the same...

H

I finally got this to work last night and it was thrilling and disappoint at the same time. The disappointment came from the limitations of fusion.

1. open a terminal session and type in the following command - cat /Library/Preferences/VMware\ Fusion/networking

output will look like this:

answer VNET_1_DHCP yes answer VNET_1_DHCP_CFG_HASH 92E246053EEA6B7CB0B82DC219EF1718D17C33E9 answer VNET_1_HOSTONLY_NETMASK 255.255.255.0 answer VNET_1_HOSTONLY_SUBNET 172.16.253.0 answer VNET_1_VIRTUAL_ADAPTER yes answer VNET_3_DHCP no answer VNET_3_NAT no answer VNET_3_VIRTUAL_ADAPTER no answer VNET_8_DHCP yes answer VNET_8_DHCP_CFG_HASH 62D54CAB586054004EC0B057F4EF4E7704F14749 answer VNET_8_HOSTONLY_NETMASK 255.255.255.0 answer VNET_8_HOSTONLY_SUBNET 192.168.185.0 answer VNET_8_NAT yes answer VNET_8_VIRTUAL_ADAPTER yes add_bridge_mapping en0 2

If you look closely and VNET 1 and VNET 8, it gives you the 2 subnets that you can use to set up your VM devices so you can access your device from the external interface. In this case, the subnets are 172.16.253.0/24 and 192.168.185.0/24.

Set your adapters to the following and you should be home free (I configured my external interface on port 1.1 on the LTM)

net adapter 1 = bridged net adapter 2 = host only net adapter 3 = host only net adapter 4 = host only

add a default route for your external interface. ( I used 172.16.253.1 ). I also ran a continuos ping in terminal until I saw the external gate respond and also the external interface on my LTM.

Sweet... Loading from *.iso worked great.

I plan to work up a how-to, to share.

Thanks

Same... Im not sure I've ever got one of the actual imports going since the original v10 test edition came out originally...

Once you've installed just add the license like normal

H

i always build from .iso on workstation and fusion products. Just specify 2 CPU, 7G ram (if enabling more than 2 modules, 4G if not), and then a 100G disk. After the basic vm configuration, attach the .iso, power up, and push enter twice at the prompts and you should be good to go.