SNMPv1 supports only traps, not inform requests. To enable SNMP inform requests, you must use SNMPv2 or SNMPv3.
Because each sent receipt increases the amount of memory in use on the router and the amount of network traffic, we recommend that you consider whether it is necessary to send a receipt for every SNMP notification. If an inform request must be sent more than once, the retries increase traffic. They are held in memory until the sender gets a response. However, inform requests consume more resources. A trap is sent only once, and the receiver does not send any acknowledgment when it gets the trap.Īn inform request is more reliable than a trap because your Firebox knows whether the inform request was received.
).Then monitor the trap receiver if that specific trap was received in time. ), or something similar via a scheduler (either on the EX itself or from external by SSH, SNMP. If your device does not get a response, it sends the inform request again until the SNMP manager sends a response. Ben Well, I mean the spoofed traps you mention above - you could trigger a custom trap ( request snmp spoof-trap), deliberately cause a situation triggering a specific trap (run invalid command. Modify the device configuration(s) to add a trap receiver in order for. Your device can send a trap for any policy.Īn SNMP inform request is similar to a trap, but the receiver sends a response. Prime Infrastructure uses SNMP polling to gather information about your network.
The trap identifies when a specific condition occurs, such as a value that is more than its predefined threshold. Enable SNMP Management Stations and TrapsĪn SNMP trap is an event notification your Firebox sends to an SNMP management station.
0 kommentar(er)
