Network Devices
Network Devices manages the network equipment deployed across your sites: the routers, access points, and gateways that carry plant traffic. It covers inventory, remote configuration, topology, and geographic location.
This is the management counterpart to Device Monitor. Device Monitor watches any SNMP-reachable device and tells you its health. Network Devices takes configuration to the network equipment it manages.
What you get
The view opens as a set of tabs.
Devices
A live inventory: name, MAC address, IP, operating system, and model. Each device carries two independent status fields, and it's worth keeping them apart:
| Field | Values | What it tells you |
|---|---|---|
| Config status | applied, modified, error | Whether the device is running the configuration you intended |
| Monitoring status | ok, problem, critical, unknown | Whether the device is healthy right now |
A device can be perfectly healthy and still show modified, meaning someone
changed its config locally and it has drifted from the template. That is the case
worth catching early, because it survives reboots and disappears silently the
next time a template is pushed over it.
Filter and search by name, MAC, IP, or either status field. Opening a device shows its templates, connections, location, and notes.
Topology
A visual graph of how devices connect. Links are drawn solid when up and dashed red when down, and each carries its link cost, so you can see routing preference rather than inferring it.
Monitoring
Aggregate health across all devices in scope, with a time-range selector covering 1, 3, 7, 30, and 365 days, plus a breakdown by monitoring status.
Alerts
Critical and problem devices, priority-sorted, refreshing continuously. Each row links straight to the device.
Map
Devices plotted geographically. Useful when "which site is this?" is the actual question, which at multi-site scale it usually is.
Configuration by template
Devices are configured from templates, which are reusable definitions covering things like VPN settings and SSH keys. You attach a template to a device and push it, rather than editing devices individually.
This is why config status matters more than it first appears: the template is the
source of truth, and modified means a device has stopped matching it.
Organizations
Each EmberNet tenant maps to one organization here, and that mapping is what scopes the view. Tenant users see their organization and no other.
| Role | Scope | What they can do |
|---|---|---|
| Global Command | All tenants | Full management: push configs, execute commands, reboot devices, activate and deactivate, manage organizations |
| Admin | Own organization | View everything, push configuration to their own devices |
| Engineer | Own organization | View everything, read-only |
| Operator | None | Not visible |
Remote command execution, including reboots and password changes, is restricted to platform staff.
Next steps
- Device Monitor: health monitoring for any SNMP device
- ArcNet: the tunnels managed devices connect over
- Multi-Tenancy: how tenants map to organizations