ZenPacks : HP ProLiant Monitor : Comments

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 02 Nov 2009 16:21:28 GMT

Great pack but there are no installation notes. Can someone please update the post w/ an install section.

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 07 Feb 2010 21:23:37 GMT

If like me you use Ubuntu (or Debian I guess), and want to take advantage of this you need Net-SNMP and HP's 'HP ProLiant Support Pack CD for dpkg-based distributions'

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=1121486&prodNameId=3288144&swEnvOID=4084&swLang=8&mode=2&taskId=135&swItem=MTX-ee4cf438fc6a4fbb875baad8ed

The file I ended up with was called: HP_ProLiant_Value_Add_Software-8.32-6-2.iso

These commands might help you:

root@virt01:~# mount HP_ProLiant_Value_Add_Software-8.32-6-2.iso /cdrom -t iso9660 -o loop

root@virt01:~# apt-cdrom -m add

root@virt01:~# apt-get install hp-health

root@virt01:~# apt-get install hp-snmp-agents

root@virt01:~# /sbin/hpsnmpconfig

root@virt01:~# /etc/init.d/hp-snmp-agents restart

root@virt01:~# umount /cdrom

Subsequently you should get some action when walking like so: snmpwalk -v2c -c <snmp community> <proliant ip> 1.3.6.1.4.1.232

Following this just use the procedure given above. Given again here for completeness:

1. From the > Menu select More -> Collector Plugins

2. Remove the zenoss.snmp.Cpu (click the X next to it)

3. Click "Add Fields"

4. Drag and drop all of the "community.snmp.HP*" entries in the right list over into the left list.

5. CLICK SAVE (don't forget this step)

6. From the > Menu select Manage -> Model Device

7. Once it is completed modeling check out the hardware tab for the device, you should see CPUs, Harddrives, Fans, etc. If you don't you may have problems with snmp, so check those settings the usual way.

You snmpd.conf might look like this:

dlmod cmaX /usr/lib64/libcmaX64.so

rwcommunity <snmp community> localhost

rwcommunity <snmp community>

trapcommunity <snmp community>

trapsink <trap host ip> <snmp community>

If you are not using AMD64/EM64T version but x86 the iso CD image is a different one, be aware:

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3288144&prodTypeId=15351&prodSeriesId=1121486&swLang=8&taskId=135&swEnvOID=4085

If you use DeadRat, then call your account manager... ;-)

RE: HP ProLiant Monitor

community@zenoss.org — Sat, 20 Feb 2010 15:14:34 GMT

the zenpack seems unable to collect physical disks for BL 465c blade servers, everything else is working fine.

edit: typo's

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 21 Feb 2010 21:49:29 GMT

Hello mastrboy,

can you provide MIB for BL465c physical drives?

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 23 Feb 2010 16:13:29 GMT

well something is just off.. After letting zenoss just run,2 days after adding the Zenpack the physical disks decides to pop-up.. Not sure what is wrong, any logs i could look at to find out why they suddenly appeared on their own? (It's a clean install of zenoss 2.5.1 on debian 5.0)

The mibs are probably included but something in my modeling/collecting is wrong, but what...

I now have the problem on a BL460c blade, the physical disks does not show up no matter how many times i re-model the device

RE: HP ProLiant Monitor

community@zenoss.org — Sat, 27 Feb 2010 21:47:35 GMT

Mashboy,

I don't know if I am seeing the same thing, but I have added the zenpacks and modeled my HP DL585. Everything shows up except the physical/logical drives. Guess I will wait the 2-3 days and see what pops up. I have sniffed the SNMP traffic during the modeling process and I see the disk information retrieved from the box, so I do not know why the UI is not showing the information.

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 28 Feb 2010 12:54:53 GMT

put HPHardDiskMap, HPLogicalDiskMap and HPExpansionCardMap collector plugins to the end of zCollectorPlugins list.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 28 Feb 2010 16:51:38 GMT

i'll try that, does this mean you can confirm the "bug" ?

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 28 Feb 2010 18:47:10 GMT

Thanks Egor, I will give that a try.

BTW: My physical hard disks appeared two days after the system was modeled just as mashboy indicated. The logical drives did not.

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 28 Feb 2010 19:47:56 GMT

I tried making the changes and here is my experience:

1. I cannot drag/drop collectors plugins with IE7/IE8, only Firefox. However, in Firefox I cannot drag/drop anything that is not on the first page. If I scroll down the list, items no longer drag/drop correctly. So, I had to use IE7 to edit the text in the entry field on that browser using cut/paste.

2. The logical disks are still not showing.

3. The Power Supplies are all stating 0 watts and unknown voltage

4. The CPU's are all stating 0mV for Volts

5. If I click on any hard disk, the graph shows negative numbers for LWrites. One disk shows a positive single LRead value.

6. On the CPU graphs, the Y-axis is in Centigrade and the "degree" symbox is a square with an "X" in it. On the hardware tab, the CPU temperatures are in Fahrenheit.

7. The fan speed is shown as "Normal", but the graph shows a constant speed of "2".

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 28 Feb 2010 22:33:20 GMT

Hello svandomelen,

1. address this problem to Zenoss developers, please.

2. please install, Advanced Device Details ZenPack first and restart zenoss.

3. HP SIM Agent doesn't return voltage and watts values for PowerSupplies.

4. HP SIM Agent doesn't return voltage and L1 cache size for CPUs.

5. isn't an error but a Feature.

6. HP SIM Agent returned temperature value in Celsius

7, HP SIM Agent returned FAN speed as discret value (1: Unknown, 2:Normal, 3:High)

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 01 Mar 2010 00:07:40 GMT

Hi Egor,

I will take the cut/paste comments to the other developers, just thought I would be complete in my description.

I installed the Advanced Device Details ZenPack before installing the HP Proliant Monitor. I even tried uninstalling and reinstalling both, but it did not help.

Since my last comment, I now show eight disk drives. The ones that end in "2" have graphs with a red X.

Thanks for all of the other clarifications. I really appreciate the work and support on this Zenpack.

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 01 Mar 2010 00:23:19 GMT

Egor,

I removed the Advanced Device Details and the HP Proliant Monitor zenpacks from my installation and restart Zenoss. Then, I reinstalled them and restart zenoss again. Nothing changed, so I remodeled the server again. It had kept the collector plugins, so I did not have to add them back in.

To my delight, everything came up perfectly. Number of drives, logical disks and the DIMMs.

Not sure why my first attempts did not work, but I am happy with my current results.

Thanks so much again for your patience, support and a great Zenpack!

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 22 Mar 2010 14:55:38 GMT

Anyone else have problem with the memory on DL360 G6?

Board0 DIMM9

Unknown

DDR DIMM 2.0GB 1333MHz

2.0GB

IT shows up under model and size but shows a yellow dot with not present.

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 24 Mar 2010 13:17:57 GMT

I have a HP server where I recieve events about components that I can't find i the UI. I can look at the components by following the links in the event viewer, and then I see a status page with a graph and Template and Modifications tabs. But I can't find them under the Hardware tab.

If I enter this adress in my browser:

http://zenosshost:8080/zport/dmd/Devices/Server/Windows/devices/192.168.250.61/hw/cards/

I get this output:

[<cpqDaCntlr at /zport/dmd/Devices/Server/Windows/devices/192.168.250.61/hw/cards/cpqDaCntlr2>, <cpqIdeController at /zport/dmd/Devices/Server/Windows/devices/192.168.250.61/hw/cards/cpqIdeController0>, <cpqNicIfPhysAdapter at /zport/dmd/Devices/Server/Windows/devices/192.168.250.61/hw/cards/cpqNicIfPhysAdapter0_1>, <cpqNicIfPhysAdapter at /zport/dmd/Devices/Server/Windows/devices/192.168.250.61/hw/cards/cpqNicIfPhysAdapter0_2>, <cpqSm2Cntlr at /zport/dmd/Devices/Server/Windows/devices/192.168.250.61/hw/cards/cpqSm2Cntlr0>]

Shouldn't those components show up under the Hardware tab? The adresses indicates that they're in a subgroup called cards, but there's no such group under the Hardware tab.

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 08 Aug 2010 02:25:44 GMT

is there a way to display the ILO IP address on a zlink value?

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 26 Aug 2010 13:28:19 GMT

any idea of how to display the HP ILO IP address as a Zlink using this zenpack?

I can see the ip address in the details panel of the ilo extensions cards components

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 26 Aug 2010 16:56:10 GMT

Hi rebelinux,

set zLink to:

"<a href='https://${here/manageIp}:2381' target='_'>HP Management Agent</a> <a href='https://${here/hw/cards/cpqSm2Cntlr0/ipaddress}' target='_'>iLO Board</a>"

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 02 Sep 2010 06:00:27 GMT

Hi Everybody,

Currently I'm making tests for a group of HP Proliant servers with the 3.0.1 zenoss version. I'm followed the next steeps:

For the modeler

1. Install HP Proliant and Advanced Device Details ZenPacks with the GUI (web administration), and I restarted the zeoctl service.

2. In the device I have added the modeler plugins and saved.

3. (re)Model device (after restarting the zenoss service)

4. The device show correctly the new components

For the Collector, it's the problem, when I go to Add the "Bind Template" (action button in the bottom of device administration) don't appear the cpq* and HP* entries. Only shows the selected Device (/server/windows)

What am I doing wrong?

Thanks for all.

Regards,

Alex.

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 02 Sep 2010 14:03:21 GMT

Hi alexgm,

it's NOT necessary to bind components templates to device.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 03 Sep 2010 06:18:02 GMT

Hi Egor,

Thanks for help me. I'm a newbie and only was following the instructions of http://community.zenoss.org/thread/11008?start=0&tstart=0 jbose post

It's a great pack.

Regards,

Alex.

RE: HP ProLiant Monitor

community@zenoss.org — Sat, 04 Sep 2010 00:50:14 GMT

any plans to add reports on this zenpack like Storage controller ROM version, ILO ROM Version or Server BIOS Version

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 05 Sep 2010 17:46:42 GMT

im trying to create a custom report that show the ilo rom version and the storage rom version. Can you show me how to access this variables?

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 08 Sep 2010 00:55:54 GMT

I made a zlink that check the hp warranty of servers. It depends of a plug-in that collects the serial number and the productid from the server. See the plug-in:

from Products.DataCollector.plugins.CollectorPlugin import SnmpPlugin, GetMap

class HPProductMap(SnmpPlugin):
"""Map mib elements from HP to retreive Serial & Product ID number.
"""

maptype = "HPProductMap"

    snmpGetMap = GetMap({
        '.1.3.6.1.4.1.232.2.2.2.5.0' : 'setHWSerialNumber',
        '.1.3.6.1.4.1.232.2.2.2.6.0' : 'setHWTag',
        })

    def process(self, device, results, log):
        """collect snmp information from this device"""
        log.info('processing %s for device %s', self.name(), device.id)
        getdata, tabledata = results
        om = self.objectMap(getdata)
        return om

it can be save in:

/usr/local/zenoss/zenoss/Products/DataCollector/plugins/zenoss/snmp/HPProductMap.py

and you have to add it as a modeler on the server class.

And the Zlink:

<a href='http://h20000.www2.hp.com/bizsupport/TechSupport/WarrantyResults.jsp?lang=en&cc=us&prodSeriesId=366505&prodTypeId=329290&sn=${here/getHWSerialNumber}&pn=${here/getHWTag}&country=PR&nickname=&find=Display+Warranty+Information+%C2%BB' target='_'>HP Warranty Check</a>

You have to change the country to match your ubication.

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 13 Sep 2010 15:39:50 GMT

Hi rebelinux,

i've added 'HP iLO Boards' and 'HP Storage Controllers' reports and 'TAG' property modelling to this ZenPack.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 13 Sep 2010 17:58:51 GMT

you are the best!!!!!!

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 13 Sep 2010 18:50:54 GMT

i install and test this version and the reports doesn’t appear in the report class. i have to manually copy the rpt files to the directory $ZENHOME/Products/ZenReports/reports and execute

python ReportLoader.py --force to see its.

Any advice?

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 14 Sep 2010 18:59:49 GMT

Hi rebelinux,

look under 'Device Reports'.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 14 Sep 2010 19:32:21 GMT

I think the zenpack installation process didn’t install the report properly.

i have to manually copy it to $ZENHOME/Products/ZenReports/reports and run ReportLoader.py. after that i can see the reports under Device Reports.

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 Sep 2010 05:11:45 GMT

Great Pack - I am extremely impressed with its features. Quick question -

We are gettting the following event every for every single hp server we have with that has a dual nic card.

"threshold of status exceeded: current status other"

The device listed in the event is simply the unused nic port. Is their anyway to suppress this event since its not actionable?

Thanks

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 Sep 2010 14:47:05 GMT

Hi ebailey,

set 'Monitor' property of this nic to 'False'.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 Sep 2010 18:09:12 GMT

I have alot's of hp proliant dl380 g5 and dl385 and I see its doesnt show memorymodules components when the servers have installed windows server 2008.

RE: HP ProLiant Monitor

community@zenoss.org — Sat, 18 Sep 2010 06:43:03 GMT

I cant figure how to do that with one nic and I am not sure I would want to anyway. I have several hundred servers and I would hate to make this manual change for every server. Is thier someway to configure the device template or event class to not alert when status is other?

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 06 Oct 2010 10:02:29 GMT

This is a very useful ZenPack. I have deployed it in an environment with HP Proliant servers running Red Hat, CentOS and SuSE. There was a problem with the one system running SuSE in that the modeler crashed when handling om.setOSProductKey. The line:

om.setOSProductKey = om.setOSProductKey.split('-', 1)[1].strip()

produces an error because in this system there is no '-' in the attribute.

In my copy of modeler/plugins/community/snmp/HPDeviceMap.py I have replaced:

elif re.search(r'SuSE', om.setOSProductKey, re.I): om.setOSProductKey = om.setOSProductKey.split('-', 1)[1].strip() om.setOSProductKey = "Novell %s %s" %(om.setOSProductKey, om._OSVer) manuf = "Novell"

with

elif re.search(r'SuSE', om.setOSProductKey, re.I): if '-' in om.setOSProductKey: om.setOSProductKey = om.setOSProductKey.split('-', 1)[1].strip() om.setOSProductKey = "Novell %s %s" %(om.setOSProductKey, om._OSVer) manuf = "Novell"

The modeler now runs and sets setOSProductKey to :

Novell SuSE Linux Enterprise Server 10SP3

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 07 Oct 2010 19:03:05 GMT

Do you know how to get CPU and Memory usage graph with these components ? As the default CpuPercentProcessoTim, memoryPagesPerSec, and memoryAvailableKBytes seems not to be available with HP SMI ?

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 07 Oct 2010 19:09:34 GMT

CPU and memory usage in HP SIM depend from Host Operating System. I want leave this ZenPack compatible with any OS.

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 07 Oct 2010 19:32:50 GMT

Thanks, that's why I asked on WMI Data source page This package also work on ILO interfaces which is not correlated to the OS so that's great.

However I asked about the best practice on where to create device, because using WMI classes and then adding this zenpacks does not seem to work well graphs are lacking). See details there:

