Dell SNMP - Windows vs. Linux

Fred Skrotzki fskrotzki at textwise.com
Tue Apr 3 10:21:58 CDT 2007


Yell at your Dell service guy the next time he replaces the Motherboard.
A part of the replacement is to update the bios with the machines
correct service tag.  That is what I was told when we noticed it once.
We've never had a problem since. 

-----Original Message-----
From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Nick Stephens
Sent: Monday, April 02, 2007 5:35 PM
To: TLesniak at lyrix.com; linux-poweredge at lists.us.dell.com
Subject: RE: Dell SNMP - Windows vs. Linux

Good call, the system in question has indeed been serviced!  I will
update that information in the BIOS next time I have a chance to reboot.

Thanks everyone!

Nick

 

-----Original Message-----
From: TLesniak at lyrix.com [mailto:TLesniak at lyrix.com]
Sent: Monday, April 02, 2007 2:27 PM
To: Nick Stephens
Subject: RE: Dell SNMP - Windows vs. Linux

Patrick,

Chances are that the system that responded with a service-tag of "Dell"
has had it's motherboard replaced. I know that i've had a couple of
motherboards replaced and they always have a service tag of "Dell" set
on them.

      - Tom




|---------+-------------------------------->
|         |           "Nick Stephens"      |
|         |           <nick at ceiva.com>     |
|         |           Sent by:             |
|         |           linux-poweredge-bounc|
|         |           es at dell.com          |
|         |                                |
|         |                                |
|         |           04/02/2007 05:15 PM  |
|---------+-------------------------------->
 
>-----------------------------------------------------------------------
----------------------------------------|
  |
|
  |        To:      <Patrick_Boyd at dell.com>,
<linux-poweredge at lists.us.dell.com>                                  |
  |        cc:
|
  |        Subject: RE: Dell SNMP - Windows vs. Linux
|
 
>-----------------------------------------------------------------------
----------------------------------------|




Thank you for the quick response, Patrick.

I checked the RHEL4 machine in question and attempted to restart it, but
I received a few error messages regarding missing libs.  I fiddled with
it for a few minutes adding proper paths to ldconf until I got to a
non-descript error.  Then I simply uninstalled the existing OMSA and
up2date installed the newest.

I started the services up (error free) and got exactly the information I
needed... I can't believe I missed those services failing even as I
pasted to here!

To clarify for those following along at home, you do not need to fiddle
with the MIBS whatsoever (those are only for client side OID -> name
mapping, no effect on what OID's the remote system will respond to).

To verify this I took a machine that I had not mucked with, updated the
OMSA on it to the latest version (5.1), and then properly received the
requested SNMP information... well, with the exception that one of the
RHEL machines decided to respond to my service-tag snmp request with
just "DELL " instead of the actual tag.

One final question: Is it necessary to install the entire OMSA package
on each linux box that we want to enable Dell SNMP Mibs?  I don't
suspect that this would be a problem, except that a few of the machines
run linux distros that are currently "unsupported" by OMSA.

Thank you again, Patrick, you just made my life much happier!

Nick

-----Original Message-----
From: Patrick_Boyd at Dell.com [mailto:Patrick_Boyd at Dell.com]
Sent: Monday, April 02, 2007 12:15 PM
To: Nick Stephens; linux-poweredge at lists.us.dell.com
Subject: RE: Dell SNMP - Windows vs. Linux

dsm_sa_datamgr32d is stopped
dsm_sa_eventmgr32d is stopped
dsm_sa_snmp32d is stopped

These 3 services need to be running to get SNMP

-----Original Message-----
From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Nick Stephens
Sent: Monday, April 02, 2007 1:15 PM
To: linux-poweredge-Lists
Subject: Dell SNMP - Windows vs. Linux

Greetings all,

I am on a newfound mission across my network to get SNMP working
properly on every device in an attempt to use some great management
tools.  I had been relatively lax about SNMP in the past, so I have a
lot of catching up to do ?  One thing that I have found recently is
confusing me a bit, and that is the way that my Windows servers react to
SNMP vs my Linux servers.  Please allow me to cite an example:

PowerEdge server running Windows 2003 with OMSA installed, snmp enabled:

# snmpget -v2c -c xxxxx windows-box
.1.3.6.1.4.1.674.10892.1.300.10.1.11.1
SNMPv2-SMI::enterprises.674.10892.1.300.10.1.11.1 = STRING: "XXX111"


PowerEdge server running RHEL4 with OMSA installed, snmp enabled:

# snmpget -v2c -c xxxxx linux-box .1.3.6.1.4.1.674.10892.1.300.10.1.11.1
SNMPv2-SMI::enterprises.674.10892.1.300.10.1.11.1 = No Such Object
available on this agent at this OID


As you can see, the Windows machine properly responds to my request for
it's service tag information, whereas the linux box is not aware of this
oid?  I have downloaded the dell MIBs (10892.mib) and placed it in
/usr/share/snmp/mibs/, however I _believe_ this has more to do with
being able to call the OID by name instead of number, and not with
responding to a request for information.

I also believe that my problem has something to do with net-SNMP, but
I'm not sure what exactly.  Am I missing something easy, or is this
somehow not available in linux environments?  Below is some more
information regarding the RHEL4 linux box, but please note as well that
I have tried this with the exact same results on a newer CentOS 4.4 box
with OMSA 5.1 installed.

Thank you in advance, I am a bit lost at this point!


[root at linux-box ~]# srvadmin-services.sh status dcdbas (module) is
running dell_rbu (module) is running dsm_sa_datamgr32d is stopped
dsm_sa_eventmgr32d is stopped dsm_sa_snmp32d is stopped dsm_om_shrsvc32d
(pid 7708) is running dsm_om_connsvc32d (pid 7762 7761) is running

[root at linux-box ~]# rpm -qa|grep -i srvad
srvadmin-deng-5.0.0-463
srvadmin-old-5.0.0-463
srvadmin-diagnostics-1-0
srvadmin-ipmi-5.0.0-463.rhel4
srvadmin-base-1-0
srvadmin-omilcore-5.0.0-463
srvadmin-omacore-5.0.0-463
srvadmin-odf-5.0.0-463
srvadmin-storage-5.0.0-463
srvadmin-web-interface-1-0
srvadmin-cm-5.0.0-463
srvadmin-hapi-5.0.0-463
srvadmin-omhip-5.0.0-463
srvadmin-all-1-0
srvadmin-jre-5.0.0-463
srvadmin-iws-5.0.0-463
srvadmin-isvc-5.0.0-463

[root at linux-box ~]# cat /etc/snmp/snmpd.conf

com2sec mynetwork my.ip.add.ress xxxxx
group MyROGroup  v1        mynetwork
group MyROGroup  v2c        mynetwork
view all    included  .1                               80
access MyROGroup ""      any       noauth    prefix      all    none
none
syslocation Burbank
syscontact Nick Stephens
exec getjavaproc /etc/snmp/getjavaproc.sh exec gethttpdproc
/etc/snmp/gethttpdproc.sh exec getresintimewait
/etc/snmp/getresintimewait.sh

# Allow Systems Management Data Engine SNMP to connect to snmpd using
SMUX smuxpeer .1.3.6.1.4.1.674.10892.1

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq



More information about the Linux-PowerEdge mailing list