Subnetting allows you to create multiple logical networks that exist within a single Class A/B/C network.

You are tasked to setup a network given a 172.29.0.0/16 address. We have 16 bits to work with for subnetting.

• 15 states
• 6 data centers in each state
• 50 servers per data center

Keep in mind we need point-to-point connections from HQ to the 15 regions and from the regions to each data center. That means we need at least 2 x 15 = 30 WAN IPs in the first subnet division.

# of Hosts (3rd octet) Subnet Mask
128 /17
64 /18
32 /19
16 /20
8 /21
4 /22

So we need to borrow 3 bits from the 255.255.0.0 mask for a /19 mask with 32 hosts.

State Network
CA 172.29.0.0/19
MN 172.29.32.0/19
WA 172.29.64.0/19
CO 172.29.96.0/19
NJ 172.29.128.0/19

I’m not showing all the states but each network will be at increments of 32. Let’s take a look at the Colorado (172.29.96.0/19) network. There are 6 data centers. This means at least we need a subnet with at least (2×6) 12 hosts. Luckily we need a minimum of 50 hosts per subnet anyway. Depending on their growth intent (subnets vs more IPs). If the customer decides 50 clients are enough per data center, but they may add additional data centers, we should make sure we can accommodate the clients first. We’ll need to borrow 2 bits from the 4th octet (64 hosts), so our mask will be /26

128 /25
64 /26
32 /27
16 /28
8 /29
4 /30

The six data center networks:

 172.29.96.0/26 172.29.96.64/26 172.29.96.128/26 172.29.96.192/26 172.29.97.0/26 172.29.97.64/26

Each center has a router that needs to be linked to the Colorado router. The point-to-point connections total to (5 x 2) 10 IPs. We can start from 172.29.97.128/26.

WAN IPs:

 172.29.97.128/30 172.29.97.132/30 172.29.97.136/30 172.29.97.140/30 172.29.97.144/30 172.29.97.148/30

You can use this calculator to check:
http://www.vlsm-calc.net/