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


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


NEs Fail to Be Added to eSight

Publication Date:  2019-04-11 Views:  78 Downloads:  0

Issue Description

NEs fail to be added to eSight.

Handling Process

1. Ping NEs from eSight. It is found that the network connectivity is normal.
2. Check the SNMP configuration.
  snmp-agent sys-info version v2c 
  snmp-agent mib-view included View_ALL iso
  snmp-agent community read cipher *******  mib-view View_ALL acl 2005
  snmp-agent community write cipher ******  mib-view View_ALL acl 2005
3. Check whether the ACL configuration is correct.
  acl number 2005
  rule 0 permit source 10.X.X.5 0
4. On the eSight, obtain packet header information about the SNMP reply packets that are not received by NEs.
5. Check the route information on NEs. It is found the traffic hitting VPN routes exists.

Root Cause

The interface is bound to a VPN instance, and the reply packets sent by the NEs are transmitted through VPN.


VPN is used in the ACL rule.
acl 2005
rule 5 permit source 10.X.X.5 0  vpn-instance XXXX