HP 6400/8400 HP StorageWorks 6400/8400 Enterprise Virtual Array User Guide - Page 66

Oracle SAN driver, without MPxIO, The LUN is displayed after

Get HP 6400/8400 PDF manuals and user guides View all HP 6400/8400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 66 highlights

To identify the WWLUN ID assigned to the virtual disk and/or the LUN assigned by the storage administrator: • Oracle SAN driver, with MPxIO enabled: ◦ You can use the luxadm probe command to display the array/node WWN and associated array for the devices. ◦ The WWLUN ID is part of the device file name. For example: /dev/rdsk/c5t600508B4001030E40000500000B20000d0s2 ◦ If you use luxadm display, the LUN is displayed after the device address. For example: 50001fe1002709e9,5 • Oracle SAN driver, without MPxIO: ◦ The EVA WWPN is part of the file name (which helps you to identify the controller). For example: /dev/rdsk/c3t50001FE1002709E8d5s2 /dev/rdsk/c3t50001FE1002709ECd5s2 /dev/rdsk/c4t50001FE1002709E9d5s2 /dev/rdsk/c4t50001FE1002709EDd5s2 If you use luxadm probe, the array/node WWN and the associated device files are displayed. ◦ You can retrieve the WWLUN ID as part of the format -e (scsi, inquiry) output; however, it is cumbersome and hard to read. For example: 09 e8 20 04 00 00 00 00 00 00 35 30 30 30 31 46 45 31 30 30 32 37 30 39 45 30 35 30 30 30 31 46 45 31 30 30 32 37 30 39 45 38 36 30 30 35 30 38 42 34 30 30 31 30 33 30 45 34 30 30 30 30 35 30 30 30 30 30 42 32 30 30 30 30 00 00 00 00 00 00 .........50001F E1002709E050001F E1002709E8600508 B4001030E4000050 0000B20000 ◦ The assigned LUN is part of the device file name. For example: /dev/rdsk/c3t50001FE1002709E8d5s2 You can also retrieve the LUN with luxadm display. The LUN is displayed after the device address. For example: 50001fe1002709e9,5 • Emulex (lpfc)/QLogic (qla2300) drivers: ◦ You can retrieve the WWPN by checking the assignment in the driver configuration file (the easiest method, because you then know the assigned target) or by using HBAnyware/SANSurfer. ◦ You can retrieve the WWLUN ID by using HBAnyware/SANSurfer. You can also retrieve the WWLUN ID as part of the format -e (scsi, inquiry) output; however, it is cumbersome and difficult to read. For example: 09 e8 20 04 00 00 00 00 00 00 35 30 30 30 31 46 45 31 30 30 32 37 30 39 45 30 35 30 30 30 31 46 45 31 30 30 32 37 30 39 45 38 36 30 30 35 30 38 42 34 30 30 31 30 33 30 45 34 30 30 30 30 35 30 30 30 30 30 42 32 30 30 30 30 00 00 00 00 00 00 .........50001F E1002709E050001F E1002709E8600508 B4001030E4000050 0000B20000 ◦ The assigned LUN is part of the device file name. For example: /dev/dsk/c4t20d5s2 66 Configuring application servers

  • 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
To identify the WWLUN ID assigned to the virtual disk and/or the LUN assigned by the storage
administrator:
•
Oracle SAN driver, with MPxIO enabled:
You can use the
luxadm probe
command to display the array/node WWN and
associated array for the devices.
◦
◦
The WWLUN ID is part of the device file name. For example:
/dev/rdsk/c5t
600508B4001030E40000500000B20000
d0s2
◦
If you use
luxadm display
, the LUN is displayed after the device address. For
example:
50001fe1002709e9,
5
•
Oracle SAN driver, without MPxIO:
The EVA WWPN is part of the file name (which helps you to identify the controller). For
example:
/dev/rdsk/c3t
50001FE1002709E8
d5s2
/dev/rdsk/c3t
50001FE1002709EC
d5s2
◦
/dev/rdsk/c4t
50001FE1002709E9
d5s2
/dev/rdsk/c4t
50001FE1002709ED
d5s2
If you use
luxadm probe
, the array/node WWN and the associated device files are
displayed.
◦
You can retrieve the WWLUN ID as part of the
format -e
(scsi, inquiry) output; however,
it is cumbersome and hard to read. For example:
09 e8 20 04 00 00 00 00 00 00 35 30 30 30 31 46
.........
50001F
45 31 30 30 32 37 30 39 45 30 35 30 30 30 31 46
E1002709E050001F
45 31 30 30 32 37 30 39 45 38 36 30 30 35 30 38
E1002709E8
600508
42 34 30 30 31 30 33 30 45 34 30 30 30 30 35 30
B4001030E4000050
30 30 30 30 42 32 30 30 30 30 00 00 00 00 00 00
0000B20000
◦
The assigned LUN is part of the device file name. For example:
/dev/rdsk/c3t50001FE1002709E8d
5
s2
You can also retrieve the LUN with
luxadm display
. The LUN is displayed after the
device address. For example:
50001fe1002709e9,
5
•
Emulex (lpfc)/QLogic (qla2300) drivers:
You can retrieve the WWPN by checking the assignment in the driver configuration file
(the easiest method, because you then know the assigned target) or by using
HBAnyware/SANSurfer
.
◦
◦
You can retrieve the WWLUN ID by using
HBAnyware/SANSurfer
.
You can also retrieve the WWLUN ID as part of the
format -e
(scsi, inquiry) output;
however, it is cumbersome and difficult to read. For example:
09 e8 20 04 00 00 00 00 00 00 35 30 30 30 31 46
.........
50001F
45 31 30 30 32 37 30 39 45 30 35 30 30 30 31 46
E1002709E050001F
45 31 30 30 32 37 30 39 45 38 36 30 30 35 30 38
E1002709E8
600508
42 34 30 30 31 30 33 30 45 34 30 30 30 30 35 30
B4001030E4000050
30 30 30 30 42 32 30 30 30 30 00 00 00 00 00 00
0000B20000
◦
The assigned LUN is part of the device file name. For example:
/dev/dsk/c4t20d
5
s2
66
Configuring application servers