You wouldnt have read this far if you werent up for the challenge, right.In this part, we will look at adding the iSCSI disks to the servers.
Windows Server 2008 Failover Cluster Series Of StepsThe series of steps outlined below should be done on both nodes.This second NIC will be considered your heartbeat, where communication between nodes will travel.
How these cards are configured will come into the picture as we go along in the process. Windows Server 2008 Failover Cluster Install This SoftwareWindows Server 2008 Failover Cluster Software Prior ToThis differs from previous versions of Microsoft Windows where you need to download and install this software prior to connecting to an iSCSI storage. You can launch the tool from Administrative Tools and select iSCSI Initiator. If you are hosting the target on another Windows host, make sure that you have your Windows Firewall configured to enable inbound traffic to port 3260. You should see a list of the iSCSI Targets that we have defined in Part 1 of this series. Repeat this process for all the target disks we initially created. I wont go into much detail on this process as it is similar to how we used to do it in Windows Server 2003, except for the new management console. After the disks have been initialized and volumes created, you can try logging in to the other server and verify that you can see the disks there as well. This completes the installation of the Failover Clustering feature on the first node. One word of caution: do not skip any error message that this wizard generates in the final report. This will run all the necessary tests to check the servers that will be a part lof the cluster. Further runs can be selective tests as long as you know what you are testing. This would be appropriate when adding new hardware such as network cards or disks to the existing cluster. Click on the View Report button to see a detailed report that was generated by the wizard. In fact, I expect you to have errors, as most of the installations Ive done werent successful, thanks to a known issue. You will see an error in the Summary Report similar to the one displayed below. Found duplicate IP address fe80::100:7f:fffe13 on node node1.domain.local adapter Local Area Connection X and node node2.domain.local adapter Local Area Connection X. In my case, however, I needed to do steps 3 to 5 before I got a successful summary report generated by the Validate Cluster Configuration wizard. In the third part of this series, we will walk through the process of creating the cluster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |