Re: Cluster Help?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Kevin Fitzpatrick (fitzit22_at_yahoo.com)
Date: 07/27/04 

Date: 27 Jul 2004 04:27:38 -0700

The ip configuration is fine, I can ping the public and heartbeat from
the first and second node. I can also ping the public from other
servers. It is really strange. Both Network cards in node 2 are
unavaible through cluster administrator. I added a third network card
to the server and have the same problem with that NIC, it is
unavailable.

Windows 2000 IP Configuration

Ethernet adapter Public:

        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
#3
        Physical Address. . . . . . . . . : 00-10-18-03-64-83
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 10.224.54.200
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.224.54.1
        DNS Servers . . . . . . . . . . . : 10.224.53.19
                                            10.224.52.19
                                            10.224.98.19
        Primary WINS Server . . . . . . . : 10.224.52.19
        Secondary WINS Server . . . . . . : 10.224.98.19

Ethernet adapter Heartbeat:

        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
        Physical Address. . . . . . . . . : 00-02-55-DC-46-F3
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.11
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . :
        NetBIOS over Tcpip. . . . . . . . : Disabled

"Ramon Jiménez" <rjimenezm.athome@my.hotmail.com> wrote in message news:<Oc#hlZ6cEHA.3620@TK2MSFTNGP10.phx.gbl>...
> Check your NIC's are operational and functional.
>
> Check that your Public Nic is configured to use All communications and your
> Private Nic is configured to Cluster Communications.
>
> But you seem to have a NIC problem...please send an IPconfig /all from your
> node failing to join...
>
> --
> Saludos
> Ramon
> PMP, ITIL Certified
> MCSE & MCSA 2000/2003, CCA
> "Kevin Fitzpatrick" <fitzit22@yahoo.com> wrote in message
> news:81548847.0407261201.3ed640a4@posting.google.com...
> > Hello,
> >
> > I am having an issue with my second node of an active/passive cluster.
> > The second node is unable to rejoin the cluster. The second node had
> > been fine until two weeks ago when it was rebooted.
> >
> > Here are the errors that I am receiving in my Event Log.
> >
> > Event ID 1107 Cluster node AMHEPICL01 failed to make a connection to
> > the node over network 'Heartbeat'. The error code was 1721.
> >
> > Also, in cluster administrator both of the network cards are
> > unavailable with red x's through them. With an unavailable status.
> >
> > I also receive error 1721 not enough system resources to start the
> > cluster service as well. When I try to start the cluster service.
> >
> > Any help would be greatly appreciated.
> >
> > Kevin
> >
> > Here is a couple of lines from my cluster.log file. I thought maybe
> > it was the cluster service account, but I am not seeing any access
> > denied error 5's.
> >
> > 00000858.00000918::2004/07/26-13:06:41.542 [NMJOIN] Creating RPC
> > bindings for member node 1
> > 00000858.00000918::2004/07/26-13:06:41.542 [NMJOIN] Attempting to use
> > network Public to create bindings for node 1
> > 00000858.00000904::2004/07/26-13:06:41.557 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000904::2004/07/26-13:06:41.557 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000904::2004/07/26-13:06:41.573 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000904::2004/07/26-13:06:41.589 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000914::2004/07/26-13:06:41.589 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000918::2004/07/26-13:06:41.589 [NMJOIN] Member node 1
> > failed to create binding to us, status 1721
> > 00000858.00000918::2004/07/26-13:06:41.589 [NMJOIN] Attempting to use
> > network Heartbeat to create bindings for node 1
> > 00000858.00000914::2004/07/26-13:06:41.589 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000914::2004/07/26-13:06:41.589 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000914::2004/07/26-13:06:41.604 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000914::2004/07/26-13:06:41.604 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000914::2004/07/26-13:06:41.604 [ClMsg] Deleting security
> > contexts for node 1.
> > 00000858.00000918::2004/07/26-13:06:41.604 [NMJOIN] Member node 1
> > failed to create binding to us, status 1721
> > 00000858.00000918::2004/07/26-13:06:41.604 [NMJOIN] Cluster node 1 is
> > not reachable. Join failed.
> > 00000858.00000918::2004/07/26-13:06:41.604 [JOIN] NmJoinCluster
> > failed, status 1721.
> > 00000858.00000918::2004/07/26-13:06:41.604 [INIT] Cleaning up failed
> > join attempt.
> > 00000858.00000918::2004/07/26-13:06:41.604 [INIT] Leaving cluster
> > 00000858.00000918::2004/07/26-13:06:41.604 [NM] Shutting down
> > membership...
> > 00000858.00000918::2004/07/26-13:06:41.604 [ClMsg] Cleaning up
> > 00000858.00000644::2004/07/26-13:06:41.604 [ClMsg] Receive datagram
> > failed, status 995
> > 00000858.00000644::2004/07/26-13:06:41.604 [ClMsg] Post of receive
> > datagram failed, status 10038
> > 00000858.00000644::2004/07/26-13:06:41.714 [ClMsg] Datagram socket was
> > closed. status 10038
> > 00000858.00000644::2004/07/26-13:06:41.714 [ClMsg] Control Channel was
> > closed.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Membership shutdown
> > complete.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Interface cleanup
> > starting...
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] deleting object for
> > interface 1f387670-01f2-4fb1-b728-95b03d9321c2
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Deregistering network
> > 99b12271-a8c1-45c1-9e6f-90692beb949a (Public) from cluster transport.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] destroying object for
> > interface 1f387670-01f2-4fb1-b728-95b03d9321c2
> > 00000858.00000918::2004/07/26-13:06:41.714 [OM] Deleting object Public
> > - AMHEPICL02 (1f387670-01f2-4fb1-b728-95b03d9321c2)
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] deleting object for
> > interface 74c0e5ec-e612-4d25-ae50-d420fbc292fa
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Deregistering network
> > 220d5c83-1b4b-40fa-bc2c-0585632b2b7c (Heartbeat) from cluster
> > transport.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] destroying object for
> > interface 74c0e5ec-e612-4d25-ae50-d420fbc292fa
> > 00000858.00000918::2004/07/26-13:06:41.714 [OM] Deleting object
> > Heartbeat - AMHEPICL02 (74c0e5ec-e612-4d25-ae50-d420fbc292fa)
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] deleting object for
> > interface 75f6f2eb-1ab9-48b1-92b9-4aebe41600cf
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] destroying object for
> > interface 75f6f2eb-1ab9-48b1-92b9-4aebe41600cf
> > 00000858.00000918::2004/07/26-13:06:41.714 [OM] Deleting object Public
> > - AMHEPICL01 (75f6f2eb-1ab9-48b1-92b9-4aebe41600cf)
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] deleting object for
> > interface 137bc8e3-35fd-4529-af06-2d38d624c336
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] destroying object for
> > interface 137bc8e3-35fd-4529-af06-2d38d624c336
> > 00000858.00000918::2004/07/26-13:06:41.714 [OM] Deleting object
> > Heartbeat - AMHEPICL01 (137bc8e3-35fd-4529-af06-2d38d624c336)
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Network interface
> > cleanup complete
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Network cleanup
> > starting...
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Deleting object for
> > network 220d5c83-1b4b-40fa-bc2c-0585632b2b7c.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Deregistering network
> > 220d5c83-1b4b-40fa-bc2c-0585632b2b7c (Heartbeat) from cluster
> > transport.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] destroying object for
> > network 220d5c83-1b4b-40fa-bc2c-0585632b2b7c
> > 00000858.00000918::2004/07/26-13:06:41.714 [OM] Deleting object
> > Heartbeat (220d5c83-1b4b-40fa-bc2c-0585632b2b7c)
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Deleting object for
> > network 99b12271-a8c1-45c1-9e6f-90692beb949a.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Deregistering network
> > 99b12271-a8c1-45c1-9e6f-90692beb949a (Public) from cluster transport.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] destroying object for
> > network 99b12271-a8c1-45c1-9e6f-90692beb949a
> > 00000858.00000918::2004/07/26-13:06:41.714 [OM] Deleting object Public
> > (99b12271-a8c1-45c1-9e6f-90692beb949a)
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Network cleanup
> > complete
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Node cleanup
> > starting...
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Deleting object for
> > node 1.
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] destroying node 1
> > 00000858.00000918::2004/07/26-13:06:41.714 [OM] Deleting object
> > AMHEPICL01 (1)
> > 00000858.00000918::2004/07/26-13:06:41.714 [NM] Node cleanup complete
> > 00000858.00000918::2004/07/26-13:06:41.714 [INIT] Deregistering RPC
> > endpoints & interfaces.
> > 00000858.00000918::2004/07/26-13:06:41.714 [INIT] Failed to deregister
> > endpoint for ExtroCluster interface, status 1752.
> > 00000858.00000918::2004/07/26-13:06:41.714 [INIT] Failed to deregister
> > endpoint for JoinVersion interface, status 1752.
> > 00000858.00000918::2004/07/26-13:06:41.714 [INIT] Failed to join
> > cluster, status 1721
> > 00000858.00000918::2004/07/26-13:06:41.714 [CS] ClusterInitialize
> > failed 1721
> > 00000858.00000918::2004/07/26-13:06:41.714 [INIT] The cluster service
> > is shutting down.
> > 00000858.00000918::2004/07/26-13:06:41.714 [EVT] EvShutdown
> > 00000858.00000918::2004/07/26-13:06:41.714 [FM] Shutdown: Failover
> > Manager requested to shutdown groups.
> > 00000858.00000918::2004/07/26-13:06:41.714 [FM] FmpCleanupGroups:
> > Entry
> > 00000858.00000918::2004/07/26-13:06:41.714 [FM] FmpCleanupGroups: Exit
> > 00000858.00000918::2004/07/26-13:06:41.714 [Dm] DmShutdown
> > 00000858.00000918::2004/07/26-13:06:41.714 [DM] DmpShutdownFlusher:
> > Entry
> > 00000858.00000918::2004/07/26-13:06:41.714 [DM] DmpShutdownFlusher:
> > Setting event
> > 00000858.00000770::2004/07/26-13:06:41.714 [DM] DmpRegistryFlusher:
> > got 0
> > 00000858.00000770::2004/07/26-13:06:41.714 [DM] DmpRegistryFlusher:
> > exiting
> > 00000858.00000918::2004/07/26-13:06:41.714 [MM] MMLeave is called when
> > rgp=NULL.
> > 00000858.00000918::2004/07/26-13:06:41.714 [CS] Service Stopped. exit
> > code = 1721

