Connect & Register the Edge Appliance
This guide covers on-site work: mounting and cabling the appliance, opening SSH, and registering with monozu edge register. Pairing the device to your tenant is completed by Monozu — see Claim Code Pairing for what your administrators verify in the cloud UI.
Before you start
Section titled “Before you start”| Item | Details |
|---|---|
| Network | Outbound HTTPS to cloud.monozu.io and api.cloud.monozu.io; WireGuard UDP to your VPN Hub hostname |
| Credentials | SSH username/password or key provided with the appliance by Monozu |
| Tenant | Your organization must already exist in Monozu Cloud — Monozu pairs the claim code to your tenant |
| On-site actor | Monozu technician (typical) or your OT engineer with Monozu delivery credentials |
1. Connect and power on the appliance
Section titled “1. Connect and power on the appliance”-
Mount the appliance per Monozu delivery documentation.
-
Connect power and wait for boot (first start may take several minutes).
-
Connect network cables:
- WAN / uplink — path to internet or corporate egress.
- LAN — OT/IT VLAN for discovery or protection (one appliance per isolated segment is typical).
-
Confirm outbound access to
cloud.monozu.io,api.cloud.monozu.io, and your VPN Hub hostname (Network & Connectivity).
2. Access the device (SSH or local console)
Section titled “2. Access the device (SSH or local console)”-
Obtain the appliance IP address (DHCP reservation, label, or temporary console display).
-
Connect using credentials from your Monozu delivery packet:
Terminal window ssh <username>@<appliance-ip> -
If SSH fails, verify management VLAN access, power, and site firewall rules allowing SSH to the appliance on your network.
Local console
Section titled “Local console”Attach a display and keyboard if required. The registration command below runs the same from SSH or console.
3. Register with monozu edge register
Section titled “3. Register with monozu edge register”-
On the appliance, run:
Terminal window monozu edge register -
Complete any network setup prompts (WAN/LAN, DHCP or static IP) if shown.
-
Note the claim code displayed on the console (short code, e.g.
ABC-123). Share it with Monozu if your rollout process requires it. -
Wait while Monozu completes pairing to your tenant. The CLI finishes automatically when pairing succeeds.
-
In Monozu Cloud, your administrator opens Edge Devices and confirms status Online (Claim Code Pairing).
-
Enable optional modules (VPN, backup, security) per your License and module documentation.
4. After registration
Section titled “4. After registration”| Task | Where |
|---|---|
| Verify connectivity | Edge Devices — status Online |
| Discovery | Assets / CMDB — hosts after scan (Asset Discovery) |
| Site / zones | Assets — link discovered assets to sites and zones |
| VPN / backup / security | Cloud UI modules per license |
Troubleshooting
Section titled “Troubleshooting”| Problem | What to try |
|---|---|
| Cannot SSH | Check IP, cable, VLAN, local ACLs; use console |
monozu command not found | Contact Monozu support — image may need recovery |
| Claim code expired | Re-run monozu edge register; contact Monozu if pairing was delayed |
| Device Offline in cloud | Firewall/proxy blocking outbound HTTPS; see Network & Connectivity |
| Discovery empty | LAN on correct interface; licensed module; wait for scan interval |