Can we identify Server "UP" / "Down" Status in an iRule

Thanks for the reply... We should be OK waiting until something official is released.

 

 

I will be testing an alternative to this later in the week. What would make more sense is for me to create a "Node" level Monitor that does a "Reverse" check against Server1 and assign it to Server2.

 

 

This way when Server1 goes "Down", Server2 comes "UP" and when Server1 comes back "UP" Server2 changes to status "Down".

 

 

Once I can control this using Priority Activation, I can have the pool send a "Reset" on service down, solving my initial problem. (Eliminating the need for an iRule to send TCP::Close)

 

 

My current issue is that Node Level Monitors are not recognized by the Pool. So Priority Activation cannot occur when monitors are set at the Node Level.

 

 

There is speculation that I can get around this behavior and plan to validate this later in the week.