Mappings

A mapping connects a block volume to a host — a registered iSCSI, Fibre Channel, or NVMeOF initiator — so that host can actually see and use the volume. Creating a volume provisions the storage; mapping it to a host is the separate step that makes it usable, by assigning it a LUN ID the host will see it as.

A volume can be mapped to more than one host (for example, every node in a cluster that needs shared access), and a host can be mapped to more than one volume — each volume/host pairing gets its own LUN ID, which you can either choose yourself or let StorONE assign automatically with *.

Mappings can be managed from either side: by host (pick a host, decide which volumes it can see) or by volume (pick a volume, decide which hosts can see it). Both end up changing the same underlying mappings — use whichever perspective matches how you're thinking about the change.

Editing a volume's host mappings (by volume)

This replaces the complete set of hosts a volume is mapped to — any host you leave out of --hosts is unmapped from the volume. Leaving --hosts out entirely makes no change.

Using the web interface

1. Open Application Volumes > Mappings, switch to the By Volume view.
2. Select the volume and click Edit.
3. Under Volume Selection, confirm the application and volume.
4. Under Hosts - Lun Ids, list the hosts this volume should be mapped to, and optionally a specific LUN ID for each (leave blank / use * to auto-assign).
5. Confirm the change.

Using the CLI

applications mappings edit --application=<name> --volume=<name> [(--hosts=<name...> --lunIds=<lun_id...>)]

Option	Description
--application=<name>	The name of the application.
--volume=<name>	The name of the volume to map the hosts to.
--hosts=<name...>	The names of the hosts to map the volume to.
--lunIds=<lun_id...>	The LUN ID for each host. Use * to assign an available LUN ID.

Examples

Map the ledgers volume to two hosts, letting StorONE assign LUN IDs:

applications mappings edit --application finance --volume ledgers --hosts esx01,esx02 --lunIds *,*

Unmap ledgers from every host:

applications mappings edit --application finance --volume ledgers --hosts

Editing a host's volume mappings (by host)

The same operation from the host's side: this replaces the complete set of volumes a host is mapped to within an application. Any volume you leave out of --volumes is unmapped from the host. Leaving --volumes out entirely makes no change.

Using the web interface

1. Open Application Volumes > Mappings, switch to the By Host view.
2. Select the host and click Edit.
3. Under Application Selection, confirm the application, and under Host Selection, confirm the host.
4. Under Volume - Lun Ids, list the volumes this host should be mapped to, and optionally a specific LUN ID for each.
5. Confirm the change.

Using the CLI

hosts mappings edit --application=<name> --host=<name> [(--volumes=<name...> --lunIds=<lun_id...>)]

Option	Description
--application=<name>	The name of the application.
--host=<name>	The name of the host to map the volumes to.
--volumes=<name...>	The names of the volumes to map.
--lunIds=<lun_id...>	The LUN ID for each volume. Use * to assign an available LUN ID.

Example — map esx01 to two volumes in the finance application:

hosts mappings edit --application finance --host esx01 --volumes ledgers,archive --lunIds *,*

Adding mappings without replacing existing ones

mappings edit replaces the whole list, which is inconvenient if you just want to add one more volume or host to an already-mapped set. mappings add only adds — it leaves existing mappings alone. It's CLI-only; there's no separate web interface control for it (use Edit in the web interface instead).

applications mappings add --application=<name> --hosts=<name...> [(--volumes=<name...> --lunIds=<lun_id...>)]

(Equivalently: hosts mappings add, same parameters.)

Option	Description
--application=<name>	The name of the application.
--hosts=<name...>	The names of the hosts to map the volumes to.
--volumes=<name...>	The names of the volumes to map. If not specified, all volumes within the application are mapped.
--lunIds=<lun_id...>	The LUN ID for each volume. Use * to assign an available LUN ID.

Examples

Add a mapping from a new host to a single existing volume, without touching that volume's other mappings:

applications mappings add --application finance --hosts esx03 --volumes ledgers --lunIds *

Map every volume in the finance application to a new host in one shot:

applications mappings add --application finance --hosts esx03

Deleting specific mappings

Similarly, mappings delete removes specific mappings without requiring you to retype the full surviving list. It's CLI-only; use Edit in the web interface to remove mappings there.

applications mappings delete --application=<name> [--hosts=<name...> --volumes=<name...>] [--force]

(Equivalently: hosts mappings delete, same parameters.)

Option	Description
--application=<name>	The name of the application.
--hosts=<name...>	The names of the hosts to unmap. If not specified, all mapped hosts are unmapped.
--volumes=<name...>	The names of the volumes to unmap. If not specified, all volumes within the application are unmapped.
--force	Skip the confirmation prompt.

Examples

Unmap esx03 from the ledgers volume only:

applications mappings delete --application finance --hosts esx03 --volumes ledgers

Remove every mapping for the finance application entirely:

applications mappings delete --application finance --force

Listing mappings by host

Using the web interface

Open Application Volumes > Mappings, By Host view. Each host is shown with the volumes and LUN IDs mapped to it.

Using the CLI

hosts mappings list [--application=<name> --host=<name>]

Option	Description
--application=<name>	Filter by application name.
--host=<name>	Filter by host name.

Example

hosts mappings list --application finance --host esx01

Listing mappings by volume

Using the web interface

Open Application Volumes > Mappings, By Volume view. Each volume is shown with the hosts and LUN IDs it's mapped to.

Using the CLI

applications mappings list [--application=<name> --volume=<name>]

Option	Description
--application=<name>	Filter by application name.
--volume=<name>	Filter by volume name.

Example

applications mappings list --application finance --volume ledgers

---

See also: Volumes. Mapping applies to block volumes (iSCSI/FC/NVMeOF); for NAS/object volumes, see File Systems instead — a volume is either mapped to hosts as block storage or given a file system, not both.