Forum Discussion
Mani090
Nimbostratus
NimbostratusPool & members showing up in active LB but in standby it is showing down.
I am seeing one pool & its pool member is showing up on active load balancer but on standby it is showing down. Both devices are in sync. On standby pool, session monitor is not showing. Is this some configuration issue or issue is from server end
tmos)# list ltm pool ent-abc-ghaw-389_pool
ltm pool ent-abc-ghaw-389_pool {
members {
10.140.10.14:ldap {
address 10.140.10.14
session monitor-enabled
state up
}
10.142.102.37:ldap {
address 10.142.102.37
session monitor-enabled
state up
}
10.142.102.47:ldap {
address 10.142.102.47
session monitor-enabled
state up
}
}
monitor tcp
}
====================
session monitor is not showing. This is config on standby device
mos)# list ltm pool ent-abc-ghaw-389_pool
ltm pool ent-abc-ghaw-389_pool {
members {
10.140.10.14:ldap {
address 10.140.10.14
state down
}
10.142.102.37:ldap {
address 10.142.102.37
state down
}
10.142.102.47:ldap {
address 10.142.102.47
state down
}
}
monitor tcp
}
Hi,
This is not a Sync problem or in other words ( HA doesn't Sync Pool members Status ) as the standby unit should do the health monitoring by it's own selfip ( specially the selfip that can reach to servers/pool members )
so in this case you need to do the following:- use #ip route get <Pool_member_ip> to know which selfip in the standby unit reach/talk to servers.
- If you have a Firewall between your Bigip and servers , you need to monitor if the standby selfip sends health monitor packets periodically to servers or not, also you need to check if the firewall allows the access between the standby unit and servers.
- Try to perform telnet test on LDAP port and see if you can connect or not.
- Take a packet capture for health monitor traffic between Standby selfip and server, Packet capture should show you what is the issue exactly in the standby path to LDAP servers.
- Please check this article , it has more insights for health monitor troubleshooting and a sample Packet capture command:
https://my.f5.com/manage/s/article/K12531
Man_YauCirrus
I have the same issue, but i when tried to run packet capture on the standby unit and filter on the ip address it is failing, i don't see traffic. When filter on the ip address it is working, i see traffic.
It seems the standby unit don't send healthmonitor traffic on specific ip address
i'm running TMOS 17.1.1.2
- Man_Yau
i have found the solution for this. When i remove the healthmonitor -> update -> enable the healthmonitor -> update, this trigger the healthmonitor again on the standby unit. Server on both unit came active.
