[Check_mk (english)] Monitoring a Dell Power Edge server with Check_MK

Hi Folks,

I’ve a Dell PowerEdge machine with OMSA installed and with the agents running.

However, when trying to monitor this machine via SNMP, I can’t get those services to work :

$ check_mk -L | grep dell_om

dell_om_disks snmp no yes Physical Disk %s
dell_om_esmlog snmp no yes ESM Log
dell_om_mem snmp no yes Module %s

dell_om_processors snmp no yes Processor %s
dell_om_sensors snmp yes yes Sensor %s

I’ve tried also to force the inventory with :

$cmk -II

But it’s still getting only basic stuff…

I really would appreciate any help here.

check_mk version : 1.2.4p2

Thanks.

guerra.

A few things to obtain more information:

Are any snmp checks being returned?
Are the Dell servers configured for snmp traffic?
Can you test with a sysDescr snmpwalk from your monitoring host and paste output.
Have you added the snmp tag to the server in your mk config?

Can you paste output of;
Cmk -D <host>

···

Sent from my iPhone

On Apr 10, 2014, at 16:26, Renan Guerra Nannetti <renan.nannetti@gmail.com> wrote:

Hi Folks,

I've a Dell PowerEdge machine with OMSA installed and with the agents running.
However, when trying to monitor this machine via SNMP, I can't get those services to work :

$ check_mk -L | grep dell_om

dell_om_disks snmp no yes Physical Disk %s
dell_om_esmlog snmp no yes ESM Log
dell_om_mem snmp no yes Module %s
dell_om_processors snmp no yes Processor %s
dell_om_sensors snmp yes yes Sensor %s

I've tried also to force the inventory with :

$cmk -II <host>

But it's still getting only basic stuff...
I really would appreciate any help here.

check_mk version : 1.2.4p2

Thanks.

guerra.
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.

The Dell servers are configured to do it and are responding to my manual snmpwalk/get commands ( see below ).

Yes. I’ve added the tag to it ( etc/check_mk/main.mk )

all_hosts = [

‘hostname|snmp’
]

I don’t know what I’m missing…

Thanks for you help.

renan.

$ snmpget -v1 -c public sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64

$ cmk -D

()
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:

Contact groups: all
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: no)
Is aggregated: no
Services:
checktype item params description groups summarized to groups


ucd_cpu_load None (5, 10) CPU load

ucd_cpu_util None None CPU utilization
if64 2 {‘state’: [‘1’], ‘errors’: (0.01, 0.10000000000000001), ‘speed’: 1000000000} Interface 2

hr_mem None (150.0, 200.0) Memory used
snmp_info None None SNMP Info

snmp_uptime None {} Uptime
hr_fs / {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

···

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring paulmonitoring@gmail.com wrote:

A few things to obtain more information:

Are any snmp checks being returned?

Are the Dell servers configured for snmp traffic?

Can you test with a sysDescr snmpwalk from your monitoring host and paste output.

Have you added the snmp tag to the server in your mk config?

Can you paste output of;

Cmk -D

Sent from my iPhone

On Apr 10, 2014, at 16:26, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Folks,

I’ve a Dell PowerEdge machine with OMSA installed and with the agents running.

However, when trying to monitor this machine via SNMP, I can’t get those services to work :

$ check_mk -L | grep dell_om

dell_om_disks snmp no yes Physical Disk %s

dell_om_esmlog snmp no yes ESM Log

dell_om_mem snmp no yes Module %s

dell_om_processors snmp no yes Processor %s

dell_om_sensors snmp yes yes Sensor %s

I’ve tried also to force the inventory with :

$cmk -II

But it’s still getting only basic stuff…

I really would appreciate any help here.

check_mk version : 1.2.4p2

Thanks.

guerra.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Renan,

first thing: we don't have any dell servers here!

...but when you look at e.g. ~/share/check_mk/checks/dell_om_disks you
can see the used test (to detect if this check applies) as
"snmp_scan_function". In case of dell_om_disks it says to apply if
SNMP OID .1.3.6.1.4.1.674.10893.1.20.1.0 exists and is not null.

You should check this OID manually. Maybe an additional SNMP agent for
OMSA must be configured/started on the server to get such OIDs
provided...

HTH,
Marcel

···

2014-04-11 12:45 GMT+02:00 Renan Guerra Nannetti <renan.nannetti@gmail.com>:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.
The Dell servers are configured to do it and are responding to my manual
snmpwalk/get commands ( see below ).
Yes. I've added the tag to it ( etc/check_mk/main.mk )

all_hosts = [
'hostname|snmp'
]

I don't know what I'm missing...
Thanks for you help.

renan.

$ snmpget -v1 -c public <host> sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux <host> 2.6.18-194.el5 #1 SMP Tue Mar
16 21:52:39 EDT 2010 x86_64

$ cmk -D <host>

<host> (<ip>)
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:
Contact groups: all
Type of agent: SNMP (community: 'public', bulk walk: yes, port:
default, inline: no)
Is aggregated: no
Services:
  checktype item params
description groups summarized to groups
  ------------ -----------------
---------------------------------------------------------------------------------------------------------------------
-------------------- ------ ------------- ------
  ucd_cpu_load None (5, 10)
CPU load
  ucd_cpu_util None None
CPU utilization
  if64 2 {'state': ['1'], 'errors': (0.01,
0.10000000000000001), 'speed': 1000000000}
Interface 2
  hr_mem None (150.0, 200.0)
Memory used
  snmp_info None None
SNMP Info
  snmp_uptime None {}
Uptime
  hr_fs / {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True}
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True}
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize': 20,
'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize': 20,
'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize': 20,
'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize': 20,
'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring <paulmonitoring@gmail.com> > wrote:

A few things to obtain more information:

Are any snmp checks being returned?
Are the Dell servers configured for snmp traffic?
Can you test with a sysDescr snmpwalk from your monitoring host and paste
output.
Have you added the snmp tag to the server in your mk config?

