Installing SNM Agents

Solstice Enterprise Manager 4.1 Installation Guide

Chapter 6

Installing SNM Agents

This chapter provides instructions for installing SunNet Manager (SNM) Agents that are shipped with Solstice Enterprise Manager (Solstice EM) software. Install these on remote systems.

This chapter describes the following topics:

Section 6.1 Updating NIS Maps or NIS+ Tables for SNM Agents
Section 6.2 SNM RPC Agents
Section 6.3 Using pkgadd to Install Agents
Section 6.4 Using getagents to Install Agents

6.1 Updating NIS Maps or NIS+ Tables for SNM Agents

If you plan to use the SunNet Manager (SNM) agents and are running NIS or NIS+, you must update the NIS services and rpc.bynumber maps or the equivalent tables in NIS+.

To Update NIS Maps or NIS+ Tables

1. On the master NIS or NIS+ server, log in as root or become superuser.
For example:

hostname% su
Password: ************
2. Edit the /etc/services file by adding the following lines:

snmp 161/udp # Simple Network Mgmt Protocol

snmp-trap 162/udp snmptrap # SNMP trap (event) messages
3. If the following lines do not exist in the /etc/rpc file, edit the file to add the following lines:

event 100101 na.event

logger 100102 na.logger

sync 100104 na.sync

diskinfo 100105 na.diskinfo

iostat 100106 na.iostat

hostperf 100107 na.hostperf

activity 100109 na.activity

lpstat 100111 na.lpstat

hostmem 100112 na.hostmem

sample 100113 na.sample

ping 100115 na.ping

rpcnfs 100116 na.rpcnfs

hostif 100117 na.hostif

etherif 100118 na.etherif

ippath 100119 na.ippath

iproutes 100120 na.iproutes

layers 100121 na.layers

snmp 100122 na.snmp

traffic 100123 na.traffic

layers2 100131 na.layers2

etherif2 100135 na.etherif2

iostat2 100136 na.iostat2

hostmem2 100137 na.hostmem2
4. Implement the changes by using one of the following methods:

If you are running NIS, update the maps using the ypmake command, then push the maps out to the slave NIS servers using the yppush command.
If you are running NIS+, update the tables using the nisaddent command.
Note – Refer to your system administration documentation if you need additional information on these commands.
5. Look for, and send a signal to, the inetd process by typing the following commands:

# ps -ef | grep inetd
# kill -HUP processnumber
In the preceding command, processnumber is the inetd process number.

6.2 SNM RPC Agents

The workstation running the Solstice EM MIS is the focal point for collecting and analyzing information. It receives the information from data collection programs (agents), which usually run on remote machines.

The Solstice EM software includes SNM RPC agents that run on:

Solaris 2.0 and compatible systems on a SPARC platform
Solaris 2.0 and compatible systems on an x86 platform
SunOS 4.1 and compatible systems on a SPARC platform

You install these agents on remote Solaris 2.0 and compatible systems by running the pkgadd program. You install agents on remote SunOS 4.1 and compatible systems by running getagents.

Solstice EM provides tools (the Viewer and the Object Configuration Tool) that enable you to configure machines as SNM RPC agents. With the proper configuration and with SNM agents installed, you can manage SNM agents similar to the way you use Solstice EM to manage CMIP or SNMP objects.

Note – Throughout this chapter, the term "MIS machine" designates the machine on which the SNM agents package is installed. In fact, you need not have installed the agents package on the same machine as the MIS. If you did not, when performing the procedures here, substitute the name of the machine on which the agents package is installed for the name of the MIS machine.

6.3 Using pkgadd to Install Agents

The SNM agents are contained in the Site/SunNet/Domain Agents and Libraries package (SUNWsnmag). You have already installed the SUNWsnmag package, if you:

Chose to install the Solstice EM MIS component using the setup program
Selected the SUNWsnmag package during installation using the pkgadd command

This section describes how to install the SUNWsnmag package using pkgadd.

To Install Agents Using the pkgadd Utility

1. Log in as root.

2. Change to the directory where the CD-ROM is mounted.
Usually, this directory is /cdrom/solstice_em_4.1
For example.

