Transparent cloud tiering events
The following table lists the events that are created for the Transparent cloud tiering component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| tct_account_active | STATE_CHANGE | INFO | no | Message: Cloud provider account, which is configured with Transparent Cloud Tiering service, is active. |
| Description: Cloud provider account, which is configured with Transparent Cloud Tiering service, is active. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| tct_account_bad_req | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of a bad request error. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of a bad request error. | ||||
| Cause: A bad request is encountered. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_certinvalidpath | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because it was unable to find a valid certification path. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because it was unable to find a valid certification path. | ||||
| Cause: Unable to find a valid certificate path. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_configerror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering refuses to connect to the cloud provider. |
| Description: Transparent Cloud Tiering refuses to connect to the cloud provider. | ||||
| Cause: Some of the cloud provider-dependent services are down. | ||||
| User Action: Check whether the cloud provider-dependent services are up and running. | ||||
| tct_account_configured | STATE_CHANGE | WARNING | no | Message: Cloud provider account is configured with Transparent Cloud Tiering, but the service is down. |
| Description: Cloud provider account is configured with Transparent Cloud Tiering, but the service is down. | ||||
| Cause: The Transparent Cloud Tiering service is down. | ||||
| User Action: Run the mmcloudgateway service start command to resume the cloud gateway service. | ||||
| tct_account_connecterror | STATE_CHANGE | ERROR | no | Message: An error occurred while attempting to connect a socket to cloud provider URL. |
| Description: The connection was refused remotely by cloud provider. | ||||
| Cause: No process is listening on the cloud provider address. | ||||
| User Action: Check whether the cloud provider hostname and port numbers are valid. | ||||
| tct_account_containecreatererror | STATE_CHANGE | ERROR | no | Message: The cloud provider container creation failed. |
| Description: The cloud provider container creation failed. | ||||
| Cause: The cloud provider account might not be authorized to create a container. | ||||
| User Action: For more information, check the trace messages and error logs. Also, check whether the account creates issues. For more information, see the 'Transparent Cloud Tiering issues' section in the Problem Determination Guide. | ||||
| tct_account_dbcorrupt | STATE_CHANGE | ERROR | no | Message: The database of Transparent Cloud Tiering service is corrupted. |
| Description: The database of Transparent Cloud Tiering service is corrupted. | ||||
| Cause: Database is corrupted. | ||||
| User Action: For more information, check the trace messages and error logs. Use the mmcloudgateway files rebuildDB command to repair it. | ||||
| tct_account_direrror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering failed because one of its internal directories is not found. |
| Description: Transparent Cloud Tiering failed because one of its internal directories is not found. | ||||
| Cause: Transparent Cloud Tiering service internal directory is missing. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_invalidcredentials | STATE_CHANGE | ERROR | no | Message: The cloud provider account credentials are invalid. |
| Description: The Transparent Cloud Tiering service failed to connect to cloud provider because the authentication failed. | ||||
| Cause: Cloud provider account credentials that are either changed or expired. | ||||
| User Action: Run the mmcloudgateway account update command to change the cloud provider account password. | ||||
| tct_account_invalidurl | STATE_CHANGE | ERROR | no | Message: Cloud provider account URL is invalid. |
| Description: The reason can be because of 'HTTP 404 Not Found' error. | ||||
| Cause: The reason can be because of 'HTTP 404 Not Found' error. | ||||
| User Action: Check whether the cloud provider URL is valid. | ||||
| tct_account_lkm_down | STATE_CHANGE | ERROR | no | Message: The local key manager, which is configured for Transparent Cloud Tiering is not found or corrupted. |
| Description: The local key manager, which is configured for Transparent Cloud Tiering is not found or corrupted. | ||||
| Cause: Local key manager is not found or corrupted. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_malformedurl | STATE_CHANGE | ERROR | no | Message: Cloud provider account URL is malformed. |
| Description: Cloud provider account URL is malformed. | ||||
| Cause: The cloud provider URL is malformed. | ||||
| User Action: Check whether the cloud provider URL is valid. | ||||
| tct_account_manyretries | INFO | WARNING | no | Message: Transparent Cloud Tiering service faced too many internal retries. |
| Description: Transparent Cloud Tiering service faced too many internal retries. | ||||
| Cause: The Transparent Cloud Tiering service faced connectivity issues with the cloud provider. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_network_down | STATE_CHANGE | ERROR | no | Message: The network connection to the Transparent Cloud Tiering node is down. |
| Description: The network connection to the Transparent Cloud Tiering node is down. | ||||
| Cause: A network connection problem was encountered. | ||||
| User Action: For more information, check the trace messages and error logs. Also, check whether the network connection is valid. | ||||
| tct_account_noroute | STATE_CHANGE | ERROR | no | Message: The response from cloud provider is invalid. |
| Description: The response from cloud provider is invalid. | ||||
| Cause: The cloud provider URL returns a response code as '-1'. | ||||
| User Action: Check whether the cloud provider URL is accessible. | ||||
| tct_account_notconfigured | STATE_CHANGE | WARNING | no | Message: Transparent Cloud Tiering is not configured with the cloud provider account. |
| Description: The Transparent Cloud Tiering is not configured with the cloud provider account. | ||||
| Cause: The Transparent Cloud Tiering installed, but account is not configured or account is deleted. | ||||
| User Action: Run the mmcloudgateway account create command to create the cloud provider account. | ||||
| tct_account_preconderror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of a precondition failed error. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of a precondition failed error. | ||||
| Cause: Cloud provider URL returned an 'HTTP 412 Precondition Failed' error message. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_rkm_down | STATE_CHANGE | ERROR | no | Message: The remote key manager, which is configured for Transparent Cloud Tiering, is inaccessible. |
| Description: The remote key manager, which is configured for Transparent Cloud Tiering, is inaccessible. | ||||
| Cause: The Transparent Cloud Tiering fails to connect to the IBM Security Key Lifecycle Manager. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_servererror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of a cloud provider service encounters an unavailability error. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of a cloud provider server error or when the container size reached the maximum storage limit. | ||||
| Cause: Cloud provider returns an 'HTTP 503 Server' error message. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sockettimeout | STATE_CHANGE | ERROR | no | Message: Timeout occurred on a socket while connecting to the cloud provider. |
| Description: Timeout occurred on a socket while connecting to the cloud provider. | ||||
| Cause: A network connection problem was encountered. | ||||
| User Action: For more information, check the trace messages and error log. Also, check whether the network connection is valid. | ||||
| tct_account_sslbadcert | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of a bad SSL certificate. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of a bad SSL certificate. | ||||
| Cause: A bad SSL certificate is found. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslcerterror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering failed to connect to the cloud provider because of an untrusted server certificate chain. |
| Description: Transparent Cloud Tiering failed to connect to the cloud provider because of an untrusted server certificate chain. | ||||
| Cause: An untrusted server certificate chain error was encountered. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslerror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of an error, which is found in the SSL subsystem. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of an error, which is found in the SSL subsystem. | ||||
| Cause: An error is found in the SSL subsystem. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslhandshakeerror | STATE_CHANGE | ERROR | no | Message: The cloud account status failed due to an unknown SSL handshake error. |
| Description: The cloud account status failed due to an unknown SSL handshake error. | ||||
| Cause: TCT and cloud provider cannot negotiate the desired level of security. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslhandshakefailed | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because they cannot negotiate the desired level of security. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because they cannot negotiate the desired level of security. | ||||
| Cause: Transparent Cloud Tiering and cloud provider server cannot negotiate the desired level of security. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslinvalidalgo | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering failed to connect to the cloud provider because of invalid SSL algorithm parameters. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of invalid or inappropriate SSL algorithm parameters. | ||||
| Cause: Invalid or inappropriate SSL algorithm parameters are found. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslinvalidpadding | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering failed to connect to the cloud provider because of invalid SSL padding. |
| Description: Transparent Cloud Tiering failed to connect to the cloud provider because of invalid SSL padding. | ||||
| Cause: Invalid SSL padding is found. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslkeyerror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of a bad SSL key or misconfiguration. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of a bad SSL key or misconfiguration. | ||||
| Cause: A bad SSL key or misconfiguration is found. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslnocert | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because no certificate is available. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because no certificate is available. | ||||
| Cause: No certificate is available. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslnottrustedcert | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of an untrusted SSL server certificate. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of an untrusted SSL server certificate. | ||||
| Cause: The cloud provider server SSL certificate is untrusted. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslpeererror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because its identity cannot be verified. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because its identity cannot be verified. | ||||
| Cause: Cloud provider identity cannot be verified. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslprotocolerror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because an error is found during the SSL protocol operation. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because an error is found during the SSL protocol operation. | ||||
| Cause: An SSL protocol implementation error is found. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslscoketclosed | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because a remote host closed the connection during a handshake. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because a remote host closed the connection during a handshake. | ||||
| Cause: Remote host had closed the connection during a handshake. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslunknowncert | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of an unknown SSL certificate. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of an unknown SSL certificate. | ||||
| Cause: An unknown SSL certificate is found. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_sslunrecognizedmsg | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud provider because of an unrecognized SSL message. |
| Description: Transparent Cloud Tiering fails to connect to the cloud provider because of an unrecognized SSL message. | ||||
| Cause: An unrecognized SSL message is found. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_timeskewerror | STATE_CHANGE | ERROR | no | Message: The time, which is observed on the Transparent Cloud Tiering service node, is not in sync with the time on the target cloud provider. |
| Description: The time, which is observed on the Transparent Cloud Tiering service node, is not in sync with the time on the target cloud provider. | ||||
| Cause: Transparent Cloud Tiering service node current timestamp is not in sync with the target cloud provider. | ||||
| User Action: Change the Transparent Cloud Tiering service node timestamp to be in sync with NTP server, and rerun the operation. | ||||
| tct_account_unknownerror | STATE_CHANGE | ERROR | no | Message: The cloud provider account is inaccessible due to an unknown error. |
| Description: The cloud provider account is inaccessible due to an unknown error. | ||||
| Cause: An unknown runtime exception is found. | ||||
| User Action: For more information, check the trace messages and error logs. | ||||
| tct_account_unreachable | STATE_CHANGE | ERROR | no | Message: Cloud provider account URL is unreachable. |
| Description: The cloud provider end-point URL is unreachable because either it is down or has network issues. | ||||
| Cause: The cloud provider URL is unreachable. | ||||
| User Action: For more information, check trace messages, error log, and DNS settings. | ||||
| tct_container_alreadyexists | STATE_CHANGE | ERROR | no | Message: The cloud provider container creation failed as it already exists. CSAP/Container pair set: {id}. |
| Description: The cloud provider container creation failed as it already exists. | ||||
| Cause: The cloud provider container already exists. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_container_creatererror | STATE_CHANGE | ERROR | no | Message: The cloud provider container creation failed. CSAP/Container pair set: {id}. |
| Description: The cloud provider container creation failed. | ||||
| Cause: The cloud provider account might not be authorized to create a container. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_container_limitexceeded | STATE_CHANGE | ERROR | no | Message: The cloud provider container creation failed as it exceeded the maximum limit. CSAP/Container pair set: {id}. |
| Description: The cloud provider container creation failed as it exceeded the maximum limit. | ||||
| Cause: The cloud provider containers exceeded the maximum limit. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_container_notexists | STATE_CHANGE | ERROR | no | Message: The cloud provider container does not exist. CSAP/Container pair set: {id}. |
| Description: The cloud provider container does not exist. | ||||
| Cause: The cloud provider container does not exist. | ||||
| User Action: Check the cloud provider to verify whether the container exists. | ||||
| tct_cs_disabled | STATE_CHANGE | INFO | no | Message: Cloud service {id} is disabled. |
| Description: Cloud service is disabled. | ||||
| Cause: A Cloud service is disabled by the administrator. | ||||
| User Action: N/A | ||||
| tct_cs_enabled | STATE_CHANGE | INFO | no | Message: Cloud service {id} is enabled. |
| Description: Cloud service is enabled for cloud operations. | ||||
| Cause: A Cloud service is enabled by the administrator. | ||||
| User Action: N/A | ||||
| tct_cs_found | INFO_ADD_ENTITY | INFO | no | Message: Cloud service {0} is found. |
| Description: A new cloud service is found. | ||||
| Cause: A new cloud service is listed by the mmcloudgateway service status command. | ||||
| User Action: N/A | ||||
| tct_cs_vanished | INFO_DELETE_ENTITY | INFO | no | Message: Cloud service {0} is unavailable. |
| Description: One of the cloud services cannot be detected anymore. | ||||
| Cause: One of the previously monitored cloud services is not listed by the mmcloudgateway service status command anymore, possibly because Transparent Cloud Tiering service is in the suspended state. | ||||
| User Action: N/A | ||||
| tct_csap_access_denied | STATE_CHANGE | ERROR | no | Message: Cloud storage access point failed due to an authorization error. CSAP/Container pair set: {id}. |
| Description: Access is denied due to an authorization error. | ||||
| Cause: Access is denied due to an authorization error. | ||||
| User Action: Check the authorization configurations on the cloud provider. | ||||
| tct_csap_bad_req | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of a bad request error. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of a bad request error. | ||||
| Cause: Bad request is encountered. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_base_found | INFO_ADD_ENTITY | INFO | no | Message: CSAP {0} was found. |
| Description: A new CSAP was found. | ||||
| Cause: A new CSAP is listed by the mmcloudgateway service status command. | ||||
| User Action: N/A | ||||
| tct_csap_base_removed | INFO_DELETE_ENTITY | INFO | no | Message: CSAP {0} was deleted or converted to a CSAP or container pair. |
| Description: A CSAP was deleted. | ||||
| Cause: One of the previously monitored CSAPs is not listed by the mmcloudgateway service status command anymore. | ||||
| User Action: N/A | ||||
| tct_csap_certinvalidpath | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering failed to connect cloud storage access point because it could not find a valid certification path. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering failed to connect cloud storage access point because it could not find a valid certification path. | ||||
| Cause: Unable to find a valid certificate path. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_configerror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering refused to connect to the cloud storage access point. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering refused to connect to the cloud storage access point. | ||||
| Cause: Some of the cloud provider-dependent services are down. | ||||
| User Action: Check whether the cloud provider-dependent services are up and running. | ||||
| tct_csap_connecterror | STATE_CHANGE | ERROR | no | Message: An error occurred while attempting to connect a socket to the cloud storage access point URL. CSAP/Container pair set: {id}. |
| Description: The connection was refused remotely by the cloud storage access point. | ||||
| Cause: No process is listening to the cloud storage access point address. | ||||
| User Action: Check whether the cloud storage access point hostname and port numbers are valid. | ||||
| tct_csap_dbcorrupt | STATE_CHANGE | ERROR | no | Message: The database of Transparent Cloud Tiering service is corrupted. CSAP/Container pair set: {id}. |
| Description: The database of Transparent Cloud Tiering service is corrupted. | ||||
| Cause: Database is corrupted. | ||||
| User Action: Run the mmcloudgateway files rebuildDB command to rebuild the database. | ||||
| tct_csap_forbidden | STATE_CHANGE | ERROR | no | Message: Cloud storage access point failed with an authorization error. CSAP/Container pair set: {id}. |
| Description: The 'HTTP 403 Forbidden' error message is encountered. | ||||
| Cause: The 'HTTP 403 Forbidden' error message is encountered. | ||||
| User Action: Check the authorization configurations on the cloud provider. | ||||
| tct_csap_found | INFO_ADD_ENTITY | INFO | no | Message: CSAP or container pair {0} was found. |
| Description: A new CSAP or container pair was found. | ||||
| Cause: A new CSAP or container pair is listed by the mmcloudgateway service status command. | ||||
| User Action: N/A | ||||
| tct_csap_invalidcredentials | STATE_CHANGE | ERROR | no | Message: The cloud storage access point account {0} credentials are invalid. CSAP/Container pair set: {id}. |
| Description: The Transparent Cloud Tiering service fails to connect to the cloud storage access point because the authentication failed. | ||||
| Cause: Cloud storage access point account credentials are either changed or expired. | ||||
| User Action: Run the mmcloudgateway account update command to change the cloud provider account password. | ||||
| tct_csap_invalidurl | STATE_CHANGE | ERROR | no | Message: Cloud storage access point URL is invalid. CSAP/Container pair set: {id}. |
| Description: An 'HTTP 404 Not Found' error message is encountered. | ||||
| Cause: An 'HTTP 404 Not Found' error message is encountered. | ||||
| User Action: Check whether the cloud provider URL is valid. | ||||
| tct_csap_lkm_down | STATE_CHANGE | ERROR | no | Message: The local key manager, which is configured for Transparent Cloud Tiering, is not found or corrupted. CSAP/Container pair set: {id}. |
| Description: The local key manager, which is configured for Transparent Cloud Tiering, is not found or corrupted. | ||||
| Cause: Local key manager is not found or corrupted. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_malformedurl | STATE_CHANGE | ERROR | no | Message: Cloud storage access point URL is malformed. CSAP/Container pair set: {id}. |
| Description: Cloud storage access point URL is malformed. | ||||
| Cause: The cloud provider URL is malformed. | ||||
| User Action: Check whether the cloud provider URL is valid. | ||||
| tct_csap_noroute | STATE_CHANGE | ERROR | no | Message: The response from cloud storage access point is invalid. CSAP/Container pair set: {id}. |
| Description: The response from cloud storage access point is invalid. | ||||
| Cause: The cloud storage access point URL returns a response code '-1'. | ||||
| User Action: Check whether the cloud storage access point URL is accessible. | ||||
| tct_csap_online | STATE_CHANGE | INFO | no | Message: Cloud storage access point, which is configured with Transparent Cloud Tiering service, is active. CSAP/Container pair set: {id}. |
| Description: Cloud storage access point, which is configured with Transparent Cloud Tiering service, is active. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| tct_csap_preconderror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of a precondition failed error. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of a precondition failed error. | ||||
| Cause: Cloud storage access point URL returns an 'HTTP 412 Precondition Failed' error message. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_removed | INFO_DELETE_ENTITY | INFO | no | Message: CSAP or container pair {0} is unavailable. |
| Description: A CSAP or container pair cannot be detected anymore. | ||||
| Cause: One of the previously monitored CSAPs or container pair is not listed by the mmcloudgateway service status command anymore, possibly because Transparent Cloud Tiering service is in the suspended state. | ||||
| User Action: N/A | ||||
| tct_csap_rkm_down | STATE_CHANGE | ERROR | no | Message: The remote key manager, which is configured for Transparent Cloud Tiering, is inaccessible. CSAP/Container pair set: {id}. |
| Description: The remote key manager, which is configured for Transparent Cloud Tiering, is inaccessible. | ||||
| Cause: The Transparent Cloud Tiering failed to connect to the IBM Security Key Lifecycle Manager. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_servererror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of cloud storage access point service encounters an unavailability error. CSAP/Container pair set:{id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of cloud storage access point server error or container size reached the maximum storage limit. | ||||
| Cause: Cloud storage access point returned an 'HTTP 503 Server' error message. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sockettimeout | STATE_CHANGE | ERROR | no | Message: Timeout occurred on a socket while connecting to the cloud storage access point URL. CSAP/Container pair set: {id}. |
| Description: Timeout occurred on a socket while connecting to the cloud storage access point URL. | ||||
| Cause: A network connection problem is encountered. | ||||
| User Action: For more information, check the trace messages and error log. Also, check whether the network connection is valid. | ||||
| tct_csap_sslbadcert | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of a bad SSL certificate. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of a bad SSL certificate. | ||||
| Cause: A bad SSL certificate is encountered. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslcerterror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an untrusted server certificate chain. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an untrusted server certificate chain. | ||||
| Cause: An untrusted server certificate chain error is encountered. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslerror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an error that is found in the SSL subsystem. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an error that is found in the SSL subsystem. | ||||
| Cause: An error is found in the SSL subsystem. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslhandshakeerror | STATE_CHANGE | ERROR | no | Message: The cloud storage access point status failed due to an unknown SSL handshake error. CSAP/Container pair set: {id}. |
| Description: The cloud storage access point status failed due to an unknown SSL handshake error. | ||||
| Cause: Transparent Cloud Tiering and cloud storage access point cannot negotiate the desired level of security. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslhandshakefailed | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because they cannot negotiate the desired level of security. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because they cannot negotiate the desired level of security. | ||||
| Cause: Transparent Cloud Tiering and cloud storage access point cannot negotiate the desired level of security. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslinvalidalgo | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of invalid SSL algorithm parameters. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of invalid or inappropriate SSL algorithm parameters. | ||||
| Cause: Invalid or inappropriate SSL algorithm parameters are found. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslinvalidpadding | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of invalid SSL padding. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of invalid SSL padding. | ||||
| Cause: Invalid SSL padding is found. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslkeyerror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of a bad SSL key or misconfiguration. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of a bad SSL key or misconfiguration. | ||||
| Cause: A bad SSL key or misconfiguration is encountered. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslnocert | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because no certificate is available. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because no certificate is available. | ||||
| Cause: No certificate is available. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslnottrustedcert | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an untrusted server certificate. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an untrusted SSL server certificate. | ||||
| Cause: The cloud storage access point server SSL certificate is untrusted. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslpeererror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because its identity cannot be verified. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because its identity cannot be verified. | ||||
| Cause: Cloud provider identity cannot be verified. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslprotocolerror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an error that is found in the SSL protocol operation. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an error that is found in the SSL protocol operation. | ||||
| Cause: An SSL protocol implementation error is found. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslscoketclosed | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because the remote host closed the connection during a handshake. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because the remote host closed the connection during a handshake. | ||||
| Cause: Remote host closed the connection during a handshake. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslunknowncert | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an unknown SSL certificate. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an unknown SSL certificate. | ||||
| Cause: An unknown SSL certificate is found. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_sslunrecognizedmsg | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an unrecognized SSL message. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering fails to connect to the cloud storage access point because of an unrecognized SSL message. | ||||
| Cause: An unrecognized SSL message is found. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_timeskewerror | STATE_CHANGE | ERROR | no | Message: The time, which is observed on the Transparent Cloud Tiering service node, is not in sync with the time on target cloud storage access point. CSAP/Container pair set: {id}. |
| Description: The time, which is observed on the Transparent Cloud Tiering service node, is not in sync with the time on target cloud storage access point. | ||||
| Cause: Transparent Cloud Tiering service node current timestamp is not in sync with the target cloud storage access point. | ||||
| User Action: Change Transparent Cloud Tiering service node timestamp to be in sync with NTP server and rerun the operation. | ||||
| tct_csap_toomanyretries | INFO | WARNING | no | Message: Transparent Cloud Tiering service experienced too many internal retries. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering service experienced too many internal retries. | ||||
| Cause: The Transparent Cloud Tiering service might experience connectivity issues with the cloud service provider. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_unknownerror | STATE_CHANGE | ERROR | no | Message: The cloud storage access point account is inaccessible due to an unknown error. CSAP/Container pair set: {id}. |
| Description: The cloud storage access point account is inaccessible due to an unknown error. | ||||
| Cause: An unknown runtime exception is found. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_csap_unreachable | STATE_CHANGE | ERROR | no | Message: Cloud storage access point URL is unreachable. CSAP/Container pair set: {id}. |
| Description: The cloud storage access point URL is unreachable because it is down or due to network issues. | ||||
| Cause: The cloud storage access point URL is unreachable. | ||||
| User Action: For more information, check the trace messages, error logs, and DNS settings. | ||||
| tct_dir_corrupted | STATE_CHANGE | ERROR | no | Message: The directory of Transparent Cloud Tiering service is corrupted. CSAP/Container pair set: {id}. |
| Description: The directory of Transparent Cloud Tiering service is corrupted. | ||||
| Cause: Directory is corrupted. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_fs_configured | STATE_CHANGE | INFO | no | Message: The Transparent Cloud Tiering is configured with the file system. |
| Description: The Transparent Cloud Tiering is configured with the file system. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| tct_fs_corrupted | STATE_CHANGE | ERROR | no | Message: The file system {0} of Transparent Cloud Tiering service is corrupted. CSAP/Container pair set: {id}. |
| Description: The file system of Transparent Cloud Tiering service is corrupted. | ||||
| Cause: File system is corrupted. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_fs_notconfigured | STATE_CHANGE | WARNING | no | Message: The Transparent Cloud Tiering is not configured with the file system. |
| Description: The Transparent Cloud Tiering is not configured with the file system. | ||||
| Cause: The Transparent Cloud Tiering is installed, but the file system is not configured or deleted. | ||||
| User Action: Run the mmcloudgateway filesystem create command to configure the file system. | ||||
| tct_fs_running_out_space | INFO | WARNING | no | Message: Available disk space is {0}. |
| Description: File system, where Transparent Cloud Tiering got installed, is running out of space. | ||||
| Cause: File system, where Transparent Cloud Tiering got installed, is running out of space. | ||||
| User Action: Free up disk space on the file system where Transparent Cloud Tiering is installed. | ||||
| tct_internal_direrror | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering failed because one of its internal directories is not found. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering failed because one of its internal directories is not found. | ||||
| Cause: Transparent Cloud Tiering service internal directory is missing. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_km_error | STATE_CHANGE | ERROR | no | Message: The key manager, which is configured for Transparent Cloud Tiering, is not found or corrupted. CSAP/Container pair set: {id}. |
| Description: The key manager, which is configured for Transparent Cloud Tiering, is not found or corrupted. | ||||
| Cause: Key manager is not found or corrupted. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_network_interface_down | STATE_CHANGE | ERROR | no | Message: The network of Transparent Cloud Tiering node is down. CSAP/Container pair set: {id}. |
| Description: The network of Transparent Cloud Tiering node is down. | ||||
| Cause: A network connection problem is encountered. | ||||
| User Action: For more information, check the trace messages and error log. Also, check whether the network connection is valid. | ||||
| tct_only_ensure | STATE_CHANGE | INFO | no | Message: Transparent Cloud Tiering container is available on cloud, but does not guarantee that migrate operations would work. Container pair set: {id}. |
| Description: Transparent Cloud Tiering container is available on cloud, but does not guarantee that migrate operations would work. | ||||
| Cause: Transparent Cloud Tiering container is available on cloud, but does not guarantee that migrate operations would work. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_resourcefile_notfound | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering failed because resource address file is not found. CSAP/Container pair set: {id}. |
| Description: Transparent Cloud Tiering failed because resource address file is not found. | ||||
| Cause: Transparent Cloud Tiering failed because resource address file is not found. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_rootdir_notfound | STATE_CHANGE | ERROR | no | Message: Transparent Cloud Tiering failed because its container pair root directory is not found. Container pair set: {id}. |
| Description: Transparent Cloud Tiering failed because its container pair root directory is not found. | ||||
| Cause: Transparent Cloud Tiering failed because its container pair root directory is not found. | ||||
| User Action: For more information, check the trace messages and error log. | ||||
| tct_service_down | STATE_CHANGE | ERROR | no | Message: Cloud gateway service is down. |
| Description: The cloud gateway service is down and cannot be started. | ||||
| Cause: The mmcloudgateway service status command returned that the cloud gateway service is stopped. | ||||
| User Action: Run the mmcloudgateway service start command to start the cloud gateway service. | ||||
| tct_service_notconfigured | STATE_CHANGE | WARNING | no | Message: Transparent Cloud Tiering is not configured. |
| Description: The Transparent Cloud Tiering is not configured or its service is not started. | ||||
| Cause: The Transparent Cloud Tiering is not configured or its service is not started. | ||||
| User Action: Set up the Transparent Cloud Tiering and start its service. | ||||
| tct_service_restart | INFO | WARNING | no | Message: The cloud gateway service failed. Trying to recover. |
| Description: Attempt to restart the cloud gateway process. | ||||
| Cause: A problem with the cloud gateway process is detected. | ||||
| User Action: N/A | ||||
| tct_service_suspended | STATE_CHANGE | WARNING | no | Message: Cloud gateway service is suspended. |
| Description: The cloud gateway service is manually suspended. | ||||
| Cause: The mmcloudgateway service status command returns suspended. | ||||
| User Action: Run the mmcloudgateway service start command to resume the cloud gateway service. | ||||
| tct_service_up | STATE_CHANGE | INFO | no | Message: Cloud gateway service is up and running. |
| Description: The cloud gateway service is up and running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| tct_service_warn | INFO | WARNING | no | Message: The cloud gateway monitoring returned an unknown result. |
| Description: The cloud gateway check returned an unknown result. | ||||
| Cause: N/A | ||||
| User Action: Perform troubleshooting. For more information, see the Problem Determination Guide. |