dpid2 Daemon

Purpose

Starts the dpid2 Distributed Protocol Interface - SNMP multiplexer protocol (DPI-SMUX) converter daemon as a background process.

Syntax

dpid2 [ -d [Level] ]

Description

The dpid2 command starts the dpid2 DPI-SMUX converter daemon. This command can be issued only by a user with root privileges or by a member of the system group.

The dpid2 DPI-SMUX converter daemon complies with the standard Simple Network Management Protocol (SNMP) DPI version 2.0 that is defined by RFC 1592 and SNMP SMUX protocol and Management Information Base (MIB) defined by RFC 1227.

The dpid2 daemon acts as a DPI 2.0 to SMUX converter. It is used to allow DPI subagents, such as /usr/sbin/hostmibd, to communicate with the AIX® SNMP version 1 agent. The converter changes DPI2 messages into SMUX protocol messages and vice versa. The dpid2 daemon itself is implemented as SMUX peer. It connects with the TCP port 199 of the SMUX server that is part of the snmpd agent. To a DPI2 subagent (for example, /usr/sbin/hostmibd), the dpid2 daemon behaves like a DPI2 agent. It listens on an arbitrary TCP port for a connection request from a DPI2 subagent. This port number is registered by the dpid2 daemon with the snmpd agent through MIB variable dpiPortForTCP (1.3.6.1.4.1.2.2.1.1.1). The DPI2 subagent learns this port number from the snmpd agent by sending a get-request query for the dpiPortForTCP.0 (1.3.6.1.4.1.2.2.1.1.1.0) instance to the snmpd agent. After the DPI2 subagent knows the TCP port number, which the DPI2 agent is listening on, it then tries to connect to it.

The dpid2 daemon is normally run during system startup when the /etc/rc.tcpip shell script is called.

The dpid2 daemon must be controlled by using the System Resource Controller (SRC). Entering dpid2 at the command line is not recommended.

Use the following SRC commands to manipulate the dpid2 daemon:

startsrc: Starts a subsystem, group of subsystems, or a subserver.
stopsrc: Stops a subsystem, group of subsystems, or a subserver.
refresh: Causes a subsystem or group of subsystems to reread the appropriate configuration file.
lssrc: Gets the status of a subsystem, group of subsystems, or a subserver.

Note: The snmpdv3 agent itself acts as a DPI2 agent and listens on the dpiPortForTCP.0 TCP port. Therefore, the dpid2 daemon is not needed when you use the snmpdv3 agent. Therefore, the dpid2 daemon is not run in the system startup and the dpid2 line in /etc/rc.tcpip is commented out.

Flags

Item	Description
-d Level	Specifies tracing or debug level. 8 DPI level 1 16 DPI level 2 32 Internal level 1 64 Internal level 2 128 Internal level 3 Add the numbers for multiple trace levels. Note: If the -d flag is specified, but the level number is not specified, the default level is 56. If -d flag is not specified, the default level is 0.

Examples

To start the dpid2 daemon, enter a command similar to the following command:
```
startsrc -s dpid2 -a "-f /tmp/dpid2.log"
```
This command starts the dpid2 daemon and logs information to the /tmp/dpid2.log file at debug level 0.
To stop the dpid2 daemon normally, enter the following command:
```
stopsrc -s dpid2
```
This command stops the dpid2 daemon. The -s flag specified the subsystem that follows to be stopped.
To get the short status from the dpid2 daemon, enter the following command:
```
lssrc -s dpid2
```
This command returns the name of the daemon, the process ID of the daemon, and the state of the daemon (active or inactive).

Files

Item	Description
/etc/snmpd.conf	Specify SMUX peer entry in snmpd version 1 agent configuration file.
/etc/snmpd.peers	Specify the configuration for SMUX peer.
/etc/mib.defs	Defines the MIB variables the SNMP agent and manager must recognize and handle.