Add_workflow_for_techpubs | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Additional sections:
|
...
Traps are faults/events that SNMP devices reportsreport. All SNMP traps are not alarms, howeverbut, all alarms are SNMP traps. However, SIP call failure is a trap and not an alarm.
SNMP Traps tagged as alarms are displayed through CLI. However, it is generated only when the parameter trapTarget
is configured.
Note | ||||
---|---|---|---|---|
| ||||
To configure trapTarget using CLI, refer How to Configure SNMP Trap Targets To configure trap Target using EMA, refer SNMP - Trap Target To configure traps using EMS, refer SNMP Trap Management |
To view the trapsthe related alarms, execute the command:
Code Block |
---|
show table alarms currentStatus |
...
A trap is considered as an alarm only if it notifies a hardware fault, or a fault that requires manual intervention, or certain conditions that lights up the SBC LEDs. In other cases (such as SIP call failure) it is only a trap and not alarm. Alarms are displayed in CLI, EMA, and for major/critical alarms on the SBC itself through LEDs.”when there is a condition that needs attention by the operator. Some alarms are cleared by themselves, such as a port up/down alarm. Other alarms require manual intervention to clear.
Alarms provide alerts/warnings of Alarms are warnings that indicate an abnormal activity such as a software failures, system faults, exceptions, hardware issues, and so on. Alarms are primarily viewed using the CLI and EMA interfaces. But some major and critical alarms are viewed through LEDs on also have LED indicators on the SBC.
SBC displays alarms according to the following categories:
...
For additional details with viewing alarms and configuring SBC for alarms, refer:
...