LTM query

Do you want to forward to secondary servers only want both primary servers fail or you trying to do a one-to-one relationship so a user on server A will stick to server A just be forwarded to the secondary port?

Client will disable one of the service port 82801 on both servers and then the traffic should Failover to server A and server B set with service port 83801

what do you mean by "Server"? Is it a VIP or a back-end server?

Backend server.

Maybe priority group activation may help you Manual Chapter: About Pools

No it doesn't work as in here port based Failover is initiated an 2 proves are used for monitoring

I mean 2 probes

here you have for priority groups

Two pool member with port 82801 with higher priority Two pool members with port 83801 with lower priority

If one of the pool members in higher priority group fails monitoring, lower priority group will take care.

What is the problem with that?

A pool using Priority Groups should do the job, like Surgeon said.

1. Enable Priority Groups in the pool by setting the Priority Group Activation to be Less than 1 Available Member(s).
2. Under the Pool Member for group A, set the Priorty Group to be 20
3. Under the Pool Member for group B, set the Priorty Group to be 10

Example of what your pool should look like:

pool my_pool { 
lb_mode fastest 
min active members 1
member ServerA:82801 priority 20
member ServerB:82801 priority 20
member ServerA:83801 priority 10
member ServerB:83801 priority 10
}

Now if both pool members ServerA and ServerB on port 82301 as disabled or the monitors fail, all traffic will be load balanced to ServerA and ServerB on port 83801.

Problem

2 different monitoring probes are used ie 82801 & 83801

Client doesn't disable the server but he disables the port 82801 . When port 82801 is disabled ,the traffic isn't routed to next pool member whose service port is set to 83801. This is bcoz 2 probes ports 83801 & 82801 are set as monitoring ports as well in OR logic mode ie the option atleast 1 port in monitoring probe is tick marked. Hence the pool member with service port 82801 still remains up inspite of the port 82801 is disabled due to which traffic isn't routed to next available pool member with port 83801.

I need solution for this.