search

quantum / esos

An open source, high performance, block-level storage platform.
http://www.esos-project.com/
Other
278 stars 57 forks source link

SNMP feature is missing #55

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
not everyone uses nagios, so a more public way to monitor the esos would be 
nice.
alsi impi to snmp should be done.

Original issue reported on code.google.com by mahir.ya...@gmail.com on 22 Feb 2014 at 10:12

GoogleCodeExporter commented 9 years ago 
Hi,

I know very little about SNMP. With the NRPE (Nagios), the software is 
installed, but its up to the user to write scripts/checks to use with their 
ESOS system and NRPE.

Is that how it would work with SNMP? Some software (service) needs to be 
installed and then the user would write scripts for what they want to check or 
get information on via SNMP? If so, what package?

--Marc

Original comment by msmith...@gmail.com on 23 Feb 2014 at 4:31

GoogleCodeExporter commented 9 years ago 
Hi Marc,
you should include net-snmp and net-snmp-utils in esos.
For simple configuration snmpd.conf should uncomment the line
#load 12 14 14 (System Load Monitoring)
comment the lines
view    systemview    included   .1.3.6.1.2.1.1
view    systemview    included   .1.3.6.1.2.1.25.1.1
and add a line like this
view    systemview    included   .1 (all known OIDs will be served)
add a line for disk usage
includeAllDisks MINPERCENT% 

this is all for the config.

maybe some libs or dependencies will be missing.

This will give SNMP GET readonly public access in SNMPv1 to esos.

The Trap part is also possible but i have not tested it yet.

Original comment by mahir.ya...@gmail.com on 23 Feb 2014 at 6:50

GoogleCodeExporter commented 9 years ago 
Gotcha, so I found this: 
http://sourceforge.net/projects/net-snmp/files/net-snmp/5.7.2/

And out of that package, we're really just after the 'snmpd' daemon and 
whatever is required to make it run?

--Marc

Original comment by msmith...@gmail.com on 24 Feb 2014 at 2:18

GoogleCodeExporter commented 9 years ago 
i am not sure. all seems included also the MIBS are inside.

I can tell you what i have done to get SNMP working on esos.
I use my CenOS6.2 machine and installed net-snmp and net-snmp-utils.
From the downloaded packages i copied the content to esos.
Missing libs i have copied from my source machine. That's it

I had also to modify the init scripts because esos uses rc.d and not init.d, 
but this i without problems.

In the same way i have installed the LSI MegaRais StorageManager and the LSI 
SAS SNMPAgent, works fine.

Original comment by mahir.ya...@gmail.com on 24 Feb 2014 at 2:47

GoogleCodeExporter commented 9 years ago 
I've got net-snmp nearly complete -- what about snmptrapd? Is that needed/used 
for anything? Do I need an init script for that too, or would it not be used 
with ESOS?

--Marc

Original comment by msmith...@gmail.com on 25 Feb 2014 at 9:07

GoogleCodeExporter commented 9 years ago 
this is to be discussed i think. You can use SNMPtrap for exec commands or 
collect the traps in a logfile. SMNPTrap has functions for trap2mail, this can 
be usefull.

For example snmpd is running with linkupdownnotfication=yes and includeAllDisks 
10%, then snmpd will trap to snmptrapd on localhost (esos) if link becomes up 
or down and one of the Mountpoint hass less then 10% free space. From here you 
can decide what to do.

snmptrap should only listen on localhost and not on all ipv4 adresses.
snmptrap needs his own init and config file.

smnptrapd.conf example (testing@now):
authCommunity log,execute,net public
ignoreauthfailure no
donotlogtraps no
logoption f /var/log/snmptrapd.log
#printeventnumbers yes (only work if patched, maybe included in the latest 
sources)
format1 %V\n% Agent Address: %A \n Agent Hostname: %B \n Date: %H - %J - %K - 
%L - %M - %Y \n Enterprise OID: %N \n Trap Type: %W \n Trap Sub-Type: %q \n 
Community/Infosec Context: %P \n Uptime: %T \n Description: %W \n PDU 
Attribute/Value Pair Array:\n%v \n -------------- \n
format2 %V\n% Agent Address: %A \n Agent Hostname: %B \n Date: %H - %J - %K - 
%L - %M - %Y \n Enterprise OID: %N \n Trap Type: %W \n Trap Sub-Type: %q \n 
Community/Infosec Context: %P \n Uptime: %T \n Description: %W \n PDU 
Attribute/Value Pair Array:\n%v \n -------------- \n

