# GSLB not marking local VS as down

**URL:** <https://community.f5.com/t/gslb-not-marking-local-vs-as-down/75940>\
**Category:** Technical Forums\
**Tags:** vip, gslb, virtual-server\
**Created:** [March 26, 2025, 4:34pm UTC](https://community.f5.com/t/gslb-not-marking-local-vs-as-down/75940 "2025-03-26T16:34:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![geo\_1997](https://avatars.discourse-cdn.com/v4/letter/g/839c29/32.png) [@geo\_1997](https://community.f5.com/u/geo_1997)\
**Post date:** [March 26, 2025, 4:34pm UTC](https://community.f5.com/t/gslb-not-marking-local-vs-as-down/75940/1 "2025-03-26T16:34:42Z")

</div>

Hi all,

I currently have 2 BIG-IP nodes with their own separate LTM pool.

When all pool members on 1 BIG-IP node are down, I would have expected the VIP to be marked down in the GSLB VIP pool as well, but this does not seem to be the case for local VIPs.

So in my situation, I shut down all pool members on BIG-IP node B.

BIG-IP node A sees only its own VIP as available and online, and marks the remote VIP as offline.  
However, on BIG-IP node B, both VIPs are marked as green.

This is a problem, because users are being routed to a VIP that has no active pool members.

Its worth mentioning that the VS correctly marks itself down (available - the children pool members might be disabled) on BIG-IP node B, but this is not reflected in the GSLB VIP pool.

I have no health monitor in the VIP pool, my GSLB \> Servers are using the bigip health monitor (I believe this is default for BIG-ip System) and the virtual servers are using a HTTPS health monitor.

Any help here would be greatly appreciated, please let me know if I can provide any additional information

---

<div class="post-metadata">

**Author:** ![Teerarat](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/teerarat/32/4921_2.png) [@Teerarat](https://community.f5.com/u/Teerarat)\
**Post date:** [March 31, 2025, 4:10am UTC](https://community.f5.com/t/gslb-not-marking-local-vs-as-down/75940/2 "2025-03-31T04:10:56Z")

</div>

Hello,

Do you have object GSLB Server for BIG-IP DNS devices ?

---

<div class="post-metadata">

**Author:** ![david598ball](https://avatars.discourse-cdn.com/v4/letter/d/ac91a4/32.png) [@david598ball](https://community.f5.com/u/david598ball)\
**Post date:** [March 31, 2025, 11:15am UTC](https://community.f5.com/t/gslb-not-marking-local-vs-as-down/75940/3 "2025-03-31T11:15:12Z")

</div>

Hello,  
It seems like the issue might be related to the absence of a dedicated health monitor in the GSLB VIP pool. Try adding an HTTPS health monitor directly to the VIP pool in GSLB to ensure accurate status checks. This should help synchronize the health state correctly across nodes.

Best Regards,  
David Ball

---

<div class="post-metadata">

**Author:** ![LiefZimmerman](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/liefzimmerman/32/3355_2.png) [@LiefZimmerman](https://community.f5.com/u/LiefZimmerman)\
**Post date:** [March 31, 2025, 8:15pm UTC](https://community.f5.com/t/gslb-not-marking-local-vs-as-down/75940/4 "2025-03-31T20:15:55Z")

</div>

@david598ball - If your answer is AI/LLM assisted you must make a note to that affect in your reply or, per community guidelines, your account is subject to permanent suspension.