Inventory & IPAM
Every node, found and detailed.
NetEnds discovers your nodes and reads what they hold. Addresses and subnets live beside the inventory — IPAM stops being a spreadsheet.
- Vendor, model and OS identified
- Interfaces, VLANs, routes, hardware
- A subnet tree built from what nodes report
Monitoring
Hear about it before your users do.
Health, capacity and routing state across every vendor, with baselines learned from your own traffic — so “abnormal” has a number behind it.
- CPU, memory, interfaces, power, optics
- Alerts from both ends of a failed link, grouped into one incident
- Streaming telemetry on supported Arista, Cisco and Aruba switches
Topology
Topology built from the network itself.
Physical, VLAN and routed maps are built from what your network reports — not from a diagram someone forgot to update.
- Site, physical, VLAN and routed views
- Multicast and MPLS included
- Detail follows collection depth
The Sites map, rendered from the product’s own code · Sample data
Configuration
Every change, before and after.
Configs are captured on a schedule and on change, versioned, and diffable line by line. A push you prepare is backed up first and waits for an approver.
- 50 versions kept by default, up to 500, any two compared
- Who changed it, read from the node’s own log
- OS upgrades proposed — a person applies them
Logs & flows
Logs and flows from every vendor. One place.
Syslog, NetFlow, IPFIX, sFlow and SNMP traps land in NetEnds. Logs and flows become searchable across every vendor at once.
- Top talkers and conversations
- Search every vendor’s logs together
- Traps received from day one