ZenPacks : Dell Monitor : Comments

RE: Dell Monitor

community@zenoss.org — Fri, 08 Jan 2010 18:00:08 GMT

It uses here.threshold all over the place but it doesn't seem to be defined. Might wait to add instructions for adding it or where it comes from?

Thanks

Robert

RE: Dell Monitor

community@zenoss.org — Fri, 08 Jan 2010 19:14:13 GMT

This value collected by DellTemperatureSensorMap plugin from OID:.1.3.6.1.4.1.674.10892.1.700.20.1.10

RE: Dell Monitor

community@zenoss.org — Fri, 22 Jan 2010 03:15:27 GMT

Looks to me the hardware montitor for CPU Cores is incorrect.

My Intel Xeon Intel(R) Xeon(R) CPU E5345 _ 2.33GHz Stepping 7 processor is showing 1 core per proc when these procs are quad core (http://processorfinder.intel.com/details.aspx?sSpec=SL9YL).

Anyone have ideas on this one?

RE: Dell Monitor

community@zenoss.org — Tue, 04 May 2010 04:53:04 GMT

This is causing problems for me as well. Going to Perf tab after this ZenPack is installed gives the error:

User-supplied Python expression (here.threshold) for minimum value caused error: ['rpm_rpm']

I have checked, and the value from that OID can be properly retrieved.

RE: Dell Monitor

community@zenoss.org — Tue, 04 May 2010 17:56:44 GMT

try to remodel your server first.

RE: Dell Monitor

community@zenoss.org — Mon, 12 Jul 2010 12:37:58 GMT

Is there any documentation about how to install and use it? I've installed the Zenpack and added the collector plugin community.snmp.DellTemperatureSensorMap to one host. After remodeling I could not see any difference. Especially I don't see any new template available for this host. What do I miss?

RE: Dell Monitor

community@zenoss.org — Tue, 31 Aug 2010 07:10:09 GMT

<EDIT>

Scrap that, it works! My bad.

My snmpd.conf on ESX 4 had only the line "rocommunity public" and although it was putting out the usual information, it did not output any Dell specific ones.

I then used default snmpd.conf and verified with:

snmpwalk -v2c -cpublic <ip_addr> .1.3.6.1.4.1.674.10892.1

Thanks for this great zenpack!

</EDIT>

I have the same problem as dim2ue.

1. I have DellMon 2.1, deviceAdvDetail 2.2, and Zenoss 3.0.1

2. Installed Dell Openmanage, seems to be working as I can see the devices in its web-based Server Administrator

3. I don't see any new graphs under Graphs, or any other thing for that matter, even after leaving out everything except the DellMon modeler plugins. I do see the templates under Advanced | Monitoring Templates

RE: Dell Monitor

community@zenoss.org — Fri, 08 Oct 2010 18:26:40 GMT

I am running Zenoss 2.5.2 and revision 2.0 of this zenpack. I have a memory DIMM that is in degraded state as reported by Dell Open Manage. If I go to the hardware tab on the device I see the memory DIMM is amber colored, however it does not show up on the Status tab (under Component Type) and no event is created.

Is this expected behavior?

RE: Dell Monitor

community@zenoss.org — Thu, 14 Oct 2010 03:19:25 GMT

Egor -

Love the ZenPack. Thanks!

A couple of requests:

1. Would love the expansion card data to return DRAC information more than slot (IP, firmware, etc.) just like the HPMON does for iLO's.

2. would love reports like you have on the HPMon ZenPack for Dell DRACs (IP address, firmeware version, etc.).

3. would love events for if/when the DRACs stop responding (which does happen more than it should!)

If you don't have this anywhere on your radar, let me know. I may take a crack at it.

Thanks!

RE: Dell Monitor

community@zenoss.org — Thu, 14 Oct 2010 17:30:10 GMT

Hi elevin,

i doesn't have any Dell servers. So we have two options:

1. PM with snmpwalk dump for .1.3.6.1.4.1.674.10892.2 OID.

2. PM with you patches.

Egor

RE: Dell Monitor

community@zenoss.org — Fri, 22 Oct 2010 12:33:20 GMT

Hi Egor,

if i add the community.snmp.DellExpansionCardMap to the plugin list, i become the following error:

2010-10-22 14:30:08,749 ERROR zen.ZenModeler: Traceback (most recent call last):

File "/var/opt/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner

return callable(*args, **kw)

File "/var/opt/zenoss/Products/ZenHub/services/ModelerService.py", line 109, in remote_applyDataMaps

if adm._applyDataMap(device, map):

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 198, in _applyDataMap

changed = self._updateRelationship(tobj, datamap)

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 256, in _updateRelationship

objchange, obj = self._createRelObject(device, objmap, rname)

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 404, in _createRelObject

constructor = importClass(objmap.modname, objmap.classname)

File "/var/opt/zenoss/Products/ZenUtils/Utils.py", line 364, in importClass

raise ex

ImportError: No module named DellRemoteAccessCntlr

Traceback (most recent call last):

File "/opt/zenoss/Products/DataCollector/zenmodeler.py", line 658, in processClient

if driver.next():

File "/var/opt/zenoss/Products/ZenUtils/Driver.py", line 64, in result

raise ex

RemoteException: Traceback (most recent call last):

File "/var/opt/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner

return callable(*args, **kw)

File "/var/opt/zenoss/Products/ZenHub/services/ModelerService.py", line 109, in remote_applyDataMaps

if adm._applyDataMap(device, map):

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 198, in _applyDataMap

changed = self._updateRelationship(tobj, datamap)

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 256, in _updateRelationship

objchange, obj = self._createRelObject(device, objmap, rname)

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 404, in _createRelObject

constructor = importClass(objmap.modname, objmap.classname)

File "/var/opt/zenoss/Products/ZenUtils/Utils.py", line 364, in importClass

raise ex

ImportError: No module named DellRemoteAccessCntlr

2010-10-22 14:30:08,751 ERROR zen.ZenModeler: Client eos finished with message: [Failure instance: Traceback (failure with no frames): : Traceback (most recent call last):

File "/var/opt/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner

return callable(*args, **kw)

File "/var/opt/zenoss/Products/ZenHub/services/ModelerService.py", line 109, in remote_applyDataMaps

if adm._applyDataMap(device, map):

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 198, in _applyDataMap

changed = self._updateRelationship(tobj, datamap)

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 256, in _updateRelationship

objchange, obj = self._createRelObject(device, objmap, rname)

File "/var/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 404, in _createRelObject

constructor = importClass(objmap.modname, objmap.classname)

File "/var/opt/zenoss/Products/ZenUtils/Utils.py", line 364, in importClass

raise ex

ImportError: No module named DellRemoteAccessCntlr

]

2010-10-22 14:30:08,751 INFO zen.ZenModeler: Scan time: 5.91 seconds

2010-10-22 14:30:08,787 INFO zen.ZenModeler: Daemon ZenModeler shutting down

Thomas

RE: Dell Monitor

community@zenoss.org — Fri, 29 Oct 2010 15:36:02 GMT

Ok after struggling a bit to get this ZenPack working, I got it working.

My situation started here, if you're interested to see the background.

My environment:

Zenoss v3.0.2 VMWare appliance;

Advanced Device Details v2.4

Dell Monitor v2.2

Dell Open Manage 6.2.0.1

For whom who need's advice, I put it to work this way:

After installing everything, i.e.: Dell Open Manage (on client servers), Advande Device Details zenpack and Dell Monitor zenpack, you need to add this:

community.snmp.DellCPUMap
community.snmp.DellDeviceMap
community.snmp.DellExpansionCardMap
community.snmp.DellFanMap
community.snmp.DellHardDiskMap
community.snmp.DellLogicalDiskMap
community.snmp.DellMemoryModuleMap
community.snmp.DellNicMap
community.snmp.DellPowerSupplyMap
community.snmp.DellTemperatureSensorMap

to the node you want to monitor, in:

Configuration Properties \ zCollectorPlugins

After this, remeber to Model Device.
Wait a few minutes to get the information gathered by the agent. Once you reopen the device you'll see below Components, all the information provided by this ZenPack.

Let me say that it work's like a charm.

Maybe there is a way to do this easily. If you know one I'll be glad to learn it.

Thank's and regards,

Luís

RE: Dell Monitor

community@zenoss.org — Thu, 16 Dec 2010 12:23:17 GMT

Hi,

I'm trying to use the DellMonitor Zenpack (v2.3) on Zenoss 3.0.03 (Zenoss was installed using the stack installer, but I don't suppose that makes any difference)