snmpd.conf example with restricted public acces, only snmpv3 user can see all 
mib trees  (testing@now):
###############################################################################
#
# snmpd.conf:
#   An example configuration file for configuring the ucd-snmp snmpd agent.
#
###############################################################################
#
#       Global System Settings
#
dontLogTCPWrappersConnects yes

syslocation ESOS Storage Server
syscontact root@esos.storage.server

sysservices 79 #this number has to be confirmed, maybe there is a better 
services number for a SAN/NAS

#
#       send all Traps to the local SNMP Agent
#
trapsink        127.0.0.1       public
trap2sink       127.0.0.1       public
#informsink     127.0.0.1       public
trapcommunity   public
authtrapenable  1

#
#       This is the SNMPv1 and SNMPv2c Stuff
#
com2sec notConfigUser  default       public
group   notConfigGroup v1           notConfigUser
group   notConfigGroup v2c           notConfigUser
view    systemview    included   .1.3.6.1.2.1.1
access  notConfigGroup ""      any       noauth    exact  systemview none none

#
#       What we want to test and Trap
#
load  30 10 5
includeAllDisks 10%

#linkUpDownNotifications        yes

proc snmpd 1 (i have not confirmed if proc is working with esos)
proc snmptrapd 1
proc iscsi-scstd 1
proc lsi_mrdsnmpagent 1

file  /var/log/messages 10000
file  /var/log/daemon.log 10000
file  /var/log/user.log 10000
file  /var/log/snmptrapd.log 10000

#
#       This is for the LSI SNMP Agent
#
pass .1.3.6.1.4.1.3582 /usr/sbin/lsi_mrdsnmpmain

#########################################################
#       SNMPv3 Stuff here
#########################################################
engineIDType 3 #generate from MAC

rouser  esosro noauth .1.3.6.1.2.1.1 # could be esos or public instead of esosro
# also the view is restricted in V3 
createUser      esosrw  MD5     "esosrwesosrw" # SNMPv3 User could be root or 
esos to make it unique 
#the password should be synced with the root passwd
iquerySecName   esosrw
rwuser esosrw authnopriv .1

Original comment by mahir.ya...@gmail.com on 25 Feb 2014 at 9:33

GoogleCodeExporter commented 9 years ago 
addon:
the password for snmpv3 User has to be at least 8 characters, else it will not 
allow to login. (so if it is synced with the root password this is to be known.

Original comment by mahir.ya...@gmail.com on 25 Feb 2014 at 9:36

GoogleCodeExporter commented 9 years ago 
I've added the net-snmp package; this has been committed (r577) and the 
Buildbot should have a new image posted in a few hours. Please test and confirm 
this is fixed. Please test/check the setup and make any recommendations for the 
default configuration file.

Thanks!

--Marc

Original comment by msmith...@gmail.com on 28 Feb 2014 at 9:58

GoogleCodeExporter commented 9 years ago 
in snmpd.conf agentaddress should not be 127.0.0.1 this was true for 
snmptrapd.conf.
with agentaddress only beeing localhost you can not query esos from remote 
station.

Original comment by mahir.ya...@gmail.com on 2 Mar 2014 at 2:41

GoogleCodeExporter commented 9 years ago 
These global options should be set
engineIDType 3
dontLogTCPWrappersConnects yes

Works in v1 and v2 with public and in v3 if you CreateUser authUserOnly with 
password.

Original comment by mahir.ya...@gmail.com on 2 Mar 2014 at 3:12

GoogleCodeExporter commented 9 years ago 
I added these those last 2 options to the bottom of the default snmpd.conf file:
engineIDType 3
dontLogTCPWrappersConnects yes

As for the localhost address, we'll let the users customize the file and decide 
what interface(s) they'd like to bind to. =)

I'll keep this issue open for another day or two, and if there are no changes 
after that, I'll close it.

--Marc

Original comment by msmith...@gmail.com on 2 Mar 2014 at 4:28

GoogleCodeExporter commented 9 years ago 
snmpd crashes with
error on subcontainer 'dr_addr' insert (-1)
while snmpwalk to esos.

v1 v2 or v3 does not matter, about the first 500 items are displayed then there 
is a timeout and snmpd chrashes.

you have to kill the task with killall.

Original comment by mahir.ya...@gmail.com on 2 Mar 2014 at 6:00

GoogleCodeExporter commented 9 years ago 
You'd have to check with the net-snmp project -- when I added this package, it 
was the latest stable release available on their web site. I did quick Google 
search on that error and some users seem to indicate its just being verbose, 
and not really a problem:
http://www.novell.com/support/kb/doc.php?id=7005030

If you find out is for sure a problem, and when its fixed upstream, let me know 
and I'll do a version bump in ESOS. If you find its some configuration issue, 
let me know and I can change the default net-snmp configuration file.

--Marc

Original comment by msmith...@gmail.com on 2 Mar 2014 at 8:17

GoogleCodeExporter commented 9 years ago 
net-snmp-5.7.2.1 is the latest

Original comment by mahir.ya...@gmail.com on 2 Mar 2014 at 8:18

GoogleCodeExporter commented 9 years ago 
Of course most of the errors you can hide witf -LS0-6d -Lf /dev/null.
But here snmpd freezes or crahes.
You can verify this behaviour with
view   systemonly  included   .1
in snmpd.conf.
do "snmpwalk -v1 localhost" on esos. 
This will result in a timeout and snmpd stops working.

This behaviour is true for v1, v2 or v3.

Original comment by mahir.ya...@gmail.com on 2 Mar 2014 at 8:40

GoogleCodeExporter commented 9 years ago 
Okay, has this already been reported upstream for the net-snmp project, or is 
this something that was fixed in 5.7.2.1 (we're on 5.7.2)?

--Marc

Original comment by msmith...@gmail.com on 2 Mar 2014 at 8:53

GoogleCodeExporter commented 9 years ago 
Hi Marc, in the CHANGELOGS for 5.7.2.1 is only this mentioned:
* 5.7.2.1 *
    snmpd:
      - SECURITY: a denial of service attack vector was discovered on
        the linux implementation of the ICMP-MIB.  This release fixes
        this bug and all users are encouraged to update their SNMP
        agent if they make use of the ICMP-MIB table objects.

so i believe you have forget something to compile or maybe some libs are 
missing, had no time tó find it out.

for snmptrapd.conf some confgi parms are not working, eg logfile and 
printeventnumbers.

I had used 5.5. before without problems.

Original comment by mahir.ya...@gmail.com on 2 Mar 2014 at 11:21

GoogleCodeExporter commented 9 years ago 
Okay, and that could be the case, but I'll keep this issue open for now until 
we have it resolved.

--Marc

Original comment by msmith...@gmail.com on 3 Mar 2014 at 2:38

GoogleCodeExporter commented 9 years ago 
I think 5.7.2 is affected with the security issue because
these are the last lines while doing snmpwalk to esos

495: icmpOutTimestamps.0 14
496: icmpOutTimestampReps.0 0
497: icmpOutAddrMasks.0 0
498: icmpOutAddrMaskReps.0 0
499: icmpStatsInMsgs.1 30
500: icmpStatsInMsgs.2 0
501: icmpStatsInErrors.1 0
502: icmpStatsInErrors.2 0
503: icmpStatsOutMsgs.1 0
504: icmpStatsOutMsgs.2 0
505: icmpStatsOutErrors.1 30
506: icmpStatsOutErrors.2 0
507: icmpMsgStatsInPkts.1.0 14
508: icmpMsgStatsInPkts.1.3 2
509: icmpMsgStatsInPkts.1.8 14
510: icmpMsgStatsOutPkts.1.0 14
511: icmpMsgStatsOutPkts.1.3 2
512: icmpMsgStatsOutPkts.1.8 14
513: tcpRtoAlgorithm.0 other(1)
514: tcpRtoMin.0 200
515: tcpRtoMax.0 120000
516: tcpMaxConn.0 -1
517: tcpActiveOpens.0 17
518: tcpPassiveOpens.0 3
519: tcpAttemptFails.0 15
520: tcpEstabResets.0 0
Timeout

Original comment by mahir.ya...@gmail.com on 3 Mar 2014 at 1:58

GoogleCodeExporter commented 9 years ago 
can you inclide lm_sensors to esos?
this would make ucd-mib/lmSensors usable.

Original comment by mahir.ya...@gmail.com on 3 Mar 2014 at 7:53

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
for net-snmp 5.7.2.1 please include these for make

--enable-minimalist
--disable-deprecated
--with-mib-modules="ucd-snmp/diskio etherlike-mib"
--disable-manuals     
--disable-scripts

Original comment by mahir.ya...@gmail.com on 4 Mar 2014 at 1:18

GoogleCodeExporter commented 9 years ago 
Okay, I'll commit with those changes tomorrow. You think lm_sensors is really 
necessary ? Besides adding the package itself, it looks as though there are a 
number of kernel drivers that are needed too. Does it also need the sensord 
daemon to be running? Seems like a lot of bloat to get some temperature 
readings. =)

Original comment by msmith...@gmail.com on 4 Mar 2014 at 2:24

GoogleCodeExporter commented 9 years ago 
if you include freeipmi instead of ipmitoll i can test if the results for query 
hardware data is statisfied. I have not find a way yet how the data pulled from 
ipmi will get into net-snmp.

if this is true there is no need for lm_sensors, but for SNMP 
ucd-snmp/lmSensors (needs lm_sensors and this needs rrdttol if you want to use 
sensorsd as daemon) writes direkt to the table so you can monitor the events.

lm_senors need i2c_chardev =y in kernel, and of course possible modules for 
newer hardware.

Original comment by mahir.ya...@gmail.com on 4 Mar 2014 at 3:05

GoogleCodeExporter commented 9 years ago 
Yeah, it seems like lm_sensors is for desktop-type computers -- servers should 
all have IPMI BMC's. Also, what sensor data would we export via SNMP? I'm 
trying to understand how/why someone might use this with ESOS.

Original comment by msmith...@gmail.com on 4 Mar 2014 at 3:11

GoogleCodeExporter commented 9 years ago 
the goal is always the same, get as much data from your esos with snmpget as 
possible - temps, fans, voltage, disks and so on.

lm_sensors is not only for desktops since there are modules for fujitsu Siemens 
hermes Chipsets or Intel temp_drivers and so on.
ucd-snmp/lmSensors would provide zhis data to snmpd directly (using sensorsd) i 
believe. (so you have Fans and Voltages)

nut snmpagent would do the same with the all the powerdata. NUT will get data 
local on serial or usb or queried from network with snmp and would work as 
proxy to snmpd.
i have not tested yet but nut uses freeipmi in addition to query voltage data 
(and maybe the State of the powersupllies in the machine)

But the most enterprise Way would be with ipmi only but this is only possible 
if you install the vendor specific snmpagent(DELL/FUJITSU eg).
if you use not the vendor tools you will miss data. 
e.g. it was reported that query the disks with freeipmi or ipmitools you will 
get a wrong state reported. for testing you pull out a drive but ipmi report 
drive ok)