http://community.zenoss.org/docs/DOC-3392#cf

Thanks for your work and advice.

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Oct 2010 13:01:16 GMT

I am running v2.0 of this Zenpack and am testing 2.1 on another instance (Zenoss 2.5.2). With 2.1, I have modeled my DL360 G5 and the iLO is not showing up in the Expansion Cards.

Is there an order required for the Collector Plugins?

Anyone else experiencing this with 2.1?

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Oct 2010 19:02:43 GMT

yes, order is important. Put HPHardDiskMap, HPLogicalDiskMap and HPExpansionCardMap collector plugins to the end of zCollectorPlugins list.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Oct 2010 19:38:09 GMT

That did it, Egor! THANK YOU!

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Oct 2010 21:59:00 GMT

Im running a fresh install of 302 on openSuse 11.3 and trying to set up monitoring an HPDL380 G5 running W2008. I added the zenpacks, one at a time, stopping and starting zenoss each time, and modeling the device each time after adding the new plugins. But none of the new components show up. Where are the new pages supposed to show up? What am I doing wrong?

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Oct 2010 22:15:01 GMT

install HP Insight Management Agents on monitored system

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 14 Oct 2010 18:44:57 GMT

Hi Egor,

I already create some thresholds that inform of errors occurring on hard disk (notreadyerr, hardwareerror, hardreaderrs & hatdwriteerrs, etc.), also create the transforms to produce a more readable output. It should be a cool feature for your zenpack.

##########################################################################################

import re

match = re.search('threshold of diskerror [^:]+: current value ([\d\.]+)', evt.message)

if match and device:

evt.summary = "Hard Disk with Hardware or Not Ready Erros: Future Replacement Posible"

import re

match = re.search('threshold of harderror [^:]+: current value ([\d\.]+)', evt.message)

if match and device:

evt.summary = "Hard Disk with Write or Read Erros: Future Replacement Posible"

##########################################################################################

import re

match = re.search('threshold of cpqDaPhyDrv status', evt.message)

if match and device:

if evt.compStatus == 3.0:

evt.summary = "Hard Disk Failure: Replace Failed Hard Disk"

evt.severity = 5

elif evt.compStatus == 4.0:

evt.summary = "Hard Disk Predictive Failure: Check Disk Errors"

evt.severity = 4

##########################################################################################

import re

match = re.search('threshold of cpqDaLogDrv status', evt.message)

if match and device:

if evt.compStatus == 2:

evt.summary = "Logical Volume Status: Volume OK"

evt.severity = 2

elif evt.compStatus == 3:

evt.summary = "Logical Volume Status: Volume Failed"

evt.severity = 5

elif evt.compStatus == 4:

evt.summary = "Logical Volume Status: Volume UN-configured"

evt.severity = 2

elif evt.compStatus == 5:

evt.summary = "Logical Volume Status: Volume Recovering"

evt.severity = 3

elif evt.compStatus == 6:

evt.summary = "Logical Volume Status: Volume Ready Rebuild"

evt.severity = 3

elif evt.compStatus == 7:

evt.summary = "Logical Volume Status: Volume Rebuilding"

evt.severity = 3

else:

