3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-11
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
The alarm cause indicates the probable cause, which can result from a problem
on a related object lower in the hierarchy, even though no alarms are reported
against it. However, the problem may be caused by the state conditions of the
affected object itself.
2 To view the affected object states, click on the Affected Objects tab button,
select an object and click on the View Object button.
a If the Administrative State is Up and the Operational State is Down, there are
two possibilities:
• The affected object is the root cause of the problem. The alarm probable
cause is the root cause. See section 3.5 for additional information about
the alarm, which may help to correct the problem. When the problem is
fixed, all correlated alarms are cleared. See section 3.4 for a sample
equipment problem.
• The affected object is not the root cause of the problem. The alarm
probable cause does not provide the root cause of the problem. The root
cause is with a related, supporting object that is lower in the managed
object hierarchy. Perform Procedure 3-6 to review related object
information.
b If the Administrative State is Up and the Operational State is not Up or Down
but states a specific problem such as Not Ready or MTU Mismatch, this is the
root cause of the alarm. Correct the specified problem and all correlated
alarms should clear. See section 3.4 for a sample configuration problem. If
alarms still exist, perform Procedure 3-6.
c If the object Administrative State is Down, it is not the root cause of the
alarm on the object; however, it may cause alarms higher in the network
object hierarchy. Change the Administrative State to Up. See section 3.4 for
a sample underlying port state problem. This does not clear the alarm on the
affected object that you are investigating. Perform Procedure 3-6 to review
related object information.
To Next Page
Loading...
