About this task
This task maps a volume to a host or a cluster.
Infinidat simplifies the mapping of volumes to hosts as much as possible. The LUN number assigned for each mapping is insignificant. Its only role is to maintain the uniqueness of the volume - host mapping, so as long as it works, InfiniBox does not bother the user with it and assigns the LUNs automatically.
The InfiniBox RESTful management API for mapping a volume to host or cluster accepts a LUN number as an optional parameter. If the parameter is not specified, the LUN is automatically assigned by the system. (This is also the case with our VMware plugin.)
LUN numbers are automatically assigned as follows:
- For host - next available number, starting from 1.
- For cluster - next available number, starting from 11.
The reason we start assigning LUNs to a cluster starting with 11 is to avoid collision with LUNs mapped to individual hosts within the cluster. As long as no more than 10 volumes are mapped to a host individually, there is no collision between volumes mapped individually and volumes mapped to the cluster. In the rare case that a host has more than 10 volumes mapped only to it, and it also belongs to a cluster, the LUN number assignment has to be set manually.
The InfiniBox management GUI and CLI support setting the LUN number manually (in addition to the default behavior that is explained above) by the user when mapping a volume to host or cluster.
- A volume
- A host, or a cluster
- Right-click a volume from the Volume & FS screen and select Modify Mapping from the pop-up menu.
- Browse or search for a host and click Map.
- Click Apply.
The volume is mapped to the host.
Mapping a volume to a host or a cluster can be done by the following InfiniShell command:
The mapping is visible through the following queries: