Qsim/Fam Alarms; Working With History Alarms; Viewing And Printing History Alarms - 3Com 3C63400-3AC-C - PathBuilder S700 Switch Reference Manual

Working with History
Alarms
Table 44 DSX-1/E1 CBR Module Alarms (continued)
Transmit FIFO The cell bus is congested, and
Overflow cells are backed up on the CBR.
Traffic at the output side of the
CBR port is being transmitted
more slowly than it is being
received from the cell bus. As a
result, the output buffer is
overflowing. In general, the
problem is that the CBR
connection is not synchronized
end-to-end. The clock rate of
the output port does not
match the clock rate of the
device from which the traffic
originated.
VC RDI Receive VC RDI (Remote Defect
Indication) OAM received in
the connection. The far end
equipment has a problem with
the signal it is receiving,
indicating that the problem lies
between the network provider
and the far end terminal
equipment for this connection.

QSIM/FAM Alarms

Table 45 describes the alarms specific to QSIMs and FAMs
Table 45 QSIM Alarms
Alarm Meaning
LMI Link Down The Local Management
Interface has taken the link
down.
The PathBuilder S700 captures all alarms and information events and keeps them
in an alarm history file. This file can hold up to 300 events; it fills on a
first-in/first-out basis. We recommend that you routinely view the alarm history file
before events are lost. We also recommend that you print the file for comparison
with previous history files and entry into your maintenance log.

Viewing and Printing History Alarms

To view and print an alarm history, follow these steps:
1 From the Main menu, select [3] Fault Management to display the Fault
Management menu shown earlier in Figure 163.
2 Select [3] Display History Alarms to view the alarm history. Figure 165 shows a
representative Display History Alarm screen.
Managing System Alarms
The entire CBR connection must be
synchronous end-to-end. Make sure
the clock rates of the devices at either
end of the connection match each
other and match the transmit clock rate
of the CBR ports on the PathBuilder
device.
Check for a defective cable between
the far end interface port and your
service provider's network interface
unit. An open transmit line can cause
this condition.
Troubleshooting Steps
Check the LMI protocol configuration
for the port.
219