MONITORING
Configuring the Domino SNMP Agent for Solaris
Follow the steps below, once per platform, to configure the Domino SNMP Agent for Solaris.

Note Before using the Domino SNMP Agent, ensure that TCP/IP and SNMP are properly installed and configured on the server. To use the NET-SNMP Master Agent provided, refer to Using NET-SNMP with the Domino SNMP Agent. Otherwise, verify that your Master SNMP Agent supports the SMUX protocol, per RFC 1227. Ensure that the Domino executable and the Domino data directories are in your search path.

Tip If you are using the NET-SNMP Master Agent provided, the trap destinations and community names are configured in the /etc/net-snmpd.conf file. Otherwise, refer to the documentation for the master agent technology you are using. Configure appropriate trap destinations and community names for your remote management infrastructure.

Note The Domino SNMP Agent is set up to run automatically. Once the Domino SNMP Agent is configured, it is virtually always running, even when Domino is not. If you later upgrade Domino, stop the LNSNMP process, before beginning the upgrade process.

Note Execute the following commands as the root user.

1. Stop the LNSNMP process. Enter this command:


2. Stop the Master SNMP Agent. If you’re using the NET-SNMP Master Agent provided, enter this command:
3. Configure the Master SNMP Agent to accept LNSNMP as an SMUX peer. If you are using the NET-SNMP Master Agent provided, this has already been done. Otherwise, refer to your Master SNMP Agent’s documentation. The three parameters associated with SMUX authentication for LNSNMP are:
4. Start the Master SNMP Agent. If you’re using the NET-SNMP Master Agent provided, enter this command:
5. Start the LNSNMP process. Enter this command:
6. Create a link to the LNSNMP script. Enter this command, changing the Domino executable path if necessary:
7. Arrange for LNSNMP to be restarted after a reboot. Enter these commands:
You have completed the Solaris-specific portion of the Domino SNMP Agent configuration. Follow the instructions found in Completing the Configuration of the Domino SNMP Agent.

Configuring the PEER Encapsulator Agent with other master agents

If you installed the PEER Master Agent above, but were using another Master SNMP Agent and need to continue using it, you should read the remainder of this section.

Most Network Management Stations (NMS) view managed objects on a host through a single SNMP Agent. The NMS will usually direct its SNMP requests to an agent listening on port 161. Because only a single SNMP Agent can be listening at port 161, this limits the NMS to managing only the variables accessible to the one agent listening at that port. If you install the PEER Master agent, it will listen on port 161, so that all queries directed to that host will go to the PEER Master agent.

If you already have non-PEER master agents installed on that host, they too will want to listen on port 161, so you need to reconfigure these non-PEER agents to listen on other ports. Then, configure the PEER Encapsulator agent to emulate an NMS and pass on the appropriate SNMP requests from the PEER Master agent to the encapsulated agents at their respective ports. The PEER Encapsulator agent works by hiding the non-PEER agents, so they are visible to the NMS only through the PEER Master agent.

Configure the PEER Encapsulator agent to recognize non-PEER agents, respective sub-trees, SNMP ports, and traps. Then when a non-PEER agent sends a trap, the PEER Encapsulator agent listening for the trap forwards it up to the PEER Master agent or discards it, as configured. When the PEER Master agent receives an NMS SNMP request about an encapsulated agent's managed sub-tree, it passes it on to the Encapsulator agent which, in turn, forwards the request to that encapsulated agent at its listening port.

To install the PEER Encapsulator Agent enter these commands:


To configure the PEER Encapsulator Agent edit the /etc/peer.encaps.conf file, using the comments as a guide. Refer to your other Master SNMP Agent’s documentation for information about configuring it.

To start the PEER Encapsulator Agent enter this command:


This is the same command script used to start the PEER Master Agent and is responsible for both Agents if they’re both installed. Therefore, if you already configured the PEER Master Agent to restart automatically after a reboot, the PEER Encapsulator Agent will also restart automatically.

See also