Can you paste output of;
Cmk -D <host>

Sent from my iPhone

> On Apr 10, 2014, at 16:26, Renan Guerra Nannetti >> > <renan.nannetti@gmail.com> wrote:
>
> Hi Folks,
>
>
> I've a Dell PowerEdge machine with OMSA installed and with the agents
> running.
> However, when trying to monitor this machine via SNMP, I can't get those
> services to work :
>
> $ check_mk -L | grep dell_om
>
> dell_om_disks snmp no yes Physical Disk %s
> dell_om_esmlog snmp no yes ESM Log
> dell_om_mem snmp no yes Module %s
> dell_om_processors snmp no yes Processor %s
> dell_om_sensors snmp yes yes Sensor %s
>
> I've tried also to force the inventory with :
>
> $cmk -II <host>
>
> But it's still getting only basic stuff...
> I really would appreciate any help here.
>
> check_mk version : 1.2.4p2
>
> Thanks.
>
>
> guerra.
> _______________________________________________
> checkmk-en mailing list
> checkmk-en@lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Renan,

You should verify the OMSA software is running. ‘omreport system summary’ should show lots of information on your hardware.

Have you configured your snmpd to pass through the Dell OIDs? On our system we have the following line in /etc/snmp/snmpd.conf:

Allow Systems Management Data Engine SNMP to connect to snmpd using SMUX

(NOTE: For Dell nodes running OM)

smuxpeer .1.3.6.1.4.1.674.10892.1

You should be able to snmpwalk that tree:

snmpget -v1 -c public .1.3.6.1.4.1.674.10892.1

Shawn

···

On Fri, Apr 11, 2014 at 6:45 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.

The Dell servers are configured to do it and are responding to my manual snmpwalk/get commands ( see below ).

Yes. I’ve added the tag to it ( etc/check_mk/main.mk )

all_hosts = [

‘hostname|snmp’
]

I don’t know what I’m missing…

Thanks for you help.

renan.

$ snmpget -v1 -c public sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64

$ cmk -D

()
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:

Contact groups: all
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: no)
Is aggregated: no
Services:
checktype item params description groups summarized to groups


ucd_cpu_load None (5, 10) CPU load

ucd_cpu_util None None CPU utilization
if64 2 {‘state’: [‘1’], ‘errors’: (0.01, 0.10000000000000001), ‘speed’: 1000000000} Interface 2

hr_mem None (150.0, 200.0) Memory used
snmp_info None None SNMP Info

snmp_uptime None {} Uptime
hr_fs / {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring paulmonitoring@gmail.com wrote:

A few things to obtain more information:

Are any snmp checks being returned?

Are the Dell servers configured for snmp traffic?

Can you test with a sysDescr snmpwalk from your monitoring host and paste output.

Have you added the snmp tag to the server in your mk config?

Can you paste output of;

Cmk -D

Sent from my iPhone

On Apr 10, 2014, at 16:26, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Folks,

I’ve a Dell PowerEdge machine with OMSA installed and with the agents running.

However, when trying to monitor this machine via SNMP, I can’t get those services to work :

$ check_mk -L | grep dell_om

dell_om_disks snmp no yes Physical Disk %s

dell_om_esmlog snmp no yes ESM Log

dell_om_mem snmp no yes Module %s

dell_om_processors snmp no yes Processor %s

dell_om_sensors snmp yes yes Sensor %s

I’ve tried also to force the inventory with :

$cmk -II

But it’s still getting only basic stuff…

I really would appreciate any help here.

check_mk version : 1.2.4p2

Thanks.

guerra.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Shawn,

Yes, I did that. I’m currently able get data from dell enterprise tree, from my nagios server:

$ snmpwalk -v2c -c public .1.3.6.1.4.1.674.10892.1.700.20.1

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.2.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.3.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.4.1.1 = INTEGER: 2

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.5.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.6.1.1 = INTEGER: 160
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.7.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.8.1.1 = STRING: “System Board Ambient Temp”

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.10.1.1 = INTEGER: 470
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.11.1.1 = INTEGER: 420
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.12.1.1 = INTEGER: 80
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.13.1.1 = INTEGER: 30

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.15.1.1 = INTEGER: 15

But, the services that are bundled with check_mk are not are note ‘seeing’ that…

I’m trying to run cmk -II with debug to see why the cmk is not inventorying those services.

Thanks a lot for your help. : )

Renan.

···

On Fri, Apr 11, 2014 at 8:30 AM, Shawn McKee smckee@umich.edu wrote:

Hi Renan,

You should verify the OMSA software is running. ‘omreport system summary’ should show lots of information on your hardware.

Have you configured your snmpd to pass through the Dell OIDs? On our system we have the following line in /etc/snmp/snmpd.conf:

Allow Systems Management Data Engine SNMP to connect to snmpd using SMUX

(NOTE: For Dell nodes running OM)

smuxpeer .1.3.6.1.4.1.674.10892.1

You should be able to snmpwalk that tree:

snmpget -v1 -c public .1.3.6.1.4.1.674.10892.1

Shawn

On Fri, Apr 11, 2014 at 6:45 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.

The Dell servers are configured to do it and are responding to my manual snmpwalk/get commands ( see below ).

Yes. I’ve added the tag to it ( etc/check_mk/main.mk )

all_hosts = [

‘hostname|snmp’
]

I don’t know what I’m missing…

Thanks for you help.

renan.

$ snmpget -v1 -c public sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64

$ cmk -D

()
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:

Contact groups: all
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: no)
Is aggregated: no
Services:
checktype item params description groups summarized to groups


ucd_cpu_load None (5, 10) CPU load

ucd_cpu_util None None CPU utilization
if64 2 {‘state’: [‘1’], ‘errors’: (0.01, 0.10000000000000001), ‘speed’: 1000000000} Interface 2

hr_mem None (150.0, 200.0) Memory used
snmp_info None None SNMP Info

