List of points to confirm (Cloud for Google Cloud)

Verify that you performed the necessary tasks by using the correct procedure as described in the document.

Verify the content of the notes and cautions described in the procedures again.

When you perform an operation from the REST API/CLI, verify that the access-destination address is correctly specified.

Specify the correct IP address or host name of the storage cluster, individual storage node, or load balancer you want to operate.

For details on specifying the address in the CLI, see the VSP One SDS Block and SDS Cloud CLI Reference.

If you use an FQDN to specify the destination when you perform an operation from the REST API/CLI, verify that the FQDN can correctly resolve to an IP address.

Verify that the DNS record is correctly set for the FQDN.

When using REST API/CLI, verify that the parameters and other options are correctly specified.

For more information, see the VSP One SDS Block and SDS Cloud REST API Reference or VSP One SDS Block and SDS Cloud CLI Reference.

When you perform an operation from the REST API/CLI, verify that the SSL/TLS communication settings are correctly specified.

For more information, see the VSP One SDS Block System Administrator Guide.

When you perform an operation from the REST API/CLI, verify that the controller node is correctly set.

See Configuring an environment for using a VSP One SDS Block CLI in the VSP One SDS Cloud for GCP Setup and Configuration to verify that the settings and status are correct.

Verify that the external servers accessed by the storage system are configured and operating normally.

The storage system works in cooperation with multiple external servers.

If the external servers are not set correctly, a failure might occur. Verify that the following external servers are configured and operating normally.

• External authentication (LDAP) server

• iSNS server

• SMTP server

• SNMP manager

• Syslog server

For information about how to verify each external server setting, see the VSP One SDS Block System Administrator Guide.

A user of the storage system might have to be registered with an external server, such as an LDAP server.

If KARS08202-E is output, verify that the NTP server is running.

Confirm the failure information about the cloud by, for example, referencing the cloud vendor's web pages, and then verify that the NTP server is running normally and the network between the storage node and NTP server is normal.

If failure information about the cloud cannot be confirmed, contact customer support of the cloud vendor for any failure information.

If a failure occurs in the cloud, wait until recovery from the failure completes.

You can use either of the following commands to verify the NTP server to which the storage node is connected.

REST API: GET /v1/objects/storage-time-setting

CLI: storage_time_setting_show

If KARS08200-E is output, verify that the DNS server is running.

Confirm the failure information about the cloud by, for example, referencing the cloud vendor's web pages, and then verify that the DNS server is running normally and the network between the storage node and DNS server is normal.

If failure information about the cloud cannot be confirmed, contact customer support of the cloud vendor for any failure information.

If a failure occurs in the cloud, wait until recovery from the failure completes.

Verify that each Compute Engine instance is operating normally.

Verify the status of the Compute Engine instance from the Google Cloud Console.

If the status of all the Compute Engine instances is Stopped, you need to start the storage system.