evt.summary = "Logical Volume Status: Unknown"

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 29 Oct 2010 11:54:03 GMT

Hi Egor,

Firstly I would like to echo other peoples comments on what a great ZenPack this is. I hope to use it to drive changes and revolutionize monitoring at my workplace.

I have a couple of questions though if I may :-

Firstly I have got the 'TAG' property modelling working (I have confirmed this by using the warranty check ZLink as described earlier in this thread)

However in both of my 2 test systems, (one running 2.5.2 and one running 3.0.2) and the TAG property does not show in the GUI (Status Tab in 2.5.2 and Overview item in 3.0.2), even though it is being collected. Is there a simple tweak I can use to make this appear?

Also we have been seeing issues with the Array Accelerators on a number of our servers and I would like to be able to monitor this metric as well.

From the CPQIDA-MIB I have been able to see these 2 particular variables.

cpqDaAccelStatus 1.3.6.1.4.1.232.3.2.2.2.1.2 (this is the overall Array Status)
cpqDaAccelBattery 1.3.6.1.4.1.232.3.2.2.2.1.6 (this is the Array Battery Status specifically)

What would be the best way for me to get this information added to my system (and alert depending on the value returned)?

I guess this would best fit under Expansion cards, unless anyone has any better suggestions. Could it be as a sub-section of the array controller?

Thanks

Paul

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 08 Nov 2010 10:28:46 GMT

Hi,

I have installed the zenpack and all looks good, I do have one question:

1. What are LWrites and why are they negative?

Thanks,

RE: HP ProLiant Monitor

community@zenoss.org — Sat, 13 Nov 2010 17:48:39 GMT

Hi Egor,

With the 2.2 version of your zenpack now i can see the memory module on the win2008 servers. thanks

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 19 Nov 2010 16:14:51 GMT

Has anyone been able to figure out how to create a zLink from the iLO IP address available in the 2.2 version of this AMAZING zenpack?

The IP Address for each iLO board is shown in the iLO Report so I would assume this data is available to use as a zLink. Any thoughts?

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 19 Nov 2010 16:19:11 GMT

I did some hacking around with the warranty check link above and you don't need the product number as mentioned above. I use the following link without the product number using the serial number only. It works flawlessly on all my servers.

<a href='http://h20000.www2.hp.com/bizsupport/TechSupport/WarrantyResults.jsp?lang=en&cc=us&prodSeriesId=366505&prodTypeId=329290&sn=${here/getHWSerialNumber}&country=US&nickname=&find=Display+Warranty+Information+%C2%BB' target='_'>HP Warranty Check</a>

In addition to the Warranty Check zLink I also have a link the the HPSM homepage. This link assumes the device name is in DNS. If it isn't in DNS you could use the manage ip field instead.:

<a href='https://${here/getId}:2381' target='_blank'>HP System Management Homepage</a>

And finally I am still trying to figure out how to pull the iLO IP address from the DMD so I can create a zLink to the iLO webpage:

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 19 Nov 2010 16:54:47 GMT

http://community.zenoss.org/docs/DOC-3394#comment-2520

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 19 Nov 2010 17:20:28 GMT

Event transform for cpqDaAccelStatus:

import re
match = re.search('threshold of cpqDaCntlr status', evt.message)
if match and device:
    if evt.compStatus == 1.0:
            evt.summary = "Unknown Raid Array Condition"
        evt.severity = 2
    elif evt.compStatus == 3.0:
        evt.summary = "Raid Array Status: Degradated"
        evt.severity = 4
    elif evt.compStatus == 4.0:
        evt.summary = "Raid Array Status: Failed"
        evt.severity = 5

RE: HP ProLiant Monitor

community@zenoss.org — Sat, 20 Nov 2010 01:04:49 GMT

Nice one, thanks for that. Is there an easy way of getting this showing in the Hardware Tab at all?

I would love to see the status of the following system attributes :-

cpqDaAccelStatus
cpqDaAccelBattery

Am i trying to do too much, it's just that we have a major problem with write cache batteries in the 1000's of servers that I monitor and I would like to see if I can see status proactively before the services performance is degraded too much by the failure.

Thanks

Paul

RE: HP ProLiant Monitor

community@zenoss.org — Sat, 20 Nov 2010 04:04:51 GMT

bigegor add support for cpqDaAccelStatus on HPMON 2.2. You only have to create a event transform that display the current status of cpqDaAccelBattery


     cpqDaAccelBattery OBJECT-TYPE
        SYNTAX  INTEGER
        {
            other(1),
            ok(2),
            recharging(3),
            failed(4),
            degraded(5)
        }
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
            "Array Accelerator Board Battery Status.

            This monitors the status of each battery pack on the board.  The
            batteries can only recharge when the system has power applied.   

            The following values are valid:

            Other (1)       
              Indicates that the instrument agent does not recognize
              battery status.  You may need to update your software.

            Ok (2)
              Indicates that a particular battery pack is fully charged.

            Charging (3)    
              The battery power is less than 75%.  The Drive Array
              Controller is attempting to recharge the battery.  A
              battery can take as long as 36 hours to fully recharge.  
              After 36 hours, if the battery has not recharged, it is 
              considered failed. 

            Failed (4) 
              The battery pack is below the sufficient voltage level and 
              has not recharged in 36 hours.  Your Array Accelerator board 
              needs to be serviced.  

            Degraded (5)    
              The battery is still operating, however, one of the batteries 
              in the pack has failed to recharge properly.  Your Array 
              Accelerator board should be serviced as soon as possible."  
        ::= { cpqDaAccelEntry 6 }

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 24 Nov 2010 20:03:11 GMT

I create a threshold in cpqDaCntlr named accelStatus and add the accelStatus data source on it.

Also create the event transform on /Change/Set/Status

import re
match = re.search('threshold of accelStatus exceeded', evt.message)
if match and device:
    if evt.compStatus == 1.0:
        evt.summary = "Unknown Raid Battery Pack Status: You may need to update your software"
        evt.severity = 2
    elif evt.compStatus == 3.0:
        evt.summary = "Raid Battery Pack Charging: The Drive Array Controller is attempting to recharge the battery"
        evt.severity = 3
    elif evt.compStatus == 4.0:
        evt.summary = "Raid Battery Pack Failed: The battery pack is below the sufficient voltage level"
        evt.severity = 5
    elif evt.compStatus == 5.0:
        evt.summary = "Raid Battery Pack Degradated: Your Array Accelerator board should be serviced as soon as possible."
        evt.severity = 5

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 24 Nov 2010 20:09:08 GMT

your are right. But in some cases HP requires the to variables SerialNumber & ProductNumber. With only SerialNumer some of our new servers didnt show the correct warranty info.

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 15 Dec 2010 15:26:46 GMT

I have a few hundred servers that I would love to monitor with this ZenPack.

Is there an easy way to get the required Collector Plugins onto each new host in 1 go, other than dragging and dropping the "community.snmp.HP*" entries from the right hand list to the left hand list for each and every server? Otherwise I might get finger strain !! I did try to add the collectors plugins to the /Device/Server level template but didn't have any success.

Thanks again for your help with this ZenPack

Paul

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 Dec 2010 20:18:26 GMT

Great ZenPack, thanks! One thing I find missing is the ability to see reundancy (specifically, how do I know my RAID1 is still ok?)

I can see this in my HP Agent page, but not with Zenoss, even with this great ZenPack. Am I missing something?

RE: HP ProLiant Monitor

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

can you see Logical Disk components after modeling?

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 Dec 2010 21:43:33 GMT

No I can't. I can see alot of new things, but there is no logical disk component.

The "instructions" say to put them at the end of the list when adding modeler plugins, but I can't manage to place it in the slot I want. It puts itself where it wants. Or am I missing a MIB/ZenPack?

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 Dec 2010 21:52:58 GMT

I have found recently if you drag the 3 plugins to the "bottom" of the list as is required, and then drag the others and put them before the 3 bottom ones then it seems to work, was after some trial and error as initially I had the same problem, but have mastered it now Just need to work out how to do it for 100's of servers now.

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 Dec 2010 22:02:31 GMT

Well look at that, I can't drag down the three that need to be dragged down, but I cn drag up the other 50 :-)

Thanks, that worked and I get my extra info.

What do I do with iLo devices now? How can I get any info out of them? (is this even possible, or useful?)

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 20 Dec 2010 13:03:24 GMT

Hi,

Does anyone know what LWrites are and why are they negative?

Thanks

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 30 Dec 2010 10:19:03 GMT

Hi Egor,

I have some G6 / G7 servers and the Disk controller is coming up as Unknown Array Controller (39) it is a SmartArray P410i but having a look at the MIB provided by this ZenPack there is no entry for value 39 (they stop at 26).

I have been able to get a more recent MIB from :-

http://h18000.www1.hp.com/products/servers/management/hpsim/mibkit.html

I looked at MIB Kit Version 8.60 as this was the latest (I downloaded the Windows version but I suspect the Linux version is the same except for the archive type).

Having looked at it the content is indeed expanded at the cpqDaCntlrModel section (OID 1.3.6.1.4.1.232.3.2.2.1.1.2).

I have tried to import the new MIB as follows (the MIB was copied to /opt/zenoss/share/mibs/site first):-

