Larry Sams wrote:
Here is the netinfo -i and a breif netinfo list…
#//10/>netinfo -l
…
Logical Net 1
Network Card: ARCNET/Corman
…
Vid Sequence Rx Error … 5020
Not too much to worry about, except I wonder about this high count of rx
sequence errors.
Logical Net 2
Network Card: Ethernet/ne1000/2000 (or compatible)
No errors at all for the Ethernet driver. However, there is certainly some
questionable stuff below.
#//10/>netinfo
Date Net (Nid|Status) Code Description
22:19:30 2 Status 56 (507) 1000 ( tx) timeout (no nack)
22:19:30 2 Status 1 (507) 1000 ( tx) timeout (no nack)
22:19:30 2 0050DA 0B9EA0 (507) 1000 ( tx) timeout (no nack)
22:19:30 2 Status 11076 (507) 1000 ( tx) timeout (no nack)
22:19:30 2 Status 7975 (507) 1000 ( tx) timeout (no nack)
22:19:30 2 Status 2 (507) 1000 ( tx) timeout (no nack)
22:19:30 2 Status 3 (507) 1000 ( tx) timeout (no nack)
Lots of these tx timeouts. Do you have entries in your netmap that don’t
actually exist on the network?
22:19:31 2 0050DA 0B9EA0 ( 37) NET ( rx) unrecognized raw packet
protocol
Non-QNX traffic on Ethernet? You don’t by any chance have the Ethernet card
of a Windows machine listed in your netmap?
22:19:31 1 t31 ( 37) NET ( rx) unrecognized raw packet
protocol
Non-QNX traffic on ARCNET?
22:19:31 2 Status 12591 (552) 1000 ( rx) ok_vseq(): simple dup pkt: vid
22:19:31 2 Status 2 (553) 1000 ( rx) ok_vseq(): simple dup pkt: seq
num (reject)
22:19:31 2 Status 3 (536) 1000 ( rx) ok_vseq(): simple dup pkt: pkt
type
22:19:31 2 0050DA 0B9EA0 (527) 1000 ( rx) rxd dup last pkt, txing ACK
22:19:31 2 0050DA 0B9EA0 (524) 1000 ( rx) bad vid seq# - duplicate pkt
22:19:31 2 Status 29953 (552) 1000 ( rx) ok_vseq(): simple dup pkt: vid
22:19:31 2 Status 46 (553) 1000 ( rx) ok_vseq(): simple dup pkt: seq
num (reject)
22:19:31 2 Status 5 (536) 1000 ( rx) ok_vseq(): simple dup pkt: pkt
type
22:19:31 2 0050DA 0B9EA0 (527) 1000 ( rx) rxd dup last pkt, txing ACK
22:19:31 2 0050DA 0B9EA0 (524) 1000 ( rx) bad vid seq# - duplicate pkt
Different kind of trouble communicating with the same Ethernet adapter
again. Guess it must be a QNX node. Seeing duplicate packets often means
that one node is not managing to receive as fast as another node is
transmitting to it. A slow CPU or a slow interface to an Ethernet card (eg.
ISA bus) might cause this.
For further help, you might post your netmap file (also check your in-memory
netmap on node 1 and 10).
–
Bert Menkveld
P. Eng.
B&E Technologies
bert@betech.biz
Alex Burk wrote:
On Sat, 03 Mar 2007 00:20:20 +0200, Larry Sams
lsams@tulsaconnect.com> > wrote:
We have an 10 node QNX 4 network. Node 10 has a performance problem
that we can not locate. The quick version of the network is:
10 node have Arcnet card on the production floor
Node 1 and Node 10 have ethernet cards connected to the office
(Windows XP) network.
The office computers connect to Nodes 1 and 10 to access data via
Telnet. Node 10 has a noticable delay. All the tests I run show
Idle running most of the time. SAC shows all activity in priority
0. But a netinfo show about 60-100 errors per minute. Is there a way
to stop this error logging?
Suggestions???
Thanks,
Larry Sams
need to see your
netinfo -l
what strings you think error ?