LinkUp(3): Select to filter for a re-established connection to the network device. LinkDown(2): Select to filter for a severed connection to the network device. WarmStart(1):Select to filter for a warm start of the network device. There are six options available:ĬoldStart(0): Select to filter for a cold start of the network device. Select to specify the generic identifier of the SNMP trap. Select to specify the enterprise identifier of the event raised by the device. Select to specify the IP address of the device where the event originates. If you select port 162, the Microsoft SNMP Trap Service must be disabled because it uses the same port when it runs. If you select the No dependency option, type the communication port number that will be monitored for SNMP traps. Select this option to monitor SNMP traps using a port rather than the Microsoft SNMP Trap Service. This service is only compatible with SNMP versions SNMPv1 and SNMPv2c. Select this option to use the Microsoft SNMP Trap Service. Microsoft SNMP Trap Service (SNMPv1, SNMPv2c) Use the following information to configure the Monitor SNMP Trap activity. Generic or specific identifier of the device that you are monitoring Configuring the Monitor SNMP Trap Activityīefore you configure the Monitor SNMP Trap activity, you need to determine the following: Use the Monitor SNMP Trap activity to monitor a network device for critical errors, automatically create a trouble ticket, and perform level 1 diagnostics on the device. Using filters, you can invoke your runbooks according to the device that raised the event or the enterprise, generic, or specific identifiers of the SNMP trap. The Monitor SNMP Trap activity waits for an event to occur either in the Microsoft SNMP Trap Service, or on a port that you specify. The actual trap doesn’t have to carry alert information, which minimizes bandwidth usage.This version of Orchestrator has reached the end of support, we recommend you to upgrade to Orchestrator 2019. The management information base (MIB) stores the translation of each OID, so the manager can simply refer to the MIB to understand the trap message. In this case, traps have their own OIDs, so the SNMP manager can easily identify what kind of message the trap is sending.

In this case, all traps have the same object identifier (OID) and the managing device must be able to process the information within the trap.

Alert data can be included within the traps. There are two ways SNMP traps can ensure the right data is communicated to the manager: The manager decodes and analyzes the message, then can trigger alerts or actions or display key information for admins.

When an event (like a failure or error) occurs on the device, a message is sent from the device to the central manager. SNMP traps inform a central SNMP receiver of whatever issue the device is currently experiencing.

Snmp trap receiver logs