Clustering Highlights From the Blogs of Rod and Russ

Archives

January 2005 | February 2005 | March 2005 | May 2005 | June 2005 | July 2005 | August 2005 | September 2005 | October 2005 | January 2006 | February 2006

 

New Cluster Info - Russ Kaufmann

I was at the MVP summit last week and as part of the summit, we spent several hours with the cluster team and learned all about some of the really fun new stuff.

Sorry, I can't share. I just wanted to tease everyone. :)

One item that I can share, it is clear to me that anyone out there that is using DHCP to assign IP addresses to your cluster nodes should be spanked by a large hairy and sweaty man.

DHCP, in my opinion, should never be used to distribute IP addresses to cluster nodes. Never. Write it down, never. For anyone that does this, please go back to page 1 in the high availability class and note that it is a very bad thing to build dependencies to other processes that can cause failures of your highly available applications. If you can avoid such a dependency, you should.

Thus, don't use DHCP to assign IP addresses to your cluster nodes. I don't care if it is being done through reservations, it is still a bad thing.

OK, now I am off my soap box.

How-To: Configure Network Load Balancing (NLB) with Two Network Adapters - Rodney R. Fournier

1. Assign appropriate IP addresses to each NIC, placing the NICs in separate
subnets. Rename the first NIC “Public“ and the second to “NLB“, do this for each machine.

* Node1 -

o "Public" NIC
* IP address: 10.10.10.11
* Subnet: 255.255.255.0
* Gateway: 10.10.10.1
* DNS: as appropriate

o "NLB" NIC
* IP address: 192.168.1.1
* Subnet: 255.255.255.0
* Gateway: N/A
* DNS: N/A


* Node2 -

o "Public" NIC
* IP address: 10.10.10.12
* Subnet: 255.255.255.0
* Gateway: 10.10.10.1
* DNS: as appropriate

o "NLB" NIC
* IP address: 192.168.1.2
* Subnet: 255.255.255.0
* Gateway: N/A
* DNS: N/A

2. On the "Public" NICs, click "Advanced" and add an additional IP address
as the Virtual IP Address which clients will connect to from the Public
network (i.e. - 10.10.10.169)

3. Install "Network Load Balancing" as an additional service from the
"Public" adapter properties.
* Click "Install.." and then select "Service" in the upper-window and
click "Add."
* Select "Network Load Balancing" in the upper-window and click "OK"
* Answer any prompts and provide the correct path to installation media (Windows 2000 installs only).

4. Once NLB is installed, return to the Properties page for the "Public"
NIC and select the check-box next to "Network Load Balancing."  This
enables the service globally.

5. Next, select the item "Network Load Balancing" and click "Properties"

6. Configure the NLB Cluster properties according to your parameters,
using the following example steps as a guide.

* Node1 -

o "Public" NLB Cluster Parameters tab
* Primary IP address: 10.10.10.169
* Subnet: 255.255.255.0
* Full Internet Name mail.clusterhelp.com

o "Public" NLB Host Parameters tab
* Priority: 1
* Dedicated IP address: 10.10.10.11
* Subnet: 255.255.255.0


* Node2 -

o "Public" NLB Cluster Parameters tab
* Primary IP address: 10.10.10.169
* Subnet: 255.255.255.0
* Full Internet Name mail.clusterhelp.com

o "Public" NLB Host Parameters tab
* Priority: 2
* Dedicated IP address: 10.10.10.12
* Subnet: 255.255.255.0

7. MultiCast support can be optional in this configuration, though I would not recommend it.

8. You can also now take time to create a static Host record (A record) in
your scenario's DNS infrastructure to provide appropriate name resolution
to the NLB cluster name (i.e. - mail.clusterhelp.com or just mail).

9. Your NLB cluster should be up and running after the nodes converge.

10. An external client should now be able to ping the IP address of the
NLB cluster (i.e. - 10.10.10.169) as well as each of the individual node
addresses (i.e. - 10.10.10.11 & 10.10.10.12).

