Optical Network Operations at Scale

The optical and transport layer carries everything above it, yet it is the layer most network configuration tools treat as out of scope. Generic NCM platforms model routers and switches well and then stop at the transport boundary, leaving DWDM, OTN, SONET and SDH gear to whatever element manager shipped with the hardware.

That gap has a cost. Optical configuration drifts unnoticed because nothing outside the vendor’s own tooling is watching it. Backups live in a silo, change is manual, and an audit of the transport estate means logging into a different system for every vendor. The optical layer ends up managed to a lower standard than the IP layer that depends on it, which is exactly backwards.

An optical estate is multi-vendor by necessity. It is built up over years of procurement cycles, and the transport gear in the ground spans Ciena, Nokia, Infinera, Adtran, Cisco, Juniper, Ribbon and Fujitsu, often several of them in the same metro. Managing all of it to one standard only works if the management layer is genuinely neutral.

rConfig sells no network hardware. There is no transport line to protect and no reason to favour one optical vendor over another, so neutrality here is structural, not a marketing promise. Driver support is template-driven and customer-extensible, which means a new optical platform is a configuration change rather than a feature request you wait a release cycle for. Every vendor’s kit lands in one inventory, under one configuration standard, on one neutral plane.

That breadth is the proof, not the claim. See multi-vendor configuration management for how the same neutral model holds across the whole estate, IP and optical alike.

The same disciplines you expect on the IP layer, brought to the transport layer and held without manual effort across every vendor in the estate, at the carrier scale covered in managing 100,000 network devices.

Much of the installed transport base still speaks TL1, the legacy command protocol of SONET, SDH, DWDM and OTN gear. It is verbose, quirky, and unlike anything a modern CLI parser expects, which is a large part of why generic NCM tools quietly leave optical alone. rConfig handles TL1 natively, as a first-class protocol alongside CLI, NETCONF and REST.

If your transport estate lives or dies on TL1, that depth is the detail worth reading next. See TL1 configuration management for the protocol’s quirks, why most tools struggle with it, and how rConfig manages TL1 estates at scale.