Forum Discussion
NimbostratusF5 BIG IP and wmware workstation
AdminOk. I think it may be that your host doesn't have an IP on the 10.10.10.0/24 subnet? VMware Workstation would have installed some VMnet adapters on your local machine and you can assign it an IP address within that subnet so it can communicate via that
Nimbostratusprecisely vmware created the network 10.10.10.0/24 on my machine
Carte Ethernet VMware Network Adapter VMnet13 :
Suffixe DNS propre à la connexion. . . :
Adresse IPv6 de liaison locale. . . . .: fe80::bce3:aace:8d40:8ea3%31
Adresse IPv4. . . . . . . . . . . . . .: 10.10.10.1
Masque de sous-réseau. . . . . . . . . : 255.255.255.0
Passerelle par défaut. . . . . . . . . :
- buulam
I see... have you tried the other network binding methods, bridge, NAT in addition to host-only? And your PC_Client is onto attached to VMnet 13, can it reach the self IP's and VS's?
- farid95
yes I have already tried but still the same problem
- farid95
Summary of my LAB :
The Networks I created on vmware workstation
Vmnet 11: 192.168.10.0/24, host only
VMnet 13 : 10.10.10.0/24 , host only
Machine F5 sitting :
Network adaptater ----> custom vmnet11
Network adaptater 3 ----> custom vmnet13
External VLAN: interface 1.2, vlan untagged
IP self : 10.10.10.200 , vlan externalping OK from my pysic machine to management ip 192.168.10.200
ping NOK from my pysic machine to ip self 10.10.10.200 ( allow default , allow all) - buulam
Have you checked the MAC addressing to line up interface 1.2 with vmnet 13? Anything else different you can spot between vmnet 11?
You could go as far as trying to swap them around and re-assigning IP's for troubleshooting purposes as well