snmp_uptime None {} Uptime
hr_fs / {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring paulmonitoring@gmail.com wrote:

A few things to obtain more information:

Are any snmp checks being returned?

Are the Dell servers configured for snmp traffic?

Can you test with a sysDescr snmpwalk from your monitoring host and paste output.

Have you added the snmp tag to the server in your mk config?

Can you paste output of;

Cmk -D

Sent from my iPhone

On Apr 10, 2014, at 16:26, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Folks,

I’ve a Dell PowerEdge machine with OMSA installed and with the agents running.

However, when trying to monitor this machine via SNMP, I can’t get those services to work :

$ check_mk -L | grep dell_om

dell_om_disks snmp no yes Physical Disk %s

dell_om_esmlog snmp no yes ESM Log

dell_om_mem snmp no yes Module %s

dell_om_processors snmp no yes Processor %s

dell_om_sensors snmp yes yes Sensor %s

I’ve tried also to force the inventory with :

$cmk -II

But it’s still getting only basic stuff…

I really would appreciate any help here.

check_mk version : 1.2.4p2

Thanks.

guerra.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Renan,

did you check the OID as requested? Just checked and all dell_om_*
checks have this OID as snmp_scan_function.

Regards,
Marcel

···

2014-04-11 13:21 GMT+02:00 Marcel Schulte <schulte.marcel@gmail.com>:

Hi Renan,

first thing: we don't have any dell servers here!

...but when you look at e.g. ~/share/check_mk/checks/dell_om_disks you
can see the used test (to detect if this check applies) as
"snmp_scan_function". In case of dell_om_disks it says to apply if
SNMP OID .1.3.6.1.4.1.674.10893.1.20.1.0 exists and is not null.

You should check this OID manually. Maybe an additional SNMP agent for
OMSA must be configured/started on the server to get such OIDs
provided...

HTH,
Marcel

2014-04-11 12:45 GMT+02:00 Renan Guerra Nannetti <renan.nannetti@gmail.com>:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.
The Dell servers are configured to do it and are responding to my manual
snmpwalk/get commands ( see below ).
Yes. I've added the tag to it ( etc/check_mk/main.mk )

all_hosts = [
'hostname|snmp'
]

I don't know what I'm missing...
Thanks for you help.

renan.

$ snmpget -v1 -c public <host> sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux <host> 2.6.18-194.el5 #1 SMP Tue Mar
16 21:52:39 EDT 2010 x86_64

$ cmk -D <host>

<host> (<ip>)
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:
Contact groups: all
Type of agent: SNMP (community: 'public', bulk walk: yes, port:
default, inline: no)
Is aggregated: no
Services:
  checktype item params
description groups summarized to groups
  ------------ -----------------
---------------------------------------------------------------------------------------------------------------------
-------------------- ------ ------------- ------
  ucd_cpu_load None (5, 10)
CPU load
  ucd_cpu_util None None
CPU utilization
  if64 2 {'state': ['1'], 'errors': (0.01,
0.10000000000000001), 'speed': 1000000000}
Interface 2
  hr_mem None (150.0, 200.0)
Memory used
  snmp_info None None
SNMP Info
  snmp_uptime None {}
Uptime
  hr_fs / {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True}
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True}
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize': 20,
'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize': 20,
'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize': 20,
'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize': 20,
'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring <paulmonitoring@gmail.com> >> wrote:

A few things to obtain more information:

Are any snmp checks being returned?
Are the Dell servers configured for snmp traffic?
Can you test with a sysDescr snmpwalk from your monitoring host and paste
output.
Have you added the snmp tag to the server in your mk config?

Can you paste output of;
Cmk -D <host>

Sent from my iPhone

> On Apr 10, 2014, at 16:26, Renan Guerra Nannetti >>> > <renan.nannetti@gmail.com> wrote:
>
> Hi Folks,
>
>
> I've a Dell PowerEdge machine with OMSA installed and with the agents
> running.
> However, when trying to monitor this machine via SNMP, I can't get those
> services to work :
>
> $ check_mk -L | grep dell_om
>
> dell_om_disks snmp no yes Physical Disk %s
> dell_om_esmlog snmp no yes ESM Log
> dell_om_mem snmp no yes Module %s
> dell_om_processors snmp no yes Processor %s
> dell_om_sensors snmp yes yes Sensor %s
>
> I've tried also to force the inventory with :
>
> $cmk -II <host>
>
> But it's still getting only basic stuff...
> I really would appreciate any help here.
>
> check_mk version : 1.2.4p2
>
> Thanks.
>
>
> guerra.
> _______________________________________________
> checkmk-en mailing list
> checkmk-en@lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Paul, Shawn, Folks,

I think I figured out what was the issue.

Inside the dell modules provide with check_mk, before adding this service to the host, it verifies if the OMSA is present.

For this, it checks for the OID .1.3.6.1.4.1.674.10893.1.20.1.0, which I verified that do not exist ( at least on my instance ) and hence the service is not added.

I’ve replaced this check OID for another one from dell tree : .1.3.6.1.4.1.674.10892.1.2000.10.1.6.1.1, and now the service got added.

Best regards,

Renan.

···

On Fri, Apr 11, 2014 at 8:46 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Shawn,

Yes, I did that. I’m currently able get data from dell enterprise tree, from my nagios server:

$ snmpwalk -v2c -c public .1.3.6.1.4.1.674.10892.1.700.20.1

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.2.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.3.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.4.1.1 = INTEGER: 2

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.5.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.6.1.1 = INTEGER: 160
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.7.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.8.1.1 = STRING: “System Board Ambient Temp”

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.10.1.1 = INTEGER: 470
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.11.1.1 = INTEGER: 420
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.12.1.1 = INTEGER: 80
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.13.1.1 = INTEGER: 30

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.15.1.1 = INTEGER: 15

But, the services that are bundled with check_mk are not are note ‘seeing’ that…

