Review two-node storage reference pattern IP requirements for Azure Stack HCI
Applies to: Azure Stack HCI, versions 23H2 and 22H2
In this article, learn about the IP address requirements for deploying a two-node network reference pattern in your environment.
Deployments without microsegmentation and QoS enabled
| Network | IP component | Network ATC intent | Network routing | Subnet properties | Required IPs |
|---|---|---|---|---|---|
| Storage 1 | 1 IP for each host | Storage | No defined gateway. IP-less L2 VLAN. |
Network ATC managed subnet. Default VLAN tag 711. |
2 |
| Storage 2 | 1 IP for each host | Storage | No defined gateway. IP-less L2 VLAN. |
Network ATC managed subnet. Default VLAN tag 712. |
2 |
| Management | 1 IP for each host, 1 IP for Failover Cluster, 3 IPs for Azure Resource Bridge (ARB) management stack, 1 IP for VM update role, 1 IP for OEM VM (optional) |
Management | Connected, outbound access to required URLs. | Customer-defined management VLAN. (Native VLAN preferred but trunk mode supported). |
7 required 1 optional |
| Total | 11 IPs minimum. 12 IPs if using optional OEM VM. |
Deployments with microsegmentation and QoS enabled
| Network | IP component | Network ATC intent | Network routing | Subnet properties | Required IPs |
|---|---|---|---|---|---|
| Storage 1 | 1 IP for each host | Storage | No defined gateway. IP-less L2 VLAN. |
Network ATC managed subnet. Default VLAN tag 711. |
2 |
| Storage 2 | 1 IP for each host | Storage | No defined gateway. IP-less L2 VLAN. |
Network ATC managed subnet. Default VLAN tag 712. |
2 |
| Management | 1 IP for each host, 1 IP for Failover Cluster, 1 IP for Network Controller REST API, 3 IPs for Azure Resource Bridge (ARB) management stack, 1 IP for VM update role, 1 IP for OEM VM (optional) |
Management | Connected, outbound access to required URLs. | Customer-defined management VLAN. (Native VLAN preferred but trunk mode supported). |
8 required 1 optional |
| Total | 12 IPs minimum. 13 IPs if using optional OEM VM. |
Deployments with SDN optional services
| Network | IP component | Network ATC intent | Network routing | Subnet properties | Required IPs |
|---|---|---|---|---|---|
| Storage 1 | 1 IP for each host | Storage | No defined gateway. IP-less L2 VLAN. |
Network ATC managed subnet. Default VLAN tag 711. |
2 |
| Storage 2 | 1 IP for each host | Storage | No defined gateway. IP-less L2 VLAN. |
Network ATC managed subnet. Default VLAN tag 712. |
2 |
| Tenant compute | Tenant VM IPs connected to corresponding VLANs | Compute | Tenant VLAN routing/access customer-managed. VLAN trunk configuration on the physical switches required. |
Customer-defined | |
| Management | 1 IP for each host, 1 IP for Failover Cluster, 1 IP for Network Controller REST API, 3 IPs for Azure Resource Bridge (ARB) management stack, 1 IP for VM update role, 1 IP for OEM VM (optional) Two-node: 1 IP for Network Controller VM, 1 IP for Software Load Balancer (SLB) VM, 1 IP for Gateway VM |
Management | Connected, outbound access to required URLs. | Customer-defined management VLAN. (Native VLAN preferred but trunk mode supported). |
11 required 1 optional |
| HNV | 2 IPs for each host Two-node: 1 IP for SLB VM 1 IP for Gateway VM |
N/A | Requires default gateway to route the packets externally. | Provider Address Network VLAN Subnet size needs to allocate hosts and SLB VMs Potential subnet growth to be considered |
6 required (NC-managed IPs) |
| Public VIPs | SLB and gateway public VIPs | N/A | Advertised through BGP | Network Controller-managed IPs | |
| Private VIPs | SLB private VIPs | N/A | Advertised through BGP | Network Controller-managed IPs | |
| GRE VIPs | GRE connections for gateway VIPs | N/A | Advertised through BGP | Network Controller-managed IPs | |
| L3 Forwarding | N/A | Separate physical network subnet to communicate with virtual network | |||
| Total | 21 IPs minimum. 22 IPs if using optional OEM VM. |
Next steps
Learn about Two-node reference pattern components.