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

NE40E-M2 V800R010C10SPC500 Configuration Guide - System Management 01

This is NE40E-M2 V800R010C10SPC500 Configuration Guide - System Management
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).
Configuring Fault Management

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

Configuration Procedures

Perform one or more of the following configurations as required.

Setting the Alarm Severity

You can change the default alarm severity.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run alarm

    The alarm management view is displayed.

  3. Run alarm-name alarm-name severity { critical | major | minor | warning }

    The alarm severity is set.

    If you are concerned about certain types of alarms, you can set the highest severity for these types of alarms and configure filtering conditions. In this manner, the system reports only these types of alarms to the NMS.

  4. Run commit

    The configuration is committed.

Configuring a Suppression Period for an Alarm

You can configure a suppression period for an alarm to prevent the alarm from being reported frequently.

Context

Alarm reporting frequently affects fault locating efficiency. To prevent the system from reporting a large number of invalid alarms, you can enable delayed alarm reporting and configure a suppression period for an alarm, so that the alarm is not reported to the NMS within the period.

After a suppression period is configured for an alarm, the following situations occur:

  • If the alarm is generated but its clear alarm is not generated, the alarm is reported to the NMS only after the suppression period elapses.
  • If both the alarm and its clear alarm are generated during this period, they are both deleted from the alarm queue and will not be reported to the NMS.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run alarm

    The alarm management view is displayed.

  3. Run suppression alarm-name alarm-name { cause-period cause-seconds | clear-period clear-seconds }

    A suppression period is configured for an alarm.

    cause-period cause-seconds specifies the period after which a generated alarm is reported.

    clear-period clear-seconds specifies the period after which a generated clear alarm is reported.

  4. Run commit

    The configuration is committed.

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.

Context

Alarm suppression has the following impacts on the system:

  • When alarm suppression is enabled, alarm suppression takes effect, and you can configure an alarm suppression period.
  • When alarm suppression is disabled, alarm suppression does not take effect in the system.

By default, alarm suppression is enabled.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run alarm

    The alarm management view is displayed.

  3. Run delay-suppression enable

    Alarm suppression is enabled.

    To disable alarm suppression, run the undo delay-suppression enable command.

    Do not leave alarm suppression disabled. Otherwise, a large number of redundant alarms will be generated.

  4. Run commit

    The configuration is committed.

Filtering Out All Alarms

Terminal users can filter out all alarms.

Context

Terminal users include command line users and NMS users. If terminal users do not expect any alarms sent from the device, they can filter out all alarms.

Procedure

  • Command line users run the undo terminal alarm command in the user view to filter out all alarms.
  • NMS users on the host named host-name perform the following operations to filter out all alarms:

    1. Run the system-view command to enter the system view.
    2. Run the alarm command to enter the alarm management view.
    3. Run the undo alarm snmp target-host host-name command to 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 concern about.

Context

Terminal users include command line users and NMS users. Different users are concerned about different types of alarms. Terminal users can configure an alarm filtering table to filter out the unwanted alarms.

Flexible filtering rules can be defined in an alarm filtering table.

  • Filtering out alarms with the specific severity, such as alarms with the severity lower than Major
  • Filtering out alarms that are generated for a specific service, such as alarms for the MPLS service
  • Filtering out alarms with specific names, such as an LDP session alarm

Different terminal users can share the same alarm filtering table, but each terminal user can use only one alarm filtering table.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run alarm

    The alarm management view is displayed.

  3. Run the mask slot slot-id [ card card-id ] command to masks hardware alarms about a specified board or card. Run the undo mask slot slot-id [ card card-id ] command to cancel the configuration.
  4. Run mask name mask-name

    The alarm filtering table view is displayed.

  5. Run one or more of the following commands to filter out specific alarms:
    • Run the mask alarm-name alarm-name command to filter out a specific alarm.

      To filter out multiple alarms with specific names, you need to run this command multiple times. Run the undo mask alarm-name alarm-name command to cancel the configuration.

    • Run the mask feature-name feature-name command to filter out an alarm for a specific service.

      To filter out multiple alarms for specific services, you need to run this command multiple times. Run the undo mask feature-name feature-name command to cancel the configuration.

    • Run the mask severity { Critical | Major | Minor | Warning } command to filter out an alarm with specific severity.

      The severity of an alarm can be Critical, Major, Minor, or Warning. To filter out multiple alarms with specific severity levels, run this command multiple times. Run the undo mask severity { Critical | Major | Minor | Warning } command to cancel the configuration.

  6. Run quit

    Return to the alarm management view.

  7. Run either of the following commands based on the specific terminal user type and function:

    • Command line users run the terminal mask name mask-name command to filter out specific alarms.
    • NMS users on the host named host-name run the snmp target-host host-name mask name mask-name command to filter out specific alarms.

  8. Run commit

    The configuration is committed.

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.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run alarm

    The alarm management view is displayed.

  3. Run reverse mode auto-resume

    The alarm inversion mode is set to automatic recovery.

  4. Run reverse

    The alarm inversion view is displayed.

  5. Run reverse interface interface-type interface-number

    Alarm inversion is enabled on an interface.

  6. Run commit

    The configuration is committed.

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.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run alarm

    The alarm management view is displayed.

  3. Run correlation-analyze enable

    Alarm correlation analysis is enabled.

    This function must be enabled before you configure correlative alarm suppression.

  4. Run alarm correlation-suppress enable target-host ip-address securityname securityname [ vpn-instance vpn-instance-name ]

    NMS-based correlative alarm suppression is enabled.

Verifying the Fault Management Configuration

After configuring FM, verify the configuration, including the feature for which the alarm is generated, alarm name, alarm ID, alarm severity, and alarm suppression period.

Prerequisites

FM has been configured.

Procedure

  • Run the display alarm active root command to check active root alarms.
  • Run the display alarm information [ name alarm-name ] command to check alarm parameters.

Example

Run the display alarm active root command. The command output shows active root alarms.

<HUAWEI> display alarm active root
1:Critical  2:Major  3: Minor  4:Warning
--------------------------------------------------------------------------------
Sequence   AlarmId    Level Date Time  Description                              
--------------------------------------------------------------------------------
6          0xD300007  2     2013-01-08 The storage usage exceeded the pre-set ov
                             09:13:16  erload threshold.(TrapSeverity=4, Probabl
                                       eCause=75265, EventType=3, PhysicalIndex=
                                       17956865, PhysicalName=IPU slot 1, Relat
                                       iveResource=cfcard, UsageType=5, SubIndex
                                       =1, UsageValue=89, Unit=1, UsageThreshold
                                       =85)                                     
--------------------------------------------------------------------------------

Run the display alarm information name pmthresholdalarm brief command. The command output shows basic information about an alarm named PmThresholdAlarm.

<HUAWEI> display alarm information name pmthresholdalarm
Feature             : PMSERVER
AlarmName           : PmThresholdAlarm
AlarmId             : 177209348
Severity            : Major
Cause Suppress Time : 1
Clear Suppress Time : 1
Download
Updated: 2019-01-02

Document ID: EDOC1100058392

Views: 15161

Downloads: 24

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