2.1 Introduction

2.1.1 Native Operating System Support

2.2 Windows NT 4.0 Systems

2.2.1 Installing SNMP on a Windows NT 4.0 System

2.2.2 Configuring SNMP on a Windows NT 4.0 System

2.2.3 Running SNMP on a Windows NT 4.0 System

2.2.4 OAM Package Uninstallation

2.3 Solaris Systems

2.3.1 Installing SNMP on a Solaris System

2.3.2 Configuring SNMP on a Solaris System

2.3.3 Modifying NmsChassis.acl

2.3.4 Registration Files

2.3.5 Modifying snmpdx.acl

2.3.6 Modifying enterprises.oid File

2.3.7 Modifying rc3

2.3.8 Running SNMP on a Solaris System

2.3.9 Stopping SNMP Subagents on a Solaris System

2.4 Unixware Systems

2.4.1 Installing SNMP on a Unixware System

2.4.2 Configuring SNMP on a Unixware System

2.4.3 Modifying snmpd.peers

2.4.4 Modifying the snmpd.trap File

2.4.5 Modifying the snmpd.comm File

2.4.6 Running SNMP on a Unixware System

2.4.7 Stopping SNMP on a Unixware System

2.5 Sample snmp.cfg File

2.1 Introduction

This chapter lists procedures for installing and activating SNMP software on:

• Windows NT 4.0 Systems

• SPARC Solaris Systems (version 7.0.1 or later)

• Unixware Systems (version 7)

• Intel Solaris Systems (versions 2.6 and 7)

This chapter also provides a sample configuration (snmp.cfg) file in Section 2.5.

2.1.1 Native Operating System Support

All agents from NMS work in conjunction with the native SNMP master agent for every supported operating system. NMS subagents run under the control of this master agent.

2.2 Windows NT 4.0 Systems

This section describes how to install, configure, and run SNMP on a Windows NT 4.0 system. For more detailed configuration information, see the Windows NT 4.0 documentation for SNMP.

2.2.1 Installing SNMP on a Windows NT 4.0 System

1. Install the SNMP service from the Windows NT 4.0 distribution CD.
   If the SNMP service does not already exist, you must add the SNMP service as a network service.

2. Install the NMS SNMP package, included on the Natural Access CD-ROM. There are two methods for installing this package, depending on which version of CT Access you will be using.

3. For CT Access 4.0 or later, install the OAM service.
   Installing the OAM service from a Natural Access CD-ROM also installs the NMS SNMP subagents. For information about installing OAM, see the OAM System User's Manual.

4. For CT Access 3.x, install CT Access.
   Installing CT Access from a Natural Access CD-ROM also installs the NMS SNMP subagents. For information about installing CT Access, see the CT Access Installation Manual.

5. Reinstall the version of Windows NT Service Pack you were running on your system.

6. Configure SNMP. See Section 2.2.2.

7. Start SNMP by issuing the following commands from a command prompt:
   net stop snmp
   net start snmp

2.2.2 Configuring SNMP on a Windows NT 4.0 System

1. Run the agSnmp.exe utility.

   WARNING:

   The Windows NT 4.0 SNMP service must be installed before running this utility.

   Command line options are:

   Option	Description
   -I	Installs all SNMP subagents.
   -U	Uninstalls all SNMP subagents.
   -A agent_name	Installs or uninstalls the subagents.

   For example:

   Command	Description
   agSnmp -I	Installs all subagents.
   agSnmp -U	Uninstalls all subagents.
   agSnmp -I -A snmpDtmAgent	Installs the DtmAgent only.
   agSnmp -U -A snmpNmsChassis	Uninstalls the NmsChassis subagent only.

2. Click on the Network icon in the Control Panel. The Network dialog box displays. Select the Services tab.

3. Select SNMP Service and click Properties.
   The SNMP Properties dialog appears.

4. Select the Traps tab.
   Add a Community Name. For example, public.

5. Add the addresses of the hosts that you wish to send traps to, if any, to the Trap Destination list.

6. Apply the changes, close the SNMP Properties dialog, and close the Network dialog.

2.2.3 Running SNMP on a Windows NT 4.0 System

The NMS SNMP agents will not recognize any boards unless ctdaemon is running in client server mode. Make sure that the DTM service is specified in the cta.cfg file. The default cta.cfg configuration file does specify DTM. See the CT Access Developer's Reference Manual for more information about cta.cfg. See the T1/E1 Digital Trunk Monitor Service Developer's Reference Manual for information about DTM.

If ctdaemon stops running, the agents will not report any data to SNMP requests.

