Forum Discussion
jsgibbs1
Nimbostratus
NimbostratusFQDN Pool member failing becuase previously added by IP
I ran into an interesting problem on 12.1.2 and was wondering if this is expected behavior, and if so, why?
I had a pool that had a member(node) added by IP with a basic TCP monitor, which worked. I then had a requirement to point to this node by FQDN. After creating the new FQDN pool with a basic TCP monitor, I noticed it would not go green, with /var/log/ltm showing member not found error. This made no sense to me, since I could resolve the FQDN from the CLI and that fact that I was looking at the member as green in the original pool.
To resolve the issue, I deleted the node previously created by IP. Once I did that and forced a new resolution, it worked!
Any thoughts? If nothing else, hopefully this helps someone else out.
JGCumulonimbus
I'd open a support case to report the problem.
jsgibbs1Yes, tried different monitors on each pool (tcp, https, and custom https with increased timeout) but no joy.
- P_K
Altostratus
Did you try changing to a different monitor? something like tcp_half or gateway_icmp?? on what port is the server listening?