Relevant Pages

  • Re: Clustering Exchange
    ... As your application is Exchange and you have A/A/P configuration, ... actively block any node hosting two Exchange virtual servers. ... are you done creating the three node cluster? ...
    (microsoft.public.windows.server.clustering)
  • Network Load Balancing Problems
    ... We actually have the following configuration: ... + 03 Terminal Servers with Windows Server 2003 EE ... We dont have configured the full servers cluster, ... Terminal Server hosts to the NLB cluster. ...
    (microsoft.public.windows.server.clustering)
  • Re: Load balancing strange issue
    ... I often made a NLB cluster but never had this much problems configuring it. ... I updated the NIC drivers to the newest version today on both servers. ... >> Cluster configuration stabilized. ...
    (microsoft.public.windows.server.clustering)
  • RE: Cannot add node
    ... we're already on the basic NTLM settings, ... cluster service on each node? ... >| array is connected to both server, both servers see it ... >| cluster configuration cannot be saved. ...
    (microsoft.public.windows.server.clustering)
  • Re: Unable to add second node with NLB
    ... > I'm running two Win2K3 SUS servers and I wish to cluster them using NLB. ... cluster and re-installing it on the second node generate the same error, ... it seems like it's an issue with the communication between the two servers. ... Within NLB configuration, ...
    (microsoft.public.windows.server.clustering)