"chrismk" <Multiple IP's (from 2 different networks) on a single SQL 2005
Cluster> wrote in message
> I'm currently building up a SQL 2005 Active/Standby cluster in a DMZ. I
> have three NIC's in each server.
BTW, I am not trying to be a pain, but some of the issues here have me
extremely curious. First, why are you putting it in the perimeter network?
You should have it behind the internal firewall so the data is fully
protected and have anything that runs in the perimeter network to make its
calls through the internal firewall using a non-standard port. Data needs to
be protected.
> Each NIC is connected to a different network:
> 192.168.100.1 is the public NIC
> 10.0.0.1 is the NIC used for communication betwen the cluster nodes
> (heartbeat)
> 192.168.200.1 is the admin NIC
Why do you need an admin NIC. There is this concept of IP routing that
should make this requirement go away. <G>
> I have installed my cluster using the 192.168.100.0 network for public
> access. This means that my SQL virtual ip is 192.168.100.10
>
> Each server can be administered over the 192.168.200.0 network (admin) and
> the cluster/sql sever ip is available from the 192.168.100.0 (public)
> network.
>
> Now for my question: How can I assign a ip address from my admin network
> (e.g.192.168.200.10) to the existing SQL server cluster to make it
> available from my admin network while keeping the public ip.
It should work. Add the new IP Address resource and set the dependencies on
all the other resources as needed.
However, just because it should work does not mean it is your best
alternative.
--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web
http://www.clusterhelp.com
Blog
http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Dec 10 - 13 in Denver
Jan 18 - 31 in Denver
FAQ
Search
Profile
Private Messages
Log in
