The U2000 cannot receive NE alarms. Alarms occur on NEs but are not reported to the U2000. Why?

What type of the NEs?

Reference:

Fault Analysis

• The server disk space is full.
• The database space is insufficient.
• Alarm masking is enabled on NEs, so that alarms are discarded.
• The fault service processes is abnormal.
• The The number of records in the database table has reached the threshold and The Database Usage Is Too High (Critical) alarms are displayed on the U2000, indicating that alarms cannot be dumped in the database. Therefore, alarms cannot be reported to the database.
• The priority of board software is higher than that of NE software.
• The trap IP address for disk array has not bee configured. For a HA system, you need to assign two Trap IP to the disk array. Each Trap IP corresponds to the NMS application IP address configured on each server.
• Other possible causes for Router series, Switch series, PTN 6900 series, Access series and Security NEs are as follows:
  • The SNMP parameters on NEs are incorrect.
  • NEs that do not support fragmentation exist on the network, and SNMP packets that exceed the maximum packet size will be dropped.
  • The firewall on the U2000 server does not allow the UDP 162 port to receive alarms.
  • The Trap sending function is not enabled for the associated feature on NEs.
  • The network is not stable.

Procedure

• Clean up the disk space of the server.
• Manually dump alarm.
  1. Choose Administration > Task Schedule > Task Management from the main menu (traditional style); alternatively, double-click System Management in Application Center and choose Task Schedule > Task Management from the main menu (application style).
  2. In the navigation tree on the left of the Task Management, choose Manual Dump.
  3. In the task list of the Task Management window, right-click Alarm Manual Dump or Event Manual Dump, and then choose Run.
• Modify the rules of alarm masking.
  1. Choose Fault > Settings > Mask Rules from the main menu (traditional style); alternatively, double-click Fault Management in Application Center and choose Alarm Settings > Mask Rules from the main menu (application style).
  2. In the Mask Rule window, view and modify the masking rules.
• Restart the fault service process
  1. Log in to the System Monitor client.
  2. In the main window, click the Service Monitor tab.
  3. On the Service Monitor tab, select FaultService process, click Service Management, and choose Stop the Service from the drop-down list. Alternatively, right-click the desired NE process and choose Stop the Service from the shortcut menu.
  4. In the Confirm dialog box, click Yes.
  5. Wait until the process is stopped by the U2000. After the process is stopped, select the process, click Service Management, and choose Start the Service from the drop-down list. Alternatively, right-click the process and choose Start the Service from the shortcut menu.
  6. After the fault service process is started, U2000 can receive NE alarms.
• Board software downgrade:
  1. Refer to the related chapters of User Guide (NE Software Management).
• Clear the The number of records in the database table has reached the threshold and The Database Usage Is Too High (Critical)alarms .
  1. Clear the The Database Usage Is Too High (Critical) alarm. For details, see ALM-103 The Database Usage Is Too High (Critical).
  2. Clear the The number of records in the database table has reached the threshold alarm. For details, see ALM-120 The number of records in the database table has reached the threshold.
