The problem is that the NMS is not expecting to receive SNMP information via traps as has been configured, but instead the NMS appears to be using SNMPwalk to collect the information from
the AR router. As a result based on the current configuration the customer’s NMS is receiving the SNMP traps and rejecting them.
It is not so much that the customer is looking to disable SNMP traps but that it is not able to get any response when using SNMPwalk.
He is using a simple snmpwalk from the poller:
-v2c -chighlightREAD 62.44.XX.XXX sysName
and monitoring traffic with Wireshark.
We can see that there is still no Outbound UDP packets reported for 62.44.XX.XXX
The client wants to understand why the SNMP UDP packets are not being received by the NMS and whether it is a configuration issue on the router.
1. Asked for more the output of the command: display diagnostic-information from the router
2. Checking the configuration
After analyzing the configuration, I concluded the fact that the following IP address: 62.44.XX.XXX is the IP of the NMS, as I could find it in the following command configured on your router: “snmp-agent target-host trap-hostname nms address 62.44.XX.XXX udp-port 162 trap-paramsname ifDescr”
Therefore, the command “snmp-agent server-source -a 62.44.XX.XXX” is not correctly configured, as it should be mentioned here the IP of the outside interface of your router (the interface connecting to the Internet). Given the above, i suggest him to undo this command like below:
[Huawei] undo snmp-agent 62.44.XX.XXX server-source