This is just a snippet of the pages and pages of information relating to all the MIBs installed.

[zenoss@pvzenhubhh1001 site]$ pwd
/opt/zenoss/share/mibs/site
[zenoss@pvzenhubhh1001 site]$ zenmib run -v 10 CPQIDA-MIB

2010-12-30 09:58:03,171 INFO zen.ZenMib: Found 1 MIBs to import.
2010-12-30 09:58:03,171 DEBUG zen.ZenMib: Attempting to load /opt/zenoss/share/mibs/site/CPQIDA-MIB
2010-12-30 09:58:03,171 WARNING zen.ZenMib: MIB definition CPQIDA-MIB found in /opt/zenoss/share/mibs/site/CPQIDA-MIB is already loaded at /.
2010-12-30 09:58:03,172 WARNING zen.ZenMib: Unable to find a file that defines CPQHOST-MIB
2010-12-30 09:58:03,172 DEBUG zen.ZenMib: Running smidump --keep-going --format python --preload /opt/zenoss/share/mibs/ietf/RFC1155-SMI --preload /opt/zenoss/share/mibs/ietf/RFC-1215 --preload /opt/zenoss/share/mibs/ietf/RFC1213-MIB --preload /opt/zenoss/share/mibs/ietf/RFC-1212 /opt/zenoss/share/mibs/site/CPQIDA-MIB
Traceback (most recent call last):
File "/opt/zenoss/lib/python2.6/logging/__init__.py", line 773, in emit
stream.write(fs % msg.encode("UTF-8"))
UnicodeDecodeError: 'utf8' codec can't decode byte 0x92 in position 319: unexpected code byte
2010-12-30 09:58:03,194 DEBUG zen.Relations: obj /zport/dmd/Mibs/mibs/CPQIDA-MIB already exists on /zport/dmd/Mibs/mibs
2010-12-30 09:58:03,333 DEBUG zen.ZenMib: Committing a batch of objects
2010-12-30 09:58:03,382 DEBUG zen.ZenMib: Committing a batch of objects
2010-12-30 09:58:03,382 INFO zen.ZenMib: Parsed 0 nodes and 0 notifications from CPQIDA-MIB
2010-12-30 09:58:03,382 DEBUG zen.ZenMib: Committing a batch of objects
2010-12-30 09:58:03,382 INFO zen.ZenMib: Loaded MIB CPQIDA-MIB into the DMD
2010-12-30 09:58:03,382 INFO zen.ZenMib: Loaded 1 MIB file(s)

If I remove the old MIB and try and install this MIB I lose all of the information previously held, am I doing something wrong?

I am using Zenoss 3.0.3 with AdvDetails 2.5 and HPMON 2.2 if this helps.

Thanks

Paul

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 06 Jan 2011 18:45:53 GMT

I posted in the forum before I knew better

http://community.zenoss.org/message/54253#54253

That I would love to un-monitor the interfaces but I can't the option is grayed out.

Is there a dependency somewhere I've mised

WaltB

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 18 Jan 2011 17:50:32 GMT

Hi all,

Firstly thanks for the new version (it means I can now see all of my storage controllers). Now I am trying to schedule a report for firmware versions of Storage Controllers.

/opt/zenoss/bin/reportmail -u "http://172.16.4.235:8080/zport/dmd/reports#reporttree:.zport.dmd.Reports.Device%20Reports.HP%20ProLiant%20Reports.Storage%20Controllers" -U reporting -p reporting -s "Firmware Versions BETA report" -f FROMADDRESS -a RECIPIENT.

This gives me the raw code from the main page.(along with the button text at the bottom).

Is there a way I can get this to export the data to a .csv (there is an export option in the page itself which will save the .csv file), and then mail the .csv file to the recipient(s)

Sorry to sound thick.

Thanks

Paul

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 26 Jan 2011 12:15:01 GMT

Hi Everyone

I've installed this Zenpack on my zenoss version 3.0.3 and I loss my Bind Templates feature , when i click on bind templates I have see this error :

The server reported the following error:

NameError name 'InitializeClass' is not defined

The system has encountered an error. Please reload the page.

At the next I trace my prolblem in logfiles and found this :

2011-01-26T15:42:51 ERROR extdirect name 'InitializeClass' is not defined
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenUtils/extdirect/router.py", line 128, in _processDirectRequest
    result = _targetfn(**data)
File "/opt/zenoss/Products/Zuul/routers/device.py", line 475, in getBoundTemplates
    for template in templates:
File "/opt/zenoss/Products/Zuul/facades/devicefacade.py", line 358, in _getBoundTemplates
    for template in obj.getAvailableTemplates():
File "/opt/zenoss/Products/ZenModel/Device.py", line 2158, in getAvailableTemplates
    if isinstance(self, t.getTargetPythonClass()) ]
File "/opt/zenoss/Products/ZenModel/RRDTemplate.py", line 276, in getTargetPythonClass
    return importClass(cname)
File "/opt/zenoss/Products/ZenUtils/Utils.py", line 361, in importClass
    __import__(modulePath, globals(), locals(), classname)
File "/opt/zenoss/ZenPacks/ZenPacks.community.HPMon-2.2.71.egg/ZenPacks/community/HPMon/HPFan.py", line 44, in <module>
    InitializeClass(HPFan)
NameError: name 'InitializeClass' is not defined

Dose anyone knows how can I fix this issue ?

Thanks

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 26 Jan 2011 12:42:15 GMT

Hi all,

We found this in our install as well.

We updated the file /opt/zenoss/ZenPacks/ZenPacks.community.HPMon-2.2.71.egg/ZenPacks/community/HPMon/HPFan.py, adding the following line:

“from HPComponent import *”

This line is present in other modules in the same directory. This fixed our issue and allowed us to bind the templates. I have been meaning to mention this for a few days, sorry for the delay.

Paul

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 26 Jan 2011 13:36:48 GMT

Yeahhhh.

Thanks

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 26 Jan 2011 19:38:47 GMT

Thanks, fixed in git.

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 24 Feb 2011 14:14:56 GMT

Egor,

As always thank you for the great work on this Zenpack.

I have a question about querying for Serial Numbers. It seems when I pull the Serial Number for our HP Blades (BL460c G1s) the SN returned is that of the chassis.

Is there anything I can do to address this on my end or do I just need to be patient for an update?

Thanks,

John

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 24 Feb 2011 21:07:30 GMT

Hi John,

do you know Serial Numbers OID for HP Blades?

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 25 Feb 2011 13:44:52 GMT

I think this is what you're looking for as it returns the correct serial number.

cpqSiSysSerialNum 1.3.6.1.4.1.232.2.2.2.1 DisplayString read-only mandatory

I get the same serial number from this OID as well:

cpqSiSysServiceNum 1.3.6.1.4.1.232.2.2.2.5 DisplayString read-only mandatory

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 27 Feb 2011 20:19:17 GMT

HI John,

cpqSiSysSerialNum 1.3.6.1.4.1.232.2.2.2.1

it already used in this ZenPack. Add community.snmp.HPDeviceMap collector plugin to zCollectorPlugins list.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 28 Feb 2011 13:35:53 GMT

that plugin is already in the zCollectorPlugins list.

it looks like this:

zenoss.snmp.NewDeviceMap

zenoss.snmp.DeviceMap

HPDeviceMap

communiity.wmi.InterfaceMap

zenoss.wmi.WinServiceMap

community.wmi.RouteMap

community.wmi.ProcessorMap

community.wmi.NewDeviceMap

community.wmi.ProductMap

community.wmi.FileSystemMap

community.wmi.ProcessMap

community.wmi.WinServiceMap

community.wmi.DeviceMap

HPCPUMap

zenoss.protscan.IpServiceMap

community.snmp.HPCPUMap

community.snmp.HPDaCntrlrMap

community.snmp.HPDaPhyDrvMap

community.snmp.HPDaLogDrvMap

community.snmp.HPDeviceMap

community.snmp.HPSsChassisMap

community.snmp.HPMemoryModuleMap

community.snmp.HPFanMap

community.snmp.HPScsiLogDrvMap

community.snmp.HPScsiPhyDrvMap

community.snmp.HPSm2CntlrMap

community.snmp.HPNicMap

community.snmp.HPTemperatureSensorMap

community.snmp.HPScsiCntlrMap

community.snmp.HPSasLogDrvMap

community.snmp.HPSasPhyDrvMap

community.snmp.HPSashbaMap

community.snmp.HPIdeLogicalDriveMap

community.snmp.PowerSupplyMap

community.snmp.HPFcTapeCntlrMap

community.snmp.HPIdeControllerMap

I removed the redundant HPDeviceMap and HPCPUMap and remodeled but the Serial Number reported is still that of the chassis.

Any other ideas?

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 01 Mar 2011 22:37:32 GMT

1. READ installation note of this ZenPack (chapter 4).