Please decide what way to go.
Leave all essential and make use of vendor specific tools or not?

--enable-minimalist
--disable-deprecated
--with-mib-modules="ucd-snmp/diskio etherlike-mib"
--disable-manuals     
--disable-scripts

Original comment by mahir.ya...@gmail.com on 4 Mar 2014 at 7:03

GoogleCodeExporter commented 9 years ago 
i had compiled net-snmp-5.7.2 with this addes in the makefile

--enable-minimalist
--disable-deprecated
--with-mib-modules="ucd-snmp/diskio etherlike-mib"
--disable-manuals     
--disable-scripts 

but there failure is still there. snmpwalk crashes snmpd after querying 520 
entries.

Original comment by mahir.ya...@gmail.com on 4 Mar 2014 at 7:04

GoogleCodeExporter commented 9 years ago 
For comment # 26, I'm still waffling on this -- I get some users might use SNMP 
to get some informational/performance data from their ESOS system, but to what 
extent? What are they going to do with this data?

I think I'm going to draw the line for SNMP (for now at least) with not adding 
any more dependencies. I feel like we're not being generic enough and adding 
this is really only for a small subset of users, while adding bloat to ESOS. It 
should be thin and light (as much as can be).

If there is more pressure for this feature with net-snmp in the future, then we 
can look at adding it in then.

