unexpected behaviour with net-snmp-5.1-80.3 under SLES 9

[email protected]
Newsgroups gmane.network.net-snmp.user
Message-ID <OF18880441.6775E359-ONC125708B.002329EE-C125708B.00244DA3@gavi.de>
dear community member,

we ´ve got net-snmp-5.1-80.3 running under SLES9.
Since we have problems to get percentage of mountpoint usage via 
"hrStorageSize" and "hrStorageUsed" we refer to 
the net-snmp community in hope to get a solution or workaround.

An snmpwalk through the "host" section of MIBII passes the tree exactly up 
to hrStorageSize. From this point on it doesn´t 
provide any further values. This behaviour seems to occur specifically 
within net-snmp-5.1-80.3 under SLES9 
(reproducable on several other machines with same OS). The installation of 
net-snmp has been carried out effectively
"out of the box".

You may have a look on our configuration of snmpd.conf to prevent that 
configuration failures has been made.


Is there a known bug or similar strange behaviour concerning this 
constellation ?
is there a hint or workaround to fix this ?
Are there any other versions of net-snmp available for SLES9 ?

kind regards
Roland

Roland Tomuschat
Abteilung SP1 
Netzwerkmanagement
70376 Stuttgart
Löwentorstraße 65
Tel. 0711/898-2208
Fax: 0711/898-2036
snmpd.conf (application/octet-stream, 4.4 KB)
###########################################################################
#
# snmpd.conf
#
#   - created by the snmpconf configuration program
#
###########################################################################
# SECTION: Access Control Setup
#
#   This section defines who is allowed to talk to your running
#   snmp agent.

# rocommunity: a SNMPv1/SNMPv2c read-only access community name
#   arguments:  community [default|hostname|network/bits] [oid]

rocommunity public 127.0.0.1
rocommunity  18rem2cv  

# rwcommunity: a SNMPv1/SNMPv2c read-write access community name
#   arguments:  community [default|hostname|network/bits] [oid]

rwcommunity  18rem2rw

###########################################################################
# SECTION: Trap Destinations
#
#   Here we define who the agent will send traps to.

# trapsink: A SNMPv1 trap receiver
#   arguments: host [community] [portnum]

trapsink  10.2.29.11  

# trap2sink: A SNMPv2c trap receiver
#   arguments: host [community] [portnum]

trap2sink  10.2.29.11  



###########################################################################
# SECTION: Monitor Various Aspects of the Running Host
#
#   The following check up on various aspects of a host.

# proc: Check for processes that should be running.
#     proc NAME [MAX=0] [MIN=0]
#   
#     NAME:  the name of the process to check for.  It must match
#            exactly (ie, http will not find httpd processes).
#     MAX:   the maximum number allowed to be running.  Defaults to 0.
#     MIN:   the minimum number to be running.  Defaults to 0.
#   
#   The results are reported in the prTable section of the UCD-SNMP-MIB tree
#   Special Case:  When the min and max numbers are both 0, it assumes
#   you want a max of infinity and a min of 1.

proc  Xvnc 2 2

# disk: Check for disk space usage of a partition.
#   The agent can check the amount of available disk space, and make
#   sure it is above a set limit.  
#   
#    disk PATH [MIN=100000]
#   
#    PATH:  mount path to the disk in question.
#    MIN:   Disks with space below this value will have the Mib's errorFlag set.
#           Can be a raw byte value or a percentage followed by the %
#           symbol.  Default value = 100000.
#   
#   The results are reported in the dskTable section of the UCD-SNMP-MIB tree

disk  /work 3006292
disk  /install 3637628



###########################################################################
# SECTION: Agent Operating Mode
#
#   This section defines how the agent will operate when it
#   is running.

# master: Should the agent operate as a master agent or not.
#   Currently, the only supported master agent type for this token
#   is "agentx".
#   
#   arguments: (on|yes|agentx|all|off|no)

master  agentx

# agentaddress: The IP address and port number that the agent will listen on.
#   By default the agent listens to any and all traffic from any
#   interface on the default SNMP port (161).  This allows you to
#   specify which address, interface, transport type and port(s) that you
#   want the agent to listen on.  Multiple definitions of this token
#   are concatenated together (using ':'s).
#   arguments: [transport:]port[@interface/address],...

agentaddress  



###########################################################################
# SECTION: System Information Setup
#
#   This section defines some of the information reported in
#   the "system" mib group in the mibII tree.

# syslocation: The [typically physical] location of the system.
#   Note that setting this value here means that when trying to
#   perform an snmp SET operation to the sysLocation.0 variable will make
#   the agent return the "notWritable" error code.  IE, including
#   this token in the snmpd.conf file will disable write access to
#   the variable.
#   arguments:  location_string

syslocation Server Room
syslocation  "SL SP1-S"

# syscontact: The contact information for the administrator
#   Note that setting this value here means that when trying to
#   perform an snmp SET operation to the sysContact.0 variable will make
#   the agent return the "notWritable" error code.  IE, including
#   this token in the snmpd.conf file will disable write access to
#   the variable.
#   arguments:  contact_string

syscontact Sysadmin (root@localhost)
syscontact  [email protected]

# sysservices: The proper value for the sysServices object.
#   arguments:  sysservices_number

sysservices 0
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.