Segregated Network
A segregated network would look like below
In this case, these networks would map to different networks.
For example,
- 10.102.1.2 - 10.102.1.20 (VM Network)
- 10.102.2.2 - 10.102.2.20 (ESXi_Network)
- 10.102.3.2 - 10.102.3.20 (Uplink_WAN_Network)
- 10.102.4.2 - 10.102.4.20 (HDM_Internal_Networking)
Identify and map each of the network to the correct network in your environment. Each of the network will have a seperate subnet range and gateway.
Network planning spreadsheet
Please download the spreadsheet Planning Template and use along with your deployment process.
The Planning Template is an active spreadsheet which will allow you to specify the deployment mode you have chosen. You need to select the correct mode using the drop down.
- Choose the "Cloud Type"
- Choose the "Deployment Mode"
- Choose the "Resource Allocation"
After this you need to fill in the number of ESXi on premises and on the cloud. For vCD the number of nodes on the cloud is irrelevant and please fill in 1 here.
The rest of the form requires you to fill in network configuration details like IP address, ranges. The dynamic part of the form gives you information on the number of the resources you need to provision.
The information in the Planning Template is almost identical to the sections below and should serve to identify the size of the IP pool required and capture information for easy entry during the deployment steps.
HDM Network Configuration - Planning
Please fill the table below for use during installation later.
| Network | IP | Netmask | Gateway |
| VM Network (Management Network) | |||
| HDM_Internal_Network | |||
| Uplink_WAN_Network | |||
| ESXi_Network |
Network requirements during on-premise deployment
During the premise deployment phase of the installation we will configure the following networks on prem.
- HDM_Internal_Network
- Uplink_WAN_Network
- ESXi_Network
These are the same as the ones described in previous section on OVF Deployment. During the premise deployment however you need to provide a range or list of IPs for each of these networks.
For all the 3 categories of network, choose the IP allocation mechanism : static IP.
For static IP, following details are required for configuration.
- IP range : IP list that are free to be allocated for use.
- Subnet mask : subnet of the IP range
- Gateway : gateway IP of the network
- Domain : domain name of the network
- DNS : to translate the domain name to IP
- NTP : for time sync
A pool of IP addresses need to be allocated. The number of IPs for each category are
HDM_Internal_Network: 2 IPs required
Uplink_WAN_Network: 2 IPs required
ESXi_Network: 2 IPs required
Note:
- The subnet range 172.17.0.0/16 is not available for the deployment; it is internally used by HDM microservices.
- Please check the static ip usage using arping command before using it to ensure that ip should not be in use. arping -c 2 -w 20 -I ens192 [IP]
Please fill the table below for reference during the installation process.
HDM_Internal_Network
| Example | Fill value here | |
| IP range | 10.102.4.2-10.102.4.4, 10.102.4.7 | |
| Subnet mask | 255.255.0.0 | |
| Gateway | 10.102.4.1 | |
| Domain | domain.lan | |
| DNS | 10.102.5.20, 10.102.5.21 | |
| NTP | 10.102.5.22 |
Uplink_WAN_Network
| Example | Fill value here | |
| IP range | 10.102.3.2-10.102.3.4 | |
| Subnet mask | 255.255.0.0 | |
| Gateway | 10.102.3.1 | |
| Domain | domain.lan | |
| DNS | 10.102.5.20, 10.102.5.21 | |
| NTP | 10.102.5.22 |
ESXi_Network
| Example | Fill value here | |
| IP range | 10.102.2.2-10.102.2.4 | |
| Subnet mask | 255.255.0.0 | |
| Gateway | 10.102.2.1 | |
| Domain | domain.lan | |
| DNS | 10.102.5.20, 10.102.5.21 | |
| NTP | 10.102.5.22 |
Network requirement during on-cloud deployment
Similar to the previous two deployment stages we need to provision IPs and identify the correct networks that satisfy the connectivity requirements. The networks that need to be configured are.
HDM Internal network: 20 IP pool. Will also be used for VMs during migration
WAN network configuration: 2 IPs.
Please fill the table below for reference during the installation process.
HDM_Internal_Network
| Example | Fill value here | |
| IP range | 10.50.10.100-10.50.10.120 | |
| Subnet mask | 255.255.0.0 | |
| Gateway | 10.50.10.1 | |
| Domain | domain.lan | |
| DNS | 10.50.5.20, 10.50.5.21 | |
| NTP | 10.50.5.22 |
Uplink_WAN_Network
| Example | Fill value here | |
| IP range | 10.50.10.121,10.50.10.122, 10.50.10.123 | |
| Subnet mask | 255.255.0.0 | |
| Gateway | 10.50.10.1 | |
| Domain | domain.lan | |
| DNS | 10.102.5.20, 10.102.5.21 | |
| NTP | 10.102.5.22 |
WAN Routing Configuration
The following WAN routes are required to access on-cloud from on-premise and vice-versa. This is required in during the Set WAN route part of cloud configuration.
-
On Premises WAN network details
The route which would be set on HDM appliance on premise. The routes will enable communication from on-premise to HDM appliances on-cloud.
- On-Premise WAN subnet : Subnet of premise WAN network on which HDM appliances are deployed
- On-Premise WAN gateway : On premise WAN gateway which allows access to on-cloud WAN subnet. This should be the IP address of PFSense server on premise which is connected to Uplink_WAN_Network.
-
On Cloud WAN network details
The route which would be set on HDM appliance on cloud. The routes will enable communication from on-cloud to HDM appliances on-premise. This should be the IP address of PFSense server on cloud which is connected to Uplink_WAN_Network.
- On-Cloud WAN subnet : Subnet of cloud WAN network on which HDM appliances are deployed
- On-Cloud WAN gateway : On cloud WAN gateway which allows access to on-premise WAN subnet
| Example | Fill value here | |
| On-Premise WAN subnet | 10.102.0.0/16 | |
| On-Premise WAN gateway | 10.102.10.1 | |
| On-Cloud WAN subnet | 10.50.0.0/16 | |
| On-Cloud WAN gateway | 10.50.10.1 |