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>


To have a better experience, please upgrade your IE browser.


Problem with sending SNMP traps packets over vpn-instacne

Publication Date:  2014-10-31 Views:  116 Downloads:  0
Issue Description

【Problem Summary】[Novosibirsk, NE40E] NMS can't receive SNMP traps from NE40E
【Problem Details】

Customer complains that NMS is connected  over Shtora-Mgmt can’t get SNMP traps from router.
During analysis was discovered that router had following configuration:
snmp-agent local-engineid 800007DB03E0247FFA4E3F
snmp-agent community read  ******
snmp-agent community read  ******
snmp-agent community write cipher *****************
snmp-agent community read  *****************
snmp-agent community read cipher **********************
snmp-agent community write cipher ***********************
snmp-agent sys-info contact Company
snmp-agent sys-info location City ,Russia
snmp-agent target host trap X.Y.Z.W
snmp-agent sys-info version all


Handling Process

during analysis was discovered that NE40E didn't send SNMP trap over interface Ge7/0/18.930 which is binded into vpn-instace Shtora-mgmt, while IP address "X.Y.Z.W" is accessable through this interface.




Root Cause

This situation happened because NE40E can't send SNMP trap packets over vpn-instance by default. from version V600R003 NE40E support sending SNMP trap over vpn-instance interfaces. but need to change configuration.


【Resolution Summary】use "vpn-instanse" option in command snmp-agent target-host"
【Resolution Details】 use command "snmp-agent target-host trap address udp-domain ip-address [ udp-port port-number | { public-net | vpn-instance vpn-instance-name } ] * params securityname security-string [ { v3 [ authentication | privacy ] | v2c | v1 } | notify-filter-profile profile-name | private-netmanager | ext-vb ] * "// Risk of Solution:Non-Risk Operation