Forum Discussion
F5 Fundamental Lab-can't communicate between servers
- Apr 18, 2018
Hi Anuj,
To me, it looks like VMnet issue rather then the F5 issue. Try swapping VMnet2 with other interfaces.
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,
- anujg27_358584Apr 18, 2018Nimbostratus
Hannes,
Since I am just having issue with the pinging internal servers I have not configured anything else but the internal network. As advised by you I have tried to put the 10.2.0.11, .22 and .33 and my internal interfaces of BIGIP all on Lan Segment 1 and still the same issue. All webservers can ping each other but can't ping the big ip - 10.2.0.145
- Hannes_RappApr 18, 2018Nimbostratus
Did you set your BigIP VLAN configuration as tagged or untagged? It's possible you have a mismatch
First thing I'd check
- anujg27_358584Apr 22, 2018Nimbostratus
Untagged
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