Notes and restrictions

In this manual, the phrase "VSP Gx00 models, VSP Fx00 models" should be interpreted to also include the following storage system models: VSP N400, VSP N600, VSP N800.

When a user executes an asynchronous processing API function job that takes two hours or more to process, the KART30031-E error occurs and the job fails.

This problem occurs if the user executes an API function command to perform one of the following tasks and the job takes two hours or more to complete.

• Deleting a journal volume from a journal

• Formatting a volume

• Shredding a volume

• Formatting a parity group

• Deleting a parity group

• Initializing the capacity-saving function for a pool

• Shrinking a pool

• Restoring a pool

• Relocating a pool

Even though the KART30031-E error occurs, the request might have succeeded. Confirm the status of the resources.

If all of the following conditions are met, the progressRate attribute, which indicates the progress of processing, is displayed:

• The isClone attribute of the pair is set to false.

• The canCascade attribute of the pair is set to false.

• The pair status is COPY, RCPY, SMPP, or PSUP.

In the above case, the value displayed for the progressRate attribute is actually the value of the concordanceRate attribute.

A difference of several hours between the storage system's date and time and the NTP server's date and time occurs if all of the following conditions are met:

• A time zone for which daylight saving time is supported is set.

• Automatic adjustment of daylight saving time is enabled.

• You synchronize the storage system with the NTP server during the transition period from standard time to daylight saving time or the transition period from daylight saving time to standard time.

To recover from this problem, synchronize with the NTP server again after the transition period from standard time to daylight saving time or the transition period from daylight saving time to standard time.

The symptoms of this problem occur if all of the following conditions are met:

• A time zone for which daylight saving time is supported is set.

• Automatic adjustment of daylight saving time is enabled.

Symptom 1:

• An NTP server synchronization time that was set during standard time incorrectly changes to one hour earlier than the actual time when daylight saving time begins.

• An NTP server synchronization time that was set during daylight saving time incorrectly changes to one hour later than the actual time when daylight saving time ends.

To resolve this problem, reset the NTP server synchronization time by re-executing the API function to change the date and time of the storage system after daylight saving time begins or ends.

Symptom 2:

• When the date and time of the REST server is in daylight saving time and the date and time of the storage system is in standard time, a time one hour earlier than the time you request as the time of synchronization with the NTP server is set as the synchronization time for the storage system.

• When the date and time of the REST server is in standard time and the date and time of the storage system is in daylight saving time, a time one hour later than the time you request as the time of synchronization with the NTP server is set as the synchronization time for the storage system.

To resolve this problem, set the same date and time for the REST server and the NTP server, and then re-set the NTP server synchronization time by re-executing the API function to change the date and time of the storage system.

If the error occurred by using the following API, a part of the resource might be created.

• HDT pool creation

When the error occurred, check the status of the resource, delete the resource created partially, and perform the API again.

If the following conditions are met, attempts to create Thin Image pairs fail, and the KART00000-E message is output.

1. The specified snapshot group name is already being used for another snapshot group.

2. The API command to create a Thin Image pair is executed when the API command to delete a Thin Image pair is executed at the same time, and both APIs are using the same pvolLdevId attribute without svolLdevId attribute.

If this problem occurs, re-execute the API command to create a Thin Image pair.

If the maximum number of resources already exist on the storage system and you use one of the following API commands to create a new resource, the job might fail and the KART30013-E message might be output:

• Creating a host group (without specifying hostGroupNumber)
• Creating an LU path (without specifying lun)

Creating Thin Image pair API may fail with KART40188-E or KART4009-E when clonesAutomation=true or autoSplit=true is specified.

Execute cloning Thin Image pair API or storing snapshot data API after confirming if pair status of Thin Image is "PAIR".

When getting a list of external path groups in an environment where number of external path is 10000 or more, all of the information may not be obtained.

Perform the follow actions after checking the nextPageHeadPathGroupId in the external path group:

• When the value of nextPageHeadPathGroupId is other than -1, execute the getting list of external path group API with specifying the value of nextPageHeadPathGroupId by the value of the previous headPathGroupId, and obtain the list of the external path groups in the range that could not be acquired.
• When the value of nextPageHeadPathGroupId is -1, no additional action is required.

When any of the following operations is executed, affectedResources displays an incorrect URL.

• Unmapping an external volume

  DELETE base-URL/v1/objects/external-parity-groups/object-ID

• Removing an external path from an external path group

  POST base-URL/v1/objects/external-path-groups/object-ID/actions/remove-path/invoke

• Disconnecting from an external volume

  POST base-URL/v1/objects/external-parity-groups/object-ID/actions/disconnect/invoke

• Performing migration

  POST base-URL/v1/objects/local-clone-copypairs/object-ID/actions/migrate/invoke

• Performing migration for an entire copy group

  POST base-URL/v1/objects/local-clone-copygroups/object-ID/actions/migrate/invoke

To check whether the above operations were successful, execute the following APIs.

• Unmapping an external volume

  GET base-URL/v1/objects/external-path-groups

• Removing an external path from an external path group

  GET base-URL/v1/objects/external-path-groups/object-ID

• Disconnecting from an external volume

  GET base-URL/v1/objects/external-path-groups

• Performing migration ^#

  GET base-URL/v1/objects/local-clone-copypairs/object-ID

• Performing migration for an entire copy group ^#

  GET base-URL/v1/objects/local-clone-copygroups/object-ID

• #: The possible pair statuses are as follows.

  If the pair status is PSUS: Migration succeeded.

  If the pair status is PSUE: Migration failed.

Do not specify "dummydevgroup" as a device group name.

If "dummydevgroup" is specified as a device group name, API response takes much time, or error might occur with KART20022-E message.

When REST API doesn't respond for a long period, reboot the GUM that the CTL has a problem by using maintenance utility. If REST API still doesn't respond after GUM is rebooted, detailed investigation is required. Collect the normal dump and contact the support center.

If any attribute of the following object IDs contains a comma ("," or "%2c"), the KART40014-E error occurs when an API for managing copy groups or snapshot groups is executed:

• pvolDeviceGroupName
• svolDeviceGroupName
• localDeviceGroupName
• remoteDeviceGroupName
• copyGroupName
• copyPairName
• snapshotGroupId

Note that, when an object ID includes commas for combining attribute values, such commas do not cause the KART40014-E error.