Configure the SNMP Trap Collector Extension For the SNMP trap collector extension to receive traps from network devices, each device must designate the MID Server that runs the SNMP trap collector extension as a recipient of the trap. Before you beginRole required: Admin About this taskTo configure the trap collector extension: Procedure Navigate to MID Server > Extensions > SNMP Trap Collectors Click New or open an existing extension. Fill in the fields from the table, as appropriate. Click Submit or Update. Table 1. SNMP trap collector form Field name Description Name A unique name for this SNMP trap collector extension for easy identification. Short description A description of the MID Server extension, if more description than the Name is necessary. Extension [Read-Only] The extension type is automatically set to TrapExtension. UDP port The port number that your network hardware uses when sending a trap to the designated MID Server. Port numbers 1024 and above are recommended. Port numbers 1023 and lower may be system reserved and can result in access violations for MID Servers that are not running with administrative credentials. Status [Read-Only] The status of the trap collector extension. This field is blank until the extension is run. After it is run, the value may be: Started: The extension is running. Stopped: The extension is not running. Offline: The MID Server is down. Error: The extension failed with an error. Execute on The location for running this extension: a Specific MID Server or a Specific MID Server Cluster. The recommended setting is Specific MID Server. Network hardware typically has to be configured to send to a specific IP address. If the listener moved to a different MID Server in the cluster, the trap would not be received. MID Server The name of the designated MID Server if you selected Specific MID Server in the Execute on field. The name of the designated MID Server cluster if you selected Specific MID Server Cluster in the Execute on field. If you selected Specific MID Server Cluster, a ServiceNow algorithm determines which server in the cluster runs the extension. Executing on [Read-Only] The name of the MID Server on which the extension is running. This field shows the name of the MID Server even if the MID Server is down. If the extension is stopped by the user, this field is empty.