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.

Knowledge Base

FAQ-Why Cannot an AR Router Send Trap Messages

Publication Date:  2019-07-04  |   Views:  721  |   Downloads:  0  |   Document ID:  EKB1000074993


Issue Description

Why Cannot an AR Router Send Trap Messages?


SNMP provides the trap function to control the output of trap messages. An AR router generates trap messages only when the trap function has been enabled on the AR router.

Perform the following operations to enable the trap function on an AR router:

1.  Run the system-view command to enter the system view.

2.  Run the snmp-agent trap enable command to enable the AR router to send trap messages to the NMS.

3.  Run the snmp-agent target-host trap-paramsname paramsname v1 securityname securityname [ binding-private-value ] [ trap-filterprofilename filterprofilename ] [ private-netmanager ] command to set parameters for sending trap messages.

V200R001C01 and later versions support binding-private-value.
V200R002C00 and later versions support private-netmanager.

4.  Run the snmp-agent target-host trap-hostname hostname address ipv4-addr [ udp-port udp-portid ] [ public-net | vpn-instance vpn-instance-name ] trap-paramsname paramsname command to specify the destination host for receiving trap messages and error codes.

The default destination UDP port number is 162. To ensure secure communication between the NMS and managed devices, run the udp-port command to change the UDP port number to a non-well-known port number.