03-Feb-2022 18:53
03-Feb-2022 20:51 - edited 03-Feb-2022 20:52
can you describe it in more details if i understood correctly
WIP(FQDN) --> pool1(A record ) and pool 2(A Record) --> pool --> two VIPs as member of POOL1 and POOL2 i believe is backup VIP. both are on LB with diffrent port and if one of the VIP goes down then how you make the pool marked down.
Now if both members in POOL1 are working then your resolution will give one of the pool member from same pool.
doesnt seem to be an ideal scenario but is it correct understanding about this setup ?
05-Feb-2022 08:22
Hi Vaibhav, that's exactly right!
How do I make the WIP not choosing Pool1 for resolution if any member (VIPs on another LTM with the same IP but with different ports) goes down?
Thanks!
Difan
04-Feb-2022 00:52
I couldn't understand your GTM setup though, but from what I understood, you want to mark down the other pool member (2.2.2.2) also, when one of the pool member (1.1.1.1) is marked down. You'll have to use the depends on feature on the GTM to do this. The monitoring will understand that it has a depends on to mark it up.
05-Feb-2022 08:27
Hi Jiakumar_f5,
Sorry for lacking details in my question...
So my WIP is mail.example.com. It has two pools (POOL1 and POOL2). POOL1 has LTM1's two VIPs (VIP1 and VIP2) as members. VIP1 and VIP2 are with the same IP address 10.1.1.1 but with different ports (993 for IMAP and 995 for POP3).
Right now, we are having issues with the IMAP health monitor on the LTM after the upgrade of the LTM. I have a case open to investigate. The POP3 remains up. Therefore, the GTM still provides 10.1.1.1 in its DNS response. I want to not give it in the response.
Hopefully, this is clear. Thanks!
Difan