I've installed the Advanced Device Details Zenpack v2.5 and restarted Zenoss

Then installed the DellMonitor pack, restarted Zenoss

(both were installed via the command line and showed no errors on installation, have also tried installing via the GUI but I assume it's exactly the same )

Have added the modeller plugins to the device im trying to model (via Add Fields on the Modeler Plugins page for the device)

Then modelled the device

When I go to view Graphs, I see

User-supplied Python expression (here.threshold) for minimum value caused error: ['rpm_rpm']

I assume that is related to the DellFan template, if I unbind that template and re-model, I get a very similar error this time relating to temperature (presumably one of the two temperature-related templates)

I also dont see any of the additional tabs that these packs are meant to add eg Hardware, OSDetail (I assume that in 3.0 these don't show as tabs, rather as entries on the left hand navigation, but they dont appear anywhere)

I DO see the additional reports the DellMonitor pack is supposed to add - DRAC Controllers and Dell Storage Controllers.

Other Zenpacks I have installed work with no problems.

Anyone seen this before?

Cheers,

Mark

RE: Dell Monitor

community@zenoss.org — Thu, 16 Dec 2010 20:08:47 GMT

Hi Mark,

unbind all Dell* templates from devices and device classes.

RE: Dell Monitor

community@zenoss.org — Thu, 16 Dec 2010 23:04:21 GMT

Hi,

My mistake - they are unbound, it's actually if I remove the graph definition then the error message just changes from the one regarding the fan to one regarding temperature (obviously, as the fan graph is no longer trying to display on the page).

I have actually got most of this to work now, the only bit I haven't been able to fix is getting the fan speed and the temp probes to work. The issue seems to have been old versions of OpenManage - when I snmpwalked the OID's they were returning nothing, I installed a newer version of OpenManage and now I get RPM and temperature valus returned when I snmpwalk those OIDS.

However, the Temperature Sensor and Fans components still don't return those values in Zenoss - they show up as monitored, status OK etc but the temp/fan speeds show as 'unknown'

Graphs still shows the

"User-supplied Python expression (here.threshold) for minimum value caused error: Dell Monitor"

This pack is brilliant, really useful as all our servers are Dell. I just want to get these last two bits working if I can.

Thanks,

Mark

RE: Dell Monitor

community@zenoss.org — Fri, 21 Jan 2011 18:42:10 GMT

I'm getting this too.

"User-supplied Python expression (here.threshold) for minimum value caused error: 'rpm_rpm'"

I tried removing the value from the threshold minimum field. It then showed an error for the temperature sensor. I removed that threshold value and it then came up with an error in the filesystem template. That is when I figured there was another problem.

Since filesystem is working on other systems, there must be something else at issue. I just don't know how to track it down. I'm going to try other troubleshooting tricks, but I think that the problem is embedded in the Fan collector.

I have unbound the Dell* templates, but then I don't get any graphs for those. HELP??

RE: Dell Monitor

community@zenoss.org — Mon, 28 Mar 2011 03:41:16 GMT

bigegor, I would like to request you to change the component name for (Hard Disks), since there is conflict with Zenoss(Hard Disks) itself against the component name.

Thanks.

RE: Dell Monitor

community@zenoss.org — Mon, 28 Mar 2011 18:47:54 GMT

Hi Gavin_Shen,

i'm not realy understend your problem. Which conflict do you mean? In DellMon class names are different, page templates have different names and performance templates also have differnent names.

Egor

RE: Dell Monitor

community@zenoss.org — Wed, 27 Apr 2011 17:16:45 GMT

When I attempt to model a server with OpenManage installed I receive this error:

2011-04-27 10:45:27,837 INFO zen.ZenModeler: processing DellDeviceMap for device X.X.X.X

2011-04-27 10:45:27,837 ERROR zen.ZenModeler: Problem while executing plugin DellDeviceMap

2011-04-27 10:45:27,842 ERROR zen.ZenModeler: Traceback (most recent call last):

File "/opt/zenoss/Products/DataCollector/zenmodeler.py", line 613, in processClient

datamaps = plugin.process(device, results, self.log)

File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.DellMonitor-2.1.0-py2.6.egg/ZenPacks/zenoss/DellMonitor/modeler/plugins/DellDeviceMap.py", line 40, in process

if getdata['setHWProductKey'] is None: return None

KeyError: 'setHWProductKey'

Further details are in the forums at http://community.zenoss.org/message/58323

Any help is appreciated.

RE: Dell Monitor

community@zenoss.org — Fri, 20 May 2011 13:54:16 GMT

Hello Egor,

We have devices that are reporting their Hardware make as Unknown and others reporting as Generic. I believe I know what the problem is with those reporting as Generic but not sure about the ones that are Unknown. One of these example devices is a Dell R610.

Is it possible your ZenPack needs to be updated to support newer models are should we be taking a closer look at things on our end?

Thanks,

John

RE: Dell Monitor

community@zenoss.org — Tue, 14 Jun 2011 18:41:25 GMT

Nevermind I ended up setting this manually. =)

Thanks for the great Zenpack once again!

RE: Dell Monitor

community@zenoss.org — Fri, 24 Jun 2011 18:17:38 GMT

Hi!

I have an issue I suspect may be this pack or the Device Adv Detail pack.

Ubuntu 8.04

Zenoss 3.1.0 stack installer (upgrade)

Dellmon 2.4

deviceAdvDetail 2.7

The pack is able identify my hardware correctly but my problem is that I have several PERC cards that have older firmware and are alerting as "threshold of DellStorageCntlr status exceeded: current status Non-critical". True to it's word, it's non-critical and I don't really care about it. In fact, I don't really care to monitor those cards at all so I am trying to set their monitored status to 'false'. I can do so, but as soon as the device is modeled again, the status changes back to 'true'. Is there a way I can make that stick?

thanks!

Marc

RE: Dell Monitor

community@zenoss.org — Fri, 24 Jun 2011 18:24:19 GMT

Hi Mark,

you can comment or delete line 44 in DellExpansionCardMap.py file.

Egor

RE: Dell Monitor

community@zenoss.org — Fri, 24 Jun 2011 18:31:33 GMT

Thank you! Appears to have done the trick!

RE: Dell Monitor

community@zenoss.org — Sat, 17 Sep 2011 14:16:05 GMT

The problem isn't the class, it's the fact that the Dell Disk Drives are put under the component "Hard Disks" which is also where the WMIPerf_Windows puts it's hard disks. Hence, there is a conflict. Is there any way to fix this?

RE: Dell Monitor

community@zenoss.org — Sun, 18 Sep 2011 09:20:33 GMT

remove either community.snmp.DellHardDiskMap or community.wmi.DiskDriveMap from zCollectorPlugins list and remodel your server.

RE: Dell Monitor

community@zenoss.org — Sun, 18 Sep 2011 15:01:38 GMT

I removed community.wmi.DiskMap and remodeled but it's still showing the PHYSICALDRIVE 0 under Hard Disks and not the Dell Hard Drives. So I deleted the device, added it back and made sure community.wmi.DiskMap was not there. Now it won't create the Hard Disks component, even though I can do a successful snmpget against the drives. Any ideas?

RE: Dell Monitor

community@zenoss.org — Mon, 19 Sep 2011 16:33:24 GMT

It appears that it's the model of the Dell server that's the issue. Only the 9th generation models work right with this zenpack. 2850's and any new R or T series do not pull everything and most importantly they won't pull the Hard Drives. Any way to fix this? I can't imagine Dell changed the OID from 8th gen to 9th gen to 11th gen.

RE: Dell Monitor

community@zenoss.org — Mon, 19 Sep 2011 22:13:14 GMT

I reinstalled OMSA and was able to start getting a response via SNMP for the Hard Disks but they still aren't appearing under Components. I do however get Temp, Fans, etc.

snmpwalk -cpublic -v2c server 1.3.6.1.4.1.674.10893.1.20.130.4.1.4

SNMPv2-SMI::enterprises.674.10893.1.20.130.4.1.4.1 = INTEGER: 3

SNMPv2-SMI::enterprises.674.10893.1.20.130.4.1.4.2 = INTEGER: 3

I also get a valid response back from the storage controller.. SAS 6/iR

snmpwalk -cpublic -v2c server 1.3.6.1.4.1.674.10893.1.20.130.1.1.38

SNMPv2-SMI::enterprises.674.10893.1.20.130.1.1.38.1 = INTEGER: 3

I also don't get any power supplies.

Any ideas? Server is WIndows 2008 R2, PowerEdge R210 with OMSA 6.5.

RE: Dell Monitor

community@zenoss.org — Thu, 22 Sep 2011 00:09:26 GMT

try version 2.4.2 from GIT repository.

RE: Dell Monitor

community@zenoss.org — Thu, 22 Sep 2011 02:45:24 GMT

That's above my skill level. Can you email me the zenpack? I am more than willing to be your beta tester, I have a full Dev Zenoss box set up.

RE: Dell Monitor

community@zenoss.org — Thu, 22 Sep 2011 13:30:23 GMT

I figured it out and will install and report back.

For anyone else:

yum install git

git clone git://github.com/epuzanov/ZenPacks.community.DellMon.git

zenpack --link --install ZenPacks.community.DellMon

RE: Dell Monitor

community@zenoss.org — Thu, 22 Sep 2011 14:28:52 GMT

THe R210 is now picking up the hard drives. Thank you so much!

Seeing this in the logs though. It appears the 2.4 version as well as the 2.4.2 version were both getting this. Safe to ignore or something to fix?

WARNING zen.ApplyDataMap: The attribute moduletype was not found on object BANK2_B from device server.domain.local

RE: Dell Monitor

community@zenoss.org — Thu, 22 Sep 2011 17:47:20 GMT

Fixed in Git. Thanks for the report!

RE: Dell Monitor

community@zenoss.org — Wed, 28 Sep 2011 13:11:29 GMT

Egor,

I installed the newest version from GIT on v4.0.2, and I'm getting a transform error:

Component:	/Change/Set/Status
Event Class:	/
Status:	New
Message:	Problem with line 474:

exception	AttributeError: firstTime
transform	0 if evt.firstTime == evt.lastTime and hasattr(evt, 'compClass'): 1 for comp in device.getMonitoredComponents(type=evt.compClass): 2 if comp.id != evt.component: continue 3 comp.status = int(evt.compStatus) 4 from transaction import commit 5 commit() 6 break

Any idea how to fix this?

Thanks

RE: Dell Monitor

community@zenoss.org — Tue, 25 Oct 2011 20:52:02 GMT

Hi Egor,

I noticed when we have a hardware event (for example a failed PSU) that while the trap is sent to Zenoss the component on the device in question doesn't reflect that this component has failed/is bad.

Is this expected behavior? Or is it possible we have something setup/configured incorrectly?

Thanks,

John

RE: Dell Monitor

community@zenoss.org — Thu, 27 Oct 2011 13:36:04 GMT

John, this zenpack does SNMP gets, not traps. There is a zenpack called Dell Transform or something like that, that will transform an SNMP trap from the server and generate an alert but I don't think it's going to make the component from this zenpack show red. It's worth a try though.

http://community.zenoss.org/docs/DOC-4537

RE: Dell Monitor

community@zenoss.org — Wed, 07 Mar 2012 13:52:34 GMT

Hi,

Has anyone gotten this to work with 3.2.1? I've tried to install it but the zenpack never appears and I get no error message.. (I was looking in Zope log in the daemon page) I assume it's because the plugin is python 2.4. Is there a version for 2.6 available/forthcoming?

Thanks,

Joan

RE: Dell Monitor

community@zenoss.org — Thu, 07 Jun 2012 16:50:33 GMT

Hi joanypony,

I've got this working on 3.2.1. Have you got the Advanced Device Details zenpack installed? Also restarting zope alone didn't do it for me, I had to restart all of zenoss (stack).

Cheers, Jim

RE: Dell Monitor

community@zenoss.org — Mon, 20 Aug 2012 20:33:30 GMT

Do you have a version ready for Zenoss 4.2?

RE: Dell Monitor

community@zenoss.org — Mon, 20 Aug 2012 21:44:19 GMT

I answered my own question. Installed the advanced detail from github and saw it was py2.7 and then dell monitor 2.4.4 from github as well, also say it was 2.7 Will let you know if I find any bugs.

Thanks for all of the good work!

RE: Dell Monitor

community@zenoss.org — Tue, 21 Aug 2012 18:34:12 GMT

So, did you get to install this on Zenoss Core v.4? what's the receip?

RE: Dell Monitor

community@zenoss.org — Tue, 21 Aug 2012 18:53:16 GMT

I was able to install it successfully and it's working against a Dell R210 and Dell OMSA 6.5 at the moment. Haven't tried it against any other hardware or new/older OMSA versions just yet.

Here is what I did to get it installed with Zenoss 4.2.

su - zenoss

git clone git://github.com/epuzanov/ZenPacks.community.deviceAdvDetail.git

zenpack --install ZenPacks.community.deviceAdvDetail

git clone git://github.com/epuzanov/ZenPacks.community.DellMon.git

zenpack --install ZenPacks.community.DellMon

zenoss restart | may not be needed but I like to restart just to make sure everything is good.

RE: Dell Monitor

community@zenoss.org — Tue, 21 Aug 2012 18:55:37 GMT

awesome, I'll look at it.

cheers,

2012/8/21 OneLoveAmaru <community@zenoss.org>

**
Zenoss Community <http://community.zenoss.org/index.jspa> Dell
Monitor new comment by OneLoveAmaru<http://community.zenoss.org/people/OneLoveAmaru> View
all comments on this document<http://community.zenoss.org/docs/DOC-3410#comment-6000>

RE: Dell Monitor

community@zenoss.org — Sat, 29 Sep 2012 21:39:00 GMT

Hi mate,

Have you found any bugs in this or is it working as expected?

Regards, Jim

RE: Dell Monitor

community@zenoss.org — Mon, 01 Oct 2012 08:09:05 GMT

for my own part I need to set up my environment for accepting WMI. It's a shitty job on all servers. But with Core 4.2, the Dell package and SNMP monitoring It works rather well and for all the basic meatrics you want to get from your server farm are in place. If this package fails, it's not the package itself, it's your setup that doesn't completely match it's prerequisites. I know, I've spent some time cursing it all

RE: Dell Monitor

community@zenoss.org — Mon, 03 Dec 2012 08:25:56 GMT

I have model my windows based servers of this zenpack but unable to model Linux based servers so kindly advice me.

RE: Dell Monitor

community@zenoss.org — Mon, 03 Dec 2012 09:57:20 GMT

below are the logs for your reference.

2012-12-03 14:56:30,971 INFO zen.ZenModeler: Connecting to localhost:8789

2012-12-03 14:56:30,987 INFO zen.ZenModeler: Connected to ZenHub

2012-12-03 14:56:31,109 INFO zen.ZenModeler: Collecting for device orastb.fti-nbil.com

2012-12-03 14:56:31,288 INFO zen.ZenModeler: No WMI plugins found for orastb.fti-nbil.com

2012-12-03 14:56:31,299 INFO zen.ZenModeler: No Python plugins found for orastb.fti-nbil.com

2012-12-03 14:56:31,303 INFO zen.ZenModeler: No command plugins found for orastb.fti-nbil.com

2012-12-03 14:56:31,309 INFO zen.ZenModeler: SNMP collection device orastb.fti-nbil.com

2012-12-03 14:56:31,309 INFO zen.ZenModeler: plugins: community.snmp.DellCPUMap, community.snmp.DellExpansionCardMap, community.snmp.DellFanMap, community.snmp.DellLogicalDiskMap, community.snmp.DellMemoryModuleMap, community.snmp.DellPowerSupplyMap, community.snmp.DellTemperatureSensorMap, zenoss.snmp.DeviceMap, zenoss.snmp.NewDeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap, zenoss.snmp.IpServiceMap, zenoss.snmp.HRFileSystemMap, zenoss.snmp.HRSWRunMap, community.snmp.DellDeviceMap, community.snmp.DellHardDiskMap

2012-12-03 14:56:31,389 INFO zen.ZenModeler: No portscan plugins found for orastb.fti-nbil.com

2012-12-03 14:56:32,244 INFO zen.SnmpClient: snmp client finished collection for orastb.fti-nbil.com

2012-12-03 14:56:32,245 INFO zen.ZenModeler: processing community.snmp.DellCPUMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,246 INFO zen.ZenModeler: processing community.snmp.DellExpansionCardMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,247 INFO zen.ZenModeler: processing community.snmp.DellFanMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,248 INFO zen.ZenModeler: processing community.snmp.DellLogicalDiskMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,249 INFO zen.ZenModeler: processing community.snmp.DellMemoryModuleMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,250 INFO zen.ZenModeler: processing community.snmp.DellPowerSupplyMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,250 INFO zen.ZenModeler: processing community.snmp.DellTemperatureSensorMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,251 INFO zen.ZenModeler: processing zenoss.snmp.DeviceMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,252 INFO zen.ZenModeler: Processing zenoss.snmp.NewDeviceMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,254 INFO zen.ZenModeler: Modeler zenoss.snmp.InterfaceMap processing data for device orastb.fti-nbil.com

2012-12-03 14:56:32,256 INFO zen.ZenModeler: processing zenoss.snmp.RouteMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,258 INFO zen.ZenModeler: processing zenoss.snmp.IpServiceMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,260 INFO zen.ZenModeler: Modeler zenoss.snmp.HRFileSystemMap processing data for device orastb.fti-nbil.com

2012-12-03 14:56:32,261 INFO zen.ZenModeler: Skipping Memory Buffers (other) as it matches zFileSystemMapIgnoreTypes.

2012-12-03 14:56:32,261 INFO zen.ZenModeler: Skipping Swap Space (virtualMemory) as it matches zFileSystemMapIgnoreTypes.

2012-12-03 14:56:32,262 INFO zen.ZenModeler: Skipping Real Memory (ram) as it matches zFileSystemMapIgnoreTypes.

2012-12-03 14:56:32,264 INFO zen.ZenModeler: Processing zenoss.snmp.HRSWRunMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,282 INFO zen.ZenModeler: processing community.snmp.DellDeviceMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,282 INFO zen.ZenModeler: processing community.snmp.DellHardDiskMap for device orastb.fti-nbil.com

2012-12-03 14:56:32,459 INFO zen.ZenModeler: No change in configuration detected

2012-12-03 14:56:32,511 INFO zen.ZenModeler: Scan time: 1.40 seconds

2012-12-03 14:56:32,520 INFO zen.ZenModeler: Daemon ZenModeler shutting down

RE: Dell Monitor

community@zenoss.org — Mon, 03 Dec 2012 17:37:50 GMT

Hi arshadkhan20,

have you installed Dell OpenManage Agent on your Linux machines?

RE: Dell Monitor

community@zenoss.org — Tue, 04 Dec 2012 04:47:13 GMT

Hi Bigegor,

We have installed "Dell OpenManage Server Administrator" on linux based machines. Below is the web access snap of said server for your reference.

RE: Dell Monitor

community@zenoss.org — Tue, 04 Dec 2012 10:27:38 GMT

The web console is not required for SNMP and has no bearing on it. Can you manually run an snmpwalk from another machine and query your server in question? If you can't do that, then zenoss can't do it. You need to check your /etc/snmp/snmpd.conf file and verify it's set up correctly and also verify port 161 UDP is open.

Here is my snmpd.conf, it's very short and sweet.

rocommunity public

com2sec local localhost public

com2sec mynetwork 192.168.0.33 public

syslocation "Data Center"

syscontact admin@domain.com

smuxsocket 127.0.0.1

smuxpeer .1.3.6.1.4.1.674.10892.1

dontLogTCPWrappersConnects yes

Change public to your SNMP community and syslogcation/syscontact and you should be in business.

What connects the snmpd process to OMSA is the smuxsocket and smuxpeer.

After you update your file, give snmpd a restart and also dataeng a restart.

/etc/init.d/snmpd restart

/etc/init.d/dataeng restart

RE: Dell Monitor

community@zenoss.org — Tue, 04 Dec 2012 10:48:07 GMT

Hi,

Try

/etc/init.d/dataeng enablesnmp

/etc/init.d/dataeng restart

/etc/init.d/snmpd restart

The newer releases do not enable snmp always.

Kind regards,

Maurice

Verstuurd vanaf mijn iPhone

RE: Dell Monitor

community@zenoss.org — Tue, 05 Mar 2013 20:01:44 GMT

The Dell Disks need it's own section. ucd hardiskmap overides this and then we loose the serial number and actual disk failure info. Please fix.

RE: Dell Monitor

community@zenoss.org — Tue, 05 Mar 2013 20:51:25 GMT

remove ucd hardiskmap plugin from zCollectorPlugins list.

RE: Dell Monitor

community@zenoss.org — Tue, 12 Mar 2013 17:54:37 GMT

Hi, I have several poweredge r320 servers with iDRAC7 cards. None of these cards show up under the DRAC report, I do have a antoher server with a iDRAC6 card which does show up. The only thing I have noticed which may be the problem is that on the r320's the drac card is not listed under the pci slots. Here are the details of the card from the drac web interface:

RAC Information

Name

iDRAC

Product Information

Integrated Dell Remote Access Controller 7 Enterprise

Date/Time

Tue Mar 12 12:50:13 2013

Firmware Version

1.23.23 (Build 01)

Firmware Updated

Fri Nov 9 00:03:16 2012

Hardware Version

0.01

Please let me know if there is anything else I can provide you with.

Thanks

RE: Dell Monitor

community@zenoss.org — Thu, 02 May 2013 00:22:47 GMT

Egor,

Would you be interested in adding support for the Predicted Failure flag on physical disks as exposed via SNMP? The below OID indicates if a disk is in predicted failure (i.e. SMART is angry):
.1.3.6.1.4.1.674.10893.1.20.130.4.1.31.1

1 = OK, 2 = Failure Predicted

Thanks~

RE: Dell Monitor

community@zenoss.org — Tue, 12 Nov 2013 17:42:41 GMT

Hello,

I am getting errors for DellFan, MemoryModules, and Dell Storage Controller. I am using Zenoss 4.2.4. Everything appears to be working except for the Storage Controller and these critical events that are being triggered.

Has anyone come across these before?

Thank you,

John

Unhandled exception in zenhub service ZenPacks.zenoss.CalculatedPerformance.services.CalcPerfConfig.CalcPerfConfig: 'DellFan' object has no attribute 'id'

Unhandled exception in zenhub service ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService.ZenJMXConfigService: 'DellFan' object has no attribute 'getThresholdInstances'

Traceback (most recent call last): File "/opt/zenoss/Products/ZenCollector/services/config.py", line 116, in _wrapFunction return functor(*args, **kwargs) File "/opt/zenoss/Products/ZenCollector/services/config.py", line 233, in _createDeviceProxies proxy = self._createDeviceProxy(device) File "/opt/zenoss/Products/ZenHub/services/CommandPerformanceConfig.py", line 196, in _createDeviceProxy commands, proxy.thresholds) File "/opt/zenoss/Products/ZenHub/services/CommandPerformanceConfig.py", line 93, in _safeGetComponentConfig if not comp.monitorDevice(): AttributeError: 'DellFan' object has no attribute 'monitorDevice'

Unhandled exception in zenhub service Products.ZenHub.services.SnmpPerformanceConfig.SnmpPerformanceConfig: 'DellFan' object has no attribute 'snmpIgnore'

RE: Dell Monitor

community@zenoss.org — Tue, 12 Nov 2013 19:05:37 GMT

I had installed this ZenPack through the GUI. A messages popped up saying to restart zope so I did. I had to restart Zenoss. Once I did that everything worked great.

Thank you.