Is it possible to load balance http traffic on different ports to the same pool members using the same VS?
For example we have an application that uses a virtual server on our LTM of appsvr.
A user browses to appsvr and gets port 80 traffic sent to one of the pool members. Great!
Now we also have an application that needs to communicate with the system behind appsvr but does this on port 9000. Can I add this port somehow to the appsvr virtual server on the F5 so that it can forward that traffic on to the same pool members using the same virtual server name?
Create a new virtual with the same IP that listens on port 9000. Whilst configuring that, create a new pool using all the same pool members but configure them to listen on port 9000 as well. You can specify the port in the iApp.
RobL216, Maybe it will help if you think of it this way,… You are not adding a port to the existing VIP, you are actually building a completely new one, just using the same IP with a new port. You could build this manually outside the iApp wizard, or you could create a new iApp template with the ports you need, and use it to build the VIP. Good Luck!
So it seems I need to create a second VS with a different new IP for the second system to access the same pool. I understand this but we do have other applications that we were thinking of load balancing but I guess this may not work for us as there are multiple systems that access these other applications on different ports but use the same ‘name’.
I think I am getting to grips with the way things work now.
Not quite. First, create a new pool, using the same Nodes, but configure it with the new port(9000). Then create a new VIP with the SAME IP as the 80 and 443 VIPs, but with the new port(9000). Lastly, associate the new VIP:9000 with a new pool:9000.
You can create the new VIP with same IP address and different port.
Create a new VIP with same IP address and port 9000. Create a new pool with members abd port number 9000. Thats it.
As David stated above, Vips are ip and port combination and you can create many VIPs with same IP and different ports.
If you have many vips on same IP address and different ports, i would suggest to create a wildcard vip (IP:any) and create an iRule to make the lb decisions. It is pretty easy and straight forward.
Building on David’s terminology clarification, ‘node’ would be the back-end server IP, while ‘pool member’ is an ip:port combination. So you’re forwarding to the same node, but different ports on the node, hence different pool members.
I tend to think of VIP as just the virtual IP address, and the combination of VIP and port/service as a ‘virtual service/server’. However people use many of the terms interchangeably, hence need for clarification sometimes.