Configuring Event Trapping for SNMP

The following events are trapped by default when you configure Vertica to trap events for SNMP:

  • Low Disk Space
  • Read Only File System
  • Loss of K Safety
  • Current Fault Tolerance at Critical Level
  • Too Many ROS Containers
  • WOS Over Flow
  • Node State Change
  • Recovery Failure
  • Stale Checkpoint
  • CRC Mismatch

To Configure Vertica to Trap Events for SNMP

  1. Enable Vertica to trap events for SNMP.
  2. Define where Vertica sends the traps.
  3. Optionally redefine which SNMP events Vertica traps.

After you complete steps 1 and 2 above, Vertica automatically traps the default SNMP events. Only perform step 3 if you want to redefine which SNMP events are trapped. Vertica recommends that you trap the Stale Checkpoint event even if you decide to reduce the number events Vertica traps for SNMP. The specific settings you define have no effect on traps sent to the log. All events are trapped to the log.

To Enable Event Trapping for SNMP

Use the following SQL command:

=> ALTER DATABASE DEFAULT SET SnmpTrapsEnabled = 1;

To Define Where Vertica Send Traps

Use the following SQL command, where Host_name and port identify the computer where SNMP resides, and CommunityString acts like a password to control Vertica's access to the server:

=> ALTER DATABASE DEFAULT SET SnmpTrapDestinationsList = 'host_name port CommunityString';

For example: 

=> ALTER DATABASE DEFAULT SET SnmpTrapDestinationsList = 'localhost 162 public';

You can also specify multiple destinations by specifying a list of destinations, separated by commas:

=> ALTER DATABASE DEFAULT SET SnmpTrapDestinationsList = 'host_name1 port1 CommunityString1, hostname2 port2 CommunityString2';

: Setting multiple destinations sends any SNMP trap notification to all destinations listed.

To Define Which Events Vertica Traps

Use the following SQL command, where Event_Name is one of the events in the list below the command:

=> ALTER DATABASE DEFAULT SET SnmpTrapEvents = 'Event_Name1, Even_Name2';
  • Low Disk Space
  • Read Only File System
  • Loss Of K Safety
  • Current Fault Tolerance at Critical Level
  • Too Many ROS Containers
  • WOS Over Flow
  • Node State Change
  • Recovery Failure
  • Recovery Error
  • Recovery Lock Error
  • Recovery Projection Retrieval Error
  • Refresh Error
  • Tuple Mover Error
  • Stale Checkpoint
  • CRC Mismatch

The above values are case sensitive.

The following example specifies two event names: 

=> ALTER DATABASE DEFAULT SET SnmpTrapEvents = 'Low Disk Space, Recovery Failure';