Static route configuration in the customer network - Edge and core routers

This section covers the static route configuration considerations for edge and core routers in the customer network.

The following configuration is required if no dynamic routing protocols (e.g. BGP) are enabled between the stack’s interconnects and the customer network.

Table 1. Static route configuration in the customer network - edge and core routers

Destination Subnet	Netmask	Gateway	Description
hyp_range_subnet	hyp_range_netmask	wan_vip	Route to reach the hypervisor network, which is used for management and control communication between the ThinkAgile CP stack and the Cloud Controller.
vnet_range_subnet1 ... vnet_range_subnetN (optional)	vnet_range_netmask1 ... vnet_range_netmaskN (optional)	wan_vip	One route per VNET, which must be reachable from the customer data center network.1

¹ These routes are only required under two conditions: no dynamic routing protocol is enabled between the ThinkAgile CP stack and the customer data center network; and you want to allow applications running in these VNETs to access hosts in the customer data center network. In other words, the VNET into consideration is using a public IP address range.