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>

Reminder

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

upgrade

SNMP not working after upgrade

Publication Date:  2018-03-22 Views:  193 Downloads:  0
Issue Description

Customer upgraded the S12708 from software version V200R008C00SPC500 to V200R010C00SPC600, after doing the upgrade SNMP was not working. 

eSight version: V300R007C00SPC305

snmp version: SNMPv3


Handling Process

1.First step: We should check the log:

         Line 46628: Feb  8 2018 03:00:51+01:00 ssc-core-1 %%01SNMP/4/SNMP_FAIL(s)[405]:Failed to login through SNMP. (Ip=172.24.32.96, Times=5, Reason=the ACL filter function, VPN= )

         Line 46647: Feb  8 2018 02:30:47+01:00 ssc-core-1 %%01SNMP/4/SNMP_FAIL(s)[424]:Failed to login through SNMP. (Ip=172.24.32.96, Times=2, Reason=the ACL filter function, VPN= )

         Line 46650: Feb  8 2018 02:30:45+01:00 ssc-core-1 %%01SNMP/4/SNMP_FAIL(s)[427]:Failed to login through SNMP. (Ip=172.24.32.96, Times=1, Reason=the ACL filter function, VPN= )

         Line 46653: Feb  8 2018 02:20:51+01:00 ssc-core-1 %%01SNMP/4/SNMP_FAIL(s)[430]:Failed to login through SNMP. (Ip=172.24.32.96, Times=3, Reason=the ACL filter function, VPN= )

         Line 46657: Feb  8 2018 02:20:47+01:00 ssc-core-1 %%01SNMP/4/SNMP_FAIL(s)[434]:Failed to login through SNMP. (Ip=172.24.32.96, Times=6, Reason=the ACL filter function, VPN= )

 

    2. We search the Product Document:


 SNMP/4/SNMP_FAIL

 Possible causes are as follows:

  • 1. The SNMP version was incorrect.
  • 2. SNMP messages were over-sized.
  • 3. Messages failed to be added to the message list.
  • 4. A PDU decoding error occurred.
  • 5. The community was incorrect.
  • 6. The ACL filter function was faulty.
  • 7. The value of contextname was incorrect.
  • 8. Authorization failed
  • 9. Access denied

                   3. We have checked the possibile causes and then noticed that the acl filter was not configured.


Solution

We created acl to identify the traffic between network device (switch) and eSight after that you need to use the command snmp-agent acl xxx.

 

<HUAWEI> system-view

[HUAWEI] acl xxxx

[HUAWEI-basic-xxx] rule permit source 192.168.10.10 0

[HUAWEI-basic-xxx] quit

[HUAWEI] snmp-agent acl xxx

After we added the above commands the issue was solved.


END