transparent cloud tiering status description

Run the mmcloudgateway account create command to create a cloud provider account.

N/A

Run the mmcloudgateway service start command to resume the cloud gateway service.

Ensure that the cloud provider is online. Check whether the network is reachable between the cloud provider and transparent cloud tiering. Also, check the DNS settings.

For more information, check the trace messages and error log.

Check whether the configured cloud provider URL is valid.

Check whether the following conditions are met:

• Cloud provider URL is valid.
• Cloud provider URL has a proper legal protocol, such as HTTP or HTTPS.
• Cloud provider URL has space or any special characters that cannot be parsed.

Check whether the following conditions are met:

• DNS and firewall settings are configured.
• Network is reachable between transparent cloud tiering and the cloud provider.

Check whether the following conditions are met:

• Network is reachable between transparent cloud tiering and the cloud provider.
• Cloud provider URL is valid.
• Cloud provider receives connections.

Check whether network is reachable between transparent cloud tiering and the cloud provider.

Check whether the cloud object store is configured correctly.

For a Swift cloud provider, check whether both Keystone and Swift provider configuration are proper. Also, check whether Swift is reachable over Keystone.

Check whether the access key and secret key are valid. Also, check whether the username and password are correct.

Check whether the network interface on the transparent cloud tiering node is proper and is able to communicate with public and private networks.

Check whether the following conditions are met:

• Cloud provider supports secured communication and is properly configured with certificate chain.
• The provided cloud provider URL is secure (HTTPS).
• A secure connection to cloud provider is established by running the openssl s_client -connect <cloud provider ipaddress>: <secured_port> command on a transparent cloud tiering node.

Check whether the following conditions are met:

• The server certificate is not expired, still valid, and the DER is properly encoded.
• A self-signed or internal CA signed certificate is added to Transparent cloud tiering truststore. Use –server-cert-path option to add a self-signed certificate.
• The server certificate is valid by using the openssl x509 -in <server_cert> -text -noout command. Check the Validity section and ensure that the certificate is not expired and still valid.

Check whether the following conditions are met:

• A secure network connection is established and that secure port is reachable.
• A secured connection is established to the cloud provider by running the openssl s_client -connect <cloud_provider_ipaddress>: <secured_port> command on the Transparent cloud tiering node.

Ensure that a self-signed or internal CA-signed certificate is properly added to the Transparent cloud tiering truststore. Use the –server-cert-path option to add a self-signed certificate.

Check whether the following conditions are met:

• A proper self-signed or internal CA-signed certificate is added to the Transparent cloud tiering truststore. Use the –server-cert-path option to add a self-signed certificate.
• A client (Transparent cloud tiering ) and server (cloud provider) certificate are signed with same certificate authority or configured with same self-signed certificate.
• Proper cloud provider certificates are returned when a load balancer or firewall is present.
• A valid certificate chain is returned from the cloud provider by running the openssl s_client -connect <cloud_provider_ipaddress>: <secured_port> command on the Transparent cloud tiering node.

Ensure that the cloud provider supports TLSv1.2 protocol and TLSv1.2 enabled cipher suites.

Ensure that a proper self-signed or internal CA-signed certificate is added to the Transparent cloud tiering truststore. Use the –server-cert-path option to add a self-signed certificate.

Check whether the following conditions are met:

• The SSL configuration on cloud provider is proper.
• The Transparent cloud tiering truststore, /var/MCStore/.mcstore.jceks, is not corrupted. If the /var/MCStore/.mcstore.jceks is corrupted, then remove it and restart the server. This action replaces the /var/MCStore/.mcstore.jceks from the CCR file.

Check whether the following conditions are met:

• The cloud provider has a valid SSL configuration in place.
• The cloud provider supports TLSv1.2 protocol and TLSv1.2 enabled cipher suites.
• A secure connection is in place to the cloud provider by using the openssl s_client -connect <cloud_provider_ipaddress>: <secured_port> command on the Transparent cloud tiering node.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs. Also, check whether the account creates problems in Transparent cloud tiering issues.

Change the transparent cloud tiering service node timestamp to be in sync with the NTP server and rerun the operation.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs. Run the mmcloudgateway files rebuildDB command to repair when any issues are found.

Run the mmcloudgateway filesystem create command to configure the file system.

Run the mmcloudgateway service start command to start the cloud gateway service.

Run the mmcloudgateway service start command to resume the cloud gateway service.

Set up the transparent cloud tiering and start the service.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

The state when the cloud storage access point is reachable, and credentials are valid.

unreachable

The cloud provider end-point URL is unreachable.

invalid_csp_endpoint_url

The specified end-point URL is invalid.

malformed_url

The URL is malformed.

There is no route to the CSP, which indicates a possible firewall issue.

There is a connection exception when you connect.

The socket times out.

There is an invalid cloud configuration, check the cloud.

The credentials that are provided during addCloud are no longer valid (including if the password is expired).

The network is down on the mcstore node.

There is an SSL handshake exception.

There is an SSL handshake certificate exception.

There is an SSL handshake socket closed exception.

There is an SSL handshake bad certificate exception.

There is an SSL handshake invalid path certificate exception.

There is an SSL handshake failure exception.

There is an SSL handshake unknown certificate exception.

There is an SSL key exception.

Check whether the following conditions are met:

• The transparent cloud tiering has a valid SSL configuration in place.
• The cloud provider supports TLSv1.2 protocol and TLSv1.2 enabled cipher suites.
• A secured connection to the cloud provider is in place by using the openssl s_client -connect <cloud_provider_ipaddress>: <secured_port> command on the transparent cloud tiering node.

Ensure that the Cloud Provider SSL configuration supports TLSv1.2 protocol.

Check whether a secured connection to the cloud provider is in place by using the openssl s_client -connect <cloud_provider_ipaddress>: <secured_port> command on the transparent cloud tiering.

For more information, check error log and traces to find further cause and take necessary actions, as this is generic error.

Check whether the following conditions are met:

• A self-signed or internal root CA certificate is properly added to the transparent cloud tiering truststore.
• Add a self-signed certificate or internal root CA certificate by using the –server-cert-path option.

Check whether the JRE security file (java.security) is installed under /opt/ibm/MCStore/jre/lib/security got updated to an unsupported SSL algorithm or invalid key length.

Make sure that server SSL configuration uses TLSv11.2 enabled cipher suites.

Check whether the cloud provider is responding to requests through other available tools and make sure that the resource is accessible.

Retry the operation once the server is able to serve the requests.

Some unchecked exception is caught.

The container creation failed.

The container creation failed.

The container creation failed.

The cloud operations failed.

The resource address file is not found and shows the RESOURCE_ADDRESSES_FILE_NOT_FOUND message.

The transparent cloud tiering service is corrupted and shows the db_corrupted message.

The SKLM server is not accessible. This condition is valid only when ISKLM is configured.

The local .jks file is not found or corrupted. This action is valid only when local key manager is configured.

The action is forbidden.

Access is denied.

The file system is corrupted.

There is a directory error.

There is a key manager error.

The container pair root directory is not found.

There are too many retries.

The Cloud service is enabled.

The Cloud service is disabled.

The server is stopped abruptly, for example, JVM crash.

The TCT service is stopped intentionally.

The TCT service is started up and running.

The TCT service status has an unknown value.

The TCT service is restarted.

The TCT service is recently installed.

The state when the container pair set is reachable.

Connection failure due to directory_error or TCT directory error.

container_does_not_exist

The cloud container cannot be found but the cloud connection is active.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.

For more information, check trace messages and error logs.