Activate F5 product registration key
Verify the proper operation of your BIG-IP system
Get up to speed with free self-paced courses
Join the community of 250,000+ technical peers
Advance your career with F5 Certification
Product Manuals and Release notes
In situations where the BIG-IP Controller accepts connections for virtual servers from more than one router, you can send the return data back through the same device from which the connection originated. You can use this option to spread the load among outbound routers, or to ensure that connections go through the same device if that device is connection-oriented, such as a proxy, cache, firewall, or VPN router.
To set up last hop pools, define a list of routers as a pool from which the BIG-IP Controller receives packets. For information about creating a pool, see Defining pools, on XREF. The BIG-IP Controller determines the MAC address of the routers when you define the pool. Then the pool is associated with the virtual server by using the lasthop keyword to specify the last hop pool for the virtual server. When a packet arrives for the virtual server, the MAC address that the packet came from is matched up with the MAC address of the members of the last hop pool. The IP address of the matching member is stored with the connection as the last hop address. Then, connections coming from nodes and heading out towards the client are routed to the router with that last hop address, instead of to the default route.
Use the following syntax to configure last hop pools for virtual servers:
bigpipe vip <vip>:<port> lasthop pool <pool_name>
For example, you might use the following command:
bigpipe vip 192.168.1.10:80 lasthop pool secure_routers
Before you follow this procedure, you must configure at least one pool (for your routers or firewalls) and one virtual server that references the pool.