cd /cdrom/solstice_em_4.1
3. Perform one of the following steps, as applicable:
To install in the default location, type the following pkgadd command:

pkgadd -d . SUNWsnmag

This command installs the packages in the default directory /opt
To install in a directory other than the default, type the following command:

pkgadd -d . -a none SUNWsnmag
During the installation, you will be asked questions regarding the following:

Executing scripts with superuser permissions
Installing files with setuid and/or setgid permissions
4. For each of the questions you are asked, type y if you want to continue, or n if you do not.

5. If you are installing the Site/SunNet/Domain Manager Agents and Libraries Package, answer the questions for this package:

Specify the location of the SNM log files or press Return if the default of /var/opt/SUNWconn/snm is acceptable.
Verify your selection by pressing Return, or type n to specify another location.
Note – On an x86 platform, the SUNWsnmag package is referred to as SUNW86nma. This package name appears only inside the actual script text.

The pkgadd script terminates after this package is installed, and the menu showing the various packages available for installation is displayed. Type q to quit the installation procedure.

6.4 Using getagents to Install Agents

This section contains an overview of the getagents script, information on copying scenarios, and the following procedures:

Running the getagents script using an NFS mount
Running the getagents script using rcp
Overview of the getagents script

The getagents script allows a Sun^TM machine to run SNM agents and proxy agents by editing system files (similar to what the installation script does) and copying agents, libraries, and the SNMP proxy agent schema from the MIS machine to another machine. The script makes backup copies of all system files that are modified.

Specifically, the getagents script does the following:

Copies the agents, schema files, libraries, and native SNMP agent files from the MIS machine.
Under SunOS 4.0 and compatible versions, creates symbolic links from the libnetmgt.sa.2.0 and libnetmgt.so.2.0 shared library files to /usr/lib. These files are used by SNM agent and manager applications. If the link creation fails, an error message is printed, and you need to make the links yourself.
Note – Shared library files (or links to them) should be placed in /usr/lib. If you put them somewhere else, run ldconfig(8) with the library path names.

Adds SNM agent entries to /etc/rpc--see rpc(5).
Adds SNMP definitions to the /etc/services file for SunOS 4.x systems.
Updates /etc/inetd.conf under SunOS 4.x and asks inetd(8C) to reread its configuration file. See the inetd.conf(5) man page.
Creates a sample database file you can add to your management database on an SNM Console machine (if you are running SNM somewhere on your network).
Creates the /var/adm/snm/snmp.hosts file as well as the /var/adm/snm/snmp.traps file for use by the SNMP proxy agent.

6.4.1 Copying Scenarios

The MIS machine can make files available to other machines in several ways. Two common approaches are NFS and rcp(1). NFS is the recommended method, but an option that does not exist at every site. If rcp is used, the /.rhosts file on the MIS machine must contain the name of the remote (agent) machine, allowing the agent machine root access to the MIS machine. After you have installed the agents, you can remove the agent machine name from the MIS machine's /.rhosts file to restore security.

Because the getagents script copies files across the network, it needs to know what access method is going to be used for the copy. The three basic scenarios are:

The system has the Solstice EM distribution NFS mounted from the MIS machine. Do not copy the agents because you will run the agents over the mount.
The system has the Solstice EM distribution NFS mounted from the MIS machine. You want to copy the agents because you will run the agents from a different file system.
The Solstice EM distribution is not NFS mounted, so rcp is needed to copy the agents.

The programs do not use copy methods such as tftp(1).

6.4.2 Running getagents Using an NFS Mount

In the following procedure, the local machine (agenthost) has the Solstice EM distribution files NFS mounted from the manager (mgrhost) station.

To run the getagents script using an NFS mount:

1. Log in as root on the MIS machine.
2. Type the commands to export the file system and start the NFS daemons, if they are not already running.

share -F nfs -o ro /opt/SUNWconn/snm
/usr/lib/nfs/nfsd 8
/usr/lib/nfs/mountd
3. Log in as root to the machine that runs the agents (this machine is referred to as the local machine).
4. Create a mount point on the local machine.

