Getting configuration information (including additional information) from the SVP
About getting additional information from the SVP
You can get this information from the following storage systems:
- VSP 5000 series
The following figure shows an implementation in which configuration information, including additional information, is obtained from the storage system cache on the SVP.
API requests for getting information from the SVP
-
The following API requests can get configuration information, including additional information:
- Summary information about storage systems
- Channel board information
-
The following API requests can get configuration information, including additional information, by specifying a query parameter:
- Information about parity groups
API: Getting information about parity groups
Query parameter: detailInfoType=class
- Information about external parity groups
API: Getting information about external parity groups
Query parameter: detailInfoType=class
- Information about drives
API: Getting a list of drive information
Query parameter: detailInfoType=class
- Information about volumes
API: Getting volume information
Query parameter: detailInfoType=class
API: Getting information about virtual LDEVs
Query parameter: detailInfoType=class
- Information about ports
API: Getting information about a specific port
Query parameter: detailInfoType=class
- Information about pools
Query parameter: detailInfoType=class
- Information about remote copy groups
API: Getting information about a specific remote copy group
Query parameter: detailInfoType=class
API: Getting information about a specific remote copy group
Query parameter: detailInfoType=class
- Information about hardware installed on a storage system#
API: Getting information about the hardware installed in a storage system
Query parameter: componentOption=class
- Information about parity groups
-
The following API requests can get information about copy pairs:
- Getting information about all of ShadowImage pairs
- Getting information about all of Thin Image pairs
- Getting information about all of remote copy pairs (TrueCopy/Universal Replicator)
- Getting information about all of remote copy pairs (global-active device)
-
The following API requests can add and get detailed information about copy pairs, by specifying a query parameter:
- Getting a list of copy groups (ShadowImage)
API: Getting a list of copy groups
Query parameter: detailInfoType=pair
- Getting information about Thin Image pairs in units of snapshot groups
API: Getting information about Thin Image pairs in units of snapshot groups
Query parameter: detailInfoType=pair
- Getting a list of remote copy groups (TrueCopy/Universal Replicator)
API: Getting a list of remote copy groups
Query parameter: detailInfoType=pair
- Getting a list of remote copy groups (global-active device)
API: Getting a list of remote copy groups
Query parameter: detailInfoType=pair
- Getting a list of copy groups (Volume Migration)
API: Getting a list of copy groups (Volume Migration)
Query parameter: detailInfoType=pair
- Getting a list of copy groups (ShadowImage)
#: For the information about the hardware installed in the storage system, only additional information is obtained from the storage system cache.
It usually takes from one to five minutes (but can take as long as an hour) before the latest information is applied to the cache. To obtain the latest information, run the API request that updates the cache of storage system configuration information to refresh the cache data, and then run the API request for getting information.
Updating the cache of storage system configuration information
The procedure for obtaining information about resources after performing operations such as changing the configuration of resources is as follows.
- Run the API request that changes the configuration of resources described in the explanation about API requests for getting information from the SVP.
- Run the API request that updates the cache of storage system configuration information.
It takes about 10 seconds or longer to update the cache information. Depending on the storage system usage status, it might take as long as 20 minutes to receive a response for this API request. Also, if multiple operations for changing the configuration are running concurrently, it might take a long time to receive a response for this API request.
We recommend that you lock the target resources before running this API request.
NoteThis API request might fail depending on the number of configuration change operations and the number of resources such as LDEVs. If such a failure occurs, the HTTP status code 503 will be returned. In such a case, wait a while, and then run the request again.
- Run the API request that obtains information about the resources whose configuration has been changed.
Storage Administrator (View)
POST base-URL/v1/services/storage-cache-service/actions/refresh/invoke
Object ID
None.
Query parameters
None.
Body
None.
Body
None.
None.
For details on the status codes of the request for this operation, see the description of HTTP status codes.
curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session d7b673af189048468c5af9bcf3bbbb6f" -X POST https://192.0.2.100/ConfigurationManager/v1/services/storage-cache-service/actions/refresh/invoke -d ""