ID | Name | Meaning |
---|---|---|
1 | Site No. | Number of the site where the faulty board or module is located Value range: 0-2047 |
2 | Board Type | Number of the type which the faulty board belongs to. 55:IASU |
3 | Board No. | Number of the fault board 0:IASU |
4 | PassNo | Number of the passage where the faulty board is located. |
5 | SubLink No. | Alarm sub-category number 0:E1 port 1 1:E1 port 2 2:E1 port 3 |
6 | Cell Index | Index of the cell where the board or module is located 0-2047: Cell index of the faulty cell in the data configuration 65535: None |
7 | Site Type | Type of the site where the faulty board or module is located 9: BTS3002C |
8 | RackNo | Number of the rack where the faulty board is located. |
9 | BoxNo | Number of the subrack where the faulty board is located. |
10 | SlotNo | Number of the slot where the faulty board is located. |
11 | Site Name | Site Name |
12 | Alarm Attribute | Alarm Character 0:Normal 1:Transient Count |
When the alarm occurs, the BTS services or independent E1 services will be interrupted. The remote maintenance on the BTS is unavailable.
Then check whether the alarm is cleared.
Y=> The alarm handling ends.
N=> Go to Step 2.
This alarm might be triggered once the IOMU is reset. Check the maintenance log of the IOMU to see whether it has been reset.
Y=>The alarm is cleared when the reset of the IOMU is complete. The alarm handling ends.
N=>Go to Step 3.
Check the service configuration for the TU in the IASU to see whether there are some invalid services. If yes, delete them and check whether the alarm is cleared.
Y=> The alarm handling ends.