Everytime i have upgraded PP on a Cluster was i moved everything off of one node.  Then upgraded that node and rebooted.  When it came backup, i failed everything back to it and upgraded the last node.

Microsoft Cluster does not like changes to a Cluster Resource such as storage. I upgraded PowerPath on the standby node then failed over to the standby node and upgraded what was previously the active node. To make sure that there were no issues, I failed back to the original active node.

most of the time u can upgrade the PP version w/ removing the old PP unles your version too old. If you to remove the PP then make a note of the `powermt check registration` and add license key back once the installation is completed.

Hi All,

Unfortunately I do the upgrade failed at my client's site.

The goal is upgrade windows 2000 to Windows 2003, and then update related host softwares, such as HBA driver & utility, PowerPath.

The procedures as following:

1. move all cluster resources to one node

2. upgrade PP 4.5.1 to PP 4.5.2 for Windows 2003 upgrade fulfillment

3. upgrade Windows 2000 to Windows 2003

4. cluster function is good.

5. install Hotfix KB957910

6. upgrade PP 4.5.2 to PP 5.3.1b

7. Cluster service cannot start due to cannot access disk

another method also failed:

1. remove all old PP

2. upgrade windows 2000 to windows 2003

3. install hotfix KB957910

4. install PP 5.3.1b

very appreciated for any suggestion

Dennis Dai

1. move all cluster resources to one node 2. upgrade PP 4.5.1 to PP 4.5.2 for Windows 2003 upgrade fulfillment 3. upgrade Windows 2000 to Windows 2003 4. cluster function is good. 5. install Hotfix KB957910 6. upgrade PP 4.5.2 to PP 5.3.1b 7. Cluster service cannot start due to cannot access disk

did cluster services start after step 5 ?  After step 6 did you see the drives in Disk Management ?

Hi All,

The root cause is HBA persisten binding configuration.

I update the driver, and destory persisten binding automatically.

Then add it back original binding, and cluster service was up and fine.

Why the binding changed cause the cluster failed?

Dennis

a better question is why are you using binding in the first place ? You typically see binding on Windows done when you attach tape drives and you want to make them persistent (their address, for example \\.\Tape0). You have PowerPath running on the box so it masks all the device address changes from the host, as long as the disk signature matches, windows/ms clustering is happy.

Hi Dynamox,

This is previous configuration that one company implemented, I thought he followed hba doc to set persistent binding.

Many customer will face ESOL for Windows 2000. so I support them to do OS upgrade to Windows 2003.

As my experience, cluster service will not work properly due to incorrect consistent binding even if the signature is correct. 

interesting, never had to do persistent binding in win2k clusters ..oh well as long as it works.