Forum Discussion
BIGIP VE under Fusion Pro 10
Hi,
trying to install a BIGIP VE on VMware Fusion 10 (Trial). (I originally used Parallels for Mac, but I couldn't license it as it was identified as platform "")
I'm following this guide: https://devcentral.f5.com/articles/f5-developer-edition-installing-big-ip-on-vmware-fusion-8
To rule out mistakes, I applied this interface config: https://devcentral.f5.com/articles/vmware-fusion-custom-networking-for-big-ip-ve-lab
However, when I try to run
tmsh create net vlan external interfaces add { 1.1 { untagged } }
I get: 01070256: Requested VLAN member (1.1) is not valid
tmsh show net interface all
: https://i.imgur.com/vg7nbjd.png
On my laptop:
$ 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
vmnet9: flags=8863 mtu 1500
vmnet10: flags=8863 mtu 1500
vmnet11: flags=8863 mtu 1500
- Chase_AbbottEmployee
From macOS Terminal:
cat /Library/Preferences/VMware\ Fusion/networking
What is your output? You should see a bunch of stuff similar to this:
cat /Library/Preferences/VMware\ Fusion/networking VERSION=1,0 answer VNET_1_DHCP yes answer VNET_1_DHCP_CFG_HASH 4096360A66F5587A10B999CC4758A010E918F6B6 answer VNET_1_HOSTONLY_NETMASK 255.255.255.0 answer VNET_1_HOSTONLY_SUBNET 192.168.186.0 answer VNET_1_VIRTUAL_ADAPTER yes answer VNET_2_DHCP yes answer VNET_2_DHCP_CFG_HASH EDE43DD0AE3EC6967BE41D250865C4010F7B01E9 answer VNET_2_HOSTONLY_NETMASK 255.255.255.0 answer VNET_2_HOSTONLY_SUBNET 10.128.1.0 answer VNET_2_VIRTUAL_ADAPTER yes
.....
- NiHo_202842Cirrostratus
From the page you mentioned, I put in this:
VERSION=1,0 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_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_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_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_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_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.1a
- Chase_AbbottEmployee
Hrm. If you configure the interfaces from the virtual machine settings, are they available to modify? Can you go into "Network Adapter 2" and select a vmnetX? My worry is that Fusion in a trial may not let you use more than X adapters.
- NiHo_202842Cirrostratus
Hmmm, I suppose not? : https://i.imgur.com/n2YVGXt.png
- Chase_AbbottEmployee
If that's the case then you should be able to use mgmt and the 1.0 interface if the trial does not allow you to add further network adapters.
Just use the 1.0 interface to hairpin traffic, not an uncommon solution in smaller cloud deployments. Traffic will go in and exit that same interface but you can still config virtual servers and play around with the features.
- NiHo_202842Cirrostratus
Wait, I misread that. I can add more interfaces; https://i.imgur.com/lVVy6hC.png
- NiHo_202842Cirrostratus
It's available, I added a bunch of vmnet interfaces in my previous screenshot as proof.
- Chase_AbbottEmployee
Sorry, missed that. If you restart BIG-IP following the additional interface creation do the interfaces show as uninitialized?
- NiHo_202842Cirrostratus
Hello @Chase, I rebooted the F5 several times
- Boggs_5738Nimbostratus
your bigip shows that it has not activated its license yet per screenshot. I suggest you activate the license first then move on to configuration.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com