mkdir mountpoint
5. Mount the Solstice EM software on your local machine from the MIS machine (by default, in /opt/SUNWconn/snm directory)

mount mgrhost:/opt/SUNWconn/snm/4.x mountpoint
Note – You must specify an absolute path when specifying the mount point using the mount command.
6. Run the getagents script from the bin directory under the mount point you created on the local machine.

./mountpoint/bin/getagents
The getagents script starts and asks for the name of the directory where you are installing the agents.

7. Press Return if /opt/SUNWconn/snm is correct, specify a directory, or type NFS to run the agents over an NFS mount.

Note – If you type NFS, the getagents script asks for the name of the root directory under which the Solstice EM agents and libraries are located. Go to Step10.

After specifying a directory, the getagents script asks if you want to create the agents directory.

8. Press Return to create the directory.

The getagents script asks for the name of the host where the agents are located.

9. Press Return to accept the default, localhost.

The getagents script asks for the name of the root directory under which the agents and libraries are located.

10. Type the name of the mount point you created in Step4.

The getagents script creates library links, then asks if you want to install the Sun SNMP agent.

11. Choose one of the following options:

If you want to install the Sun SNMP agent, press Return.
If you do not, type n.
Note – If you type n, the getagents script creates the /etc/snm.conf file, then asks for the location of the database files. Go to Step15.

The getagents script displays several messages and information about community names, then asks for the read community name.

12. To accept the default read community name, "public," press Return, or enter a new read community name.

The getagents script asks if you want to change the default write community name.

13. To accept the default write community name, "private," press Return, or enter a new write community name.
The getagents script then displays lines that must be added to the /etc/rc.local file, and asks if you want them to be added now.

To run the Sun SNMP agent at each reboot, the following lines

need to be added to the end of /etc/rc.local:

if [ -f /etc/snmpd.conf -a -x /usr/etc/snmpd ]; then

/usr/etc/snmpd -c /etc/snmpd.conf && echo `Starting snmpd.'

fi

Would you like me to do this? [y]
14. If you want to add these lines, press Return, or type n if you do not.

If you type n, you must manually update the file after the installation.
The getagents script creates the /etc/snm.conf file, then asks for the location of the database files.

15. To accept the default location, /var/adm/snm, press Return, or type n to specify a different location.

If you type n, you are prompted for the location of the database files.
The getagents script then asks for the location of the log files.

16. To accept the default location, /var/adm/snm, press Return, or type n to specify a different location.

If you type n, you will be prompted for the location of the log files.
The getagents script creates snmp files, updates other files, and displays a message that it has finished.
You have installed the agents, and they are ready to run and be managed on this system.

6.4.3 Running getagents Using rcp

The following procedure uses rcp to copy agents from mgrhost (the MIS machine) to agenthost (the local host). To run the getagents script using rcp, follow these steps:

1. Log in as root.

2. If /.rhosts does not exist, type the command touch /.rhosts to create it.
3. Set up the MIS machine to allow root access across the network for the host(s) that will be running getagents (add agenthost to the list of trusted hosts).

# cat >>/.rhosts
agenthost
^D
4. Copy getagents from the MIS machine to the local machine.

# rlogin agenthost
Password: *********
SunOS Release 4.1.1 (AGENTHOST) #1: Wed May 6 12:30:46 PDT 1992

# rcp mgrhost:/opt/SUNWconn/snm/bin/getagents /tmp
5. Run the getagents script.

The getagents script starts and asks for the name of the directory where the agents will be installed.
The following instructions assume you have copied getagents to /tmp on the local host, although you can copy it to any directory.

6. To accept the default, /usr/snm press Return, or type the name of a different directory.

The getagents script asks if you want to create this directory.

7. If you want to create the directory, press Return, or type n if you do not.

The getagents script asks for the name of the host where the agents are located.

8. To accept the default, <localhost>, press Return, or enter a host name.

The getagents script asks for the name of the root directory on the MIS machine under which the agents and libraries are located.

9. To accept the default, /opt/SUNWconn/snm press Return, or enter a directory of your choice.

The getagents script continues, installs the agents, then asks if you want to install the Sun SNMP agent.

10. If you want to install the Sun SNMP agent, press Return, or type n if you do not.

Note – If you type n, the getagents script creates the /etc/snm.conf file, then asks for the location of the database files. Go to Step14.

The getagents script displays several messages and information about community names, then asks for the read community name.

11. To accept the default read community name, "public," press Return, or enter a new read community name.

The getagents script then asks if you want to change the default write community name.

12. To accept the default write community name, "private," press Return, or enter a new write community name.
The getagents script displays lines that must be added to the /etc/rc.local file, and asks if you want them to be added now.

To run the Sun SNMP agent at each reboot, the following lines

need to be added to the end of /etc/rc.local:

if [ -f /etc/snmpd.conf -a -x /usr/etc/snmpd ]; then

/usr/etc/snmpd -c /etc/snmpd.conf && echo `Starting snmpd.'

