LEARN. PRACTICE. GROW.Concept and mechanism
Prefix length divides network and host bits. In a conventional IPv4 /27, five bits leave thirty-two total addresses; excluding network and broadcast leaves thirty host addresses. Include the gateway in requirements too. Aggregation requires binary adjacency and alignment rather than visually similar numbers: 10.20.8.0/24 and 10.20.9.0/24 fit exactly within 10.20.8.0/23. A /22 would include more networks and could advertise reachability that does not exist. In IPv6, address scope matters beyond length. Link-local serves the link and does not become global by increasing hop limit or adding a route.
Guided application
In a fictional project, twenty-seven servers and one gateway need addresses. The block fits, but little headroom remains for growth and additional addresses; record the assumption instead of claiming unlimited capacity. The same reasoning applies to CoS. Classifying traffic and arranging queues helps manage loss and delay under congestion without adding physical bandwidth. Compare interactive-call and bulk-copy requirements using interval measurements. Acceptance should state what load fits and what happens when it exceeds capacity. For diagnosis, also distinguish the destination IP address from the local next hop and layer-two resolution. A mask error can make a host seek locally a destination it should reach through the gateway.
28 required addresses fit within the 30 hosts of a conventional /27.
Common pitfalls
Aggregation without alignment; forgetting gateway; link-local as global; CoS as created capacity.
Related topics: Junos planes and state interpretation · CLI, candidate, and rollback · Access, inheritance, and recovery
Calculate scope and make available headroom explicit.
Reference: CIDR and prefix aggregation · JN0-106, effective 2026-04-06; Junos OS 21.2 exam baseline