I’m trying to run cmk -II with debug to see why the cmk is not inventorying those services.

Thanks a lot for your help. : )

Renan.

On Fri, Apr 11, 2014 at 8:30 AM, Shawn McKee smckee@umich.edu wrote:

Hi Renan,

You should verify the OMSA software is running. ‘omreport system summary’ should show lots of information on your hardware.

Have you configured your snmpd to pass through the Dell OIDs? On our system we have the following line in /etc/snmp/snmpd.conf:

Allow Systems Management Data Engine SNMP to connect to snmpd using SMUX

(NOTE: For Dell nodes running OM)

smuxpeer .1.3.6.1.4.1.674.10892.1

You should be able to snmpwalk that tree:

snmpget -v1 -c public .1.3.6.1.4.1.674.10892.1

Shawn

On Fri, Apr 11, 2014 at 6:45 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.

The Dell servers are configured to do it and are responding to my manual snmpwalk/get commands ( see below ).

Yes. I’ve added the tag to it ( etc/check_mk/main.mk )

all_hosts = [

‘hostname|snmp’
]

I don’t know what I’m missing…

Thanks for you help.

renan.

$ snmpget -v1 -c public sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64

$ cmk -D

()
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:

Contact groups: all
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: no)
Is aggregated: no
Services:
checktype item params description groups summarized to groups


ucd_cpu_load None (5, 10) CPU load

ucd_cpu_util None None CPU utilization
if64 2 {‘state’: [‘1’], ‘errors’: (0.01, 0.10000000000000001), ‘speed’: 1000000000} Interface 2

hr_mem None (150.0, 200.0) Memory used
snmp_info None None SNMP Info

snmp_uptime None {} Uptime
hr_fs / {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring paulmonitoring@gmail.com wrote:

A few things to obtain more information:

Are any snmp checks being returned?

Are the Dell servers configured for snmp traffic?

Can you test with a sysDescr snmpwalk from your monitoring host and paste output.

Have you added the snmp tag to the server in your mk config?

Can you paste output of;

Cmk -D

Sent from my iPhone

On Apr 10, 2014, at 16:26, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Folks,

I’ve a Dell PowerEdge machine with OMSA installed and with the agents running.

However, when trying to monitor this machine via SNMP, I can’t get those services to work :

$ check_mk -L | grep dell_om

dell_om_disks snmp no yes Physical Disk %s

dell_om_esmlog snmp no yes ESM Log

dell_om_mem snmp no yes Module %s

dell_om_processors snmp no yes Processor %s

dell_om_sensors snmp yes yes Sensor %s

I’ve tried also to force the inventory with :

$cmk -II

But it’s still getting only basic stuff…

I really would appreciate any help here.

check_mk version : 1.2.4p2

Thanks.

guerra.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Marcel,

Just got your mail now, from the digest.

Yes! :slight_smile: That’s exactly what I did.

Just need now to setup the the server to receive snmp traps…

Many thanks.

Mfg,

Renan.

···

On Fri, Apr 11, 2014 at 9:12 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Paul, Shawn, Folks,

I think I figured out what was the issue.

Inside the dell modules provide with check_mk, before adding this service to the host, it verifies if the OMSA is present.

For this, it checks for the OID .1.3.6.1.4.1.674.10893.1.20.1.0, which I verified that do not exist ( at least on my instance ) and hence the service is not added.

I’ve replaced this check OID for another one from dell tree : .1.3.6.1.4.1.674.10892.1.2000.10.1.6.1.1, and now the service got added.

Best regards,

Renan.

On Fri, Apr 11, 2014 at 8:46 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Shawn,

Yes, I did that. I’m currently able get data from dell enterprise tree, from my nagios server:

$ snmpwalk -v2c -c public .1.3.6.1.4.1.674.10892.1.700.20.1

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.2.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.3.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.4.1.1 = INTEGER: 2

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.5.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.6.1.1 = INTEGER: 160
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.7.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.8.1.1 = STRING: “System Board Ambient Temp”

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.10.1.1 = INTEGER: 470
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.11.1.1 = INTEGER: 420
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.12.1.1 = INTEGER: 80
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.13.1.1 = INTEGER: 30

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.15.1.1 = INTEGER: 15

But, the services that are bundled with check_mk are not are note ‘seeing’ that…

I’m trying to run cmk -II with debug to see why the cmk is not inventorying those services.

Thanks a lot for your help. : )

Renan.

On Fri, Apr 11, 2014 at 8:30 AM, Shawn McKee smckee@umich.edu wrote:

Hi Renan,

You should verify the OMSA software is running. ‘omreport system summary’ should show lots of information on your hardware.

Have you configured your snmpd to pass through the Dell OIDs? On our system we have the following line in /etc/snmp/snmpd.conf:

Allow Systems Management Data Engine SNMP to connect to snmpd using SMUX

(NOTE: For Dell nodes running OM)

smuxpeer .1.3.6.1.4.1.674.10892.1

You should be able to snmpwalk that tree:

snmpget -v1 -c public .1.3.6.1.4.1.674.10892.1

Shawn

On Fri, Apr 11, 2014 at 6:45 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.

The Dell servers are configured to do it and are responding to my manual snmpwalk/get commands ( see below ).

Yes. I’ve added the tag to it ( etc/check_mk/main.mk )

all_hosts = [

‘hostname|snmp’
]

I don’t know what I’m missing…

Thanks for you help.

renan.

$ snmpget -v1 -c public sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64

$ cmk -D

()
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:

Contact groups: all
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: no)
Is aggregated: no
Services:
checktype item params description groups summarized to groups


ucd_cpu_load None (5, 10) CPU load

ucd_cpu_util None None CPU utilization
if64 2 {‘state’: [‘1’], ‘errors’: (0.01, 0.10000000000000001), ‘speed’: 1000000000} Interface 2

hr_mem None (150.0, 200.0) Memory used
snmp_info None None SNMP Info

