none
Failed in adding node template to compute RRS feed

  • Question

  • Hi everyone, 

    I am running cluster with topology 1. My head node is connected to enterprise network with 1 port and connected to a switch with another port. A compute node is also connected to the switch. 
    Then, I have added my compute node which runs on 32-bit windows server 2008 enterprise to my cluster. However, the state is shown as UNKNOWN and the health is OK.
    From what I read in the installation guide, it seems to be okay after I add the node template to the compute node.
    But somehow it failed saying that couldn't contacted the compute node. I have attached my ipconfig and the error message below. Thx.

    Updating Cluster Configuration

    Time Message
    3/8/2010 9:18:27 PM A socket operation was attempted to an unreachable network 169.254.80.23:5800
    3/8/2010 9:18:27 PM Failed to communicate with the cluster scheduler service. A socket operation was attempted to an unreachable network 169.254.80.23:5800
    3/8/2010 9:18:17 PM Retrying operation Update, retry count 1
    3/8/2010 9:18:17 PM A socket operation was attempted to an unreachable network 169.254.80.23:5800
    3/8/2010 9:18:17 PM Failed to communicate with the cluster scheduler service. A socket operation was attempted to an unreachable network 169.254.80.23:5800
    3/8/2010 9:18:16 PM Updating the scheduler MPICH_SUBNET binding. 192.168.1.0/255.255.255.0
    3/8/2010 9:18:16 PM Updating the global host file for the cluster


    Assigning template

    Time Message
    3/8/2010 8:56:36 PM Failed to execute the change on the target node
    3/8/2010 8:56:36 PM Could not contact node 'COMPUTENODE1' to perform change. The management service was unable to connect to the node using any of the ip addresses resolved for the node.
    3/8/2010 8:56:36 PM Could not contact node 'COMPUTENODE1' to perform change. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.2:6729
    3/8/2010 8:55:52 PM Checking the configuration of compute node HPC.TEST\COMPUTENODE1.
    3/8/2010 8:55:52 PM Failed to execute the change on the target node



    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Administrator>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : WIN-51TJUDNYIR2
       Primary Dns Suffix  . . . . . . . : HPC.test
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : HPC.test

    Ethernet adapter Private:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
     NIC
       Physical Address. . . . . . . . . : 00-E0-4C-BA-BC-8F
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.1(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Enterprise:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) 82567LF-2 Gigabit Network Connec
    tion
       Physical Address. . . . . . . . . : 00-1C-C0-7D-3F-F6
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.18.42.21(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Monday, March 08, 2010 12:19:33 PM
       Lease Expires . . . . . . . . . . : Tuesday, March 09, 2010 6:19:33 AM
       Default Gateway . . . . . . . . . : 172.18.42.1
       DHCP Server . . . . . . . . . . . : 172.16.3.247
       DNS Servers . . . . . . . . . . . : 172.16.3.247
                                           172.16.1.247
       Primary WINS Server . . . . . . . : 172.16.3.247
       Secondary WINS Server . . . . . . : 172.16.1.247
                                           129.20.100.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 8:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{D3FFF260-25A2-48C3-AB72-CA4C37B48
    154}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 9:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{6F41947A-BBF8-4A36-9B05-6189A7858
    B25}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Monday, March 8, 2010 1:30 PM

Answers

  • Hi there
    I notice that your compute node is running a 32 bit version of Windows Server 2008. One of the requirements of Windows HPC Server is a 64 bit version of Windows Server 2008. This is likely causing the issues you are experiencing.
    Check out the HPC Server FAQ for more: http://www.microsoft.com/hpc/en/us/faq.aspx
    Regards
    Dan
    • Marked as answer by Green126 Thursday, April 8, 2010 2:01 AM
    Monday, March 8, 2010 2:02 PM

All replies

  • Hi there
    I notice that your compute node is running a 32 bit version of Windows Server 2008. One of the requirements of Windows HPC Server is a 64 bit version of Windows Server 2008. This is likely causing the issues you are experiencing.
    Check out the HPC Server FAQ for more: http://www.microsoft.com/hpc/en/us/faq.aspx
    Regards
    Dan
    • Marked as answer by Green126 Thursday, April 8, 2010 2:01 AM
    Monday, March 8, 2010 2:02 PM
  • how did you get your compute node to be a compute node?
    did you deploy a 32 bit OS on it using our tools?
    did you run hpc pack setup on it manually?
    we shoudl be blocking both ways, so not sure how you got to a state where your compute node is 32 bits...
    pm
    Thursday, March 18, 2010 10:50 PM
    Moderator