Page History
| Panel | ||||
|---|---|---|---|---|
In this section:
|
Overview
The
| Spacevars | ||
|---|---|---|
|
| Field | Description |
|---|---|
| Severity |
Represents the severity level assigned by the device and is displayed in bold green font directly underneath the alarm name. Possible severity levels are: Critical, Major, Minor, and Informational. See Severity Mapping Rules below. | |
| Definition |
| Describes the purpose of the alarm. | |
| Impact |
| Describes the impact to the system when the indicated failure or fault occurs. | |
| Action |
| Details the action to be taken by the operator to eliminate/prevent the failure condition. When appropriate, step-by-step procedures will be provided. Traps do not have clearing events. | |
| Clearing |
This field identifies how an alarm clears from the Fault Manager Event List. Alarm clearing is either automatic or manual. |
The clearing status of alarms in the SBC documentation is based on how a generic OAM trap manager behaves (i.e., the SBC generates fault alarms and clearing alarms, and the fault alarms are removed from an OAM display when the clearing alarms arrive). However, the SBC has no means to specify how/when to remove clearing alarms from an OAM display; therefore, they are defined as manual clearing. Alternatively, the EMS uses proprietary logic to remove entries from the Fault Manager display including alarms that are defined as manual clearing. For example, any alarms in the following EMS file with a number "2" defined after the alarm name will clear over time automatically:
| ||
| Repetition | Identifies if an alarm is repeated for each occurrence of a particular failure relating to the same managed object instance. When appropriate, repetition interval information is included in this field. | |
| Instance Fields |
| By default, all alarms are instanced by a source host and trap type. For some alarms, an Instance ID field is included to uniquely identify the alarms. The Instance ID is created by appending values of the instance fields to the fault instance information. In this Guide, when instance fields exist for an alarm, the Instance Fields category in the alarm description is populated with one or more instance fields. | |
| Event Code(s) |
| Identifies detailed event information contained in the alarm (event levels and classes, threshold types, clearing strings, and so forth). This field may not always be included. |
Refer to Dashboard - Alarms to learn more about viewing alarms from the EMA.
| Anchor | ||||
|---|---|---|---|---|
|
The following table describes the rules used to map the SonusEventLevel to EMS display severity level. EMS severity names are color-coded to correspond with the EMS GUI alarm color convention.
| SonusEventLevel | Description | Action to Take | EMS Severity | ||||
|---|---|---|---|---|---|---|---|
| critical | Call impairment is either already occurring or is imminent | Requires immediate operator action. Contact
| CRITICAL | ||||
| major | Future call impairment is a significant concern. | Take action as soon as possible. Contact
| MAJOR | ||||
| minor | Low-impacting situations or conditions. Normally, calls/revenue are not impacted by these low-severity events. | Determine if error is routine (minor), or indicative of a significant problem. | MINOR | ||||
| informational | Intended to help the user identify potential future problems. | Usually requires no immediate operator action. | WARNING |
| Pagebreak |
|---|
Overview
Content Tools