2. remove unnecessary plugins (it's a bad practice to put all plugins together, you will get some unexpected results)

3. dump value of 1.3.6.1.4.1.232.2.2.2.1 OID with snmpwalk

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 02 Mar 2011 14:19:52 GMT

Egor,

You are as we like to say in the USA 'the man'.

Removing all of the plugins EXCEPT the community.snmp.HP* plugins seemed to fix the problem.

Seems that by default when a new server is added to this device class these plugins are added. I'll have to look into this and modify plugins for the whole device class.

Thanks again,

John

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 02 Mar 2011 15:41:35 GMT

One more question. I thought we needed the community.wmi.* plugins so we could do things such as monitor the OS filesystem disk size/usage.

Should I expect the same functionality from this Zenpack or is this a situation where combining plugins is acceptable?

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 02 Mar 2011 19:27:13 GMT

you can combine plugins from core and different ZenPacks, but you must prevent to use multiple plugins for the same components type o.e. zenoss.snmp.DeviceMap, HPDeviceMap,community.wmi.DeviceMap, community.wmi.NewDeviceMap, community.snmp.HPDeviceMap all trying to set Device Serial Number.

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 05 Apr 2011 20:33:10 GMT

Hello Egor,

I'm trying to figure out why some multi-CPU servers of ours are reporting the incorrect number of CPUs in the hardware tab and was hoping you could provide some insight.

I've peeked at the OIDs in HPCPUMap.py and they seem to return sane information. For example:

[zenoss@monitor: ~] PROD $ snmpwalk -v2c -c<commstring> <Device> .1.3.6.1.4.1.232.1.2.2.1.1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.1.0 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.1.1 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.1.2 = INTEGER: 2

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

SNMPv2-SMI::enterprises.232.1.2.2.1.1.2.0 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.2.1 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.2.2 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.2.3 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.3.0 = STRING: "Intel Xeon MP"

SNMPv2-SMI::enterprises.232.1.2.2.1.1.3.1 = STRING: "Intel Xeon MP"

SNMPv2-SMI::enterprises.232.1.2.2.1.1.3.2 = STRING: "Intel Xeon MP"

SNMPv2-SMI::enterprises.232.1.2.2.1.1.3.3 = STRING: "Intel Xeon MP"

SNMPv2-SMI::enterprises.232.1.2.2.1.1.4.0 = INTEGER: 2400

SNMPv2-SMI::enterprises.232.1.2.2.1.1.4.1 = INTEGER: 2400

SNMPv2-SMI::enterprises.232.1.2.2.1.1.4.2 = INTEGER: 2400

SNMPv2-SMI::enterprises.232.1.2.2.1.1.4.3 = INTEGER: 2400

SNMPv2-SMI::enterprises.232.1.2.2.1.1.5.0 = INTEGER: 11

SNMPv2-SMI::enterprises.232.1.2.2.1.1.5.1 = INTEGER: 11

SNMPv2-SMI::enterprises.232.1.2.2.1.1.5.2 = INTEGER: 11

SNMPv2-SMI::enterprises.232.1.2.2.1.1.5.3 = INTEGER: 11

SNMPv2-SMI::enterprises.232.1.2.2.1.1.6.0 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.6.1 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.6.2 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.6.3 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.7.0 = INTEGER: 1066

SNMPv2-SMI::enterprises.232.1.2.2.1.1.7.1 = INTEGER: 1066

SNMPv2-SMI::enterprises.232.1.2.2.1.1.7.2 = INTEGER: 1066

SNMPv2-SMI::enterprises.232.1.2.2.1.1.7.3 = INTEGER: 1066

SNMPv2-SMI::enterprises.232.1.2.2.1.1.8.0 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.8.1 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.8.2 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.8.3 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.9.0 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.9.1 = INTEGER: 2

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

SNMPv2-SMI::enterprises.232.1.2.2.1.1.9.3 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.10.0 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.10.1 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.10.2 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.10.3 = INTEGER: 2

SNMPv2-SMI::enterprises.232.1.2.2.1.1.15.0 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.15.1 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.15.2 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.15.3 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.20.0 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.20.1 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.20.2 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.20.3 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.21.0 = INTEGER: 4800

SNMPv2-SMI::enterprises.232.1.2.2.1.1.21.1 = INTEGER: 4800

SNMPv2-SMI::enterprises.232.1.2.2.1.1.21.2 = INTEGER: 4800

SNMPv2-SMI::enterprises.232.1.2.2.1.1.21.3 = INTEGER: 4800

SNMPv2-SMI::enterprises.232.1.2.2.1.1.22.0 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.22.1 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.22.2 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.22.3 = INTEGER: 0

SNMPv2-SMI::enterprises.232.1.2.2.1.1.23.0 = STRING: "Xeon MP"

SNMPv2-SMI::enterprises.232.1.2.2.1.1.23.1 = STRING: "Xeon MP"

SNMPv2-SMI::enterprises.232.1.2.2.1.1.23.2 = STRING: "Xeon MP"

SNMPv2-SMI::enterprises.232.1.2.2.1.1.23.3 = STRING: "Xeon MP"

SNMPv2-SMI::enterprises.232.1.2.2.1.1.24.0 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.24.1 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.24.2 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.24.3 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.25.0 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.25.1 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.25.2 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.25.3 = INTEGER: 4

SNMPv2-SMI::enterprises.232.1.2.2.1.1.26.0 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.26.1 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.26.2 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.26.3 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.27.0 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.27.1 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.27.2 = INTEGER: 1

SNMPv2-SMI::enterprises.232.1.2.2.1.1.27.3 = INTEGER: 1

[zenoss@monitor: ~] PROD $ snmpwalk -v2c -c?<commstring> <device> .1.3.6.1.2.1.25.3.3.1

(there are 16 cores)

HOST-RESOURCES-MIB::hrProcessorFrwID.2 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.3 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.4 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.5 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.6 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.7 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.8 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.9 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.10 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.11 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.12 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.13 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.14 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.15 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.16 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorFrwID.17 = OID: SNMPv2-SMI::zeroDotZero

HOST-RESOURCES-MIB::hrProcessorLoad.2 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.3 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.4 = INTEGER: 1

HOST-RESOURCES-MIB::hrProcessorLoad.5 = INTEGER: 3

HOST-RESOURCES-MIB::hrProcessorLoad.6 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.7 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.8 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.9 = INTEGER: 2

HOST-RESOURCES-MIB::hrProcessorLoad.10 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.11 = INTEGER: 1

HOST-RESOURCES-MIB::hrProcessorLoad.12 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.13 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.14 = INTEGER: 2

HOST-RESOURCES-MIB::hrProcessorLoad.15 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.16 = INTEGER: 0

HOST-RESOURCES-MIB::hrProcessorLoad.17 = INTEGER: 4

This is a Windows machine using both WMI and HP collector plugins. Here's the list:

c.wmi.interfacemap

c.wmi.winservicemap

c.wmi.processormap

c.wmi.productmap

c.wmi.filesystemmap

c.wmi.diskdrivemap

c.wmi.processmap

zenoss.portscan.ipservicemap

c.snmp.hp*

Do you have any idea why there is only 1 CPU being reported back?

Thanks,

John

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 05 Apr 2011 20:44:32 GMT

Hi,

remove c.wmi.processormap plugin.

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 05 Apr 2011 20:58:44 GMT

That was the fix. You're help is invaluable Egor. I owe you at least 2 beers now.

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Apr 2011 15:43:51 GMT

Egor,

I notice in the image you provide for the Zenpack you have an MSA1000 that's found in the Expansion Cards section of the hardware tab. We have MSA2xxx's in use and were hoping they would also be found in the hardware tab.

The collector plugins I mentioned in a previous post are still in use and I made sure the necessary collector plugins were at the end of the list (harddiskmap, logicaldiskmap, expansioncardmap).

Do you know if this is something we could fix on our end? Could it be the OID is missing or would I need to submit a patch?

Thanks,

John

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Apr 2011 18:04:30 GMT

Hi John,

first of all, test this OID: 1.3.6.1.4.1.232.16.2.2.1.1 against your server with MSA2xxx.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Apr 2011 18:26:53 GMT

Thanks for the prompt reply Egor.

[zenoss@<monitor>: ~] PROD $ snmpwalk -v2c -c<commnity> <device> 1.3.6.1.4.1.232.16.2.2.1.1

SNMPv2-SMI::enterprises.232.16.2.2.1.1 = No Such Object available on this agent at this OID

The CPQFCA-MIB is loaded in Zenoss.

In case it matters, we are connected to the MSA via a HP FC1242SR 4Gb PCI-e DC HBA which is in the expansion cards section of the Hardware tab.

Thanks again,

John

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 26 Apr 2011 20:03:41 GMT

Egor,

Any other ideas on how I can continue to troubleshoot this and figure out why our MSAs aren't showing up?

Thanks,

John

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 27 Apr 2011 22:57:49 GMT

Hi Egor (again!),

I'm trying to pull the FWRev for expansion cards on some of my HP machines using your Zenpack. For some reason I'm getting an attribute error when I try to do something like:

for c in dev.hw.cards():

print c.FWRev

I can see in Zope that FWRev is a property of this card, and when I'm in zendmd I can tab out most of the attritutes but not FWRev.

Any idea why I'm having a problem retrieving this?

Many thanks,

John

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 27 Apr 2011 23:00:02 GMT

I was finally able to retrieve it using card.getProperty('FWRev')

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 19 May 2011 20:41:03 GMT

Hi,

anyone with this kind of errors? now i cant see the temperature info

------
2011-05-19T16:15:43 ERROR Zope.SiteErrorLog 1305836143.010.862560064914 
http://utg-zenoss-01.agm.su:8080/zport/dmd/Devices/Server/Windows/Hp%20Servers/Security%20Servers/devices/
utg-nasuac-01/device_router
Traceback (innermost last):
  Module ZPublisher.Publish, line 127, in publish
  Module ZPublisher.mapply, line 77, in mapply
  Module ZPublisher.Publish, line 47, in call_object
  Module Products.ZenUtils.extdirect.zope.router, line 24, in __call__
  Module Products.ZenUtils.extdirect.router, line 88, in __call__
  Module Products.ZenUtils.jsonutils, line 152, in json
  Module json, line 230, in dumps
  Module json.encoder, line 367, in encode
  Module json.encoder, line 309, in _iterencode
  Module json.encoder, line 275, in _iterencode_dict
  Module json.encoder, line 309, in _iterencode
  Module json.encoder, line 275, in _iterencode_dict
  Module json.encoder, line 309, in _iterencode
  Module json.encoder, line 275, in _iterencode_dict
  Module json.encoder, line 306, in _iterencode
  Module json.encoder, line 204, in _iterencode_list
  Module json.encoder, line 309, in _iterencode
  Module json.encoder, line 275, in _iterencode_dict
  Module json.encoder, line 306, in _iterencode
  Module json.encoder, line 204, in _iterencode_list
  Module json.encoder, line 309, in _iterencode
  Module json.encoder, line 275, in _iterencode_dict
  Module json.encoder, line 317, in _iterencode
  Module json.encoder, line 323, in _iterencode_default
  Module json.encoder, line 344, in default
TypeError: <bound method HPTemperatureSensor.state of <HPTemperatureSensor at 
/zport/dmd/Devices/Server/Windows/Hp Servers/Security Servers/devices/utg-nasuac-01
/hw/temperaturesensors/ambient1>> is not JSON serializable
------

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 11 Jul 2011 11:04:06 GMT

Hi - I'm looking into using this excellent ZenPack for monitoring our HP servers. Would it be possible to add the ilo license key to the next version (SNMPv2-SMI::enterprises.232.9.2.2.31.0 = STRING: "34QTN-2WT7B-3LBYT-XXXX-XXXXX")? This would be really useful for auditing purposes.

Cheers,

Ian

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Jul 2011 08:32:21 GMT

Hello,

First, thank you for this excellent zenpack ! It's really useful for us, here. That said, I have some problem using it...

1) I installed the Zenpack correctly, it worked, no issues but for some reasons I wanted to remove it and re-install it. Ever since I've done that, Zenoss takes toooo much time to restart. Is it because I had a machine monitored using this Zenpack ? When reinstalling the zenpack an error affected to this machine showed up saying there was an issue installing the zenpack (broken pipe), that said.. the machine is still monitored with no issues (haven't tried to remodel though). Any idea how to resolve this ?