Note: The SNMP subagents will continue to work whether or not ctdaemon is running. If you restart this process while a subagent is running, boards will be detected (if configured).

For CT Access 4.0 or later, refer to the Natural Access installation booklet and to the OAM System User's Manual for more information about installing CT Access and the OAM service.

For versions of CT Access prior to 4.0, agmon must be started. You must also specify the AIS service and the ADI service in the cta.cfg file. Refer to the AG Runtime Configuration and Developer's Manual for more information about agmon.

2.2.4 OAM Package Uninstallation

If you wish to uninstall the OAM package from your system, you need to ensure that you have stopped the SNMP service. In addition, invoke the following command:

agSnmp -U

Once these steps have been taken, the OAM package can be uninstalled safely.

2.3 Solaris Systems

This section describes how to install, configure, and run SNMP on a Solaris system. For more detailed configuration information, see the Solstice Enterprise Agents User Guide.

2.3.1 Installing SNMP on a Solaris System

1. Install the Solstice Enterprise Agent for Solaris.

2. Install the NMS SNMP package, included on the Natural Access CD-ROM. There are two methods for installing this package, depending on which version of CT Access you are using.

3. For CT Access 4.0 or later, install the OAM service.
   Installing the OAM service from a Natural Access CD-ROM also installs the NMS SNMP subagents. For information about installing OAM, see the OAM System User's Manual.

4. For CT Access 3.x, install CT Access.
   Installing CT Access from a Natural Access CD-ROM also installs the NMS SNMP subagents. For information about installing CT Access, see the CT Access Installation Manual.

5. Configure SNMP. See Section 2.3.2.

6. Reboot the system, or stop and restart the master agent. To stop and restart the master agent:
   From a console window, run the following command:

   ps -A | grep snmpdx
   
   

   If the master agent is running, the command will produce output similar to:

   136 ?   0:00 snmpdx
   
   

   If the master agent is running, run the kill command to send a kill signal to that process. Using the output from the example above, as a superuser, run the command:

   kill -9 136
   

   Another way to stop the master agent process is by invoking:

   /etc/init.d/init.snmpdx stop
   
   

   As a superuser, run the command:

   /usr/lib/snmp/snmpdx
   
   

   or:

   /etc/init.d/init.snmpdx start
   
   

   to start the master agent.

2.3.2 Configuring SNMP on a Solaris System

To configure SNMP, run the agSnmp utility.

Command line options are:

Option	Description
-I	Installs all SNMP subagents.
-U	Uninstalls all SNMP subagents.
-A agent_name	Specifies a subagent to install or uninstall.

For example:

Command	Description
agSnmp -I	Installs all subagents.
agSnmp -U	Uninstalls all subagents.
agSnmp -I -A snmpDtmAgent	Installs the DTM subagent only.
agSnmp -U -A snmpNmsChassis	Uninstalls the NMS Chassis subagent.

The following files are loaded into the /etc/snmp/conf directory when the NMS Chassis subagent is configured with the agSnmp utility:

File	Description
NmsChassis.acl	Chassis MIB access control file. Optionally, modify the community names to add security.
NmsChassis.rsrc	Chassis MIB registration file. No modifications are necessary.

The following files are loaded into the /etc/snmp/conf directory when the DTM subagent is configured with the agSnmp utility:

File	Description
DtmAgent.acl	DS1 MIB access control file. Optionally, modify the community names to add security.
DtmAgent.rsrc	DS1 MIB registration file. No modifications are necessary.

The following files are loaded when Solaris is installed. The agSnmp utility modifies these files as necessary:

File	Description
snmpdx.acl	Master agent access control file.
snmpdx.rsrc	Master agent registration file. Defines subagents to the master agent.
enterprises.oid	Lists the OIDs of enterprise subtrees.

The entries in the NmsChassis.acl file must match the entries in the snmpdx.acl file. The snmpdx.acl file defines the NMS subagents to Solaris. The NmsChassis.acl and DtmAgent.acl files define parameters for the NMS subagents.

2.3.3 Modifying NmsChassis.acl

The NmsChassis.acl file consists of two sections:

• Access Control: If you wish to modify the community names to enhance security, modify this section. The community name acts as a password to allow access to the MIB information on this node. The value Public allows any host to access this node, so you may want to change it. You can also specify hosts that you wish to receive requests from. The default setting (*) allows any host to make SNMP requests.

  ##################
  # access control # 
  ##################
  
  # The list of community names needed for read/write access
  # to the entire MIB.
  # If the list is empty, the only valid community name
  # is "public" and its access type is read-only
  
  acl = {
          {
       communities = public, private
       access = read-write
       managers = *
          }
  }
  
  
  

