HP StorageWorks MSA 2/8 HP StorageWorks Fabric OS Procedures V3.1.x/4.1.x User - Page 157

restart I/O. For example, If you are using multi-pathing software, re-enable the affected path.

Page 157 highlights

Updating Switches to the Core PID Addressing 14. Import the volume groups using vgimport. The proper usage would be vgimport -m . For example: vgimport -m /tmp/jbod_map /dev/jbod /dev/dsk/c64t8d0 /dev/dsk/c64t9d0 15. Activate the volume groups using vgchange. The proper usage would be vgchange -a y . For example: vgexport -a y /dev/jbod 16. If you are not using multi-pathing software, mount all devices again and restart I/O. For example: mount /mnt/jbod 17. If you are using multi-pathing software, re-enable the affected path. The preceding steps do not "clean up" the results from ioscan. When viewing the output of ioscan (see the following example), notice that the original entry is still there, but now has a status of NO_HW. Example # ioscan -funC disk Class I H/W Path Driver S/W State H/W Type Description disk 0 0/0/1/1.2.0 adisk CLAIMED DEVICE SEAGATEST39204LC /dev/dsk/clt2d0 /dev/rdsk/c1t2d0 disk 1 0/0/2/1.2.0 adisk CLAIMED DEVICE HP DVD-ROM 304 /dev/dsk/c3t2d0 /dev/rdsk/c3t2d0 disk 319 0/4/0/0.1.2.255.14.8.0 adisk CLAIMED DEVICE SEAGATEST336605FC /dev/dsk/c64t8d0 /dev/rdsk/c64t8d0 disk 320 0/4/0/0.1.18.255.14.8.0adisk NO_HW DEVICE SEAGATEST336605FC /dev/dsk/c65t8d0 /dev/rdsk/c65t8d0 18. To remove the original (outdated) entry, the command rmsf (remove special file) will be needed. The proper usage for this command would be rmsf -a -v . For example: rmsf -a -v /dev/dsk/c65t8d0 Fabric OS Procedures Version 3.1.x/4.1.x User Guide 157

  • 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
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270

Updating Switches to the Core PID Addressing
157
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
14.
Import the volume groups using
vgimport
. The proper usage would be
vgimport
–m <mapfile> <path_to_volume_group>
<physical_volume_path>
.
For example:
vgimport
–m /tmp/jbod_map /dev/jbod /dev/dsk/c64t8d0
/dev/dsk/c64t9d0
15.
Activate the volume groups using vgchange. The proper usage would be
vgchange
–a y <path_to_volume_group>
.
For example:
vgexport
–a y /dev/jbod
16.
If you are not using multi-pathing software, mount all devices again and
restart I/O. For example:
mount
/mnt/jbod
17.
If you are using multi-pathing software, re-enable the affected path. The
preceding steps do not “clean up” the results from ioscan. When viewing the
output of ioscan (see the following example), notice that the original entry is
still there, but now has a status of NO_HW.
Example
18.
To remove the original (outdated) entry, the command rmsf (remove special
file) will be needed. The proper usage for this command would be
rmsf
–a
–v <path_to_device>
. For example:
rmsf
–a –v /dev/dsk/c65t8d0
# ioscan -funC disk
Class
I H/W Path
Driver S/W StateH/W TypeDescription
-------------------------------------------------------------------------------
disk
0 0/0/1/1.2.0
adisk CLAIMED DEVICE SEAGATEST39204LC
/dev/dsk/clt2d0 /dev/rdsk/c1t2d0
disk
1 0/0/2/1.2.0
adisk CLAIMED DEVICE HP
DVD-ROM 304
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk
319 0/4/0/0.1.2.255.14.8.0adisk CLAIMED DEVICE SEAGATEST336605FC
/dev/dsk/c64t8d0 /dev/rdsk/c64t8d0
disk
320 0/4/0/0.1.18.255.14.8.0adisk NO_HW
DEVICE SEAGATEST336605FC
/dev/dsk/c65t8d0 /dev/rdsk/c65t8d0