Keywords

Alarm

Case Information

U2000	OS	Database	NE
V100R009C00	Windows/Solaris/Linux	--	--

 

Symptom

The U2000 frequently reports alarms although no NE alarm is generated.

Cause Analysis

A sequence number starting from 1 is assigned to each alarm that an NE reports to a target host. The U2000 determines whether alarms are lost based on alarm sequence numbers. Data of lost alarms detected will be synchronized to the U2000. If multiple target hosts based on the same U2000 are specified for an NE, each alarm sent to the U2000 has multiple sequence numbers. As a result, the U2000 receives multiple discontinuous alarms that are the same but have different sequence numbers. This triggers frequent alarm synchronizations, causing the U2000 to continuously report alarms.

Problem Locating

Perform the following operations to check whether multiple target hosts based on the same U2000 have been specified or whether both the primary and secondary sites/NICs in an HA/dual-NIC system have been specified as target hosts:

                               Step 1      Run the following command on the NE:

dis cur | inc snmp

 snmp-agent target-host trap address udp-domain 10.107.227.101 params securityname public v2c private-netmanager ext-vb

snmp-agent target-host trap address udp-domain 10.107.227.101 vpn-instance vpn params securityname public v2c private-netmanager ext-vb

                               Step 2      In the NE Explorer of the U2000, choose System Management > NE Channel Management > Trap Service from the navigation tree. Then check the Receive Host IP Address column in the Trap Service window.

 

----End

Solutions

l   Single-Server System with Only One NIC

If multiple target hosts are specified based on the same U2000, reserve only one target host that can communicate with the NE while deleting all the other target host configurations.

l   Single-Server System with Dual NICs

If both the primary and secondary NICs are specified as target hosts and can communicate with the NE, delete the target host configurations on the secondary NIC.

Deletion Methods

l   Deletion from Network Side

Run the undo snmp-agent target-host $U2000 IP address securityname $community command in the system view.

l   Deletion from the U2000

In the NE Explorer of the U2000, choose System Management > NE Channel Management > Trap Service from the navigation tree. In the Trap Service window, select a record, right-click, and choose Delete from the shortcut menu.

 

Suggestion and Summary

Restart the faulty process and the TrapReceiver process after the deletion.