Avaya DEFINITY Server CSI Maintenance Manual page 1817

Table of Contents

Advertisement

UDS1-BD (UDS1 Interface Circuit Pack)
Table 536. TEST #144 Slip Alarm Inquiry Test — Continued
Error
Test
Code
Result
PASS
No Slip alarm is detected on the UDS1 Interface circuit pack.
0
NO
The test could not relate the internal ID to the port (no board). This could be
BOARD
due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
This should re-establish the linkage between the internal ID and the port.
Misframe Alarm Inquiry Test (#145)
Misframe Alarm indicates that framing bits observed on a UDS1 Interface circuit
pack are in error. The Misframe Alarm Inquiry Test queries the total number of
misframes that have occurred on a DS1 Interface circuit pack since the last
inquiry.
When the DS1 Interface circuit pack detects a misframe error, it increments its
misframe counter by one. If the counter reaches a specified threshold (i.e., 17), a
MISFRAME-COUNT message is automatically sent to the switch maintenance
software. After the maintenance software receives the MISFRAME-COUNT
message, the Misframe Alarm Inquiry Test is initiated to collect the misframe
counts from the UDS1 Interface circuit pack.
When the threshold of misframes is reached, if the UDS1 Interface circuit pack is
supplying the system synchronization source, then a switching synchronization
source message is sent to the TDM Bus Clock. See TDM-BUS (TDM Bus)
Maintenance documentation for details. A Minor alarm against the UDS1 Interface
circuit pack is raised, but all trunks or ports of the UDS1 Interface circuit pack
remain in the in-service state.
555-233-119
Description/ Recommendation
1. Ensure that the board translations are correct. Execute the add ds1
UUCSS command to administer the UDS1 interface if it is not already
administered.
2. If the board was already administered correctly, check the error log to
determine whether the board is hyperactive. If this is the case, the board
is shut down. Reseating the board will re-initialize the board.
3. If the board was found to be correctly inserted in step 1, then issue the
busyout board command.
4. Issue the reset board command.
5. Issue the release busy board command.
6. Issue the test board long command.
Continued on next page
Issue 5 October 2002
1817

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents