Multiple subnets and clustering (DCOM Client/Server app)
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Multiple subnets and clustering (DCOM Client/Server app)

 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering
Author Message
Oliver
Guest
Posted: Mon Jan 10, 2005 2:15 am    Post subject: Multiple subnets and clustering (DCOM Client/Server app) Reply with quote
Hello people!
Im quite new to clustering and i have a question.
The project im working on requires a "lot" of redundancy. Im using MSCS to
add redundancy support to my client/server application. I have developped a
resource dll to communicate with my server app and all is working fine.
The two nodes on my cluster are equipped with two NIC (both configured for
private and public communication) that are used on two different subnet (for
redudancy!). This way if a subnet fails the other is used to communicate with
my server application. Client PCs are connected to both subnets.

What i would like to do is use a the same Network Name (Using virtual
servers in my cluster configuration) to connect to the server application
with clients application. My configuration looks like this

Resource: IP1
Param : 10.1.10.1
Resource type : Network Name
Param : SERVER
Depends on : IP1

Resource : IP2
Param : 10.5.10.1
Resource type : Network Name
Param : SERVER
Depends on : IP2

This way the client app (connected to both subnets) uses the network name
SERVER to connect to the server and then uses whatever subnet is currently up
and running (I think DCOM will handle this ?)...

But this is not working... Both network names cannot be brought online on
MSCS. I get the error "Duplicate names exist on the network" even if the
names are on two different subnet...

Will i have to use NLB or DNS round robin to get around this problem ? Maybe
it is impossible to do ?

Thanks in advance
Any help would be greatly appreciated!!
Back to top
Russ Kaufmann [MCT]
Guest
Posted: Tue Jan 11, 2005 12:23 am    Post subject: Re: Multiple subnets and clustering (DCOM Client/Server app) Reply with quote
"Oliver" <Oliver@discussions.microsoft.com> wrote in message
news:F38E8AC0-8CF9-4BCB-8D0E-D95559B345E6@microsoft.com...
Quote:
Hello people!
Im quite new to clustering and i have a question.
The project im working on requires a "lot" of redundancy. Im using MSCS to
add redundancy support to my client/server application. I have developped
a
resource dll to communicate with my server app and all is working fine.
The two nodes on my cluster are equipped with two NIC (both configured for
private and public communication) that are used on two different subnet
(for
redudancy!). This way if a subnet fails the other is used to communicate
with
my server application. Client PCs are connected to both subnets.

What i would like to do is use a the same Network Name (Using virtual
servers in my cluster configuration) to connect to the server application
with clients application. My configuration looks like this

Resource: IP1
Param : 10.1.10.1
Resource type : Network Name
Param : SERVER
Depends on : IP1

Resource : IP2
Param : 10.5.10.1
Resource type : Network Name
Param : SERVER
Depends on : IP2

This way the client app (connected to both subnets) uses the network name
SERVER to connect to the server and then uses whatever subnet is currently
up
and running (I think DCOM will handle this ?)...

But this is not working... Both network names cannot be brought online on
MSCS. I get the error "Duplicate names exist on the network" even if the
names are on two different subnet...

Will i have to use NLB or DNS round robin to get around this problem ?
Maybe
it is impossible to do ?

The issue appears to be that you have both NICs configured for both private
adn public access. Your heartbeat network, in general, should be configured
for private only and then your public configured for both public and private
so that if the heartbeat network dies, the cluster can still pass the
heartbeat over the public network. Change your intended heartbeat network to
private only and then disable the DNS check box so it doesn't try to
register with DNS and then also disable NetBIOS on it.
Back to top
Oliver
Guest
Posted: Tue Jan 11, 2005 7:55 am    Post subject: Re: Multiple subnets and clustering (DCOM Client/Server app) Reply with quote
If if do this ill have to add a NIC for private heartbeat only...

Ill try it tomorow and give you feedback if it worked!

Thanks for your help!


"Russ Kaufmann [MCT]" wrote:

Quote:
"Oliver" <Oliver@discussions.microsoft.com> wrote in message
news:F38E8AC0-8CF9-4BCB-8D0E-D95559B345E6@microsoft.com...
Hello people!
Im quite new to clustering and i have a question.
The project im working on requires a "lot" of redundancy. Im using MSCS to
add redundancy support to my client/server application. I have developped
a
resource dll to communicate with my server app and all is working fine.
The two nodes on my cluster are equipped with two NIC (both configured for
private and public communication) that are used on two different subnet
(for
redudancy!). This way if a subnet fails the other is used to communicate
with
my server application. Client PCs are connected to both subnets.

What i would like to do is use a the same Network Name (Using virtual
servers in my cluster configuration) to connect to the server application
with clients application. My configuration looks like this

Resource: IP1
Param : 10.1.10.1
Resource type : Network Name
Param : SERVER
Depends on : IP1

Resource : IP2
Param : 10.5.10.1
Resource type : Network Name
Param : SERVER
Depends on : IP2

This way the client app (connected to both subnets) uses the network name
SERVER to connect to the server and then uses whatever subnet is currently
up
and running (I think DCOM will handle this ?)...

But this is not working... Both network names cannot be brought online on
MSCS. I get the error "Duplicate names exist on the network" even if the
names are on two different subnet...

Will i have to use NLB or DNS round robin to get around this problem ?
Maybe
it is impossible to do ?

The issue appears to be that you have both NICs configured for both private
adn public access. Your heartbeat network, in general, should be configured
for private only and then your public configured for both public and private
so that if the heartbeat network dies, the cluster can still pass the
heartbeat over the public network. Change your intended heartbeat network to
private only and then disable the DNS check box so it doesn't try to
register with DNS and then also disable NetBIOS on it.


Back to top
Russ Kaufmann [MCT]
Guest
Posted: Wed Jan 12, 2005 6:42 am    Post subject: Re: Multiple subnets and clustering (DCOM Client/Server app) Reply with quote
"Oliver" <Oliver@discussions.microsoft.com> wrote in message
news:C144F9C4-B49A-4E70-B5F8-0F51C5D8DE16@microsoft.com...
Quote:
If if do this ill have to add a NIC for private heartbeat only...

Ill try it tomorow and give you feedback if it worked!

I strongly suggest reading on the recommended heartbeat config here
http://support.microsoft.com/?id=258750

You might want to do a little reading on the behavior and configuration with
multiple NICs as well.
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q175/7/67.asp&NoWebContent=1

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q176/3/20.ASP&NoWebContent=1

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q242/6/00.asp&NoWebContent=1
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB