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

CL380 CR3500 problems

Brett Tesdall
Occasional Advisor

CL380 CR3500 problems

My company has a CL380 sitting around that we'd like to use to host some virtual servers. We'd like to reconfigure this server so that both nodes run as independent servers, but can simultaneously access specific logical drives set up in the shared storage space. We do NOT want it configured as a cluster.

I've read everything I can about how to connect everything and achieve this. I've upgraded the server BIOS, the RAID BIOS in each node, and the firmware of the CR3500. I've installed Windows Server 2003 R2 Standard on both nodes, and installed the Support Packs and CR3500 Array configuration program.

The problem currently is this: When node 1 is up and running by itself, it can access the shared storage space and all the logical drives set up in it. However, when node 2 is powered up, strange things begin happening. Most of the time, node 1 just loses connection to the CR3500, but sometimes running both nodes will also cause freezes and BSOD's. I have checked the SCSI ID's on the controllers of both nodes that connect to the CR3500, and they are set to 6 and 7 for node 1 and node 2, respectively.

What else am I doing wrong?
14 REPLIES
Andrzej Kowalik
Honored Contributor

Re: CL380 CR3500 problems

Both servers and storage have ONE shared SCSI bus. If both server are running and no cluster service is started, no one know who is owner of shared disks...

regards,
Andrzej Kowalik
Brian_Murdoch
Honored Contributor

Re: CL380 CR3500 problems

Hi Brett,

One of the other things to be aware of is that both nodes may have the SCSI ID of the shared storage adapter in the server set to ID7. If you perform a System Erase or have had the system board on one of the DL380's replaced this is common. One node will boot OK but when the second is booted, all hell breaks loose as there are two initiators on the bus at ID7.

Go into the system config utility (SCU) via F10 or Smartstart on each node and check the SCSI ID of the controller. If both are set to 7 then change one to 6 then you won't have any conflicts.

I have attached an image with this section of the software user guide which explains how to achieve this.

I hope this helps.

Brian
Brian_Murdoch
Honored Contributor

Re: CL380 CR3500 problems

Brett,

I forgot to add that once you have the nodes up and running OK, you will have to use ACU and SELECTIVE STORAGE PRESENTATION (SSP) within ACU to restrict access to the logical drives since you won't be running it as a cluster.

Regards,

Brian
Brett Tesdall
Occasional Advisor

Re: CL380 CR3500 problems

Hello, and thanks for your replies so far. I am going to upgrade our server from Windows Server 2003 R2 Standard to Enterprise to see if configuring it as a cluster will make it work properly.

Regarding the SCSI ID's for the cards that connect the nodes to the CR3500 shared storage, as I stated, I have already changed these to 6 and 7, so there should not be any SCSI bus conflicts. I have node 1 up now and created 2 logical drives on the CR3500 array, but the ACU does not see them. ACU only shows me the array on the on-board SCSI RAID in each server node. How do I get ACU to see the CR3500 array?
Andrzej Kowalik
Honored Contributor

Re: CL380 CR3500 problems

CR3500 is not supported with ACU. This is not Smart Array controller.
You must use CR3500 Configuration Utility.

regards,
Andrzej Kowalik
Brian_Murdoch
Honored Contributor

Re: CL380 CR3500 problems

Hi Brett,

Sorry I didn't read your full initial request so I apologise for ranting on about the SCSI ID's but I've seen this a few times when engineers have replaced system boards at customer sites. Reply back if you can when you have tried the clustered setup.

If the Windows based ACU can't see the CR3500 try the older WIN32 application based ACU.
http://h18023.www1.hp.com/support/files/server/us/download/14185.html

Download it and run it. You can't install it directrly in Server 2003 but you can extract the files (click extract) to a folder C:\CR3500 for example and run CPQACU.EXE from there. It works fine in Windows 2003 and XP too even though it's completely unsupported. Choose the CR3500 from the dropdown box at the top. You'll see the embedded 5i controller as the default but the CR3500 should be there.

I hope this helps.

Brian
Brett Tesdall
Occasional Advisor

Re: CL380 CR3500 problems

OK, this is where I am at now.

I've had to upgrade the nodes to Windows Server 2003, Enterprise Edition because the Standard Edition does not support clustering.

On Node 1, I created a new cluster. It found the logical drives on the CR3500 shared storage array and designated one as a quorum, which is fine. It complained a bit about the network cards being set to DHCP, but it successfully created the cluster. I then powered up node 2 in order to upgrade it, and while node 2 was still booting, the cluster on node 1 went offline, the logical drives on the shared storage disappeared, and trying to open My Computer to view the drives froze. Node 2 never managed to fully boot, getting stuck on the Windows Server 2003 splash screen.

I have now powered down node 1 and in the process of upgrading node 2.

The problem right now seems to be that node 1 and node 2 still cannot access the shared storage simultaneously, which was my problem before upgrading to Enterprise Edition.

Is there still something more that I need to do on node 2 that might get this to finally work? I know I have to try to add it to the cluster, but will that allow the 2 machines to access the shared storage at the same time? Both nodes can see it if the other node is powered down.

Also, this CL380 only has a single CR3500. Could the problem of the nodes freezing up each other be due to a defective CR3500 unit? Or do I need to purchase a second CR3500?

Lastly, I downloaded the Win32 ACU utility, and it still is only showing the integrated smart array in the node. The CR3500 is not in the drop-down and I can find no way to make it see the CR3500.

Any help is appreciated!
Brian_Murdoch
Honored Contributor

Re: CL380 CR3500 problems

