Use the SNMP Agent Manager to:
The SNMP Agent Manager allows you to perform most SNMP configuration graphically. You can start the SNMP Agent Manager in any of these ways:
Fatal error: building package index for `/usr/lib/scoadmin/snmpmgr/generic.tlib' failed: couldn't open "/usr/lib/scoadmin/snmpmgr/generic.tndx": permission deniedTo resolve this problem, run the SNMP Agent Manager as root. After it has been run once by root, the SNMP Agent Manager can then be run by any user with owner privileges.
For more information on using SCOadmin managers, see ``Administering your system with SCOadmin''.
To configure SNMP:
To limit the list to those hosts matching a certain pattern, enter the pattern (including wildcard characters) in the ``Filter'' field, then click on Filter. Then, select the host name from the list and click on OK.
To sort the list by name or address, click on the appropriate radio button.
The system group contains the basic information that the SNMP agent needs. These are:
Generally, only the latter three items need to be updated.
Enter the appropriate information in each field, and click on OK when done.
The last item, SMUX reserved classes, allows you to specify those SMUX MIB classes that may only be managed by the local agent. Any classes not listed here may be, but will not necessarily be, managed by other SNMP agents.
When you make changes to the system group using the SNMP Agent Manager, the information is placed into the file /etc/snmpd.conf:
Sample snmpd.conf file
descr=SCO TCP/IP Runtime Release 2.0.0 objid=SCO.220.127.116.11 contact=Trevor Jones x 256 location=First Floor Computer Room smux_reserved=sco
An SNMP community is a group of hosts that you can manage as a distinct group with SNMP.
The SNMP communities group contains a list of community/IP address pairs identifying those management stations from which the agent on the local host accepts queries. Along with each pair is an access field that controls whether access is allowed, and if so, whether the access granted is read-only or read-write. In addition, the special community public, with an address of 0.0.0.0, restricts or allows access to all other members of the public community.
With the Community Names Editor of the SNMP Agent Manager, you can:
The changes you make are saved to the file /etc/snmpd.comm
when you click on OK in the information screen.
By default, this file originally contains one
public 0.0.0.0 read. This allows
read access to all members of the public community.
The following is an example of /etc/snmpd.comm. In this example, system 18.104.22.168 of community ``mynet.rivers'' is allowed read access only, whereas system 22.214.171.124 of community ``mynet.cities'' is allowed read and write access. Note that the public community default read access has been changed to no access.
Sample snmpd.comm file
# community address access # public 0.0.0.0 none mynet.rivers 126.96.36.199 read mynet.cities 188.8.131.52 write
The trap group contains a list of community/IP address pairs identifying those management stations to which the agent sends traps following unusual events, such as a ``cold start''. The trap IP port can also be modified; its default value is 162.
With the Trap Configuration Editor of the SNMP Agent Manager, you can:
The changes you make are saved to the file /etc/snmpd.trap when you click on OK in the information screen:
Sample snmpd.trap file
# community address port # mynet.rivers 184.108.40.206 162 mynet.cities 220.127.116.11 162
The peers group contains a list of SMUX peers known to the local SNMP agent. This information is needed only to enable the agent to communicate with a SMUX peer that exports a specific MIB module. Fields include:
With the Peers Configuration Editor of the SNMP Agent Manager, you can:
The changes you make are saved to the file /etc/snmpd.peers when you click on OK in the information screen:
Sample snmpd.peers file
# # <name> <object-id> <password> [<priority>] # "gated" 18.104.22.168.22.214.171.124.126.96.36.199 "gated_password" "foo" 188.8.131.52.184.108.40.206.99 "aintNoThing" -1