• Perform the following operations if the U2000 cannot receive alarms generated on Router series, Switch series, PTN 6900 series, Access series and Security NEs:
  • Configure SNMP parameters on NEs.
    NOTE:

    Configuring SNMPv3 on routers is used as an example.
    1. Run the following command to log in to the NE CLI:

       • telnet NE IP Address

       • stelnet NE IP Address

       NOTE:

       Using STelnet (if supported) to log in to NEs is recommended.
    2. Run the following command to access the system view:

       system-view

    3. Run the following command to enable SNMP:

       snmp-agent sys-info version v3

    4. Run the following command to configure the SNMP user group:

       snmp-agent group v3 group-name [ authentication | privacy] [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] [ acl acl-number ]

    5. Run the following command to configure SNMP user information:

       snmp-agent usm-user v3 user-name group-name [ [ authentication-mode { md5 | sha } password ] [ privacy-mode des56 password ] ] [ acl acl-number ]

    6. Run the following command to enable the function of sending traps on NEs:

       snmp-agent trap enable

    7. Run the following command to configure the U2000 server, the trap target host:

       snmp-agent target-host trap address udp-domain ip-address [ udp-port port-number | source interface-type interface-number | { public-net | vpn-instance vpn-intance-name } ] params securityname security-string [ v3 authentication | privacy ] [ private-netmanager ] [ notify-filter-profile profile-name | ext-vb ]

       NOTE:

       The v3 version in the command must be consistent with the in-use SNMP version. Otherwise, the U2000 fails to receive the traps sent by NEs.

    8. Run the following command to specify the source interface that sends traps:

       snmp-agent trap source interface-type interface-number

       NOTE:

       Ensure that an IP address is assigned to the source interface for sending trap packets and the IP address is reachable for the U2000.

  • Run the snmp-agent packet max-size byte-count command to set the SNMP packet size to prevent NEs that do not support fragmentation from discarding packets.
  • Configure that the firewall on the U2000 server allows UDP port 162 to receive alarms.
  • Perform the following operations to restart the TrapReceiver0101 process of the U2000:
    1. Choose Start > Run. In the Run dialog box, enter services.msc and press Enter.
    2. In the Services window, right click Internet Connection Sharing (ICS) and choose Stop from the shortcut menu.
    3. Right click Internet Connection Sharing (ICS) and choose Properties from the shortcut menu. In the dialog box that is displayed, set Startup type to Manual and click OK.
    4. Open the Windows Task Manager and click the Processes tab.
    5. Right click EmfTrapReceiver.exe and choose End Process from the shortcut menu.
    6. In the dialog box that is displayed, click End Process.
    7. Log in to the System Monitor client.
    8. Right click TrapReceiver0101 on the Service Monitor tab and choose Start the Service from the shortcut menu.
  • Run the following command to enable the Trap sending function for the associated feature on the NE:

    snmp-agent trap enable feature-name feature-name [ trap-name trap-name ]

    NOTE:

    Using sequence numbers to ensure alarm reliability is recommended. If devices and the VRP platform versions do not support the sequence number, use the Inform mode.

    Using sequence numbers can ensure alarm reliability and prevent alarm loss. Perform the following operations:

    Configuration on the U2000

    1. Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
    2. Choose System Management > NE Channel Management > Trap Service from the service tree.
    3. On the Trap Service tab page, click Synchronize to synchronize alarms from the NE.
    4. Right-click and choose Create from the shortcut menu. In the dialog box that is displayed, set the associated parameters and click Huawei OSS and Extended VB.
       
       
       
    5. Click OK.

    Configuration on the NE

    1. Run the following command to access the system view:

       system-view

    2. Run the following command to start the SNMP agent:

       snmp-agent

    3. Run the following command to add the private-netmanager option to the destination host of the NE:

       snmp-agent target-host trap address udp-domain X.X.X.X params securityname privacy v3 private-netmanager ext-vb

       NOTE:

       • X.X.X.X specifies the IP address of the destination host. Here, set it to the IP address of the U2000 server.
       • If the NE has been configured with the private-netmanager attribute before sending an alarm, the NE alarm generation time recorded on the U2000 is the same as that recorded on the NE. If the NE has not been configured with the private-netmanager attribute before sending an alarm, the NE alarm generation time recorded on the U2000 is the U2000 server time when the U2000 receives the trap packet from the NE.
       • If the SNMPv3 protocol is not used, add cipher next to the securityname. SNMPv3 is recommended because it is more secure.

• Perform the following operations if the U2000 cannot receive alarms generated on MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except PTN 6900 series) and marine series NEs:
  • Disable alarm suppression.
    1. Right-click an NE in the Main Topology and choose NE Explorer from the shortcut menu.
    2. Select an NE in the NE Explorer and choose Alarm > NE Alarm Suppression from the function tree. Alternatively, select a board in the NE Explorer and choose Alarm > Alarm Suppression from the function tree.
    3. Change the value of Status to Not Suppressed for the associated event.
  • Configure automatic alarm reporting.
    1. Right-click an NE in the Main Topology and choose NE Explorer from the shortcut menu.
    2. Select an NE in the NE Explorer and choose Alarm > Alarm Severity and Auto Reporting from the function tree. Alternatively, select a board in the NE Explorer and choose Alarm > Alarm Severity and Auto Reporting from the function tree.
    3. Change the value of Auto Reporting Status to Reported for the associated event.
  • Disable alarm reversion.
    1. Right-click an NE in the Main Topology and choose NE Explorer from the shortcut menu.
    2. Select an NE in the NE Explorer and choose Alarm > NE Alarm Attributes from the function tree. Alternatively, select a board in the NE Explorer and choose Alarm > Alarm Reversion from the function tree.
    3. Change the value of Alarm Reversion to Disable or Reversion Status to Disable for the associated alarm.