Mapping VLANs to Subnets and Gateways

The Anatomy of an IPAM Document

An IPAM document is more than just a list of subnets. It's a detailed spreadsheet that serves as the single source of truth for your network's Layer 3 addressing. A well-structured IPAM provides an at-a-glance understanding of your entire IP space.

What should it contain? While templates vary, a comprehensive IPAM for a large network should include the following fields for each subnet:

• VLAN ID: The numeric identifier for the VLAN.
• VLAN Name / Purpose: A descriptive name (e.g., DATA_HQ, SERVERS_DC).
• Site / Location: The physical or logical location of the subnet (e.g., HQ Building, R&D Data Center).
• Subnet Address (CIDR): The network address and prefix length (e.g., 10.10.0.0/24).
• Subnet Mask: The mask in dotted-decimal notation (e.g., 255.255.255.0).
• Network Address: The first address in the subnet.
• Broadcast Address: The last address in the subnet.
• Default Gateway (SVI): The IP address assigned to the Layer 3 interface for that VLAN. This is the gateway for all hosts in the subnet.
• Usable Host Range: The range of IP addresses available for assignment to devices.
• Static IP Assignments: A reserved range for devices that need fixed addresses (servers, printers, network gear).
• DHCP Scope: The pool of addresses to be handed out by a DHCP server.
• Notes: Any other relevant information, such as security policy notes or planned usage.

The Cisco IP Addressing Guide provides a solid framework for thinking about this.

Defining Assignment Standards

Before you can populate the IPAM, you need a set of rules. A consistent set of standards for assigning addresses within each subnet is the mark of a professional design. It makes the network predictable and vastly simplifies configuration and troubleshooting. Since you're a CLI pro, you know the value of consistency when you're managing dozens or hundreds of devices.

Let's establish our standards for Aperture Logistics:

1. Default Gateway Assignment: The default gateway (which will be the IP address of the Switched Virtual Interface, or SVI, on our L3 switch) will always be the first usable IP address in the subnet (e.g., .1). This is a widely adopted convention.
2. Static IP Reservation: For subnets that contain user devices, we'll reserve a small block of addresses immediately following the gateway for static assignments (e.g., printers, special devices). Let's reserve .2 through .10.
3. DHCP Scope: The remaining block of usable IP addresses will be allocated to the DHCP scope for dynamic client assignment.

This Cisco guide provides excellent recommendations for creating these standards.

Populating the Aperture Logistics IPAM

Now, let's execute. We will take the VLSM plan from our previous lesson, assign logical VLAN IDs, and build out the full IPAM document based on the standards we just defined.

Here's the VLSM allocation we finalized last time:

We will now expand this into our final IPAM document. For clarity, I've assigned logical VLAN IDs that group similar functions.

Aperture Logistics - Final IPAM Document

This table is the culmination of all our planning work so far. It's clear, detailed, and actionable. From this document, any network engineer can understand the addressing scheme and begin configuring interfaces, DHCP scopes, and static routes.

Conclusion

Congratulations! You have just created a professional-grade IPAM document. This crucial step transforms your theoretical VLAN and VLSM plans into a practical, operational blueprint for the Aperture Logistics network. You have not only mapped VLANs to subnets but also established and applied standards for gateway and host addressing, fulfilling a key requirement of enterprise network design.

Key Takeaways:

• The IPAM is the Blueprint: It is the single source of truth for your network's Layer 3 addressing scheme.
• Standards Enforce Consistency: Establishing rules for assigning gateways, static IPs, and DHCP scopes before you start makes the network predictable and easier to manage.
• Documentation is Non-Negotiable: A comprehensive IPAM document saves countless hours of troubleshooting and prevents costly configuration errors like duplicate IP addresses or overlapping subnets.
• From Plan to Action: The IPAM contains all the necessary information (VLANs, subnets, gateways) to begin configuring the network's Layer 3 interfaces and services.

Preview of the Next Lesson:
Our IPAM document looks complete, but in networking, the philosophy is "trust but verify." In the next lesson, we will focus on verifying the IPAM plan for completeness and the absence of overlapping allocations. You will learn how to audit your own work to catch any potential errors before they are implemented in a live environment, ensuring your design is flawless.