PDATA-PT (Packet Data Line Port)
Issue 1 May 2002
8-877555-233-142
c. These three counters are incremented for errors which may or may not be
caused by the PDATA port itself. For example, the Invalid LAP-D Frame
counter (error type 513) could exceed threshold due to a large number of
“bad CRC” errors. The errors could be caused by packets arriving from the
“other end” which have a bad CRC, in which case the PDATA port is
behaving properly and should not be alarmed. On the other hand, the error
could be caused by faulty CRC-checking hardware on the PDATA board, in
which case the PDATA board should be alarmed.
Since these error counters do not necessarily indicate problems with the
PDATA port itself, no alarms are raised when the counters exceed
threshold. Instead, testing escalates to the LAP-D Connectivity test. If the
LAP-D Connectivity test fails repeatedly, then the PDATA port is the source
of the problem and will be alarmed. More exhaustive tests can be run with
the reset board UUCSS command.
d. This error occurs if the switch has trouble in writing the translation data into
memory. A MINOR alarm is raised if this error occurs. This alarm indicates
the failure of either the Angel hardware or the RAM on the board. If the
Angel is the cause of the failure, similar alarms should be raised against
every other port on the board. If the RAM is the cause of the failure, then
only the port is affected — other ports may function normally.
No associated test can retire this alarm. The repair procedure for this
alarm is as follows. First, reset the circuit pack (i.e., use busyout board
UUCSS and reset board UUCSS commands). If the circuit pack comes
back into service after the reset (the red LED on the circuit pack is off), then
execute the test port UUCSSpp long clear command to clear the alarm. If
the PDATA circuit pack fails to reset properly (i.e., the red LED is lit on the
circuit pack), replace the circuit pack.
Notice that the corresponding Translation RAM test always passes
because it issues a translation write command but does not wait around for
the failure up-link message from the board.
e. This error occurs when the receive FIFO RAM buffers on a circuit pack
overflow (i.e., the circuit pack receives data from the bus faster than it can
distribute the data to its endpoints). If this error occurs frequently, however,
it may indicate a LAP-D parameter mismatch. LAP-D should be able to
recover from this problem, but it may degrade the performance of the
packet bus. No alarm is raised for this error.
f. This error occurs if the PDATA Port Local Loop-Around test fails. If so, a
MINOR alarm is raised. This alarm indicates the failure of the UART
device on the port. The circuit pack should be replaced if this alarm cannot
be cleared. See the repair procedure for PDATA Port Local Loop-Around
test (#602) for more details.
g. This error occurs if the System Port Connectivity test (#603) fails or if the
System Port connection fails in the call set-up procedure. This error is only
applicable to ports used as a System Port. If this test fails repeatedly, a
MINOR alarm is raised.
To Next Page
Loading...
