Forum Discussion

David_Sudjiman_'s avatar
David_Sudjiman_
Icon for Nimbostratus rankNimbostratus
Sep 13, 2016

Connectivity Issue (Cannot Ping) BIG-IP Ext Interface from Server and from Mac via VMWARE Fusion

Hi Guys,

 

Apologies for the verbose output but I hope I've included all if not most of the required info and what I've done for checking.

 

I've been spending some time on the devcentral to look for answers but I still cannot make my BIG-IP network (External) to be connected to the servers on the same VMNET and my Mac either.

 

On one of the article in DevCentral (https://devcentral.f5.com/questions/f5-initial-setup-help-server-cannot-ping-network), I've also found that BIG-IP will drop traffic if it's not Virtual Server, SNAT, or NAT).

 

I hope this is not something really silly that I've wrongly configured.

 

application delivery
BIG-IP
LTM
vmware fusion

3 Replies

Sort By
  • David_Sudjiman_'s avatar
    David_Sudjiman_
    Icon for Nimbostratus rankNimbostratus
    Sep 13, 2016

    I've installed BIG-IP-11.3.0.39 on VMWARE Fusion (7.1.3) with details below.

      Network Adapter (0) - Mgmt     - VMNET 7 (10.1.0.0/24)
  Network Adapter 2   - External - VMNET 6 (192.168.1.0/24)
  Network Adapter 3   - Internal - VMNET 9 (10.2.0.0/24)
  Network Adapter 4   - HA       - VMNET 10 (10.3.0.0/24)

    From My Mac (El Capitan), I've setup the VMNET as below:

      Mgmt     - VMNET 7 (10.1.0.0/24)    - NAT (checked); Connect to Mac
  External - VMNET 6 (192.168.1.0/24) - Connect to Mac (Just for testing)
  Internal - VMNET 9 (10.2.0.0/24)    - NAT (checked); Connect to Mac (Just for testing)
  HA       - VMNET 10 (10.3.0.0/24)   - NAT (NOT CHECKED); Connect to Mac (NOT CHECKED)

    So far, From my Mac I can ping 

      MAC - VMNET 7  10.1.0.1/24,    I can    ping BIG-IP Mgmt 10.1.0.145
  MAC - VMNET 6  192.168.1.1/24, I CANNOT ping BIG-IP Ext  192.168.1.145
  MAC - VMNET 9  10.2.0.1/24,    I CANNOT ping BIG-IP Int  10.2.0.145

    Double checking on my Mac, I can see the configuration is as below

      vmnet6: flags=8863 mtu 1500
    ether 00:50:56:c0:00:06 
    inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
  vmnet7: flags=8863 mtu 1500
    ether 00:50:56:c0:00:07 
    inet 10.1.0.1 netmask 0xffffff00 broadcast 10.1.0.255
  vmnet8: flags=8863 mtu 1500
    ether 00:50:56:c0:00:08 
    inet 172.16.50.1 netmask 0xffffff00 broadcast 172.16.50.255
  vmnet9: flags=8863 mtu 1500
    ether 00:50:56:c0:00:09 
    inet 10.2.0.1 netmask 0xffffff00 broadcast 10.2.0.255

    Checking on my BIG-IP, the interfaces are configured as below.

    HA   inet addr: 10.3.0.145 mask: 255.255.255.0
eth0 inet addr: 10.1.0.145 mask: 255.255.255.0
eth1 inet addr: None configured
eth2 inet addr: None configured
eth3 inet addr: None configured
ext  inet addr: 192.168.1.145 mask: 255.255.255.0 (Note. I CANNOT Ping this from Mac)
int  inet addr: 10.2.0.145    mask: 255.255.255.0 (Note. I CANNOT Ping this from Mac)

    Particularly on network 10.2.0.0/24 (Internal), I've also setup a server with IP of 10.2.0.11/24. I've put this interface on the same VMNET 9 10.2.0.0/24. My Mac can ping 10.2.0.11 and vice-versa.

    And neither my server 10.2.0.11/24 CANNOT ping 10.2.0.145 either and vice-versa.

    Below also my VMNET details

    $ cat /Library/Preferences/VMware\ Fusion/networking
VERSION=1,0
answer VNET_10_DHCP no
answer VNET_10_HOSTONLY_NETMASK 255.255.255.0
answer VNET_10_HOSTONLY_SUBNET 10.3.0.0
answer VNET_10_VIRTUAL_ADAPTER no
answer VNET_1_DHCP yes
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 172.16.242.0
answer VNET_1_VIRTUAL_ADAPTER yes
answer VNET_2_DHCP no
answer VNET_2_HOSTONLY_NETMASK 255.255.255.0
answer VNET_2_HOSTONLY_SUBNET 172.16.1.0
answer VNET_2_VIRTUAL_ADAPTER yes
answer VNET_3_DHCP no
answer VNET_3_HOSTONLY_NETMASK 255.255.255.0
answer VNET_3_HOSTONLY_SUBNET 172.16.2.0
answer VNET_3_VIRTUAL_ADAPTER yes
answer VNET_4_DHCP no
answer VNET_4_HOSTONLY_NETMASK 255.255.255.0
answer VNET_4_HOSTONLY_SUBNET 172.16.3.0
answer VNET_4_VIRTUAL_ADAPTER yes
answer VNET_5_DHCP no
answer VNET_5_HOSTONLY_NETMASK 255.255.255.0
answer VNET_5_HOSTONLY_SUBNET 172.16.10.0
answer VNET_5_NAT no
answer VNET_5_VIRTUAL_ADAPTER yes
answer VNET_6_DHCP no
answer VNET_6_HOSTONLY_NETMASK 255.255.255.0
answer VNET_6_HOSTONLY_SUBNET 192.168.1.0
answer VNET_6_NAT no
answer VNET_6_VIRTUAL_ADAPTER yes
answer VNET_7_DHCP no
answer VNET_7_HOSTONLY_NETMASK 255.255.255.0
answer VNET_7_HOSTONLY_SUBNET 10.1.0.0
answer VNET_7_NAT yes
answer VNET_7_VIRTUAL_ADAPTER yes
answer VNET_8_DHCP yes
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 172.16.50.0
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes
answer VNET_9_DHCP no
answer VNET_9_HOSTONLY_NETMASK 255.255.255.0
answer VNET_9_HOSTONLY_SUBNET 10.2.0.0
answer VNET_9_NAT yes
answer VNET_9_VIRTUAL_ADAPTER yes
add_bridge_mapping en0 -1
add_bridge_mapping en4 -1
add_bridge_mapping en5 -1
  • TayF5un's avatar
    TayF5un
    Icon for Nimbostratus rankNimbostratus
    Sep 20, 2016

    Did you check vlan and self-ip addr. and could you please check port lockdown settings of self-IPs.

     

  • andrewbytes's avatar
    andrewbytes
    Icon for Altocumulus rankAltocumulus
    May 30, 2019

    I solved this yesterday;

    The ROUTE for management server needs to be WHATEVER Fusion decides, not what the article decides. In my case, the article said change the route to "10.128.1.1" for the route, and Fusion already decided on 10.128.1.2 as the route. in the console, type "CONFIG" and correct this, or re-install from scratch selecting the correct network interfaces and point it to the right place.