After a Switch Is Added to eSight and SNMP Parameters Are Correctly Configured, Switch Alarms Cannot Be Displayed on eSight

Publication Date:  2015-10-14 Views:  486 Downloads:  0
Issue Description
After a switch is successfully added to eSight and the SNMP test succeeds, an alarm indicating the interface Up and Down exists in the switch's log, but the alarm is not displayed on eSight.
Handling Process
interface LoopBack0 
ip address 10.228.255.9 255.255.255.255 

snmp-agent 
snmp-agent local-engineid 800007DB0304F93890F760 
snmp-agent community write cipher %#%#uC&FKV;y4(:eo}Coo*fB{,6b8LYORQ8nU[,-PHQMBqk6>+x.826~iO"H)~GVK%~lY}V]=ZgtX+M,w"\X%#%# acl 2001
snmp-agent community read cipher %#%#x<QiB#Y[KF,3dEJ]6Q})7;)qX9-1;*>Rr.$JU.xYtB{ZBaG6'Tu-NLEa\Ow=X[R&6MEKn$0aV_(e^KRW%#%# mib-view iso-view
snmp-agent sys-info version all 
snmp-agent target-host trap address udp-domain 10.228.248.1 params securityname cipher %#%#>w66BjD|XM1DF+H(uz\EMza"XM#5`1BX`tB=EmfT%#%# v2c
snmp-agent mib-view included iso-view iso 
snmp-agent trap source LoopBack0 
snmp-agent inform timeout 5 
snmp-agent inform resend-times 6 
snmp-agent inform pending 7 
snmp-agent trap enable 

[SRCU-A-NT-OPM-ZDS01-N5-GigabitEthernet2/5/0/13] shut 
May 11 2015 15:44:29+08:00 SRCU-A-NT-OPM-ZDS01-N5 %%01IFPDT/4/IF_STATE(l)[6]:Interface GigabitEthernet2/5/0/13 has turned into UP state.
May 11 2015 15:43:13+08:00 SRCU-A-NT-OPM-ZDS01-N5 %%01IFPDT/4/IF_STATE(l)[7]:Interface GigabitEthernet2/5/0/13 has turned into DOWN state.
May 11 2015 15:34:03+08:00 SRCU-A-NT-OPM-ZDS01-N5 %%01IFPDT/4/IF_STATE(l)[8]:Interface GigabitEthernet2/5/0/13 has turned into UP state.
May 11 2015 15:33:00+08:00 SRCU-A-NT-OPM-ZDS01-N5 %%01IFPDT/4/IF_STATE(l)[9]:Interface GigabitEthernet2/5/0/13 has turned into DOWN state.
May 11 2015 15:32:29+08:00 SRCU-A-NT-OPM-ZDS01-N5 %%01IFPDT/4/IF_STATE(l)[10]:Interface GigabitEthernet2/5/0/13 has turned into UP state.

The information shows that no masking rule is configured on eSight, and the corresponding trap messages have been sent to the eSight server.

The following figure shows information of received messages.

Root Cause
As you can see from the preceding figure, the user adds the switch to eSight using the management IP address 10.228.225.254, but the source address for sending traps is set to 10.228.255.9 in the SNMP settings. A device actively sends traps to eSight, and eSight filters received packets by determining whether the source address of a trap is the management IP address of the managed device.
Suggestions
Delete the switch from eSight, and then add the switch to eSight again using 10.228.255.9 as its management IP address. Alternatively, change the source address from sending traps in the SNMP settings to 10.228.225.254.

END