Page 1 of 1

Never enough...

Posted: Fri May 19, 2006 7:31 pm
by grunt
It just isnt... Folding is worse then crack, Im averaging around 850ppd and Im still not satisfied!

Posted: Fri May 19, 2006 8:36 pm
by infinitevalence
now you know why i got so many xeons... if only i could get my cluster working agian...

Re: Never enough...

Posted: Fri May 19, 2006 8:58 pm
by pcrobot
grunt wrote:It just isnt... Folding is worse then crack, Im averaging around 850ppd and Im still not satisfied!
LOL, it hard only having one rig... :rolleyes:

Posted: Mon May 22, 2006 8:21 pm
by werewolfdaddy
infinitevalence wrote:now you know why i got so many xeons... if only i could get my cluster working agian...
What's wrong with your cluster?

Posted: Mon May 22, 2006 9:33 pm
by infinitevalence
its something with the DHCP, my nodes are downloading their OS fine off the TFTP server but they are not able to connect after being assigned an adress fomr the DHCP server.

Posted: Tue May 23, 2006 12:52 pm
by kenc51
infinitevalence wrote:its something with the DHCP, my nodes are downloading their OS fine off the TFTP server but they are not able to connect after being assigned an adress fomr the DHCP server.
Have you entered a default gateway?

Posted: Tue May 23, 2006 2:11 pm
by infinitevalence

Posted: Tue May 23, 2006 2:23 pm
by kenc51
try this command

route add -net default gw 192.168.2.1 dev eth0

change the IP to what ever is your gateway/router.....

Posted: Tue May 23, 2006 2:58 pm
by infinitevalence

Code: Select all

# DHCP configuration file for DHCP ISC 3.0
 
ddns-update-style none;
 
# Definition of PXE-specific options
# Code 1: Multicast IP address of boot file server
# Code 2: UDP port that client should monitor for MTFTP responses
# Code 3: UDP port that MTFTP servers are using to listen for MTFTP requests
# Code 4: Number of seconds a client must listen for activity before trying
#         to start a new MTFTP transfer
# Code 5: Number of seconds a client must listen before trying to restart
#         a MTFTP transfer
 
option space PXE;
option PXE.mtftp-ip               code 1 = ip-address;
option PXE.mtftp-cport            code 2 = unsigned integer 16;
option PXE.mtftp-sport            code 3 = unsigned integer 16;
option PXE.mtftp-tmout            code 4 = unsigned integer 8;
option PXE.mtftp-delay            code 5 = unsigned integer 8;
option PXE.discovery-control      code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr   code 7 = ip-address;
 
subnet 192.168.1.0 netmask 255.255.255.0 {
 
  
  class "pxeclients" {
    match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
    option vendor-class-identifier "PXEClient";
    vendor-option-space PXE;
 
    # At least one of the vendor-specific PXE options must be set in
    # order for the client boot ROMs to realize that we are a PXE-compliant
    # server.  We set the MCAST IP address to 0.0.0.0 to tell the boot ROM
    # that we can't provide multicast TFTP (address 0.0.0.0 means no
    # address).
 
    option PXE.mtftp-ip 0.0.0.0;
 
    # This is the name of the file the boot ROMs should download.
    filename "pxelinux.0";
    # This is the name of the server they should get it from.
    # Use the master's IP
    next-server 192.168.1.1;
  }

  # If you are using etherboot with a non specific image 
  class "etherboot" {
        if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
        filename "/diskless/vmlinuz";
        }
  }
  
  pool {
    max-lease-time 86400;
    default-lease-time 86400;
    # This prevents unlisted machines from getting an IP
    deny unknown-clients;
  }
 
  host slave21 {
       # Use your slave's MAC address
       hardware ethernet                00:40:63:C2:CA:C9;
       # Give your slave a static IP
       fixed-address                    192.168.1.21;
       server-name                      "master";
       # Use your gateway IP, if required
       option routers                   192.168.1.1;
       # Use your DNS IP, if required
       option domain-name-servers       192.168.1.1;
       option domain-name               "mydomain.com";
       # Use your slave hostname
       option host-name                 "slave21";
       
       
       # Etherboot and pxe boot with a mac specific image
       option root-path                 "/diskless/192.168.1.21";
       
       if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
                        filename "/vmlinuz_arch";
        } else if substring (option vendor-class-identifier, 0,9) ="PXEClient" {
                        filename "/pxelinux.0";
        }
                                                               
  }
}
Yeah its not that... its something in the DHCP config info on the DHCP server. Sadly my roommate admins that server so i have to get his ass to fix it :(

Posted: Tue May 23, 2006 3:22 pm
by kenc51
The end of that .config file..
# Use your gateway IP, if required
option routers 192.168.1.1;
# Use your DNS IP, if required
option domain-name-servers 192.168.1.1;

option domain-name "mydomain.com";
# Use your slave hostname
option host-name "slave21";
Instead of using your gateway(192.168.1.1) to resolve DNS, enter your ISP's primary DNS server IP.
It's worth a try!
After that I wouldn't have a clue......

Posted: Tue May 23, 2006 3:26 pm
by infinitevalence
yeah its something with the way its attaching to the NFS server for RW, and DHCP i think.... not anything to do with the external gateway, i dont even need internet connections on these as they all load and download from the master NFS server.