How can we help?
-
zWAN
-
-
-
-
-
-
- Articles coming soon
-
-
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
- Articles coming soon
-
- IPsec Tunnel not Establishing
- SSL-VPN Tunnel not Establishing
- Mobile Network Issues
- Management Tunnel does not Establish
- DNS not Resolving from Local Network Appliance
- DNS Resolution Issues in Tunnel Configuration
- DHCP Server not Leasing IP to LAN PC
- Debugging EC Events - Unknown Status Issue
- Trusted-MAC Geofencing Issues
- DNS Issues from DC LAN PC
- Troubleshooting LAN Connectivity to Internet via WAN, Remote Branch LAN, or Local Branch LAN
- NetBalancer gateways displaying Faulty/Inactive
- Packet Drop Issues
-
-
zTC
-
StorTrends
-
zAccess
-
zGuardian
You are here:
Print
Integrating zDM Server
0 out Of 5 Stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |
Integrating zDM Server
Summary
The zDM Device Management Server mediates communications between zMAN Director and zTC endpoints using the OMA LwM2M (CoAP) protocol. It receives management commands from zMAN and forwards them to registered thin clients, and relays device telemetry back to zMAN :contentReference[oaicite:2]{index=2}.
Prerequisites
- zMAN Director deployed (standalone or multi-node)
- zDM Server installed per the zDM Server Setup Guide
- Network connectivity: UDP port 5683 accessible between zMAN and zDM
Procedure
- In the zMAN Director UI, navigate to **Server Configuration → zDM Management**. Pending zDM servers (identified by their IP) will appear under the **Pending zDM** list :contentReference[oaicite:3]{index=3}.
- Click the **Onboard** icon next to the desired entry. The server moves to the **Registered zDM** list, indicating successful integration :contentReference[oaicite:4]{index=4}.
- To remove an entry, click the **Delete** (trash) icon. Deleted zDM servers must re-register from the zDM side to reappear in Pending :contentReference[oaicite:5]{index=5}.
Troubleshooting
- If no Pending entries appear, verify that the zDM Server’s Management Portal URL and Access Key match zMAN’s API Access Key (found under **Server Configuration → API Access Key**) and that the zDM service is running :contentReference[oaicite:6]{index=6}.
- After regenerating the API Access Key, all registered zDM servers go offline. Re-onboard each server by clicking **Onboard** again under Pending entries :contentReference[oaicite:7]{index=7}.
Was this article helpful?
0 out Of 5 Stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |
5
Table of Contents