> For AI agents: the complete documentation index is available at https://www.jumpserver.com/docs/llms.txt, the full documentation bundle is available at https://www.jumpserver.com/docs/llms-full.txt.

# Device Manager


Enterprise Edition

**Device Manager (JDMC)** requires JumpServer Enterprise Edition. The entry is
available only when the deployment includes JDMC and the license permits it.

[Request 14-day free trial](https://www.jumpserver.com/free-trial)

Device Manager opens **JDMC**, an independent operations console that is deployed
alongside JumpServer. JDMC manages the server that hosts JumpServer rather than
the assets protected by JumpServer: network configuration, disk expansion,
license, high availability, backups, and container lifecycle.

For operational scenarios and a capability overview, see
[Device Manager](https://www.jumpserver.com/docs/operations/device-manager.md).


Warning

JDMC operates on the host system and its containers. Changes made there affect
the whole deployment and can interrupt running sessions. Restrict access to
administrators who are authorized to manage the JumpServer server, and [back
up the deployment](https://www.jumpserver.com/docs/operations/backup-restore.md) before you change network,
disk, or high-availability settings.

## Open JDMC


1

In the right area of the top navigation bar, click .

![image](/docs/images/docs/navs/nav-settings.png)

2

In the left menu, click **Device manager**. JDMC opens in a new browser tab
and uses the current JumpServer sign-in.

3

If you open the console directly by browsing to `/jdmc/`, sign in with the
root password of the server, accept the user and privacy agreements, and click
**Log in to the console**.

The entry is shown only when JDMC is enabled in the deployment and the account
has the required permission. JDMC shares the JumpServer host name and serves
under the `/jdmc/` path, for example `https://jumpserver.example.com/jdmc/`.

![Figure 1: Device Manager entry](/images/v5/jumpserver/v5_jdmc_overview_entry.png)

![Figure 2: JDMC sign-in page](/images/v5/jumpserver/v5_jdmc_overview_login.png)

## Interface structure

| Group                  | Menu                       | What it manages                                                     |
| ---------------------- | -------------------------- | ------------------------------------------------------------------- |
| System management      | Network configuration      | Network interfaces, routes and gateways, DNS, and Docker networks.  |
| System management      | Domain configuration       | Access domain names and service certificates.                       |
| System management      | Disk management            | Data disk expansion and mount point usage.                          |
| System management      | License management         | Machine code and license upload.                                    |
| System management      | Service settings           | Root password, port exposure policy, SNMP, and system time.         |
| System management      | Primary/standby management | Two-node high availability clustering.                              |
| Application management | Data backup                | Configuration files, database, system logs, and session recordings. |
| Application management | Application status         | Start, restart, and inspect the JumpServer containers.              |
| Application management | Application configuration  | Deployment-level configuration for JumpServer.                      |
| Application management | Application logs           | Live logs from each container.                                      |

## Maintenance and high availability

New in v5.1.0
JDMC adds primary and standby management, system upgrade management, and patch
package management. Use primary and standby management to inspect and configure
a two-node high-availability cluster, system upgrade management to upgrade the
JumpServer deployment, and patch package management to manage patch packages for
the deployment.

![Figure 3: JDMC system upgrade and patch package pages.](/images/v5/jumpserver/v5_jdmc_upgrade_01.png)

### Reliability in high availability deployments

Changed in v5.1.1
In high availability deployments, stronger persistent write protection applies
to databases and Redis across container restarts, re-creation, and failure
recovery. Redeployment completion checks tolerate normal replication lag, and
switchover waits and recovery coordination are refined to reduce false failure
detection.

## Runtime environment check

Every page except the dashboard shows a runtime check result. When the check
passes, it reports **Runtime environment normal**; open the details to see each
required and optional dependency and the executable path that was found. Click
**Re-check** to run the test again after you install a missing dependency.


Note

A missing required dependency, such as `chronyc` on the system time page,
blocks only the operations that need it. Install the dependency and re-check
before you continue. JDMC actions are not available in deployments that do not
ship the console.

## Version history

| Version | Change                                                                                         |
| ------- | ---------------------------------------------------------------------------------------------- |
| v5.1.1  | Improved persistent write protection and high-availability recovery checks.                    |
| v5.1.0  | Added primary and standby management, system upgrade management, and patch package management. |