Forum Discussion
AltostratusF5 DNS Links Auto Discovery Assigning Incorrect Link to VS
Hi everyone,
I am using F5 GTM with Links Auto Discovery to automatically associate Links with Virtual Servers (VS). However, I encountered an issue where one of the Links is being incorrectly assigned.
After troubleshooting, I found that my ISP provided two different IP ranges:
- One subnet is used for underlying communication and routing between my network and the ISP.
- The other subnet is for public service IPs, which are assigned to my Virtual Servers (VS).
The problem arises because F5 detects the routing subnet (P2P link) instead of the service subnet, meaning the discovered Link’s IP does not match the VS IP subnet. As a result, VS instances are not automatically assigned to the correct Link.
I have many VS configurations, and I also expect to add more in the future. I would prefer not to manually assign the correct Link to each VS every time.
Is there a way to make F5 automatically associate VS with the correct Link when the underlying network and VS IPs are in different subnets?
Thanks for any suggestions!
- Nikoolayy1
MVP
Hi, Unfortunately I don't think it is. ""The BIG-IP DNS system does not automatically discover virtual severs on the BIG-IP LTM devices that reside behind a firewall NAT. You must manually add the BIG-IP LTM virtual servers to the BIG-IP DNS configuration."" Even if the LTM and GTM are on the same box as LLDP is used for link discovery.
Configuring BIG-IP DNS server objects for BIG-IP devices that reside behind a firewall NAT
VVVGot it, thanks! I’ll manually add the LTM virtual servers to the BIG-IP DNS configuration as suggested.
