<div>
Fantastic, I completely overlooked setting the initiator back to 7.
</div>


Fantastic, I completely overlooked setting the initiator back to 7.

<div>
<div class="content wysiwyg-content">
I have built a cluster using:<br />
<br />
2 x IBM X345<br />
2 x ServeRAID 6M cards<br />
Windows 2003 Enterprise<br />
Firmware - 7.12.07<br />
BIOS - 7.12.07<br />
Driver - 7.10.18<br />
ServerRAID Manager - 7.10.18<br />
<br />
We recently had the 6M card in the secondary cluster node fail. After replacing the card and bringing all the BIOS and Firmware up to sync with the primary node's card. I loaded up the mini config during boot and copied the configuration from the drives to the new SCSI card. Upon booting the secondary node it takes control of the RAID arrays causing all the drives to show as defunct.<br />
<br />
What is the proper procedure for bringing this second node back online without disrupting the cluster?
</div>
</div>


I have built a cluster using:

2 x IBM X345
2 x ServeRAID 6M cards
Windows 2003 Enterprise
Firmware - 7.12.07
BIOS - 7.12.07
Driver - 7.10.18
ServerRAID Manager - 7.10.18

We recently had the 6M card in the secondary cluster node fail. After replacing the card and bringing all the BIOS and Firmware up to sync with the primary node's card. I loaded up the mini config during boot and copied the configuration from the drives to the new SCSI card. Upon booting the secondary node it takes control of the RAID arrays causing all the drives to show as defunct.

What is the proper procedure for bringing this second node back online without disrupting the cluster?

Replacing SCSI card in Microsoft Failover cluster IBM hardware

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.