Using SNMPv3

The following sections explain how to use SNMPv3:

•	What's New in SNMPv3

•	How to Configure for Running Utilities in SNMPv3

•	What's Changed from SNMPv1 to SNMPv3

What's New in SNMPv3

Compiling with SNMPv3, Oracle Tuxedo SNMP provides you two important security features:

•	USM (User-based Security Model)

Provides authentication and privacy (encryption) functions and operates at the message level.

•	VACM (View-based Access Control Model)

Determines whether a given principal is allowed access to a particular MIB object to perform specific functions and operates at the PDU level.

How to Configure for Running Utilities in SNMPv3

You should configure SNMPv3 for the following configuration file and utilities.

•	Oracle SNMP Agent Configuration File: beamgr.conf

•	Oracle SNMP Agent Utilities

Oracle SNMP Agent Configuration File: beamgr.conf

The following commands/utilities read Oracle SNMP Agent Configuration File (beamgr.conf), and check its keyword SYS_VERSION to determine which SNMP version should be run. Therefore, you should set this SYS_VERSION to 3 for running unitilies in SNMPv3.

•	snmp_integrator (the Oracle SNMP Agent Integrator)

•	tux_snmpd (the Oracle SNMP Agent)

•	snmptrapd (an Oracle Tuxedo SNMP Agent utility)

For more information, see Oracle SNMP Agent Configuration File: beamgr.conf.

Oracle SNMP Agent Utilities

The following utilities are run in SNMPv1 by default. To run them in SNMPv3, you should set their -v option to 3.

•

snmpget

•	snmpgetnext

•

snmptest

•

snmptrap

•

snmptrapd

•

snmpwalk

For more information, see Oracle SNMP Agent Utilities.

What's Changed from SNMPv1 to SNMPv3

Compared to SNMPv1, there are just few changes made in SNMPv3. Except for the points mentioned below, all behaviors in SNMPv3 remain unchanged as they are in SNMPv1.

•	Changes on Configuration Files

•	Changes on Utilities

•	Support for New Utility

Changes on Configuration Files

Oracle SNMP Agent Configuration File: beamgr.conf

The following keywords are added to Oracle SNMP Agent Configuration File (beamgr.conf).

•	SYS_VERSION

•	ENGINE_ID STRING

•	CMD_PARAMETERS

•

USM_USER

•	VACM_GROUP

•

VACM_VIEW

•	VACM_ACCESS

The following keywords are updated in Oracle SNMP Agent Configuration File (beamgr.conf).

•

TRAP_HOST

•	NON_SMUX_PEER

For more information, see Oracle SNMP Agent Configuration File: beamgr.conf.

Changes on Utilities

The following command line options are added to the following utilities.

Added command line options are

•	-a authProtocol

•	-A authPassword

•	-c community

•	-e engineID

•	-l secLevel

•	-s agent_addr (this option is only used by snmptrap to replace its original -a agent_addr)

•	-u secName

•

-v 1 | 3

•	-x privProtocol

•	-X privPassword

Affected utilities are

•

snmpget

•	snmpgetnext

•

snmptest

•

snmptrap

•

snmptrapd

•

snmpwalk

Notes:

In SNMPv1, snmptrap has an option -a agent_addr, which is used to specify an originating address; in SNMPv3, this option is replaced with -s agent_addr because -a is occupied for another usage (-a authprotocol is used to specify the authentication protocol in SNMPv3).

When using SNMPv1 with snmptrapd, do not use the -v3 option.

When using SNMPv3 with snmptrapd, you must add the following options: -v 3 -p -l 4400.

For more information, see Oracle SNMP Agent Utilities.

Support for New Utility

Oracle Tuxedo SNMP introduces a new utility snmpkey in SNMPv3 to generate authentication and, when applicable, generate privacy keys.

For more information, see Oracle SNMP Agent Utilities.