Forum Discussion
smurteira_23292
Cirrus
CirrusTCP Monitor after migrating from 11.4.1 to 12.0
I just migrated from 11.4.1 to 12.0. Everything seems fine with the exception of my Pools. They are all marked " Offline (Enabled) The children pool member(s) are down". On 11.4.1 I was using the default tcp monitor and my pool was green. On 12.0 it is down even though my nodes are up. If I change to use gateway_icmp the pool turns green. Any idea why I can't use my default tcp monitor on 12.0?
I'm sorry I didn't respond earlier. Turns out it was user (me) error. I only put the floating IP address in the firewall. The problem is that the monitoring is being done by the internal IP and not the floating IP of the F5. Once I added the other two IP addresses for each unit, everything started working as expected.
smurteira_23292Also, same is happening with my https monitors.
Gary_ZhuNimbostratus
I am about to upgrade from 11.4 to either 11.6 or 12, so this is important for me to know the answer. On the other hand, I am using LTM to terminate SSL (common), so the pool monitoring (already plain text) should not be the issue, again, I'd like to confirm.it.
IanBEmployee
I suggest you grab a tcpdump of the traffic between the LTM and the pool member to see what's actually happening Can you telnet to the pool member from the BigIP commandline (to the port listed in the pool)- Gary_ZhuIs this still a problem or just a configuration mishap? If version 12 is not stable, I don't have to go there. For me, moving to 11.6 will gain GCM cipher support, and moving to 12.0 will get me HSTS, but I already has iRule to emulate HSTS, so version 12.0 is not the "must have".
- smurteira_23292I'm sorry I didn't respond earlier. Turns out it was user (me) error. I only put the floating IP address in the firewall. The problem is that the monitoring is being done by the internal IP and not the floating IP of the F5. Once I added the other two IP addresses for each unit, everything started working as expected.
- smurteira_23292
I'm sorry I didn't respond earlier. Turns out it was user (me) error. I only put the floating IP address in the firewall. The problem is that the monitoring is being done by the internal IP and not the floating IP of the F5. Once I added the other two IP addresses for each unit, everything started working as expected.
- smurteira_23292
I'm sorry I didn't respond earlier. Turns out it was user (me) error. I only put the floating IP address in the firewall. The problem is that the monitoring is being done by the internal IP and not the floating IP of the F5. Once I added the other two IP addresses for each unit, everything started working as expected.
- smurteira_23292
I'm sorry I didn't respond earlier. Turns out it was user (me) error. I only put the floating IP address in the firewall. The problem is that the monitoring is being done by the internal IP and not the floating IP of the F5. Once I added the other two IP addresses for each unit, everything started working as expected.
- smurteira_23292
I'm sorry I didn't respond earlier. Turns out it was user (me) error. I only put the floating IP address in the firewall. The problem is that the monitoring is being done by the internal IP and not the floating IP of the F5. Once I added the other two IP addresses for each unit, everything started working as expected.
- smurteira_23292
I'm sorry I didn't respond earlier. Turns out it was user (me) error. I only put the floating IP address in the firewall. The problem is that the monitoring is being done by the internal IP and not the floating IP of the F5. Once I added the other two IP addresses for each unit, everything started working as expected.