That is the correct behavor of “name confilict”.
The “hostname” (and domain, called FQNN) is the “global unique address” of
a node. That means, we will try to avoid if two nodes come up with same
(it’s like in a IP network, you can’t have 2 machine have same IP).
As part of the QNET startup, it will try to determine if there is a “name
on network. If it found one, (in your case, one of the “localhost” win, but
second one detect a conflict) QNET put itself into this mode that it only
itself, but won’t talk to anybody on the network.
So in your case, if you have a 3rd machine with some other name, (other then
you would actually see one “localhost” is Okey, but the other is
To avoid name conflict, you either use “Configure->Network Config” to set
hostname for each machine (which it will remember, and set same hostname
you boot); Or you use QNET host=“name.domin” option to pass one to QNET.
Once you are in the name conflict status, you can also reset your hostname
QNET will notice the hostname is changed, and re-try the new name; and if it
conflict with anybody, it will then fully start up.
Jan Ptacek <email@example.com> wrote in message
I have problems with QNET since I upgraded to 6.2. I have 2 boxes running
6.2 on the same subnet, network cards are 3Com905-TX. Sometimes after I
reboot one of them, I can’t see the second one in the /net. On both
machines there is only localhost name in the /net directory. When I do ls
/net/second_machine I get “No route to host” though I can ping or telnet
between the boxes. I tried to restart io-net manually with different
parameters - nothing works. I must do HW reset of both machines (even a
few times) before i finally get both nodes to /net.
Thanks in advance,