Edit

Review single-server storage reference pattern IP requirements for Azure Stack HCI

  • Article

Applies to: Azure Stack HCI, versions 23H2 and 22H2

In this article, learn about the IP requirements for deploying a single-server network reference pattern in your environment.

Deployments without microsegmentation and QoS enabled

The following table lists network attributes for deployments without microsegmentation and Quality of Service (QoS) enabled. This is the default scenario and is deployed automatically.

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.		 1 optional if connected to switch.
Storage 2 1 IP for each host Storage No defined gateway.
IP-less L2 VLAN.		 Network ATC managed subnet.
Default VLAN tag 712.		 1 optional if connected to switch.
Management 1 IP for each host,
1 IP for Failover Cluster,
1 IP for OEM VM (optional)		 Management Outbound connected (internet access required).
Disconnected (Arc autonomous controller).		 Customer-defined management VLAN.
(Native VLAN preferred but trunk mode supported).		 2 required,
1 optional.
Total 2 required.
2 optional for storage,
1 optional for OEM VM.

(Optional) Deployments with microsegmentation and QoS enabled

The following table lists network attributes for deployments with microsegmentation and QoS enabled. This scenario is optional and deployed only with Network Controller.

Network IP component Network ATC intent Network routing Subnet properties Required IPs
Storage 1 1 IP for each host Storage No defined GW.
IP-less L2 VLAN.		 Network ATC managed subnet.
Default VLAN tag 711.		 1 optional if connected to switch.
Storage 2 1 IP for each host Storage No defined GW.
IP-less L2 VLAN.		 Network ATC managed subnet.
Default VLAN tag 712.		 1 optional if connected to switch.
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 Outbound connected (internet access required).
Disconnected (Arc autonomous controller).		 Customer-defined management VLAN.
(Native VLAN preferred but trunk mode supported).		 4 required,
1 optional
Total 4 Required.
2 optional for storage,
1 optional for OEM VM.

Deployments with SDN optional services

The following table lists network attributes for deployments 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 GW.
IP-less L2 VLAN.		 Network ATC managed subnet.
Default VLAN tag 711.		 1 optional if connected to switch.
Storage 2 1 IP for each host Storage No defined GW.
IP-less L2 VLAN.		 Network ATC managed subnet.
Default VLAN tag 712.		 1 optional if connected to switch.
Tenant compute Tenant VM IPs connected to corresponding VLANs Compute Tenant VLAN routing/access customer-managed.
VLAN trunk configuration on 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)

Single 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).		 6 required
1 optional
HNV (also known as PA network) 2 IPs for each host

Single node:
1 SLB VM IP
1 gateway VM IP		 N/A Requires default gateway to route packets externally. Provider Address Network VLAN.
Subnet needs to allocate hosts and SLB VMs.
Potential subnet growth consideration.		 IPs automatically assigned out of the subnet by Network Controller
Public VIPs LB and GWs, Public VIPs N/A Advertised through BGP Network Controller-managed IPs
Private VIPs LB Private VIPs N/A Advertised through BGP Network Controller-managed IPs
GRE VIPs GRE connections, gateway VIPs N/A Advertised through BGP Network Controller-managed IPs
L3 Forwarding N/A Separate physical subnet to communicate with virtual network
Total 6 required.
2 optional for storage,
1 optional for OEM VM.

Next steps