HP 3PAR Upgrade Pre-Planning Guide

3. The Administrator will then be prompted to provide a Vendor String, which is used
to distinguish between different vendor types. The script will only modify those devices
whose Vendor String matches the one that has been entered into the prompt.
Enter 3PAR in the prompt to allow the script to be executed on all HP 3PAR LUNs currently
presented to the host as shown in the output below:
Enter Vendor String: 3PAR
4. The script will then iterate through all HP 3PAR LUNs currently present on the host and
set the Attributes registry value to 0. In order to verify that the Attributes value
for all HP 3PAR LUNs were properly modified, issue the following command:
Get-ItemProperty -path
"HKLM:\SYSTEM\CurrentControlSet\Enum\SCSI\Disk*Ven_3PARdata*\*\Device
Parameters\Partmgr" -Name Attributes
The Attributes value should be set to 0 as shown in the example below:
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Enum\SCSI\Disk&Ven_3PARdata&Prod_VV\5&381f35e2&0&00014f\Device Parameters\Partmgr
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Enum\SCSI\Disk&Ven_3PARdata&Prod_VV\5&381f35e2&0&00014f\Device Parameters
PSChildName : Partmgr
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry
Attributes : 0
• If you are upgrading to HP 3PAR OS 3.1.3 MU1
After an upgrade to HP 3PAR OS 3.1.3 MU1, HP requires that host persona 15 be used for
Windows Server 2012 R2 and non-R2 and Windows Server 2008 R2 and non-R2 to prevent
this issue from occurring. The host persona must be changed to 15 before the first restart of
the Windows Server host following the upgrade. Changing to host persona 15 is an online
procedure. Use the HP 3PAR OS CLI sethost command to change the persona, and verify
by using the showhost command following the upgrade.
# sethost -persona 15 windowshost
showhost
Id Name Persona -WWN/iSCSI_Name- Port
0 windowshost WindowsServer 10000000C9606724 0:5:1
10000000C9606724 1:5:1
Microsoft MPIO Driver on Windows Server 2008
With Windows Server 2008, using the Microsoft native MPIO driver, the load-balancing policy
defaults to Active/Passive. HP requires that the load-balancing policy be set to Round Robin.
See the HP 3PAR Windows Server 2012 and Windows Server 2008 Implementation Guide for
more details on configuring the load-balancing policy.
CAUTION: During an HP 3PAR OS online upgrade from HP 3PAR OS 2.2.4 to HP 3PAR OS
2.3.1, or from HP 3PAR OS 2.3.1 to HP 3PAR OS 3.1.1, for Windows Server 2008 and Windows
Server 2008 R2 failover clusters (including failover clusters as guest OS), HP requires that all data
LUNs that are presented to Microsoft failover clusters from the HP 3PAR StoreServ Storage first be
put into Maintenance Mode. Once the HP 3PAR OS online upgrade is completed, maintenance
mode must be turned off.
This does not apply to upgrades from HP 3PAR OS 3.1.1 (that is, those with HP 3PAR OS 3.1.1.x
as a base) and later.
26 Windows Server OS Guidelines