For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Scott_Delk_4899's avatar
Scott_Delk_4899
Icon for Nimbostratus rankNimbostratus
Jul 06, 2006

Get Pool Members

Currently I am using     Pool.CommonIPPortDefinition[][] members = Pool.get_member(pool_list);     to return a list of all pool members so I can duplicate the list that I see when logged i...
dev
devops
iControl
Joe_Pruitt's avatar
Joe_Pruitt
Oct 17, 2007
Bottom line is that the BIG-IP will have to resolve a name to an address anyway to be able to create the physical connection to the backend server.

 

 

Your example about load balancing from BIG-IP to two web servers (LT-KM3456.us.f5.com, and LT-KM3478.us.f5.com) is very very common. Typically the way this is configured is to create a DNS name for your exposed Virtual Server address (VIP). Then, configure your backend servers to accept that domain name in the Host HTTP request header. All of the HTTP headers (including the Host, the URI, etc) will be passed on to the backend server as they were passed into the Virtual Server.

 

 

BIGIP (Virtual Server LT-KMCommon.us.f5.com - 20.20.20.20)

 

-> Member (LT-KM3456.us.f5.com - 10.10.10.10)

 

-> Member (LT-KM3478.us.f5.com - 10.10.10.20)

 

 

Where 20.20.20.20 is the external Virtual Server address and the 10.* network is internal to your BIG-IP. Just configure your web apps to take LT-KMCommon.us.f5.com as a Host Header, and you should be all set. The pool members are completely hidden from the user and are masked by the virtual server address.

 

 

I guess, I'm missing why you are tying how BIG-IP stores it's PoolMember configuration with how the client accesses your Virtual Server. Please let me know if I haven't explained it clearly enough.

 

 

-Joe