virtual pool

Hi, sounds like you've got a good idea of how the virtual / pool relationship works. One other consideration is the forwarding or network virtual server which can route packets based strictly on routing (or layer 3 info). Some if the virtual server types:

http://support.f5.com/kb/en-us/solutions/public/14000/100/sol14163.html

Hi Kevin, Thanks for the link, I'll take a look at that later. But, how would you best answer my question about creating an additional virtual pool or not? Also, I'm not sure of what type of virtual server it is, I do know that I am not interested in load balancing, only proxying. External IP>>>>Virtual Server\Pool>>>>>Node

Anyone?

Morning, the list of services you see on the pool represents the most popular. You could type your own custom port or even choose "all services". When the virtual receives a connection, it will be sent to the pool using the destination port in the client packet.

Thanks Kevin. What if I need to assign\open additional ports for those nodes, do I create a new virtual pool and add those nodes under it as well with the new port number(s), say https? In other words, say I have two nodes part of a pool and they only need to listen on port 80, I will put both of them together under 1 virtual pool. What if one of the nodes (pool members) now needs to listen on port 443, do I create a new virtual pool that listens only on that port and add that node? So what happens down the line when I need to add more nodes? Is it best practice or not to create virtual pools with members that listen only on the same port? So if I only care about port 80, port 443 and port 5050 would I then create 3 virtual pools and add whatever members to those respective pools?

Welcome, It is the best practice to create virtual servers with pool members that listen on the same port. So port 80 virtual and pool, port 443 virtual and pool, port 5050 virtual and pool.

Great! Thanks a lot.