For details about how to start the storage system, see Starting the storage cluster (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration.

If the response to the system drive access of a storage node is delayed, the message KARS08205-W is output.

• In case of a temporary system drive access response delay, KARS08206-I is output 10 to 15 minutes after KARS08205-W is output, notifying that the system drive access response has become normal.

• If KARS08206-I is not output for more than 15 minutes after KARS08205-W is output, perform the procedure as described in Performing maintenance blocking for storage nodes (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration for the applicable storage node, and then perform the procedure as described in Performing maintenance recovery for storage nodes (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration.

  Identify the applicable storage node from the storage node ID included in KARS08205-W.

  KARS08206-I is not output if the system drive access response has become normal after performing the procedure described in Performing maintenance recovery for storage nodes (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration. Therefore, determine that the system drive access response has become normal if KARS08205-W is not output even after 15 minutes of OS startup.

  If KARS08205-W is output again after OS startup, perform Replacing storage nodes (Cloud for Google Cloud) in theVSP One SDS Block and SDS Cloud System Administration to recover the storage node.

Verify that the Google Cloud environment is running normally.

Confirm information about Google Cloud failures (for example, by accessing the Google Cloud web pages).

Verify that all services in the target regions are running normally from the Google Cloud Service Health.

If an error occurs in the Google Cloud, wait for the error to be corrected, and then restart the storage system.

For details about how to start the storage system, see Starting the storage cluster (Cloud for Google Cloud) in the VSP One SDS Block and SDS Cloud System Administration.

Verify that access to the Google Cloud Console is possible.

If you cannot access the Google Cloud Console when there is no error in the Google Cloud, check the privileges of the Google Cloud account.

If TCP retransmission increases during internode network, event log KARS08330-W is output.

Possible causes of TCP retransmission are network failure, network performance degradation, or Compute Engine instance failure of Google Cloud. Network failure, network performance degradation, and Compute Engine instance failure of Google Cloud affect storage system operation. Confirm the failure information of Google Cloud.

If failure information of Google Cloud cannot be confirmed, contact customer support of Google Cloud for any failure information.

If a failure occurs in Google Cloud, wait until recovery from the failure completes.

Verify that the account for operating Google Cloud is assigned the necessary privileges.

See the Google Cloud documentation and Google account permissions in the VSP One SDS Cloud for GCP Setup and Configuration to verify that the account has the necessary privileges to operate.

If you are using a CMEK for disk encryption, you must add rights to access Google Cloud Key Management Service.

For details, see the Google Cloud user guide.

Verify that the IAM user operating the gcloud CLI has been assigned the necessary privileges.

See the Google Cloud documentation and Google account permissions in the VSP One SDS Cloud for GCP Setup and Configuration to verify that the account has the necessary privileges to operate.

If you are using a CMEK for disk encryption, you must add rights to access Google Cloud Key Management Service.

For details, see the Google Cloud user guide.

Verify that sufficient Google Cloud resources are secured.

See the Google Cloud documentation and VSP One SDS Cloud for GCP Setup and Configuration to verify whether the resources necessary for configuring VSP One SDS Block are secured.

Verify that the storage nodes that are no longer used have been disconnected from the control network, compute network, and internode network that make up VSP One SDS Block.

If a storage node VM is no longer used after removal or replacement of a storage node or storage software uninstallation, delete the storage node VM according to instructions of each procedure.

VMs remaining on these storage nodes might cause problems. For example, the network settings remaining in the VMs might cause IP address conflicts.

Verify if the name of the Cloud Storage bucket for storing the VM configuration file contains dots (.).

If the name of the Cloud Storage bucket for storing the VM configuration file contains dots (.), change the bucket name to a name that does not include dots (.). Alternatively, use an existing bucket whose name does not contain dots (.).

For information about how to check the names of Cloud Storage buckets, see Example Cloud Storage operations in the VSP One SDS Cloud for GCP Setup and Configuration.

Verify whether the VSP One SDS Block and compute node are correctly connected when KARS03228-I is output.

If there is a blockage in a storage node within the storage cluster, follow the Cause and action taken in storage node maintenance for your cloud platform in the VSP One SDS Block System Administrator Guide to perform either the procedure Performing maintenance recovery for storage nodes or Replacing storage nodes to recover the applicable storage node.

If maintenance operations are in progress, wait until they are completed.

Perform the procedure as described in Obtaining a list of path information about compute nodes in the VSP One SDS Block System Administrator Guide to verify that paths are registered in a full mesh configuration for the compute nodes.

If the compute port is iSCSI, see ALUA configuration guidelines in the VSP One SDS Block System Administrator Guide and configure ALUA on the compute nodes.

If the compute port is NVMe/TCP, see ANA configuration guidelines in the VSP One SDS Block System Administrator Guide to configure ANA on the compute nodes.

See the respective OS vendor's document and configure the system so that all paths from the compute nodes are recognized as online.

If KARS03228-I continues to be output repeatedly after configuration, contact customer support.