Problem with upgrade to 10.1

Posted By Chris Miller on 08/10/2010 06:08 AM

 

 

Shall I assume you upgraded from 9.x to 10.1 and are using network failover? The transport protocol changed a bit so both units would think they are active/active. As far as your monitor situation goes, that never should have worked. You're telling your monitor to check the port on which your pool member is listening. In this case, your pool member is listening on all ports so your monitor doesn't know what to check.

 

That's right, I was expecting them both to go active and to have to separate them at network level. it's the monitoring issue which is odd. I hadn't looked at these before, all done long before I joined the organisation.

 

 

Looking at the active unit still running 9.4.7 I can see that the default http monitor is set to * All Ports.

 

The pool members are configured to use the same method as the pool.

 

 

So we're running this on live for most of our virtual servers even though the F5 shouldn't have accepted it. How is this possible?