F5 Fundamental Lab-can't communicate between servers

run a tcpdump on the 1.2 interface, do you see the traffic enter?

Tried below command

[root@BIG-IP-test:Active:Standalone] config tcpdump -ni 1.2 tcp port 80 -w/var/tmp/http.cap tcpdump: listening on 1.2, link-type EN10MB (Ethernet), capture size 65535 bytes

<>>

and? what was the result?

i would do it without any filter and to screen first, to check any data is coming in. then perform a ping towards the F5 and see if you see that.

Thanks for helping me out. I understand you are trying to help but I am beginner with tcpdump and F5 so please don't get upset. I tried the below command with no filters but there is no traffic. please let me if below info is any help otherwise if you can tell me what command to run and I will do that.

[root@BIG-IP-test:Active:Standalone] config tcpdump -ni 1.2 tcp port 80 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on 1.2, link-type EN10MB (Ethernet), capture size 65535 bytes

I tried ping again from server to F5 but still can't ping

please without filter, so no

tcp port 80

the general idea is to make sure there is some traffic going on there, i.e. arp, perhaps spanning-tree, although that is doubtful on vmware. but i would like to make sure you don't have a vmware config issue.

Sorry about the delay, I removed the filter and receiving below arp output

[root@BIG-IP-test:Active:Standalone] config tcpdump -ni 1.2 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on 1.2, link-type EN10MB (Ethernet), capture size 65535 bytes 05:04:01.538995 ARP, Request who-has 10.2.0.33 tell 10.2.0.145, length 35 out slot1/tmm0 lis= 05:04:01.829990 ARP, Request who-has 10.2.0.11 tell 10.2.0.145, length 35 out slot1/tmm1 lis= 05:04:02.140067 ARP, Request who-has 10.2.0.22 tell 10.2.0.145, length 35 out slot1/tmm1 lis= 05:04:02.542342 ARP, Request who-has 10.2.0.33 tell 10.2.0.145, length 35 out slot1/tmm0 lis= 05:04:02.830053 ARP, Request who-has 10.2.0.11 tell 10.2.0.145, length 35 out slot1/tmm1 lis= 05:04:03.140270 ARP, Request who-has 10.2.0.22 tell 10.2.0.145, length 35 out slot1/tmm1 lis= 05:04:03.542078 ARP, Request who-has 10.2.0.33 tell 10.2.0.145, length 35 out slot1/tmm0 lis= 05:04:03.829821 ARP, Request who-has 10.2.0.11 tell 10.2.0.145, length 35 out slot1/tmm1 lis= 05:04:04.140054 ARP, Request who-has 10.2.0.22 tell 10.2.0.145, length 35 out slot1/tmm1 lis= 05:04:04.541731 ARP, Request who-has 10.2.0.33 tell 10.2.0.145, length 35 out slot1/tmm0 lis= 05:04:04.829547 ARP, Request who-has 10.2.0.11 tell 10.2.0.145, length 35 out slot1/tmm1 lis= 05:04:05.151254 ARP, Request who-has 10.2.0.22 tell 10.2.0.145, length 35 out slot1/tmm1 lis= 05:04:05.541915 ARP, Request who-has 10.2.0.33 tell 10.2.0.145, length 35 out slot1/tmm0 lis=

yeah that pretty much indicates some sort of network issue. assuming your big-ip has ip 10.2.0.145 and the servers are 10.2.0.11, .22 and .33.

the big-ip is looking for them, but they aint responding. you need to look at the VMware network level for this. if the others parts are working then it is probably some configuration issue.

In VMware player or workstation pro, Host-Only network is just for the purpose as the name reads. You use it to establish communication channel between your Host and Guests. This will be suitable for management interface (if no internet connectivity is needed) and external interface so that your host can access VIPs.

Guest-to-Guest communication does not work with Host-Only networking. If you run native instances of web-servers, then you can use Host-Only networking for internal segment, but if you virtualize them, you can not.

With virtualized web-servers, your internal network needs Guest-to-Guest connectivity (BigIP to servers, and servers to BigIP). Your best choice here is to use "Lan Segment" for the respective network adapter.

My own lab on VMware was built as follows:

NetAdapter 1 (Management). NAT for internet connectivity via mgmt interface (a)
NetAdapter 2 (Client-Side/External). Host-Only with host adapter and DHCP disabled
NetAdapter 3 (Server-Side/Internal). Lan Segment 1
NetAdapter 4 (HA). Lan Segment 2

a) NAT also hides the mgmt interface from other folks in same network. If you build
 your lab on top of a laptop that you occasionally take to a conference or workplace,
 you should never use bridged networking in place of NAT for internet connectivity

With this setup, I could freely pick whether I use VLAN tagging or not. Also the routing can be implemented cleanly as in production-like environments without the requirement to use SNAT. Asymmetric routing issues are avoided by design.

Good luck with the studies and regards,

In VMware player or workstation pro, Host-Only network is just for the purpose as the name reads. You use it to establish communication channel between your Host and Guests. This will be suitable for management interface (if no internet connectivity is needed) and external interface so that your host can access VIPs.

Guest-to-Guest communication does not work with Host-Only networking. If you run native instances of web-servers, then you can use Host-Only networking for internal segment, but if you virtualize them, you can not.

With virtualized web-servers, your internal network needs Guest-to-Guest connectivity (BigIP to servers, and servers to BigIP). Your best choice here is to use "Lan Segment" for the respective network adapter.

My own lab on VMware was built as follows:

NetAdapter 1 (Management). NAT for internet connectivity via mgmt interface (a)
NetAdapter 2 (Client-Side/External). Host-Only with host adapter and DHCP disabled
NetAdapter 3 (Server-Side/Internal). Lan Segment 1
NetAdapter 4 (HA). Lan Segment 2

a) NAT also hides the mgmt interface from other folks in same network. If you build
 your lab on top of a laptop that you occasionally take to a conference or workplace,
 you should never use bridged networking in place of NAT for internet connectivity

With this setup, I could freely pick whether I use VLAN tagging or not. Also the routing can be implemented cleanly as in production-like environments without the requirement to use SNAT. Asymmetric routing issues are avoided by design.

Good luck with the studies and regards,