Provider · Registry · IP space

The address plan.

Every prefix, VLAN, ASN, and VRF with an owner and a purpose. Address space is inventory; unaccounted space is debt. The integrity agent flags overlaps and duplicate scopes before they reach the fabric.

Prefixes94 roots · 5 children

Hottest pool67%203.0.113.0/24

VLANs53 global scope

VRFs44 prefix/VLAN bindings

ASNs412 BGP peerings

Open conflicts21 critical · 1 warning

Prefix tree

parents roll up their children

Prefixes as an indented tree with role and utilization
Prefix	Role	Utilization
10.0.0.0/8	Infrastructure (RFC1918 root)	34%
10.0.0.0/12	Device management	41%
10.16.0.0/12	PoP loopbacks & p2p	28%
10.32.0.0/12	Customer L3 handoffs	52%
100.98.0.0/16	Federation interconnect (CGN range)	18%
100.98.0.0/20	Meridian ↔ NaaS Labs	44%
100.98.16.0/20	Corepath ↔ NaaS Labs	22%
203.0.113.0/24	Public service pool (documentation range in sim)	67%
2001:db8:4e41::/48	IPv6 service pool	9%

Assignments come from the same records the provisioning engine writes. A handoff gets its /31 from 10.32.0.0/12 at turn-up; nothing is typed twice.

VLANs

global = every site, same VID

VLANs with identifier, name, scope, and purpose
VID	Name	Scope	Purpose
100	CUST-HANDOFF	global	Customer L2 handoff (translated per EVC)
210	FED-XCON	ORD	Federation cross-connect
211	FED-XCON	IAD	Federation cross-connect
900	MGMT-OOB	global	Out-of-band management
666	QUARANTINE	global	Compromised-endpoint isolation

ASNs

private range in simulation

Autonomous system numbers with holder and peering count
ASN	Holder	Peerings
AS64500	NaaS Labs (fabric)	5
AS64512	Meridian Capacity Co.	3
AS64513	Corepath Networks	2
AS64514	Aurora Transit	2

VRFs

RD = route distinguisher · RT = route target

Virtual routing instances with route distinguisher, route targets, bound prefixes, site scope, and purpose
VRF	RD	Route targets	Prefixes	Sites	Purpose
MGMT	64500:100	64500:100	10.0.0.0/12	global	Device management
CUST-L3	64500:300	64500:300, 64512:300	10.32.0.0/12	ORDDFWDEN	Customer L3 handoffs
FED-X	64500:210	64512:210, 64513:210	100.98.0.0/16	ORDIAD	Federation interconnect
QUARANTINE-VRF	64500:666	64500:666	10.66.0.0/24	global	Compromised-endpoint isolation (vlan 666 bound)

Each VRF owns its prefixes and VLANs through the bindings below.

Conflict detector

1 critical

Overlapping prefixes and duplicate VLAN scopes are caught here before they reach a routing table. Severity is named in text: a critical row will collide on the wire if it ships; a warning wants a human to disambiguate scope.

warningduplicate VLAN
VLAN 210 (FED-XCON) is defined at both ORD and IAD with the same name. Disambiguate or segment the scope.
- vlanVLAN 210 @ ORD
- vlanVLAN 210 @ IAD
criticaloverlapping prefix
10.32.0.0/12 (Customer L3 handoffs) overlaps a newly discovered 10.32.4.0/22 advertised from a partner edge at DFW.
- prefix10.32.0.0/12
- discovered10.32.4.0/22 @ DFW

Logical to physical bindings

6 links · one owner per record

Logical-to-physical bindings: each row names a binding kind, the logical entity (VRF, VLAN, or ASN), the physical target it owns (prefix, circuit, or site), and a note
Kind	Logical	Bound to	Note
VRF to prefix	VRF MGMT	10.0.0.0/12	Management VRF owns the device-management prefix
VRF to prefix	VRF CUST-L3	10.32.0.0/12	Customer VRF owns the L3 handoff prefix
VRF to VLAN	VRF QUARANTINE-VRF	VLAN 666	QUARANTINE vlan 666 bound to the isolation VRF
VLAN to circuit	VLAN 100	CLR-2416	CUST-HANDOFF vlan 100 carries the DEN-KC handoff
ASN to site	AS64500	DEN	Fabric ASN present at Denver
VRF to VLAN	VRF FED-X	VLAN 210	Federation VRF on FED-XCON vlan 210 (ORD)

These bindings are how a circuit's A and Z endpoints resolve to the VRF, VLAN, and ASN that carry them. Edit a binding and every dependent view reconciles to the same record.