snmp_uptime None {} Uptime
hr_fs / {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring paulmonitoring@gmail.com wrote:

A few things to obtain more information:

Are any snmp checks being returned?

Are the Dell servers configured for snmp traffic?

Can you test with a sysDescr snmpwalk from your monitoring host and paste output.

Have you added the snmp tag to the server in your mk config?

Can you paste output of;

Cmk -D

Sent from my iPhone

On Apr 10, 2014, at 16:26, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Folks,

I’ve a Dell PowerEdge machine with OMSA installed and with the agents running.

However, when trying to monitor this machine via SNMP, I can’t get those services to work :

$ check_mk -L | grep dell_om

dell_om_disks snmp no yes Physical Disk %s

dell_om_esmlog snmp no yes ESM Log

dell_om_mem snmp no yes Module %s

dell_om_processors snmp no yes Processor %s

dell_om_sensors snmp yes yes Sensor %s

I’ve tried also to force the inventory with :

$cmk -II

But it’s still getting only basic stuff…

I really would appreciate any help here.

check_mk version : 1.2.4p2

Thanks.

guerra.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Renan,

seems as if you need another config or software running.

According to http://en.community.dell.com/dell-groups/dell-management-console/f/3731/t/19326804.aspx
and/or http://en.community.dell.com/dell-groups/dell-management-console/f/3731/t/19283067.aspx
OID tree .1.3.6.1.4.1.674.10892 seems to apply to OMSA and OID tree
.1.3.6.1.4.1.674.10893 applies to OMSS.

If your OMSS is configured and running correctly your system should
provide info in the second tree, too.

What about changing the check's OID from
.1.3.6.1.4.1.674.10893.1.20.1.0 (check for OMSA version) to
.1.3.6.1.4.1.674.10892.1.100.2.0 (check for OMSA version)? Maybe the
checks should be tweaked this way

Regards,
Marcel

···

2014-04-11 14:25 GMT+02:00 Renan Guerra Nannetti <renan.nannetti@gmail.com>:

Hi Marcel,

Just got your mail now, from the digest.
Yes! :slight_smile: That's exactly what I did.
Just need now to setup the the server to receive snmp traps...

Many thanks.

Mfg,

Renan.

-------------------

Hi Renan,

did you check the OID as requested? Just checked and all dell_om_*
checks have this OID as snmp_scan_function.

Regards,
Marcel

2014-04-11 13:21 GMT+02:00 Marcel Schulte <schulte.marcel@gmail.com>:

Hi Renan,

first thing: we don't have any dell servers here!

...but when you look at e.g. ~/share/check_mk/checks/dell_

om_disks you

can see the used test (to detect if this check applies) as
"snmp_scan_function". In case of dell_om_disks it says to apply if
SNMP OID .1.3.6.1.4.1.674.10893.1.20.1.0 exists and is not null.

You should check this OID manually. Maybe an additional SNMP agent for
OMSA must be configured/started on the server to get such OIDs
provided...

HTH,
Marcel

On Fri, Apr 11, 2014 at 9:12 AM, Renan Guerra Nannetti > <renan.nannetti@gmail.com> wrote:

Paul, Shawn, Folks,

I think I figured out what was the issue.
Inside the dell modules provide with check_mk, before adding this service
to the host, it verifies if the OMSA is present.
For this, it checks for the OID .1.3.6.1.4.1.674.10893.1.20.1.0, which I
verified that do not exist ( at least on my instance ) and hence the service
is not added.
I've replaced this check OID for another one from dell tree :
.1.3.6.1.4.1.674.10892.1.2000.10.1.6.1.1, and now the service got added.

Best regards,

Renan.

On Fri, Apr 11, 2014 at 8:46 AM, Renan Guerra Nannetti >> <renan.nannetti@gmail.com> wrote:

Hi Shawn,

Yes, I did that. I'm currently able get data from dell enterprise tree,
from my nagios server:

$ snmpwalk -v2c -c public <host> .1.3.6.1.4.1.674.10892.1.700.20.1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.2.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.3.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.4.1.1 = INTEGER: 2
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.5.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.6.1.1 = INTEGER: 160
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.7.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.8.1.1 = STRING: "System
Board Ambient Temp"
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.10.1.1 = INTEGER: 470
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.11.1.1 = INTEGER: 420
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.12.1.1 = INTEGER: 80
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.13.1.1 = INTEGER: 30
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.15.1.1 = INTEGER: 15

But, the services that are bundled with check_mk are not are note
'seeing' that...
I'm trying to run cmk -II with debug to see why the cmk is not
inventorying those services.

Thanks a lot for your help. : )

Renan.

On Fri, Apr 11, 2014 at 8:30 AM, Shawn McKee <smckee@umich.edu> wrote:

Hi Renan,

You should verify the OMSA software is running. 'omreport system
summary' should show lots of information on your hardware.

Have you configured your snmpd to pass through the Dell OIDs? On
our system we have the following line in /etc/snmp/snmpd.conf:

# Allow Systems Management Data Engine SNMP to connect to snmpd using
SMUX
# (NOTE: For Dell nodes running OM)
smuxpeer .1.3.6.1.4.1.674.10892.1

You should be able to snmpwalk that tree:

snmpget -v1 -c public <host> .1.3.6.1.4.1.674.10892.1

Shawn

On Fri, Apr 11, 2014 at 6:45 AM, Renan Guerra Nannetti >>>> <renan.nannetti@gmail.com> wrote:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.
The Dell servers are configured to do it and are responding to my
manual snmpwalk/get commands ( see below ).
Yes. I've added the tag to it ( etc/check_mk/main.mk )

all_hosts = [
'hostname|snmp'
]

I don't know what I'm missing...
Thanks for you help.

renan.

$ snmpget -v1 -c public <host> sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux <host> 2.6.18-194.el5 #1 SMP Tue
Mar 16 21:52:39 EDT 2010 x86_64

$ cmk -D <host>