2) When I set a network interface to DOWN, I see no event and its status goes to Unknown. I suspect the reason is that there were no traps emitted. Any idea how to set up traps (trapsink in snmpd.conf correctly configured...) ?

Thanks for your help

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Jul 2011 21:13:51 GMT

Thanks Ian, i'll add this to the next release.

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Jul 2011 21:30:02 GMT

Hey Egor,

I have some new BL360 G7 blades that are running ESXi 4.1

I am unable to install the Insight Management Agents under ESXi, and I have heard that ESX will be discontinued soon, just leaving the ESXi platform (with no SNMP / ability to install plugins).

From what I have read, all monitoring of ESXi (certainly going forward) has to be done via WBEM / CIM.

Would there be a way for this ZenPack to do something over this protocol rather than SNMP.

I appreciate this may be a fairly big job, and I suspect may even require a new ZenPack. If that is the case, would it be something you would be willing to look into?

I have this pack monitoring Windows and Linux servers fine, it's just this niggling issue with ESXi that I would love to sort out.

Thanks again for the great ZenPack, it has made my life so much easier !!

Paul

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Jul 2011 21:30:51 GMT

Hi Photon,

1. this ZenPack contains a lot of MIB objects, this is why installation of this ZenPack can take a long time. So try to use CLI (zenpack --install=ZenPacks.community.HPMon) instead of GUI.

2. are you sure your snmpd.conf correctly configured? do you get any traps from this server?

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Jul 2011 21:37:03 GMT

Hi Paul,

i'm working now on CIM Monitoring ZenPack https://github.com/epuzanov/ZenPacks.community.CIMMon

Warning!!!ALPHA quality, not for production use.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Jul 2011 21:38:51 GMT

Hi Egor,

1. I didn't express myself well maybe. It's the start/restart of Zenoss that takes too long. Zenpack is already installed.

2. Well.. This problem was a weird one. I was testing network interfaces UP/DOWN status change to get traps. I was getting a trap for UP and not for DOWN ! The problemn is that the cmanic agent (HP) that was parsing /var/log/messages for interface changes didn't find an entry for ethX Link is Down. When I add this using the echo command, it generates a trap... weird, but we're working on it ^^

Thanks for yout anwsers

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Jul 2011 21:42:03 GMT

You are a legend (and a mind-reader) !!! How would I go about trying this out, I guess I am asking how do I make the .egg file so I can install under Zenoss 3.1.

Thanks again

Paul

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 13 Jul 2011 21:51:29 GMT

Hi Paul,

as zenoss user run:

python setup.py bdist_egg

But again, do NOT use it in production environment.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 14 Jul 2011 01:06:35 GMT

Hi Egor,

I'm not sure this is a bug, but I have noticed that the Queue Depth metric for Logical Disks seems to be cumulative. The value either stays at a constant level or continues to increase, rather than fluctuate as one would expect, (as the logical disk's queue depth increases/decreases).

Is this correct?

Thanks,

James

FYI, I am using the latest version of your Zenpack.

Cheers,

James

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 14 Jul 2011 17:45:22 GMT

Hi James,

i've checked "Queue Depth" graph, and it correctly displayed for my servers.

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 01 Aug 2011 10:17:07 GMT

About the IO Graph :

It should be blocks/sec not bytes I think. Also, what if we have two disks ? does it graph the sum of their IO ?

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 30 Aug 2011 16:19:09 GMT

Hi Egor

What a great plugin, thank you! Are you aware that IE9 doesn't display some components correctly? E.g. memory modules appear as down in IE9, but not in Chrome.

Thanks!

Rob

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 30 Aug 2011 18:24:09 GMT

Hi Rob,

i'm not sure whether IE9 is fully supported by Zenoss (check list of supported browsers on download page).

Egor

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 20 Sep 2011 13:45:25 GMT

Hello Egor,

I had a problem upgrading to 3.2.0, which I have tracked down to cpqSsChassis.py.

This defines "name" as a string, this causes errors about a non serializable object in 3.2.0, which is expecting the object to have a method "name()" . I have just removed the code that defines "name" but perhaps that's not correct. I notice that this is the only module in that directory that defines "name" like this.

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 22 Sep 2011 18:56:48 GMT

Hi Egor,

I seem to have a problem monitoring physical and logical hard disks using this ZenPack and the WMI ZenPack. We're using Zenoss 3.1.0.

I saw a user (OneLoveAmaru) of your DellMon ZenPack so I'm thinking the problem exists with the HP Proliant Monitor ZenPack and not the WMI Perf monitor ZenPack so I've decided to post here.

I see my 2 physical hard disks under the Hard Disks component however there doesn't appear to be a monitoring template (Win32DiskDrive) attached to them and therefore no graphs are being created. The same is true for logical disks.

Is this correct behavior? I was expecting to see IO and Disk QueueLength such as what I see on other Windows devices.

My list of modeler plugins is:

c.wmi.filesystemmap

c.wmi.interfacemap

c.wmi.processmap

c.wmi.productmap

c.wmi.winservicemap

z.snmp.ipservicemap

c.snmp.HP* (HPLogicalDiskMap, HPHardDiskMap, and HPExpansionCardMap are at the end of the list)

I've tried different combinations of the modeler plugins including:

1. Adding c.wmi.diskdrivemap to plugins list

This creates a single PHYSICALDRIVE0 under the Hard Disks component with IO Bytes and Disk Queue Length.

2. Adding c.wmi.diskdrivemap and removed c.snmp.hpdalogdrvmap, c.snmp.hpdacntlrmap, and c.snmp.hpdaphydrvmap plugins.

Same as above.

Any ideas on how I can fix this scenario?

Thanks,

John

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 23 Sep 2011 13:11:33 GMT

Hello again BigEgor,

Another thing... we'd really like to see the amount of memory and size of the page file in the overview of a Windows device however none of the community.snmp.hp* modeler plugins set this for us. So we use the community.wmi.devicemap plugin from yoru WMI Perf ZenPack which does set them however it also messes up the serial number of our HP Blades (BL460c G1) and instead shows the serial number for the chassis instead fo the blade itself.

So what I normally do is model a device with the c.wmi.devicemap plugin included and then remove the plugin after memory has been set.

Is there a better way to go about this? Or is it possible to get a plugin in the HP Proliant Monitor ZenPack that will set these values for us?

