HP 3PAR StoreServ 7200 2-node HP 3PAR Web Service API 1.2 Developer's - Page 46

Volume Modification Success, Table 34 Message Body JSON Objects for Volume Modification Request

Get HP 3PAR StoreServ 7200 2-node PDF manuals and user guides View all HP 3PAR StoreServ 7200 2-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 46 highlights

Table 34 Message Body JSON Objects for Volume Modification Request (continued) Member JSON Type API Type Ignored Values Description (Since WSAPI 1.2) rmUsrSpcAllocLimit Boolean None If true, remove User Space allocation limit. If False, and limit value is 0, then ignore. If False, and limit value is positive, then set. (Since WSAPI 1.2) The volume policies object is described in Table 29 (page 40). The policies object may be set to the staleSS, oneHost, or zeroDetect policies. Volume Modification Success Upon a successful request to modify a VV, the HTTP code 200 OK is returned. The location portion of the response header will contain the new URI for updated VV: /api/v1/volumes/ Volume Modification Errors Possible error codes following a VV modification request are shown in Table 35 (page 46). For generic API error codes, see Table 5 (page 17). Table 35 Volume Modification Request Error Codes API Error INV_INPUT_WARN_GT_LIMIT HTTP Code 400 Bad Request Description Allocation warning level is higher than the limit. (Since WSAPI 1.2) INV_INPUT_USR_ALRT_NON_TPVV INV_INPUT_RETAIN_GT_EXPIRE INV_INPUT_VV_POLICY 400 Bad Request 400 Bad Request 400 Bad Request User space allocation alerts are valid only with a TPVV. Retention time is greater than expiration time. Invalid policy specification (for example, caching or system is set to true). (Since WSAPI 1.2) INV_INPUT_EXCEEDS_LENGTH 400 Bad Request Invalid input: string length exceeds limit. (Since WSAPI 1.2) INV_INPUT_TIME INV_OPERATION_VV_MODIFY_USR_CPG_TPVV 400 Bad Request 403 Forbidden Invalid time specified. usr_cpg cannot be modified on a TPVV. (Since WSAPI 1.2) UNLICENSED_FEATURE 400 Bad Request Retention time cannot be modified on a system 46 Working with Storage Volumes

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
Table 34 Message Body JSON Objects for Volume Modification Request
(continued)
Description
Ignored Values
API Type
JSON Type
Member
(Since WSAPI 1.2)
If true, remove User
Space allocation limit.
None
Boolean
rmUsrSpcAllocLimit
If False, and limit
value is 0, then
ignore.
If False, and limit
value is positive, then
set.
(Since WSAPI 1.2)
The volume
policies
object is described in
Table 29 (page 40)
. The
policies
object may be
set to the
staleSS
,
oneHost
, or
zeroDetect
policies.
Volume Modification Success
Upon a successful request to modify a VV, the HTTP code
200 OK
is returned. The location portion
of the response header will contain the new URI for updated VV:
/api/v1/volumes/<volume name>
Volume Modification Errors
Possible error codes following a VV modification request are shown in
Table 35 (page 46)
. For
generic API error codes, see
Table 5 (page 17)
.
Table 35 Volume Modification Request Error Codes
Description
HTTP Code
API Error
Allocation warning level
is higher than the limit.
400 Bad Request
INV_INPUT_WARN_GT_LIMIT
(Since WSAPI 1.2)
User space allocation
alerts are valid only with
a TPVV.
400 Bad Request
INV_INPUT_USR_ALRT_NON_TPVV
Retention time is greater
than expiration time.
400 Bad Request
INV_INPUT_RETAIN_GT_EXPIRE
Invalid policy
specification (for
400 Bad Request
INV_INPUT_VV_POLICY
example, caching or
system is set to true).
(Since WSAPI 1.2)
Invalid input: string
length exceeds limit.
400 Bad Request
INV_INPUT_EXCEEDS_LENGTH
(Since WSAPI 1.2)
Invalid time specified.
400 Bad Request
INV_INPUT_TIME
usr_cpg
cannot be
modified on a TPVV.
403 Forbidden
INV_OPERATION_VV_MODIFY_USR_CPG_TPVV
(Since WSAPI 1.2)
Retention time cannot be
modified on a system
400 Bad Request
UNLICENSED_FEATURE
46
Working with Storage Volumes