Retrieve the ping results from a target

POST api/v2/jobs/rvc '{"method":"cluster.ping","hostnames":["<node_hostname>"]}'

Starts a SC//Reliant™ Virtual Controller (RVC) job which pings a target and reports the results. The available targets are a node, node group, or saved filter. The response will indicate that the RVC job is created and is scheduled to run. You can use the job ID from the response to retrieve the job status.

In the job payload, the result for each node contains the hostname of the other node in the cluster pair, the url of its RVC server, and the roundtrip_time_ms of the ping in milliseconds.

In order to perform this action, the following conditions must be met:

Must have the Remote Job Execution feature turned on at the site level.
The user must have the following capabilities:
- Create and Update a RVC job
- Call Cluster read-only methods

Request syntax

post api/v2/jobs/rvc '{"method":"cluster.ping","hostnames":["<node_hostname>"]}'

Request parameters

The request accepts the following data in JSON format.

Parameter	Type	Description	Required
`method`	String	The RVC action to start. This value is specified as a combination of the RVC module and method. For example, to retrieve the ping results from a target you would specify the `cluster` module and the `ping` method combined as `cluster.ping`.	Yes
`hostnames`	String array	The list of node hostnames on which to run the RVC job.	Dependent. Only if no node group or saved filter is provided.
`node_group_name`	String	The name of the node group on which to run the RVC job. The RVC job will run on all nodes that are members of the node group.	Dependent. Only if no hostnames or saved filter is provided.
`node_group_id`	Integer	The ID of the node group on which to run the RVC job. The RVC job will run on all nodes that are members of the node group.	Dependent. Only if no hostnames or saved filter is provided.
`saved_filter_name`	String	The name of the saved filter on which to run the RVC job. The RVC job will run on all nodes that match the saved filter.	Dependent. Only if no hostnames or node group is provided.
`saved_filter_id`	Integer	The ID of the saved filter on which to run the RVC job. The RVC job will run on all nodes that match the saved filter.	Dependent. Only if no hostnames or node group is provided.

Response syntax

When the hostnames request parameter is used, the following response syntax is received.

{
    "id": integer,
    "type": "RVC3",
    "status": "string",
    "message": "string",
    "trigged_by": "string",
    "parameters": {
        "method": "cluster.ping",
        "hostnames": [
            "string",
            "string"
        ]
    },
    "time_started": "timestamp"
}

When the node group or saved filter request parameters are used, the following response syntax is received.

{
    "id": integer,
    "type": "RVC3",
    "status": "string",
    "message": "string",
    "trigged_by": "string",
    "parameters": {
        "method": "cluster.ping",
        "node_group_name": "string",
        "node_group_id": integer,
        "saved_filter_name": "string",
        "saved_filter_id": integer
    },
    "time_started": "timestamp"
}

Response parameters

If the action is successful, an HTTP 200 response is returned. The following data is returned in JSON format.

Field	Type	Description
`id`	Integer	The ID of the RVC job.
`type`	String	The type of RVC job. For RVC jobs, it is `RVC3`.
`status`	String	The status of the job.
`message`	String	This field is reserved for internal use.
`trigged_by`	String	The username of the person who initiated the job.
`parameters`	String	The request parameters indicating the hostnames, node groups, or saved filters the RVC job ran on.
`time_started`	Timestamp	The timestamp indicating when the job started. The timestamp is given in ISO 8601 UTC datetime format.

Errors

For a list of potential errors, refer to the common errors, as this action does not have any unique error responses. For more information, see Common errors.

Examples

Example 1: Start an RVC job requesting the ping results for a list of node hostnames.

This example starts an RVC job which pings a node with hostname sit0001red0 and reports the results back.

ruby api.rb <customer_code> POST api/v2/jobs/rvc '{"method":"cluster.ping","hostnames":["sit0001red0"]}'

Response

{
  "id": 1596603,
  "type": "RVC3",
  "status": "pending",
  "message": null,
  "trigged_by": "test.user",
  "parameters": {
    "method": "cluster.ping",
    "hostnames": [
      "sit0001red0"
    ]
  },
  "time_started": "2025-04-07T19:51:03Z"
}

Example 2: Start an RVC job requesting the ping results for a node group.

This example starts an RVC job requesting the ping results for the nodes in node group Test Node Group.

ruby api.rb <customer_code> POST api/v2/jobs/rvc '{"method":"cluster.ping","node_group_name":"Test Node Group"}'

Response

{
  "id": 1596606,
  "type": "RVC3",
  "status": "pending",
  "message": null,
  "trigged_by": "test.user",
  "parameters": {
    "method": "cluster.ping",
    "node_group_name": "Test Node Group"
  },
  "time_started": "2025-04-07T19:55:06Z"
}

Example 3: Retrieving the payload from an RVC job.

This example retrieves the payload from an RVC job ID which displays the payload of the cluster.ping method.

ruby api.rb <customer_code> GET api/jobs/1598647\?include_payload=true

Response

{
  "id": 1598647,
  "type": "RVC3",
  "status": "finished",
  "message": null,
  "trigged_by": "test.user",
  "success_nodes_count": 1,
  "failed_nodes_count": 0,
  "total_nodes_count": 1,
  "parameters": {
    "method": "cluster.ping",
    "params": {},
    "hostnames": [
      "sit0001red0"
    ],
    "update_rpm": true
  },
  "time_started": "2026-10-12T17:38:05Z",
  "time_finished": "2026-10-12T17:38:05Z",
  "payload": {
    "sit0001red0": [
      {
        "result": {
          "url": "tcp://172.16.16.2:3232",
          "hostname": "sit0001red1",
          "roundtrip_time_ms": 29
        },
        "timestamp": 1791826686
      }
    ]
  }
}