Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: rebranding

...

Noprint
Panel
borderColorgreen
borderWidth2

In this section:

Table of Contents
maxLevel2
Panel

...

borderColorGreen
bgColorTransparent
borderWidth2

...

Back to Table of Contents

In this section:

Table of Contents
maxLevel2
Info
iconfalse

Related articles:

Overview

The

Spacevars
0series4
alarm notifications are defined by the fields: Severity, Description, Impact, Action, Clearing, Repetition, Instance Fields, and Event Code(s).

  • 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.
  • 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.

...

...

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.

 

SonusEventLevelDescriptionAction to TakeEMS Severity
criticalCall impairment is either already occurring or is imminentRequires immediate operator action. Contact

...

Spacevars
0company
TAC; may require reconnecting cables, replacing components, or rebuilding a drive.
CRITICAL
majorFuture call impairment is a significant concern.Take action as soon as possible. Contact

...

Spacevars
0company
TAC; may require reconnecting cables, replacing components, or rebuilding a drive.
MAJOR
minorLow-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
informationalIntended to help the user identify potential future problems.Usually requires no immediate operator action.WARNING

Pagebreak