Re: DHCP in openMosix

Hello Murali P


  I don't know if you have resolved your cluster configuration
issue, however, I do have an alternative test for you to 
perform.

  The following guide shows how to construct and test a 
cluster as small as two nodes on a cross-over cable.  It uses
the RPMs that you used, and the cluster that it builds - works.
  http://midnightcode.org/papers/How%20To%20-%20Instant%20openMosix.pdf

  If you are still having difficulty with your cluster, then try
taking two nodes, link them with a cross-over network cable
and build them from the document.  If you succeed, put them
on your LAN and test them.  If that succeeds then you should
be fine for a cluster on the first LAN segment, but then you
will need to do some work to integrate the second LAN 
segment.





----- Original Message -----
>From: "Ian Latter" <[email protected]>
>To: <openmosix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
>Subject:  Re: [openMosix-general] DHCP in openMosix
>Date: Fri, 10 Feb 2006 10:42:09 +1000
>
> Hello,
> 
> 
>   Cleaning up some mail here;
> 
>     You need to follow through on your network testing;
>       "A good network test for an unfiltered environment; can
>        you ping from each cluster node to each other cluster 
>        node?"
> 
>   Prove to yourself that you don't have a network connectivity
> issue *before* you attempt to resolve your openMosix
> configuration issue.  I am confident that you have *both* 
> problems.
> 
>   1. Telnet or SSH to each node from each node.  
>   2. Does this work?
>   3. If not, find the network problem and solve it, go back to 1.
>   4. Now that the network is ok, look hard at the openMosix
>         configuration on each box. 
>   5. Does every node have the same configuration?
>   6. If not, fix and go back to 4.
>   7. Does every node acnknowledge every other node? (showmap)
>   8. If not, check logs, try to fix, or consider going back to 1.
> 
>   If your network is filtered at that router, then you may have
> problems.  Consider telnet'ing netcat'ing to the nodes from each
> other to confirm connectivity.  Use "netstat -an" to validate
> established TCP sessions at each end.
> 
>   You need to work to clarify the exact point at which your 
> problem occurs, then come back for some advice.
> 
> 
> 
> 
> ----- Original Message -----
> >From: "Murali P" <[email protected]>
> >To: "openMosix Mailing List" <openmosix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
> >Subject:  Re: [openMosix-general] DHCP in openMosix
> >Date: Wed, 01 Feb 2006 10:22:27 +0530
> >
> > Well, I tried the two things. I enquired  about the router to my nework 
> > admin and he said there is a router connecting all the VLANs.
> > 
> > I tried the second the option also, but still to no avail.
> > 
> > I had used the rpm file for my installation. Is it because of this that 
> > i am facing trouble?
> > i used the openmosix-kernel-2.4.26-?.i386.rpm
> > 
> > regards
> > Murali
> > 
> > Ian Latter wrote:
> > > Dude,
> > >
> > >   There are two possibilities here;
> > >
> > > 1. NETWORK ISSUE
> > >
> > >   So long as the following hold true;
> > >     - all of your openMosix machines have only one NIC
> > >     - all of your openMosix machines are connected to the
> > >        same LAN or VLAN (i.e. none are seperated by routers)
> > >
> > > .. then your problem is a network configuration issue.
> > >
> > > In your environment, you have;
> > >     - Vader at 192.168.4.144/255.255.255.0
> > >     - A second machine at  192.168.2.14/(what mask?) 
> > >     - And other machines per DHCP allocation
> > >
> > > Vader is unable to see the second machnie, and 
> > > probably the DHCP allocated machines as 192.168.4.144/
> > > 255.255.255.0 must route to something on the 
> > > 192.168.4.x  network to get to 192.168.2.14.
> > >
> > > Without a router, and while you are using different 
> > > networks with different masks, then neither auto-
> > > discovery nor static maps will work.
> > >
> > > A good network test for an unfiltered environment; can
> > > you ping from each cluster node to each other cluster 
> > > node?
> > >
> > >
> > > 2. OPENMOSIX ISSUE
> > >
> > > If, however, your network is setup in a more typical
> > > manner;
> > >     - all of your openMosix machines have only one NIC
> > >     - all of your openMosix machines are connected to 
> > >         LANs or VLANs that are routed (and not filtered)
> > >
> > > .. then your problem is an openMosix configuration 
> > > issue.
> > >
> > > Try disabling auto-discovery (in this routed environment)
> > > and use the following openMosix Map file on *all* cluster
> > > machines;
> > >
> > > # Static openMosix configuration
> > > # ==============================
> > > #
> > > # Each line in this file should contain 3 fields, statically mapping
> > > # IP addresses to openMosix node-numbers:
> > > #
> > > # 1) The first openMosix node-number in this range.
> > > # 2) The IP address of the above node (or node-name from /etc/hosts).
> > > # 3) The number of nodes in this range.
> > > #
> > > # Note: If you don't create a valid IP <-> node-number mapping, the
> > > #       autodiscovery daemon will be started, automatically assigning
> > > #       node-numbers to all visible openMosix machines.
> > > #
> > > # Example: 10 machines with IP addresses 192.168.1.50 - 192.168.1.59
> > > #          which will have openMosix node-numbers 1-10:
> > > #
> > > # 1        192.168.1.50     10
> > > #
> > > # MOSIX-#  IP  number-of-nodes
> > > # ============================
> > > 1         192.168.2.1     255
> > > 256    192.168.4.1     255
> > >
> > >
> > > Note that this assumes that you DHCP allocation is 
> > > going to populate either the 192.168.2.x network or
> > > the 192.168.4.x network.  If your DHCP machines
> > > are in another network, say 192.168.3.x, then add
> > > the following line to the above openmosix.map file;
> > >
> > > 512    192.168.3.1     255
> > >
> > >
> > >
> > >
> > >
> > > Hope that helps,
> > >
> > >   
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > _______________________________________________
> > openMosix-general mailing list
> > openMosix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > https://lists.sourceforge.net/lists/listinfo/openmosix-general
> > 
> 
> 
> --
> Ian Latter
> Late night coder ..
> http://midnightcode.org/
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> openMosix-general mailing list
> openMosix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/openmosix-general
> 


--
Ian Latter
Late night coder ..
http://midnightcode.org/



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642