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).
Example for Configuring FM

Example for Configuring FM

This section describes how to configure FM.

Networking Requirements

As shown in Figure 20-1, a user logs in to the Device. To help rapidly locate faults and rectify the faults that occurred on the network, configure FM.

Figure 20-1 Configuring FM

Configuration Roadmap

The configuration roadmap is as follows:

  • Configure a suppression period for an alarm

  • Edit and applying an alarm filtering table

Data Preparation

To complete the configuration, you need the following data:

  • Alarm name

  • Alarm suppression period

  • Name of the alarm filtering table

  • Alarm severity

  • Name of the NMS host

Procedure

  1. Enter the alarm management view.

    <HUAWEI> system-view
    [~HUAWEI] sysname Device
    [*HUAWEI] commit
    [~Device] alarm

  2. Configure the severity and suppression period of the alarm named hwOpticalInvalid.

    # Set the severity of the alarm named hwOpticalInvalid to Critical.

    [~Device-alarm] alarm-name hwBTBChassisRunningModeConflict severity critical

    # Set the generation period to 5s and clearing period to 15s for the alarm named hwOpticalInvalid in alarm suppression.

    [*Device-alarm] suppression alarm-name hwBTBChassisRunningModeConflict cause-period 5
    [*Device-alarm] suppression alarm-name hwBTBChassisRunningModeConflict clear-period 15
    [*Device-alarm] commit

    After the configuration is complete, run the display alarm information name hwBfdSessReachLimit command to verify the configuration.

    [~Device-alarm] display alarm information name hwBTBChassisRunningModeConflict
    --------------------------------------------------------------------------------
    Feature             : DEVM
    AlarmName           : hwBTBChassisRunningModeConflict
    AlarmId             : 0x801002B
    Severity            : Critical
    Cause Suppress Time : 5
    Clear Suppress Time : 15                                                          
    --------------------------------------------------------------------------------

  3. Edit the alarm filtering table.

    # Create an alarm filtering table named mask1 and enter the mask1 view.

    [~Device-alarm] mask name mask1

    # Configure filtering rules.

    [*Device-alarm-mask1] mask feature-name PMSERVER
    [*Device-alarm-mask1] mask severity minor
    [*Device-alarm-mask1] mask severity warning
    [*Device-alarm-mask1] commit

    # After the configuration is complete, run the display this command in the mask1 view to verify the configuration.

    [~Device-alarm-mask1] display this
      mask alarm-name PmThresholdAlarm
      mask severity Minor
      mask severity Warning

  4. Apply the alarm filtering table.

    # Configure the NMS host named target-host1 to use the alarm filtering table named mask1.

    [~Device-alarm-mask1] quit
    [~Device-alarm] snmp target-host target-host1 mask name mask1
    [*Device-alarm] commit

    # After the configuration is complete, run the display this command in the alarm management view to verify the configuration.

    [~Device-alarm] display this
     snmp target-host target-host1 mask name mask1

  5. (Optional) Configure correlative alarm suppression to prevent the system from sending hwBTBChassisRunningModeConflict's correlative alarms to an NMS named aaa123 with IP address 192.168.3.1.

    [~Device-alarm] correlation-analyze enable
    [*Device-alarm] alarm correlation-suppress enable target-host 192.168.3.1 securityname aaa123

Example

#
 sysname Device
#                                                                               
alarm                                                                           
 suppression alarm-name hwBTBChassisRunningModeConflict cause-period 5                            
 suppression alarm-name hwBTBChassisRunningModeConflict clear-period 15                           
 alarm-name hwBTBChassisRunningModeConflict severity Critical                               
 snmp target-host target-host1 mask name mask1                                  
 #                                                                              
 mask name mask1                                                                
  mask severity Minor                                                           
  mask severity Warning                                                         
  mask alarm-name PmThresholdAlarm                                              
#                                                                           
return                                                                          
Download
Updated: 2019-01-02

Document ID: EDOC1100058392

Views: 15206

Downloads: 25

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