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

Configuring raw device mapping, Windows, Verifying virtual disk access 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 71 highlights

Vendor: HP Model: HS400 Type: Direct-Access Rev: ANSI SCSI revision: 02 Configuring raw device mapping Raw Device Mapping is not supported with Windows 2003 Virtual Machine Guest Operating System on versions earlier than ESX 3.5.0. To avoid issues with RDM LUNs, complete the following changes for the applicable ESX version. For VMware ESX 3.0.1 or 3.0.2 Using the Virtual Infrastructure Client console, complete the following steps: 1. From the Configuration Tab, select Advanced Settings > Disk. 2. Add HSV3: HSV4 to the following setting: HSV1:HSV2:DGC:MSA_VOLUME:HSV3:HSV4 3. Click OK to apply the changes. Windows Verifying virtual disk access from the host With Windows, you must rescan for new virtual disks to be accessible. After you rescan, you must select the disk type, and then initialize (assign disk signature), partition, format, and assign drive letters or mount points according to standard Windows conventions. Setting the Pending Timeout value for large cluster configurations For clusters, if disk resource counts are greater than 8, HP recommends that you increase the Pending Timeout value for each disk resource from 180 second to 360 seconds. Changing the Pending Timeout value will ensure continuous operation of disk resources across the SAN. To set the Pending Timeout value: 1. Open Microsoft Cluster Administrator. 2. Select a Disk Group resource in the left pane. 3. Right-click a Disk Resource in the right pane and select Properties. 4. Click the Advanced tab. 5. Change the Pending Timeout value to 360. 6. Click OK. 7. Repeat steps 3-6 for each disk resource. Windows 71

  • 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
Vendor: HP
Model: HS400
Rev:
Type: Direct-Access
ANSI SCSI revision: 02
Configuring raw device mapping
Raw Device Mapping is not supported with Windows 2003 Virtual Machine Guest Operating
System on versions earlier than ESX 3.5.0.
To avoid issues with RDM LUNs, complete the following changes for the applicable ESX version.
For VMware ESX 3.0.1 or 3.0.2
Using the Virtual Infrastructure Client console, complete the following steps:
1.
From the Configuration Tab, select
Advanced Settings > Disk
.
2.
Add
HSV3
:
HSV4
to the following setting:
HSV1:HSV2:DGC:MSA_VOLUME:HSV3:HSV4
3.
Click
OK
to apply the changes.
Windows
Verifying virtual disk access from the host
With Windows, you must rescan for new virtual disks to be accessible. After you rescan, you must
select the disk type, and then initialize (assign disk signature), partition, format, and assign drive
letters or mount points according to standard Windows conventions.
Setting the Pending Timeout value for large cluster configurations
For clusters, if disk resource counts are greater than 8, HP recommends that you increase the
Pending Timeout value for each disk resource from 180 second to 360 seconds. Changing the
Pending Timeout value will ensure continuous operation of disk resources across the SAN.
To set the Pending Timeout value:
1.
Open Microsoft Cluster Administrator.
2.
Select a Disk Group resource in the left pane.
3.
Right-click a Disk Resource in the right pane and select
Properties
.
4.
Click the
Advanced
tab.
5.
Change the Pending Timeout value to 360.
6.
Click
OK
.
7.
Repeat steps 3-6 for each disk resource.
Windows
71