Forum Discussion
symtex_22198
Nimbostratus
NimbostratusGTM design question: GTM/LTM LTM/ASM multisite deployment iquery requirements
Hey guys,
I'm a little confused about iquery design. I have the following topology
The following is true:
- GTM/LTM site1 can have iquery connectivity with GTM/LTM site2.
- GTM/LTM site1 can have iquery connectivity with LTM/ASM site1.
- GTM/LTM site2 can have iquery connectivity with LTM/ASM site2.
- GTM/LTM site1 cannot have iquery connectivity with LTM/ASM site2.
- GTM/LTM site2 cannot have iquery connectivity with LTM/ASM site1.
if the GTMs are in the same synchronization group, will GTM/LTM site1 know if a virtual server on LTM/ASM site2 is DOWN using the iquery connection it has with GTM site2?
Also the GTM has virtual servers for the public IP addresses as it does the NAT through virtualserver/pool/nodes. Would I have to define the GTM's local LTM as a server also? or would I only define the LTM/ASM as servers in GTM configuration?
if full mesh connectivity is required. perhaps I can accomodate public IP address virtual servers on GTM/LTM that NAT to the self IP addresses of LTM/ASM nodes? and establish iquery through NAT according to SOL14707. has something like this ever been done?
Arnaud_LemaireEmployee
in a traditionnal GTM design, all GTM should have access to all Big-IP it is monitoring. Otherwise in your example if GTM2 cluster fail, GTM1 won't be able to touch you remote devices and they will be seen as down.
Having said that, in your topology, i won't do monitoring by GTM of you LTM/ASM pairs. I would only include LTM services hosted on GTM/LTM to be monitored in the GTM group. As the LTM services hosted on your LTM/GTM will monitor second LTM/ASM level it should be enough.