Entering content frame

Function documentation Adjusting the Configuration File for Receiving SNMP Traps Locate the document in its SAP Library structure

Use

You require a configuration file in the following cases to set up the receiving of SNMP traps:

·        If you are using the test tool rectraps; use this tool to test whether SNMP traps were sent correctly (see Structure linkTesting the Correct Sending of SNMP Traps with rectraps)

·        When receiving the SNMP traps as a function of the CCMS agents (see Setting Up the Sending and Receiving of SNMP Traps Using CCMS Agents)

You define details about the receipt of the SNMP traps in the configuration file, such as the port at which the recipient is to listen.

Features

Make the following settings in the configuration file:

·        Section [SNMP_TRAPD]

Parameter

Description

Default

MIB_DIR

Directory that contains the MIB files (Management Information Base); this is required to display the received traps correctly

Note

Change this value to the path of the MIBS directory.

. (program’s directory)

LISTEN_PORT_<x>

Transport protocol and port number with which the traps are received; by using different values of X=0,1,2..., traps can be received by different ports

UDP:162

DROP_AUTH

With SNMP Version 3, the user must authenticate himself or herself; in the case of incorrect authorization, an Authentication Failure Trap is generated. You can avoid traps of this type being displaying by setting DROP_AUTH=1

0

·        Section [SNMP_USER]

If you are using SNMP version 3, define one or more SNMP users which receive the SNMP traps in this section. For SNMP versions 1 and 2c, leave this section empty.

To define users, create a line with the following format for each user:

createUser [–e <SECURITY_ENGINE>] <USER_NAME> <AUTH_PROTOCOL>

              <AUTH_PASSPHRASE>

When making these specifications, the following applies:

Parameter

Description

<SECURITY_ENGINE>

Engine ID of the application from which the SNMP traps are to be sent; this parameter is only required if INFORM=0, since the engine ID is generated during the communication if INFORM=1

<USER_NAME>

Name of the user

<AUTH_PROTOCOL>

Procedure for authenticating the message (creation of a checksum used to ensure that the message was not changed); the MD5 (Message Digest 5) procedure is supported

              <AUTH_PASSPHRASE>

Password of the user

Example

The template rectraps.cfg for the configuration file is in the directory for_recipient of the SNMPLIB. It has the following content:

[SNMP_TRAPD]
DROP_AUTH=0
MIB_DIR=.
LISTEN_PORT_0=udp:162

[SNMP_USER]
createUser myuser MD5 mypassword
createUser -e 0x0102030405 myuser1 MD5 mypassword1

This graphic is explained in the accompanying text Structure linkSending and Receiving Alerts Using SNMP Traps start page

 

Leaving content frame