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, and this page is available as Markdown at https://www.jumpserver.com/docs/features/system-settings/infrastructure/device-manager.md.
🎉 JumpServer v5.1.1 is available. See what's new →
  • v5

    • 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

    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.

    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 before you change network, disk, or high-availability settings.

    Open JDMC

    1

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

    image
    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

    Figure 2: JDMC sign-in page

    Interface structure

    GroupMenuWhat it manages
    System managementNetwork configurationNetwork interfaces, routes and gateways, DNS, and Docker networks.
    Domain configurationAccess domain names and service certificates.
    Disk managementData disk expansion and mount point usage.
    License managementMachine code and license upload.
    Service settingsRoot password, port exposure policy, SNMP, and system time.
    Primary/standby managementTwo-node high availability clustering.
    Application managementData backupConfiguration files, database, system logs, and session recordings.
    Application statusStart, restart, and inspect the JumpServer containers.
    Application configurationDeployment-level configuration for JumpServer.
    Application logsLive 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.

    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

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