Open network protocol coverage
Collectors normalize SNMP v2/v3, SSH/CLI, REST and cloud APIs, NetFlow, sFlow, IPFIX, CDP, and LLDP into site, device, topology, flow, port, and configuration context.
Network operations
See the path behind the problem.
Connect discovery, topology, traffic and configuration history before you change a client’s network.
A change you can inspect
Follow the dependency. Then choose the action.
Network operations
Live state, configuration history, and change evidenceTopology previewSelected site
Illustrative workflow · explore the steps · no action is executed
01
Deploy a regional collector
Place a tenant-bound collector near the managed network and grant only the Digital Vault-held credentials it needs.
Confirm this step for your release, permissions and environment.02
Discover and normalize
Collect supported SNMP, CLI, REST, cloud, neighbor, and flow data into a consistent device and topology model.
Confirm this step for your release, permissions and environment.03
Investigate or change
Run remote diagnostics or route a configuration action through review, approval, execution, and evidence.
Confirm this step for your release, permissions and environment.Connect discovery, topology, traffic, configuration, and remote diagnostics.
Use site-bound collectors to map supported L1/L2/L3 relationships, traffic, and configuration state.
Move configuration change through comparison, approval, execution, verification, and rollback evidence.
Inside the workflow
The work this connects.
- Multi-method collection
- Use SNMP, CLI, REST, cloud APIs, CDP, and LLDP across supported network vendors.
- Topology and port mapping
- Build dynamic L1, L2, and L3 views with switch-port, VLAN, subnet, and endpoint relationships.
- Traffic visibility
- Ingest NetFlow, sFlow, and IPFIX to explain talkers, applications, interfaces, and paths.
- Wireless and edge operations
- Monitor supported wireless, firewall, and VPN state beside the rest of the client network.
- Configuration assurance
- Back up configurations, compare versions, detect drift, and restore an approved known state.
- Remote diagnostics
- Run supported path, reachability, DNS, interface, and device checks without a site visit.
Try one useful scenario
Configuration drift with an unsupported command
Fictional example: a switch interface drifts from its approved configuration. The collector is stale, so the operator refreshes evidence before proposing a restore. An unsupported command must be rejected.
Illustrative evaluation scenario, not a recorded product result.What a useful result must show
Record device/firmware, protocol, credential scope, observation time, inferred edges, approval, command result and read-back. Confirm the fallback owner if rollback is unsupported.
Get the evaluation worksheet →Check the support boundaries
- Collector placement and network permissions
- Vendor, model, firmware and protocol
- Observed versus inferred topology
- Flow/telemetry freshness and retention
A protocol or vendor name is not blanket device support. Separate missing telemetry from a healthy interface; request the current collector and action matrix.
Check public evidence and availability →Scope, availability and evaluation details
Vendor, model, protocol, MIB, API, flow, and configuration actions must be verified against current provider evidence.
Discovery is bounded to authorized sites, subnets, credentials, rates, schedules, and collector policy.
The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →
Review full environment and integration scope
Credentials and actions stay controlled
Collector credentials remain Digital Vault references, while polling, remote diagnostics, configuration capture, and approved restore use bounded adapters, signed commands, provider read-back, and audit.
Collectors use purpose-bound Vault credentials and connect network state to sites, devices, alerts, tickets, configuration archives, and reports.
Questions, answered
Before you choose your next step.
Does network management require an appliance?
Network management uses a lightweight regional collector placed close to the managed network; deployment options depend on the supported environment.
Which network vendors are supported?
Provider-specific evaluation scope and evidence status appear in the integration directory. Current vendor, model, protocol, and action support must be verified for the intended release and environment.
Can it map switch ports and topology?
Target design: Discovery, CDP and LLDP neighbors, interface data, and IP relationships support dynamic topology and switch-port views.
Can technicians restore a device configuration?
Supported restores run through policy, authorization, approval where required, and post-change evidence rather than an untracked push.