<host> (<ip>)
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:
Contact groups: all
Type of agent: SNMP (community: 'public', bulk walk: yes,
port: default, inline: no)
Is aggregated: no
Services:
  checktype item params
description groups summarized to groups
  ------------ -----------------
---------------------------------------------------------------------------------------------------------------------
-------------------- ------ ------------- ------
  ucd_cpu_load None (5, 10)
CPU load
  ucd_cpu_util None None
CPU utilization
  if64 2 {'state': ['1'], 'errors': (0.01,
0.10000000000000001), 'speed': 1000000000}
Interface 2
  hr_mem None (150.0, 200.0)
Memory used
  snmp_info None None
SNMP Info
  snmp_uptime None {}
Uptime
  hr_fs / {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True}
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True}
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata': True}
<path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring >>>>> <paulmonitoring@gmail.com> wrote:

A few things to obtain more information:

Are any snmp checks being returned?
Are the Dell servers configured for snmp traffic?
Can you test with a sysDescr snmpwalk from your monitoring host and
paste output.
Have you added the snmp tag to the server in your mk config?

Can you paste output of;
Cmk -D <host>

Sent from my iPhone

> On Apr 10, 2014, at 16:26, Renan Guerra Nannetti >>>>>> > <renan.nannetti@gmail.com> wrote:
>
> Hi Folks,
>
>
> I've a Dell PowerEdge machine with OMSA installed and with the
> agents running.
> However, when trying to monitor this machine via SNMP, I can't get
> those services to work :
>
> $ check_mk -L | grep dell_om
>
> dell_om_disks snmp no yes Physical Disk
> %s
> dell_om_esmlog snmp no yes ESM Log
> dell_om_mem snmp no yes Module %s
> dell_om_processors snmp no yes Processor %s
> dell_om_sensors snmp yes yes Sensor %s
>
> I've tried also to force the inventory with :
>
> $cmk -II <host>
>
> But it's still getting only basic stuff...
> I really would appreciate any help here.
>
> check_mk version : 1.2.4p2
>
> Thanks.
>
>
> guerra.
> _______________________________________________
> checkmk-en mailing list
> checkmk-en@lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Trond Amunsen's check_openmanage nagios plugin (http://folk.uio.no/trondham/software/check_openmanage.html) detects OpenManage using the following perl code:

···

#
# Checking if SNMP works by probing for "chassisModelName", which all
# servers should have
#
sub snmp_check {
    my $chassisModelName = '1.3.6.1.4.1.674.10892.1.300.10.1.9.1';
    my $result = $snmp_session->get_request(-varbindlist => [$chassisModelName]);

    # Typically if remote host isn't responding
    if (!defined $result) {
        printf "SNMP CRITICAL: %s\n", $snmp_session->error;
        exit $E_CRITICAL;
    }

    # If OpenManage isn't installed or is not working
    if ($result->{$chassisModelName} =~ m{\A noSuch (Instance|Object) \z}xms) {
        print "ERROR: (SNMP) OpenManage is not installed or is not working correctly\n";
        exit $E_UNKNOWN;
    }
    return;
}

Cheers,

Phil

-----Original Message-----
From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de] On Behalf Of Marcel Schulte
Sent: 11 April 2014 13:43
To: checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] Monitoring a Dell Power Edge server with Check_MK

Hi Renan,

seems as if you need another config or software running.

According to http://en.community.dell.com/dell-groups/dell-management-console/f/3731/t/19326804.aspx
and/or http://en.community.dell.com/dell-groups/dell-management-console/f/3731/t/19283067.aspx
OID tree .1.3.6.1.4.1.674.10892 seems to apply to OMSA and OID tree
.1.3.6.1.4.1.674.10893 applies to OMSS.

If your OMSS is configured and running correctly your system should provide info in the second tree, too.

What about changing the check's OID from
.1.3.6.1.4.1.674.10893.1.20.1.0 (check for OMSA version) to
.1.3.6.1.4.1.674.10892.1.100.2.0 (check for OMSA version)? Maybe the checks should be tweaked this way

Regards,
Marcel

2014-04-11 14:25 GMT+02:00 Renan Guerra Nannetti <renan.nannetti@gmail.com>:

Hi Marcel,

Just got your mail now, from the digest.
Yes! :slight_smile: That's exactly what I did.
Just need now to setup the the server to receive snmp traps...

Many thanks.

Mfg,

Renan.

-------------------

Hi Renan,

did you check the OID as requested? Just checked and all dell_om_*
checks have this OID as snmp_scan_function.

Regards,
Marcel

2014-04-11 13:21 GMT+02:00 Marcel Schulte <schulte.marcel@gmail.com>:

Hi Renan,

first thing: we don't have any dell servers here!

...but when you look at e.g. ~/share/check_mk/checks/dell_

om_disks you

can see the used test (to detect if this check applies) as
"snmp_scan_function". In case of dell_om_disks it says to apply if
SNMP OID .1.3.6.1.4.1.674.10893.1.20.1.0 exists and is not null.

You should check this OID manually. Maybe an additional SNMP agent
for OMSA must be configured/started on the server to get such OIDs
provided...

HTH,
Marcel

On Fri, Apr 11, 2014 at 9:12 AM, Renan Guerra Nannetti > <renan.nannetti@gmail.com> wrote:

Paul, Shawn, Folks,

I think I figured out what was the issue.
Inside the dell modules provide with check_mk, before adding this
service to the host, it verifies if the OMSA is present.
For this, it checks for the OID .1.3.6.1.4.1.674.10893.1.20.1.0,
which I verified that do not exist ( at least on my instance ) and
hence the service is not added.
I've replaced this check OID for another one from dell tree :
.1.3.6.1.4.1.674.10892.1.2000.10.1.6.1.1, and now the service got added.

Best regards,

Renan.

On Fri, Apr 11, 2014 at 8:46 AM, Renan Guerra Nannetti >> <renan.nannetti@gmail.com> wrote:

Hi Shawn,

