No traffic going to pool, but works with different name
I'm seeing an odd issue on our LTM where traffic will not flow to one of my pools. It's inside an irule, but the issue isn't with the rule itself. In a bit of desperation, I created a new pool which was the exact same as the problem pool, except with a '_Test' appended to the name. I updated the irule with the new pool name and traffic flowed as expected.
I then deleted the original pool, saved the config, re-created it, modified the irule with the original pool name and once again no traffic. The stats are 0's across the board for the pool, no traffic even attempting to go to it.
It seems odd that the name of the pool would matter, but I can't come up with any other explanation. Anyone seen something like this?
For what it's worth, I'm on 11.6.0 HF1
ltm pool /D04TS/DP_REST_FIREWALL_Servers {
members {
/D04TS/DP-1:8149 {
address X.X.X.X
}
}
monitor /Common/gateway_icmp
}
ltm pool /D04TS/DP_REST_FIREWALL_Servers_Test {
members {
/D04TS/DP-1:8149 {
address X.X.X.X
}
}
monitor /Common/gateway_icmp
}
Just in case anyone else runs into the same issue, the problem wound up being we had pools in different partitions/route domains with the same name, i.e. 'DP_REST_FIREWALL_Servers', which confuses the device if the partition is not explicitly called out. So the fix was just a matter of updating the irule to read
pool /D04TS/DP_REST_FIREWALL_Servers
instead of
pool DP_REST_FIREWALL_Servers