Template created by Joshaven Potter <josh@wisp.live> https://joshaven.com

Abstract

This document is intended to help you develop both a device naming convention and an IP schema that is simple, meaningful and scalable.

Device Naming

It is often helpful to match the SSID, Device Name & DNS name to the same so that confusion is avoided as much as possible.

I like the format of a letter to indicate your company (“E” is used below for Example)

Followed by the site ID number (in three digit format from 0 to 255)

Followed by the use Indicator shorthand

E000-BGP                        Example Site 0 BGP Peering Router

E001-PE                        Example Site 1 Provider Edge Router

E001-AC                        Example Site 1 Access Control Router

E001-CE                        Example Site 1 Router

E001-AP-RFE40-80                Example Site 1 East AP RF Elements 40º horn at 80º from north

E001-003                        Example Backhaul from Site1 to Site3

E001-002                        Example Backhaul from Site1 to Site2

Example device names (update to your favorite list)

CE        Customer Edge Router

PE        Provider Edge Router

AC        Access Control Router

SW        Switch

POE        Power Over Ethernet Switch (IE: Netonix or ToughSwitch)

WET        Weather Station

N        North Sector

NE        North-East Sector

SE        South-East Sector

SW        South-West Sector

NW        North-West Sector

WiFi        Tower WIFI for remote administration

Simple Scalable IP Schema

First Network 256 POP Sites (aggregatable into 10.0.0.0/21, 10.0.0.0-10.7.255.255)

Loopbacks

10.0.0.{tower_id} /32 assigned one to each tower

Backhaul IP's

10.1.{tower_id}.{device_id}/29

.0-.63                (8) /29 subnets for backhaul

.64-.12 7        (16) /30 subnets for PTP Connections VPLS & bonding, etc.

Primary Access Equipment & Subscriber Management (first 229 devices)

10.2.{tower_id}.{device_id}/24

.1                Assigned to Router

.2                First PoE management Device

.3                AC Power Controller

.4                Site Sensors

.9                Power Outage Notification WiFI

.10-24                Assigned from North-most AP in a clockwise orientation

.25-254        DHCP Pool for Subscriber Management

Secondary Equipment & Subscriber Management (next 229 devices)

10.3.{tower_id}.{device_id}/24

.1                Assigned to Router

.25-254        DHCP Pool for Additional Subscriber Management

Reserved

10.4/16 - 10.7/16

CGNAT IP's or Public IP's are assigned as needed via subnets of size /32 or larger.

If providing NAT at the tower:

100.64.{tower_id}.0/24        Primary

100.65.{tower_id}.0/24        Overflow

If providing NAT at the core:

        100.64.0.0/22                 for first Access Control Router

        100.64.4.0/22                 for second Access Control Router

        100.64.8.0/22                 for third Access Control Router

        100.64.12.0/22        for fourth Access Control Router

Alt1 IP Schema (Unique AP MGMT subnets)

First Network 256 POP Sites (aggregatable into 10.0.0.0/21, 10.0.0.0-10.7.255.255)

Loopbacks

10.0.0.{tower_id} /32 assigned one to each tower

Backhaul IP's

10.1.{tower_id}.{device_id}/29

.0-.63                (8) /29 subnets for backhaul

.64-.12 7        (16) /30 subnets for PTP Connections VPLS & bonding, etc.

Primary Access Equipment & Subscriber Management (58 devices max per AP)

10.2.{tower_id}.{device_id}/26 (64 IP’s per subnet)

.1                Assigned to Router

.2                AP

.3                Reserved

.4-62                DHCP Pool for Subscriber Management

(repeat for 4 subnets) within the /24 (use the second octets 2,3,4,5,6 & 7 for up to 20 AP’s

CGNAT IP's or Public IP's are assigned as needed via subnets of size /32 or larger.

If providing NAT at the tower:

100.64.{tower_id}.0/24        Primary

100.65.{tower_id}.0/24        Overflow

If providing NAT at the core:

        100.64.0.0/22                 for first Access Control Router

        100.64.4.0/22                 for second Access Control Router

        100.64.8.0/22                 for third Access Control Router

        100.64.12.0/22        for fourth Access Control Router

This schema limits each AP to 58 subscribers with can be a limitation especially with Cambium 450M which scales well to higher density deployments.  In this case, you may want to consider using /25 or /24 subnets


Alt2 IP Schema (seporate AP & SM MGMT subnets)

First Network 256 POP Sites (aggregatable into 10.0.0.0/21, 10.0.0.0-10.7.255.255)

Loopbacks

10.0.0.{tower_id} /32 assigned one to each tower

Backhaul IP's

10.1.{tower_id}.{device_id}/29

.0-.63                (8) /29 subnets for backhaul

.64-.12 7        (16) /30 subnets for PTP Connections VPLS & bonding, etc.

Primary Access Equipment Management (first 229 devices)

10.2.{tower_id}.{device_id}/24

.1                Assigned to Router

.2                First PoE management Device

.3                AC Power Controller

.4                Site Sensors

.9                Power Outage Notification WiFI

.10-24                Assigned from North-most AP in a clockwise orientation

Subscriber Equipment & Subscriber Management (next 252 devices)

10.3.{tower_id}.{device_id}/24

.1                Assigned to Router

.2-254        DHCP Pool for Additional Subscriber Management

Reserved

10.4/16 - 10.7/16

CGNAT IP's or Public IP's are assigned as needed via subnets of size /32 or larger.

If providing NAT at the tower:

100.64.{tower_id}.0/24        Primary

100.65.{tower_id}.0/24        Overflow

If providing NAT at the core:

        100.64.0.0/22                 for first Access Control Router

        100.64.4.0/22                 for second Access Control Router

        100.64.8.0/22                 for third Access Control Router

        100.64.12.0/22        for fourth Access Control Router

Note: 10.3.{Tower_ID}.x-10.7.{Tower_ID}.x can be further subnetted per AP as desirable.

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.