iRule broken after code update?

Hey Aaron,

 

 

This rule is in place to perform a bit of persistence.

 

 

There are 2 servers that use this VS (and only two) and there are two servers that these boxes can talk to.

 

 

The servers sending data are 10.102.16.18 and 16.19

 

 

The servers that will handle their requests are 10.102.101.50 and 52.

 

 

I created two pools with priority groups.

 

 

One pool has .50 and the primary and the other pool has .52 as the primary.

 

 

So the goal was to take requests from 16.18 and pin it up to .50 unless .50 went away, then it needs to go to .52. And when .50 comes back up...It needs to gracefully go back to .50. And the same is true for .16.19 and the .52 server.

 

 

I pulled the logs from the load-balancer and it looks like it worked after the code update (on the 12th) but something on the 13th caused it to stop functioning.

 

 

I'm guessing I need to perform a either a bigstart restart or perhaps a b load to kinda jar this LB back into functioning properly?

 

 

I just don't get why it stopped working. I might need to perform a more serious packet capture and analyze the traffic going into the LB a little more closely.

 

 

Thanks,

 

 

James