Unable to browse VIP from my LAPTOP of F5 VM LAB setup

Okay, so most likely vmnet1 is your management interface (on the 10.128.1.0/24 network), which leaves vmnet2 (192.168.1.0/24) and vmnet3 (172.16.0.0/16) for data plane interfaces 1.1 and 1.2. Your VIP is on 10.10.4.100, but that doesn't match any of the self-ip subnets. I'm guessing you also can't ping the VIP or any of the self-IPs from your laptop either. Is there a router between you and the external interface?

Hi Kevin,

You are very much right. Below is the ping output from my machine. I am new to VMware. So i am not sure if i have done something wrong with my VM setup.

C:>ping 10.128.1.10 ----------------------> F5 LTM Mgmt IP

Pinging 10.128.1.10 with 32 bytes of data: Reply from 10.128.1.10: bytes=32 time=10ms TTL=64 Reply from 10.128.1.10: bytes=32 time<1ms TTL=64 Reply from 10.128.1.10: bytes=32 time<1ms TTL=64 Reply from 10.128.1.10: bytes=32 time<1ms TTL=64

Ping statistics for 10.128.1.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 10ms, Average = 2ms

C:>ping 10.10.4.100 -----------------------> VIP which i created on F5 LTM

Pinging 10.10.4.100 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.

Ping statistics for 10.10.4.100: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:>ping 10.10.5.31 ---------------------> Self IP of external interface on F5 LTM

Pinging 10.10.5.31 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.

Ping statistics for 10.10.5.31: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:>

Okay, so to recap:

vmnet1 is your management interface on the 10.128.1.0/24 network. Your management IP should be something in this address space

vmnet2 is (probably) your external 1.1 interface on the 192.168.1.0/24 network. Your external virtual server IPs need to be in this address space and you should be able to ping these addresses from your laptop.

vmnet3 is (probably) your internal 1.2 interface on the 172.16.0.0/16 network. Your internal backend servers should be in this address space, the servers should be able to ping the BIG-IP self-ip, and the BIG-IP should be able to ping the servers.

VMware Workstation has an odd tendency to swap interfaces sometimes. The fist vmnet is always the management interface, but you may need to swap interfaces between the internal and external VLANs until you get a good ping from your laptop to the external VLAN's self-ip.

Superb...you are a champ...I got the idea from your above response. I changed the network of my Vmnet 2 from 192.168.1.0/24 to 10.10.0.0/16 and post this i was able to access the VIPs and the backend server on port 80 as well as on port 443.

Thanks a lot dear !!!