-###############################################################################\r
-#\r
-# EXAMPLE.conf:\r
-# An example configuration file for configuring the ucd-snmp snmpd agent.\r
-\r
-#\r
-###############################################################################\r
-#\r
-# This file is intended to only be an example. If, however, you want\r
-# to use it, it should be placed in /etc/snmp/snmpd.conf.\r
-\r
-# When the snmpd agent starts up, this is where it will look for it.\r
-#\r
-# You might be interested in generating your own snmpd.conf file using\r
-# the "snmpconf" program (perl script) instead. It's a nice menu\r
-\r
-# based interface to writing well commented configuration files. Try it!\r
-#\r
-# Note: This file is automatically generated from EXAMPLE.conf.def.\r
-# Do NOT read the EXAMPLE.conf.def file! Instead, after you have run\r
-\r
-# configure & make, and then make sure you read the EXAMPLE.conf file\r
-# instead, as it will tailor itself to your configuration.\r
-\r
-# All lines beginning with a '#' are comments and are intended for you\r
-\r
-# to read. All other lines are configuration commands for the agent.\r
-\r
-#\r
-# PLEASE: read the snmpd.conf(5) manual page as well!\r
-#\r
-\r
-\r
-###############################################################################\r
-\r
-# Access Control\r
-###############################################################################\r
-\r
-# YOU SHOULD CHANGE THE "COMMUNITY" TOKEN BELOW TO A NEW KEYWORD ONLY\r
-# KNOWN AT YOUR SITE. YOU *MUST* CHANGE THE NETWORK TOKEN BELOW TO\r
-\r
-# SOMETHING REFLECTING YOUR LOCAL NETWORK ADDRESS SPACE.\r
-\r
-# By far, the most common question I get about the agent is "why won't\r
-# it work?", when really it should be "how do I configure the agent to\r
-\r
-# allow me to access it?"\r
-#\r
-# By default, the agent responds to the "public" community for read\r
-# only access, if run out of the box without any configuration file in # place. The following examples show you other ways of configuring \r
-# the agent so that you can change the community names, and give\r
-# yourself write access as well.\r
-#\r
-# The following lines change the access permissions of the agent so\r
-# that the COMMUNITY string provides read-only access to your entire\r
-\r
-# NETWORK (EG: 10.10.10.0/24), and read/write access to only the\r
-# localhost (127.0.0.1, not its real ipaddress).\r
-#\r
-# For more information, read the FAQ as well as the snmpd.conf(5)\r
-\r
-# manual page.\r
-\r
-####\r
-# First, map the community name (COMMUNITY) into a security name\r
-# (local and mynetwork, depending on where the request is coming\r
-# from):\r
-\r
-# sec.name source community\r
-\r
-#com2sec paranoid default public\r
-#com2sec paranoid localhost private\r
-com2sec readonly default public\r
+###############################################################################
+#
+# EXAMPLE.conf:
+# An example configuration file for configuring the ucd-snmp snmpd agent.
+
+#
+###############################################################################
+#
+# This file is intended to only be an example. If, however, you want
+# to use it, it should be placed in /etc/snmp/snmpd.conf.
+
+# When the snmpd agent starts up, this is where it will look for it.
+#
+# You might be interested in generating your own snmpd.conf file using
+# the "snmpconf" program (perl script) instead. It's a nice menu
+
+# based interface to writing well commented configuration files. Try it!
+#
+# Note: This file is automatically generated from EXAMPLE.conf.def.
+# Do NOT read the EXAMPLE.conf.def file! Instead, after you have run
+
+# configure & make, and then make sure you read the EXAMPLE.conf file
+# instead, as it will tailor itself to your configuration.
+
+# All lines beginning with a '#' are comments and are intended for you
+
+# to read. All other lines are configuration commands for the agent.
+
+#
+# PLEASE: read the snmpd.conf(5) manual page as well!
+#
+
+
+###############################################################################
+
+# Access Control
+###############################################################################
+
+# YOU SHOULD CHANGE THE "COMMUNITY" TOKEN BELOW TO A NEW KEYWORD ONLY
+# KNOWN AT YOUR SITE. YOU *MUST* CHANGE THE NETWORK TOKEN BELOW TO
+
+# SOMETHING REFLECTING YOUR LOCAL NETWORK ADDRESS SPACE.
+
+# By far, the most common question I get about the agent is "why won't
+# it work?", when really it should be "how do I configure the agent to
+
+# allow me to access it?"
+#
+# By default, the agent responds to the "public" community for read
+# only access, if run out of the box without any configuration file in # place. The following examples show you other ways of configuring
+# the agent so that you can change the community names, and give
+# yourself write access as well.
+#
+# The following lines change the access permissions of the agent so
+# that the COMMUNITY string provides read-only access to your entire
+
+# NETWORK (EG: 10.10.10.0/24), and read/write access to only the
+# localhost (127.0.0.1, not its real ipaddress).
+#
+# For more information, read the FAQ as well as the snmpd.conf(5)
+
+# manual page.
+
+####
+# First, map the community name (COMMUNITY) into a security name
+# (local and mynetwork, depending on where the request is coming
+# from):
+
+# sec.name source community
+
+#com2sec paranoid default public
+#com2sec paranoid localhost private
+com2sec readonly default public
com2sec readwrite default private
rocommunity public
-rwcommunity private\r
+rwcommunity private
rocommunity COMMUNITY SOURCE -V VIEW
-\r
-####\r
-# Second, map the security names into group names:\r
-\r
-\r
-# sec.model sec.name\r
-group MyROSystem v1 paranoid\r
-group MyROSystem v2c paranoid\r
-group MyROSystem usm paranoid\r
-group MyROGroup v1 readonly\r
-\r
-group MyROGroup v2c readonly\r
-group MyROGroup usm readonly\r
-group MyRWGroup v1 readwrite\r
-group MyRWGroup v2c readwrite\r
-group MyRWGroup usm readwrite\r
-\r
-####\r
-# Third, create a view for us to let the groups have rights to:\r
-\r
-\r
-# incl/excl subtree mask\r
-view all included .1 80\r
-view system included .iso.org.dod.internet.mgmt.mib-2.system \r
-####\r
-# Finally, grant the 2 groups access to the 1 view with different\r
-# write permissions:\r
-\r
-# context sec.model sec.level match read write notif\r
-access MyROSystem "" any noauth exact system none none\r
-\r
-access MyROGroup "" any noauth exact all none none\r
-access MyRWGroup "" any noauth exact all all none\r
-\r
-# -----------------------------------------------------------------------------\r
-\r
-\r
-\r
-###############################################################################\r
-# System contact information\r
-#\r
-\r
-# It is also possible to set the sysContact and sysLocation system\r
-# variables through the snmpd.conf file. **PLEASE NOTE** that setting\r
-\r
-# the value of these objects here makes these objects READ-ONLY\r
-# (regardless of any access control settings). Any attempt to set the\r
-# value of an object whose value is given here will fail with an error\r
-# status of notWritable.\r
-\r
-\r
-syslocation Unknown (configure /etc/snmp/snmpd.local.conf)\r
-syscontact Root <root@localhost> (configure /etc/snmp/snmpd.local.conf)\r
-\r
-# Example output of snmpwalk:\r
-# % snmpwalk -v 1 -c public localhost system\r
-\r
-# system.sysDescr.0 = "SunOS name sun4c"\r
-# system.sysObjectID.0 = OID: enterprises.ucdavis.ucdSnmpAgent.sunos4\r
-# system.sysUpTime.0 = Timeticks: (595637548) 68 days, 22:32:55\r
-# system.sysContact.0 = "Me <me@somewhere.org>"\r
-\r
-# system.sysName.0 = "name"\r
-# system.sysLocation.0 = "Right here, right now."\r
-# system.sysServices.0 = 72\r
-\r
-\r
-# -----------------------------------------------------------------------------\r
-\r
-\r
-\r
-###############################################################################\r
-# Process checks.\r
-#\r
-# The following are examples of how to use the agent to check for\r
-# processes running on the host. The syntax looks something like:\r
-\r
-#\r
-# proc NAME [MAX=0] [MIN=0]\r
-#\r
-# NAME: the name of the process to check for. It must match\r
-# exactly (ie, http will not find httpd processes).\r
-# MAX: the maximum number allowed to be running. Defaults to 0.\r
-\r
-# MIN: the minimum number to be running. Defaults to 0.\r
-\r
-#\r
-# Examples:\r
-#\r
-\r
-# Make sure mountd is running\r
-#proc mountd\r
-\r
-# Make sure there are no more than 4 ntalkds running, but 0 is ok too.\r
-\r
-#proc ntalkd 4\r
-\r
-# Make sure at least one sendmail, but less than or equal to 10 are running.\r
-#proc sendmail 10 1\r
-\r
-# A snmpwalk of the prTable would look something like this:\r
-# # % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.2 \r
-# enterprises.ucdavis.procTable.prEntry.prIndex.1 = 1\r
-# enterprises.ucdavis.procTable.prEntry.prIndex.2 = 2\r
-# enterprises.ucdavis.procTable.prEntry.prIndex.3 = 3\r
-# enterprises.ucdavis.procTable.prEntry.prNames.1 = "mountd"\r
-\r
-# enterprises.ucdavis.procTable.prEntry.prNames.2 = "ntalkd"\r
-# enterprises.ucdavis.procTable.prEntry.prNames.3 = "sendmail"\r
-# enterprises.ucdavis.procTable.prEntry.prMin.1 = 0\r
-# enterprises.ucdavis.procTable.prEntry.prMin.2 = 0\r
-\r
-# enterprises.ucdavis.procTable.prEntry.prMin.3 = 1\r
-# enterprises.ucdavis.procTable.prEntry.prMax.1 = 0\r
-# enterprises.ucdavis.procTable.prEntry.prMax.2 = 4\r
-# enterprises.ucdavis.procTable.prEntry.prMax.3 = 10\r
-\r
-# enterprises.ucdavis.procTable.prEntry.prCount.1 = 0\r
-# enterprises.ucdavis.procTable.prEntry.prCount.2 = 0\r
-# enterprises.ucdavis.procTable.prEntry.prCount.3 = 1\r
-# enterprises.ucdavis.procTable.prEntry.prErrorFlag.1 = 1\r
-\r
-# enterprises.ucdavis.procTable.prEntry.prErrorFlag.2 = 0\r
-# enterprises.ucdavis.procTable.prEntry.prErrorFlag.3 = 0\r
-# enterprises.ucdavis.procTable.prEntry.prErrMessage.1 = "No mountd process running."\r
-\r
-# enterprises.ucdavis.procTable.prEntry.prErrMessage.2 = ""\r
-# enterprises.ucdavis.procTable.prEntry.prErrMessage.3 = ""\r
-# enterprises.ucdavis.procTable.prEntry.prErrFix.1 = 0\r
-# enterprises.ucdavis.procTable.prEntry.prErrFix.2 = 0\r
-\r
-# enterprises.ucdavis.procTable.prEntry.prErrFix.3 = 0\r
-#\r
-# Note that the errorFlag for mountd is set to 1 because one is not\r
-# running (in this case an rpc.mountd is, but thats not good enough),\r
-# and the ErrMessage tells you what's wrong. The configuration\r
-\r
-# imposed in the snmpd.conf file is also shown. # # Special Case: When the min and max numbers are both 0, it assumes \r
-# you want a max of infinity and a min of 1.\r
-#\r
-\r
-\r
-# -----------------------------------------------------------------------------\r
-\r
-\r
-###############################################################################\r
-\r
-# Executables/scripts\r
-#\r
-\r
-#\r
-# You can also have programs run by the agent that return a single\r
-# line of output and an exit code. Here are two examples.\r
-#\r
-# exec NAME PROGRAM [ARGS ...]\r
-#\r
-# NAME: A generic name.\r
-\r
-# PROGRAM: The program to run. Include the path!\r
-# ARGS: optional arguments to be passed to the program\r
-\r
-# a simple hello world\r
-#exec echotest /bin/echo hello world\r
-\r
-# Run a shell script containing:\r
-\r
-#\r
-# #!/bin/sh\r
-# echo hello world\r
-# echo hi there\r
-# exit 35\r
-#\r
-# Note: this has been specifically commented out to prevent\r
-# accidental security holes due to someone else on your system writing\r
-# a /tmp/shtest before you do. Uncomment to use it.\r
-\r
-#\r
-#exec shelltest /bin/sh /tmp/shtest\r
-# Then, # % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.8 \r
-# enterprises.ucdavis.extTable.extEntry.extIndex.1 = 1\r
-# enterprises.ucdavis.extTable.extEntry.extIndex.2 = 2\r
-# enterprises.ucdavis.extTable.extEntry.extNames.1 = "echotest"\r
-\r
-# enterprises.ucdavis.extTable.extEntry.extNames.2 = "shelltest"\r
-# enterprises.ucdavis.extTable.extEntry.extCommand.1 = "/bin/echo hello world"\r
-# enterprises.ucdavis.extTable.extEntry.extCommand.2 = "/bin/sh /tmp/shtest"\r
-\r
-# enterprises.ucdavis.extTable.extEntry.extResult.1 = 0\r
-# enterprises.ucdavis.extTable.extEntry.extResult.2 = 35\r
-# enterprises.ucdavis.extTable.extEntry.extOutput.1 = "hello world."\r
-# enterprises.ucdavis.extTable.extEntry.extOutput.2 = "hello world."\r
-\r
-# enterprises.ucdavis.extTable.extEntry.extErrFix.1 = 0\r
-# enterprises.ucdavis.extTable.extEntry.extErrFix.2 = 0\r
-\r
-# Note that the second line of the /tmp/shtest shell script is cut\r
-# off. Also note that the exit status of 35 was returned.\r
-\r
-\r
-# -----------------------------------------------------------------------------\r
-\r
-\r
-###############################################################################\r
-# disk checks\r
-#\r
-\r
-# The agent can check the amount of available disk space, and make\r
-\r
-# sure it is above a set limit. \r
-# disk PATH [MIN=DEFDISKMINIMUMSPACE]\r
-#\r
-# PATH: mount path to the disk in question.\r
-# MIN: Disks with space below this value will have the Mib's errorFlag set.\r
-# Default value = DEFDISKMINIMUMSPACE.\r
-\r
-\r
-# Check the / partition and make sure it contains at least 10 megs.\r
-\r
-#disk / 10000\r
-disk / 10%\r
-disk /home 10%\r
-\r
-# % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.9\r
-# enterprises.ucdavis.diskTable.dskEntry.diskIndex.1 = 0\r
-\r
-# enterprises.ucdavis.diskTable.dskEntry.diskPath.1 = "/" Hex: 2F # enterprises.ucdavis.diskTable.dskEntry.diskDevice.1 = "/dev/dsk/c201d6s0" \r
-# enterprises.ucdavis.diskTable.dskEntry.diskMinimum.1 = 10000\r
-# enterprises.ucdavis.diskTable.dskEntry.diskTotal.1 = 837130\r
-# enterprises.ucdavis.diskTable.dskEntry.diskAvail.1 = 316325\r
-\r
-# enterprises.ucdavis.diskTable.dskEntry.diskUsed.1 = 437092\r
-# enterprises.ucdavis.diskTable.dskEntry.diskPercent.1 = 58\r
-# enterprises.ucdavis.diskTable.dskEntry.diskErrorFlag.1 = 0\r
-# enterprises.ucdavis.diskTable.dskEntry.diskErrorMsg.1 = ""\r
-\r
-\r
-# -----------------------------------------------------------------------------\r
-\r
-\r
-###############################################################################\r
-# load average checks\r
-#\r
-\r
-# load [1MAX=DEFMAXLOADAVE] [5MAX=DEFMAXLOADAVE] [15MAX=DEFMAXLOADAVE]\r
-\r
-#\r
-# 1MAX: If the 1 minute load average is above this limit at query\r
-# time, the errorFlag will be set.\r
-# 5MAX: Similar, but for 5 min average.\r
-# 15MAX: Similar, but for 15 min average.\r
-\r
-# Check for loads:\r
-\r
-load 12 14 14\r
-\r
-# % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.10\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveIndex.1 = 1\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveIndex.2 = 2\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveIndex.3 = 3\r
-\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveNames.1 = "Load-1"\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveNames.2 = "Load-5"\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveNames.3 = "Load-15"\r
-\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveLoad.1 = "0.49" Hex: 30 2E 34 39 # enterprises.ucdavis.loadTable.laEntry.loadaveLoad.2 = "0.31" Hex: 30 2E 33 31 # enterprises.ucdavis.loadTable.laEntry.loadaveLoad.3 = "0.26" Hex: 30 2E 32 36 # enterprises.ucdavis.loadTable.laEntry.loadaveConfig.1 = "12.00" \r
-# enterprises.ucdavis.loadTable.laEntry.loadaveConfig.2 = "14.00"\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveConfig.3 = "14.00"\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveErrorFlag.1 = 0\r
-\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveErrorFlag.2 = 0\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveErrorFlag.3 = 0\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveErrMessage.1 = ""\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveErrMessage.2 = ""\r
-\r
-# enterprises.ucdavis.loadTable.laEntry.loadaveErrMessage.3 = ""\r
-\r
-# -----------------------------------------------------------------------------\r
-\r
-\r
-###############################################################################\r
-\r
-# Extensible sections.\r
-# \r
-# This alleviates the multiple line output problem found in the\r
-# previous executable mib by placing each mib in its own mib table:\r
-\r
-# Run a shell script containing:\r
-#\r
-# #!/bin/sh\r
-\r
-# echo hello world\r
-# echo hi there\r
-# exit 35\r
-#\r
-# Note: this has been specifically commented out to prevent\r
-# accidental security holes due to someone else on your system writing\r
-# a /tmp/shtest before you do. Uncomment to use it.\r
-\r
-#\r
-# exec .1.3.6.1.4.1.2021.50 shelltest /bin/sh /tmp/shtest\r
-\r
-# % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.50\r
-# enterprises.ucdavis.50.1.1 = 1\r
-# enterprises.ucdavis.50.2.1 = "shelltest"\r
-\r
-# enterprises.ucdavis.50.3.1 = "/bin/sh /tmp/shtest"\r
-# enterprises.ucdavis.50.100.1 = 35\r
-# enterprises.ucdavis.50.101.1 = "hello world."\r
-# enterprises.ucdavis.50.101.2 = "hi there."\r
-\r
-# enterprises.ucdavis.50.102.1 = 0\r
-\r
-# Now the Output has grown to two lines, and we can see the 'hi\r
-# there.' output as the second line from our shell script.\r
-#\r
-# Note that you must alter the mib.txt file to be correct if you want\r
-\r
-# the .50.* outputs above to change to reasonable text descriptions.\r
-\r
-# Other ideas:\r
-# # exec .1.3.6.1.4.1.2021.51 ps /bin/ps # exec .1.3.6.1.4.1.2021.52 top /usr/local/bin/top \r
-# exec .1.3.6.1.4.1.2021.53 mailq /usr/bin/mailq\r
-\r
-# -----------------------------------------------------------------------------\r
-\r
-\r
-###############################################################################\r
-\r
-# Pass through control.\r
-# \r
-# Usage:\r
-# pass MIBOID EXEC-COMMAND\r
-#\r
-# This will pass total control of the mib underneath the MIBOID\r
-# portion of the mib to the EXEC-COMMAND. # \r
-# Note: You'll have to change the path of the passtest script to your\r
-# source directory or install it in the given location.\r
-# # Example: (see the script for details) \r
-# (commented out here since it requires that you place the\r
-# script in the right location. (its not installed by default))\r
-\r
-# pass .1.3.6.1.4.1.2021.255 /bin/sh /usr/local/passtest\r
-\r
-\r
+
+####
+# Second, map the security names into group names:
+
+
+# sec.model sec.name
+group MyROSystem v1 paranoid
+group MyROSystem v2c paranoid
+group MyROSystem usm paranoid
+group MyROGroup v1 readonly
+
+group MyROGroup v2c readonly
+group MyROGroup usm readonly
+group MyRWGroup v1 readwrite
+group MyRWGroup v2c readwrite
+group MyRWGroup usm readwrite
+
+####
+# Third, create a view for us to let the groups have rights to:
+
+
+# incl/excl subtree mask
+view all included .1 80
+view system included .iso.org.dod.internet.mgmt.mib-2.system
+####
+# Finally, grant the 2 groups access to the 1 view with different
+# write permissions:
+
+# context sec.model sec.level match read write notif
+access MyROSystem "" any noauth exact system none none
+
+access MyROGroup "" any noauth exact all none none
+access MyRWGroup "" any noauth exact all all none
+
+# -----------------------------------------------------------------------------
+
+
+
+###############################################################################
+# System contact information
+#
+
+# It is also possible to set the sysContact and sysLocation system
+# variables through the snmpd.conf file. **PLEASE NOTE** that setting
+
+# the value of these objects here makes these objects READ-ONLY
+# (regardless of any access control settings). Any attempt to set the
+# value of an object whose value is given here will fail with an error
+# status of notWritable.
+
+
+syslocation Unknown (configure /etc/snmp/snmpd.local.conf)
+syscontact Root <root@localhost> (configure /etc/snmp/snmpd.local.conf)
+
+# Example output of snmpwalk:
+# % snmpwalk -v 1 -c public localhost system
+
+# system.sysDescr.0 = "SunOS name sun4c"
+# system.sysObjectID.0 = OID: enterprises.ucdavis.ucdSnmpAgent.sunos4
+# system.sysUpTime.0 = Timeticks: (595637548) 68 days, 22:32:55
+# system.sysContact.0 = "Me <me@somewhere.org>"
+
+# system.sysName.0 = "name"
+# system.sysLocation.0 = "Right here, right now."
+# system.sysServices.0 = 72
+
+
+# -----------------------------------------------------------------------------
+
+
+
+###############################################################################
+# Process checks.
+#
+# The following are examples of how to use the agent to check for
+# processes running on the host. The syntax looks something like:
+
+#
+# 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.
+
+#
+# Examples:
+#
+
+# Make sure mountd is running
+#proc mountd
+
+# Make sure there are no more than 4 ntalkds running, but 0 is ok too.
+
+#proc ntalkd 4
+
+# Make sure at least one sendmail, but less than or equal to 10 are running.
+#proc sendmail 10 1
+
+# A snmpwalk of the prTable would look something like this:
+# # % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.2
+# enterprises.ucdavis.procTable.prEntry.prIndex.1 = 1
+# enterprises.ucdavis.procTable.prEntry.prIndex.2 = 2
+# enterprises.ucdavis.procTable.prEntry.prIndex.3 = 3
+# enterprises.ucdavis.procTable.prEntry.prNames.1 = "mountd"
+
+# enterprises.ucdavis.procTable.prEntry.prNames.2 = "ntalkd"
+# enterprises.ucdavis.procTable.prEntry.prNames.3 = "sendmail"
+# enterprises.ucdavis.procTable.prEntry.prMin.1 = 0
+# enterprises.ucdavis.procTable.prEntry.prMin.2 = 0
+
+# enterprises.ucdavis.procTable.prEntry.prMin.3 = 1
+# enterprises.ucdavis.procTable.prEntry.prMax.1 = 0
+# enterprises.ucdavis.procTable.prEntry.prMax.2 = 4
+# enterprises.ucdavis.procTable.prEntry.prMax.3 = 10
+
+# enterprises.ucdavis.procTable.prEntry.prCount.1 = 0
+# enterprises.ucdavis.procTable.prEntry.prCount.2 = 0
+# enterprises.ucdavis.procTable.prEntry.prCount.3 = 1
+# enterprises.ucdavis.procTable.prEntry.prErrorFlag.1 = 1
+
+# enterprises.ucdavis.procTable.prEntry.prErrorFlag.2 = 0
+# enterprises.ucdavis.procTable.prEntry.prErrorFlag.3 = 0
+# enterprises.ucdavis.procTable.prEntry.prErrMessage.1 = "No mountd process running."
+
+# enterprises.ucdavis.procTable.prEntry.prErrMessage.2 = ""
+# enterprises.ucdavis.procTable.prEntry.prErrMessage.3 = ""
+# enterprises.ucdavis.procTable.prEntry.prErrFix.1 = 0
+# enterprises.ucdavis.procTable.prEntry.prErrFix.2 = 0
+
+# enterprises.ucdavis.procTable.prEntry.prErrFix.3 = 0
+#
+# Note that the errorFlag for mountd is set to 1 because one is not
+# running (in this case an rpc.mountd is, but thats not good enough),
+# and the ErrMessage tells you what's wrong. The configuration
+
+# imposed in the snmpd.conf file is also shown. # # Special Case: When the min and max numbers are both 0, it assumes
+# you want a max of infinity and a min of 1.
+#
+
+
+# -----------------------------------------------------------------------------
+
+
+###############################################################################
+
+# Executables/scripts
+#
+
+#
+# You can also have programs run by the agent that return a single
+# line of output and an exit code. Here are two examples.
+#
+# exec NAME PROGRAM [ARGS ...]
+#
+# NAME: A generic name.
+
+# PROGRAM: The program to run. Include the path!
+# ARGS: optional arguments to be passed to the program
+
+# a simple hello world
+#exec echotest /bin/echo hello world
+
+# Run a shell script containing:
+
+#
+# #!/bin/sh
+# echo hello world
+# echo hi there
+# exit 35
+#
+# Note: this has been specifically commented out to prevent
+# accidental security holes due to someone else on your system writing
+# a /tmp/shtest before you do. Uncomment to use it.
+
+#
+#exec shelltest /bin/sh /tmp/shtest
+# Then, # % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.8
+# enterprises.ucdavis.extTable.extEntry.extIndex.1 = 1
+# enterprises.ucdavis.extTable.extEntry.extIndex.2 = 2
+# enterprises.ucdavis.extTable.extEntry.extNames.1 = "echotest"
+
+# enterprises.ucdavis.extTable.extEntry.extNames.2 = "shelltest"
+# enterprises.ucdavis.extTable.extEntry.extCommand.1 = "/bin/echo hello world"
+# enterprises.ucdavis.extTable.extEntry.extCommand.2 = "/bin/sh /tmp/shtest"
+
+# enterprises.ucdavis.extTable.extEntry.extResult.1 = 0
+# enterprises.ucdavis.extTable.extEntry.extResult.2 = 35
+# enterprises.ucdavis.extTable.extEntry.extOutput.1 = "hello world."
+# enterprises.ucdavis.extTable.extEntry.extOutput.2 = "hello world."
+
+# enterprises.ucdavis.extTable.extEntry.extErrFix.1 = 0
+# enterprises.ucdavis.extTable.extEntry.extErrFix.2 = 0
+
+# Note that the second line of the /tmp/shtest shell script is cut
+# off. Also note that the exit status of 35 was returned.
+
+
+# -----------------------------------------------------------------------------
+
+
+###############################################################################
+# disk checks
+#
+
+# The agent can check the amount of available disk space, and make
+
+# sure it is above a set limit.
+# disk PATH [MIN=DEFDISKMINIMUMSPACE]
+#
+# PATH: mount path to the disk in question.
+# MIN: Disks with space below this value will have the Mib's errorFlag set.
+# Default value = DEFDISKMINIMUMSPACE.
+
+
+# Check the / partition and make sure it contains at least 10 megs.
+
+#disk / 10000
+disk / 10%
+disk /home 10%
+
+# % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.9
+# enterprises.ucdavis.diskTable.dskEntry.diskIndex.1 = 0
+
+# enterprises.ucdavis.diskTable.dskEntry.diskPath.1 = "/" Hex: 2F # enterprises.ucdavis.diskTable.dskEntry.diskDevice.1 = "/dev/dsk/c201d6s0"
+# enterprises.ucdavis.diskTable.dskEntry.diskMinimum.1 = 10000
+# enterprises.ucdavis.diskTable.dskEntry.diskTotal.1 = 837130
+# enterprises.ucdavis.diskTable.dskEntry.diskAvail.1 = 316325
+
+# enterprises.ucdavis.diskTable.dskEntry.diskUsed.1 = 437092
+# enterprises.ucdavis.diskTable.dskEntry.diskPercent.1 = 58
+# enterprises.ucdavis.diskTable.dskEntry.diskErrorFlag.1 = 0
+# enterprises.ucdavis.diskTable.dskEntry.diskErrorMsg.1 = ""
+
+
+# -----------------------------------------------------------------------------
+
+
+###############################################################################
+# load average checks
+#
+
+# load [1MAX=DEFMAXLOADAVE] [5MAX=DEFMAXLOADAVE] [15MAX=DEFMAXLOADAVE]
+
+#
+# 1MAX: If the 1 minute load average is above this limit at query
+# time, the errorFlag will be set.
+# 5MAX: Similar, but for 5 min average.
+# 15MAX: Similar, but for 15 min average.
+
+# Check for loads:
+
+load 12 14 14
+
+# % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.10
+# enterprises.ucdavis.loadTable.laEntry.loadaveIndex.1 = 1
+# enterprises.ucdavis.loadTable.laEntry.loadaveIndex.2 = 2
+# enterprises.ucdavis.loadTable.laEntry.loadaveIndex.3 = 3
+
+# enterprises.ucdavis.loadTable.laEntry.loadaveNames.1 = "Load-1"
+# enterprises.ucdavis.loadTable.laEntry.loadaveNames.2 = "Load-5"
+# enterprises.ucdavis.loadTable.laEntry.loadaveNames.3 = "Load-15"
+
+# enterprises.ucdavis.loadTable.laEntry.loadaveLoad.1 = "0.49" Hex: 30 2E 34 39 # enterprises.ucdavis.loadTable.laEntry.loadaveLoad.2 = "0.31" Hex: 30 2E 33 31 # enterprises.ucdavis.loadTable.laEntry.loadaveLoad.3 = "0.26" Hex: 30 2E 32 36 # enterprises.ucdavis.loadTable.laEntry.loadaveConfig.1 = "12.00"
+# enterprises.ucdavis.loadTable.laEntry.loadaveConfig.2 = "14.00"
+# enterprises.ucdavis.loadTable.laEntry.loadaveConfig.3 = "14.00"
+# enterprises.ucdavis.loadTable.laEntry.loadaveErrorFlag.1 = 0
+
+# enterprises.ucdavis.loadTable.laEntry.loadaveErrorFlag.2 = 0
+# enterprises.ucdavis.loadTable.laEntry.loadaveErrorFlag.3 = 0
+# enterprises.ucdavis.loadTable.laEntry.loadaveErrMessage.1 = ""
+# enterprises.ucdavis.loadTable.laEntry.loadaveErrMessage.2 = ""
+
+# enterprises.ucdavis.loadTable.laEntry.loadaveErrMessage.3 = ""
+
+# -----------------------------------------------------------------------------
+
+
+###############################################################################
+
+# Extensible sections.
+#
+# This alleviates the multiple line output problem found in the
+# previous executable mib by placing each mib in its own mib table:
+
+# Run a shell script containing:
+#
+# #!/bin/sh
+
+# echo hello world
+# echo hi there
+# exit 35
+#
+# Note: this has been specifically commented out to prevent
+# accidental security holes due to someone else on your system writing
+# a /tmp/shtest before you do. Uncomment to use it.
+
+#
+# exec .1.3.6.1.4.1.2021.50 shelltest /bin/sh /tmp/shtest
+
+# % snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.50
+# enterprises.ucdavis.50.1.1 = 1
+# enterprises.ucdavis.50.2.1 = "shelltest"
+
+# enterprises.ucdavis.50.3.1 = "/bin/sh /tmp/shtest"
+# enterprises.ucdavis.50.100.1 = 35
+# enterprises.ucdavis.50.101.1 = "hello world."
+# enterprises.ucdavis.50.101.2 = "hi there."
+
+# enterprises.ucdavis.50.102.1 = 0
+
+# Now the Output has grown to two lines, and we can see the 'hi
+# there.' output as the second line from our shell script.
+#
+# Note that you must alter the mib.txt file to be correct if you want
+
+# the .50.* outputs above to change to reasonable text descriptions.
+
+# Other ideas:
+# # exec .1.3.6.1.4.1.2021.51 ps /bin/ps # exec .1.3.6.1.4.1.2021.52 top /usr/local/bin/top
+# exec .1.3.6.1.4.1.2021.53 mailq /usr/bin/mailq
+
+# -----------------------------------------------------------------------------
+
+
+###############################################################################
+
+# Pass through control.
+#
+# Usage:
+# pass MIBOID EXEC-COMMAND
+#
+# This will pass total control of the mib underneath the MIBOID
+# portion of the mib to the EXEC-COMMAND. #
+# Note: You'll have to change the path of the passtest script to your
+# source directory or install it in the given location.
+# # Example: (see the script for details)
+# (commented out here since it requires that you place the
+# script in the right location. (its not installed by default))
+
+# pass .1.3.6.1.4.1.2021.255 /bin/sh /usr/local/passtest
+
+
# % snmpwalk -v 1 -c public localhost .1.
-# enterprises.ucdavis.255.1 = "life the universe and everything"\r
-# enterprises.ucdavis.255.2.1 = 42\r
-# enterprises.ucdavis.255.2.2 = OID: 42.42.42\r
-\r
-# enterprises.ucdavis.255.3 = Timeticks: (363136200) 42 days, 0:42:42\r
-# enterprises.ucdavis.255.4 = IpAddress: 127.0.0.1\r
-# enterprises.ucdavis.255.5 = 42\r
-# enterprises.ucdavis.255.6 = Gauge: 42\r
-#\r
-# % snmpget -v 1 -c public localhost .1.3.6.1.4.1.2021.255.5\r
-\r
-# enterprises.ucdavis.255.5 = 42\r
-#\r
-# % snmpset -v 1 -c public localhost .1.3.6.1.4.1.2021.255.1 s "New string"\r
-# enterprises.ucdavis.255.1 = "New string"\r
-#\r
-\r
-# For specific usage information, see the man/snmpd.conf.5 manual page\r
-\r
-# as well as the local/passtest script used in the above example.\r
-\r
-###############################################################################\r
-# Subagent control\r
-#\r
-\r
-# The agent can support subagents using a number of extension mechanisms.\r
-\r
-# From the 4.2.1 release, AgentX support is being compiled in by default.\r
-# However, this is still experimental code, so should not be used on\r
-# critical production systems.\r
-# Please see the file README.agentx for more details.\r
-\r
-#\r
-# If having read, marked, learnt and inwardly digested this information,\r
-# you decide that you do wish to make use of this mechanism, simply\r
-# uncomment the following directive.\r
-#\r
-# master agentx\r
-#\r
-\r
-# I repeat - this is *NOT* regarded as suitable for front-line production\r
-# systems, though it is probably stable enough for day-to-day use.\r
-# Probably.\r
-#\r
-# No refunds will be given.\r
-\r
-\r
-###############################################################################\r
-\r
-# Further Information\r
-#\r
-# See the snmpd.conf manual page, and the output of "snmpd -H".\r
-# MUCH more can be done with the snmpd.conf than is shown as an\r
-# example here.\r
-\r
-\r
+# enterprises.ucdavis.255.1 = "life the universe and everything"
+# enterprises.ucdavis.255.2.1 = 42
+# enterprises.ucdavis.255.2.2 = OID: 42.42.42
+
+# enterprises.ucdavis.255.3 = Timeticks: (363136200) 42 days, 0:42:42
+# enterprises.ucdavis.255.4 = IpAddress: 127.0.0.1
+# enterprises.ucdavis.255.5 = 42
+# enterprises.ucdavis.255.6 = Gauge: 42
+#
+# % snmpget -v 1 -c public localhost .1.3.6.1.4.1.2021.255.5
+
+# enterprises.ucdavis.255.5 = 42
+#
+# % snmpset -v 1 -c public localhost .1.3.6.1.4.1.2021.255.1 s "New string"
+# enterprises.ucdavis.255.1 = "New string"
+#
+
+# For specific usage information, see the man/snmpd.conf.5 manual page
+
+# as well as the local/passtest script used in the above example.
+
+###############################################################################
+# Subagent control
+#
+
+# The agent can support subagents using a number of extension mechanisms.
+
+# From the 4.2.1 release, AgentX support is being compiled in by default.
+# However, this is still experimental code, so should not be used on
+# critical production systems.
+# Please see the file README.agentx for more details.
+
+#
+# If having read, marked, learnt and inwardly digested this information,
+# you decide that you do wish to make use of this mechanism, simply
+# uncomment the following directive.
+#
+# master agentx
+#
+
+# I repeat - this is *NOT* regarded as suitable for front-line production
+# systems, though it is probably stable enough for day-to-day use.
+# Probably.
+#
+# No refunds will be given.
+
+
+###############################################################################
+
+# Further Information
+#
+# See the snmpd.conf manual page, and the output of "snmpd -H".
+# MUCH more can be done with the snmpd.conf than is shown as an
+# example here.
+
+
master agentx
createUser MD5User MD5 mysecretpass DES mysecretpass