Forum Discussion
Hi patrik,
To summarize:
- gtm private ip : 10.0.1.11
- ltm 1 ip : 10.0.0.11
- ltm 2 ip : 10.0.0.12
- ltm vs : 10.0.0.22
- ltm vs public ip (nat by firewall) : 1.2.3.4
If you want gtm to answer with private ip, gtm vs must be created with the same ip as ltm one
If you want gtm to answer with public ip, you must create the gtm vs with public ip (1.2.3.4) and define translation ip and port with ltm ip ( used to request ltm vs status)
Ltm and gtm does not share vs status with name but with ip / port
I think f5 must change this configuration because lots of deployment are with nat and we can't use vs discovery in such configuration! Maybe they are waiting IPv6 to solve this issue :-)
EDIT (included in comments bellow):
In gtm servers objects, you must have an object per gtm and an object per ltm
Same configuration as vs.. if gtm is behind nat device and need to communicate with another gtm device via internet, you must configure translation.
If you create link objects assigned to LTM object in GTM configuration, it must be defined with IP address of next hop of the appliance. if Link object is down, all related objects are down even if LTM VS status is up.
If GTM / LTM communication use the only internet link of a datacenter, Link configuration is not necessary as if link is down, GTM will not be able to get status... :-)