Forum Discussion

SimonG_179714's avatar
SimonG_179714
Icon for Nimbostratus rankNimbostratus
May 05, 2017

F5 GTM Issue : Virtual Server discovery

Hi,

I am labbing up a problem i have with LTM virtual discovery on a GTM with version 13.0 HF0 (and also HF2 released last night).

The data center is configured with both GTM and LTM, the bigip_add works correctly, as this is a lab environment portlockdown is set to "allow all", iqdump shows the information is being passed from LTM to GTM, Auto-discovery is enabled, Big3d version is the same on both and is running, there are no NAT translations and the GTM still wont auto discover the VSs on the LTM.



   4
   ::ffff:192.168.19.7
   ::
   1
   66
   Thu May  4 20:52:05 2017



   1
   ::ffff:192.168.2.242
   ::ffff:255.255.255.0
   0
   66
   /Common/Vlan2


   2
   ::ffff:192.168.2.243
   ::
   80
   0
   /Common/APC_VS


   2
   ::ffff:192.168.19.244
   ::
   10000
   0
   /Common/Webmin


   5
   ::
   ::
   0
   0

I've gone through K9138, K14106, K15190, and others.

When i manually input the VS, the BIGIP health check fails in the logs, but not in iqdump.

May  4 11:46:55 gtm1 alert gtmd[4975]: 011a6006:1: SNMP_TRAP: VS APC_VS (ip:port=192.168.2.243:0) (Server /Common/WIP_APC) state change blue --> red ( Monitor /Common/bigip from  : no reply from big3d: timed out)

The output implies an issue with iquery, but that coming back as OK.

[root@gtm1:Active:Standalone] config  iqdump 192.168.19.7





13.0.0
big3d Version 13.0.0.2.0.1671
linux


   99300
   49791
   49509
   5159064
   2328835
   2830229
   0
   41640
   1
   0
   notice
   0
   0
   0
   0
   0
   0
   0
   0

Any advice/ideas? S,

application delivery
auto-discovery
BIG-IP DNS

5 Replies

Sort By
  • Leonardo_Souza's avatar
    Leonardo_Souza
    Icon for Cirrocumulus rankCirrocumulus
    May 05, 2017

    Enable more logging, and you should get an explanation about what is happening. I saw in the pass messages saying that the system could not find itself (GTM server object was not configured), so it would not continue with auto discovery. Just one example of possible problems, but the logs are very explicit about the problem.

     

    I don't remember wich one is necessary, here are the possible 3 keys:

     

    log.gtm.level

     

    log.mcpd.level

     

    gtm.verbosemcpmessages

     

    See this solution about how to change:

     

    https://support.f5.com/csp/article/K13455

     

  • vegetax's avatar
    vegetax
    Icon for Nimbostratus rankNimbostratus
    May 31, 2017

    I am running into the same issue can you please add some clarification on "by adding in ALL the self-ips of the LTM" did you add all your self ip's you have on your ltm on GLSB server list?

     

    -Error message I am getting in logs getconfig_put: Could not find my own box, will not continue with auto discovery

     

    • Leonardo_Souza's avatar
      Leonardo_Souza
      Icon for Cirrocumulus rankCirrocumulus
      Jun 01, 2017

      You need to add a server object for the GTM/DNS itself. The message says it can't find the GTM server object, this why it is stopping with the auto discovery to the other server objects.

       

  • vegetax_222338's avatar
    vegetax_222338
    Icon for Nimbostratus rankNimbostratus
    May 31, 2017

    I am running into the same issue can you please add some clarification on "by adding in ALL the self-ips of the LTM" did you add all your self ip's you have on your ltm on GLSB server list?

     

    -Error message I am getting in logs getconfig_put: Could not find my own box, will not continue with auto discovery

     

    • Leonardo_Souza's avatar
      Leonardo_Souza
      Icon for Cirrocumulus rankCirrocumulus
      Jun 01, 2017

      You need to add a server object for the GTM/DNS itself. The message says it can't find the GTM server object, this why it is stopping with the auto discovery to the other server objects.