Transparent cloud tiering status description
This topic describes the various statuses and their description that is associated with the health status of Cloud services running on each node in the cluster.
| Entity | Status | Description | Comments |
|---|---|---|---|
| TCT Account Status | Not configured | The Transparent cloud tiering installed, but the account is not configured or the account is deleted. | Run the mmcloudgateway account create command to create the cloud provider account. |
| Active | The cloud provider account that is configured with Transparent cloud tiering service is active. | ||
| Configured | The cloud provider account is configured with Transparent cloud tiering, but the service is down. | Run the mmcloudgateway service start command to resume the cloud gateway service. | |
| unreachable | The cloud provider end-point URL is unreachable due to either it being down or network issues. | Check the trace messages and error log for further details. Also, check the DNS settings. | |
| invalid csp endpoint URL | Might be caused by an HTTP 404 Not Found error. | Check that the cloud provider URL is valid. | |
| malformed URL | The cloud provider account URL is malformed. | Check that the cloud provider URL is valid. | |
| no route to csp | The response from the cloud provider is invalid. | Check that the cloud provider URL is accessible. | |
| connect exception | The connection was refused remotely by the cloud provider. It might be that no process is listening on the cloud provider address. | Check that the cloud provider host name and port numbers are valid. | |
| socket timeout | Timeout occurred on a socket while it was connecting to the cloud provider. | Check the trace messages and error log for further details. Also, check that the network connection is valid. | |
| invalid cloud configuration | Transparent cloud tiering refused to connect to the cloud provider because some of the cloud provider's dependent services are down. | Check that the cloud provider's dependent services are running. | |
| credentials invalid | The Transparent cloud tiering service failed to connect to the cloud provider because authentication failed. | Run the mmcloudgateway account update command to change the cloud provider's account password. | |
| mcstore node network down | The network of the Transparent cloud tiering node is down. | Check the trace messages and error logs for further details. Also, check that the network connection is valid. | |
| TCT Account Status | ssl handshake exception | The cloud account status failed due to an unknown SSL handshake error. | Check the trace messages and error logs for further details. |
| ssl handshake certificate exception | Transparent cloud tiering failed to connect to the cloud provider because of an untrusted server certificate chain. | Check the trace messages and error logs for further details. | |
| ssl handshake sock closed exception | Transparent cloud tiering failed to connect to the cloud provider because the remote host closed the connection during handshake. | Check the trace messages and error logs for further details. | |
| ssl handshake bad certificate exception | Transparent cloud tiering failed to connect to the cloud provider because of a bad certificate. | Check the trace messages and error logs for further details. | |
| ssl handshake invalid path certificate exception | Transparent cloud tiering failed to connect to the cloud provider because it was unable to find a valid certification path. | Check the trace messages and error logs for further details. | |
| ssl handshake failure exception | Transparent cloud tiering failed to connect to the cloud provider because it could not negotiate the wanted level of security. | Check the trace messages and error logs for further details. | |
| ssl handshake unknown certificate exception | Transparent cloud tiering failed to connect to the cloud provider because of an unknown certificate. | Check the trace messages and error logs for further details. | |
| ssl key exception | Transparent cloud tiering failed to connect to the cloud provider because of bad SSL key or misconfiguration. | Check the trace messages and error logs for further details. | |
| ssl peer unverified exception | Transparent cloud tiering failed to connect to the cloud provider because its identity could not be verified. | Check the trace messages and error logs for further details. | |
| ssl protocol exception | Transparent cloud tiering failed to connect to the cloud provider because of an error in the operation of the SSL protocol. | Check the trace messages and error logs for further details. | |
| ssl exception | Transparent cloud tiering failed to connect to the cloud provider because of an error the SSL subsystem. | Check the trace messages and error logs for further details. | |
| ssl no certificate exception | Transparent cloud tiering failed to connect to the cloud provider because a certificate was not available. | Check the trace messages and error logs for further details. | |
| TCT Account Status | ssl not trusted certificate exception | Transparent cloud tiering failed to connect to the cloud provider because it could not locate a trusted server certificate. | Check the trace messages and error logs for further details. |
| ssl invalid algorithm exception | Transparent cloud tiering failed to connect to the cloud provider because of invalid or inappropriate SSL algorithm parameters. | Check the trace messages and error logs for further details. | |
| ssl invalid padding exception | Transparent cloud tiering failed to connect to the cloud provider because of invalid SSL padding. | Check the trace messages and error logs for further details. | |
| ssl unrecognized message | Transparent cloud tiering failed to connect cloud provider because of an unrecognized SSL message. | Check the trace messages and error logs for further details. | |
| bad request | Transparent cloud tiering failed to connect to the cloud provider because of a request error. | Check the trace messages and error logs for further details. | |
| precondition failed | Transparent cloud tiering failed to connect to the cloud provider because of a precondition failed error. | Check the trace messages and error logs for further details. | |
| default exception | The cloud provider account is not accessible due to an unknown error. | Check the trace messages and error logs for further details. | |
| container create failed | The cloud provider container creation failed. The cloud provider account might not be authorized to create the container. | Check the trace messages and error logs for further details. Also, check the account create related issues in Transparent cloud tiering issues. | |
| time skew | The time observed on the Transparent cloud tiering service node is not in sync with the time on the target cloud provider. | Change the Transparent cloud tiering service node time stamp to be in sync with the NTP server and rerun the operation. | |
| server error | Transparent cloud tiering failed to connect to the cloud provider because of a cloud provider server error (HTTP 503) or the container size reached max storage limit. | Check the trace messages and error logs for further details. | |
| internal dir not found | Transparent cloud tiering failed because one of its internal directory is not found. | Check the trace messages and error logs for further details. | |
| db corrupted | The database of Transparent cloud tiering service is corrupted. | Check the trace messages and error logs for further details. Use the mmcloudgateway files rebuildDB command to repair it. | |
| TCT File system Status | Not configured | Transparent cloud tiering installed, but the file system is not configured or it was deleted. | Run the mmcloudgateway filesystem create command to configure the file system. |
| Configured | The Transparent cloud tiering is configured with a file system. | ||
| TCT Server Status | Stopped | The cloud gateway service is down and could not be started. | Run the mmcloudgateway service start command to start the cloud gateway service. |
| Suspended | The cloud service was suspended manually. | Run the mmcloudgateway service start command to resume the cloud gateway service. | |
| Started | The cloud gateway service is running. | ||
| Not configured | Transparent cloud tiering was either not configured or its services were never started. | Set up the Transparent cloud tiering and start the service. | |
| Security | rkm down | The remote key manager who is configured for Transparent cloud tiering is not accessible. | Check the trace messages and error logs for further details. |
| lkm down | The local key manager who is configured for Transparent cloud tiering is either not found or corrupted. | Check the trace messages and error logs for further details. | |
| Cloud Storage Access Point | ONLINE | Cloud storage access point that is configured with Transparent cloud tiering service is active. | The state when the cloud storage access point is reachable, and credentials are valid. |
| OFFLINE | The cloud storage access point URL is unreachable due to either it is down or network issues. | unreachable The cloud provider end point URL is not reachable. |
|
| OFFLINE | The reason could be because of HTTP 404 Not Found error. | invalid_csp_endpoint_url
The specified end point URL is invalid. |
|
| OFFLINE | The cloud storage access point URL is malformed. | malformed_url
The URL is malformed. |
|
| OFFLINE | The response from cloud storage access point is invalid. | no_route_to_csp There is no route to the CSP, which indicates a possible a firewall issue. |
|
| OFFLINE | The connection is refused remotely by the cloud storage access point. | connect_exception There is a connection exception when you connect. |
|
| OFFLINE | Timeout occurs on a socket while it connects to the cloud storage access point URL. | SOCKET_TIMEOUT The socket times out. |
|
| OFFLINE | Transparent cloud tiering refuses to connect to the cloud storage access point. | invalid_cloud_config There is an invalid Cloud configuration, check the cloud. |
|
| OFFLINE | The Transparent cloud tiering service fails to connect cloud storage access point because the authentication fails. | credentials_invalid The credentials that are provided during addCloud are no longer valid (including if the password is expired). |
|
| OFFLINE | The network of Transparent cloud tiering node is down. | mcstore_node_network_down The network is down on the mcstore node. |
|
| OFFLINE | The cloud storage access point status fails due to an unknown SSL handshake error. | ssl_handshake_exception There is an SSL handshake exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because of an untrusted server certificate chain. | ssl_handshake_cert_exception There is an SSL handshake certificate exception. |
|
| Cloud Storage Access Point | OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because the remote host closed connection during handshake. | ssl_handshake_sock_closed_exception There is an SSL handshake socket closed exception. |
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because of a bad certificate. | ssl_handshake_bad_cert_exception There is an SSL handshake bad certificate exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because it is unable to find a valid certification path. | ssl_handshake_invalid_path_cert _exception There is an SSL handshake invalid path certificate exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect to the cloud storage access point because it could not negotiate the desired level of security. | ssl_handshake_failure_exception There is an SSL handshake failure exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because of an unknown certificate. | ssl_handshake_unknown_cert _exception There is an SSL handshake unknown certificate exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because of a bad SSL key or misconfiguration. | ssl_key_exception There is an SSL key exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because its identity is not verified. | ssl_peer_unverified_exception There is an SSL peer unverified exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect to the cloud storage access point because of an SSL protocol operation error. | ssl_protocol_exception There is an SSL protocol exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect to the cloud storage access point because of an SSL subsystem error. | ssl_exception There is an SSL exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect to the cloud storage access point because there is no available certificate. | ssl_no_cert_exception There is an SSL not trusted certificate exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect to the cloud storage access point because the server certificate is not trusted. | ssl_not_trusted_cert_exception There is an SSL not trusted certificate exception. |
|
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because of invalid or inappropriate SSL algorithm parameters. | ssl_invalid_algo_exception There is an SSL invalid algorithm exception. |
|
| Cloud Storage Access Point | OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because of invalid SSL padding. | ssl_invalid_padding_exception There is an SSL invalid padding exception. |
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because of an unrecognized SSL message. | ssl_unrecognized_msg There is an SSL unrecognized message exception. |
|
| OFFLINE | Transparent cloud tiering fails to the connect cloud storage access point because of a request error. | bad_request This is a bad request. |
|
| OFFLINE | Transparent cloud tiering fails to connect to the cloud storage access point because of a precondition failed error. | precondition_failed The pre-condition failed. |
|
| OFFLINE | The cloud storage access point account is not accessible due to unknown error. | default Some unchecked exception is caught. |
|
| OFFLINE | The cloud provider container creation fails. | CONTAINER_CREATE_FAILED
The container creation failed. |
|
| OFFLINE | The cloud provider container creation fails because it exists. | CONTAINER_ALREADY_EXISTS The container creation failed. |
|
| OFFLINE | The cloud provider container creation fails because it exceeds the maximum limit. | BUCKET_LIMIT_EXCEEDED The container creation failed. |
|
| OFFLINE | The cloud provider container does not exist. | CONTAINER_DOES_NOT_EXIST cloud operations failed | |
| OFFLINE | The time observed on the Transparent cloud tiering service node is not in sync with the time observed on target cloud storage access point. | TIME_SKEW | |
| OFFLINE | Transparent cloud tiering fails to connect cloud storage access point because the cloud storage access point server error or container size reaches the maximum storage limit. | SERVER_ERROR | |
| OFFLINE | Transparent cloud tiering fails because one of its internal directories is not found. | The internal directory is not found: internal_dir_notfound | |
| Cloud Storage Access Point | OFFLINE | Transparent cloud tiering failed because the resource address file is not found. | The resource address file is not found: RESOURCE_ADDRESSES_FILE_NOT_FOUND |
| OFFLINE | The database of Transparent cloud tiering service is corrupted | The Transparent cloud tiering service is corrupted: db_corrupted | |
| OFFLINE | The remote key manager who is configured for Transparent cloud tiering is not accessible. | The SKLM server is not accessible. This is valid only when ISKLM is configured | |
| OFFLINE | The local key manager who is configured for Transparent cloud tiering is either not found or corrupted. | The local .jks file is either not found or corrupted. This is valid only when local key manager is configured. | |
| OFFLINE | The reason could be because of an HTTP 403 Forbidden error. | This action is forbidden. | |
| OFFLINE | Access denied due to authorization error. | Access is denied. | |
| OFFLINE | The filesystem of Transparent cloud tiering service is corrupted. | The filesystem is corrupted. | |
| OFFLINE | The directory of Transparent cloud tiering service is corrupted. | There is a directory error. | |
| OFFLINE | The key manager configured for Transparent cloud tiering is either not found or corrupted. | There is a key manager error. | |
| OFFLINE | Transparent cloud tiering failed because its container pair root directory not found. | The container pair root directory is not found. | |
| Transparent cloud tiering service is has too many retries internally. | There are too many retries. | ||
| Cloud Service | ENABLED | The cloud service is enabled for cloud operations. | The Cloud service is enabled, |
| DISABLED | The cloud service is disabled. | The Cloud service is disabled. | |
| TCT Service | STOPPED | The cloud gateway service is down and could not be started | The server is stopped abruptly, for example, JVM crash. |
| SUSPENDED | The cloud gateway service is suspended manually. | The TCT service is stopped intentionally. | |
| STARTED | The cloud gateway service is up and running. | The TCT service is started up and running. | |
| The cloud gateway check returns an unknown result. | The TCT service status is unknown value. | ||
| Attempt to restart the cloud gateway process. | The TCT service is restarted. | ||
 NOT_CONFIGURED |
The Transparent cloud
tiering was either not configured
or its service was never started. |
The TCT service is recently installed. |
|
| Container pair status |
ONLINE |
The container pair set is configured with an active Transparent cloud tiering service. |
The state when the container pair set is reachable. |
| OFFLINE | Transparent cloud tiering failed to connect to the container pair set because of a directory error. | Connection failure due to:
|
|
| Transparent cloud tiering failed to connect to the container pair set because the container does not exist. | container_does_not_exist The cloud container cannot be found but the connection to the cloud is active. |
||
| Transparent cloud tiering failed to connect to the cloud provider because of precondition failed error. | Check trace messages and error logs for further details. | ||
| Transparent cloud tiering failed to connect because resource address file is not found. | Check trace messages and error logs for further details. | ||
| Transparent cloud tiering failed to connect because one of its internal directory is not found. | Check trace messages and error logs for further details. | ||
| Transparent cloud tiering failed because one of its internal directory is not found. | Check trace messages and error logs for further details. | ||
| Transparent cloud tiering failed to connect cloud storage access point because of cloud storage access point service unavailability error. | Check trace messages and error logs for further details. | ||
| Transparent cloud tiering failed to connect cloud storage access point because of a bad certificate. | Check trace messages and error logs for further details. |