Configuring Fault Management

You can configure FM on a device to use the alarm filtering, alarm delivery, and alarm suppression functions.

Usage Scenario

As the network scale expands, the network becomes increasingly complex, and therefore more network configurations and applications are deployed. If a module on a device fails, multiple alarms may be generated on one or more devices. The devices and NMS, however, may not be able to process all alarms, causing alarm loss during the alarm transmission. If some alarms that users are concerned about cannot be obtained, network management becomes difficult. FM dynamically manages and reports alarms generated on devices in a centralized manner.

The NetEngine 8000 F supports the following FM functions:

Filters out repeated alarms, intermittent alarms, and flapping alarms.
Filters out the alarms that users are not concerned about.
Displays alarm configurations, active alarms, historical alarms, and alarm statistics to present details about network faults.
Clears historical alarms to simplify the alarm display.
Simulates and reports alarms to check whether the terminal and NMS host are correctly configured and whether the management link is reachable.

Pre-configuration Tasks

Before configuring FM, complete the following tasks:

Install the router and power it on properly.
Complete the alarm definition on the NetEngine 8000 F.

Setting the Alarm Severity: You can change the default alarm severity.

Configuring a Suppression Period for an Alarm: You can configure a suppression period for an alarm to prevent the alarm from being reported frequently.

Configuring Alarm Suppression: The system suppresses repeated alarms, flapping alarms, and intermittent alarms by default. You can disable alarm suppression of alarms that you are concerned about, hardware alarms, and ambient alarms.

Filtering Out All Alarms: Terminal users can filter out all alarms.

Configuring an Alarm Filtering Table to Filter Out Alarms: This section describes how to edit and apply an alarm filtering table. An alarm filtering table can be used by different terminal users to filter out the alarms that they are not concerned about.

Configuring Alarm Inversion: If you do not want an interface to generate loss alarms for services that have been deployed but not accessed, configure alarm inversion.

Configuring NMS-based Correlative Alarm Suppression: This section describes how to configure NMS-based correlative alarm suppression. This function enables the system to filter out NMS-based correlative alarms and only reports root alarms to an NMS.

Enabling Alarm Status Re-check: After you enable alarm status re-check for a device, the device re-checks the status of a specified type of status change alarm and reports alarms again.