[ Bottom of Page | Previous Page | Next Page | Contents | Index | Library Home | Legal | Search ]

Commands Reference, Volume 2

dpid2 Daemon

Purpose

Starts the dpid2 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 may only be issued 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 Distributed Protocol Interface Version 2.0 defined by RFC 1592 and SNMP MUX Protocol and MIB defined by RFC 1227.

dpid2 acts as a DPI 2.0 to SMUX converter. It is used to allow DPI sub-agents, such as /usr/sbin/hostmibd, to talk with the AIX SNMP version 1 agent. The converter changes DPI2 messages into SMUX protocol messages and vice-versa. dpid2 itself is implemented as SMUX peer. It will connect with the TCP port 199 of the SMUX server which is part of snmpd agent. To a DPI2 sub-agent (e.g. /usr/sbin/hostmibd), dpid2 behaves as a DPI2 agent. It listens on an arbitrary TCP port for a connection request from a DPI2 sub-agent. This is port number is registered by dpid2 daemon with the snmpd agent through MIB variable dpiPortForTCP (1.3.6.1.4.1.2.2.1.1.1). The DPI2 sub-agent 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 sub-agent knows the TCP port number which the DPI2 agent is listening on, it will then try to connect to it.

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

The dpid2 daemon should be controlled 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
On AIX release 5.2.0 and after, the snmpdv3 agent itself acts as a DPI2 agent and listens on the dpiPortForTCP.0 TCP port. Therefore, dpid2 is not needed when using the snmpdv3 agent. Therefore, the dpid2 daemon won't be executed in the system startup and the dpid2 line in /etc/rc.tcpip will be commented out.

Flags

-d Level Specifies tracing/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, by the level number is not specified, the default level will be 56. If -d flag is not specified, the default level is 0.

Examples

  1. To start the dpid2 daemon, enter a command similar to the following:
    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.
  2. To stop the dpid2 daemon, normally enter:
    stopsrc -s dpid2
    This command stops the dpid2 daemon. The -s flag specified the subsystem that follows to be stopped.
  3. To get the short status from the hostmbid, enter:
    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

/etc/snmpd.conf Specify smux peer entry in snmpd v1 agent configuration file.
/etc/snmpd.peers Specify the configuration for smux peer.
/etc/mib.defs Defines the Management Information Base (MIB) variables the SNMP agent and manager should recognize and handle.

Related Information

The snmpdv1 daemon, hostmibd command.

The /etc/snmpd.peers file.

[ Top of Page | Previous Page | Next Page | Contents | Index | Library Home | Legal | Search ]