• Trap Parameters: If you wish to send traps, uncomment the trap parameters area, then edit these parameters to add the hosts you will send traps to, and the community string. Make the trap-num equal to 1, which is the number of trap types that the chassis subagent can send. A modified version of the trap parameters section is shown in the following example:

  ###################
  # trap parameters #
  ###################
  trap = {
   {
    trap-community = public
    hosts = myhost, localhost
      {
        enterprise = "Nms Chassis"
        trap-num = 1
      }
   }
  }
  

2.3.4 Registration Files

Registration files (NmsChassis.rsrc and DtmAgent.rsrc) consist of the following sections:

• Macros: Define the path to the MIB in the MIB namespace. No modifications are necessary.

• Agent: Defines settings for the subagent. NMS has filled in the necessary fields. An example of this section of the file for the Chassis MIB is provided:

  agents =
  {
     {
      name = "NmsChassis"
      subtrees = { nmschassis }
      timeout = 4000000
      watch-dog-time = 0
     }
  }
  

2.3.5 Modifying snmpdx.acl

The snmpdx.acl file consists of the following sections:

• Access Control: No modifications are necessary.

• Trap Parameters: If you wish to send traps, modify snmpdx.acl to define the chassis subagent to the Solaris master agent. Add a community string that matches the one you added to NmsChassis.acl. Uncomment the section that defines the NMS Chassis subagent, and enter 1 as the trap-num value, as shown in the following example:

  ###################
  # trap parameters #
  ###################
  
  trap = {
    {
   trap-community = public
   hosts = myhost
   {
     enterprise = "sun"
     trap-num = 0, 1, 2-5, 6-16
    }
  # {
  #   enterprise = "Nms Chassis"
  #   trap-num = 1
  # }
  

2.3.6 Modifying enterprises.oid File

Make sure that the NMS chassis subagent has been defined to this Solaris system file, as shown in the following example:

"Nms Chassis"      "1.3.6.1.4.1.2628.2.2.6"
"DS1"      "1.3.6.1.2.1.10.18.15"

This entry can be anywhere in the file, which defines the OIDs for all enterprise MIBs known to the system.

2.3.7 Modifying rc3

Modify /etc/rc3 to add:

LD_LIBRARY_PATH=/opt/nms/lib
export LD_LIBRARY_PATH

2.3.8 Running SNMP on a Solaris System

The NMS SNMP agents will not recognize any boards unless ctdaemon is running in client server mode. Make sure that the DTM service is specified in the cta.cfg file. The default cta.cfg configuration file does specify DTM. See the CT Access Developer's Reference Manual for more information about cta.cfg. See the T1/E1 Digital Trunk Monitor Service Developer's Reference Manual for information about DTM.

If ctdaemon stops running, the agents will not report any data to SNMP requests.

Note: The SNMP subagents will continue to work whether or not ctdaemon is running. If you restart this process while a subagent is running, boards will be detected (if configured).

For CT Access 4.0 or later, refer to the Natural Access installation booklet and to the OAM System User's Manual for more information about starting CT Access and the OAM service.

For versions of CT Access prior to 4.0, agmon must be started. You must also specify the AIS service and the ADI service in the cta.cfg file. Refer to the AG Runtime Configuration and Developer's Manual for more information about agmon.

To check that either process is running, run the ps commands in a console window. For example:

ps -A | grep ctdaemon

which will produce output similar to:

106 ? 0:00 ctdaemon

If either of these processes stops running, the agents will not report any data to SNMP requests.

2.3.9 Stopping SNMP Subagents on a Solaris System

Run the ps command to find the process ID for each subagent. For example, if you are running the DTM subagent,

ps -A | grep snmpDtmAgent

will produce output similar to:

126 ?   0:00 snmpDtmAgent

Run the kill command to send a kill signal to that process. Using the output from the example above, run the command:

kill -15 126

to kill the snmpDtmAgent process.

2.4 Unixware Systems

This section describes how to install, configure, and run SNMP on a Unixware system. For more detailed configuration information, see the Unixware SNMP documentation.

2.4.1 Installing SNMP on a Unixware System

Install the NMS SNMP package, included on the Natural Access CD-ROM. There are two methods for installing this package, depending on which version of CT Access you are using.

• For CT Access 4.0 or later, install the OAM service.
  Installing the OAM service from a Natural Access CD-ROM also installs the NMS SNMP subagents. For information about installing OAM, see the OAM System User's Manual.

• For CT Access 3.x, install CT Access.
  Installing CT Access from a Natural Access CD-ROM also installs the NMS SNMP subagents. For information about installing CT Access, see the CT Access Installation Manual.

2.4.2 Configuring SNMP on a Unixware System

The following files are loaded into the /etc/netmgt directory when Unixware is installed:

File	Description
snmpd.peers	Defines subagents to the Unixware SNMP agent.
snmpd.trap	Defines host systems to which SNMP will send trap information.
snmpd.comm	Defines host systems that will be allowed to set SNMP variables.

If these files do not exist on your system, see the Unixware SNMP documentation.

2.4.3 Modifying snmpd.peers

The Unixware system file /etc/netmgt/snmpd.peers defines subagents to the Unixware SNMP daemon. Add the following lines to the bottom of snmpd.peers to define the NMS subagents:

"snmpNmsChassis" 1.3.6.1.4.1.2628.2.2.6 "nopassword"
"snmpDtmAgent" 1.3.6.1.2.1.10.18.15 "nopassword"

2.4.4 Modifying the snmpd.trap File

The Unixware system file /etc/netmgt/snmpd.trap defines which systems will receive traps. If you want the system to send traps, add the following line to the snmpd.trap file:

ip group_name ip_address 162

where group_name is the group name, ip_address is the address of the host system, and 162 is the port number.

For example,

ip public 10.1.7.68 162

tells the system to send traps to the IP address 10.1.7.68 on port 162, under the group name public.

Note: The value ip_address must be given in numerical form.

2.4.5 Modifying the snmpd.comm File

The Unixware file /etc/netmgt/snmpd.comm defines which systems will be able to set SNMP variables. Add the following line for each system you wish to allow to use SNMP set:

ip group_name ip_address write

where group_name is the group name, and ip_address is the address of the host system. The IP address 0.0.0.0 allows all systems access.

For example,

ip admin 0.0.0.0 write

allows all systems using the group name admin to read and write SNMP variables.

2.4.6 Running SNMP on a Unixware System

1. The SNMP master agent (in.snmpd) should be running. If it is not, see the Unixware SNMP documentation. To check that the process is running, run the ps command in a console window:
   ps -A | grep in.snmpd
   You should see output similar to this:
   1026 TS 85 pts/3 0:00 in.snmpd

2. Ensure that all CT Access environment variables are properly set, as specified in the CT Access Installation Manual.
   The NMS SNMP agents will not recognize any boards unless ctdaemon is running in client server mode. Make sure that the DTM service is specified in the cta.cfg file. The default cta.cfg configuration file does specify DTM. See the CT Access Developer's Reference Manual for more information about cta.cfg. See the T1/E1 Digital Trunk Monitor Service Developer's Reference Manual for information about DTM.
   If ctdaemon stops running, the agents will not report any data to SNMP requests.
   The SNMP subagents will continue to work whether or not this process is running. If you restart this process while a subagent is running, boards will be detected (if configured).
   For CT Access 4.0 or later, refer to the Natural Access installation booklet and to the OAM System User's Manual for more information about starting CT Access and the OAM service.
   For versions of CT Access prior to 4.0, agmon must be started. You must also specify the AIS service and the ADI service in the cta.cfg file. Refer to the AG Runtime Configuration and Developer's Manual for more information about agmon.
   To check that either process is running, run the ps command in a console window. For example:
   ps -A | grep ctdaemon
   which will produce output similar to
   1028 TS 85 pts/3 0:00 ctdaemon

3. Login as root, and start the NMS subagents using the following commands:

   Command	Description
   snmpNmsChassis	Starts the NMS Chassis subagent.
   snmpDtmAgent	Starts the DTM subagent.

2.4.7 Stopping SNMP on a Unixware System

Run the ps command to find the process ID for each subagent. For example, if you are running the DTM subagent: ps -A | grep snmpDtmAgent

will produce output similar to:

1026 TS 85 pts/3 0:00 snmpDtmAgent

Run the kill command to send a kill signal to that process. Using the output from the example above, run the command:

kill -15 1026

to kill the snmpDtmAgent process.

2.5 Sample snmp.cfg File

This section provides an example snmp.cfg file. The uncommented entries in this file set the value of variables in the NMS Chassis MIB when the SNMP subagent is started.

#===============================================================
# snmp.cfg
#
# This is an example of a file that specifies SNMP configuration.
#
#===============================================================


[chassis]
#Unknown chassis
#chassType  = 1

#CPCI chassis
chassType = 2

#Generic PC chassis
#chassType = 3

#Generic Sun chassis
#chasType = 4

#chassDescr = Generic PC development computer


[board]
#boardDescr = 0, Tested 01/25/1991
#boardDescr = 1, Bad
#boardDescr = 3, Bad


[allowSet]
#boardCommand = off