For comment # 27, I haven't committed with the 5.7.2.1 version yet. So we'll 
see if that fixes the issue, and if not, you'll need to check up-stream with 
the net-snmp project and see if its a bug, or some type of configuration issue. 
The binary is not producing a segmentation fault?

Original comment by msmith...@gmail.com on 4 Mar 2014 at 7:16

GoogleCodeExporter commented 9 years ago 
ok so then we make just snmp working. for the real world everybody should use 
the vendor sepcific tools to get the most available monitoring of the machine.

You are right with esos should stay thin and light, maybe nuts is also 
oversized then. and if someone want to have UPS Monitoring he could install the 
vendor agents.
you coul minimize nuts to only monitor the local attached USV (seriell(USB) for 
doing a clean shutdown since this was the first intention to have a secure 
shutdown if power fails.

doing generic monitoring with freeipmi and small tools will be very difficult.

Original comment by mahir.ya...@gmail.com on 4 Mar 2014 at 7:29

GoogleCodeExporter commented 9 years ago 
-- I get some users might use SNMP to get some informational/performance data 
from their ESOS system, but to what extent? What are they going to do with this 
data?

I want to ask clearer maybe i have missunderstood this. Do you think a working 
snmpagent is a must have for an OS that is called Enterprise Storage Operation 
System?

with the io data you could get an idea where you bottleneck is.
if you have data for network and data for diskio you will find quickly what is 
the bottlenck. almost the same reason why you have the perfagent in esos(this 
is not really needed)

Original comment by mahir.ya...@gmail.com on 4 Mar 2014 at 7:53

GoogleCodeExporter commented 9 years ago 
Oh, don't get me wrong, I think SNMP definitely belongs here, but I'm only 
interested in supporting what you said: statistics and performance data, and 
maybe some basic system information. What I don't think is applicable right now 
is finding out the RPMs of brand X fan, or temperature sensors, etc. And I'm 
not saying this won't ever be in there,  I just want to let the SNMP software 
meld in ESOS for now and discover how people would use and what additional 
options need to be set for it.

Original comment by msmith...@gmail.com on 4 Mar 2014 at 7:58

GoogleCodeExporter commented 9 years ago 
ok sorry for this. let see what is in future with this.

can you please change ipmitool with freeipmi? it has more options

and for net-snmp please leave emmbedded perl enabled, so it can be used to 
parse same information.

Original comment by mahir.ya...@gmail.com on 4 Mar 2014 at 8:13

GoogleCodeExporter commented 9 years ago 
No problem, its good to have conversations about this. Its very easy to add 
software, but very, very difficult to remove it ever later on. =)

As for freeipmi, I'll work on that tonight. And ipmitool is used by 
fence-agents, so unless freeipmi can be used as an alternative for that 
package, ipmitool will have to stay.

I'll make those changes tonight and commit.

Original comment by msmith...@gmail.com on 4 Mar 2014 at 8:29

GoogleCodeExporter commented 9 years ago 
yeap, dependencies are a real problem.

Original comment by mahir.ya...@gmail.com on 4 Mar 2014 at 9:39

GoogleCodeExporter commented 9 years ago 
i have tried to install DELL OMSA to ESOS.
This is a hard work. I got it running with all data from Dell MIB 10892 but 
there is no data for power and temp because IPMI is broken. The device Nodes 
are missing /dev/ipmi0 /dev/impi/0. 

