| Author |
Message |
Rob
Guest
|
 Posted:
Fri Oct 28, 2005 8:50 pm Post subject:
Cluster Nodes using Primary IP address - not Virtual IP when |
|
|
Hello all,
I am looking for any new information on a situation I have observed with
MSCS. Is there any news from MS on fixes to MSCS or perhaps a workaround to
have a cluster virtual server actually use its virtual IP address for both
sending and receiving TCP/IP traffic?
TIA,
Rob |
|
| Back to top |
|
 |
Rob
Guest
|
| Posted:
Fri Oct 28, 2005 8:50 pm Post subject:
Re: Cluster Nodes using Primary IP address - not Virtual IP |
|
|
Thanks Russ - I was aware of this limitation but reading Rod's story
reminded me of my own similar situation with a customer's firewall admin. I
guess I have 2 points and would love to get into the nitty-gritty details of
this situation. Rod states that the VIP is not a real network interface
which I am interpreting as that its not the primary IP on the LAN adapter.
This situation seems to be more of a limitation of the Windows OS than of
MSCS. A cluster virtual server is just a set of software processes running
on a Windows system. What would have to happen is to be able to associate a
particular set of processes with a specific secondary IP address (or VIP)
assigned to a LAN adapter. If this association was possible, whenever these
processes sent information via the network they would have their own IP
(VIP) to send from. As it stands now the processes just hand off the
network traffic to Windows which sends it out the primary IP.
I think of what VMWare does (and maybe Virt Server too) with virtualizing
network adapters so I know it can be done. Of couse VMWare actually creates
its own network adapter definition for Windows. Maybe if Virtual Server and
MSCS virtualization concepts and technologies merge then we could have this.
Just some crazy thoughts.. :)
Rob
"Russ Kaufmann [MVP]" <russ@clusterhelp.com> wrote in message
news:ujVXKz%232FHA.3732@TK2MSFTNGP15.phx.gbl...
| Quote: | "Rob" <Rob@nospam.com> wrote in message
news:%23frcib%232FHA.3020@TK2MSFTNGP15.phx.gbl...
Hello all,
I am looking for any new information on a situation I have observed with
MSCS. Is there any news from MS on fixes to MSCS or perhaps a workaround
to have a cluster virtual server actually use its virtual IP address for
both sending and receiving TCP/IP traffic?
This is by design.
Rod discusses it here:
http://msmvps.com/clustering/archive/2005/08/11/62372.aspx
--
Russ Kaufmann
MVP - Windows Server - Clustering
http://www.clusterhelp.com - Cluster Website
http://msmvps.com/clusterhelp - Blog
|
|
|
| Back to top |
|
|
Russ Kaufmann [MVP]
Guest
|
| Posted:
Fri Oct 28, 2005 8:50 pm Post subject:
Re: Cluster Nodes using Primary IP address - not Virtual IP |
|
|
"Rob" <Rob@nospam.com> wrote in message
news:ueRyg%23%232FHA.320@TK2MSFTNGP10.phx.gbl...
| Quote: | Thanks Russ - I was aware of this limitation but reading Rod's story
reminded me of my own similar situation with a customer's firewall admin.
I guess I have 2 points and would love to get into the nitty-gritty
details of this situation. Rod states that the VIP is not a real network
interface which I am interpreting as that its not the primary IP on the
LAN adapter.
|
I try not to interpret Rod. <G>
| Quote: | This situation seems to be more of a limitation of the Windows OS than of
MSCS. A cluster virtual server is just a set of software processes
running on a Windows system. What would have to happen is to be able to
associate a particular set of processes with a specific secondary IP
address (or VIP) assigned to a LAN adapter. If this association was
possible, whenever these processes sent information via the network they
would have their own IP (VIP) to send from. As it stands now the
processes just hand off the network traffic to Windows which sends it out
the primary IP.
|
If that were the case, then you would have to have a network driver like NLB
has to accept the packets on behalf of the IP for all nodes and then figure
out which one is active. This would open up MSCS to switch flooding issues.
--
Russ Kaufmann
MVP - Windows Server - Clustering
http://www.clusterhelp.com - Cluster Website
http://msmvps.com/clusterhelp - Blog |
|
| Back to top |
|
|
Russ Kaufmann [MVP]
Guest
|
| Posted:
Fri Oct 28, 2005 8:50 pm Post subject:
Re: Cluster Nodes using Primary IP address - not Virtual IP |
|
|
"Rob" <Rob@nospam.com> wrote in message
news:%23frcib%232FHA.3020@TK2MSFTNGP15.phx.gbl...
| Quote: | Hello all,
I am looking for any new information on a situation I have observed with
MSCS. Is there any news from MS on fixes to MSCS or perhaps a workaround
to have a cluster virtual server actually use its virtual IP address for
both sending and receiving TCP/IP traffic?
|
This is by design.
Rod discusses it here:
http://msmvps.com/clustering/archive/2005/08/11/62372.aspx
--
Russ Kaufmann
MVP - Windows Server - Clustering
http://www.clusterhelp.com - Cluster Website
http://msmvps.com/clusterhelp - Blog |
|
| Back to top |
|
|
Rodney R. Fournier [MVP]
Guest
|
| Posted:
Sat Oct 29, 2005 8:50 am Post subject:
Re: Cluster Nodes using Primary IP address - not Virtual IP |
|
|
Correct! The VIP is not real, nothing virtual is really :)
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Rob" <Rob@nospam.com> wrote in message
news:ueRyg%23%232FHA.320@TK2MSFTNGP10.phx.gbl...
| Quote: | Thanks Russ - I was aware of this limitation but reading Rod's story
reminded me of my own similar situation with a customer's firewall admin.
I guess I have 2 points and would love to get into the nitty-gritty
details of this situation. Rod states that the VIP is not a real network
interface which I am interpreting as that its not the primary IP on the
LAN adapter.
This situation seems to be more of a limitation of the Windows OS than of
MSCS. A cluster virtual server is just a set of software processes
running on a Windows system. What would have to happen is to be able to
associate a particular set of processes with a specific secondary IP
address (or VIP) assigned to a LAN adapter. If this association was
possible, whenever these processes sent information via the network they
would have their own IP (VIP) to send from. As it stands now the
processes just hand off the network traffic to Windows which sends it out
the primary IP.
I think of what VMWare does (and maybe Virt Server too) with virtualizing
network adapters so I know it can be done. Of couse VMWare actually
creates its own network adapter definition for Windows. Maybe if Virtual
Server and MSCS virtualization concepts and technologies merge then we
could have this.
Just some crazy thoughts.. :)
Rob
"Russ Kaufmann [MVP]" <russ@clusterhelp.com> wrote in message
news:ujVXKz%232FHA.3732@TK2MSFTNGP15.phx.gbl...
"Rob" <Rob@nospam.com> wrote in message
news:%23frcib%232FHA.3020@TK2MSFTNGP15.phx.gbl...
Hello all,
I am looking for any new information on a situation I have observed with
MSCS. Is there any news from MS on fixes to MSCS or perhaps a
workaround to have a cluster virtual server actually use its virtual IP
address for both sending and receiving TCP/IP traffic?
This is by design.
Rod discusses it here:
http://msmvps.com/clustering/archive/2005/08/11/62372.aspx
--
Russ Kaufmann
MVP - Windows Server - Clustering
http://www.clusterhelp.com - Cluster Website
http://msmvps.com/clusterhelp - Blog
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in