Thanks,

John

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 27 Sep 2011 10:10:07 GMT

Hi Gents,

in the Zenoss 2.4.x is very nice the Hardware tab to show the status of hardware component, but I don't find anything like this in Zenoss 3.1.0...

Is it ok?

Thanks

Alex

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 12 Oct 2011 17:28:46 GMT

I have servers with I/O (4.0G), disk (4.0G), and hard read (250) errors. Is there any documentation around these errors? Is this a case for HP to replace these disks?

Some servers also have the error cpqIdeController as an unknown controller - how can I resolve this?

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 20 Oct 2011 16:05:20 GMT

Hi Egor,

I'm wondering how I might be able to modify the included hard disk report to include the devices model. I can't seem to figure out how to get back to the hard disks' parent device in order to getHWProductKey.

Any advice for me?

Thanks,

John

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 28 Oct 2011 11:32:34 GMT

HP Proliant Monitor is maybe the biggest reason why I went with Zenoss and not Zabbix or one of the other alternatives.

Using this ZenPack together with redundant PSUs and raids means almost no downtime across all monitored equipment. Whenever a disk breaks or a PSU is accidentally unplugged I know it the next time I check my mail. That makes a whole lot of a difference when there are lots of servers running at remote locations.

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 23 Nov 2011 15:33:35 GMT

Is there any compatibility problem with zenoss 3.2.1?

Thanks

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 21 Dec 2011 23:28:39 GMT

Im using this Zenpack with a fresh install of Zenoss 3.2.1 and I dont see the community.hp.etc options in my Modelor Plugins, I only have the vanilla zenoss.snmp.etc ones.

I installed the Advanced zenpack as advised but im not sure why they arent showing up.

Thanks

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 12 Jan 2012 12:25:21 GMT

stupid question:

2. Remove the zenoss.snmp.Cpu (click the X next to it)

zenoss.snmp.Cpu is the same as zenoss.snmp.CpuMap?

I don't see zenoss.snmp.Cpu in my list...

Thanks

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 13 Jan 2012 03:47:54 GMT

Hello,

I try 2 dif. versions and they do not work for me...

Software Component Versions

Zenoss	Zenoss 3.2.1
OS	Linux (x86_64) 2.6.32 (Linux Zenoss 2.6.32-220.2.1.el6.x86_64 #1 SMP Fri Dec 23 02:21:33 CST 2011 x86_64)
Zope	Zope 2.12.1
Python	Python 2.6.2
Database	MySQL 5.0.45 (Ver 5.0.45)
RRD	RRDtool 1.3.9
Twisted	Twisted 8.1.0
NetSnmp	NetSnmp 5.4.1
PyNetSnmp	PyNetSnmp 0.29.13
WMI	Wmi 1.3.13

Log from 1st try:

/usr/local/zenoss/zenoss/bin/zenpack --install ZenPacks.community.HPMon-2.2.egg

2012-01-13 05:33:56,472 INFO zen.ZPLoader: Loading /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPMon-2.2.72.egg/ZenPacks/community/HPMon/objects/objects.xml

2012-01-13 05:33:56,496 WARNING zen.AddToPack: Unable to find context path /zport/dmd/Devices/Server/rrdTemplates (line 4 ?) for HPFan

2012-01-13 05:33:56,496 WARNING zen.AddToPack: Not committing any changes

2012-01-13 05:33:56,646 ERROR zen.ZenPackCmd: zenpack command failed

Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 406, in <module>

zp.run()

File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 134, in run

previousVersion= self.options.previousVersion)

File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 249, in InstallEggAndZenPack

forceRunExternal=forceRunExternal)

File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 424, in InstallDistAsZenPack

zenPack.install(dmd)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPMon-2.2.72.egg/ZenPacks/community/HPMon/__init__.py", line 27, in install

ZenPackBase.install(self, app)

File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPack.py", line 251, in install

loader.load(self, app)

File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPackLoader.py", line 99, in load

importer.loadObjectFromXML(xmlfile=f)

File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 458, in loadObjectFromXML

parser.parse(self.infile)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse

xmlreader.IncrementalParser.parse(self, source)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/xmlreader.py", line 123, in parse

self.feed(buffer)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed

self._parser.Parse(data, isFinal)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 312, in start_element

self._cont_handler.startElement(name, AttributesImpl(attrs))

File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 152, in startElement

'attributes:\n%s' % formattedAttrs)

Exception: Unable to create object using the following attributes:

* id: /zport/dmd/Devices/Server/rrdTemplates/HPFan

* module: Products.ZenModel.RRDTemplate

* class: RRDTemplate

and from 2nd:

/usr/local/zenoss/zenoss/bin/zenpack --install ZenPacks.community.HPMon-2.2.72.egg

2012-01-13 05:33:10,457 INFO zen.ZPLoader: Loading /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPMon-2.2.72.egg/ZenPacks/community/HPMon/objects/objects.xml

2012-01-13 05:33:10,471 WARNING zen.AddToPack: Unable to find context path /zport/dmd/Devices/Server/rrdTemplates (line 4 ?) for HPFan

2012-01-13 05:33:10,472 WARNING zen.AddToPack: Not committing any changes

2012-01-13 05:33:10,603 ERROR zen.ZenPackCmd: zenpack command failed

Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 406, in <module>

zp.run()

File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 134, in run

previousVersion= self.options.previousVersion)

File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 249, in InstallEggAndZenPack

forceRunExternal=forceRunExternal)

File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 424, in InstallDistAsZenPack

zenPack.install(dmd)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPMon-2.2.72.egg/ZenPacks/community/HPMon/__init__.py", line 27, in install

ZenPackBase.install(self, app)

File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPack.py", line 251, in install

loader.load(self, app)

File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPackLoader.py", line 99, in load

importer.loadObjectFromXML(xmlfile=f)

File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 458, in loadObjectFromXML

parser.parse(self.infile)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse

xmlreader.IncrementalParser.parse(self, source)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/xmlreader.py", line 123, in parse

self.feed(buffer)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed

self._parser.Parse(data, isFinal)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 312, in start_element

self._cont_handler.startElement(name, AttributesImpl(attrs))

File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 152, in startElement

'attributes:\n%s' % formattedAttrs)

Exception: Unable to create object using the following attributes:

* id: /zport/dmd/Devices/Server/rrdTemplates/HPFan

* module: Products.ZenModel.RRDTemplate

* class: RRDTemplate

Any ideas?

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 04 May 2012 11:32:44 GMT

any idea why i dont see the fans or the harddisk?

the processor doesnt give any information? it says 0 mV

i installed: the agent on the proliant dl160 g6, on the zenoss the 2 zenpacks that are needed...

thanks for advance

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 17 May 2012 16:31:21 GMT

hi Egor,

i have a question about cpqida mib templates.

in the mib hard drive errors are declared as counters, as an instance :

cpqDaPhyDrvHardReadErrs OBJECT-TYPE

SYNTAX Counter

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Hard Read Errors.

This shows the number of read errors that have occurred on a

drive that could not be recovered by a physical drive's Error

Correction Code (ECC) algorithm or through retries during the

reference time (phyDrvRefTime). Over time, a disk drive may

produce these errors. If you receive these errors, a problem

may exist with your drive.

The value increases every time the physical drive detects another

error.

The severity of these errors depends on whether the monitored

system is running in a fault tolerant mode. With fault tolerance,

the controller can remap data to eliminate the problems caused by

these errors. In either case, if you see an increase in these

errors, schedule server down time to run diagnostics to verify

that a problem exists."

but in template rrd variables declared as gauge with threshold 2

so if just 3 errors appeared on a host and not increased , error events will be generated and stay forever.

so the question:

is rrd variables in template declared as gauge intentionally or is that a bug in the template ?

if that not a bug could you please provide a description or link to a resource which provides more information about that.

thanks.

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 20 May 2012 18:54:53 GMT

hi sergevs42,

i know that, but i've decided to use GAUGE because, i want see how many errors has HardDisk and most important how this counter grows.

RE: HP ProLiant Monitor

community@zenoss.org — Mon, 21 May 2012 16:38:18 GMT

well,

what do you think about:

have two rrd variables: one gauge as now to graph without threshold, the second counter and threshold on error rate (2, the same as it now) ?

probably that will reflect mib description ("If you receive these errors, a problem may exist with your drive") , you will see total numer of errors and an event will not be always present for drives errors are not increasing over the time.

regards.

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 01 Jun 2012 18:21:42 GMT

I recently installed this ZenPack and found it did show the disks in my my server, but when we ppulled one as a test, I never saw the status on the disk change. Is there something that I need to update after modeling?

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 05 Jun 2012 12:27:50 GMT

Hello, Egor.

I have an issue with cpqdaCntrl template. Recently I have one of accel boards battery died. It made accel board status to become "failed" and controller - "degraded".

But in zenoss I had two similar events:

threshold of cpqDaCntlr status exceeded: current status Failed

threshold of cpqDaCntlr status exceeded: current status Degraded

It was pretty confusing at the first time. How can it be failed and degraded at the same time?!

Later I found out, that there is 1 threshold for two oids in the template. It would be better to have separate thresholds for acceleration board status and controller status.

