Supported devices
Your fleet, platform by platform.
18 platforms are discovered over their own API or CLI. Anything else that answers SNMP v2c or v3 joins the same inventory.
Discover
Finds the node, reads what it is and what it holds.
18 platforms over their own API or CLI
Monitor
Health, utilization and protocol state, with alerting.
Every row in the table
Back up
Pulls the running config on a schedule, versions and diffs it.
18 platforms backed up
The matrix
One table. Every platform.
Each row is a platform, or the SNMP baseline that covers any other node. Each badge says how it is discovered, monitored and backed up.
| Platform | Discover | Monitor | Back up |
|---|---|---|---|
| Arista EOS | Yes | Yes | Yes |
| Cisco NX-OS (Nexus) | Yes | Yes | Yes |
| Cisco IOS / IOS-XE | Yes | Yes | Yes |
| Cisco ASA | Yes | Yes | Yes |
| Juniper Junos | Yes | Yes | Yes |
| Aruba AOS-CX | Yes | Yes | Yes |
| Extreme EXOS | Yes | Yes | Yes |
| Fortinet FortiGate (FortiOS) | Yes | Yes | Yes |
| Palo Alto PAN-OS | Yes | Yes | Yes |
| Check Point Gaia | Yes | Yes | No |
| SonicWall SonicOS | Yes | Yes | No |
| F5 BIG-IP | Yes | Yes | No |
| Citrix NetScaler (ADC) | Yes | Yes | No |
| Nokia SR Linux | Yes | Yes | Yes |
| Huawei VRP | Yes | Yes | Yes |
| HPE / H3C Comware | Yes | Yes | Yes |
| Dell SmartFabric OS10 | SNMP | Yes | Yes |
| SONiC | Yes | Yes | Yes |
| MikroTik RouterOS | SNMP | Yes | Yes |
| VyOS | SNMP | Yes | Yes |
| OpenWrt | SNMP | Yes | Yes |
| OPNsense / pfSense | Yes | Yes | Yes |
| Ubiquiti UniFi (controller-managed) | Controller | Controller | No |
| FortiAP (FortiGate-managed) | Controller | Controller | No |
| Any other SNMP-reachable device | SNMP | SNMP | No |
- Yes
- A path built for that platform, over its own API or CLI.
- SNMP
- The standard SNMP baseline, the same one that covers any node answering SNMP.
- Controller
- Read through the controller that manages the node.
- No
- Not available for that platform. The product says so on the node’s page, with the reason.
Writing changes
Read everywhere. Write carefully.
Reading is broad: discovery, monitoring and backup, scored platform by platform above. Pushing configuration and upgrading an OS are a narrower, gated surface, on fewer platforms.
- Config push
- A push you draft shows the commands it will send and waits for approval before it runs. Where the platform is backed up, a backup is taken before the push by default and again after it, so the change is on record as a diff.
- Protection list
- Put a node on your Protection list, or a whole site, group or environment, and config push, rollback, restore, Autopilot, the console and OS upgrades all refuse it. Monitoring carries on as usual.
- OS upgrades
- Staged and proposed; an operator applies them. Each upgrade is checked before it runs and compared afterwards with the node’s state from before it.
- Autopilot
- Off until you switch it on. It then drafts the config that turns on traps, syslog, flow export and management APIs for your review, and applies changes itself only if you choose. More on Autopilot.
Wireless
Through the controller.
Onboard a UniFi controller and the access points, switches and gateways it manages come with it. A FortiGate that runs your WiFi brings its FortiAPs the same way. Each one is linked back to its controller.
Configuration for these devices lives on the controller, so their rows read No under Back up. The FortiGate itself is backed up. Wireless clients and SSIDs behind any other controller, cloud-managed ones included, are not read.
- UniFi controllers, and FortiGates acting as WiFi controllers
- Access points, radios, clients and SSIDs
- Client signal, channel, band and roam events
- New devices wait for your confirmation before they join the fleet
Don’t see your gear?
Tell us what you run and you’ll get a straight answer. Or run the trial on your own network and see what NetEnds finds.