One of the most operationally compelling aspects of OcNOS is its breadth across network segments. Rather than running different NOS platforms at different layers — a common legacy pattern that creates operational silos, separate training requirements, and inconsistent tooling — OcNOS provides a single platform with consistent CLI, management interfaces, and automation tooling from the access edge to the core.
OcNOS Across the Service Provider Network
The Operational Advantage of a Single NOS
Running a single NOS across the full network stack delivers compounding operational benefits:
- Consistent CLI — engineers trained on OcNOS can operate any segment of the network without learning a new command syntax
- Unified automation — Ansible playbooks, NETCONF templates, and gNMI subscriptions work identically across CSR, aggregation, and DC platforms
- Single TAC contact — one support organization owns all issues regardless of which segment they originate in
- Consistent upgrade path — OcNOS releases ship simultaneously for SP and DC, with a single upgrade qualification process
IP Infusion Marketing Team