GuidesREST APISlack CommunitySupport PortalOpsview 6.8+ Documentation

# Description

  • Provides script `stdin2sock` to receive traps from the device and write to fifo `/opt/opsview/snmptraps/var/run/snmp`.

  • Provides opsview-watchdog config to start, stop and reload system snmp daemons.

  • This package needs to be installed with the opsview-snmptraps-collector

  • Input to this package is an snmp trap which is translated and the packet sent to stdin2sock to be written into the fifo

## Dependencies

No dependencies

## Installation

This is deployed when installing Opsview Monitor.

See [MIBs for SNMP Traps and Gets](🔗) to add your MIBs that are required for translating SNMP Traps.

## Management

### Configuration

#### DPKGs

Watchdog service files are now managed by the package manager, removing the package would leave the watchdog service file behind with a .save extension. Purging the package will remove it. The package manager managed config files are as follows

  • /opt/opsview/watchdog/etc/services/opsview-snmptraps.conf

#### RPMs

Watchdog service files are now managed by the package manager. When removing the package, if the files listed have been modified by the user before; they will be left behind after rpmsave extension has been added to them. When upgrading the package, if the files listed have been modifed by the user before; the modified file on the disk will remain and the new config file from the upgrading package will be written to the disk with the rpmnew extension. Users will have to:

  1. Manually restore the file with the rpmsave extension.

  2. Rename the rpmnew to the config file name if they want to use the new config for the package.

  • /opt/opsview/watchdog/etc/services/opsview-snmptraps.conf

### Service Administration

As root, start, stop and restart the service using:


## Known Limitations
### snmptrapd not monitored by watchdog
Even though the `snmpd` is monitored by `opsview-watchdog` and will be restarted when that process unexpectedly dies, the `snmptrapd` process is not monitored. This means it is possible for `snmptrapd` to have an exceptional failure that is not automatically recoverable.  This is a limitation in the `opsview-watchdog` software and is a rare event.
### Trap handling within clustered nodes
See [here](🔗) for a manual fix.