Choosing Traffic IP Addresses

The Virtual Traffic Manager is typically attached to a front-end network for incoming traffic and a back-end network for back-end servers. At the IP level, these networks are described as IP subnets. For example, 192.0.2.0/24, 198.51.100.0/16, and so on.

For single-hosted and multi-hosted traffic IP groups, you must choose traffic IP addresses that are within these directly attached subnets. The Virtual Traffic Manager raises these IP addresses on the correct physical interface, so that routers and other devices on those networks can reach them directly.

For RHI traffic IP groups, you must choose traffic IP addresses that are not within these directly attached subnets. The Virtual Traffic Manager always raises RHI traffic IP addresses privately in their own /32 subnet on the Virtual Traffic Manager's internal loopback (lo) interface. Routers and other machines always send traffic to them indirectly, through the Virtual Traffic Manager's front-end IP address, according to routing information established using the OSPFv2 routing protocol.

The directly attached subnets are those you specify:

When configuring a statically raised IP address on a particular interface.

By adding an entry into the "Traffic IP Networks" table. For more information, see Interface-to-Subnet Mapping (Traffic IP Networks).