WideIP Virtual Servers and Pool offline in GTM/DNS but online in LTM on BIGIPv12 Virtual Edition

To clarify, your bigip VE is running both LTM and GTM, not separate VEs?

Hi.. using the predefined "http" monitor in both the gslb server objects and gslb pool.

sorry, and Yes running a single VE instance with both LTM and GTM/DNS. Not separate

If you remove the http monitor from the gslb server and pool do the virtual servers go green? The gslb server (your bigip) should have the bigip monitor assigned to it, that is enough for gtm to see that the virtual servers are available. Have you tried a different monitor? TCP for eaxmple?

when I remove the http monitor, the status turns to Blue/unknown both on the gslb servers and pool. Yes tried "gateway_icmp" but still red/offline. Wondering if the GTM is trying to get to the LTM to check the monitors but cant - iQuery maybe? How could I check iQuery communication on single VE instance - any ideas ?

trying to paste /config/bigip_gtm.conf contents but cant as being categorised as spam. Any suggestions what the correct method is please ?

Thanks

Use the preformatted code button above the comment field to insert the contents of bigip_gtm.conf. Each line of the code should be indented using tab then check the preview field it should look the same as it does in the conf file. Here's an example:

gtm datacenter /Common/Miami { }
gtm server /Common/gtm_4 {
addresses {
    10.10.4.31 {
        device-name /Common/gtm_4
    }
}
datacenter /Common/Miami
monitor /Common/bigip
virtual-server-discovery enabled
virtual-servers {
    /Common/http_vs_ltm4 {
        destination 10.10.4.100:80
    }
    /Common/listener_50 {
        destination 10.10.4.50:53
    }
}
}

Code


Code[root@bigip1:Active:Standalone] config  cat /config/bigip_gtm.conf

gtm datacenter /Common/DC_dy { } gtm datacenter /Common/DC_rd { } gtm server /Common/webserver1_rd { addresses { 172.25.16.32 { device-name /Common/webserver1_rd } } datacenter /Common/DC_rd monitor /Common/gateway_icmp product generic-host virtual-server-discovery enabled virtual-servers { webserver1_vs { destination 172.25.16.32:80 } } } gtm server /Common/webserver2_dy { addresses { 172.25.16.33 { device-name /Common/webserver2_dy } } datacenter /Common/DC_dy monitor /Common/gateway_icmp product generic-host virtual-server-discovery enabled virtual-servers { webserver2_vs { destination 172.25.16.33:80 } } } gtm global-settings general { cache-ldns-servers no forward-status enabled } gtm global-settings load-balancing { verify-vs-availability no } gtm global-settings metrics { metrics-collection-protocols { icmp } } gtm global-settings metrics-exclusions { addresses none } gtm pool a /Common/wideip-dr-pool { load-balancing-mode global-availability members { /Common/webserver1_rd:webserver1_vs { member-order 0 } /Common/webserver2_dy:webserver2_vs { member-order 1 } } monitor /Common/gateway_icmp } gtm pool a /Common/wideip-pool-test { members { /Common/webserver1_rd:webserver1_vs { member-order 0 } /Common/webserver2_dy:webserver2_vs { member-order 1 } } monitor /Common/http verify-member-availability disabled } gtm wideip a /Common/ { load-balancing-decision-log-verbosity { pool-member-selection } pools { /Common/wideip-pool-test { order 0 } } } gtm wideip a /Common/ { load-balancing-decision-log-verbosity { pool-selection } pool-lb-mode global-availability pools { /Common/wideip-dr-pool { order 0 } } }

The servers webserver1_rd and webserver2_dy are these addresses of VS on the LTM? Do you have the bigip itself created as a gslb server object? If not create one using an external self-ip address, product type "bigip single", assign to datacenter, and assign the bigip monitor. The GTM itself should be the first gslb server created in the config since it is responsible for running the monitors.

G. Scott Harris.. You're a STAR.. Thank you so much..