Table 68 Message Body JSON Objects for VLUN Template Request (continued)
Ignored ValuesDescriptionAPI TypeJSON TypeMember
None* (optional)A VLUN change
notification (VCN) not be
BooleannoVcn
issued after export (-novcn).
Default: False.
None* (optional)Existing lower priority
VLUNs will be overridden
BooleanoverrideLowerPriority
(-ovrd). Use only if
hostname member exists.
Default: False.
States whether the lun
number should be
autosigned.
BooleanautoLun
(Since WSAPI 1.2)
If autoLun is true, the lun
number should be in the
numbermaxAutoLun
range of lun and
maxAutoLun. If
maxAutoLun is 0, then no
max.
(Since WSAPI 1.2)
*When creating a VLUN, the volumeName and lun members are required. Either hostname or portPos (or both
in the case of matched sets) is also required. The noVcn and overrideLowerPriority members are optional.
VLUN Creation Success
With a successful VLUN creation, the HTTP status code 201 Created is returned, without a
message body.
Upon successful creation of the VLUN, the Location response header contains the URI for the newly
created VLUN in the following format:
/api/v1/vluns/<volume name>,<lun>,<host name>,[<port>]
where:
• <volume name> is the volume that the newly created VLUN exports.
• The <host name> or [<port>] information, or both (depending on the VLUN type), are
the host name and port for the newly created VLUN. The port information will not be displayed
for ahost-type VLUN.
• If the <host name> was not provided, then the location will be:
/api/v1/vluns/<volume name>,<lun>,,<port>
VLUN Creation Errors
Upon failure, the error code and API-specific error information is returned, as shown in
Table 69 (page 70). For generic API error codes, see Table 5 (page 17).
Table 69 VLUN Creation Error Codes
DescriptionHTTP CodeAPI Error
Missing volumeName or incomplete port info, specifying
override option without hostname.
400 Bad
Request
INV_INPUT_MISSING_REQUIRED
70 Working with Virtual LUNs
To Next Page
Loading...
Need help?
General