Physical Layer
Underlay topology.
Map reality to prevent chaos.
The physical foundation (WDM cabling, Spine/Leaf design) stays critical.
But as density grows, tracking it with flat files or spreadsheets becomes untenable: without a
centralised database, inventory quickly slips out of hand. Before even automating,
rule number one is to model this physical reality with absolute rigour so the infrastructure
becomes traceable, predictable and operable again.
Data Plane
Overlay architecture.
The abstraction and visibility challenge.
Moving to an Overlay (VXLAN) is dramatically efficient to decouple user services
from the physical infrastructure. But that flexibility comes with a hidden cost.
Encapsulation generates a logical matrix (VTEP, VNI)
that makes the data path fully abstract. The real challenge becomes visibility:
understanding and actually visualising deployed topologies is something humans alone can no
longer handle at scale.
Control Plane
EVPN signalling.
Exponential complexity at scale.
This is where the architecture truly hardens. To orchestrate the Overlay,
BGP EVPN brings logic and determinism. But the more the Overlay grows,
the heavier signalling becomes. Distributing hundreds of Route Distinguishers (RD)
and Route Targets (RT) by hand without a single mistake is effectively impossible.
This technical demand creates a complexity wall — but it's precisely this
absolute rigour that opens the door to automation.
Management Plane
Solving the equation with RFC 9315.
Intent-Based Networking.
This is where NetDevOps earns its place. By applying
RFC 9315 (Intent-Based Networking), the extreme complexity of the lower
layers gets absorbed by CI/CD pipelines. Engineers stop typing commands:
they declare Intent in a Source of Truth (SoT). The model is then
validated in lab (NRFU tests), deployed, and continuously verified via
telemetry. The architecture handles the data,
NetDevOps guarantees operational peace of mind.