Specifications

Remote Maintenance
356 025-9035AA
Warning Results
Result Type Description
bad CRC A TNPP packet was received with a bad CRC (bad data/noise).
CAN reply The TNPP node being transmitted to responded to the packet with a
<CAN>. Either the other terminal has not been programmed to accept this
packet's destination address, or the packet format appeared to be improper
or not understood.
dest down Channel dead, node offline. (Old form of above message).
dst down Channel dead, node offline.
Link Down The TNPP link for the specified port went down. Note that newer code
will give “link down” postings for all active ports at boot-up time.
NAK fail The TNPP packet being sent was responded to with a total of Cretry
<NAK>s, without ever seeing an <ACK>. For the default oparam values
this means that the packet was <NAK>ed 6 times.
No voice chan Could not obtain voice channel.
PS full PageSaver partition full.
retry fail The packet was not responded to within Tnri/Tnrb, for a total of Cretry
retries; or a Link Test after Tnri/Tnrb timeout was not able to establish the
link. Generally this indicates some sort of problem with the link between
the two terminals.
RS fail The TNPP packet being sent was responded to with a total of Chold <RS>
replies, without ever seeing an <ACK>. Indicates that the destination is
running out of buffer space, and may be overloaded. Or, a TAP outdial call
was rejected, called terminal sent <RS> to reject the page. This often
indicates that the subscriber ID was not in the other terminal’s database.
SUB-ETB TNPP, a packet was seen with the non-standard escaping of an <ETB>
marker.
too big TNPP received a packet that appeared to be longer than 1Kbyte This may
have been caused by noise or receiver overrun.
too far TNPP received a packet that was to be routed out another serial port, and
that packet's inertia had reached zero. Such packets will not be routed
further to other terminals. Normally indicates that the network is
misconfigured, the terminals “upstream” from the Zetron will need to
check for misrouting.
unk block A TNPP packet was received that contained a block type that ZPAGE did
not know how to process. Generally this means that something besides
CAP code or ID pages are being sent to the paging terminal.
unk node A packet being routed through the TNPP card did not have a destination.
This may occur because the destination node address has not been
programmed into the card’s oparam node table. It also may occur if a
packet has been routed to a simplex input-only port.