Yes, I did that. I'm currently able get data from dell enterprise
tree, from my nagios server:

$ snmpwalk -v2c -c public <host> .1.3.6.1.4.1.674.10892.1.700.20.1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.2.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.3.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.4.1.1 = INTEGER: 2
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.5.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.6.1.1 = INTEGER: 160
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.7.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.8.1.1 = STRING: "System
Board Ambient Temp"
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.10.1.1 = INTEGER: 470
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.11.1.1 = INTEGER: 420
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.12.1.1 = INTEGER: 80
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.13.1.1 = INTEGER: 30
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.15.1.1 = INTEGER: 15

But, the services that are bundled with check_mk are not are note
'seeing' that...
I'm trying to run cmk -II with debug to see why the cmk is not
inventorying those services.

Thanks a lot for your help. : )

Renan.

On Fri, Apr 11, 2014 at 8:30 AM, Shawn McKee <smckee@umich.edu> wrote:

Hi Renan,

You should verify the OMSA software is running. 'omreport
system summary' should show lots of information on your hardware.

Have you configured your snmpd to pass through the Dell OIDs? On
our system we have the following line in /etc/snmp/snmpd.conf:

# Allow Systems Management Data Engine SNMP to connect to snmpd
using SMUX # (NOTE: For Dell nodes running OM) smuxpeer
.1.3.6.1.4.1.674.10892.1

You should be able to snmpwalk that tree:

snmpget -v1 -c public <host> .1.3.6.1.4.1.674.10892.1

Shawn

On Fri, Apr 11, 2014 at 6:45 AM, Renan Guerra Nannetti >>>> <renan.nannetti@gmail.com> wrote:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.
The Dell servers are configured to do it and are responding to my
manual snmpwalk/get commands ( see below ).
Yes. I've added the tag to it ( etc/check_mk/main.mk )

all_hosts = [
'hostname|snmp'
]

I don't know what I'm missing...
Thanks for you help.

renan.

$ snmpget -v1 -c public <host> sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux <host> 2.6.18-194.el5 #1
SMP Tue Mar 16 21:52:39 EDT 2010 x86_64

$ cmk -D <host>

<host> (<ip>)
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:
Contact groups: all
Type of agent: SNMP (community: 'public', bulk walk: yes,
port: default, inline: no)
Is aggregated: no
Services:
  checktype item params
description groups summarized to groups
  ------------ -----------------
------------------------------------------------------------------
---------------------------------------------------
-------------------- ------ ------------- ------
  ucd_cpu_load None (5, 10)
CPU load
  ucd_cpu_util None None
CPU utilization
  if64 2 {'state': ['1'], 'errors': (0.01,
0.10000000000000001), 'speed': 1000000000} Interface 2
  hr_mem None (150.0, 200.0)
Memory used
  snmp_info None None
SNMP Info
  snmp_uptime None {}
Uptime
  hr_fs / {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True}
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True}
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata':
True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata':
True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata':
True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0), 'magic_normsize':
20, 'levels': (80.0, 90.0), 'trend_range': 24, 'trend_perfdata':
True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>
  hr_fs <path> {'levels_low': (50.0, 60.0),
'magic_normsize': 20, 'levels': (80.0, 90.0), 'trend_range': 24,
'trend_perfdata': True} <path>

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring >>>>> <paulmonitoring@gmail.com> wrote:

A few things to obtain more information:

Are any snmp checks being returned?
Are the Dell servers configured for snmp traffic?
Can you test with a sysDescr snmpwalk from your monitoring host
and paste output.
Have you added the snmp tag to the server in your mk config?

Can you paste output of;
Cmk -D <host>

Sent from my iPhone

> On Apr 10, 2014, at 16:26, Renan Guerra Nannetti >>>>>> > <renan.nannetti@gmail.com> wrote:
>
> Hi Folks,
>
>
> I've a Dell PowerEdge machine with OMSA installed and with the
> agents running.
> However, when trying to monitor this machine via SNMP, I can't
> get those services to work :
>
> $ check_mk -L | grep dell_om
>
> dell_om_disks snmp no yes Physical Disk
> %s
> dell_om_esmlog snmp no yes ESM Log
> dell_om_mem snmp no yes Module %s
> dell_om_processors snmp no yes Processor %s
> dell_om_sensors snmp yes yes Sensor %s
>
> I've tried also to force the inventory with :
>
> $cmk -II <host>
>
> But it's still getting only basic stuff...
> I really would appreciate any help here.
>
> check_mk version : 1.2.4p2
>
> Thanks.
>
>
> guerra.
> _______________________________________________
> checkmk-en mailing list
> checkmk-en@lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
Hoople Ltd, Registered in England and Wales No. 7556595
Registered office: Plough Lane, Hereford, HR4 0LE

"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."

Marcel, Phil,

Thanks for your help. Now I got it working. : )

However, I’m not getting the SNMP Traps yet on my Event Console…

I’ve enabled MKEVENTD and also modified the etc/init.d/mkeventd start line including :
${DAEMON}_open514 --syslog --syslog-fd 3 –snmptrap --snmptrap-fd 5

I’ve also, on my monitored host, included the below lines in the snmpd.conf :

trapsink <nagios_server_ip>
trap2sink <nagios_server_ip>

However, it’s not working on Nagios+Check_mk…
The host is do sending snmp traps, once I’m getting those traps displayed in the monitor system that I’m migrating from (ZenOss Core).

Using OMD 1.11 (Check_MK 1.2.4).

Would appreciate any help on this subject.

Best,

renan.

···

On Fri, Apr 11, 2014 at 9:25 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Marcel,

Just got your mail now, from the digest.

Yes! :slight_smile: That’s exactly what I did.

Just need now to setup the the server to receive snmp traps…

Many thanks.

Mfg,

Renan.


Hi Renan,

did you check the OID as requested? Just checked and all dell_om_*

checks have this OID as snmp_scan_function.

Regards,

Marcel