Also, controller status in component window reported as "Failed", when it is "degraded" (here we have discrepancy between zenoss and raw snmp).

Would you fix this problem? Should I send you a patch for zenpack? Do you need any additional information? I have fixed it for myself, though I really want it to be fixed in zenpack.

With best regards,

Ippolitov Igor.

RE: HP ProLiant Monitor

community@zenoss.org — Sun, 10 Jun 2012 17:40:46 GMT

Hi Igor,

please drop me a PM with your patch.

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 26 Jun 2012 18:45:19 GMT

Hello,

Will this work with Zenoss versions 4.1.x ? If so what would be the installation steps/dependencies, I have tried installing these but with no success yet.

Thanks,

Farhan

RE: HP ProLiant Monitor

community@zenoss.org — Fri, 24 Aug 2012 10:09:23 GMT

Does this detect S.M.A.R.T. imminent hard drive failures? I can see these in my IML log but there does not seem to be a zenoss event generated?

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 13 Sep 2012 19:49:59 GMT

Farhan,

I loaded them onto my 4.2 test server with almost problems. The only things I have run into so far is:

I'm not getting some of the graphs to populate, but I think that isn't a problem with the ZenPack but something else in my install
The fan component gives me the error: ValueError: cannot convert float NaN to integer

RE: HP ProLiant Monitor

community@zenoss.org — Wed, 10 Oct 2012 13:26:40 GMT

Is there going to be an update for this to support ESXi management agents on proliant hardware, as the ESXi OS is not running these specific HP SNMP agents?

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 11 Oct 2012 18:17:02 GMT

Hi gcollins,

try https://github.com/epuzanov/ZenPacks.community.CIMMon ZenPack, it can monitor HP Servers too.

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 30 Oct 2012 23:51:55 GMT

This definitely appears to be broken on a 4.2 install as two of us are having the exact same issue:

2012-10-30 22:43:48,062 ERROR zen.hub: Unhandled exception in zenhub service Products.ZenHub.services.SnmpPerformanceConfig.SnmpPerformanceConfig: local variable 'ifindex' referenced befor

e assignment

Traceback (most recent call last):

File "/opt/zenoss/Products/ZenCollector/services/config.py", line 108, in _wrapFunction

return functor(*args, **kwargs)

File "/opt/zenoss/Products/ZenHub/services/SnmpPerformanceConfig.py", line 145, in _createDeviceProxies

proxy = self._createDeviceProxy(device, manage_ip, components, components_only)

File "/opt/zenoss/Products/ZenHub/services/SnmpPerformanceConfig.py", line 175, in _createDeviceProxy

threshs = self._getComponentConfig(comp, perfServer, proxy.oids)

File "/opt/zenoss/Products/ZenHub/services/SnmpPerformanceConfig.py", line 109, in _getComponentConfig

oid = self._transform_oid(ds.oid.strip("."), comp)

File "/opt/zenoss/Products/ZenHub/services/SnmpPerformanceConfig.py", line 90, in _transform_oid

index = getattr(comp, "ifindex", comp.snmpindex)

File "/opt/zenoss/ZenPacks/ZenPacks.community.HPMon-2.2.72.egg/ZenPacks/community/HPMon/cpqDaLogDrv.py", line 66, in <lambda>

ifindex = property(fget=lambda self: self._getSnmpIndex(),

File "/opt/zenoss/ZenPacks/ZenPacks.community.HPMon-2.2.72.egg/ZenPacks/community/HPMon/cpqDaLogDrv.py", line 61, in _getSnmpIndex

return self.snmpindex + ifindex

UnboundLocalError: local variable 'ifindex' referenced before assignment

2012-10-30 22:44:23,178 INFO zen.ZenHub: Worker (25534) reports 2012-10-30 22:44:23,177 WARNING zen.ApplyDataMap: The attribute cacheSizeL3 was not found on object cpu2 from device 10.41.48.121

2012-10-30 22:44:23,200 INFO zen.ZenHub: Worker (25534) reports 2012-10-30 22:44:23,200 WARNING zen.ApplyDataMap: The attribute cacheSizeL3 was not found on object cpu1 from device 10.41.48.121

2012-10-30 22:44:56,438 ERROR zen.hub: Unhandled exception in zenhub service Products.ZenHub.services.SnmpPerformanceConfig.SnmpPerformanceConfig: local variable 'ifindex' referenced before assignment

The graphs stop showing data once I apply this to them.

-Brad

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 27 Nov 2012 16:13:01 GMT

Is anyone else seeing issues with the fan status with the latest version of this ZenPack? I have a handful of older servers that are regularly reporting "threshold of HPsdFan status exceeded: current status other" followed by "Event: 'threshold of HPsdFan status exceeded: current status other'" a few minutes later.

I'm using version 2.3.0 of the ZenPack on Zenoss 4.2.0 SP1

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 31 Jan 2013 12:42:14 GMT

I too would be interested in a fix for this issue.

I'm using version 2.3.0 of the ZenPack on Zenoss 4.2.0 SP1

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 31 Jan 2013 22:10:47 GMT

From talking to dhopp on the IRC channel I found that the "fix" is to update HP PSP on the server. There are bugs in older versions of the software that cause this to happen.

As a workaround you can deal with it in the even transform, I'll talk to dhopp and see if he has any problem with my posting the code he gave me (and I added toa bit).

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 May 2013 08:10:37 GMT

hi,

i use this version:

Zenoss	Zenoss 4.2.3
OS	Linux (x86_64) 2.6.32 (Linux zenoss.**** 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64)
Zope	Zope 2.13.13
Python	Python 2.7.2
Database	MySQL 5.5.28 (5.5.28)
RRD	RRDtool 1.4.7
Twisted	Twisted 11.0.0
RabbitMQ	RabbitMQ 2.8.7
Erlang	Erlang 5.8.5
NetSnmp	NetSnmp 5.5.0
PyNetSnmp	PyNetSnmp 0.30.6
WMI	Wmi 1.3.15

i installed the 2 zenpacks, i add my server under /server and i modified the "modeler plugins" and add all community.snmp.HP* plugins to selected. i do "Model Device...".

but nothing is changed, i cant see any new components

did you know why?

PS: my server is a windows 2008 on a ProLiant DL380 G5 Machine with installed HP Management Agents and HP Insight Management WBEM Providers

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 16 May 2013 08:22:01 GMT

I suppose, you should check you host with snmpwalk command, if it provides data needed for HP ZenPack (oids under 1.3.6.1.4.1.232). I would also look through list of used plugins in a windows that appears after "model device" command.

You can also try remodelling the device from command line with more verbosity to find the cause of the problem.

RE: HP ProLiant Monitor

community@zenoss.org — Thu, 11 Jul 2013 16:36:49 GMT

Hello. We have proliant servers with vmware esxi5.1 and hp offline bundle (snmp enabled). Does this zenpack work with this configuration?

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 16 Jul 2013 08:56:16 GMT

Version 2.3.0 on Zenoss 4.2.3/4.2.4 when pulling from new DL380 G8's running hp-snmp-agents 9.30-2412.33, hp-health 9.31-1572.3 on CentOS 6.4 64bit I am continuously getting the following errors:

Component:	powerSupply3
Event Class:	/HW/Temperature
Status:	New
Message:	threshold of Overheating exceeded: current value 25.000000

agent	zenperfsnmp
component	powerSupply3
dedupid	10.41.232.194\|powerSupply3\|/HW/Temperature\|TemperatureCelsius_temperature_celsius\|Overheating\|5
eventClass	/HW/Temperature
eventClassKey
eventClassMapping
eventGroup
eventKey	TemperatureCelsius_temperature_celsius\|Overheating
eventState	New
evid	d485645e-f7b0-a1b5-11e2-cc1cf583eb04
facility
message	threshold of Overheating exceeded: current value 25.000000
ntevid
priority
severity	5
summary	threshold of Overheating exceeded: current value 25.000000

Device State...

DeviceClass	/Server/Linux/Core
DeviceGroups
DevicePriority	Normal
Location
Systems
device	BACKUP-01
ipAddress	10.41.232.194
monitor	localhost
prodState	Production

Event Data...

clearid
count	12490
firstTime	2013-06-03 07:12:28
lastTime	2013-07-16 08:47:58
ownerid
stateChange	2013-06-03 07:12:28

Event Details...

current	25.0
how	exceeded
manager	ZENOSS
max	-99
zenoss.device.device_class	/Server/Linux/Core
zenoss.device.ip_address	10.41.232.194
zenoss.device.priority	3
zenoss.device.production_state	1000

This is reporting for PowerSupply3 and 4. But there is no powersupply3 or 4. And even then it shows that it is not exceeding the limit. Any help appreciated.

RE: HP ProLiant Monitor

community@zenoss.org — Tue, 04 Feb 2014 15:01:15 GMT

Updated ZenPacks.community.HPMon from 2.2.7 to 2.3 on an Enterprise 4.2.4 system.

We seem to have lost the Status, Monitored and Event (severity) fields in the GUI, JUST for Expansion Cards. Other components show these fields OK.

Anyone else seen this? Get the same with both Firefox 26.0 and Chrome 27.0.1453.116.

Thoughts for a fix?

Cheers,

Jane