HP 8/20q HP StorageWorks Simple SAN Connection Manager User Guide (5697-0633, - Page 127

Configuration using a customized deployment, CAUTION, IMPORTANT

Page 127 highlights

If the selected subsystem already has logical disks containing data, Simple SAN Connection Manager displays a message warning that the storage subsystem will be uninitialized and all logical disks and their data will be deleted. 7. To acknowledge the warning, uninitialize the storage subsystem, delete all logical disks, and start the Storage Deployment wizard, type YES, and then click OK. To abandon this deployment, click Cancel. If the configuration is successful, the results display in the dialog box. If the partition is created from the LUNs, the volume name and drive letter assigned for each LUN (Figure 105) display in the dialog box. Figure 105 Storage Deployment wizard: deployment results (template deployment) Configuration using a customized deployment Advanced users may create a customized deployment to configure the storage subsystem. To use a customized deployment, you must have extensive knowledge of the subsystem's features and capabilities. For example, you must know the number of physical disks, the number of disks required for a disk group or storage pool, the LUN types, and the Vraid or RAID types allowed for the LUN. CAUTION: Attempt custom deployment only if you are an advanced user with extensive knowledge about the storage subsystem that you want to configure. IMPORTANT: The following limitations apply to customized deployment for the MSA 2000 family: • A maximum of 16 virtual disks (disk groups) are allowed per controller. • All LUNs on a virtual disk must be of the same RAID level. • You cannot combine SAS and SATA drives in the same virtual disk. • The minimum and maximum number of disk drives for each RAID level are as follows RAID Level Minimum Drives Maximum Drives 0 2 16 1 2 16 5 3 16 6 4 16 To configure a subsystem using a customized storage deployment: 1. Start the Storage Deployment wizard automatically or manually as follows: • Automatic: If, when you start Simple SAN Connection Manager, it detects either an uninitialized EVA storage subsystem or an MSA storage subsystem that does not have any subsystem or LUN HP StorageWorks Simple SAN Connection Manager User Guide 127

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158

HP StorageWorks Simple SAN Connection Manager User Guide
127
If the selected subsystem already has logical disks containing data, Simple SAN Connection Manager
displays a message warning that the storage subsystem will be uninitialized and all logical disks and
their data will be deleted.
7.
To acknowledge the warning, uninitialize the storage subsystem, delete all logical disks, and start the
Storage Deployment wizard, type
YES
, and then click
OK
. To abandon this deployment, click
Cancel
.
If the configuration is successful, the results display in the dialog box. If the partition is created from the
LUNs, the volume name and drive letter assigned for each LUN (
Figure 105
) display in the dialog box.
Figure 105
Storage Deployment wizard: deployment results (template deployment)
Configuration using a customized deployment
Advanced users may create a customized deployment to configure the storage subsystem. To use a
customized deployment, you must have extensive knowledge of the subsystem’s features and capabilities.
For example, you must know the number of physical disks, the number of disks required for a disk group or
storage pool, the LUN types, and the Vraid or RAID types allowed for the LUN.
CAUTION:
Attempt custom deployment only if you are an advanced user with extensive knowledge about
the storage subsystem that you want to configure.
IMPORTANT:
The following limitations apply to customized deployment for the MSA 2000 family:
A maximum of 16 virtual disks (disk groups) are allowed per controller.
All LUNs on a virtual disk must be of the same RAID level.
You cannot combine SAS and SATA drives in the same virtual disk.
The minimum and maximum number of disk drives for each RAID level are as follows
To configure a subsystem using a customized storage deployment:
1.
Start the Storage Deployment wizard automatically or manually as follows:
Automatic: If, when you start Simple SAN Connection Manager, it detects either an uninitialized
EVA storage subsystem or an MSA storage subsystem that does not have any subsystem or LUN
RAID Level
Minimum Drives
Maximum Drives
0
2
16
1
2
16
5
3
16
6
4
16