Dell maybe needs openipmi, so maybe all version must be in esos to support 
various vendors.

Original comment by mahir.ya...@gmail.com on 5 Mar 2014 at 1:29

GoogleCodeExporter commented 9 years ago 
I'm working on adding the freeipmi package. This is a dependency for the 
net-snmp package? I don't see any 'ipmi' related configure options. Or are we 
getting mixed up here and freeipmi is needed for NUT?

Original comment by msmith...@gmail.com on 5 Mar 2014 at 3:11

GoogleCodeExporter commented 9 years ago 
its the second on. nut can utilize freeipmi

Original comment by mahir.ya...@gmail.com on 5 Mar 2014 at 3:12

GoogleCodeExporter commented 9 years ago 
Got it.

Can this SNMP issue/request be closed? =)

Original comment by msmith...@gmail.com on 5 Mar 2014 at 3:14

GoogleCodeExporter commented 9 years ago 
please wait till i an verify that snmpd is not crashing anymopre while walking 
through all the MIBs. i wait for 5.7.2.1 ebbeded perl should be enabled please

Original comment by mahir.ya...@gmail.com on 5 Mar 2014 at 3:15

GoogleCodeExporter commented 9 years ago 
there is a compile error on latest esos 585/586 with netsnmp-5.7.2.1 (this was 
build from new trunk)

././libs/libnetsnmpmibs.so: undefined reference to 
'netsnmp_container_table_row_insert' and many other undefined references to 
'netsnmp_.....'

collect2: Id returned 1 exit status
make[2]: *** [snmpd] Error 1
make[1]: *** [subdirs] Error 1
make: *** [net-snmp] Error 2

it has claimed before with the IPv6 components

Original comment by mahir.ya...@gmail.com on 5 Mar 2014 at 11:04

GoogleCodeExporter commented 9 years ago 
This was fixed and committed the other day -- still having problems with 
net-snmp acting up with the latest? Or resolved?

Original comment by msmith...@gmail.com on 9 Mar 2014 at 3:20

GoogleCodeExporter commented 9 years ago 
for compiling this is resolved.

for snmpd gets crashed while do snmpwalk -v1 locahost not. (this is with 
sstemview set to .1)

Original comment by mahir.ya...@gmail.com on 11 Mar 2014 at 11:30

GoogleCodeExporter commented 9 years ago 
Okay -- we'll need to report the issue upstream to the net-snmp project.

Can you provide the exact steps for re-producing the issue? Or is using the 
default configuration file and starting rc.snmpd enough to cause the "crash"?

--Marc

Original comment by msmith...@gmail.com on 14 Mar 2014 at 3:43

GoogleCodeExporter commented 9 years ago 
you use the default snmpd.conf
with 
view    systemview    included   .1
and then do snmpwalk -v1 localhost

Original comment by mahir.ya...@gmail.com on 14 Mar 2014 at 3:04

GoogleCodeExporter commented 9 years ago 
Hi,

In the default /etc/snmp/snmpd.conf file, I commented out the 2 "view 
systemview ..." lines and added this line:
view systemview included .1

I then attempted to use this command: snmpwalk -v1 localhost
With that command I get an error: No community name specified.

So I try it again with this: snmpwalk -v1 localhost -c blah
It hangs for a minute and then says this: Timeout: No Response from localhost

I tried starting snmpd (via /etc/rc.d/rc.snmpd) and I get the same timeout 
error message above.

What am I doing wrong?

--Marc

Original comment by msmith...@gmail.com on 17 Mar 2014 at 7:47

GoogleCodeExporter commented 9 years ago 
my fault: it is snmpwalk -v1 localhost -c public (-c COMMUNITYNAME was missing)

you do nothing wrong here snmpd becames a zombie and you have to kill it with 
kill -9 PID before you can start it again.

if you do ps ax | grep snmpd ewithout to kill the zombie you will have no 
result.

the first time you will do snmpwalk on .1 it will start and then stop with a 
timeout.
the second time you do this without killing and restarting snmpd you will get 
no response beacuse snmpd is already crashed.

