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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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

This section describes how to configure fault management.

Setting the Alarm Severity

Context

The system defines default alarm severity for each alarm. Users can change the alarm severity. When receiving alarms reported by a device, the NMS can configure filtering rules to display only alarms of a specified severity.

Alarm severities are defined as follows:
  • Critical: indicates that a fault affecting services has occurred and it must be rectified immediately. For example, a critical alarm is generated to notify users that a managed object fails to work and the fault must be rectified.

  • Major: indicates that services are being affected and related measures need to be taken urgently. For example, a major alarm is generated to notify users that performance of a managed object seriously degrades and all the capabilities of the managed object must be restored.

  • Minor: indicates that a fault occurs but does not affect services. To avoid more serious faults that affect services, related measures must be taken.

  • Warning: indicates that a potential or impending service-affecting fault is detected before any significant effect has been felt. Take corrective actions to diagnose and rectify the fault.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    alarm

    The alarm view is displayed.

  3. (Optional) Run:

    display alarm information [ name alarm-name ]

    The alarm severity is displayed.

  4. Run:

    alarm alarm-name severity severity

    The alarm severity is changed.

    The system has defined default alarm severity for each alarm.

  5. Run:

    commit

    The configuration is committed.

Configuring the Alarm Reporting Delay Function

Context

When an alarm is reported repeatedly, users cannot locate faults in an efficient manner. After the alarm reporting delay function is enabled and the delay is configured, a large number of invalid alarms are prevented from being reported.

After the alarm reporting delay function is enabled,

  • If no clear alarm is generated during the period, the alarm is reported to the NMS when the period expires.
  • If a clear alarm is generated during this period, the alarm and its clear alarm 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 view is displayed.

  3. Run:

    delay-suppression enable

    The alarm reporting delay function is enabled.

    By default, the alarm reporting delay function is enabled.

  4. (Optional) Run:

    suppression alarm alarm-name { cause-period cause-seconds | clear-period clear-seconds }

    The delay in reporting alarms is configured.

    The system defines a default delay in reporting alarms.

    NOTE:
    • To set the delay in reporting an active alarm, select the cause-period parameter. To set the delay in reporting a clear alarm, select the clear-period parameter.

    • To view the default delay in reporting alarms, run the undo suppression alarm alarm-name { cause-period | clear-period } and display alarm information [ name alarm-name ] commands in sequence.

  5. Run:

    commit

    The configuration is committed.

Configuring Alarm Correlation Suppression

Context

Before configuring alarm correlation suppression, enable alarm correlation analysis to analyze alarm types including root-cause and non-root-cause. For a non-root-cause alarm, the system marks the sequence number of its root-cause alarm on the non-root-cause alarm. After alarm correlation suppression is configured, the system filters out non-root-cause alarms and reports only root-cause alarms to the NMS.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    alarm

    The alarm view is displayed.

  3. Run:

    correlation-analyze enable

    Alarm correlation analysis is enabled.

    By default, alarm correlation analysis is disabled.

  4. Run the following commands to configure NMS-based alarm correlation suppression.

    • Run:

      alarm correlation-suppress enable target-host ip-address securityname { securityname | cipher securityname } [ vpn-instance vpn-instance-name ]

      Alarm correlation suppression based on the NMS IPv4 address is enabled.

    • Run:

      alarm correlation-suppress enable target-host ipv6 ipv6-address securityname { securityname | cipher securityname }

      Alarm correlation suppression based on the NMS IPv6 address is enabled.

    By default, NMS-based alarm correlation suppression is enabled.

  5. Run:

    commit

    The configuration is committed.

Checking the Configuration

Context

  • Run the display alarm information [ name alarm-name ] command to view the specified alarm configuration.

  • Run the display event information [ name event-name ] command to view the specified event information.

  • Run the display this command in the alarm view to view the alarm configuration.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 58786

Downloads: 3621

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