I have a problem with PERC 3/DC Controllers not saving their configuration correctly in a clustered configuration.

>>>Configuration <<<

Server1:

Dell 2650, PERC 3/Di with 2 x 36Gb configured as Raid-1 with Windows 2003 installed. Also installed is a PERC 3/DC (SCSI ID 6) which has Ch-0 connected to Array-A PowerVault 210 (EMM0) and Ch-1 connected to Array-B PowerVault 210 (EMM1).

Server2:

Dell 2650, PERC 3/Di with 2 x 36Gb configured as Raid-1 with Windows 2003 installed. Also installed is a PERC 3/DC (SCSI ID 7) which has Ch-0 connected to Array-B PowerVault 210 (EMM0) and Ch-1 connected to Array-A PowerVault 210 (EMM1).

Both PowerVault 210’s:

Fully populated with the same a mix of disks, i.e. 0:0 (9GB Disk), 1:0 (9GB Disk), 0:1 (18GB Disk), 1:1 (18GB Disk), etc, etc.

>>>Firmware Versions <<<

Dell 2650 BIOS A20, ESM 3.20, Backplane 1.01

PERC 3/Di, v2.8-0 Build 6092

PERC 3/DC, v3.35 FW 1970

>>>Problem <<<

When I create a PERC 3/DC configuration on either server (e.g. Mirror 0:0 to 1:0), when I start the other server the configuration is recognised by the other PERC 3/DC, but always stops during the start-up with the message [Press to Run Configuration Utility or any other Key to Continue]. If I press or any other key, it makes no difference. The server that didn’t create the original configure always stops at this point.

I assume this is because the disk configuration is different to that in the NVRAM of the controller, but I can find a way to force the controller to update it NVRAM based on the disk configuration.

This problem occurs regardless of which server configures the disks; the other server always stops with this message.

This problem also occurs regardless of whether the other server is power on or off during the disk configuration process.

Hopefully, someone might be able to tell me why this is happening and how I can fix it.

Regards,Vince