Network Virtual servers

But when it is network based Virtual servers you are running a Network and not a host. So in this case the Virtual address will be the whole network and not a single host. so how can a client specify the URL or IP particularly in the Web vrowser ?

If you specify a network virtual server, there will be a listener on the associated VLANs for the defined IP address range. Now the client can address each particular address in this range. (This might be a result of name resolution, manually entered IP address in URL or even another load balancer in front of the setup.) And if the datagram is routed to the BIG-IP it will be handled / forwarded as long as it fits the: - range of addresses - transport protocol - destination port of your network virtual server. If you are associating a pool with the network virtual servers the poolmembers may be treated as: - next hop (typical deployment to forward outgoing traffic via multiple default gatewys - ISP link load balancing) (destination NAT does not apply here and remains unchecked in your virtual server settings) - final destination (i.e. the case if you want to "catch" traffic and to force it to a proxy or whatever) (destination NAT will apply and the checkbox in your virtual server settings need to be set) Depending on the selected processing in the virtual server (applied profiles, iRules ...) there can be additional operations / manipulations applied.

Stephan, currently i am just going thru some docs for this Network Virtual servers and i will get back to you with the concern once i am done with my understanding. Many thanks for your response.