Enabling the seaProxy Module

On arrival at port 161, incoming requests that are intended for the Solstice Enterprise Agents software are received by the SMA. If a proxy exists for the request, the request is passed to the snmpdx daemon. From the snmpdx daemon, the request is passed to the Solstice Enterprise Agents software subagents. The seaProxy module generates dynamic proxies, which are not found in snmpd.conf. Dynamic proxies are based on static and dynamic Solstice Enterprise Agents subagent registrations. The seaProxy module uses Solstice Enterprise Agents subagent registration details to generate dynamic proxies.

To enable the seaProxy module provided with the System Management Agent, verify that in the /etc/sma/snmp/snmpd.conf file, for systems running on x86 platforms, the following line is configured:

dlmod seaProxy /usr/sfw/lib/libseaProxy.so

To enable the seaProxy module provided with the System Management Agent, verify that in the /etc/sma/snmp/snmpd.conf file, for systems running on SPARC platforms, the following line is configured:

dlmod seaProxy /usr/sfw/lib/sparcv9/libseaProxy.so

When the seaProxy module loads, the seaProxy module immediately begins collecting information from the Solstice Enterprise Agents subagent. For this reason, among others, the snmpd daemon must start up after the snmpdx daemon. If the snmpd daemon starts up before snmpdx daemon, the SMA re-reads the Solstice Enterprise Agents software subagent registration table. The snmpdx daemon can be running before the snmpd daemon if, for example, you stop and restart the snmpd daemon.

The seaProxy module uses the information in the software subagent registration table to generate proxies for those Solstice Enterprise Agents software subagents that have already registered.

The seaProxy module does not generate proxies for the mibiisa subagent.