HP EVA P6550 HP P6300/P6500 EVA User Guide (5697-2486, September 2013) - Page 59

Console LUN ID and OS unit ID, Adding OpenVMS hosts, show device fg/full, WWIDMGR -SHOW PORT, drvdfg

Get HP EVA P6550 PDF manuals and user guides View all HP EVA P6550 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 59 highlights

Console LUN ID and OS unit ID HP P6000 Command View software contains a box for the Console LUN ID on the Initialized Storage System Properties window. It is important that you set the Console LUN ID to a number other than zero (0). If the Console LUN ID is not set or is set to zero (0), the OpenVMS host will not recognize the controller pair. The Console LUN ID for a controller pair must be unique within the SAN. Table 11 (page 59) shows an example of the Console LUN ID. You can set the OS unit ID on the Virtual Disk Properties window. The default setting is 0, which disables the ID field. To enable the ID field, you must specify a value between 1 and 32767, ensuring that the number you enter is unique within the SAN. An OS Unit ID greater than 9999 is not capable of being served by MSCP. CAUTION: It is possible to enter a duplicate Console LUN ID or OS unit ID number. You must ensure that you enter a Console LUN ID and OS Unit ID that is not already in use. A duplicate Console LUN ID or OS Unit ID can allow the OpenVMS host to corrupt data due to confusion about LUN identity. It can also prevent the host from recognizing the controllers. Table 11 Comparing console LUN to OS unit ID ID type Console LUN ID set to 100 OS unit ID set to 50 System Display $1$GGA100: $1$DGA50: Adding OpenVMS hosts To obtain WWNs on AlphaServers, do one of the following: • Enter the show device fg/full OVMS command. • Use the WWIDMGR -SHOW PORT command at the SRM console. To obtain WWNs on Integrity servers, do one of the following: 1. Enter the show device fg/full OVMS command. 2. Use the following procedure from the server console: a. From the EFI boot Manager, select EFI Shell. b. In the EFI Shell, enter "Shell> drivers". A list of EFI drivers loaded in the system is displayed. 3. In the listing, find the line for the FCA for which you want to get the WWN information. For a Qlogic HBA, look for HP 4 Gb Fibre Channel Driver or HP 2 Gb Fibre Channel Driver as the driver name. For example: T D D Y C I R P F A V VERSION E G G #D #C DRIVER NAME IMAGE NAME 22 00000105 B X X 1 1 HP 4 Gb Fibre Channel Driver PciROM:0F:01:01:002 4. Note the driver handle in the first column (22 in the example). 5. Using the driver handle, enter the drvdfg driver_handle command to find the Device Handle (Ctrl). For example: Shell> drvcfg 22 Configurable Components Drv[22] Ctrl[25] Lang[eng] OpenVMS 59

  • 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
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
Console LUN ID and OS unit ID
HP P6000 Command View software contains a box for the Console LUN ID on the Initialized
Storage System Properties window.
It is important that you set the Console LUN ID to a number other than zero (0). If the Console LUN
ID is not set or is set to zero (0), the OpenVMS host will not recognize the controller pair. The
Console LUN ID for a controller pair must be unique within the SAN.
Table 11 (page 59)
shows
an example of the Console LUN ID.
You can set the OS unit ID on the Virtual Disk Properties window. The default setting is 0, which
disables the ID field. To enable the ID field, you must specify a value between 1 and 32767,
ensuring that the number you enter is unique within the SAN. An OS Unit ID greater than 9999
is not capable of being served by MSCP.
CAUTION:
It is possible to enter a duplicate Console LUN ID or OS unit ID number. You must
ensure that you enter a Console LUN ID and OS Unit ID that is not already in use. A duplicate
Console LUN ID or OS Unit ID can allow the OpenVMS host to corrupt data due to confusion about
LUN identity. It can also prevent the host from recognizing the controllers.
Table 11 Comparing console LUN to OS unitID
System Display
ID type
$1$GGA100:
Console LUN ID set to 100
$1$DGA50:
OS unit ID set to 50
Adding OpenVMS hosts
To obtain WWNs on AlphaServers, do one of the following:
•
Enter the
show device fg/full
OVMS command.
•
Use the
WWIDMGR -SHOW PORT
command at the SRM console.
To obtain WWNs on Integrity servers, do one of the following:
1.
Enter the
show device fg/full
OVMS command.
2.
Use the following procedure from the server console:
a.
From the EFI boot Manager, select
EFI Shell
.
b.
In the EFI Shell, enter
“
Shell> drivers
”
.
A list of EFI drivers loaded in the system is displayed.
3.
In the listing, find the line for the FCA for which you want to get the WWN information.
For a Qlogic HBA, look for
HP 4 Gb Fibre Channel Driver
or
HP 2 Gb Fibre
Channel Driver
as the driver name. For example:
T
D
D
Y C I
R
P F A
V
VERSION
E G G #D #C DRIVER NAME
IMAGE NAME
== ======== = = = == == =================================== ===================
22
00000105 B X X
1
1
HP 4 Gb Fibre Channel Driver
PciROM:0F:01:01:002
4.
Note the driver handle in the first column (22 in the example).
5.
Using the driver handle, enter the
drvdfg
driver_handle
command to find the Device
Handle (
Ctrl
). For example:
Shell>
drvcfg 22
Configurable Components
Drv[22]
Ctrl[
25
]
Lang[eng]
OpenVMS
59