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

Cluster problem

Go to solution
Occasional Advisor

Cluster problem

Hello Folks,
We are having difficulty finding the drivers for CR3500 for W2K. We have a PL1850R. Controller sees the drives but no access to data. Changed the controller but still no luck with the data. Probably missing drivers which we could not find. Any help would be appreciated.
Sunil Jerath
Honored Contributor

Re: Cluster problem

You need to do the following:
if the Found New Hardware Wizard appears for the CR3500 SCSI Array Device,

1. Select "Next".

2. Choose "Display a list of known drivers for this device so that
I can choose a specific driver".

3. Select "Other Devices".

4. Select "Unknown" under Manufacturers and select "Unsupported
Devices" under Model.

5. Select "Finish".
This is happening due to the Plug & Play support in W2k.


Sunil Jerath
Honored Contributor

Re: Cluster problem

Hello Scorpio,
Some cluster problems are caused by hardware, such as the server nodes, the communication cards, fibre channel or SCSI interconnect hardware, or the shared storage. A large number of problems, however, are caused by corrupted or misconfigured cluster services.


To check if the issue is being caused by hardware, perform the following steps:

Check Insight Manager to see if there is any prefailure warnings or Integrated Management Log entries. If no Insight Manager console is installed, attempt to access the Compaq Web Based Agents at http://ipaddress:2301.
Check the Event Viewer logs for messages relating to hardware. The Compaq Management Agents may still log errors to the Event Logs even if the Web Agent is not accessible. Sometimes, these log entries may be even more descriptive than the Integrated Management Log equivalent.
Check for LEDs indicating an error condition on GBICs, hubs, switches, raid arrays, etc. Many are documented in Cybrary.
Use diagnotics tools such as the Array Diagnostics Utility (RA4000, RA4100, Smart Array Clustered Storage) and the Smartstart Fibre Channel Array Diagnostics Utility. Note: some utilities such as ADU are not clusterable, so only one node can access the shared storage at the time the utility is running.
Once traditional, unintrusive troubleshooting has been exhausted, consider isolating the cluster service from the problem by disabling the cluster service.
Shut down to other node to prevent it from attempting to take over the shared resources, such as shared storage.
On the first node, go into the Device Manager. Device Manager is accessible from Computer Management, under Administrative Tools. From the View menu, select Show Hidden Devices. Additional categories in the Device Manager will become visible.
The category Non-Plug and Play Drivers will be represented by a grey square. In this category, you will find the Cluster Disk device. Double click on it. Click on the Drivers tab. Next to Startup Behavior, select Demand.
Save the changes and exit Computer Management.
Next, access the Services applet, also under Administrative Tools. Double click on Cluster Service. Select Manual as the Startup Type.
Save the changes and exit the Services applet.
Restart Windows.
If the problem goes away, or changes in such a way that it is evident it is a software based issue, then the problem was most likely related to cluster services or one of it's dependencies. For example, previously inaccessible shared storage might become accessible without cluster services active.
You might want to look at the following as well:
Cluster Service Startup Options

Occasional Advisor

Re: Cluster problem

Thank you Sunil for loads of amazing information. You were bang on and we were able to resolve the issue by following your advice. Once again thanks for the quick response. All the best.