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

Specifying DiskMaxLUN, Verifying connectivity, Verifying virtual disks from the host

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 70 highlights

ESX 4.x commands • The # esxcli nmp device setpolicy --device naa.6001438002a56f220001100000710000 --psp VMW_PSP_MRU command sets device naa.6001438002a56f220001100000710000 with an MRU multipathing policy. • The # esxcli nmp device setpolicy --device naa.6001438002a56f220001100000710000 --psp VMW_PSP_FIXED command sets device naa.6001438002a56f220001100000710000 with a Fixed multipathing policy. • The # esxcli nmp fixed setpreferred --device naa.6001438002a56f220001100000710000 --path vmhba1:C0:T2:L1 command sets device naa.6001438002a56f220001100000710000 with a Preferred multipathing policy. NOTE: Each LUN can be accessed through both EVA storage controllers at the same time; however, each LUN path is optimized through one controller. To optimize performance, if the LUN multipathing policy is Fixed, all servers must use a path to the same controller. You can also set the multipathing policy from the VMware Management User Interface (MUI) by clicking the Failover Paths tab in the Storage Management section and then selecting Edit... link for each LUN whose policy you want to modify. Specifying DiskMaxLUN The DiskMaxLUN setting specifies the highest-numbered LUN that can be scanned by the ESX server. • For ESX 2.5.x, the default value is 8. If more than eight LUNs are presented, you must change the setting to an appropriate value. To set DiskMaxLUN, select Options> Advanced Settings in the MUI, and then enter the highest-numbered LUN. • For ESX 3.x or ESX 4.x, the default value is set to the Max set value of 256. To set DiskMaxLun to a different value, in Virtual Infrastructure Client, select Configuration> Advance Settings> Disk> Disk.MaxLun, and then enter the new value. Verifying connectivity To verify proper configuration and connectivity to the SAN: • For ESX 2.5.x, enter the # vmkmultipath -q command. • For ESX 3.x, enter the # esxcfg-mpath -l command. • For ESX 4.x, enter the # esxcfg-mpath -b command. For each LUN, verify that the multipathing policy is set correctly and that each path is marked on. If any paths are marked dead or are not listed, check the cable connections and perform a rescan on the appropriate FCA. For example: • For ESX 2.5.x, enter the # cos-rescan.sh vmhba0 command. • For ESX 3.x or ESX 4.x, enter the # esxcfg-rescan vmhba0 command. If paths or LUNs are still missing, see the VMware or HP Storage documentation for troubleshooting information. Verifying virtual disks from the host To verify that the host can access the virtual disks, enter the # more /proc/scsi/scsi command. The output lists all SCSI devices detected by the server. An EVA6400/8400 LUN entry looks similar to the following: Host: scsi3 Channel: 00 ID: 00 Lun: 01 70 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
ESX 4.x commands
•
The
# esxcli nmp device setpolicy --device
naa.6001438002a56f220001100000710000 --psp VMW_PSP_MRU
command sets
device
naa.6001438002a56f220001100000710000
with an MRU multipathing policy.
•
The
# esxcli nmp device setpolicy --device
naa.6001438002a56f220001100000710000 --psp VMW_PSP_FIXED
command sets
device
naa.6001438002a56f220001100000710000
with a Fixed multipathing policy.
•
The
# esxcli nmp fixed setpreferred --device
naa.6001438002a56f220001100000710000 --path vmhba1:C0:T2:L1
command
sets device
naa.6001438002a56f220001100000710000
with a Preferred multipathing
policy.
NOTE:
Each LUN can be accessed through both EVA storage controllers at the same time;
however, each LUN path is optimized through one controller. To optimize performance, if the LUN
multipathing policy is Fixed, all servers must use a path to the same controller.
You can also set the multipathing policy from the VMware Management User Interface (MUI) by
clicking the
Failover Paths
tab in the Storage Management section and then selecting
Edit… link
for each LUN whose policy you want to modify.
Specifying DiskMaxLUN
The
DiskMaxLUN
setting specifies the highest-numbered LUN that can be scanned by the ESX
server.
•
For ESX 2.5.x, the default value is 8. If more than eight LUNs are presented, you must change
the setting to an appropriate value. To set
DiskMaxLUN
, select
Options> Advanced Settings
in the MUI, and then enter the highest-numbered LUN.
•
For ESX 3.x or ESX 4.x, the default value is set to the Max set value of 256. To set
DiskMaxLun
to a different value, in Virtual Infrastructure Client, select
Configuration> Advance
Settings> Disk> Disk.MaxLun
, and then enter the new value.
Verifying connectivity
To verify proper configuration and connectivity to the SAN:
•
For ESX 2.5.x, enter the
# vmkmultipath -q
command.
•
For ESX 3.x, enter the
# esxcfg-mpath -l
command.
•
For ESX 4.x, enter the
# esxcfg-mpath -b
command.
For each LUN, verify that the multipathing policy is set correctly and that each path is marked
on
.
If any paths are marked
dead
or are not listed, check the cable connections and perform a rescan
on the appropriate FCA. For example:
•
For ESX 2.5.x, enter the
# cos-rescan.sh vmhba0
command.
•
For ESX 3.x or ESX 4.x, enter the
# esxcfg-rescan vmhba0
command.
If paths or LUNs are still missing, see the VMware or HP Storage documentation for troubleshooting
information.
Verifying virtual disks from the host
To verify that the host can access the virtual disks, enter the
# more /proc/scsi/scsi
command.
The output lists all SCSI devices detected by the server. An EVA6400/8400 LUN entry looks similar
to the following:
Host: scsi3 Channel: 00 ID: 00 Lun: 01
70
Configuring application servers