Lotus Domino Administrator 8.5 Help - Configuring the Domino SNMP Agent for z/OS

MONITORING

Configuring the Domino SNMP Agent for z/OS
Follow the steps below, once per LPAR, to configure the IBM® Lotus® Domino® SNMP Agent for z/OS®.

Before using the Domino SNMP Agent, ensure that TCP/IP and SNMP are properly installed and configured on the LPAR. Also, verify that the Domino executable and the Domino data directories are in your search path. We only support community-based security (SNMPv1 / SNMPv2 formats).

If you do not have SNMP configured on your LPAR, see the following IBM documentation to configure SNMP:

z/OS Communications Server: IP Configuration Guide, SC31-8775
z/OS Communications Server: IP Configuration Reference, SC31-8776

The SNMP agent and subagents record trace information via the z/OS® UNIX® System Services syslog daemon using the daemon facility. If you are using SNMP, set up the syslog daemon. For detailed information regarding syslogd and specifying the daemon facility in the /etc/syslog.conf configuration file, see the z/OS Communications Server manuals listed above.

Note There is also a Syslogd How To informational APAR, apar II12021.

To verify that SNMP is configured correctly, enter the following command from within Unix System Services:

osnmp -h <host name> walk system

The output should resemble the following sample output:

1.3.6.1.2.1.1.1.0 = SNMPv3 agent version 1.0 with DPI version 2.0

1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.2.3.13

1.3.6.1.2.1.1.3.0 = 1192800

1.3.6.1.2.1.1.4.0 = <userid>

1.3.6.1.2.1.1.5.0 = <hostname>

1.3.6.1.2.1.1.6.0 = <location>

1.3.6.1.2.1.1.7.0 = 76

1.3.6.1.2.1.1.8.0 = 950000

1.3.6.1.2.1.1.9.1.2.1 = 1.3.6.1.4.1.2.11.7.1

1.3.6.1.2.1.1.9.1.2.2 = 1.3.6.1.4.1.2.11.7.2

1.3.6.1.2.1.1.9.1.3.1 = z/OS SNMP Agent

1.3.6.1.2.1.1.9.1.3.2 = z/OS TCP/IP SNMP Subagent

1.3.6.1.2.1.1.9.1.4.1 = 0

1.3.6.1.2.1.1.9.1.4.2 = 1800

If the output from the osnmp command does not resemble the sample output, SNMP is not correctly configured. Verify that you have SNMP configured correctly by reviewing the z/OS Communications Server manuals prior to continuing. You need to be aware of the following when setting up SNMP for Domino:

1. If you include a SACONFIG statement in your TCP/IP profile, verify that the statement in your profile is similar to the following example:

SACONFIG ENABLED COMMUNITY public AGENT 161 SETSENABLED

You can replace public with any password you prefer. If you choose to change the password, and you use a password in /etc/pw.src, verify that you have also changed that password.

2. Verify that port 161 is reserved in your TCP/IP profile.

PORT

161 UDP OMVS ; SNMP Agent

3. Verify the procedure OSNMPD is configured correctly and that it starts after every IPL.

Note

Before setting up the OSNMPD procedure, review the " z/OS Communications Server: IP Configuration Guide" which contains important information about data set naming and search sequences.

The following is an example of an OSNMPD EXEC card:

//OSNMPD EXEC PGM=EZASNMPD,REGION=4096K,TIME=NOLIMIT,

// PARM=('POSIX(ON) ALL31(ON)',

// 'ENVAR("RESOLVER_CONFIG=/etc/resolv.conf"',

// '"OSNMPD_DATA=/etc/osnmpd.data")',

// '/-d 0')

4. Mibs.data, osnmpd.data, pw.src and snmptrap.dest are not required for running the Domino SNMP agent. However, if you choose to use these members, they must be set up correctly. Verify that these members in /etc have Read access for user, group and other.

(rwxr - - r -)

If mibs.data and osnmpd.data are not in /etc, or if they are from a previous level, you can obtain the current level from TCPIP samples located in /usr/lpp/tcpip/samples.

Note Ensure that osnmp.conf is not located in /etc, because it is reserved for user-based security.

Tip Trap destinations are defined in the SNMPTRAP.DEST dataset. Configure appropriate trap destinations and community names for your remote management infrastructure.

5. If you are using /etc/pw.src or /etc/snmpd.conf, verify that they have the correct hostname as well as the IP address for the Domino server. Hostnames are case-sensitive. Enter the following command from within UNIX System Services to obtain the correct host name for your system.

hostname

The pw.src should resemble the following sample:

HOSTNAME 9.1.2.3 255.255.255.255

public 9.1.0.0 255.255.0.0

test1 9.1.0.0 255.255.0.0

If you set SACONFIG in the TCP/IP profile to not use public, replace hostname with the password used in the SACONFIG statement.

6. Verify that snmptrap.dest has the correct hostname. Hostnames are case-sensitive.

HOSTNAME UDP

For more Information about common set up problems, see information APAR II13477.

To start the Domino SNMP agent

1. As a uid 0 user, start the LNSNMP process by typing this command:

lnsnmp.sh start

Note Automatic start of the Domino SNMP Agent is not supported on z/OS.

2. When lnsnmp is started, verify that SNMP is aware of the Domino MIB by entering the following commands:

osnmp -h <host name> walk system

The output should include this line:

1.3.6.1.2.1.1.9.1.3.3 = Lotus Domino SNMP Agent

osnmp getnext 1.3.6.1.4.1.334.72

The following should be displayed:

1.3.6.1.4.1.334.72.2.1.0 = 2

The value returned should have an OID number that starts with 1.3.6.1.4.1.334.72. This confirms that the SNMP Agent is receiving the request, forwarding it to lsnmp, and that lsnmp is returning a valid value.

If you do not see the appropriate responses shown above, or if the getnext response is for an OID outside of the Lotus Domino MIB, additional debugging is required. Start an SNMP Agent trace at level 255.

To determine whether there are additional things to check for and to obtain information about setting up an SNMP Agent trace, see informational APAR II13477.

To stop the LNSMP agent use

Enter this command:

lnsnmp.sh stop

After you complete the z/OS-specific portion of the Domino SNMP Agent configuration, complete the rest of the non-platform-specific configuration.

The Domino SNMP Agent

Troubleshooting the Domino SNMP Agent

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary