Config Guide
AssuredSAN 3xx4
83-00006911-00-01 Rev B
Page 21
8.3.1.
Mapping in the V3 Interface:
Once the users have added their Disk Groups to create the Pools, they may now create and map volumes. This is very
similar to how the customers currently create volumes in the V2 WBI, however volumes are now assigned to a pool
instead of a VDisk.
RealStor includes the ability to assign volumes to groups. This grouping capability enables large numbers of initiators
to be mapped to LUNs in a single operation – improving the efficiency and organization of host configuration. In
addition, the V3 interface incorporates search filters that greatly simplify the task of managing large numbers of
volumes and reduce management time.
To map a volume, the user may select the Mapping topic, or click on the volume and select Mapping under the action
tab. The Mapping screen in the V3 interface is different than the V2 version and contains several enhancements.
Users may now create initiator names, assign to Hosts, and then assign Host to Host Groups. This greatly simplifies
the tasks of managing and mapping large numbers of Hosts that may have the same mapping requirements. Filter
capabilities also exist for the Host and Host group tables.
RealStor allows for users to do default mapping by selecting “All other initiators.” Selecting this will make the
volume available to all host ports. The user may also do explicit mapping - mapping to individual initiators, hosts, or
host groups. The Storage Management Console will map to both the A and B controller by default for each port.
Figure 2 is an example of the Mapping Screen.
Figure 2 – Mapping Screen in RealStor’s Management Console
8.3.2.
Provisioning and Mapping with the CLI:
RealStor will support a robust CLI. RealStor maintains a set of commands for the Linear (V2) interface, and a separate
set of commands specific to the new Virtual (V3) interface. While much of the command-set is shared between the
two, there are some significant differences which are required to maintain backwards compatibility while allowing
users to manage both versions in the same CLI.
While this document is not intended to highlight all the differences, some of the commands specific to provisioning
and mapping that customers will want to review are highlighted here. For detailed description of all the changes, CLI
Reference guide will be available.
First, specific to setting a management interface,
set protocols
and
set cli-parameters
will include support for setting
the management-mode interface to
v2
or
v3
at both a global (set protocols) or session level (set cli-parameters). This
setting will dictate which CLI commands are used.
