Find the connection.
Follow the network from a site and closet down to a switch port. Use recorded observations to investigate where an endpoint was seen.
Explore network visibility
Network & asset operations
Know your network.
Know your network.
Keep its story.
The connections. The equipment. The work that keeps it all running. Cenovel brings them together in one console, on your own appliance.
For school districts and multi-site organizations.
Kept in context.
The whole picture.
The details that matter.
When equipment, connections, and work share the same record, there’s a clear place to start.
Follow the equipment.
Keep locations, custody, components, and replacement history with the asset, from the storeroom to its next assignment.
Explore asset operationsPrepare the next visit.
Bring closet access details, open work, capacity readings, and available spares together before heading out.
Explore field workA closer lookThe equipment.
The equipment.
Everything around it.
Connect the location, observations, and work history to the equipment. Keep the context together as you investigate a connection or plan the next visit.
Built around the workA useful place
A useful place
to start the day.
Move from a question to its context, then keep what happened for the next person.
See the operations features- 01
See what needs a look
Review what is not answering Cenovel and distinguish unplanned interruptions from scheduled maintenance.
- 02
Work with the context
Follow the device to its closet, connected equipment, and related work. Open the guide you need.
- 03
Keep the history
Record moves, replacements, and the work performed, so the next investigation has a starting point.
Your environment.
Your appliance.
Understand how Cenovel fits before you bring it into your network.
Self-hosted by design
The console and operational records live on your appliance. Review the deployment requirements and external connections.
Plan your deploymentClear about what it knows
“Not answering Cenovel” reports an observation. Missing information stays distinct from a failed read or a known value.
Understand the status statesRead, then choose to act
Monitoring reads are separate from device changes. Supported writes must be enabled and reviewed before they run.
See how changes work