load balance http traffic on diiferent ports

I'm not entirely clear on the scenario you are describing. I assume that your first scenario is a user simply browsing HTTP to your virtual server:

appsvr:80 --balances to--> pool_mbr1:80, pool_mbr2:80, pool_mbr3:80

Can you further clarify your second scenario? Is the client requesting a connection on port 9000 that will go to the same nodes but port 9000 as such?

appsvr:9000 --balances to--> pool_mbr1:9000, pool_mbr2:9000, pool_mbr3:9000

Or something different?

Exactly that Ed.

It is an application that needs to read data from the same nodes but it does this on port 9000. (this is not changeable as we have asked)

But in our http iApp there is only 80 or 445 obviously.

I can't see a way of adding in another port for the same VS and pool.

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!

Thanks for the reply.

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.

Thanks for all your replies and help.

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 should have three VIPs:

VIP1.company.com:80 --balances to--> Pool:80 (pool_mbr1:80, pool_mbr2:80, pool_mbr3:80) VIP1.company.com:443 --balances to--> Pool:443 (pool_mbr1:443, pool_mbr2:443, pool_mbr3:443) VIP1.company.com:9000 --balances to--> Pool:9000 (pool_mbr1:9000, pool_mbr2:9000, pool_mbr3:900)

These are all separate VIPs, yet share the same FQDN. Keep in mind, a VIP is a ip AND port combination, not just the ip.

Good Luck!

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.

-Jinshu

David,

Really appreciate your help on this.

Can you just clarify for my head a VIP? Is this the same as Virtual Server?

I think I am getting muddled on acronyms...

Yes, When I say VIP I mean the Virtual Server.

Sorry for the confusion.

Excellent. Thank you very much.

I will give this a go and see how it all works.

Learning all the time.

Thanks again for all the help.