This document is not maintained any longer.Deploying Network Hub
The first step of the VPN infrastructure configuration is to deploy the network hub. The network hub is the core component in the VPN infrastructure that provides VPN connections and services to remote sites and users. All traffic in the VPN is routed through the network hub.
Veeam PN supports two scenarios of the network hub deployment:
- Microsoft Azure deployment
This scenario is recommended if you run some applications and services in Microsoft Azure and need to join an on-premises network with the Microsoft Azure network (site-to-site scenario), or provide users in remote networks with access to applications and services in Microsoft Azure (point-to-site scenario). In such situation, you must place the network hub in a Microsoft Azure network. After that, you must deploy site gateways in on-premises networks (site-to-site scenario) or configure OpenVPN on remote user computers (point-to-site scenario).
Setup of the VPN infrastructure with the network hub residing in Microsoft Azure is easier. You do not have to manually configure routing on remote sites — routes between remote sites are automatically added to the user-defined routing table in the Microsoft Azure network. However, since the VPN traffic is routed through the Microsoft Azure, such deployment scenario may involve additional expenses.
- Amazon AWS deployment
This scenario is recommended if you run some applications and services in Amazon AWS and need to join an on-premises network with the Amazon AWS network (site-to-site scenario), or provide users in remote networks with access to applications and services in Amazon AWS (point-to-site scenario). In such situation, you must place the network hub in an Amazon AWS network. After that, you must deploy site gateways in on-premises networks (site-to-site scenario) or configure OpenVPN on remote user computers (point-to-site scenario).
Setup of the VPN infrastructure with the network hub residing in Amazon AWS is easier. You do not have to manually configure routing on remote sites — routes between remote sites are automatically added to the user-defined routing table on the Amazon AWS network. However, since the VPN traffic is routed through Amazon AWS, such deployment scenario may involve additional expenses.
- On-premises deployment
This scenario is recommended if you want to join several remote on-premises networks (site-to-site scenario) or provide remote users with access to resources in an on-premises network (point-to-site scenario). In such situation, you must place the network hub in an on-premises network. After that, you can deploy site gateways in other on-premises networks that you want to add to the VPN (site-to-site scenario) or configure OpenVPN on remote user computers (point-to-site scenario).
Setup of the VPN infrastructure with the network hub residing in an on-premises network is more complicated than that for Microsoft Azure. You will need to manually configure routing between local sites. For more information, see Adding Static Routes on Default Gateways.
Note |
Within the Veeam PN deployment wizard, there is no option to set a static IP for the network hub appliance. If you want to set a static IP, you can configure it manually or use the Netplan tool. |
In This Section