topic Re: W2000 Cluster on Prolient 5500 in ProLiant Servers (ML,DL,SL)

W2000 Cluster on Prolient 5500

Jim Colley_1 — Wed, 18 Dec 2002 18:34:37 GMT

I have 2 Prolient 5500's with FC host adapters, using a RA4000 for the shared drives.
It was a NT 4.0 cluster and worked flawless. Now that I have done a rolling upgrade to W2000 Adavanced Server, I have a frustrating cluster error. The clustering works, but the node that was upgraded first is unable to access the shared drives if it is rebooted while the cluster is running. Everything fails back and forth as it should, until you reboot the node, once rebooted, it can not mount the shared drives. Everything must be shut down, that node brought up first, then the other node, and everything is fine.

Re: W2000 Cluster on Prolient 5500

JohnWRuffo — Wed, 18 Dec 2002 18:56:13 GMT

Take a look at this Article: http://support.microsoft.com/default.aspx?scid=kb;en-us;197047

Re: W2000 Cluster on Prolient 5500

Doug de Werd — Wed, 18 Dec 2002 21:29:32 GMT

Per the article refernced by John, check to see what the preferred servers are, and also if automatic failback is enabled. When you say it cannot "mount" the drives, what specifically do you mean by that? The only way that you will be able to "see" the drives after you reboot (by an application or via Disk Admin) is if you Move the application to the rebooted node via Cluster Admin.

Thanks,
Doug

Re: W2000 Cluster on Prolient 5500

Jim Colley_1 — Wed, 18 Dec 2002 21:40:40 GMT

Node 2 was upgraded first. Now when I move all resources to Node 1, reboot node 2, I can not fail any resources back to node node 2. They are all dependent on the disk resources which fail. If I go into disk manager, the drives do not show up. If I shut everything down and bring node 2 up first, every thing is fine.

Re: W2000 Cluster on Prolient 5500

Doug de Werd — Thu, 19 Dec 2002 15:36:46 GMT

One thing you might try is to evict Node 2 from the cluster (via Cluster Admin) and then add it back in. You might try this both before you reboot it, and if that doesn't work, try it after you reboot.

Thanks,
Doug