Hi all
I get netmap results that I don’t understand on a diskless node that boots
over Ethernet. My QNX node #9 boots from node #8 which has two Ethernet
controllers. The netmap on node #8 (and all nodes 1…10 except 9) looks
like this:
#Logical Lan Physical
1 1 00A024 47D68C
2 1 00A024 4FB36C
3 1 00A024 576443
4 1 00105A D5DB3B
5 1 00508B 4D3E80
6 1 00105A D75D55
7 1 0020AF 91E514
8 1 00D0C9 350375
8 2 00D0C9 350376
9 2 00D0C9 315203
10 1 00A024 4C50CA
As can be seen from the netmap, I want node #9 to be on LAN 2.
The boot build file for node #9 is as follows:
/boot/sys/boot
$ /boot/sys/boot -v
sys/Proc32
$ Proc32 -l 9 -D -o 3f8
sys/Slib32
$ Slib32
sys/Slib16
$ Slib16
/bin/Net
$ Net -E3 -T -n 10 -m “8 2 00D0C9 350376” -m “9 2 00D0C9 315203”
/bin/Net.rtl
$ Net.rtl
/bin/sinit
$ sinit -r //8/ TERM=qnx TZ=std01
When node #9 has booted, netmap on node #9 outputs:
Logical Lan Physical TX Count Last TX Fail Time
8 2 00D0C9 350376 ; 0
8 1 00D0C9 350376 ; 2803
9 2 00D0C9 315203 ; 0
9 1 00D0C9 315203 ; 0
If I try removing one of the mappings on node #9 with netmap -m “d 8 1”,
node #9 loses contact with node #8. But if I do ls //9 on node #8, the
netmap is restored and node #9 can access node #8’s hard drive again. Node
#8 is the only node that can see #9, and #9 can only see #8…
Help!??
Thanks in advance,
P-O Håkansson
You have to specify ‘-l2’ to the rtl driver to start it on lan 2. It
defaults to lan1. eg Net.rtl -l2
Previously, P-O H kansson wrote in qdn.public.qnx4:
Hi all
I get netmap results that I don’t understand on a diskless node that boots
over Ethernet. My QNX node #9 boots from node #8 which has two Ethernet
controllers. The netmap on node #8 (and all nodes 1…10 except 9) looks
like this:
#Logical Lan Physical
1 1 00A024 47D68C
2 1 00A024 4FB36C
3 1 00A024 576443
4 1 00105A D5DB3B
5 1 00508B 4D3E80
6 1 00105A D75D55
7 1 0020AF 91E514
8 1 00D0C9 350375
8 2 00D0C9 350376
9 2 00D0C9 315203
10 1 00A024 4C50CA
As can be seen from the netmap, I want node #9 to be on LAN 2.
The boot build file for node #9 is as follows:
/boot/sys/boot
$ /boot/sys/boot -v
sys/Proc32
$ Proc32 -l 9 -D -o 3f8
sys/Slib32
$ Slib32
sys/Slib16
$ Slib16
/bin/Net
$ Net -E3 -T -n 10 -m “8 2 00D0C9 350376” -m “9 2 00D0C9 315203”
/bin/Net.rtl
$ Net.rtl
/bin/sinit
$ sinit -r //8/ TERM=qnx TZ=std01
When node #9 has booted, netmap on node #9 outputs:
Logical Lan Physical TX Count Last TX Fail Time
8 2 00D0C9 350376 ; 0
8 1 00D0C9 350376 ; 2803
9 2 00D0C9 315203 ; 0
9 1 00D0C9 315203 ; 0
If I try removing one of the mappings on node #9 with netmap -m “d 8 1”,
node #9 loses contact with node #8. But if I do ls //9 on node #8, the
netmap is restored and node #9 can access node #8’s hard drive again. Node
#8 is the only node that can see #9, and #9 can only see #8…
Help!??
Thanks in advance,
P-O H kansson
\
Have you tried adding “-l2” to the $Net.rtl line?
“P-O Håkansson” wrote:
Hi all
I get netmap results that I don’t understand on a diskless node that boots
over Ethernet. My QNX node #9 boots from node #8 which has two Ethernet
controllers. The netmap on node #8 (and all nodes 1…10 except 9) looks
like this:
#Logical Lan Physical
1 1 00A024 47D68C
2 1 00A024 4FB36C
3 1 00A024 576443
4 1 00105A D5DB3B
5 1 00508B 4D3E80
6 1 00105A D75D55
7 1 0020AF 91E514
8 1 00D0C9 350375
8 2 00D0C9 350376
9 2 00D0C9 315203
10 1 00A024 4C50CA
As can be seen from the netmap, I want node #9 to be on LAN 2.
The boot build file for node #9 is as follows:
/boot/sys/boot
$ /boot/sys/boot -v
sys/Proc32
$ Proc32 -l 9 -D -o 3f8
sys/Slib32
$ Slib32
sys/Slib16
$ Slib16
/bin/Net
$ Net -E3 -T -n 10 -m “8 2 00D0C9 350376” -m “9 2 00D0C9 315203”
/bin/Net.rtl
$ Net.rtl
/bin/sinit
$ sinit -r //8/ TERM=qnx TZ=std01
When node #9 has booted, netmap on node #9 outputs:
Logical Lan Physical TX Count Last TX Fail Time
8 2 00D0C9 350376 ; 0
8 1 00D0C9 350376 ; 2803
9 2 00D0C9 315203 ; 0
9 1 00D0C9 315203 ; 0
If I try removing one of the mappings on node #9 with netmap -m “d 8 1”,
node #9 loses contact with node #8. But if I do ls //9 on node #8, the
netmap is restored and node #9 can access node #8’s hard drive again. Node
#8 is the only node that can see #9, and #9 can only see #8…
Help!??
Thanks in advance,
P-O Håkansson
“Richard R. Kramer” <rrkramer@kramer-smilko.com> wrote in message
news:3C0C0549.E2A6CA22@kramer-smilko.com…
Have you tried adding “-l2” to the $Net.rtl line?
Now I have, and it did the trick. You learn something new everyday - even
more if you read all the manuals… 
Thanks for your help,
P-O