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 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, 1 IP for OEM VM (optional) |
Management | Connected (outbound internet access required). Disconnected (Arc autonomous controller). |
Customer-defined management VLAN. (Native VLAN preferred but trunk mode supported). |
2 required 1 optional |
| Total | 6 required, 1 optional for 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 VM, 1 IP for Arc VM management stack VM, 1 IP for OEM VM (new) |
Management | Connected (outbound internet access required). Disconnected (Arc autonomous controller). |
Customer-defined management VLAN. (Native VLAN preferred but trunk mode supported). |
5 required 1 optional |
| Total | 9 minimum. 10 maximum. |
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 VM, 1 IP for Arc VM management stack VM, 1 IP for OEM VM (new) Two-node: 1 Network Controller VM IP 1 Software Load Balancer (SLB) VM IP 1 gateway VM IP |
Management | Connected (outbound internet access required). Disconnected (Arc autonomous controller). |
Customer-defined management VLAN. (Native VLAN preferred but trunk mode supported). |
7 required 1 optional |
| HNV | 2 IPs for each host Two-node: 1 SLB VM IP 1 gateway VM IP |
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 |
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 | 11 minimum 12 maximum |
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for