I have seen a VS:80 setup on LTM with 'Standard' type,only "TCP Profile", "Pool", "SNAT pool" and "dest_addr" Destination address affinity.
I was in impression that dest_addr is used when either there VS is working as Caching or its a Wild card VS, so that LTM will look at the destination address in packet and create a persistence record so that next time the same destination will use the previous resource.
But the setup I see contradict my understanding. How would LTM be able to determine Destination address in "Standard VS Type" because of the fact that Destination address in the packets coming in from clients always has VS address.
Hope I am being broadcast. No reply yet.
Note that there is also a port specific wildcard server, so a VS with a network destination and specific port like 10.10.10.10/24:80 could still make use of dest_addr persistence.
Using dest_addr persistence on a VS that only has one address as a destination wouldn't make much sense.
Destination address will always be sent to the same pool member, if available. AKA, it isn't load balanced in your scenario.
My question is can we use dest_addr with standard virtual server type with 2 web servers as pool member?
Yes you can, but you won't be load balancing. Traffic will always go to one node, as long as the node is available.
If the load balancing will not happen, how VS will deciede which pool member to select to new connection? Since the destination address in client request will only contain the VS IP
It will use whatever load balancing method you chose, and then pin every connection to that node.
So if you used round-robin it would select the first node in the list and then pin everything to it for as long as it is available.