# Chapter 5. Agent Integrator Commands

This chapter explains the commands for using the Agent Integrator.

## reinit_agents

### Syntax

>     reinit_agents all  |  logical_agent_name [logical_agent_name]

### Description

This utility causes the specified agents to re-read their configuration file. This utility must be run with root permissions. Using `all` causes all BEA Manager agents, including any custom agents built using the Agent Development Kit, to re-initialize. For all BEA Manager agents other than `tux_snmpd` or `m3_snmpd`, `logical_agent_name` is the name of the executable. For example, the command:

>     reinit_agents snmp_integrator

causes the Agent Integrator to re-read its configuration file.

## snmp_integrator

### Syntax

>     snmp_integrator [-d] [-n] [-p port | -r smux_port] [-b ipaddr_list | hostname_list ]

### Arguments

`-d`
  Causes the program to display a message for each SNMP/SMUX packet sent or received.

`-n`
  The program is not run as a daemon (UNIX only).

`-p` `port`
  Specifies the port on which the Agent Integrator listens for SNMP requests (default: 161/udp).

`-r` `smux_port`
  Specifies the port used to communicate with SMUX subagents (default: 199/tcp).

`-b` `ipaddr_list``|` `hostname_list`
  If the machine where the Agent Integrator is running has multiple IP addresses, by default the Agent Integrator listens on all IP addresses. The `-b` option can be used to specify a subset of IP addresses to monitor for incoming SNMP requests.

`ipaddr_list`
  Can consist of a single IP address or a blank-separated list of IP addresses.

`hostname_list`
  Can consist of one hostname or a blank-separated list of hostnames.

For example, if the machine on which the Agent Integrator is running has the following IP addresses:

`130.86.34.3
130.86.33.13
130.86.23.1`

Agent Integrator can be configured to only service requests addressed to `130.86.23.1` by starting it with the following command:

`snmp_integrator -b 130.86.23.1`

### Description

`snmp_integrator` is the BEA Manager Agent Integrator executable. It allows multiple SNMP agents and SMUX subagents from any vendor to coexist on the same node and to appear as a single SNMP agent to any SNMP manager.

The Agent Integrator can simultaneously support any number of:

- SNMP agents

- SMUX subagents

- Master agents such as other SMUX or DPI master agents or any other proprietary master agents. (The master agent must respond to requests from a manager using SNMP.)

Also, the Agent Integrator can coexist on the standard SNMP port (161/udp) with any other SNMP agent. It directly supports the SMUX MIB (RFC 1227) in addition to the `system(1)` and `snmp(3)` groups of MIB II.

When the program is running as an SNMP agent, it generates a coldStart trap to the host specified by the TRAP_HOST entry in the `beamgr.conf` file at startup. If there is no TRAP_HOST entry, the trap is sent to port 162 on the host where the utility is running, with a community defined as `public`.

Read-write and read-only communities supported by the Integrator can be specified in the `beamgr_snmpd.conf` file. By default, read-only community is `public` and read-write community is `beamgr`.

You may configure the Agent Integrator to expect a password from SMUX subagents registering with it. For more information, refer to "BEA Manager Passwords File (beamgr_snmpd.conf)."

#### UNIX

The `-d` argument is usually used when the program is executed on the command line for debugging purposes. Messages displayed are sent to the standard output of the program. If the program is started by `init`(1M), the destination of these messages is determined by the UNIX platform and version. These messages are most frequently sent to the console.

The `-n` argument is usually used when the program is started by `init`(1M) with the respawn option.

#### Windows NT

Messages displayed with the `-d` argument are sent to the NT Event Log.

The `-n` argument has no effect.

## stop_agents

### Syntax

>     stop_agents logical_agent_name | all [logical_agent_name}

### Arguments

`all`
  Stops all BEA Manager agents (including any agents built using the BEA Manager Agent Development Kit).

`logical_agent_name`
  For all BEA Manager agents other than `tux_snmpd` and `m3_snmpd`, the logical agent name is always the name of the executable.