No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OSN 500 550 580 V100R008C50 Alarms and Performance Events Reference 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Alarm Management

Alarm Management

When a network is operating abnormally, the NMS notifies the situation to the maintenance personnel, who can take immediate measures to recover the network.

Alarm management consists of the following functions:

  • Network-wide alarm monitoring and remote alarm notification enable the U2000 to notify maintenance engineers of network exceptions in a timely manner so that the engineers can rectify faults quickly.
  • Alarm/Event relevance analysis, alarm masking, alarm filtering, alarm suppression, automatic alarm reporting, alarm reversion, and maintenance experience databases improve the effectiveness and efficiency of alarm handling.
  • Alarm synchronization ensures the reliability of alarms.

Alarms can be reported in the following cases:

  • A board detects and reports the alarms to the NE software.
  • The NE software reports the alarms to the NMS server.
  • The users query the alarms on the NMS server through the NMS client.

In the alarm reporting process, an alarm goes through the following procedures before it is stored by the NMS:

  • Alarm/Event relevance analysis
  • Automatic alarm reporting
  • Alarm suppression
  • Alarm masking
  • Alarm filtering
  • Alarm reversion
  • Alarm/Event redefine

Alarm/Event Relevance Analysis

In the alarm/event relevance analysis procedure, the NMS analyzes the alarms reported within a period, identifies the root alarms and correlative alarms based on certain rules, and displays the analysis results. Root alarms cause correlative alarms. If root alarms are cleared, correlative alarms clear automatically.

The alarm/event relevance function identifies root alarms and correlatives alarms, allowing the maintenance personnel to focus on root alarms in troubleshooting and therefore improving the troubleshooting efficiency.

The alarm/event relevance function provides alarm relevance on NEs, alarm relevance on the NMS, and user-defined alarm relevance.

Automatic Alarm Reporting

If automatic alarm reporting is enabled on an NE, the NE-side alarms can be reported to the NMS immediately after they occur. Users can view the alarm information that is automatically displayed on the NMS. This function can be disabled for minor alarms to reduce the impacts of alarm information on the NMS performance.

Alarm Suppression

The NMS provides the alarm suppression function. If this function is enabled for an alarm, the NE does not report the alarm.

Alarm Masking

This function masks minor alarms to avoid unnecessary alarm information.

During the maintenance, testing or deployment of an NE, numerous alarms may be reported and there is no need to care about them. In this case, the alarm masking function can be used to mask the alarms so that the NMS does not display or store the alarm information.

Figure 1-2 provides the differences between alarm suppression and alarm masking.

  • If alarm suppression is enabled for an alarm, the NE does not report the alarm.
  • If alarm masking is enabled for an alarm, the NE still reports the alarm but the NMS discards the alarm information.
Figure 1-2  Differences between alarm suppression and alarm masking

Alarm Filtering

To avoid redundant alarm information, alarm filtering can be enabled for a specific NE on the NMS. The NMS filters the alarm information based on alarm name, object, severity, status, type, latest report time, clear time and other conditions. This function improves alarm browsing efficiency without affecting NE-side alarm reporting. The filtering conditions which users are concerned about can be added to alarm filtering templates. Selecting an alarm filtering template allows multiple required conditions to be applied at a time.

If alarm filtering is enabled for an alarm, the NMS discards the relevant alarm information; if alarm filtering is disabled for an alarm, the NMS receives and records the relevant alarm information.

Alarm Reversion

In the case of a port for which services are not activated, the alarm reversion function can be used to prevent relevant alarm information from being generated and thus to prevent interferences from the generated alarms. When the alarm reversion function is enabled, you can set the alarm status of this port to be opposite to the actual status. That is, an alarm is reported when no alarm occurs and no alarm is reported when alarms occur.

There are three modes of alarm reversion: non-revertive, auto-revertive, and manual-revertive mode.

  • Non-revertive: This is the normal alarm monitoring state, and is the default alarm mode. In this mode, the alarm reversion function cannot be enabled for a port.
  • Auto-revertive: In this mode, the alarm reversion function can be enabled only on a port that reports alarms. After the alarm reversion function is enabled, the port enters the alarm revertive mode, and does not report alarms. When the current alarms are cleared, the port automatically exits the revertive mode, and the alarm state reported by the port is restored to be the actual alarm state.
  • Manual-revertive: In this mode, the alarm reversion function can be enabled on a port, regardless of whether any alarms exist on this port.
    • When the alarm reversion function is enabled on a port, the alarm state reported by the port is inconsistent with the actual alarm state.
    • When the manual-revertive mode is disabled, the alarm reversion mode is restored to be the non-revertive mode. The alarm state reported by the port is consistent with the actual alarm state.

The precautions for setting the alarm reversion function are as follows:

  • The alarm state of the board, including the state of the alarm indicators on the board, remains unchanged, which indicates the running state of the equipment.
  • The alarm reversion function is realized by the NE software. The alarm data on the NE and on the NMS is the same, which indicates the alarm state after the alarms are reversed.

Alarm/Event Redefine

The U2000 can redefine attributes of all alarms or events, such as level, name, and type, to locate and maintain alarms more effectively. For example, you can decrease the severities of the alarms/events that do not require attention and increase the severities of the alarms/events that require attention.

The redefinition of alarm/event names takes effect for all NEs. It cannot take effect for only the specified NEs. The redefinition of types and severities can take effect for either the specified NEs or all NEs.

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 75977

Downloads: 138

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next