Managing Network Devices

Keep the on-site network behind a plant under control from your browser: discover every switch, router, logger and meter on the local subnet, watch their reachability, and store the credentials you need to reach them — without travelling to the site. This guide walks through the day-to-day tasks on the plant's Networking page. For how discovery, classification and health-checking actually work, see the Local Network Inspector feature page.

Before You Start

The network behind a plant is only reachable once its secure tunnel is up, so two things must already be in place:

The plant has a working VPN connection to its on-site router (set up in the VPN step of onboarding).
You hold a technical job role on the plant — Technical Manager or higher, which includes Operator. Viewing, scanning and editing devices all require it. A Viewer sees no Networking actions, and a cooperating organization needs the same role on the shared plant.

Open in Mirox

Open the plant's Networking section directly. Inside, the Network Devices tab holds the device list and every action below; the Overview tab shows the same devices as a health "rose" you can filter and click into.

Running a Discovery Scan

Discovery sweeps the plant's subnets, finds live hosts, fingerprints them, and adds anything new to the device list.

Open the plant's Networking section and switch to the Network Devices tab.
Press Discover. The button is available only when the on-site agent is reachable — if the agent is offline, it stays disabled.
Watch the progress bar. The scan runs through clear, named steps — pinging hosts, identifying responders, probing SNMP, analyzing port fingerprints, detecting web interfaces, verifying results, and saving — and shows a running "found so far" count.
When it finishes, the bar shows when the last scan completed, how long it took, and how many devices are tracked. New and updated devices appear in the table automatically.

Scans Run on Their Own

You rarely need to press Discover by hand. The platform schedules discovery automatically on a cadence sized to the network — smaller plants more often, larger ones less so — so the inventory stays current. Use the manual button when you have just changed something on site and want an immediate refresh.

Aborting a Scan

If a scan is taking too long or you triggered it by mistake, press Abort scan while it is running. The agent finishes the checks already in flight and winds down; any devices it had already identified are kept. The status bar marks the cycle as aborted so you know the run did not complete a full sweep.

Reading Device Status

Each device carries a clear state you can read at a glance:

Online — the device is responding to its checks.
Offline — the device is not responding.
Unknown — the platform has not yet confirmed a state (for example, right after discovery).

Click any device — a row in the table or a slice in the Overview rose — to open its detail panel. There you see its address, vendor, type, and a chart of ping latency and packet loss over your chosen time window (toggle 1h / 24h / 30d at the top of the page). A degrading latency trend is your early warning that a link is about to fail.

Spotting Trouble Fast

On the Overview tab, sort and filter the rose by name, address, type or status to surface offline devices immediately. The list itself is searchable and sortable, and on plants with more than one subnet you can filter the table to a single subnet.

A device whose address falls outside every configured VPN route is flagged out of range — usually a sign a network route was removed or the device was misconfigured. Resolve it by correcting the device or the plant's VPN routes.

Adding a Device Manually

Some equipment never answers a scan but still needs tracking. Add it by hand:

On the Network Devices tab, press Add Device.
Enter the device IP address. It must fall within one of the plant's configured VPN routes — the dialog lists the allowed subnets and blocks an address outside them.
Optionally give it a name (for example, "Park Router").
Press Add Device. You can configure SNMP, credentials and checks afterward by editing it.

Classifying and Editing a Device

Discovery fills in what it can, but you can correct or complete any device's record. Open a device and choose Edit device (or use the actions menu on its table row). The editor is organized into tabs:

General — set a display name and description, toggle whether the device is monitored, and fill in the device type (router, switch, inverter, energy meter, data logger, camera, and more), MAC address, model, serial number and firmware. Fields auto-populate from discovery where possible; anything you fill in gives your team a single source of truth.
Connection Checks — see below.
SNMP — see below.
Authentication — the credential vault, see below.
Proxy — expose the device's web interface through the Proxy.
Notes — free-text notes for your team.
Delete — remove the device (only shown if you can delete).

Configuring Connection Checks

Each device has its own monitoring profile on the Connection Checks tab, so you decide exactly how it is probed:

ICMP Ping is always on — the baseline reachability probe for every device.
Polling interval sets how often the device is checked; leave it empty to use the plant-wide default.
TCP Port Check confirms specific services are listening (for example, ports 22,80,443).
HTTP Health Check polls a web endpoint and counts any non-success response as a failure.

To stop watching a device entirely without deleting it, turn off Monitoring Enabled on the General tab — the device stays in the list but is no longer polled or alerted on.

Re-checking a Single Device

There is no separate "re-check" button — the agent re-probes each monitored device on its polling interval, so lowering the interval on the Connection Checks tab makes a flaky device report its state sooner. For a full re-sweep of the whole subnet, run a discovery scan.

Using SNMP Monitoring

For SNMP-capable equipment, SNMP collects far richer readings than a ping — interface counters, CPU, memory and hardware details. Configure it on a device's SNMP tab:

Choose the SNMP version: v2c (community string) or v3 (user-based with auth and privacy).
For v2c, enter the community string. For v3, enter the username and pick the auth protocol (MD5/SHA family) and privacy protocol (DES/AES family) with their passwords.
Press Save. Leave any credential field empty to keep the existing value unchanged.

The tab shows whether SNMP is currently Active, which version is in use, and whether credentials are stored. Once configured, SNMP readings feed into the device's richer fingerprint and metrics.

Storing Device Credentials (Credential Vault)

The Authentication tab is an encrypted credential store for each device — username, password and a free-text note describing what the credentials unlock (HTTP basic auth, SSH, an API token, and so on). Use it like a password manager for your technical team, so a device's login is stored once and reachable by whoever needs it later, including through the Proxy.

Open the device and go to the Authentication tab.
Enter the username, password and a short scheme / note. The password is masked by default — use the eye icon to reveal it, and the copy buttons to lift either value to your clipboard.
Press Save.

Credentials Are Tightly Gated

Stored device credentials are never shown in the device list. Only Operator and Technical Manager roles on the plant can view or edit them; everyone else sees a notice to ask an authorized teammate. This is deliberately stricter than the rest of the device record.

Local Network Inspector — how device discovery, classification and health-checking work behind the scenes
Using the Proxy — open a discovered device's web interface in your browser using stored credentials
Configuring Data Loggers — map the loggers discovered on the network so the platform starts collecting plant data
Using the VPN — reach the plant's local network yourself with a personal VPN profile
VPN — the secure tunnel that lets the platform reach the plant's local network