Complete all the information in the Scale Unit 1 tab. For information about the fields, see Network integration planning for Azure Stack on the Microsoft website.

In the Node Count field, enter the node count for the customer’s Azure Stack Hub specifications (4, 8, 12, or 16).

In the Scale Unit 1 tab of the Deployment Worksheet, you must provide the following network addresses to support the Azure Stack Hub deployment process. The deployment team uses the Deployment Worksheet to break out the IP networks into all the smaller networks that the system requires.

For detailed descriptions of each network, see <Network design and infrastructure> in Appendix A.

In this example, we completed the Scale Unit tab of the Deployment Worksheet with the values that are shown in the following table.

After you fill in all fields in the Scale Unit tab, run the Generate function of the Deployment Worksheet PowerShell module (Action > Generate). The Generate function creates two new tabs:

• Subnet Summary tab
• IP Assignments tab

The Subnet Summary tab shows how the supernets are split to create all the required networks, as shown in the following table. Our example includes only a subset of the columns on this tab. The actual result lists more details of each network.

The switch infrastructure network is broken into multiple networks that the physical switch infrastructure uses. This infrastructure network is different from the Azure Stack Hub infrastructure network, which only supports the Azure Stack Hub software.

The switch infrastructure network supports only the physical switches and their interconnectivity. The following table shows the subnets that are defined within the switch infrastructure network.

The network types are:

• Point-to-point (P2P)—These networks provide connectivity between all switches. The subnet size is a /30 network for each P2P. The lowest IP is always assigned to the upstream (North) device on the stack.
• Loopback—These /32 networks are assigned to each switch used in the rack. The border devices are not assigned a loopback since they are not expected to be part of the Azure Stack Hub solution.
• Switch Mgmt or Switch Management—This /29 network supports the dedicated management interfaces of the switches in the rack. The following table shows the IP address assignments. This table is also in the IP Assignments tab of the Deployment Worksheet.

The IP Assignments tab shows how the IPs are consumed.

The supernet for the BMC network is now a /26 network. The gateway uses the first IP address in the network followed by the BMC devices in the rack, as shown in the following table. The hardware lifecycle host has multiple addresses that are assigned on this network and can be used to deploy, monitor, and support the rack. These IP addresses are distributed into these groups: DVM, InternalAccessible, and ExternalAccessible.

The storage network is a private network and is not intended to be routed beyond the rack. It is the first half of the private network supernet. It is used by the switches with addresses allocated as shown in the following table, and it is not routed beyond the rack. The gateway is the first IP address in the subnet.

The second half, which is used for the Internal VIPs, is a private pool of addresses that the Azure Stack Hub SLB manages and is not shown on the IP Assignments tab. See the following table. These networks support Azure Stack Hub, and the ACLs on the ToR switches prevent these networks from being advertised and accessed outside the solution.

The infrastructure network supernet requires a /24 network and continues to be a /24 after the Deployment Worksheet tool runs. The gateway is the first IP address in the subnet, as shown in the following table.