Virtual Server Attributes

Hello Chaithy,

1) Auto Last Hop

"When enabled, allows the system to send return traffic to the MAC address that transmitted the request, even if the routing table points to a different network or interface. As a result, the system can send return traffic to clients even when there is no matching route. For example, if the system does not have a default route configured and the client is located on a remote network. This setting is also useful when the system is load balancing transparent devices that do not modify the source IP address of the packet. Without the last hop option enabled, the system could return connections to a different transparent node, resulting in asymmetric routing. You can configure this setting globally and on an object level. You set the global Auto Last Hop value on the System :: Configuration :: Local Traffic :: General screen. To configure this setting globally, retain the Default setting. When you configure Auto Last Hop with a value other than Default at the object level, its setting takes precedence over the global setting. This enables you to configure auto last hop on a per-virtual server basis. The default is Default, meaning that the system uses the global auto-lasthop setting to send back the request."

2) Client Clone By adding a pool to this setting, the F5 will clone (copy) all traffic between the client and VS and send it to that pool.

3) Server Clone By adding a pool to this setting, the F5 will clone (copy) all traffic between the server and VS and send it to that pool

4) Source Port This settings affects the source port of the server side socket (btw the selfIP and the pool member)

Options

• Preserve (default) : the system preserves the value for the source port, unless the source port is already in use, in which case the system uses a different port.

   

• Preserve Strict : the system preserves the value configured for the source port. If the port is in use, the system does not process the connection (for special case such as UDP, nPath routing,...)

   

• Change : the system changes the source port

   

Example 1 : with option "Preserve"

client side connection : src_IPA:port_A --> dst_VIP:port_443

server side connection : selfIP:port_A --> dst_poolmember:port_443

Example 2 : with option "Change"

client side connection : src_IPA:port_A --> dst_VIP:port_443

server side connection : selfIP:port_B --> dst_poolmember:port_443

As you can see, first case the port_A was preserved and in the second example port_A was change to port_B.

Hope it helps

Regards