Priority Groups

Can you please help with the option to "check the go offline on the node {server}",

We are facing similar issue,where, the traffic is intermittently routing to the wrong priority pool member on the pool. Typically 10.10.71.247:80 is online but won't serve traffic unless the two priority 2 pool members go down, but has been intermittently serving traffic even when we can see that the other two pool members in priority 2 are shown as up on the load balancers.

We have source address persistence configured because the application (hosted on the priority group 2 servers) does require this. The priority group 1 and priority group 3 servers are basically hosting a maintenance page. Priority 3 for when we have scheduled maintenance, and priority 1 for when we have unplanned downtime. In normal cases, priority 2 and priority 1 servers will be up, but no traffic shall be routed to the priority 1 server unless both priority 2 servers are down. Normally traffic will only be on the priority 2 servers, with persistence (as required by the application). If we have planned maintenance, we will bring up the priority 3 server. In all cases, we have persistence for 180 seconds only, after which the customer’s request will be re-balanced, allowing for the flexibility of persistence for short-term transactions while allowing re-balancing for less frequent use, i.e. when we bring up the priority 3 server.

we typically get 1-2 calls a day from our customers when the priority 1 pool member is up, even though the priority 2 pool members are also both up. Even when the user sees the issue, we cannot reproduce, and the F5 shows priority 2 pool members are active. what other options do we have for troubleshooting?