2014-04-11 13:21 GMT+02:00 Marcel Schulte schulte.marcel@gmail.com:

Hi Renan,

first thing: we don’t have any dell servers here!

…but when you look at e.g. ~/share/check_mk/checks/dell_
om_disks you

can see the used test (to detect if this check applies) as

“snmp_scan_function”. In case of dell_om_disks it says to apply if

SNMP OID .1.3.6.1.4.1.674.10893.1.20.1.0 exists and is not null.

You should check this OID manually. Maybe an additional SNMP agent for

OMSA must be configured/started on the server to get such OIDs

provided…

HTH,

Marcel

On Fri, Apr 11, 2014 at 9:12 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Paul, Shawn, Folks,

I think I figured out what was the issue.

Inside the dell modules provide with check_mk, before adding this service to the host, it verifies if the OMSA is present.

For this, it checks for the OID .1.3.6.1.4.1.674.10893.1.20.1.0, which I verified that do not exist ( at least on my instance ) and hence the service is not added.

I’ve replaced this check OID for another one from dell tree : .1.3.6.1.4.1.674.10892.1.2000.10.1.6.1.1, and now the service got added.

Best regards,

Renan.

On Fri, Apr 11, 2014 at 8:46 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Shawn,

Yes, I did that. I’m currently able get data from dell enterprise tree, from my nagios server:

$ snmpwalk -v2c -c public .1.3.6.1.4.1.674.10892.1.700.20.1

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.2.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.3.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.4.1.1 = INTEGER: 2

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.5.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.6.1.1 = INTEGER: 160
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.7.1.1 = INTEGER: 3
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.8.1.1 = STRING: “System Board Ambient Temp”

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.10.1.1 = INTEGER: 470
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.11.1.1 = INTEGER: 420
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.12.1.1 = INTEGER: 80
SNMPv2-SMI::enterprises.674.10892.1.700.20.1.13.1.1 = INTEGER: 30

SNMPv2-SMI::enterprises.674.10892.1.700.20.1.15.1.1 = INTEGER: 15

But, the services that are bundled with check_mk are not are note ‘seeing’ that…

I’m trying to run cmk -II with debug to see why the cmk is not inventorying those services.

Thanks a lot for your help. : )

Renan.

On Fri, Apr 11, 2014 at 8:30 AM, Shawn McKee smckee@umich.edu wrote:

Hi Renan,

You should verify the OMSA software is running. ‘omreport system summary’ should show lots of information on your hardware.

Have you configured your snmpd to pass through the Dell OIDs? On our system we have the following line in /etc/snmp/snmpd.conf:

Allow Systems Management Data Engine SNMP to connect to snmpd using SMUX

(NOTE: For Dell nodes running OM)

smuxpeer .1.3.6.1.4.1.674.10892.1

You should be able to snmpwalk that tree:

snmpget -v1 -c public .1.3.6.1.4.1.674.10892.1

Shawn

On Fri, Apr 11, 2014 at 6:45 AM, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Paul,

Yes. The very basic ones are being returned, like SNMP Info.

The Dell servers are configured to do it and are responding to my manual snmpwalk/get commands ( see below ).

Yes. I’ve added the tag to it ( etc/check_mk/main.mk )

all_hosts = [

‘hostname|snmp’
]

I don’t know what I’m missing…

Thanks for you help.

renan.

$ snmpget -v1 -c public sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64

$ cmk -D

()
Tags: snmp-only, prod, snmp, lan, wato, /wato/
Host groups:

Contact groups: all
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: no)
Is aggregated: no
Services:
checktype item params description groups summarized to groups


ucd_cpu_load None (5, 10) CPU load

ucd_cpu_util None None CPU utilization
if64 2 {‘state’: [‘1’], ‘errors’: (0.01, 0.10000000000000001), ‘speed’: 1000000000} Interface 2

hr_mem None (150.0, 200.0) Memory used
snmp_info None None SNMP Info

snmp_uptime None {} Uptime
hr_fs / {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}

hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}
hr_fs {‘levels_low’: (50.0, 60.0), ‘magic_normsize’: 20, ‘levels’: (80.0, 90.0), ‘trend_range’: 24, ‘trend_perfdata’: True}


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

On Thu, Apr 10, 2014 at 10:05 PM, Paul Monitoring paulmonitoring@gmail.com wrote:

A few things to obtain more information:

Are any snmp checks being returned?

Are the Dell servers configured for snmp traffic?

Can you test with a sysDescr snmpwalk from your monitoring host and paste output.

Have you added the snmp tag to the server in your mk config?

Can you paste output of;

Cmk -D

Sent from my iPhone

On Apr 10, 2014, at 16:26, Renan Guerra Nannetti renan.nannetti@gmail.com wrote:

Hi Folks,

I’ve a Dell PowerEdge machine with OMSA installed and with the agents running.

However, when trying to monitor this machine via SNMP, I can’t get those services to work :

$ check_mk -L | grep dell_om

dell_om_disks snmp no yes Physical Disk %s

dell_om_esmlog snmp no yes ESM Log

dell_om_mem snmp no yes Module %s

dell_om_processors snmp no yes Processor %s

dell_om_sensors snmp yes yes Sensor %s

I’ve tried also to force the inventory with :

$cmk -II

But it’s still getting only basic stuff…

I really would appreciate any help here.

check_mk version : 1.2.4p2

Thanks.

guerra.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

I have "translated" this nagios checkplugin to check_mk checks available at:

https://github.com/HeinleinSupport/check_mk/tree/master/dell_omsa/checks

Regards

···

On 11.04.2014 15:24, Randal, Phil wrote:

Trond Amunsen's check_openmanage nagios plugin (http://folk.uio.no/trondham/software/check_openmanage.html) detects OpenManage using the following perl code:

--
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

Tel: 030 / 405051-43
Fax: 030 / 405051-19

Zwangsangaben lt. §35a GmbHG:
HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein -- Sitz: Berlin