Subnet Allocation for a Server Rack
Intermediate DesignQuestion
You are designing the IP addressing for a new server rack in a datacenter. The available block is 172.16.0.0/24. Allocate subnets for four segments: Management (8 hosts), Production (30 hosts), Database (6 hosts), and Monitoring (4 hosts). Use VLSM and keep allocations contiguous for easy summarization.
Given
{
"network": "172.16.0.0/24",
"segments": [
{
"name": "Management",
"hosts": 8
},
{
"name": "Production",
"hosts": 30
},
{
"name": "Database",
"hosts": 6
},
{
"name": "Monitoring",
"hosts": 4
}
]
}
Answer
{
"subnets": [
{
"segment": "Production",
"subnet": "172.16.0.0/26",
"usable_hosts": 62,
"range": "172.16.0.1 - 172.16.0.62",
"broadcast": "172.16.0.63"
},
{
"segment": "Management",
"subnet": "172.16.0.64/28",
"usable_hosts": 14,
"range": "172.16.0.65 - 172.16.0.78",
"broadcast": "172.16.0.79"
},
{
"segment": "Database",
"subnet": "172.16.0.80/28",
"usable_hosts": 14,
"range": "172.16.0.81 - 172.16.0.94",
"broadcast": "172.16.0.95"
},
{
"segment": "Monitoring",
"subnet": "172.16.0.96/29",
"usable_hosts": 6,
"range": "172.16.0.97 - 172.16.0.102",
"broadcast": "172.16.0.103"
}
],
"remaining": "172.16.0.104/29 through 172.16.0.255/24 (152 addresses free)"
}
Try to solve it first, then click Reveal Answer
Step-by-Step Explanation
Step 1: Order segments by size (largest first)
| Segment | Required Hosts | Prefix Needed | Block Size |
|---|---|---|---|
| Production | 30 | /26 | 64 |
| Management | 8 | /28 | 16 |
| Database | 6 | /28 | 16 |
| Monitoring | 4 | /29 | 8 |
Step 2: Find minimum prefix for each segment
- Production (30 hosts): 2^5 = 32 < 32 needed (must include network + broadcast), so 2^6 = 64 → /26 (62 usable) ✓
- Management (8 hosts): 2^4 = 16 → /28 (14 usable) ✓
- Database (6 hosts): 2^4 = 16 → /28 (14 usable) ✓
- Monitoring (4 hosts): 2^3 = 8 → /29 (6 usable) ✓
Step 3: Allocate sequentially, largest first
172.16.0.0/26 → Production (block: .0 - .63, 64 addresses)
172.16.0.64/28 → Management (block: .64 - .79, 16 addresses)
172.16.0.80/28 → Database (block: .80 - .95, 16 addresses)
172.16.0.96/29 → Monitoring (block: .96 - .103, 8 addresses)
Total allocated: 64 + 16 + 16 + 8 = 104 addresses Remaining: 256 - 104 = 152 addresses free (172.16.0.104 - 172.16.0.255)
Step 4: Security considerations for datacenter segments
| Segment | ACL Recommendation |
|---|---|
| Management | Only accessible from admin workstations; block from Production/Monitoring |
| Production | Can reach Database; no direct internet access |
| Database | Block all inbound except from Production subnet |
| Monitoring | Read-only access to all segments; no outbound internet |
Step 5: Verify subnet boundaries align
/26 boundaries: 0, 64, 128, 192 → 172.16.0.0 ✓ /28 boundaries: multiples of 16 → .64, .80 ✓ /29 boundaries: multiples of 8 → .96 ✓
All allocations are correctly aligned to their block size.
Related Terms
More Design Worksheets
Home Lab Network Segmentation
Beginner
Allocate /30 Subnets for 15 Router Links
Intermediate
Cloud VPC CIDR Planning with 3 Availability Zones
Intermediate
Design Addressing for a 50-Person Office
Intermediate
VLAN Addressing for a Multi-Floor Building
Intermediate
Address Plan for 4 Branch Offices
Advanced