Professional Documents
Culture Documents
Storage Provisioning PDF
Storage Provisioning PDF
Technical Note
P/N 300-009-148
REV A01
April 14, 2009
1
Executive summary
Executive summary
Introduced in EMC® Solutions Enabler and Symmetrix® Management
Console (SMC) version 7.0, the Autoprovisioning Groups feature
provides an easier, faster way to provision storage in Symmetrix V-
Max™ arrays running Enginuity™ 5874. Most of the applications
running on Symmetrix arrays require a fault-tolerant environment with
clustered hosts as well as multiple paths to devices. Autoprovisioning
Groups was developed to make storage allocation easier and faster,
especially with these types of configurations.
Mapping and masking devices in previous versions of Solutions Enabler
required a separate command for each initiator/port combination
through which devices would be accessed. Both the symaccess
command in Solutions Enabler and SMC allow the user to create a group
of devices (storage group), a group of director ports (port group), and a
group of host initiators (initiator group), and associate them in a
masking view. When the masking view is created, the devices are
automatically mapped and masked.
After the masking view is created, any objects (devices, ports, or
initiators) added to an existing group automatically become part of the
associated masking view. This means that no additional steps are
necessary to add additional devices, ports, or initiators to an existing
configuration. All necessary operations to make them part of the
configuration are handled automatically by Symmetrix Enginuity once
the objects are added to the applicable group. This reduces the number
of commands needed for mapping and masking devices and allows for
easier storage allocation and de-allocation.
Introduction
This technical note describes how to provision storage using the
Symmetrix Autoprovisioning Groups feature. The goals of this paper
are:
! To summarize the functionality of the feature
! To provide examples showing how to use Autoprovisioning Groups
to provision storage
Audience
This technical note is intended for the technology professional who
works in an environment with Symmetrix V-Max disk arrays. It is
Note: The use case examples were developed using the same hosts, therefore
the initiator WWNs are the same in all of the use cases. A WWN can only
belong to a single initiator group; however, initiator groups can be cascaded
by placing them in other initiator groups.
Step 2 - Create a view and specify a view name, HBA WWN, front-end
port, and Symmetrix volumes for the second path.
Gatekeepers 093 – 096 will be made available on the second path:
The devices are now available to the initiators on the storage ports. After
the host configures the devices, they are available to the operating
system on both paths.
Symmetrix ID : 000192601254
# syminq
# symcfg discover
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767816
}
Director Identification
{
FA-7E:0
}
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767817
}
Director Identification
{
FA-7F:1
}
this goal:
1. Create a Symmetrix device group that contains the production
volumes and the clone target volumes.
2. Create the production storage group that contains the
production volumes.
3. Create the backup storage group that contains the clone target
volumes.
4. Create the port group.
5. Create the production server initiator group.
6. Create the backup server initiator group.
7. Create the production server masking view containing the
production storage group, port group, and production initiator
group.
8. Create the backup server masking view containing the backup
storage group, port group, and backup initiator group.
Once the masking view has been created, the devices are available to the
initiators on the storage ports. Host-specific commands can then be run
to configure the devices to the operating system.
The device group now contains the standard volumes (STD) for the
production host and the target volumes (TGT) for the backup host:
Groups that have been created can be viewed using symaccess list
and symaccess show commands:
Symmetrix ID : 000192601254
Symmetrix ID : 000192601254
Devices : 0798:079B
Step 3 - Create the backup storage group that contains the clone target
volumes. For this step, the device group will be used with the –tgt flag
to add the target devices:
Symmetrix ID : 000192601254
Devices : 0912:0915
Step 4 – Create the port group containing the two Symmetrix ports to
which the HBAs are zoned.
Symmetrix ID : 000192601254
Director Identification
{
FA-7E:0
FA-7F:1
}
The –detail option can also be used with symaccess list to generate
output with the port and view counts in columns:
Symmetrix ID : 000192601254
Port View
Port Group Name Count Count
-------------------------------- ----- -----
dbsrv_port 2 0
# cat /prod_WWN_file
WWN:10000000c9767816
WWN:10000000c9767817
Symmetrix ID : 000192601254
Host Initiators
{
WWN :10000000c9767816
WWN :10000000c9767817
}
{
None
}
Symmetrix ID : 000192601254
Host Initiators
{
WWN :10000000c97683e0
WWN :10000000c97683e1
}
The production masking view has now been created. Both symaccess
list and symaccess show display the view along with its associated
initiator group, port group, and storage group:
Symmetrix ID : 000192601254
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767816
WWN : 10000000c9767817
}
Director Identification
{
FA-7E:0
FA-7F:1
}
# syminq
Step 8 – Create the backup server masking view containing the backup
storage group, port group, and backup initiator group.
The backup masking view has now been created. Both symaccess list
and symaccess show display the view along with its associated initiator
group, port group, and storage group:
Symmetrix ID : 000192601254
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c97683e0
WWN : 10000000c97683e1
}
Director Identification
{
FA-7E:0
FA-7F:1
}
# syminq
Step 2 - Add target devices 916 and 917 to the device group.
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767816
WWN : 10000000c9767817
}
Director Identification
{
FA-7E:0
FA-7F:1
}
Note: The new devices will be listed as “N/A” in the PdevName field in
symdg show output and “Not Visible” in the symaccess show view
output until they are configured by the host and symcfg discover is run.
Step 4 – Run the symaccess add command to add the target devices
that were placed in the device group into the backup storage group.
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c97683e0
WWN : 10000000c97683e1
}
Director Identification
{
FA-7E:0
FA-7F:1
}
After running the applicable host commands, standard devices 7C3 and
7C4 are available to the production host and target devices 916 and 917
are available to the backup host:
# syminq
# syminq
Symmetrix ID : 000192601254
Devices : 092A:092D
Step 2 - Create a storage group that contains the volumes that will be
presented to Node A only (7DB:7DC). The devices to be added will be
specified in the CLI command.
Symmetrix ID : 000192601254
Devices : 07DB:07DC
Step 3 - Create a storage group that contains the volumes that will be
presented to Node B only (7DD:7DE). The devices to be added will be
specified in the CLI command.
Symmetrix ID : 000192601254
Devices : 07DD:07DE
Symmetrix ID : 000192601254
Director Identification
{
FA-7E:0
FA-7F:1
}
# cat clustnodeA_WWN_file
WWN:10000000c9767816
WWN:10000000c9767817
Symmetrix ID : 000192601254
Host Initiators
{
WWN :10000000c9767816
WWN :10000000c9767817
}
# cat clustnodeB_WWN_file
WWN:10000000c97683e0
WWN:10000000c97683e1
Symmetrix ID : 000192601254
Host Initiators
{
WWN :10000000c97683e0
WWN :10000000c97683e1
}
None
}
Step 8 - Add the initiator group for Node B to the cascaded initiator
group.
Symmetrix ID : 000192601254
Host Initiators
{
IG :clustnodeA_init
IG :clustnodeB_init
}
Symmetrix ID : 000192601254
Host Initiators
{
IG : clustnodeA_init
IG : clustnodeB_init
}
Director Identification
{
FA-7E:0
FA-7F:1
}
The -ig <child_ig> option can be chosen to see the cascaded group
from the child group’s perspective:
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767816
WWN : 10000000c9767817
Director Identification
{
FA-7E:0
FA-7F:1
}
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c97683e0
WWN : 10000000c97683e1
}
Director Identification
{
FA-7E:0
FA-7F:1
}
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767816
WWN : 10000000c9767817
}
Director Identification
{
FA-7E:0
FA-7F:1
}
Step 11 - Create the Node B masking view containing the Node B storage
group, port group, and Node B initiator group.
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c97683e0
WWN : 10000000c97683e1
}
Director Identification
{
FA-7E:0
FA-7F:1
}
After configuring the devices from the operating systems, the correct
devices are available to each cluster node:
Cluster Node A sees thin devices 92A – 92Das well as RAID 6 devices
7DB – 7DC:
# syminq -sym
Cluster Node B also sees thin devices 92A – 92D, but it sees RAID 6
devices 7DD – 7DE:
# syminq -sym
The order in which the parent and child initiator groups are created will have
an effect on what LUNs are assigned to the devices in the groups. If the order
used in this example were reversed, meaning that the views for the child
groups were created before the view for the parent group, the LUNs of the
devices would be different.
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c97683e0
WWN : 10000000c97683e1
}
Director Identification
{
FA-7E:0
FA-7F:1
}
Step 1 – Delete the masking view and, optionally, unmap the devices in
the associated storage group by using the –unmap option.
When the prompt returns, the view has been deleted and the devices in
the storage group have been ummapped from the FA ports:
# symaccess show view proddb_view -sid 54
...
00A8 Not Visible ???:? 09A:D3 2-Way Mir N/Grp'd RW 6
00A9 Not Visible ???:? 09C:C2 2-Way Mir N/Grp'd RW 6
00AA Not Visible ???:? 09B:D4 2-Way Mir N/Grp'd RW 6
00AB Not Visible ???:? 10D:C0 2-Way Mir N/Grp'd RW 6
...
07B0 Not Visible ???:? 10A:DA RAID-5 N/Grp'd RW 4314
07B1 Not Visible ???:? 10D:D9 RAID-5 N/Grp'd RW 4314
07B2 Not Visible ???:? 10C:DA RAID-5 N/Grp'd RW 4314
07B3 Not Visible ???:? 09A:D5 RAID-5 N/Grp'd RW 4314
...
Step 2 – Delete the initiator group. If the initiator group is not empty, the
initiators must be removed from the group prior to the delete or the –
force flag must be used.
Step 3 – Delete the port group. If the port group is not empty, the ports
must be removed from the group prior to the delete or the –force flag
must be used.
Step 4 – Delete the storage group. If the storage group is not empty, the
volumes must be removed from the group prior to deleting the group or
Symmetrix ID : 000192601254
Symmetrix ID : 000192601254
View
Group Name Count Count Type
-------------------------------- ----- ----- ---------
init_LICOA067 2 3 Initiator
licoa057_1_hbas 2 1 Initiator
ctrlsrv_licoa068 2 1 Initiator
port_LICOA067 2 3 Port
licoa057_1_ports 2 1 Port
ctrlsrv_licoa068 2 1 Port
stor_LICOA067 8 1 Storage
licoa057_1_stor 24 1 Storage
ctrlsrv_licoa068 12 1 Storage
# syminq -sym
An initiator group, storage group, and port group have already been
created for the host:
Symmetrix ID : 000192601254
View
Group Name Count Count Type
-------------------------------- ----- ----- ---------
proddb_init 2 0 Initiator
proddb_port 2 0 Port
proddb_stor 4 0 Storage
Symmetrix ID : 000192601254
Host Initiators
{
WWN :10000000c97683e0
WWN :10000000c97683e1
}
Symmetrix ID : 000192601254
Devices : 07B0:07B3
Symmetrix ID : 000192601254
Director Identification
{
FA-7E:0
FA-7F:1
}
A masking view can now be created that will mask and map the four
devices in the storage group (7B0 - 7B3) on the ports in the port group to
the WWNs in the initiator group. When the mapping is done, the devices
in the storage group will get the next four LUNs available on the FA
port. By specifying a starting LUN value, in this case LUN 1, the LUN
values will be assigned dynamically:
Because mapping is also being done, the prompt will take a few
moments to return. After the command completes, the devices are
mapped and masked and available to be configured by the host
operating system. The devices have been dynamically assigned LUNs
001 – 004, which are displayed in the Host LUN column of the storage
group:
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c97683e0
WWN : 10000000c97683e1
}
Director Identification
{
FA-7E:0
FA-7F:1
}
These LUN values differ from the LUNs actually assigned on the FA
(0B1-0B4):
# symcfg list -address -FA 07E -P 0 -sid 54
After running the host commands to configure the devices, they are now
available to the operating system on two paths with LUNs 001 - 004:
# syminq -sym
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767816
}
Director Identification
{
FA-7E:0
}
The devices have been added to the storage group and are mapped and
masked with the specified dynamic LUN addresses:
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767816
}
Director Identification
{
FA-7E:0
}
The LUNs that are actually assigned on the FA are different from the
dynamically assigned LUNs:
FA-7E 07E 0
0054 c3t5000097208139918d0s* ACLX 0 00 000
0055 Not Visible 0 00 001
0056 Not Visible 0 00 002
0088 Not Visible 0 00 003
...
00AA Not Visible 0 00 0B7
00AB Not Visible 0 00 0B8
00AC c3t5000097208139918d24* 0 00 0B9
00AD c3t5000097208139918d24* 0 00 0BA
00AE Not Visible 0 00 0BB
00AF Not Visible 0 00 0BC
0907 c3t5000097208139918d21* 0 00 0BD
0908 c3t5000097208139918d22* 0 00 0BE
00B0 Not Visible 0 00 0C0
00B1 Not Visible 0 00 0C1
...
00A4 Not Visible 0 00 0F4
00A5 Not Visible 0 00 0F5
00A6 Not Visible 0 00 0F6
00A7 Not Visible 0 00 0F7
Total ----
Mapped Devices: 215
Including Metamembers: 215
Available Addresses: 3874 (s)
After configuring the devices to the host, the host special device files
have been created using the dynamic LUN addresses:
# syminq -sym
After running symcfg discover, the special device files appear in the
symaccess show view output:
Symmetrix ID : 000192601254
Host Initiators
{
WWN : 10000000c9767816
}
Director Identification
{
FA-7E:0
}
Step 8 – Follow the same steps and create a masking view for Path 1.
The standard volumes (STD) for the production host and the target
volumes (TGT) for the backup host can now be selected. Selecting the
STD device type brings up a list of available Standards. The following
figure shows four devices (7DB – 7DE) are chosen:
folder, or the Storage Groups folder, then clicking Device Masking and
Mapping > Storage Groups Maintenance > Create Storage Group ...
Initiator Groups folder, then clicking Device Masking and Mapping >
Initiator Groups Maintenance > Create Initiator Group ...
folder, or the Masking Views folder, then clicking Device Masking and
Mapping > Masking Views Maintenance > Create Masking View ...
Step 8 – Create the backup server masking view containing the backup
storage group, port group, and backup initiator group.
host:
# syminq -sym
Target devices 7EA and 7EB are available to the backup host:
# syminq -sym
Note: It is also possible to use the Expand Storage wizard to add devices to a
storage group.
Devices 92A to 92D are chosen and added to the Group Members list by
selecting them and then clicking Add. The storage group is then created
by clicking OK:
Step 7 - Create the cascaded initiator group containing the Node A and
Node B initiator groups.
Cascaded initiator groups are created in the same way that regular
initiator groups are created except other initiator groups are added to the
cascaded group instead if individual initiators. Existing initiator groups
will appear at the end of the list of available initiators. They can be
selected and added to the cascaded initiator group just as regular
initiators are added.
folder, or the Masking Views folder, then clicking Device Masking and
Mapping > Masking Views Maintenance > Create Masking View ...
Step 9 - Create the Node A masking view containing the Node A storage
group, port group, and Node A initiator group.
Use the same steps to create the masking view for the devices that will be
seen only by Node A.
7DB – 7DC:
# syminq -sym
Cluster Node B also sees thin devices 92A – 92D, but it sees RAID 6
devices 7DD – 7DE:
# syminq -sym
Step 1 – Delete the masking view and, optionally, unmap the devices in
the associated storage group.
The dialog box used to delete views can be accessed by right-clicking on
the “dbprodsrv_view” view in the Properties pane, then clicking Device
Masking and Mapping > Masking Views Maintenance > Delete Masking
View ...
# syminq -sym
An initiator group, storage group, and port group have already been
created for the host.
A masking view can now be created that will mask and map the devices:
Conclusion
Mapping and masking devices in previous versions of Solutions Enabler
required a separate operation for each initiator/port combination
through which devices would be accessed. In Solutions Enabler and
SMC 7.0 the Autoprovisioning Groups feature allows the user to create a
group of devices (storage group), a group of director ports (port group),
and a group of host initiators (initiator group), and associate them in a
masking view. When the masking view is created, the devices are
automatically mapped and masked.
After the masking view is created, any objects (devices, ports, or
initiators) added to an existing group automatically become part of the
associated masking view. This means that no additional steps are
necessary to add additional devices, ports, or initiators to an existing
configuration. All necessary operations to make them part of the
configuration are handled automatically by Symmetrix Enginuity once
the objects are added to the applicable group. This reduces the number
of commands needed for mapping and masking devices and allows for
easier storage allocation and de-allocation.
Autoprovisioning Groups makes storage allocation easier and faster,
especially in modern storage environments where fault-tolerant
configurations with clustered hosts as well as multiple paths to devices
are normally required.