FOTC
asked on
Clustering Problems PLEASE HELP!
First of all, if i could offer more points, I would....sorry
I've spent a long time trying to figure this out...
We are trying to cluster two Server 2003 machines, which will eventually be clustered SQL server(s).
As of now, our domain looks like this:
PDC/BDC: Windows 2000 Adv. Server SP4
Almost all workstations are 2000 Pro (roughly 30); about 5 are XP Pro.
We got new IBM servers and have been trying to get them clustered for some times now. I think i have gone through every step available on the internet to get these configured correctly. I did a fresh install of Server 03 yesterday, both machines are matched to the T in hardware and software.
Every time I try to cluster them I get the error:
"A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster."
I've gone through the DNS servers to make sure there was nothing at all in there. I have flushed it, scavenged it, and cleared the cache, stopped it and started it.
I'm out of options, Google and M$ has provided me with good help but nothing that worked.
any other suggestions?
I've spent a long time trying to figure this out...
We are trying to cluster two Server 2003 machines, which will eventually be clustered SQL server(s).
As of now, our domain looks like this:
PDC/BDC: Windows 2000 Adv. Server SP4
Almost all workstations are 2000 Pro (roughly 30); about 5 are XP Pro.
We got new IBM servers and have been trying to get them clustered for some times now. I think i have gone through every step available on the internet to get these configured correctly. I did a fresh install of Server 03 yesterday, both machines are matched to the T in hardware and software.
Every time I try to cluster them I get the error:
"A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster."
I've gone through the DNS servers to make sure there was nothing at all in there. I have flushed it, scavenged it, and cleared the cache, stopped it and started it.
I'm out of options, Google and M$ has provided me with good help but nothing that worked.
any other suggestions?
ASKER
"-Look through your AD and make sure there is no pre-existing computer account with the same name as the name you are trying to name your cluster."
when you say pre-existing PC account, when i join the server to the domain it makes the account. After i reloaded both machines, i did make sure to delete the existing accounts out of the AD before i rejoined them.
when i ping the name ZEUS it resloves to the private NIC (192.168.0.6) the public ip is set for 1.1.1.1 (using crossover cable)
WINS is not in use
I havent tried different names because it has to be a name of a computer which is going to be in the cluster.
The two computers I want to cluster are ZEUS & APOLLO
So, if i'm on ZEUS and try to cluster, I go to Cluster Admin > Create new Cluster > Next
Domain: my-domain.com
Cluster Name: ZEUS
Computer Name: ZEUS
I get the name already in use error after that.
I've tried using the name APOLLO for the computer name and it will get even further in the clustering process, but it will eventually show the name already in use error.
when you say pre-existing PC account, when i join the server to the domain it makes the account. After i reloaded both machines, i did make sure to delete the existing accounts out of the AD before i rejoined them.
when i ping the name ZEUS it resloves to the private NIC (192.168.0.6) the public ip is set for 1.1.1.1 (using crossover cable)
WINS is not in use
I havent tried different names because it has to be a name of a computer which is going to be in the cluster.
The two computers I want to cluster are ZEUS & APOLLO
So, if i'm on ZEUS and try to cluster, I go to Cluster Admin > Create new Cluster > Next
Domain: my-domain.com
Cluster Name: ZEUS
Computer Name: ZEUS
I get the name already in use error after that.
I've tried using the name APOLLO for the computer name and it will get even further in the clustering process, but it will eventually show the name already in use error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok well that seemed to get me past the first two parts, but it error'd out at "Checking Node feasibility"
"this computer cannot be made a member of a cluster"
"this computer cannot be made a member of a cluster because is not have the correct version of windows installed."
I'm using Server 2003 R2 x64...Standard
"this computer cannot be made a member of a cluster"
"this computer cannot be made a member of a cluster because is not have the correct version of windows installed."
I'm using Server 2003 R2 x64...Standard
You need Enterprise OS to do Server Clustering
ASKER
do i need the compute cluster pack?
See this:
http://www.microsoft.com/technet/windowsserver/evaluate/features/compare.mspx
specifically the heading: clustering (under the 64 bit section.)
http://www.microsoft.com/technet/windowsserver/evaluate/features/compare.mspx
specifically the heading: clustering (under the 64 bit section.)
ASKER
aww no!! lol i thought standard OS supported two node clustering...
Compute clusters is something else where it will divide tasks to different computers. Great for large calculations.
You need 2003 enterprise to do Server clusters, which is what you want if you want to cluster SQL.
You need 2003 enterprise to do Server clusters, which is what you want if you want to cluster SQL.
ASKER
ok well thank you so much for all your help. I can't thank you enough!!
When you get the enterprise OS it should work like a charm.
A few things to note.
Generally when you first setup a cluster, you setup the Administration cluster group. This is the group that will contain a Network Name, and IP address and a Physical disk (your quorum).
When you setup SQL, SQL will want to create another cluster group (SQL does this for you) for each instance of SQL. It will require a different Network Name, IP address and Physical Disk (plus the SQL services)
It is also best practice to place the Microsoft Distributed Transaction Coordinator (msdtc) in its own cluster group as well. So this too will require a different Network Name, IP address and Physical Disk (plus the MSDTC service).
So you will need to carve up at least 3 separate LUNs for your cluster. One for the quorum, one for msdtc and at least one for SQL. We typically use 3 disks for SQL (database, logs, and backup).
You will need 5 separate IP address. One for each physical node, one for the Admin Cluster group, one for MSDTC and one for SQL.
You will require 5 different network names as well. I think you can see the pattern.
Considering the main purpose of this server is SQL, make sure you pick the name you want for the SQL cluster group. The other two names are used by admins or SQL and don't need to be too user friendly.
A few things to note.
Generally when you first setup a cluster, you setup the Administration cluster group. This is the group that will contain a Network Name, and IP address and a Physical disk (your quorum).
When you setup SQL, SQL will want to create another cluster group (SQL does this for you) for each instance of SQL. It will require a different Network Name, IP address and Physical Disk (plus the SQL services)
It is also best practice to place the Microsoft Distributed Transaction Coordinator (msdtc) in its own cluster group as well. So this too will require a different Network Name, IP address and Physical Disk (plus the MSDTC service).
So you will need to carve up at least 3 separate LUNs for your cluster. One for the quorum, one for msdtc and at least one for SQL. We typically use 3 disks for SQL (database, logs, and backup).
You will need 5 separate IP address. One for each physical node, one for the Admin Cluster group, one for MSDTC and one for SQL.
You will require 5 different network names as well. I think you can see the pattern.
Considering the main purpose of this server is SQL, make sure you pick the name you want for the SQL cluster group. The other two names are used by admins or SQL and don't need to be too user friendly.
-Look through your AD and make sure there is no pre-existing computer account with the same name as the name you are trying to name your cluster.
-You've mentioned you looked through DNS and it's clean. What happens if you try and ping the name you want to cluster? Does it resolve to an IP address?
-If you have WINS check that as well.
-Have you tried different cluster names?