At 8:27 PM +0200 25/5/14, Johnny Billquist wrote: More interesting would be to see EXEC COUNTERS, as well as counters for the two nodes, from both sides. Full story: ----------------------- NCP SHO EXE COUNT Node counters as of 30-MAR-82 00:20:53 Executor node = 10.1 (SHARK) 0 Buffer unavailable 0 Peak logical links active 0 Aged packet loss 0 Node unreachable packet loss 0 Node out-of-range packet loss 0 Oversized packet loss 0 Packet format error 0 Partial routing update loss 0 Verification reject NCP SHO LINE QNA-0 COUNT Line counters as of 30-MAR-82 00:20:56 Line = QNA-0 1242 Seconds since last zeroed 5309886 Bytes received 270380 Bytes sent 73284 Multicast bytes received 13435 Data blocks received 6356 Data blocks sent 240 Multicast blocks received 0 Blocks sent, single collision 0 Blocks sent, multiple collision 0 Send failure 0 Collision detect check failure 0 Receive failure 1 Unrecognized frame destination 23 Data overrun 0 System buffer unavailable ----------------------- NCP SHO EXE COUNT Node counters as of 30-MAR-82 00:20:56 Executor node = 10.2 (SNAKE) 0 Buffer unavailable 0 Peak logical links active 0 Aged packet loss 0 Node unreachable packet loss 0 Node out-of-range packet loss 0 Oversized packet loss 0 Packet format error 0 Partial routing update loss 0 Verification reject NCP SHO LINE QNA-0 COUNT Line counters as of 30-MAR-82 00:20:59 Line = QNA-0 1244 Seconds since last zeroed 359441 Bytes received 5259859 Bytes sent 73238 Multicast bytes received 6352 Data blocks received 13533 Data blocks sent 239 Multicast blocks received 0 Blocks sent, single collision 0 Blocks sent, multiple collision 0 Send failure 0 Collision detect check failure 0 Receive failure 0 Unrecognized frame destination 0 Data overrun 0 System buffer unavailable ----------------------- 10.1 runs NFT. 10.2 runs FAL. -- Jean-Yves Bernier