Owner manual

106 HP VMA SAN Gateway Users Guide AM456-9026A
Exporting LUNs
The fifth step in configuring the vSHARE SAN Gateway is to export the LUNs to an initiator. The
LUN must be exported before it may be accessed over block protocols.
Note: vSHARE LUNs are defined and saved within the Arrays themselves. vSHARE LUN export
records are, however, managed and stored within the vCLUSTER configuration database owned by
the master node.
Access to LUNs may be restricted to a specific initiator group, initiator, or target port when the LUN
is exported using the
lun export command.
The optional
[igroup | initiator] parameter identifies the initiator group or initiator
that may access the LUN.
The optional
[port] parameter identifies the target that may access the LUN.
A LUN ID is a SCSI identifier which may be used to differentiate between devices on the same
target port. By default, vSHARE automatically assigns LUN IDs to LUNs when they are exported
to an initiator group or initiator.
Optionally, vSHARE allows you to assign a special, user-defined LUN ID to a vSHARE LUN when
you export LUNs to an initiator group or initiator. User-defined LUN IDs may make it easier to
differentiate between LUNs. If you do assign user-defined LUN ID, HP recommends that you
specify a number below 255, as some operating systems (for example, Windows) only discover
LUN IDs between 0 and 254. LUNs cannot be exported if they are assigned an existing LUN ID;
an error message is returned and the export fails.
lun export Command
The
lun export command allows you to export the LUNs within a specific container to an
initiator or initiator group. A single LUN may be exported multiple times through different target
ports (multipathing) or to different initiators (clustered access).
Syntax
[no] lun export container <container_name> name <lun_name> [lunid][to
<igroup | initiator>]... [using <port …>]