Vlun Removal Example; Http Request; Http Response; Querying Vluns - HP 3PAR StoreServ 7200 2-node Manual

Table 71 VLUN Removal Error Codes
API Error
INV_INPUT
NON_EXISTENT_HOST
NON_EXISTENT_VLUN
INV_INPUT_PORT_SPECIFICATION
INV_INPUT_EXCEEDS_RANGE
INV_INPUT_MISSING_REQUIRED
NON_EXISTENT_VLUN

VLUN Removal Example

In the following example, the VLUN for volume test_vv02 with LUN 252, which is exported to
mysystem through port 2:5:2, is deleted. The optional port information is also sent because the
VLUN is of matched type.

HTTP Request

DELETE /api/v1/vluns/test_vv02,252,mysystem,2:2:4 HTTP/1.1
Host: storsys1.example.com:8080
Accept: application/json
Content-Type: application/json
X-HP3PAR-WSAPI-SessionKey: 2-33fe8891e288b34b3f914410e7cc7907-a93d1c50

HTTP Response

HTTP/1.1 200 OK
Date: Mon, 16 Apr 2012 07:16:39 GMT
Server: hp3par-wsapi
Cache-Control: no-cache
Pragma: no-cache
Connection: close

Querying VLUNs

The VLUN query collects information about all the VLUN templates and active VLUNs on the system.

Querying All VLUNs

To query for VLUN information, use the HTTP GET method in the URI. The syntax is as follows:
https://<storage system>:8080/api/v1/vluns

All-VLUNs Query Success

A successful query returns the HTTP status code 200 OK and a response body with members as
shown in Table 72 (page
HTTP Code
400 Bad Request
404 Not Found
404 Not Found
400 Bad Request
400 Bad Request
400 Bad Request
404 Not Found
74).
Description
Incomplete VLUN information.
Invalid URL percent encoding.
(Since WSAPI 1.2)
Specified hostname not found.
Incorrect LUN or volumeName
Specified port is invalid.
The LUN specified exceeds expected range.
Incomplete VLUN info.
Missing volumeName or lun, or both hostname and
port.
Incorrect LUN or volumeName
Querying VLUNs 73