Planning the service infrastructure
As we saw earlier, the service infrastructure is what ties everything together. To ensure all the components can communicate with each other, a subnet is needed; this serves as the backbone of everything. IP addresses will be needed to set up internal VPN tunnels and BGP peers.
Since this subnet serves as your backbone network in the cloud, and the cloud is connected to your data centers, a range needs to be selected that does not overlap with any of the production networks. In most cases, an x.x.x.x/23 subnet should suffice to provide enough IP addresses to support the entire infrastructure. However, if the deployment calls for several thousands of remote users in several different locations globally or a large number of remote networks in many different countries, a larger subnet may be required.
