Specifications

143
Format of TNPP Related Log File Postings
? NET0002 page no dest 03:49:15p 1 1,0101N -
A packet addressed to node “0101” was received. The Network card was programmed to
route “
0101” to Central, but Central has not been programmed as how to send such pages
- the RF paging information is missing. Check the
network.cus file.
? 0098 page no dest 10:03:25a 1 8AL BLORKSNGV
A locally originated page with “Network” destination where the entered node name was
not in the
network.cus file. The node name is posted, followed by a “V”, which stands
for a “Virtual destination” type.
- NET0002 port Link Down 03:48:48p 1 2,0105N
The link to the node connected to port two has gone down. No pages will be sent to that
port.
. 0000 page dest down 03:47:46p 1 7AL 2,0105N P0 00000000 D 3 *0*
A network outbound page should be routed out port two, but that port currently is down.
. 0000 page CAN reply 03:47:49p 1 7AL 2,0105N P0 00000000 D 3 *0*
A network outbound page was sent out port two, and a <CAN> was received as the reply to
it. This usually means the other node, connected to port two, does not know about the
destination node ID, or did not like something about the page.
. 0000 page NAK fail 03:47:55p 1 7AL 2,0105N P0 00000000 D 3 *0*
A network outbound page was sent out port two, and it received a <NAK> to each attempt
to send it, until the retry limit was reached. This usually means the link is a very noisy, the
link is not properly set up, or the other node, connected to port two, did not like something
about the page.
. 0000 page RS fail 03:53:56p 1 7AL 2,0105N P0 00000000 D 3 *0*
A network outbound page was sent out port two, and it received a <RS> to each attempt to
send it, until the resend limit was reached. This usually means the link is too busy (too
much traffic, too many very long messages), the other node is too busy, or the page is too
long for the other node to handle.
. 0000 page timed out 03:55:36p 1 7AL 2,0105N P0 00000000 D 3 *0*
A network outbound page was sent out port two, and the port did not receive a response to
the packet within the timeout interval. When using RF packet modems this often indicates
troubles with the RF transmissions such as a weak signal or an interfering transmission.
The packet modems are retrying the transmission, and may succeed in sending the packet,
but the round trip time is too long.
. 0000 packet timed out 03:56:11p 1 7AL 2,0105N
While port two was receiving an inbound packet, there was too long of a gap between
characters. In effect, the packet being received was chopped off short. Often this means
that the link has broken or interfered with, a noise burst on a RF or telephoned link could
cause this. The packet's sender should retry the transmission, however the constant
appearance of this log message indicates possible problems with the inter-node link.
- NET0002 packet too far 03:56:43p 1 7AL 2,0105N