Navigation: Fault Management > Alarm >
Description
The MTU board is not running. Possible causes are as follows: The MTU is restarted after the command such as reset board slot, reset card slot, or debug upgrade slot is executed. The MTU is removed. The MTU is restarted because an exception occurs.
Attribute
Alarm ID |
Alarm Severity |
Alarm Type |
306008016 |
Critical |
Equipment alarm |
Parameters
Name |
Meaning |
Slot |
Slot number |
Impact on the System
Users cannot make calls.
System Actions
None.
Procedure
1.Check whether the MTU is installed.
a.If the MTU is installed=>2.
b.If theMTU is not installed, install it and wait until the startup is complete=>4.
2.Replace the MTU and wait until the startup is complete. Then run the show board command to check the MTU status.
a.If the MTU is in OK state=>4.
b.If the MTU is in FAULT state=>3.
3.Install theMTU in an vacant slot and run the config add board command. Wait until the startup is complete and check the MTU status.
a.If the MTU is in OK state=>4.
b.If the MTU is in FAULT state=>5.
4.Check whether the alarm is cleared automatically.
a.If no=>5.
b.If yes, no further action is required.
5.Contact after-sales engineers.
6.End.
Clearing
When the fault is eliminated, the system will auto-clear the alarm. Manual clearing is not required.
Parent Topic: Alarm