Storage Manager 60-NT Introduction Guide

Configuring Storage Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32 C
ONFIGURING STORAGE ARRAYS
)LJXUH 'HILQLQJD9ROXPHWR/810DSSLQJ
%\GHILQLQJWKHVSHFLILFYROXPHWR/81PDSSLQJIRUYROXPH+5HVRXUFHVXVLQJ/81WKH
IROORZLQJUHVXOWVRFFXULQWKH7RSRORJ\DQG0DSSLQJV9LHZ
7RSRORJ\9LHZ5HVXOW
)LJXUH
$+RVW*URXSZLWK6SHFLILF0DSSLQJVLQWKH7RSRORJ\9LHZ
You are mapping the volume
HResources to LUN 2.
Note: If you would create a second
volume-to-LUN mapping for host
group Omaha using volume
Marketing and LUN 7, you would
have created Partition 3 as shown in
Figure 7 on page 29.
You have selected the host group
Omaha node in the Topology View and
are ready to configure a volume-to-LUN
mapping.
After you have defined the first specific volume-to-
LUN mapping (volume HResources using LUN 2)
for host group Omaha, the host group and its
associated hosts and host ports move out from
under the Default Host Group.
The associated hosts (Omaha A and Omaha B)
can now access volume HResources. However,
since they are no longer part of the Default Host
Group they cannot access any volumes with
default volume-to-LUN mappings.