11. Many good diagnostic commands can be found by typing "wlbs /?" in a
command window.  For example, "wlbs query" shows the status and
convergence state of the cluster. If you are running Windows Server 2003 (any version expect SBS) you can use the graphical Network Load Balancing Manager - I love this tool.

12. IMPORTANT NOTE: In this configuration, each individual node is NOT
able to ping the other node's Public physical IP address (i.e - 10.10.10.11
cannot ping 10.10.10.12 and vice-versa).  I believe this is expected
behavior, as the NLB cluster is now responding to requests on the Virtual
Cluster address (i.e. - 10.10.10.169).

Written by Ryan Sokolowski (blogged with permission) - with minor changes and tweaks

 

GeoClustering - How You Can Achieve Greater Availability with Failover Clustering Across Multiple Sites - Rodney R. Fournier

Just recorded -

TechNet Webcast: How You Can Achieve Greater Availability with Failover Clustering Across Multiple Sites (Level 300)

http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?culture=en-US&EventID=1032282061&CountryCode=US

This is yet another (http://msmvps.com/clustering/archive/2005/06/27/56143.aspx) excellent webcast from the master himself - Elden Christensen. This is a great free resource to learn everything you ever wanted to know about Geographically Dispersed Clusters.

The strange part is not that you learn a lot from Elden. Not that you get a glimpse of what LongHorn Server may have in store for us. Not the excellent presentation skills of Elden throughout this 68 minutes presentation. The strange part is that the slides and graphics are stunning, simply the best I have ever seen. Oh sure, you will learn something and enjoy the content, but it’s also visually entertaining.

Excellent job Elden, keep them coming buddy!

 

Installing a new SQL instance into an existing cluster on a new Node - Rodney R. Fournier

We added a node to one of our clusters. We confirmed that the hardware, firmware, bios, OS, and installed programs were exactly alike. The new machine joined the cluster like a champ, no issues.

When I went to install SQL and create a new instance, I was hit with this error:

The cluster resource failed to come online. If extended error information was reported by the clustering service it can be obtained from the event log.

It turns out this is a known issue. From http://support.microsoft.com/default.aspx?scid=kb;en-us;815431 “To run SQL Server on Windows Server 2003, you must have SQL Server 2000 Service Pack 3 (SP3) installed. Windows Server 2003 blocks TCP/IP functionality for named instances that are not running SQL Server 2000 SP3 or later. “

This will only happen when a named instance is added to a new cluster node.

The fix is really easy, follow the articles steps to install the client utilities and create a SQL Service Alias in the SQL Server Client Network Utility .

 

Should Clustered services be set to 'manual' or 'automatic'? - Rodney R. Fournier

The question goes something like this:

My cluster is installed and running SQL/Exchange nicely but I noticed that all the services for SQL/Exchange are set to start manaully. Should I set the services to automatic instead?

Answer:

Cluster controlled services should always be set to manual, so that the
cluster can control the startup and shutdown. Remember with Microsoft
clustering only one server can control a resource at any given time. Leaving
the services set to manual will help the cluster service do it's job and
ensure an error feel service :)

 

Small Business Server (SBS) Clustering - Rodney R. Fournier

 I get this question from time to time:

“Does Windows 2003 Small Business Server support clustering and if not would you suggest a 3rd party clustering solution.  The only catch I see is the SBS feature of not letting any other SBS servers in the same domain.”

Let me answer these questions with the facts:

1) You can add servers to an SBS domain. You can't not add another SBS Domain Controller (though a standard DC can be added), but a server running Exchange or SQL is allowed and works nicely.

2) You can't have another SBS server into the domain, only one SBS server is supported per domain/tree/forest. It must also own the FSMO roles for the forest.

3) SBS does not support Clustering. Never has and probably never will.

4) I do not know of any third party solutions that would work with SBS and be supported by the vendor or Microsoft.

Yes, oddly enough I am SBS certified (71-282 exam - http://www.microsoft.com/learning/exams/70-282.asp). I was invited to take the beta exam and passed.