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.

TCP Monitor after migrating from 11.4.1 to 12.0

13 Replies

Daniel_Varela
Employee
Apr 07, 2016
You also have support for CGM ciphers in 11.5.4: https://support.f5.com/kb/en-us/solutions/public/13000/100/sol13163.html. Version 12 is very good but I'd only move to that if there is something I really need. Have a look to the software support policy: https://support.f5.com/kb/en-us/solutions/public/5000/900/sol5903.html. As someone said before, 11.6 is about to reach EoSD
JG
Cumulonimbus
Apr 07, 2016
v11.6.0 reaches "End of Software Development" on 25-Aug-2016, just a few months away. There is also a bug in the v11.6.0 hotfix releases that could lead to the failure of a monitor that uses a domain-specific username as part of the credentials needed by the monitor.
Gary_Zhu
Nimbostratus
Apr 06, 2016
thanks for the quick response!
smurteira_23292
Cirrus
Apr 06, 2016
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
Cirrus
Apr 06, 2016
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
Cirrus
Apr 06, 2016
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
Cirrus
Apr 06, 2016
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
Cirrus
Apr 06, 2016
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
Cirrus
Apr 06, 2016
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.
Gary_Zhu
Nimbostratus
Apr 06, 2016
Is 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".