Forum Discussion

Rohit_Singla_17's avatar
Rohit_Singla_17
Icon for Nimbostratus rankNimbostratus
Oct 31, 2016

GTM Monitors internal LTM, but I need Public IP as Answer

Hi Team, I have a very simple setup. I need someone to answer with a tested/verified solution. Please trust that I am writing this thread after breaking my head with Translation IPs/ Dependency Lists etc.

 

Scenario Simple :

 

  1. GTM is in DMZ
  2. LTM is in Core

GTM monitors the LTM and it is able to discover all the VS of the LTM All VS on LTM as Private IPs.

 

Is there a way that I can keep monitoring these private IP VS but for wide-ips, i can answer with public-ips.

 

So is there a way, where we can have a mapping of public-ip and private-ip vs.

 

My GTM is not supposed to go to internet and monitor the public-ip directly, So i can only monitor my LTM with private IPs, but GTM need to answer with public-ips based on those private ips vs.

 

Tested/Verified tips will be very helpful.

 

3 Replies

  • Hi,

     

    when working with natted IP, GTM configuration is not optimized...

     

    you must not use virtual server discovery but create VS manually in GTM server...

     

    each VS must be create with Public IP as main address and private IP in translation address.

     

  • Kevin_K_51432's avatar
    Kevin_K_51432
    Historic F5 Account

    Hi Rohit, I believe the intention is to have GTM checking the same path as the DNS request, so probably you should point GTM to firewall (public) and have it point back to LTM (private). Then just set up translation. This article seems to offer some background about the reasoning.

     

    SOL14707: Configuring BIG-IP DNS server objects for BIG-IP devices that reside behind a firewall NAT

     

    https://support.f5.com/kb/en-us/solutions/public/14000/700/sol14707.html

     

    This seems a frustrating topic for sure!

     

    Kevin

     

  • The virtual servers should be on Public IP addresses or should at least be reachable on the public IP. I can't see how it would work if you had a virtual server on a private IP address but the GTM was returning a public IP address. Clients performing the DNS lookup would be trying to connect to a public IP address which isn't the same address as the virtual server. Virtual server IP address is the address normally returned by the GTM.

     

    You can choose to have a fallback IP address returned or create a fancy iRule for creating a "fake" response but best practice would be to have the GTM returning the same IP address as the virtual server so end clients can connect to the requested service being looked up in DNS.