Instruction manual

Troubleshooting and Repair
134 025-9416
TNPP
Response Description Solution
RS Resend - the destination node could not
accept the page at this time. An <RS>
response usually indicates one of three
conditions:
• the link is too busy (too much traffic
or too many long messages)
• the destination node is too busy
• the page is to long for the destination
node to handle
The page failed.
Check the RF link for excessive traffic.
Check the destination node for excessive
traffic.
Ensure that the page is not too long for the
destination node to process.
In most situations, the page can be resent
when traffic conditions die down.
Zetron has attempted to provide as much information about failed pages as possible. As a result,
the traffic command also includes some information pertaining to TNPP pages that is not defined
in the specification. These messages are summarized in Table 27.
Table 27. TNPP-Related Traffic Messages
Traffic
Message Description Solution(s)
port link up Indicates that the other node is up
and running. This message is a
response to a link test.
No solution required. The other node is
available to accept TNPP pages.
port link down Indicates that the connection to the
other node is down.
Do not send any pages to this node until a
“port link up” message is received.
port reset sent Indicates that the Model 640 has sent
a reset packet to the other node.
No solution required. This is done when
first connecting to the other node.
port reset seen Indicates that the Model 640 has
received a reset packet from the other
node.
No solution required. This is done when
the other node is first connecting to the
Model 640.
page no dest Inbound page - indicates that the
received page was incorrectly
addressed. (wrong node ID)
Outbound page - indicates that the
destination address is incorrect.
(wrong node ID or name)
Check the NETWORK.CUS file for missing
paging link information.
page bad dest Indicates that the Model 640 does not
recognize the destination node ID.
Check node ID programming.
page dest down Indicates that the outbound port is
currently down. Usually a
handshaking problem.
Wait for node to come back up before
resending the page.
Check the TNPP card for proper
transmission per “Testing the TNPP
Card” on page 129.
port unk node Indicates that the inbound packet was
received on a port that did not
recognize the destination address.
Check the TNPP routing.