Plumbline configuration management
Plumbline reads the running configuration of your core, transport and RAN estate, compares it against your standard build, and shows where nodes have drifted apart over time. The same model then automates routine change, so fewer maintenance windows overrun and fewer changes roll back.
| Element | Deviation | Status |
|---|---|---|
| pgw-core-02 | Software 21.4 vs standard 21.7 | Version skew |
| rtr-agg-11 | Interface MTU 1500 vs 9000 | Off standard |
| sbc-core-04 | NTP source differs from peers | Drift |
| mme-core-07 | Syslog target missing | Off standard |
| csr-edge-22 | Hostname naming exception | CHG-88412 |
| hss-core-01 | SNMP location string updated | CHG-88401 |
In production at tier-1 and multi-market operators across Europe and Asia Pacific, in mobile core, IP transport and RAN estates. Customer references available under NDA.
Emergency changes, vendor professional services and years of parallel rollout programmes leave configuration behind that nobody records. Over time the nodes that were meant to be identical stop being identical, and the estate that is running stops matching the one that was designed.
The cost shows up later, and it shows up as time. Maintenance windows overrun because the starting state was not what the method of procedure assumed. Changes roll back because one node in the batch was different. New engineers spend their first months learning which boxes are special and why. None of it is a disaster on any given night, and all of it adds up across a year.
Plumbline measures that gap continuously and gives you a way to close it.
Domains are licensed separately, so most customers start with one and extend once the model is proven.
Software version alignment, timer consistency across nodes of the same role, and configuration parity between geographically redundant pairs.
Interface and MTU consistency, routing policy parity, QoS class definitions and naming conventions across backbone and aggregation.
Consistency between the live estate and the planning tool, feature activation parity, and parameters left behind after optimisation.
Plumbline runs inside the operator's OSS environment on bare metal, VMs or Kubernetes. There is no hosted option and no requirement for outbound connectivity from the management network, which is usually what makes it straightforward to approve internally.
Subscription based collection for platforms that support it, cutting full estate collection time on large transport domains.
Starter role definitions for the 5G standalone core, shipped with 4.2 and editable in your own repository.
A customer operator group reports fewer maintenance windows overrunning after moving routine core changes onto Plumbline workflows.
Send us a configuration export from one domain and we will send back a sample consistency report against a standard build derived from it. No access to your network, no installation, nothing to approve.