Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Linux (Net-SNMP)

Mithrilhall

Does anyone monitor Linux servers?

I can't seem to get my Disk Volumes to show up.

Find more posts tagged with

Accepted answers

All comments

kindbro

I am having the same problem with my monitoring of Suse Linux servers. I have them added to Orion, but when it shows the memory, it shows it at 180% utilization and processor over 100%. The only problem with this is that the linux servers are test boxes and are carring no load. Ive spoke with the engineers at Solarwinds about this and they said to back rev to a net-snmp version 5.09. We did this and got the same results. From what I understand though is that the new version of Orion v8 should fix this problem, but if anyone does have a fix I would love to here about it.

Thanks
Bret

Mithrilhall

Bret, do you see the disks of your Suse servers in Orion or only CPU, Memory and the interfaces?

unlv

We've tried monitoring our linux servers, but after selecting the resources we want to monitor, the snmp service on the linux servers go nuts and get stuck in a busy loop. This happens with ALL of our linux servers. We are running GRSEC kernels so we thought that was why but it sounds like you're having issues also.

Alain

We are monitoring 2 different types of Linux here in both cases with
succes, by that I mean that we can monitor logical volumes, network
interface cards and processors and memory.

Below is an example of a fonctionnal snmpd.conf file from a Linux 2.4.x;
only lines which have been changed are presented:

Local informations and settings:
Used community string : Commustring
NMS server's IP address : 9.9.9.9
Domain name : LocalDomain
======
# sec.name source community
com2sec Commustringsec default Commustring
[...]
# groupName securityModel securityName
group Commustringv1 v1 Commustringsec
group Commustringv2c v2c Commustringsec
[...]
# name incl/excl subtree mask(optional)
view systemview included .1.3.6.1.2.1.1
[...]
# group context sec.model sec.level prefix read write notif
access Commustringv1 "" any noauth exact all none none
## sec.name source community
com2sec LocalDomain 9.9.0.0/16 Commustring
[...]
## incl/excl subtree mask
view all included .1 80
[...]
syslocation Salle_Server_1
syscontact Alain
[...]
trapsink 9.9.9.9 Commustring
======

Hope this may help.
Alain

Mithrilhall

Thanks for the conf file. I'll apply the changes to mine and see how it goes.

BTW...I'm running CentOS 4.3 (Kernel 2.6.9-34.EL --- Asterisk@Home 2.8).

Mithrilhall

Ok...could someone that can monitor their volumes please post their snmpd.conf in full?

I have net-snmp v5.0.9 installed and all I can monitor is CPU, Memory and Interfaces.

According to Solarwinds' support, the reason my volumes are not showing up is because my agent insn't configured properly.

epb3

I'm trying to monitor a Linux server myself and just wondering where the snmp.conf file goes. I'm fairly lost on how to go about this whole monitoring process so any help you could give me would be appreciated.

Mithrilhall

From the command line (as root) do the following:

snmpconf

The above command should get you started. Once your snmpd.conf files has been created you need to move it to the proper location.

Also, go here net-snmp.sourceforge.net/.../snmpd.html and follow the instructions. Pay close attention to the "Location, location, location" section.

I still have had no luck monitoring volumes.

Alain

Hi Mithrilhall;

I'm no expert with netsnmp; but I would look at the following lines in the snmpd.conf file:
view systemview included .1.3.6.1.2.1.1
access Commustring "" any noauth exact all none none

as those ones are the one that give acces to the subtree; so basically
if your disk subsystem is not included in that part of the tree
(that I can't tell wether they are or not included) you won't be able to
snmpGET on those.

You may try to open up the read acces to the subtree; for this I guess
you should load the relevant mibs in a mib browser and determine where
are your disks defined.
Eventually try to set something like:
view systemview included .1

Again note that this is just a guess/suggestion...
Good luck;
Alain

mjhamilton

wow you guys are going nuts over this one.. my snmpd.conf file just had about 4 lines....

location
owner
community string
snmpserver

... i deleted all the other stuff created in the setup script as Orion doesn't require them!!

I will post a copy when I am at work tomorrow.......

Q 4 u all....... have you stopped the built in SNMP agent before running net-snmp??... they can coexist but it is a real *** to reset up the listening ports.. I personally switch the built in stuff of to let net-snmp breath...

Let me know if you have any questions??

Martin J. Hamilton... lost in a sea of snmp...

Rikm1

MJ

Please can you show us a copy of your config
file??

thanks

funemone

# sec.name source community
com2sec notConfigUser 10.2.9.0/24 public

####
# Second, map the security name into a group name:

# groupName securityModel securityName
group notConfigGroup v1 notConfigUser
group notConfigGroup v2c notConfigUser

####
# Third, create a view for us to let the group have rights to:

# Make at least snmpwalk -v 1 localhost -c public system fast again.
# name incl/excl subtree mask(optional)
view systemview included .1
view systemview included .1.3.6.1.2.1.25.1.1
# group context sec.model sec.level prefix read write notif
access notConfigGroup "" any noauth exact systemview all all