fi

Would you like me to do this? [y]
13. If you want the lines added now, press Return, or type n if you do not.

If you type n, be sure to manually update the file after the installation.
The getagents script creates the /etc/snm.conf file, then asks for the location of the database files.

14. To accept the default location of the database files, /var/adm/snm press Return, or type n to specify a different location.

If you type n, you are prompted for the location of the database files.
The getagents script then asks for the location of the log files.

15. To accept the default location for the log files, /var/adm/snm press Return, or type n to specify a different location.

If you type n, you are prompted for the location of the log files.
The getagents script creates snmp files, updates other files, and displays a message that it has finished.
You have now installed the agents, and they are ready to run and be managed on this system.
Note – If you previously modified the /.rhosts file on the MIS machine to temporarily allow root access to other hosts, you should now remove the entries to prevent future security breaches.

hostname% su Password: ************

snmp 161/udp # Simple Network Mgmt Protocol snmp-trap 162/udp snmptrap # SNMP trap (event) messages

event 100101 na.event logger 100102 na.logger sync 100104 na.sync diskinfo 100105 na.diskinfo iostat 100106 na.iostat hostperf 100107 na.hostperf activity 100109 na.activity lpstat 100111 na.lpstat hostmem 100112 na.hostmem sample 100113 na.sample ping 100115 na.ping rpcnfs 100116 na.rpcnfs hostif 100117 na.hostif etherif 100118 na.etherif ippath 100119 na.ippath iproutes 100120 na.iproutes layers 100121 na.layers snmp 100122 na.snmp traffic 100123 na.traffic layers2 100131 na.layers2 etherif2 100135 na.etherif2 iostat2 100136 na.iostat2 hostmem2 100137 na.hostmem2

# ps -ef \| grep inetd # kill -HUP processnumber

cd /cdrom/solstice_em_4.1

pkgadd -d . SUNWsnmag

pkgadd -d . -a none SUNWsnmag

share -F nfs -o ro /opt/SUNWconn/snm /usr/lib/nfs/nfsd 8 /usr/lib/nfs/mountd

mkdir mountpoint

mount mgrhost:/opt/SUNWconn/snm/4.x mountpoint

./mountpoint/bin/getagents

To run the Sun SNMP agent at each reboot, the following lines need to be added to the end of /etc/rc.local: if [ -f /etc/snmpd.conf -a -x /usr/etc/snmpd ]; then /usr/etc/snmpd -c /etc/snmpd.conf && echo `Starting snmpd.' fi Would you like me to do this? [y]

# cat >>/.rhosts agenthost ^D

# rlogin agenthost Password: ******* SunOS Release 4.1.1 (AGENTHOST) #1: Wed May 6 12:30:46 PDT 1992 # rcp mgrhost:/opt/SUNWconn/snm/bin/getagents /tmp**

To run the Sun SNMP agent at each reboot, the following lines need to be added to the end of /etc/rc.local: if [ -f /etc/snmpd.conf -a -x /usr/etc/snmpd ]; then /usr/etc/snmpd -c /etc/snmpd.conf && echo `Starting snmpd.' fi Would you like me to do this? [y]

Doc Set | Contents | Previous | Next | Index