@FAJUMO You have verified that VS on 192.168.20.211 on port 7080 does have statistics showing it’s being used? It’s possible that you have persistence configured with “Match Across Pools” if you are not seeing the port 7080 pool pool members with zero statistics at all. You can apply an iRule to the virtual server in question and put a logging line similar to the following to see where the traffic is ultimately being sent that comes in on port 7080.
when LB_SELECTED {
log local0. "LB INFO - Client: [IP::remote_addr], Port: [TCP::remote_port], Pool: [LB::server]"
}
@FAJUMO Those appear to be the statistics for the pool and not the virtual server. Check the virtual server statistics and if they are zero then either the virtual server isn’t configured correctly or the client is not making a request to 7080 on that particular IP.
You could configure an 80 virtual server that balances to both the 8080 and 7080 and then an iRule on each one that performs a redirect to 8080 or 7080 depending on which virtual server you end up being balanced to in the pool for the 80 virtual server.