ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Win Server 2003 Enterprise on CL380 Cluster

 
Charles Crawford
Occasional Contributor

Win Server 2003 Enterprise on CL380 Cluster

Cannot get the second node to join without corruption. Recd error in event log of device\scsi\sym_hi1. Any suggestions.

Thanks
16 REPLIES
Doug de Werd
Honored Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

You might check some of these other message threads. have you also updated latest firmware on the HW? cna you be a little more descriptive about how far you get into the install and when exactly the error comes up?

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=568994

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=537969

Thanks,
Doug
Expert in ProLiant Clusters
Brian_Murdoch
Honored Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

Charles,

You must make sure that one node has SCSI ID7 (Default) and the other has SCSI ID 6 when communicating with the shared storage.

This has to be changed using the SCU if you have performed a system erase and wiped the settings. Both will default to 7, so when you bring up the second node you will hit problems.

I have attached a note on this to my reply.

I hope this helps.

Brian
Charles Crawford
Occasional Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

Thanks for you help gents.

I install both nodes as I did with win2000. I change the SCSI id's (one node 6 and the other is 7)

I power on one server and config the shared array and then accomplish the cluster config. When I power on the second node, it freezes on the Windows (black) screen. Disabling its access to the shared drive allows it to boot. I add the second node, then all hades breaks loose. Can't fail or move resources, the servers lock up, the cluster fails, cluster services stop on their own, etc. The common thread seems to be the sym_hi.sys file or driver.

Thanks
Brian_Murdoch
Honored Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

Hi Charles,

Sym_hi.sys is a Symbios Logic SCSI miniport driver however you should not be using any Sybios Logic drivers. This suggests that you may not have applied the Windows 2003 Product Support Pack to use only HP drivers for everything.

Try applying the PSP and see if the problem goes away. Also upgrade the system BIOS on each DL380 node if not already done.

The complete CL380 G1 kits can be found here.

http://h18023.www1.hp.com/support/files/server/us/locate/69_1125.html

I hope this helps.

Brian



Brian_Murdoch
Honored Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

Charles,

Can you also please have a look at the attached "Implementing Microsoft Windows Server 2003 on Proliant Servers" just in case any pre-requisites are not met.

The CL380 is covered.

Its a 280K PDF file.

Regards,

Brian
Ron Caguin
Occasional Visitor

Re: Win Server 2003 Enterprise on CL380 Cluster

I'm having the same problem, but everything is up to date (bios, drivers, controller). I configured both nodes with the system configuration utility exactly the same. When node 1 is up and running, I try to power up node 2 and it hangs on the Windows 2003 splash screen.Any other suggestions?

Thanks,

Ron
Terry Hutchings
Honored Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

Which OS is selected in the system configuration?
The truth is out there, but I forgot the URL..
Ron Caguin
Occasional Visitor

Re: Win Server 2003 Enterprise on CL380 Cluster

I have Windows NT > Windows 2000, selected. If I choose other, either nodes will not boot up to OS. The only way I can get node 2 up when node 1 is operational is by isolating node 2 using the node service button in the back. Node 1 is set to SCSCI ID 7 and Node 2 is set to 6. I did try flipping the two ID's around (digging for answers) and it didn't work. I am getting the sym_hi event. Like I said in my previous post, every bios and firmware on each nodes are up to date. Thanks.

Ron
thiru_1
Occasional Advisor

Re: Win Server 2003 Enterprise on CL380 Cluster

i am having the same exact problem as well.... :-s.. hopefully HP guys could shed some light here...
Doug de Werd
Honored Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

Check out this doc - it applies to both Windows 2000 and 2003.

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_EC000818_CW02

Basically what is happening is that Windows is trying to load a Symbios driver, which is the wrong one. The driver that should be loaded is the HP ProLiant 32-Bit SCSI Controller Driver for Windows 2000/Windows Server 2003 (cpq32fs2.sys) driver.

This can be found at the Support Pack web site at: http://h18023.www1.hp.com/support/files/server/us/locate/69_1125.html

Hope this helps.

Thanks,
Doug
Expert in ProLiant Clusters
thiru_1
Occasional Advisor

Re: Win Server 2003 Enterprise on CL380 Cluster

So, are these the steps to install win2k3 on 2nd node?:
1 Press the button
2 Install Win2k3
3 Install all the right drivers
4 Press the button again
5 Join the cluster?

I just wonder why the problem doesnt exist when we do installation for 1st node as the 1st also supposedly shd have grabbed the wrong drivers, right...?

Doug de Werd
Honored Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

Yes that's basically it. Part of the problem may be if you are trying to install Windows on the second server befiore it fully finishes on the first.

The referenced doc indicates to [push the button on the second server to isolate it from the storage. here's what I would do.

1. install Windows on the first node, with the second node powered off. You should not have to isolate the shared storage. Update the driver, then reboot. Make sure that the cluster service is running and the first node sees all the drives in the sharde storage (via Cluster Admin)

2. Once the first server is running OK. isolate the second server from the shared storage. Then install Windows. Update the driver. Then reboot the server and enable access to the shared storage. Then add it to the cluster (onkly after the new/correct driver has been installed.

Good luck

Doug
Expert in ProLiant Clusters
thiru_1
Occasional Advisor

Re: Win Server 2003 Enterprise on CL380 Cluster

yep...it's all coz of the driver..it worked for me.. thanks to all! esp doug...
Doug de Werd
Honored Contributor

Re: Win Server 2003 Enterprise on CL380 Cluster

no problem

that's what we're here for!

Glad it's up and running.

Doug
Expert in ProLiant Clusters
Ron Caguin
Occasional Visitor

Re: Win Server 2003 Enterprise on CL380 Cluster

After installing the drivers as suggested, I still couldn't get the second node to come up. Someone suggested to power everything down, unplug the power cable, let it sit for a few seconds, and do the power up sequence. It worked, cluster up and running. Puzzled but relieved. Thanks for the help.

Ron
Graeme May
Occasional Visitor

Re: Win Server 2003 Enterprise on CL380 Cluster

On the point of SCSI ID for the two nodes.
I have had trouble configuring the SCSI ID on the 64-Bit Dual Channel Wide Ultra2 SCSI controller. I see Brians note above. When I run SCU (smartstart 5.5) under the 64 bit ultra2 controller I cannot see SCSI ID.
only Host Adapter number and controller order. Can anyone help or explain how to change or interogate the SCSI ID?