This is maybe a divide by zero error which was fixed earlier in net-snmp 5.4.

I will try to compile net-snmp with other options to see if there is any 
difference to the behaviour from now.

Original comment by mahir.ya...@gmail.com on 17 Mar 2014 at 7:56

GoogleCodeExporter commented 9 years ago 
Hi,

I've gotten time to come back to this, and just performed the following steps 
on a recent build (r671):

[root@localhost ~]# /etc/rc.d/rc.snmpd start
Starting snmpd...

[root@localhost ~]# snmpwalk -v1 localhost -c public
SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost 3.14.16-esos.prod #1 SMP Mon 
Aug 11 12:14:52 EDT 2014 x86_64
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2805) 0:00:28.05
SNMPv2-MIB::sysContact.0 = STRING: Me <me@example.org>
SNMPv2-MIB::sysName.0 = STRING: localhost
SNMPv2-MIB::sysLocation.0 = STRING: Sitting on the Dock of the Bay
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORID.1 = OID: SNMP-MPD-MIB::snmpMPDCompliance
SNMPv2-MIB::sysORID.2 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance
SNMPv2-MIB::sysORID.3 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.4 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.5 = OID: TCP-MIB::tcpMIB
SNMPv2-MIB::sysORID.6 = OID: IP-MIB::ip
SNMPv2-MIB::sysORID.7 = OID: UDP-MIB::udpMIB
SNMPv2-MIB::sysORID.8 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
SNMPv2-MIB::sysORID.9 = OID: SNMP-NOTIFICATION-MIB::snmpNotifyFullCompliance
SNMPv2-MIB::sysORID.10 = OID: NOTIFICATION-LOG-MIB::notificationLogMIB
SNMPv2-MIB::sysORDescr.1 = STRING: The MIB for Message Processing and 
Dispatching.
SNMPv2-MIB::sysORDescr.2 = STRING: The management information definitions for 
the SNMP User-based Security Model.
SNMPv2-MIB::sysORDescr.3 = STRING: The SNMP Management Architecture MIB.
SNMPv2-MIB::sysORDescr.4 = STRING: The MIB module for SNMPv2 entities
SNMPv2-MIB::sysORDescr.5 = STRING: The MIB module for managing TCP 
implementations
SNMPv2-MIB::sysORDescr.6 = STRING: The MIB module for managing IP and ICMP 
implementations
SNMPv2-MIB::sysORDescr.7 = STRING: The MIB module for managing UDP 
implementations
SNMPv2-MIB::sysORDescr.8 = STRING: View-based Access Control Model for SNMP.
SNMPv2-MIB::sysORDescr.9 = STRING: The MIB modules for managing SNMP 
Notification, plus filtering.
SNMPv2-MIB::sysORDescr.10 = STRING: The MIB module for logging SNMP 
Notifications.
SNMPv2-MIB::sysORUpTime.1 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.2 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.3 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.4 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.5 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.6 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.7 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.8 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.9 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.10 = Timeticks: (0) 0:00:00.00
HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (38496) 0:06:24.96
HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2014-8-14,14:12:32.0,+0:0
HOST-RESOURCES-MIB::hrSystemInitialLoadDevice.0 = INTEGER: 393216
HOST-RESOURCES-MIB::hrSystemInitialLoadParameters.0 = STRING: 
"BOOT_IMAGE=/bzImage-esos.prod crashkernel=128M console=ttyS0,9600n console=tty0
"
HOST-RESOURCES-MIB::hrSystemNumUsers.0 = Gauge32: 2
HOST-RESOURCES-MIB::hrSystemProcesses.0 = Gauge32: 21
HOST-RESOURCES-MIB::hrSystemMaxProcesses.0 = INTEGER: 0
End of MIB

This appears to work fine, and the snmpd process is still working, so I'm going 
to close this issue. If we discover there is a bug in net-snmp or configuration 
issues, we'll address those in the future.

--Marc

Original comment by msmith...@gmail.com on 14 Aug 2014 at 2:15