If... | Then... |
---|---|
The logical networks use VLANs, | the physical compute host must connect to a trunked switch port that has access to these VLANs. It's important to note that the physical network adapters on the computer host must not have any VLAN filtering activated. |
Using Switched-Embedded Teaming (SET) and have multiple NIC team members, such as network adapters, | you must connect all of the NIC team members for that particular host to the same Layer-2 broadcast domain. |
The physical compute host is running additional infrastructure virtual machines, such as Network Controller, SLB/MUX, or Gateway, | that host must have an additional IP address assigned from the Management logical network for each of the virtual machines hosted. Also, each SLB/MUX infrastructure virtual machine must have an IP address reserved for the HNV Provider logical network. Failure to have an IP address reserved may result in duplicate IP addresses on your network. |
Transit logical network | The RAS Gateway and SLB/MUX use the Transit logical network to exchange BGP peering information and North/South (external-internal) tenant traffic. The size of this subnet will typically be smaller than the others. Only physical compute hosts that run RAS Gateway or SLB/MUX virtual machines need to have connectivity to this subnet with these VLANs trunked and accessible on the switch ports to which the compute hosts' network adapters are connected. Each SLB/MUX or RAS Gateway virtual machine is statically assigned one IP address from the Transit logical network. |
Public VIP logical network | The Public VIP logical network is required to have IP subnet prefixes that are routable outside of the cloud environment (typically Internet routable). These will be the front-end IP addresses used by external clients to access resources in the virtual networks including the front end VIP for the Site-to-site gateway. |
Private VIP logical network | The Private VIP logical network is not required to be routable outside of the cloud as it is used for VIPs that are only accessed from internal cloud clients, such as the SLB Mananger or private services. |
GRE VIP logical network | The GRE VIP network is a subnet that exists solely for defining VIPs that are assigned to gateway virtual machines running on your SDN fabric for a S2S GRE connection type. This network does not need to be pre-configured in your physical switches or router and need not have a VLAN assigned. |
Network name | Subnet | Mask | VLAN ID on truck | Gateway | Reservations (examples) |
---|---|---|---|---|---|
Management | 10.184.108.0 | 24 | 7 | 10.184.108.1 | 10.184.108.1 – Router10.184.108.4 - Network Controller10.184.108.10 - Compute host 110.184.108.11 - Compute host 210.184.108.X - Compute host X |
HNV Provider | 10.10.56.0 | 23 | 11 | 10.10.56.1 | 10.10.56.1 – Router10.10.56.2 - SLB/MUX1 |
Transit | 10.10.10.0 | 24 | 10 | 10.10.10.1 | 10.10.10.1 – Router |
Public VIP | 41.40.40.0 | 27 | NA | 41.40.40.1 | 41.40.40.1 – Router41.40.40.2 - SLB/MUX VIP41.40.40.3 - IPSec S2S VPN VIP |
Private VIP | 20.20.20.0 | 27 | NA | 20.20.20.1 | 20.20.20.1 - Default GW (router) |
GRE VIP | 31.30.30.0 | 24 | NA | 31.30.30.1 | 31.30.30.1 - Default GW |
Network name | Subnet | Mask | VLAN ID on truck | Gateway | Reservations (examples) |
---|---|---|---|---|---|
Storage1 | 10.60.36.0 | 25 | 8 | 10.60.36.1 | 10.60.36.1 – Router 10.60.36.X - Compute host X 10.60.36.Y - Compute host Y 10.60.36.V - Compute cluster 10.60.36.W - Storage cluster |
Storage2 | 10.60.36.128 | 25 | 9 | 10.60.36.129 | 10.60.36.129 – Router 10.60.36.X - Compute host X 10.60.36.Y - Compute host Y 10.60.36.V - Compute cluster 10.60.36.W - Storage cluster |
vSwitchName
variable in the config.psd1 file.Host | Hardware Requirements | Software Requirements |
---|---|---|
Physical Hyper-v host | 4-Core 2.66 GHz CPU 32 GB of RAM 300 GB Disk Space 1 Gb/s (or faster) physical network adapter | OS: Windows Server 2016 Hyper-V Role installed |
Role | vCPU requirements | Memory requirements | Disk requirements |
---|---|---|---|
Network controller (three node) | 4 vCPUs | 4 GB min (8 GB recommended) | 75 GB for the OS drive |
SLB/MUX (three node) | 8 vCPUs | 8 GB recommended | 75 GB for the OS drive |
RAS Gateway (single pool of three node gateways, two active, one passive) | 8 vCPUs | 8 GB recommended | 75 GB for the OS drive |
RAS Gateway BGP router for SLB/MUX peering (alternatively use ToR switch as BGP Router) | 2 vCPUs | 2 GB | 75 GB for the OS drive |