Brett,

Have a look at the attached pdf which details all the SCSI device ID views for the CL380 storage with single and dual controllers installed.

When you set up the internal adapters, are both ports of each Compaq 64-bit dual channel adapter set to either 6 or 7? I.E on node 1 are both SCSI ports set to 7 and for node 2 are both SCSI ports set to 6?

What's happening still sounds like a SCSI conflict.

Brian
Brian_Murdoch
Honored Contributor

Re: CL380 CR3500 problems

The following CL380 docuemntation link might also help.

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?〈=en&cc=us&contentType=SupportManual&docIndexId=179166&prodTypeId=15351&prodSeriesId=254845〈=en&cc=us

Brian
Brett Tesdall
Occasional Advisor

Re: CL380 CR3500 problems

I tend to agree that the symptoms point to a SCSI ID conflict in the nodes, however, I can't find a conflict. The document you pointed me to says that as long as the SCSI ID's are set in one node to 6 and the other to 7, then SCSI conflicts are impossible, yet it appears to be happening.

I went into the System Setup of each node in the CL380 and looked at the settings for the Ultra2 SCSI controller that attaches to the CR3500. I have transcribed what is on each:

Node 1:

Slot 2 - Compaq 64-Bit Dual Channel Wide Ultra2 SCSI Controller (Port 1)
SCSI Resources: ENABLED
Controller Order: Third
Host Adapter Number: 1
SCSI ID: #6
Bus Speed: Auto-detection

Attached Devices:
SCSI ID 2.....Compaq CR3500 Reserved Device
SCSI ID 3.....Compaq CR3500 Reserved Device

Slot 2 - Compaq 64-Bit Dual Channel Wide Ultra2 SCSI Controller (Port 2)
SCSI Resources: ENABLED
Controller Order: Fourth
Host Adapter Number: 2
SCSI ID: #6
Bus Speed: Auto-detection


Node 2:

Slot 2 - Compaq 64-Bit Dual Channel Wide Ultra2 SCSI Controller (Port 1)
SCSI Resources: ENABLED
Controller Order: Third
Host Adapter Number: 0
SCSI ID: #7
Bus Speed: Auto-detection

Attached devices
SCSI ID 2.....Compaq CR3500 Reserved Device
SCSI ID 3.....Compaq CR3500 Reserved Device

Slot 2 - Compaq 64-Bit Dual Channel Wide Ultra2 SCSI Controller (Port 1)
SCSI Resources: ENABLED
Controller Order: Fourth
Host Adapter Number: 1
SCSI ID: #7
Bus Speed: Auto-detection




If there is a problem somewhere, it would seem that it must be here somewhere, but I can't see where the problem lies.

Could the CR3500 be defective or faulty somehow?
Brett Tesdall
Occasional Advisor

Re: CL380 CR3500 problems

I may have found the problem.

I reinstalled the driver for the Ultra2 SCSI card using the driver on the CL380 software page. Up to this point it has been using the MIcrosoft-supplied driver that was automatically installed. Once I replaced the driver with the Compaq one, the conflicts disappeared and I was able to access the CR3500 with the Array Config Utility from both nodes at the same time, which up to this point was not possible--one of the nodes would be knocked off by the other.

The issue I have now is some strange drive mappings on the shared storage array. However, now that I have potentially found the problem, I'm going to blow away the shared storage logical drives and re-install with Windows Server 2003 Standard, without the clustering, and see if I can achieve the desired configuration we want with this server.

I am definitely a step closer! Will assign points if/when I can get this working properly--probably tomorrow or Monday. Otherwise, I'll be back...
Brett Tesdall
Occasional Advisor

Re: CL380 CR3500 problems

I tried the Compaq drivers and that did allow both machines to access the shared storage array. However, I could not get the two machines to not fight over the logical drives I created. If I wrote a file to the same logical drive from both nodes, each node would only be able to see the files it created, and when a node was rebooted, the machine would think the drive was corrupt and rebuild the file tables and only show the files the other node wrote. I tried to install Windows 2003 Standard and Enterprise Edition with Clustering, and could not get it to properly cluster. When I tried it with a fresh install of Enterprise and tried to make the cluster, the Quorum drive on the first node became corrupt and unusable, thus preventing it from forming a proper cluster.

Thanks for all the help, but I don't know what else to try on this thing, except maybe backing back down to Windows 2000 Advanced Server, although we really wanted to use 2003 Server on this. I've assigned points. Thanks.
Brett Tesdall
Occasional Advisor

Re: CL380 CR3500 problems

Was able to resolve the SCSI conflicts, but could not get it to properly cluster with Windows 2003 Server, Standard or Enterprise Edition.
Jeff Vincent
Occasional Visitor

Re: CL380 CR3500 problems

I just found this thread after recently starting something very similar. We also had a CL380 sitting around and want to use it as a central file repository.

I installed SUSE 10.0 on node 1 and got it working. It can see the shared logical drive. If I power up node 2, it deactivates.

I installed Win2K3 on node 2 with the latest drivers to see if running a supported OS would help. It can also see the logical drive as long as node 1 is off. If I turn on node 1, it hangs loading the SCSI driver with continuous "Bus Reset" messages until I power off node 2.

Can I ask how you solved the SCSI ID conflict? I'm sure I am missing an important piece of the puzzle, I am just not familiar with clustering or this hardware. I did what you tried, by setting the SCSI ID of the Node 1 controllers to #6 and the ID for node 2 controllers to #7, but still have the same problems.

Thanks for any additional information you can provide.