Technical article 118824

SNMP is not working correctly when I use the getmany(ADMN) command.

OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

I am trying to use the getmany(ADMN) command to retrieve a class of
variables from an SNMP entity on a specific machine.  When I wanted to
get a variable in a class from a machine running OpenServer 5.0.4 and
earlier, I could use the command:
getmany [machine] public iso

This would traverse the entire variable tree for that machine's network entity and print the output:

Name: sysDescr.0
Value: SCO TCP/IP Runtime Release 2.0.0
Name: sysObjectID.0
Value: SCO.1.2.0.0
Name: sysUpTime.0
Value: 188918843
Name: sysContact.0
Value: [Name]
Name: sysName.0
Value: [machine].[domain]
...
I could also configure the /etc/snmpd.conf file to change the value of
some of the variables.  However, when I use getmany to retrieve a
variable from either a local machine or remote machine running
OpenServer 5.0.5 or 5.0.6, I get the following errors:

getmany: no response -- retrying. getmany: no response -- retrying.

The error loops until I kill the process.

Cause

There is a file called /etc/snmpd.comm that lists the definitions for
the communities that the snmpd daemon can support.  If the snmpd
daemon cannot find any communities to support on either a local or
remote machine, it will not be able to retrieve information from any
class of variables on that machine.  Community entries in this file
were uncommented in OpenServer 5.0.4, but were commented out in
OpenServer 5.0.5 and 5.0.6.

Solution

To allow snmpd to access a community, vi the /etc/snmpd.comm file for the machine that is not allowing SNMP access:

#test1    0.0.0.0        READ
#test2    127.0.0.1      WRITE
#public   0.0.0.0        READ

and uncomment the appropriate community line; usually "#public":

#test1    0.0.0.0        READ
#test2    127.0.0.1      WRITE
public    0.0.0.0        READ

You should then be able to use the snmpd daemon to retrieve the appropriate variables for that machine.

Please keep in mind that public access should always have READ privileges only as it is set to be accessible by any host (0.0.0.0).

See also

snmpd(ADMN), snmpd.comm(SFF), snmpd.conf(SFF)

From the Xinuos technical article database, record 118824. Reproduced with permission. The original is at www.sco.com/ta/118824, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.