Re:two node see each other as "down"

"Ian Latter" <[email protected]>
Newsgroups gmane.linux.cluster.openmosix.general
Message-ID <[email protected]>
Hello Didy,


  I've seen two good responses to this thread, one from Chris 
Thevaos and one from Evan Hisey - but I'm not sure if your 
problem was resolved.

  If you are still having trouble, then please see this paper for
further help - it is based on Fedora Core 1, but it should still
provide a template and a checklist for your own environment;
  http://midnightcode.org/papers/How%20To%20-%20Instant%20openMosix.pdf


----- Original Message -----
>From: "Didy Tehumahu" <[email protected]>
>To: "openmosix" <openmosix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
>Subject:  [openMosix-general] two node see each other as "down"
>Date: Thu, 23 Mar 2006 10:13:05 +0700
>
> 
> hello everybody out there , my name is Didy. i'm a student and i'm from =
> Indonesia
> 
> i'm now configure openmosix . all souerce i get from internet and now i'm so confusing with 
openmosix :(
> 
> i have two node in my home and i finnish to configure openmosix . when i 
> run the master and the second node,  it's work fine but two node see each other as 
"down" i'm use redhat 9 for my two node
> 
> master node :
> # ./setpe -r
> This is OpenMosix node #1
> Network protocol: 2 (AF_INET)
> OpenMosix range     1-1     begins at openMosix.domain
> OpenMosix range     2-2     begins at node-01.domain
> Total configured: 2
> 
> #  ./showmap
> My Node-Id: 0x0001
> Base Node-Id Address          Count
> ------------ ---------------- -----
> 0x0001       192.168.88.91    1
> 0x0002       192.168.88.60    1
> 
> # ./mosctl status 1
> up.
> # ./mosctl status 2
> down.
> 
> 
> 
> second node :
> # ./setpe -r
> This is OpenMosix node #2
> Network protocol: 2 (AF_INET)
> OpenMosix range     1-1     begins at openMosix.domain
> OpenMosix range     2-2     begins at node-01.localdomain
> Total configured: 2
> 
> # ./showmap
> My Node-Id: 0x0002
> Base Node-Id Address          Count
> ------------ ---------------- -----
> 0x0001       192.168.88.91    1
> 0x0002       192.168.88.60    1
> 
> # ./mosctl stat 1
> down.
> #./mosctl stat 2
> up.
> 
> my ethernet card in master node  :=20
> #  mii-tool -v
> eth0: negotiated 100baseTx-FD, link ok
>   product info: vendor 00:00:00, model 0 rev 0
>   basic mode:   autonegotiation enabled
>   basic status: autonegotiation complete, link ok
>   capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>   advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>   link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> 
> my ethernet card in second node  :
> #  mii-tool -v
> eth0: negotiated 100baseTx-FD, link ok
>   product info: vendor 00:40:63, model 52 rev 4
>   basic mode:   autonegotiation enabled
>   basic status: autonegotiation complete, link ok
>   capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>   advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD =
> flow-control
>   link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> 
> sorry my english bad , can you help me , i'm still confusing.. :(=20
> 
> 
> Didy Tehumahu
> 


--
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.