A well-designed network is half the job. The other half is knowing, at any moment, what state it is in, how it got there, and whether that matches what you intended. One Step helps providers and enterprises run their networks that way, and the pages in this section cover the pieces.

Know the state of the network from the network

Monitoring is not a dashboard someone glances at. It is the network telling you, before a customer does, that a link is taking errors, a session has dropped or a device has changed. The alarms you trust are the ones that have been tuned until they are quiet when nothing is wrong.

Keep a history of every change

Documentation starts with the logical map, the physical map and the address list, and it is only useful if it survives the person who wrote it. Every configuration should exist outside the device that runs it, with a record of who changed it, when and why. When the running configuration drifts from that record, you want to know the same day, not during the outage.

Report on what matters

Reporting turns the same data into the hourly, daily and yearly views that tell you where to spend money next and which problems keep coming back.

The people who run it

None of it works without people who know the network and have been shown how to use the tools. We train the team that will be on call, not only the person who hired us.

Where this leads

The networks our clients want to run are ones that notice their own drift and put themselves back to the intended state, with a record of having done so. Getting there starts with the three disciplines above: a true picture of the current state, a kept history of changes, and alarms you believe. Talk with us about where yours stands.