Gpfs/trace/status: GET

Lists the status of all the network configuration and operations that are associated with a group of nodes.

Availability

Available on all IBM Storage Scale editions.

Description

The GET scalemgmt/v2/gpfs/trace/status request gets the status of all the network configuration and operation that are associated with a group of nodes. For more information about the fields in the data structures that are returned, see the topic mmtracectl command.

Request URL

https://<IP address or host name of API server>:<port>/scalemgmt/v2/gpfs/trace/status
where
trace/status
Specifies the resource for the GET call.

Request parameters

The following parameters can be used in the request URL to customize the request:
Table 1. List of request parameters
Parameter name Description and applicable keywords Required/optional
nodeName The node for which the network configuration details are requested. Required.

Request headers

Accept: application/json

Request data

No request data.

Response data

{
    "mmTraceCtl": [
        {
            "daemonMode": "String",
            "kernelMode": "String",
            "nodeName": "Node name",
            "status": "Node staus"        }
    ],
    "status": {
        "code": 200,
        "message": "String"
    }
}
For more information about the fields in the following data structures, see the links at the end of this topic.
"status":
Return status.
"message": "ReturnMessage",
The return message.
"code": "ReturnCode"
The return code.
mmTraceCtl
"daemonMode":Daemon status
The status of the Daemon.
"kernelMode": "Kernel status"
The status of the kernel.
"nodeName": "Node name"
Name of the node.
status: on | off
The status of the node.

Examples

The following example lists the status of the network configuration and operations.

Request data: 
curl -k -u admin:admin001 -X GET --header 'accept:application/json'
'https://198.51.100.1:443/scalemgmt/v2/gpfs/trace/status?node=node1-11'
The request URL with no field or filter parameter returns only the details that uniquely identify the object.
Response data:
Note: In the JSON data that is returned, the return code indicates whether the command is successful. The response code 200 indicates that the command successfully retrieved the information. Error code 400 represents an invalid request and 500 represents internal server error. 
{
    "mmTraceCtl": [
        {
            "daemonMode": "blocking",
            "kernelMode": "blocking",
            "nodeName": "node1-11",
            "status": "on"
        }
    ],
    "status": {
        "code": 200,
        "message": "The request finished successfully."
    }
}