Table of Contents Link to heading

• Design Inputs: What to Establish Before Allocating Subnets
• Device Categories That Require IP Addresses
• Static versus Dynamic Addressing
• Subnet Allocation
• Common Addressing Standards
• Guidelines for VLSM

Design Inputs: What to Establish Before Allocating Subnets Link to heading

A well-structured IP addressing plan is one of the most durable investments in any network design. Getting it right early avoids the painful process of re-addressing production networks — a task that, in large environments, can take months and carry significant risk.

Before allocating a single subnet, establish the following parameters:

1. Number of sites and their physical distribution
2. Device count per site, broken down by device category — not aggregated — because different categories will land in different subnets
3. Per-site requirements across all network segments: data, wireless, VoIP, CCTV, video conferencing, access control, network management, server infrastructure, point-to-point links, and loopback addressing
4. Expected growth over a 3–5 year horizon — size subnets to accommodate growth, not just current device counts

Device Categories That Require IP Addresses Link to heading

End devices requiring a routable IP address:

1. Network hosts (workstations, laptops)
2. Peripherals with network interfaces (networked printers, IP cameras)
3. Administrator and management workstations
4. Servers (application, database, file, authentication)
5. Other end devices: IP phones, video conference endpoints

Network infrastructure devices requiring an IP address for routing:

1. Router LAN interfaces
2. Router WAN interfaces (serial, Ethernet, subinterfaces)

Network infrastructure devices requiring a management IP:

1. Layer 2 and Layer 3 switches (SVI for management)
2. Wireless access points and controllers

Static versus Dynamic Addressing Link to heading

The boundary between static and dynamic addressing is determined by the device’s operational role, not its physical type:

1. Use static addresses for all infrastructure and services requiring predictable reachability: servers, printers, WAPs, router interfaces, switch management SVIs, and any device that other systems reference by IP directly (e.g., SNMP targets, syslog destinations, NTP servers). Static addresses simplify monitoring, ACL maintenance, and troubleshooting — you know exactly where to look.

2. Use dynamic addressing (DHCP) for end-user devices, IP phones, and any device whose identity is managed through DNS or a directory service rather than its IP. DHCP reduces provisioning overhead and eliminates address conflicts from manual assignment errors.

Subnet Allocation Link to heading

Consistent subnet sizing by device category simplifies routing, ACL design, and capacity planning:

• Use RFC 1918 private space for all internal networks; reserve public addressing for external-facing interfaces only.
• Allocate /24 subnets for user device segments — sufficient for most access layer deployments while keeping the subnet boundary intuitive.
• Allocate a separate /24 for VoIP devices per site, keeping voice and data traffic in distinct subnets to simplify QoS policy application and troubleshooting.
• Allocate dedicated subnets for CCTV, access control, and video conferencing — these systems have distinct security and traffic profiles that benefit from subnet-level isolation.
• Reserve address space for future expansion; a contiguous block you reserve now is far easier to summarise into a routing policy than a non-contiguous allocation added later.
• Use /30 subnets for point-to-point routed links — exactly two usable addresses, no wasted space, no ambiguity about which end is which.
• Use /32 for loopback interfaces — loopbacks are host routes and should be treated as such.

Common Addressing Standards Link to heading

Defining and documenting addressing conventions before deployment pays dividends during troubleshooting. Engineers familiar with the standards can derive expected addresses without consulting documentation.

Recommended conventions:

• Use .1 or .254 consistently as the default gateway address across all subnets — pick one and enforce it; mixing creates confusion during incident response.
• Align VLAN IDs with the third octet of the subnet (e.g., subnet 10.10.150.0/24 maps to VLAN 150). This makes the relationship between L2 and L3 immediately legible from either the switch or the routing table.
• Reserve .1–.15 for static infrastructure assignments and .16–.239 for DHCP — leaving .240–.253 as a buffer for expansion.
• Apply a consistent device naming convention that encodes location, device type, and sequence — e.g., ausydrtr61 for a router in Sydney, Australia. Descriptive hostnames accelerate troubleshooting by making the target’s role and location visible in logs, SNMP output, and CLI prompts.

Guidelines for VLSM Link to heading

Variable Length Subnet Masking allows efficient use of address space by right-sizing subnets to actual requirements, but introduces complexity if applied without discipline:

• Design for summarisation first. Contiguous address blocks at each hierarchical level (access, distribution, core) enable route aggregation, which reduces routing table size and simplifies policy application.
• Group subnets of similar size together within a larger block. Fragmented, non-contiguous allocations make summarisation impossible and turn the routing table into an operational liability.
• Allocate VLSM subnets by subdividing a standard block — take a /24, carve out a /26 for one segment, a /27 for another. Avoid mixing classful boundaries within the same address block.
• Avoid using two different classful masks within the same major network. While CIDR allows it, the resulting summarisation behaviour can be counterintuitive and varies by routing protocol.