Allocating Ip Addresses; The Server Subnet And Proxy Ip Addresses - F5 ARX-VE Planning Manual

Chapter 1
Site Planning

Allocating IP Addresses

The Server Subnet and Proxy IP Addresses

1 - 8
Figure 1.5 ARX as proxy for CIFS and/or NFS transactions
servers
192.168.25.x
172.100.90.x
clients
As a resource proxy with distributed processors, the ARX requires several
IP addresses to communicate with front-end clients and its back-end servers.
Every network processor on the switch requires its own address to terminate
and originate transactions with back-end servers. These IP addresses are
called proxy IP addresses.
Communication to client subnets is less distributed: a minimum of one IP
address is required per namespace to handle client requests. The client-side
IP addresses are called virtual IPs, or VIPs.
The ARX also requires one or more management IP addresses to load new
software images. The switch has one out-of-band management interface,
and you can configure one in-band interface for each VLAN. The in-band
interfaces can also be used to connect one ARX to another in a Resilient
Overlay Network (RON).
Note
At least one in-band management interface is required for any redundant
switch pair.
The proxy IP addresses must reside on a single server subnet. If you have
multiple server subnets in your current network, you can configure static
routes to the remote subnets (through a router on a local server subnet). The
back end
front end
ARX (proxy)