SnmpTrap

Supported Versions SNMP V1, V2, V3
Collection Methods SNMP Listener
Requirements
  • The computers and network devices sending SNMP traps must be configured to send traps to Longitude. This configuration will vary depending on the application sending traps – consult your application’s documentation for configuration details.
  • Either the Longitude Management Console or a Longitude Remote Agent may be configured to listen for traps.
  • Any vendor specific MIBs for the traps should be copied to the Longitude\lib\mibs directory on the Longitude Management Console and any Longitude Remote Agents listening for traps.
  • Only one listener can function at a time for any given port. If other listeners are installed on a Longitude listener, whichever listener starts first will attach to the port and receive data. Stop all other SNMP listeners on Longitude servers listening for traps, and set any trap listener services to Manual start.
  • On Windows servers, the SNMP Trap service is an SNMP Trap listener, and should be stopped, and set to Manual or Disabled.
  • Verify that any routers or firewalls between the SNMP sender and the Longitude listener will not block SNMP Traffic.
  • If SNMP V3 Authentication or Encryption is used for traps, that information will be needed to configure Longitude so that it can decode the traps.
  • SNMP listeners do not require a Community string to listen for traps.
  • SNMP traps have a Generic Trap Number property which is set as follows:
    Generic Trap # Name Indicates
    0 coldStart Reboot has occurred
    1 warmStart SNMP has restarted
    2 linkDown Interface has gone down
    3 linkUp Interface is back up
    4 authenticationFailure Incorrect community string or SNMP V3 credentials
    5 egpNeighborLoss On a host running a gated daemon, indicates Exterior Gateway Protocol (EGP) neighbor loss
    6 enterpriseSpecific Vendor specific traps
Configuration
  1. Use Monitor Devices.
  2. Select SnmpTrap.
  3. Set the Agent to the Longitude Management Console or the Remote Agent listening for the traps.
  4. If the OID field is empty, all incoming traps will be recorded. If any OIDs are entered into this field, only OIDs that match the entries will be recorded.
  5. The Generic field will filter traps based on their generic trap number (see Generic Trap Number chart). In most cases you will only select enterpriseSpecific. If nothing is selected, all Generic trap number values will be collected.
  6. enterpriseSpecific traps also have Specific trap numbers which are assigned when the trap is generated. In most cases, this field will be left blank to accept all Specific trap numbers.
  7. The Device field may be used to filter which devices traps will be accepted from. In most cases, this field will be left blank to accept traps from all devices.
  8. The User field specifies the User name associated with SNMP V3 traps. Only one value is allowed in this field.
  9. Select the Authentication Protocol for SNMP V3 authentication, if used.
  10. Enter the Authentication Password for SNMP V3 if authentication is used. Only one value is allowed in this field. This field may be left blank if SNMP V3 authentication is not used.
  11. Select the Privacy Protocol if SNMP V3 encryption is used. The default value is 0 for DES, with the option of 1 for AES.
  12. Enter the Privacy Password if SNMP V3 encryption is used. Only one value is allowed in this field. This field may be left blank if SNMP V3 encryption is not used.
  13. Enter the Engine ID if SNMP V3 encryption is used. Only one value is allowed in this field. This field may be left blank if SNMP V3 encryption is not used.
  14. Click on Monitor button.
  15. If additional sets of SNMP V3 authentication and/or encrpytion are needed, configure additional Longitude Remote Agent listeners to receive these traps.
Troubleshooting
  • SNMP Traps are not displayed in the SNMP Traps view of the Event Monitor.
    1. Restart the Statistics Server service on the Longitude server receiving the traps and check the Longitude\ss\log\ss_startup.txt file. It should contain the lines:
      SnmpTrap receiver listening on port: 162
      and
      Waiting for traps
      If these lines are not listed, register the SNMPTrap application for the agent again, and check the Longitude\ss\log\yyyymmdd_ss_error_##.txt file on the Longitude server configured to listen for registration error messages.
    2. Check the Longitude\ss\log directory for files named yyyymmdd_snmptrap_##.txt – as traps are received, they are written to this file, and later archived. If this file is empty, the Longitude listener is not receiving any traps. Recheck the configuration of the devices sending traps, and if there are any firewalls blocking traps.
    3. If there is data in the trap receiver file, it will be written to the database and available in the Event Monitor on the next collection by the consolidator, which occurs every 5 minutes. If data is still not avialable after the interval has passed, check the Longitude\consolidator\log\yyyymmdd_consolidtor_error_##.txt file for errors parsing the collection file.
  • Collections fail with java.net.SocketException: Unrecognized Windows Sockets error: 0: Cannot bind error:
    Longitude is unable to listen on the requested port because the port is already bound to another listener. Check the Longitude server for other applications or services that are listening for traps. If the other listener is a service, set it to Disabled or Manual start to prevent it from attaching to the port before Longitude does after a reboot.
  • Traps contain OID numbers instead of text:
    As Longitude receives traps, it formats them based on the contents of the MIB files in the local Longiude\lib\mib directory.

    1. Check that the applicable vendor MIBs are in this directory on both the Longitude Management Console, and, if applicable, the Longitude Remote Agent receiving the traps.
    2. If the MIBs are in the directory, restart the Longitude Statistics Server service and check the Longitude\lib\ss\ss_startup.txt file for MIB compilation errors.