Re: SQL 2008 clustering with Windows 2008

Yes. All networking should be in place before Starting Cluster and SQL installation. Since the heartbeat NIC is not onany public network, it should have IP addresses hard-set.

While Windows 2008 and SQL 2008 support DHCP addresses in a cluster, that is a prety advanced setup. If you can get reserved IPs and manually configure them, I would recommend doing so.

The IP address in the SQL Resource group is the address of the SQL Instance. The SQL installer should have prompted you for that value and set it for you (DHCP will skip that step).

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"OceanDeep via SQLMonster.com" <u46587@uwe> wrote in message news:8bd0e4350b61e@xxxxxx
Geoff,

That's what I have for my network setup now. One NIC from each node is
connected to a 'public' netowrk and the other NIC from each node is conected
to a 'private (heartbeat)' network. As soon as I set up this second private
network, my failover doesn't work any more if I turned off node A. Before I
set up the second network, I have just one NIC from each node connected to
the same switch. Under this setup, if I turn off node A, it would fail over
to node B. Also, before my clustering setup and configuration, node A and
node B are configured to get the IP address from DHCP. I forgot to change it
back before I did the clustering setup. Here are my questions.

1. Should the network configuration (both public and private) be set up
before windows clustering setup and SQL setup? Because I can't change the
DHCP setting on the Windows network connection, if I change it to statis IP
there, it somehow brings down the quorum disk resource and SQL source as well.
Please advise how I can change it.

2. Do I need to set up a IP address resource in the SQL resource group in the
Failover Cluster Management tool? What is the purpose of this IP address
resource? Is this the place for the 'virtual IP' of the cluster? Is this
the one that will make the failover work if a NIC for the public network goes
bad?

OceanDeep



Geoff N. Hiten wrote:
If you are just building a tw0-node cluster, the safest heartbeat network is
a crossover cable.

Never team the crossover network.

You can team the public NICs, but you need to put them on different switches
to really make that highly redundant.

Geoff,

[quoted text clipped - 40 lines]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ocean

--
Message posted via http://www.sqlmonster.com


.

Relevant Pages

  • Re: Requirements for iSCSI Cluster
    ... Reference the Q&A from the iSCSI FAQ listed below. ... Q.How many NICs are required for an iSCSI Cluster? ... A network card that is used for connectivity with external clients. ...
    (microsoft.public.windows.server.clustering)
  • Re: Accessing Cluster Disks from a WEB Application
    ... Cluster Name ... Cluster Quorum Disk ... SQL Network Name ...
    (microsoft.public.windows.server.clustering)
  • Re: Event IDs 1122 and 1123
    ... These errors are usually causes by NIC drivers or faulty network components ... latest/greatest drivers...especially if your using Broadcom NICs. ... > Myself and Simon went in on Friday to dissolve teaming on the cluster nics ... > the AD when the first node boots up. ...
    (microsoft.public.windows.server.clustering)
  • Re: Heartbeat Network Adapter
    ... Cluster Administrator. ... that you're actually using the NICs you think you are for each distinct ... MVP - Windows Server - Clustering ... Network Configuration Best Practices for Windows 2000 ...
    (microsoft.public.windows.server.clustering)
  • Re: Tru64 NFS Performance over UDP is very slow.
    ... These nics are plugged into a Brocade Switch. ... Could the network gear be swamped? ... >> The performance in the NFS Cluster is decreasing every day until it ...
    (comp.sys.dec)