Dell PowerVault MD3200 Owner's Manual - Page 119

Changing Controller Ownership of the Virtual Disk, Defined Mappings, Mappings, Change, Change Mapping

Page 119 highlights

2 In the Defined Mappings pane, perform one of these actions: • Select a single virtual disk, and select Mappings Change Mapping. • Right-click the virtual disk, and select Change Mapping from the pop-up menu. 3 In Host group or host, select the appropriate host group or host. By default, the drop-down list shows the current host group or the host associated with the selected virtual disk. 4 In Logical unit number, select the appropriate LUN. The drop down list shows only the currently available LUNs that are associated with the selected virtual disk. 5 Click OK. Stop any host applications associated with this virtual disk, and unmount the virtual disk, if applicable, from your operating system. 6 In the Change Mapping dialog, click Yes to confirm the changes. The mapping is checked for validity and is saved. The Defined Mappings pane is updated to reflect the new mapping. The Topology pane is also updated to reflect any movement of host groups or hosts. NOTE: If a password is set on the storage array, the Enter Password dialog appears. Type the current password for the storage array, and click OK. 7 If configuring a Linux host, run the rescan_dm_devs utility on the host, and remount the virtual disk if required. This utility is installed on the host as part of the MDSM install process. 8 Restart the host applications. Changing Controller Ownership of the Virtual Disk If the host has a single data-path to the MD storage array, the virtual disk must be owned by the controller to which the host is connected. You must configure this storage array before you start I/O operations and after the virtual disk is created. You can change the RAID controller module ownership of a standard virtual disk or a snapshot repository virtual disk. You cannot directly change the RAID controller module ownership of a snapshot virtual disk because the Configuration: Disk Groups and Virtual Disks 119

  • 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
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260

Configuration: Disk Groups and Virtual Disks
119
2
In the
Defined Mappings
pane, perform one of these actions:
Select a single virtual disk, and select
Mappings
Change
Mapping
.
Right-click the virtual disk, and select
Change Mapping
from the
pop-up menu.
3
In
Host group or host,
select the appropriate host group or host.
By default, the drop-down list shows the current host group or the host
associated with the selected virtual disk.
4
In
Logical unit number
, select the appropriate LUN.
The drop down list shows only the currently available LUNs that are
associated with the selected virtual disk.
5
Click
OK
.
Stop any host applications associated with this virtual disk, and unmount
the virtual disk, if applicable, from your operating system.
6
In the
Change Mapping
dialog, click
Yes
to confirm the changes.
The mapping is checked for validity and is saved. The Defined Mappings
pane is updated to reflect the new mapping. The Topology pane is also
updated to reflect any movement of host groups or hosts.
NOTE:
If a password is set on the storage array, the
Enter Password
dialog
appears. Type the current password for the storage array, and click
OK
.
7
If configuring a Linux host, run the rescan_dm_devs utility on the host,
and remount the virtual disk if required. This utility is installed on the host
as part of the MDSM install process.
8
Restart the host applications.
Changing Controller Ownership of the Virtual Disk
If the host has a single data-path to the MD storage array, the virtual disk
must be owned by the controller to which the host is connected. You must
configure this storage array before you start I/O operations and after the
virtual disk is created.
You can change the RAID controller module ownership of a standard virtual
disk or a snapshot repository virtual disk. You cannot directly change the
RAID controller module ownership of a snapshot virtual disk because the