The network, as documented and as observed
Walk from site to building, floor, room, rack and device. Compare what is documented with what discovery observed, and approve the differences before anything changes.
Nine topology lenses
Physical, L2, L3, Management, Transport, Overlay, Services, Platforms and Storage, each as Documented, Observed or Drift.
Changes need a reviewer
Drift becomes proposals. Approved proposals become one change that updates records and raises work orders for physical work.
Know the blast radius
See what goes with a failed tray, PDU, rack, room, duct or cable, down to links, services and customers.
From setup to answer in four steps
Install a collector
Outbound-only, shipped as a container or an OVA, enrolled with a rotatable key.
Run discovery
Use SNMP v2c or v3, SSH CLI, NETCONF or gNMI. Address sweeps are off by default and rate-limited.
Reconcile
Devices are matched by serial and then hostname. Drift shows missing, unexpected and wrong links and changed devices.
Approve
A reviewer approves proposals before records change.
What you can do
A collector you can audit
Each collector reports healthy, degraded or silent, and the customer can audit everything a collector did. Discovery runs offer Run now, a success and failure chart, per-device failures and collector health.
What if this fails?
A What if this fails? button on devices, links and ducts runs a failure scenario with rerouting. Blast radius flags diversity breaches along the way.
Data quality you can score
Data quality scores each site by domain and lists the gaps behind each score. The patching diagram on rack and room records shows every panel and device port, with connections grouped into trunks.
Works with the rest of the platform
Cabling and connectivity
Patch by dragging between ports, let NetCosm route cables along your trays and work out the length, then trace any circuit end to end.
Read moreIPAM, DNS and DHCP
See aggregates and prefixes as one tree with a utilisation bar on every row, then drill down to the address, the interface and the DNS name.
Read moreSecurity events (SIEM)
Logs arrive at your own endpoint and are matched to the device, asset or site they name. Router events are tied to the exact interface and link.
Read moreFrequently asked questions
How does discovery reach our network?
Through an outbound-only collector (container or OVA) using SNMP, SSH, NETCONF or gNMI, or from IP Fabric.
Will discovery overwrite our records?
No. Differences become proposals that a reviewer approves before anything changes.
Can we see what a failure would take down?
Blast radius shows the links, services and customers behind a tray, PDU, rack, room or cable.
What views are there?
Nine topology lenses from physical to services, each as documented, observed or drift.
Can we check what the collector did on our network?
Yes. The collector activity screen is a full audit.
NetCosm is hosted in the United Kingdom, so your rack, power and network records stay in the UK.
See it on your own floor
Book a demo and we will walk through it with your rooms, racks and addresses in mind.