Checking the status of a remote Avaya Aura Device Services node from the CLI

Last Updated : Jun 10, 2026 |

About this task

You can run a health check for a remote Avaya Aura® Device Services node using the command line interface.

When you perform a health check, Avaya Aura® Device Services only displays the HTTP status code for the selected node as follows:

  • 200: All services on the node are active and the node is working as expected.

  • 503: One or more services on the node are not running.

Starting from Release 10.1.1.1, Avaya Aura® Device Services supports the HTTPS protocol for health checks.

Important:

If you deploy Avaya Aura® Device Services on Microsoft Azure, you must use HTTPS for heath checks to comply with the platform security policies.

If you need detailed information about the status of each service, use the svc aads status command. For more information, see Checking the Avaya Aura Device Services status from the CLI.

Before you begin

To run health checks using HTTPS, enable support for the HTTPS protocol. For more information, see Enabling or disabling HTTPS for health checks.

Procedure

  1. Log in to the Avaya Aura® Device Services CLI using an SSH connection.
  2. Do one of the following:

    • To run a health check using HTTP, run the following command:

      curl -k -v http://<NODE IP>:8457/health

    • To run a health check using HTTPS, run the following command:

      curl -k -v https://<NODE IP>:8457/health

    In these commands, <NODE IP> is the IP address of a remote node whose status you want to check.

Result

Avaya Aura® Device Services displays the current status of the remote node.

The following is an example of the command output:

[admin@msg-aads ~]$ curl -k -v http://192.0.2.136:8457/health
* About to connect() to 192.0.2.136 port 8457 (#0)
*   Trying 192.0.2.136...
* Connected to 192.0.2.136 (192.0.2.136) port 8457 (#0)
> GET /health HTTP/1.1
> User-Agent: curl/7.29.0
> Host: 192.0.2.136:8457
> Accept: */*
>
< HTTP/1.1 200
< Date: Fri, 12 Feb 2021 17:30:31 GMT
< Content-Length: 0
< Connection: keep-alive
<
* Connection #0 to host 192.0.2.136 left intact