ZenPacks : HP EVA Monitor : Comments

RE: HP EVA Monitor

community@zenoss.org — Sun, 16 May 2010 18:11:46 GMT

Nice. Your zenpacks are greats. The disk images will be a nice feature on the Proliant Monitor.

RE: HP EVA Monitor

community@zenoss.org — Wed, 02 Jun 2010 15:25:11 GMT

A very big thank you to the author of this plugin, it works fantastically.

One word of warning for anyone else installing it; I already had our Command Server as a basic device for ping monitoring prior to finding this plugin, and I attempted to move the existing device into the new class and remodel it. This did not give all of the functionality of the zenpack and it was not until I removed and readded the device that it began to work.

RE: HP EVA Monitor

community@zenoss.org — Tue, 10 Aug 2010 19:56:49 GMT

Strangely, I'm getting an error when trying to add my device: Unhandled exception in zenhub service ZenPacks.community.WBEMDataSource.services.WbemPerfConfig.WbemPerfConfig: list index out of range.

I think I followed the instructions correctly, with WBEMproxy set with the EVA address and the device name as the ilo address. I've tried uninstalling and reinstalling both the EVA and WBEM Zenpaks. I can see a partial traceback: Traceback (most recent call last): File "/opt/zenoss/zenoss/Products/ZenCollector/services/config.py", line 84, in _wrapFunction return functor(*args, **kwargs) File "/opt/zenoss/zenoss/ZenPacks/ZenPacks.community.WBEMDataSource-2.7.egg/ZenPacks/c

RE: HP EVA Monitor

community@zenoss.org — Tue, 10 Aug 2010 21:14:26 GMT

Hi aharon,

zWbemProxy must be set to IP address of EVA management server (server with Command View EVA software installed), not EVAs IP address.

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 18:25:11 GMT

Thanks for the note Egor. I should mention that I have tried this with the Management server's IP address as the zWbemProxy, and the ilo DNS name or address as the Device name. Each time the job log says:

2010-08-11 14:18:15,693 INFO zen.ZenDisc: Connecting to localhost:8789
2010-08-11 14:18:15,705 INFO zen.ZenDisc: Connected to ZenHub
2010-08-11 14:18:16,144 INFO zen.ZenDisc: Looking for 192.168.3.157
2010-08-11 14:18:17,505 INFO zen.ZenDisc: Result: Discovered device 192.168.3.157.
2010-08-11 14:18:17,543 INFO zen.ZenDisc: No WMI plugins found for 192.168.3.157
2010-08-11 14:18:17,548 INFO zen.ZenDisc: Python collection device 192.168.3.157
2010-08-11 14:18:17,548 INFO zen.ZenDisc: plugins: community.wbem.HPEVADeviceMap, community.wbem.HPEVAStorageDiskEnclosureMap, community.wbem.HPEVAStoragePoolMap, community.wbem.HPEVAStorageProcessorCardMap, community.wbem.HPEVAHostFCPortMap, community.wbem.HPEVADiskDriveMap, community.wbem.HPEVAStorageVolumeMap

and then hangs forever, or at least for 5 hours when I gave up. My WBEM credential and pass are correct.

The WBEM Zenpack requires no configuration from me, right? Just install and play?

Thanks for your advice. Please let me know if this is the wrong channel for such questions.

Dan

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 18:39:06 GMT

1. first of all, check WBEM connectivity with (with http://sourceforge.net/apps/mediawiki/pywbem/index.php?title=YAWN or another WBEM browser)

2. zWinUser, zWinPassword and zWbemProxy zProperties you must set for /Devices/CIM/HPEVA device class.

3. add your EVA to /Devices/CIM/HPEVA device class.

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 19:58:45 GMT

Progress. I'm not sure what namespace yawn wants. I've tried root/cim and root and cim and root/CIM/HPEVA. Don't know what I'm doing with that. With an empty namespace, yawn returns:

: : Socket error: (111, 'Connection refused')

With anything in the namepace field, I get:

Socket error: (111, 'Connection refused')

<CIM CIMVERSION="2.0" DTDVERSION="2.0">
  <MESSAGE ID="1001" PROTOCOLVERSION="1.0">
    <SIMPLEREQ>
      <IMETHODCALL NAME="EnumerateClasses">
        <LOCALNAMESPACEPATH>
          <NAMESPACE NAME="root"/>
          <NAMESPACE NAME="cim"/>
        </LOCALNAMESPACEPATH>
        <IPARAMVALUE NAME="IncludeClassOrigin">
          <VALUE>
            FALSE
          </VALUE>
        </IPARAMVALUE>
        <IPARAMVALUE NAME="IncludeQualifiers">
          <VALUE>
            FALSE
          </VALUE>
        </IPARAMVALUE>
        <IPARAMVALUE NAME="DeepInheritance">
          <VALUE>
            TRUE
          </VALUE>
        </IPARAMVALUE>
        <IPARAMVALUE NAME="LocalOnly">
          <VALUE>
            TRUE
          </VALUE>
        </IPARAMVALUE>
      </IMETHODCALL>
    </SIMPLEREQ>
  </MESSAGE>
</CIM>

Any more hints?

Thanks,

Dan

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 20:02:09 GMT

namespace is root/eva

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 20:08:46 GMT

with root/eva

Socket error: (111, 'Connection refused')

<CIM CIMVERSION="2.0" DTDVERSION="2.0">
  <MESSAGE ID="1001" PROTOCOLVERSION="1.0">
    <SIMPLEREQ>
      <IMETHODCALL NAME="EnumerateClasses">
        <LOCALNAMESPACEPATH>
          <NAMESPACE NAME="root"/>
          <NAMESPACE NAME="eva"/>
        </LOCALNAMESPACEPATH>
        <IPARAMVALUE NAME="IncludeClassOrigin">
          <VALUE>
            FALSE
          </VALUE>
        </IPARAMVALUE>
        <IPARAMVALUE NAME="IncludeQualifiers">
          <VALUE>
            FALSE
          </VALUE>
        </IPARAMVALUE>
        <IPARAMVALUE NAME="DeepInheritance">
          <VALUE>
            TRUE
          </VALUE>
        </IPARAMVALUE>
        <IPARAMVALUE NAME="LocalOnly">
          <VALUE>
            TRUE
          </VALUE>
        </IPARAMVALUE>
      </IMETHODCALL>
    </SIMPLEREQ>
  </MESSAGE>
</CIM>

That socket error seems to have a number of possible causes, none of which stand out to me. Seen that before?

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 20:16:37 GMT

try with both http or https

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 20:39:49 GMT

Same error for both. I notice that both yawn and the zWbemProxy refer to port 5989. netstat -lp grep 5989 comes up with nothing. Am I not listening in some way i should be?

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 20:48:54 GMT

have you SMI-S CIMOM installed on CommandView server?

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 21:11:36 GMT

I do now. Software that tells me what components are out of date? There are a number of available updates. Is there one in particular I'm looking for? In case it helps, I notice that the WBEM client is installed on the CommandView server, and the desta service is started.

I'm sorry to be a pest. I thought we had a vanilla install, but clearly there's some goofiness with our hosts.

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 21:15:55 GMT

whitch CommandView version installed on server?

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 21:41:11 GMT

6.02.37

RE: HP EVA Monitor

community@zenoss.org — Wed, 11 Aug 2010 21:44:21 GMT

i've tested this Zenpack with CV 9.1

RE: HP EVA Monitor

community@zenoss.org — Wed, 01 Sep 2010 07:12:24 GMT

Hi Egor

I'm thinking the possibility of using this Zenpack as a templete for ESXi hardware info.

Can this be done ?

TQ.

RE: HP EVA Monitor

community@zenoss.org — Thu, 02 Sep 2010 10:19:40 GMT

Hi Egor,

I have also the same problem as aharon's issue. The device can't be modelized and showed the error message as

"Unhandled exception in zenhub service ZenPacks.community.WBEMDataSource.services.WbemPerfConfig.WbemPerfConfig: list index out of range" in the events. Did this support on the CV 6.02.37?

I found that there is no \\root\EVA namespace in the EVA_Command_View Server, would that be a cause?

RE: HP EVA Monitor

community@zenoss.org — Thu, 02 Sep 2010 14:00:23 GMT

Hi wilsonlai,

i haven't tested this ZenPack against old CV versions. I'm using CV 9.1.

Egor

RE: HP EVA Monitor

community@zenoss.org — Fri, 10 Sep 2010 15:55:15 GMT

We have a couple 8100's and a couple 8400's and our command view servers are running CV 9.1. These EVA's do not have any kind of ip management interface. All communication between the CV servers and the EVA's is done via fiber optic cable. Is there any way to monitor them with this zenpack?

RE: HP EVA Monitor

community@zenoss.org — Sun, 12 Sep 2010 09:52:37 GMT

Hi beanfield,

Yes, it will work. This ZenPacks communicate only with CV server.

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 14 Sep 2010 14:23:14 GMT

Egor,

Thanks for following up. I was able to get this to work with one of our 9.1.1 command view servers. I set the wbem proxy as 10.0.23.245 (the ip address of our cv server) and the hostname of the device as 10.0.26.117 (the ilo for this cv server). Once I added the device, it was able to enumerate all the disks and components of one of the six eva's it controls (in this case eva11).

Above you mention:

disconnect Command View EVA from other EVAs (only One EVA can be added at the same time
add EVA to Zenoss (use iLO IP address as Device Name and /CIM/HPEVA as Device Class Path)

I'd like to add the other 5 eva's to zenoss. When you say that only one can be added at the same time....does that mean that at any given point in time, there can be only one eva per cv server in zenoss...and to add another I would have to remove the current eva from zenoss? Or do you mean that during the process of adding the eva's to zenoss...they must be done individually. I.E. I can have all 6 eva's from this cv server, I just have add the first one, then the second, then the third, etc....

When you say "disconnect Command View EVA's from other EVA's" can you describe in more detail what this entails? While this disrupt service to the underlying disks?

Thanks for all your work on this zenpack, it looks like a lot of time was spent on it. Just on this one EVA, we can easily see a lot of detail that we couldn't as easily see before. Also, thanks for your help in getting this up and running for us.

-Eric

RE: HP EVA Monitor

community@zenoss.org — Tue, 14 Sep 2010 18:56:09 GMT

Hi beanfield,

1. i mean

that during the process of adding the eva's to zenoss...they must be done individually. I.E. I can have all 6 eva's from this cv server, I just have add the first one, then the second, then the third, etc....

When you say "disconnect Command View EVA's from other EVA's" can you describe in more detail what this entails? While this disrupt service to the underlying disks?

if you connect EVA from another CV server, EVA will be disconnected from current CV server.

3. by EVA modeling you can enter any IP address as EVA address, it doesn't used for modeling or monitoring. Only Wbem Proxy address is important

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 14 Sep 2010 19:54:34 GMT

Egor,

My apologies for asking you so many questions about this. When you say "

if you connect EVA from another CV server, EVA will be disconnected from current CV server." Do you mean that we have to rezone the existing EVA that's been added into zenoss onto another CV server so that the next time I add another EVA to zenoss it picks up the next EVA on the original CV server?

I'm not sure exactly what you mean when you say "disconnect". Is it rezoning the EVA, or somehow otherwise assigning the EVA to another CV server?

-Eric

RE: HP EVA Monitor

community@zenoss.org — Wed, 15 Sep 2010 21:09:18 GMT

Hi beanfield,

1. add first EVA to Zenoss

2. change 'snmpSysName' property to WWN of next EVA (you can do this with ZMI, you can normally switch to the management interface by appending '/manage' to the url) and remodel it.

3. Repeat steps 1 and 2 for another EVAs.

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 15 Sep 2010 21:56:31 GMT

My apologies Egor, but it appears this string is not editable in the zmi. If I browse to the existing eva and go go https://zenoss/zport/dmd/Devices/CIM/HPEVA/devices/GCEVA11/manage and I click on the "Properties" tab at the top right, I can see the current value of the string snmpSysName. However, it does not allow me to edit the field. The text box physically does not allow me to delete any of the existing characters. I'm logged in as the local administrator for the zenoss install so I should have permissions. I tried finding another way to accomplish this in zendmd, but I'm not familiar enough with the syntax to set this. Do you have any further pointers for changing this value?

Thanks,

-Eric

RE: HP EVA Monitor

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

Hi beanfield,

try new version of ZenPack.

Egor

RE: HP EVA Monitor

community@zenoss.org — Fri, 24 Sep 2010 16:53:45 GMT

Hi,

Great zenpack.

Is it possible to change the Device Class?

Rui

RE: HP EVA Monitor

community@zenoss.org — Tue, 12 Oct 2010 13:58:08 GMT

Egor,

I am having problems monitoring two EVA's managed by one CV server. Irrelevant of which WWN I input into the Device Name field, after moddeling it allways returns the info relevant to one EVA, never the other. I also lists that EVA's WWN into de SNMPSysName field, not the WWN I put into the Device Name field.

I am using HPEvaMon 1.6 and WBEMDataSource 2.8.

Anyway, thank you for these zenpacks, apart from this issue it is working great.

Kind regards,

Olivier

RE: HP EVA Monitor

community@zenoss.org — Tue, 12 Oct 2010 17:56:17 GMT

Hi Olivier,

you can try to add EVA without SNMP discovery.

zendisc run --now --device=WWN --no-snmp --monitor=localhost --deviceclass=/CIM/HPEVA

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 13 Oct 2010 07:52:18 GMT

Hi Egor,

I first updated to v1.7 and readded the devices. Remoddeling does not yield any output now, but gives this error:

2010-10-13 03:20:02,245 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystem) such that {CreationClassName="HPEVA_StorageSystem"&&CIM_System:Name="5000-1FE1-5008-1170"} not found from query: HPEVA_StorageSystem

Also, the zendisc command is not working, even though I am using the VMware appliance.

./zendisc run --now --device=5000-1FE1-5008-1170 --no-snmp --monitor=localhost --deviceclass=/CIM/HPEVA

I ran this command from the /opt/zenoss/bin/ directory.

Obviously this is not a zenpack issue but perhaps someone can point me in the right direction here.

Olivier

RE: HP EVA Monitor

community@zenoss.org — Wed, 13 Oct 2010 10:02:12 GMT

Hi Olivier,

use 50001FE150081170 as Device name, so:

./zendisc run --now --device=50001FE150081170 --no-snmp --monitor=localhost --deviceclass=/CIM/HPEVA

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 13 Oct 2010 10:55:03 GMT

That did it, using the WWN without the - fixed the moddelling (using the gui). It wil now find all the hardware. It does no longer retreive the Hardware Model and Serial Number. Also, I get this error very frequently:

Could not get WBEM Instance (Received Invalid WWN64 String from query: HPEVA_StorageSystem)

Perhaps we can continue this via e-mail? I have sent you a PM with my e-mail address.

RE: HP EVA Monitor

community@zenoss.org — Thu, 04 Nov 2010 22:16:02 GMT

Hi Egor,

We use HP CV 9.3 and HPEVAMon-1.8 and when trying to model the EVA device we get the following error:

ERROR zen.ZenModeler: Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner
return callable(*args, **kw)
File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 109, in remote_applyDataMaps
if adm._applyDataMap(device, map):
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 198, in _applyDataMap
changed = self._updateRelationship(tobj, datamap)
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 261, in _updateRelationship
objchange, obj = self._createRelObject(device, objmap, rname)
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 445, in _createRelObject
return self._updateObject(remoteObj, objmap) or changed, remoteObj
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject
setter(*args)
File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.8.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 133, in setStoragePool
for storagepool in self.device().os.storagepools():
AttributeError: storagepools
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/DataCollector/zenmodeler.py", line 658, in processClient
if driver.next():
File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result
raise ex
RemoteException: Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner
return callable(*args, **kw)
File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 109, in remote_applyDataMaps
if adm._applyDataMap(device, map):
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 198, in _applyDataMap
changed = self._updateRelationship(tobj, datamap)
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 261, in _updateRelationship
objchange, obj = self._createRelObject(device, objmap, rname)
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 445, in _createRelObject
return self._updateObject(remoteObj, objmap) or changed, remoteObj
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject
setter(*args)
File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.8.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 133, in setStoragePool
for storagepool in self.device().os.storagepools():
AttributeError: storagepools
2010-11-04 12:58:59,075 ERROR zen.ZenModeler: Client 50001FE150081F20 finished with message: [Failure instance: Traceback (failure with no frames): : Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner
return callable(*args, **kw)
File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 109, in remote_applyDataMaps
if adm._applyDataMap(device, map):
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 198, in _applyDataMap
changed = self._updateRelationship(tobj, datamap)
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 261, in _updateRelationship
objchange, obj = self._createRelObject(device, objmap, rname)
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 445, in _createRelObject
return self._updateObject(remoteObj, objmap) or changed, remoteObj
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject
setter(*args)
File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.8.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 133, in setStoragePool
for storagepool in self.device().os.storagepools():
AttributeError: storagepools
]

any idea of what can be the cause?

thanks a lot

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Nov 2010 12:13:04 GMT

With Zenoss Core 3.0.2, HP CV 9.3 and HPEVAMon-1.8, I also have a very similar issue when modeling the device. I used to have HPEVAMon-1.6 installed (but unused), removed it and then installed HPEVAMon-1.8. In the traceback it is interesting to note that this line appears (note the ZenPack version):

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.6.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 133, in setStoragePool
AttributeError: storagepools

I thought the fact that it still mentions the 1.6 version of the ZenPack might be significant and so I symlinked ZenPacks.community.HPEVAMon-1.6.egg to ZenPacks.community.HPEVAMon-1.8.egg. However, this made no difference.

I have since reverted to version 1.6 of the EVA Monitor and it is mostly working. There are a couple of anomalies though:

1. Although the various components all have a green tick next to them and they are apparently collecting data quite successfully, the status shown in every case is "Down" - our EVA is definitely not down :-)

2. Although the modeler showed no errors first time through, I only see six components - the HostFC component seems to be missing. Remodeling the device again yields the following:

2010-11-05 10:24:22,341 INFO zen.ZenModeler: Connecting to localhost:8789
2010-11-05 10:24:22,357 INFO zen.ZenModeler: Connected to ZenHub
2010-11-05 10:24:22,411 INFO zen.ZenModeler: Collecting for device 5000-1FE1-500F-C020
2010-11-05 10:24:22,459 INFO zen.ZenModeler: No WMI plugins found for 5000-1FE1-500F-C020
2010-11-05 10:24:22,461 INFO zen.ZenModeler: Python collection device 5000-1FE1-500F-C020
2010-11-05 10:24:22,461 INFO zen.ZenModeler: plugins: community.wbem.HPEVADeviceMap, community.wbem.HPEVAStorageDiskEnclosureMap, community.wbem.HPEVAStoragePoolMap, community.wbem.HPEVAStorageProcessorCardMap, community.wbem.HPEVAHostFCPortMap, community.wbem.HPEVADiskDriveMap, community.wbem.HPEVAStorageVolumeMap
2010-11-05 10:24:25,280 INFO zen.ZenModeler: No command plugins found for 5000-1FE1-500F-C020
2010-11-05 10:24:25,281 INFO zen.ZenModeler: SNMP monitoring off for 5000-1FE1-500F-C020
2010-11-05 10:24:25,281 INFO zen.ZenModeler: No portscan plugins found for 5000-1FE1-500F-C020
2010-11-05 10:24:25,590 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageControllerChassis) such that {CreationClassName="HPEVA_StorageControllerChassis"&&Tag="50001FE1500FC020.\\Hardware\\Controller Enclosure\\Controller 1"} not found from query: HPEVA_StorageControllerChassis
2010-11-05 10:24:26,316 INFO zen.PythonClient: Python client finished collection for 5000-1FE1-500F-C020
2010-11-05 10:24:26,316 INFO zen.ZenModeler: processing community.wbem.HPEVAStoragePoolMap for device 5000-1FE1-500F-C020
2010-11-05 10:24:26,317 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageProcessorCardMap for device 5000-1FE1-500F-C020
2010-11-05 10:24:26,317 INFO zen.ZenModeler: processing community.wbem.HPEVAHostFCPortMap for device 5000-1FE1-500F-C020
2010-11-05 10:24:26,318 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageVolumeMap for device 5000-1FE1-500F-C020
2010-11-05 10:24:26,319 ERROR zen.ZenModeler: Received Instance: isa(HPEVA_StorageControllerChassis) such that {CreationClassName="HPEVA_StorageControllerChassis"&&Tag="50001FE1500FC020.\\Hardware\\Controller Enclosure\\Controller 1"} not found from query: HPEVA_StorageControllerChassis
2010-11-05 10:24:26,319 INFO zen.ZenModeler: processing community.wbem.HPEVADeviceMap for device 5000-1FE1-500F-C020
2010-11-05 10:24:26,320 WARNING zen.ZenModeler: processing error
2010-11-05 10:24:26,320 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageDiskEnclosureMap for device 5000-1FE1-500F-C020
2010-11-05 10:24:26,320 INFO zen.ZenModeler: processing community.wbem.HPEVADiskDriveMap for device 5000-1FE1-500F-C020
2010-11-05 10:24:31,376 INFO zen.ZenModeler: Changes in configuration applied
2010-11-05 10:24:31,433 INFO zen.ZenModeler: Scan time: 9.02 seconds
2010-11-05 10:24:31,466 INFO zen.ZenModeler: Daemon ZenModeler shutting down

I am unsure whether my problem is due to HP CV 9.3 because you've only tested against 9.1, whether my WBEM proxy is missing some stuff or whether there is an issue in the ZenPack itself. There certainly appears to be a problem in version 1.8 of the ZenPack as reported by brunomrt.

I'd appreciate any help/advice on how to address these - the ZenPack is great otherwise.

Regards,

Mick.

It has just occurred to me that the issue with the modeler not finding "Controller 1", etc. is because our controllers are named "Controller A" and "Controller B". This is a user-configurable item and so the name should be discovered and used dynamically.

RE: HP EVA Monitor

community@zenoss.org — Mon, 08 Nov 2010 10:25:16 GMT

Mick,

I have a freshly install w2k8 R2 x64 with CV 9.3 and a EVA8000 in our testing enviroment with Zenoss 3.0.2 vmware appliance which is working fine, so I doubt this is a CV 9.3 issue.

I do have a feature request; the windows perfmon allow monitoring of the DR groups and replication. Would it be possible to include these in the ZenPack?

Kind regards,

Olivier Faber

RE: HP EVA Monitor

community@zenoss.org — Tue, 09 Nov 2010 21:36:12 GMT

Mick and Oliver,

Many thanks to your inputs. I have managed to solve my problem.

After deleted this ZenPack and the wbem data source, the device and the device class Devices/CIM, i reinstalled both zenpacks and re-added the device. Dunno what happen in the previous installation, but this time the modelling worked without any error

Best Regards

Bruno

RE: HP EVA Monitor

community@zenoss.org — Wed, 17 Nov 2010 15:32:32 GMT

has anyone got a noob's guide to what to do for this ? i have just installed Zenoss and its a bit of a minefield to add this eva ?

Do i add my CV9 server just as a server first ?

Where do i set the following ?

set zWinUser and zWinPassword (same as for Command View EVA Server)

set zWbemProxy to Command View EVA Servers IP Address

RE: HP EVA Monitor

community@zenoss.org — Thu, 25 Nov 2010 14:12:59 GMT

OK this is a werid one.

I've now seen the complete reverse of Bruno's situation.

The WBEM and HP EVA Mon packages went on fine and I setup the permissions and proxy in the Devices/CIM device class and added the first WWN as a device, remodled and hey presto we got all the data we were expecting.

I then added three more EVA WWNs in and watched data coming in.

I then renamed the devices and the next day realised that it appears that the four EVAs were graphing up until the time that I renamed them all.

I reverted the names back to their WWNs and got no change.

I then decided that I would remove end re-add the EVAs but we simply got the old RRD graphs back and no additional data was being collected.

I then went further and deleted the four EVAs again, removed the HP EVA Mon and WBEM zenpacks, the CIM/HPEVA Class and rebooted.

When I performed the reinstall of the zenpacks (with a reboot after the WBEM pack went on) I now see same error when modelling an EVA that Bruno first saw

for storagepool in self.device().os.storagepools():
AttributeError: storagepools

After modelling only the cotrollers appear in the Components area and Hardware fails to appear etc..

I've removed and reinstalled twice now and the same thing happens each time.

I can roll back to a two day old snapshot but I know other work has gone on on this server since them and we'll lose stuff if I go back.

Any ideas as to what I can do to fix this?

James

RE: HP EVA Monitor

community@zenoss.org — Thu, 25 Nov 2010 14:58:14 GMT

Gareth,

This is one of the easiest configs I've done.

If you haven't got this going yet, here's what you do.

1) Install the WBEM pack and reboot the Zenoss server

2) Install the HP EVA zenpack and restart zopectl either from the GUI or from the command line zopectl restart.

3) You should now have CIM/HPEVA device class..

4) Click on the HPEVA class and select Details.

5) Click Configuration Properties on the left.

6) In the right pane, scroll to the bottom and in the zWbemProxy field add the IP address or hostname of the EVA Command View server. The reason for this is that you'ere going to use the EVA server as a boker to grab data regarding the EVAs themselves, hence you request data about an EVA using it's WWN and that request is fired at the Command View IP/Hostname.

7) In the zWinPassword and zWinUser add the correct credentials of a user account that can access the server. (possibly create a new user account in AD and add this account to the CV server)

8) Hit Save.

9) Click on See All at the top of the left pane.

10) Still in the HPEVA class click on the icon at the top of the main pane to add a new single device. Use Command View get the WWN of your EVA and paste into the Hostname or IP field and click Add.

11) Give Zenoss a chance to perform the Add Job, when I first added our EVA the Job service was down and needed starting.

12) Once the device has been added, go into it and from the icon on the bottom left select Model Device. At this point I had issues with Zenoss connecting to Zenhub and got timeout errors. It eventually reconnected and carried on sometimes it didn't, just restart the modelling if it fails but give it a chance to retry.

13) Once the modelling has completed you should then see a load of objects in the Components menu in the left pane as well as a new hardware tab where the graphical disk view can be found.

Graphing should start almost immediately, you may need to soom in to see it starting. I may have seen an issue involving the renaming of the device from the WWN where graphing stops after the rename...well that's what appears to have happened....so rename at your peril!

Hope this helps.

James

RE: HP EVA Monitor

community@zenoss.org — Thu, 25 Nov 2010 15:01:34 GMT

Many thanks james i did get it working with our 3 EVA's and it seems to be working well at the moment a lot better than cacti/wmi & perfmon. Many thanks for the instructions i am sure they will be very usefull for new users of zenoss like me in the future

Cheers again

Gareth

RE: HP EVA Monitor

community@zenoss.org — Thu, 25 Nov 2010 15:43:46 GMT

Hi James,

excellent write-up! Can I update 'Install' section of this document with your instructions?

Egor

RE: HP EVA Monitor

community@zenoss.org — Thu, 25 Nov 2010 15:52:48 GMT

Egor,

Of course you can...you did all the hard work!

If you could cast your eye over the problem I posted four posts back I would be very appreciative.

There's nothing worse than getting something working first time only to break it and not get it working again!

Cheers,

James

RE: HP EVA Monitor

community@zenoss.org — Thu, 02 Dec 2010 18:03:36 GMT

I resolved my issue by installing ZenPacks.community.WBEMDataSource-2.10.egg instead of ZenPacks.community.WBEMDataSource-2.8.egg (not sure why I was using this one).

It's all working again now and I'm getting all the graphing and data!

RE: HP EVA Monitor

community@zenoss.org — Fri, 10 Dec 2010 15:30:22 GMT

Egor:

I have installed ZenPacks.community.HPEVAMon version 1.9 and ZenPacks.community.WBEMDataSource version 2.10 but I don't have the size of used bytes from disk groups only I have the total bytes and free bytes in disk groups.

In performance I Have the following error:

User-supplied Python expression (here.totalBytes() * here.threshold / 100) for maximum value caused error: ['StoragePool_Occupancy']

regards

Jose

RE: HP EVA Monitor

community@zenoss.org — Fri, 10 Dec 2010 17:52:06 GMT

try to restart Zenoss.

RE: HP EVA Monitor

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

I am not getting all of the graphs. I get the controllers but not the VDisks or FC cards. What steps should I take to troubeshoot this?

RE: HP EVA Monitor

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

check CV version. This ZenPack was tested with CV 9.1.

RE: HP EVA Monitor

community@zenoss.org — Tue, 21 Dec 2010 11:31:13 GMT

Hi.

Could you please be more specific on what kind of performance graphs are available in your HP EVA monitor zenpack?

Could you list all your graph titles or even screenshots (this would be awesome).

To be more specific, are there graphs showing IO statistics, writes/reads per sec and/or count, MB/s etc?

please post here or email me

mvdodatno (at) gmail com

thatnks, regards

marko

RE: HP EVA Monitor

community@zenoss.org — Sat, 25 Dec 2010 15:47:09 GMT

Egor

When I test the WBEM source HPEVA_DiskDriveStatisticalData.InstanceID="${here/snmpindex}"

in test against device :

I have the following error.

Get WBEM Instance HPEVA_DiskDriveStatisticalData.InstanceID="0" from https://10.10.97.49:5989/root/eva No handlers could be found for logger "zen.WBEMClient" Received String index out of range: -1 from query: HPEVA_DiskDriveStatisticalData DONE in 1 seconds

can you help me?

RE: HP EVA Monitor

community@zenoss.org — Sun, 26 Dec 2010 16:51:19 GMT

janayam,

you can not test components template against device, because 'snmpindex' of the device is not the same as 'snmpindex' of a component. If want to test that datasource against device, you must replace ${here/snmpindex} with real InstanceID value (within zendmd enter: find('yourEVAname').hw.harddisks()[0].snmpindex ).

Egor

RE: HP EVA Monitor

community@zenoss.org — Mon, 27 Dec 2010 08:28:19 GMT

Hi Egor, Merry Xmas.

I have been running version 1.8 against 6 of our eva. And it has been running as a charm, expect that we have to reboot /restart the CV about once a week as we were loosing the performancegraphs. So I thought I'll try and upgrade to 1.9. Then I lost all the "Hardware" part of the EVAmon, Well back to 1.8. The "Hardware part is back but the Hmmm Now all the graphs are "nan" and I get the event:

prodState	0
stateChange	2010/12/27 05:18:51.000
facility	unknown
eventClassKey
agent	zenhub
dedupid	localhost\|ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService.ZenJMXConfigService\|\|\|5\|Unhandled exception in zenhub service ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService.ZenJMXConfigService: \'HPEVAConsistency
manager	maadm01a.net.dr.dk
Location
ownerid
firstTime	2010/12/22 11:24:02.000
eventClass	/Unknown
message	Unhandled exception in zenhub service ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService.ZenJMXConfigService: 'HPEVAConsistencySet' object has no attribute 'getThresholdInstances'
DevicePriority	3
suppid
monitor	localhost
priority	-1
DeviceClass
eventState	0
evid	9d1da547-bd90-4d0e-8552-d091d5ffa1fc
eventClassMapping
component	ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService.ZenJMXConfigService
clearid
DeviceGroups
eventGroup
device	localhost
severity	5
count	290
ntevid	0
summary	Unhandled exception in zenhub service ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService.ZenJMXConfigService: 'HPEVAConsistency
eventKey
lastTime	2010/12/27 05:18:51.000
ipAddress
Systems
traceback	Traceback (most recent call last): File "/admin/zenoss/zenoss/Products/ZenCollector/services/config.py", line 84, in _wrapFunction return functor(args, *kwargs) File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenJMX-3.5.2-py2.6.egg/ZenPa
methodCall	_createDeviceProxy((,), {})

Zenoss	Zenoss 3.0.3
OS	Linux (x86_64) 2.6.18 (Linux maadm01a.xx.xx 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 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.28.14

Package	Author	Version	Egg
ZenPacks.HP.Proliant.MIBs	HP	Michael C. Hoffman	1.0	Yes
ZenPacks.Nova.Cisco.Mibs	Nova	Ryan Matte	1.0	Yes
ZenPacks.SCC.ShowGraphPortlet	SCC	Anton Menshutin m	0.2	Yes
ZenPacks.community.HPEVAMon	community	Egor Puzanov	1.8	Yes
ZenPacks.community.HPMon	community	Egor Puzanov	2.2	Yes
ZenPacks.community.LinuxMonitorAddOn	community	Eric Edgar	1.0	Yes
ZenPacks.community.WBEMDataSource	community	Egor Puzanov	2.10	Yes
ZenPacks.community.deviceAdvDetail	community	Egor Puzanov	2.5	Yes

Any idears ?

RE: HP EVA Monitor

community@zenoss.org — Mon, 27 Dec 2010 18:17:56 GMT

Hi WaltB,

i think, you have a problem with ZenPacks.zenoss.ZenJMX ZenPack, it is not completely removed. Check zenoss/ZenPacks subdirectory.

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 28 Dec 2010 12:59:22 GMT

Thanks Egor

That solved the Hardware display but it didn't solve that there is no graphs at all. It probably dosen't have any thing to do with your brilliant zenpack but could you perhaps point me in the correct direction, as I'm running out of idears.

WaltB

RE: HP EVA Monitor

community@zenoss.org — Tue, 28 Dec 2010 14:26:04 GMT

Hi WaltB,

have you already tryed this http://community.zenoss.org/docs/DOC-5867#comment-2981 ?

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 28 Dec 2010 14:31:38 GMT

Thanks

I'll try that tomorrow, but as I have renamed the I'll first try to rename them back to the WWN and see if that makes any difference.

WaltB

RE: HP EVA Monitor

community@zenoss.org — Wed, 29 Dec 2010 10:26:24 GMT

Hi Egor

Removed the devices and re-installed the zenpacks . With all the nessesary restarts of the server and zope. But I now get a failure with the following traceback:

Connecting to localhost:8789

2010-12-29 11:05:01,551 INFO zen.ZenModeler: Connected to ZenHub

2010-12-29 11:05:01,588 INFO zen.ZenModeler: Collecting for device 50001FE1500F4110

2010-12-29 11:05:01,656 INFO zen.ZenModeler: No WMI plugins found for 50001FE1500F4110

2010-12-29 11:05:01,658 INFO zen.ZenModeler: Python collection device 50001FE1500F4110

2010-12-29 11:05:01,659 INFO zen.ZenModeler: plugins: community.wbem.HPEVADeviceMap, community.wbem.HPEVAStorageDiskEnclosureMap, community.wbem.HPEVAStoragePoolMap, community.wbem.HPEVAStorageProcessorCardMap, community.wbem.HPEVAHostFCPortMap, community.wbem.HPEVADiskDriveMap, community.wbem.HPEVAConsistencySetMap, community.wbem.HPEVAStorageVolumeMap

2010-12-29 11:07:35,466 INFO zen.ZenModeler: No command plugins found for 50001FE1500F4110

2010-12-29 11:07:35,466 INFO zen.ZenModeler: SNMP monitoring off for 50001FE1500F4110

2010-12-29 11:07:35,467 INFO zen.ZenModeler: No portscan plugins found for 50001FE1500F4110

2010-12-29 11:07:59,588 INFO zen.PythonClient: Python client finished collection for 50001FE1500F4110

2010-12-29 11:07:59,588 INFO zen.ZenModeler: processing community.wbem.HPEVAStoragePoolMap for device 50001FE1500F4110

2010-12-29 11:07:59,589 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageProcessorCardMap for device 50001FE1500F4110

2010-12-29 11:07:59,589 INFO zen.ZenModeler: processing community.wbem.HPEVAHostFCPortMap for device 50001FE1500F4110

2010-12-29 11:07:59,590 INFO zen.ZenModeler: processing community.wbem.HPEVAConsistencySetMap for device 50001FE1500F4110

2010-12-29 11:07:59,591 INFO zen.ZenModeler: processing community.wbem.HPEVADeviceMap for device 50001FE1500F4110

2010-12-29 11:07:59,591 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageDiskEnclosureMap for device 50001FE1500F4110

2010-12-29 11:07:59,592 INFO zen.ZenModeler: processing community.wbem.HPEVADiskDriveMap for device 50001FE1500F4110

2010-12-29 11:07:59,602 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageVolumeMap for device 50001FE1500F4110

2010-12-29 11:08:00,472 ERROR zen.ZenModeler: Traceback (most recent call last):

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

return callable(*args, **kw)

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

if adm._applyDataMap(device, map):

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

changed = self._updateRelationship(tobj, datamap)

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 261, in _updateRelationship

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

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 445, in _createRelObject

return self._updateObject(remoteObj, objmap) or changed, remoteObj

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.9.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 113, in setEnclosure

encl = getattr(self.hw().enclosures, str(encid), None)

AttributeError: enclosures

Traceback (most recent call last):

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

if driver.next():

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

raise ex

RemoteException: Traceback (most recent call last):

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

return callable(*args, **kw)

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

if adm._applyDataMap(device, map):

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

changed = self._updateRelationship(tobj, datamap)

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 261, in _updateRelationship

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

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 445, in _createRelObject

return self._updateObject(remoteObj, objmap) or changed, remoteObj

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.9.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 113, in setEnclosure

encl = getattr(self.hw().enclosures, str(encid), None)

AttributeError: enclosures

2010-12-29 11:08:00,474 ERROR zen.ZenModeler: Client 50001FE1500F4110 finished with message: [Failure instance: Traceback (failure with no frames): : Traceback (most recent call last):

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

return callable(*args, **kw)

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

if adm._applyDataMap(device, map):

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

changed = self._updateRelationship(tobj, datamap)

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 261, in _updateRelationship

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

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 445, in _createRelObject

return self._updateObject(remoteObj, objmap) or changed, remoteObj

File "/admin/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.9.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 113, in setEnclosure

encl = getattr(self.hw().enclosures, str(encid), None)

AttributeError: enclosures

]

2010-12-29 11:08:00,474 INFO zen.ZenModeler: Scan time: 178.89 seconds

2010-12-29 11:08:00,487 INFO zen.ZenModeler: Daemon ZenModeler shutting down

Does it make any sense ?

Rgds

WaltB

RE: HP EVA Monitor

community@zenoss.org — Wed, 29 Dec 2010 12:31:45 GMT

Bugger ..... it is not only when I model a EVA device it's happens with all my devices. I have to figure out first what have changed.

WaltB

RE: HP EVA Monitor

community@zenoss.org — Thu, 30 Dec 2010 12:37:32 GMT

Hi Egor

Almost Fixed got to model OK (and all my other devices) by reinstalling a few zenpacks: HPmon, Proliant MIBs, AdvDeviceDetails.Deleting the devices and adding them again.

I still have the problem that I dont get any graphs, only nan. And it make no difference if I use the WWN or have given them a readable name as i have 5 of each with the same result, nothing.

I have other devices where I get the graphs OK.

WaltB

RE: HP EVA Monitor

community@zenoss.org — Thu, 30 Dec 2010 21:22:10 GMT

Hi WaltB,

try to run as zenoss user: zenperfwbem run -v10 -d EVADEVICENAME

RE: HP EVA Monitor

community@zenoss.org — Fri, 31 Dec 2010 12:22:30 GMT

Hi Egor

Thanks, Yes I have been running that command, actually I had previously an extra cron job running that command for all the WWN's (10 eva's)

Heres the output of running the command on one of the eva's:

http://dl.dropbox.com/u/17714359/output_hpeva.log

I can see that the RRD files are created/updated but the graphs still display NAN.

RE: HP EVA Monitor

community@zenoss.org — Fri, 31 Dec 2010 13:03:59 GMT

Hi WaltB,

something is wrong with your setup. Normally, you don't need any cron jobs to run that command. Check zeperfwbem.log and zenstatus.log files. Try to set zPingMonitorIgnore = True for your EVAs.

RE: HP EVA Monitor

community@zenoss.org — Tue, 04 Jan 2011 11:56:44 GMT

Thanks for you help Egor

I've done some symlinking and that is probably causing the problem. So now I'm reinstalling on a different server that have access to our SAN.

Thanks

WaltB

RE: HP EVA Monitor

community@zenoss.org — Wed, 05 Jan 2011 15:09:21 GMT

Egor:

I am using command View Version 9.01 and when model device I am getting the following:

2011-01-05 09:08:36INFOzen.ZenModelerplugins: community.wbem.HPEVADeviceMap, community.wbem.HPEVAStorageDiskEnclosureMap, community.wbem.HPEVAStoragePoolMap, community.wbem.HPEVAStorageProcessorCardMap, community.wbem.HPEVAHostFCPortMap, community.wbem.HPEVADiskDriveMap, community.wbem.HPEVAConsistencySetMap, community.wbem.HPEVAStorageVolumeMap 2011-01-05 09:08:37ERRORzen.WBEMClientReceived CIM_ERR_INVALID_NAMESPACE: IDispatch error #3598 from query: HPEVA_StorageSystem 2011-01-05 09:08:37ERRORzen.WBEMClientReceived CIM_ERR_INVALID_NAMESPACE: IDispatch error #3598 from query: HPEVA_StorageSystem 2011-01-05 09:08:37ERRORzen.WBEMClientReceived CIM_ERR_INVALID_NAMESPACE: IDispatch error #3598 from query: HPEVA_StoragePool 2011-01-05 09:08:37ERRORzen.WBEMClientReceived CIM_ERR_INVALID_NAMESPACE: IDispatch error #3598 from query: HPEVA_StorageProcessorCard 2011-01-05 09:08:37ERRORzen.WBEMClientReceived CIM_ERR_INVALID_NAMESPACE: IDispatch error #3598 from query: CIM_FCPort 2011-01-05 09:08:38ERRORzen.WBEMClientReceived CIM_ERR_INVALID_NAMESPACE: IDispatch error #3598 from query: HPEVA_DiskModule 2011-01-05 09:08:38ERRORzen.WBEMClientReceived CIM_ERR_INVALID_NAMESPACE: IDispatch error #3598 from query: HPEVA_ConsistencySet 2011-01-05 09:08:38ERRORzen.WBEMClientReceived CIM_ERR_INVALID_NAMESPACE: IDispatch error #3598 from query: HPEVA_OrderedMemberOfCollection

thanks in advance

Jose

RE: HP EVA Monitor

community@zenoss.org — Wed, 05 Jan 2011 18:57:25 GMT

Hi janayam,

1. check zWbemProxy property (must be set to IP address of CV server)

2. check 'HP Starageworks CIM Object Manager' service must be running on CV server.

3. check eva namespace must be successfully registered on CV server

RE: HP EVA Monitor

community@zenoss.org — Thu, 06 Jan 2011 18:07:02 GMT

Hey Egor

Me again, sorry.

It was the symlinking that caused the other problems. But I now have the same problem as you have been discussing here: http://community.zenoss.org/docs/DOC-5867#comment-2835 .But I think you finished that discussion on email.

2011-01-06 19:03:00,469 INFO zen.zenperfwbem: 10 devices processed (0 datapoints)
2011-01-06 19:03:00,469 INFO zen.collector.scheduler: Tasks: 10 Successful_Runs: 275 Failed_Runs: 0 Missed_Runs: 0
2011-01-06 19:03:03,317 ERROR zen.WBEMClient: Received Invalid WWN64 String from query: HPEVA_StorageSystem
2011-01-06 19:03:05,545 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID=""} not found from query: HPEVA_StorageSystemStatisticalData
2011-01-06 19:03:05,847 ERROR zen.WBEMClient: Received Invalid WWN64 String from query: HPEVA_StorageSystem
2011-01-06 19:03:06,139 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID=""} not found from query: HPEVA_StorageSystemStatisticalData
2011-01-06 19:03:06,139 ERROR zen.zenperfwbem: Device 5001438004C82C60: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID=""} not found from query: HPEVA_StorageSystemStatisticalData
2011-01-06 19:03:06,140 ERROR zen.zenperfwbem: Device 5001438004C82C80: Received Invalid WWN64 String from query: HPEVA_StorageSystem
2011-01-06 19:03:19,433 ERROR zen.WBEMClient: Received Invalid WWN64 String from query: HPEVA_StorageSystem
2011-01-06 19:03:21,721 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID=""} not found from query: HPEVA_StorageSystemStatisticalData
2011-01-06 19:03:21,721 ERROR zen.zenperfwbem: Device 5001438004C82C20: Received Invalid WWN64 String from query: HPEVA_StorageSystem
2011-01-06 19:03:32,396 ERROR zen.WBEMClient: Received Invalid WWN64 String from query: HPEVA_StorageSystem
2011-01-06 19:03:32,691 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID=""} not found from query: HPEVA_StorageSystemStatisticalData
2011-01-06 19:03:32,691 ERROR zen.zenperfwbem: Device 5001438004C83080: Received Invalid WWN64 String from query: HPEVA_StorageSystem
2011-01-06 19:03:34,370 ERROR zen.WBEMClient: Received Invalid WWN64 String from query: HPEVA_StorageSystem
2011-01-06 19:03:34,655 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID=""} not found from query: HPEVA_StorageSystemStatisticalData
2011-01-06 19:03:34,656 ERROR zen.zenperfwbem: Device 5001438004C732E0: Received Invalid WWN64 String from query: HPEVA_StorageSystem

I can add the devices but I can't model them. I have tried to uninstall the 2 zenpacks and reinstalling the again with alle the intermediate restarting of zenoss and zopectl but to no avail.

As I reinstalled on a new server I have also installed YAWN en ensured that I can connect to my HP CV, and I can do this with no problems.

Any good idears

WaltB

RE: HP EVA Monitor

community@zenoss.org — Tue, 18 Jan 2011 11:43:53 GMT

see below

RE: HP EVA Monitor

community@zenoss.org — Tue, 18 Jan 2011 11:44:54 GMT

Hi,

i can't get EVA model to complete successfuly.

I have made a successful WBEM connectivity test from zenoss linux server to a remote CV sevrer using wmic:

[zenoss@Test-zenoss root]$ wmic -U (DOMAIN/user%pass //x.x.x.x) "select Name from CIM_Processor"

CLASS: Win32_Processor

DeviceID|Name

CPU0|Intel(R) Pentium(R) III CPU family 1266MHz

So WBEM connectivity and remote credentials are ok.

I have configured CIM/HPEVA Class:

zWbemProxy: (x.x.x.x) - CV Server IP

zWinUser and pass: (CVadminAccount and password)

Added a device using WWN format: AAAA-BBBB-CCCC-DDDD

2011-01-18 12:21:36,102 INFO zen.ZenDisc: Connecting to localhost:8789

2011-01-18 12:21:36,116 INFO zen.ZenDisc: Connected to ZenHub

2011-01-18 12:21:36,154 INFO zen.ZenDisc: Looking for 5000-1FE1-5000-9570

2011-01-18 12:21:36,156 ERROR zen.ZenDisc: Error: [Failure instance: Traceback (failure with no frames): : No IP found for name 5000-1FE1-5000-9570]

2011-01-18 12:21:36,157 INFO zen.ZenDisc: Scan time: 0.00 seconds

2011-01-18 12:21:36,158 INFO zen.ZenDisc: Daemon ZenDisc shutting down

Job completed at 2011-01-18 12:21:37. Result: success.

Modelling this device:

2011-01-18 12:25:24,391 INFO zen.ZenModeler: Connecting to localhost:8789

2011-01-18 12:25:24,405 INFO zen.ZenModeler: Connected to ZenHub

2011-01-18 12:25:24,441 INFO zen.ZenModeler: Collecting for device 5000-1FE1-5000-9570

2011-01-18 12:25:24,504 INFO zen.ZenModeler: No WMI plugins found for 5000-1FE1-5000-9570

2011-01-18 12:25:24,507 INFO zen.ZenModeler: Python collection device 5000-1FE1-5000-9570

2011-01-18 12:25:24,507 INFO zen.ZenModeler: plugins: community.wbem.HPEVADeviceMap, community.wbem.HPEVAStorageDiskEnclosureMap, community.wbem.HPEVAStoragePoolMap, community.wbem.HPEVAStorageProcessorCardMap, community.wbem.HPEVAHostFCPortMap, community.wbem.HPEVADiskDriveMap, community.wbem.HPEVAConsistencySetMap, community.wbem.HPEVAStorageVolumeMap

2011-01-18 12:25:24,521 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageSystem

2011-01-18 12:25:24,534 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageSystem

2011-01-18 12:25:24,553 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StoragePool

2011-01-18 12:25:24,680 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageProcessorCard

2011-01-18 12:25:24,693 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: CIM_FCPort

2011-01-18 12:25:24,702 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_DiskModule

2011-01-18 12:25:24,717 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_ConsistencySet

2011-01-18 12:25:24,727 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_OrderedMemberOfCollection

2011-01-18 12:25:24,727 INFO zen.ZenModeler: No command plugins found for 5000-1FE1-5000-9570

2011-01-18 12:25:24,728 INFO zen.ZenModeler: SNMP monitoring off for 5000-1FE1-5000-9570

2011-01-18 12:25:24,729 INFO zen.ZenModeler: No portscan plugins found for 5000-1FE1-5000-9570

2011-01-18 12:25:24,739 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageControllerChassis

2011-01-18 12:25:24,747 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageDiskEnclosure

2011-01-18 12:25:24,761 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_DiskDrive

2011-01-18 12:25:24,772 ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageVolume

2011-01-18 12:25:24,774 INFO zen.PythonClient: Python client finished collection for 5000-1FE1-5000-9570

2011-01-18 12:25:24,774 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StoragePool

2011-01-18 12:25:24,775 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageProcessorCard

2011-01-18 12:25:24,775 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: CIM_FCPort

2011-01-18 12:25:24,776 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_ConsistencySet

2011-01-18 12:25:24,776 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageSystem

2011-01-18 12:25:24,777 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageControllerChassis

2011-01-18 12:25:24,777 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageSystem

2011-01-18 12:25:24,777 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageDiskEnclosure

2011-01-18 12:25:24,778 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_DiskModule

2011-01-18 12:25:24,778 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_DiskDrive

2011-01-18 12:25:24,779 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_OrderedMemberOfCollection

2011-01-18 12:25:24,779 ERROR zen.ZenModeler: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageVolume

2011-01-18 12:25:24,779 INFO zen.ZenModeler: No change in configuration detected

2011-01-18 12:25:24,803 INFO zen.ZenModeler: Scan time: 0.36 seconds

2011-01-18 12:25:24,812 INFO zen.ZenModeler: Daemon ZenModeler shutting down

Removed the device, and added again using WWN format: AAAABBBBCCCCDDDD

2011-01-18 12:28:36,630 INFO zen.ZenDisc: Connecting to localhost:8789

2011-01-18 12:28:36,644 INFO zen.ZenDisc: Connected to ZenHub

2011-01-18 12:28:36,682 INFO zen.ZenDisc: Looking for 50001FE150009570

2011-01-18 12:28:36,684 ERROR zen.ZenDisc: Error: [Failure instance: Traceback (failure with no frames): : No IP found for name 50001FE150009570]

2011-01-18 12:28:36,684 INFO zen.ZenDisc: Scan time: 0.00 seconds

2011-01-18 12:28:36,686 INFO zen.ZenDisc: Daemon ZenDisc shutting down

Job completed at 2011-01-18 12:28:37. Result: success.

Modelling produces the same output as in previous attempt.

CV version is 4.1.

I know you have tested this zenpack against CV 9.1 but i figured i could give it a try.Do you have an explicit list of supported/unsupported CV versions?

I'm not an EVA expert but i think i read somewhere in the web that CV versions prior to 6.x don't have root/eva namespace. Is that true, and if yes, could this be the cause?

Anyway, i tried to go into the zenpack resources on my zenoss server and find the script or part of the code where an actual WBEM query is executed, but i couldn't find any...

Could you please provide an sample WBEM class, or namespace (or the actual WQL query), that is being used by this zenpack so that i could use directly on the CV server in order to test does this qery produces any EVA specific output on the CV server itself.

thanks

marko

RE: HP EVA Monitor

community@zenoss.org — Tue, 18 Jan 2011 16:45:42 GMT

Hello,

I just installed Zenoss and trying to get EVA pack to work. It scans CV server without any problem it does find disks, controllers, volumes and it starts to monitor performance. Issue is that there is no hardware pictures and it only find 33 out 70 disks. It reports all the right sizes but ony 33 disks. Any idea what that might be?

RE: HP EVA Monitor

community@zenoss.org — Tue, 18 Jan 2011 19:38:29 GMT

Hi Marko,

why not to update CV? CIM classes names you can find in every modeler plugin (o.e HPEVA_DiskDrive, HPEVA_StoragePool, etc)

RE: HP EVA Monitor

community@zenoss.org — Tue, 18 Jan 2011 19:57:22 GMT

Hi Marciej,

i have no idea, you have provided not enough information about your system (EVA model, Storage Enclosure models, CV version, Zenoss version, versions of WBEMDataSource and HPEVAMon ZenPacks)

RE: HP EVA Monitor

community@zenoss.org — Tue, 18 Jan 2011 20:00:53 GMT

Thank you for replaying so quickly. I do have CV 9.2 on a server. I think I did solve this issue by updating WBEM porviders on HP server. I d/l file cp012930.exe from HP SPOCK and applied that. Re-model EVA and all appears working good. Thank you again for great tool.

RE: HP EVA Monitor

community@zenoss.org — Wed, 19 Jan 2011 02:07:12 GMT

Hello Egor,

I installed HP EVA monitor pack and that worked almost well. I just have a little problem with Model Device function. When I try to Model Device function after adding Device. It gives me this error message:

Exception while performing command:

Traceback (most recent call last):
  File "/opt/zenoss/Products/ZenUI3/browser/streaming.py", line 44, in __call__
    self.stream()
  File "/opt/zenoss/Products/ZenUI3/browser/command.py", line 144, in stream
    device.collectDevice(REQUEST=self.request, write=self.write)
  File "/opt/zenoss/Products/ZenModel/Device.py", line 1814, in collectDevice
    perfConf.collectDeviceself, setlog, REQUEST, generateEvents,
AttributeError: 'NoneType' object has no attribute 'collectDevice'

Best regards,
Slikki

RE: HP EVA Monitor

community@zenoss.org — Wed, 19 Jan 2011 08:06:42 GMT

Hi Marko,

why not to update CV? CIM classes names you can find in every modeler plugin (o.e HPEVA_DiskDrive, HPEVA_StoragePool, etc)

Bigegor,

1. i'm affraid we can't update CV as this is not our CV server, but from a customer. Upgrading CV is not yet considered here, we are only permitted to test this as the customer is showing *some* interest in zenoss, but far from making them upgrade their CV

2. if you are reffering to this for example

/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.9.egg/ZenPacks/community/HPEVAMon/modeler/plugins/community/wbem/HPEVADiskDriveMap.py

then i found something, thanks. And there is a confirmation that these classes come from root/eva namespace...

well, that makes my HP EVA zenpack testing on CV 4.1 impossible i guess.

I'll try to get bigger CV version for testing.

Thanks

RE: HP EVA Monitor

community@zenoss.org — Thu, 20 Jan 2011 16:15:03 GMT

Hello again,

I have run into a different problem (more like nuisance). I am runing Zenoss appliance 3.03 with EVA pack 1.9 and WBEM DataSource 2.10. Monitoring EVA 8100 running CV 9.2. Performance collection runs well everything is showing up as it should in a hardware display but all my interfaces, disks show up with a Down Status? Any idea why and can that be corrected?

RE: HP EVA Monitor

community@zenoss.org — Thu, 20 Jan 2011 18:49:06 GMT

Hi Maciej,

by 'interfaces' you mean FCPorts? By 'disks' you mean 'Virtual Disks' or 'Hard Disks'?

RE: HP EVA Monitor

community@zenoss.org — Thu, 20 Jan 2011 20:34:21 GMT

Interfaces are FCports correct but Virtual Disks and Hard disks are showing STATUS as DOWN and picture was red. Actually the magically came up green again since I did not do any work in Zenoss.

Maciej Glowacki

Systems Engineer

Oil States International, Inc.

Tel. +1.817.548.4214

Maciej.glowacki@oilstates.com

RE: HP EVA Monitor

community@zenoss.org — Thu, 20 Jan 2011 21:09:09 GMT

change zenperfwbem daemons log level to debug, restart it and check zenperfwbem.log file.

RE: HP EVA Monitor

community@zenoss.org — Fri, 21 Jan 2011 20:37:00 GMT

Thank you again. It appears that WBEM Data collector on Zenoss appliance stops working. Once WBEM DAEMON is restarted everything comes back online.

Question, do you have a plan to add Individual Disk Group Performance to your ZenPack? It would be awsome addition to already great tool.

RE: HP EVA Monitor

community@zenoss.org — Tue, 25 Jan 2011 07:57:01 GMT

Hi Marko,

why not to update CV?

bigegor,

what would be your opinion for supported CV versions for this zenpack, if you have any?

We would like to know this information to use when presenting zenoss and this zenpack to a HPEVA team.

Like for example "This zenpack supports/works-for CV versions X.Y or higher"

Since you are the author, you know best what technology specific utilities you have used so you can pinpoint what CV versions should comply with the zenpack and what versions wouldn't.

My contribution: since this zenpack queries root/eva namespace, this is what i have found on the net regarding CV versions and WBEM namespace compatibility:

http://user-techdocs.blogspot.com/2009/04/interoperability-namespace-list.html

PROVIDER INTEROP NAMESPACE

CommandView XP v2.0	root/xp
CommandView EVA v8.0	interop
CommandView EVA v6.0.2 CommandView EVA v4.1	root/pg_interop
CommandView EVA v.3.3 CommandView EVA v.3.1	root/EVA

On the other hand, one other monitoring tool specifies (it's) requirements like this:

OpStor monitors HP EVA based on the Command View EVA(CV EVA) version installed in your environment i.e.,

If the Command View EVA version installed is 4.0 / 5.0 then use SSSU command line utility available at
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp? prodNameId=1833644&lang=en&cc=us&prodTypeId=12169&prodSeriesId=471497&taskId=135
If the Command View EVA version installed is 6.0.2 and above then use SMI-S Provider available at
http://h20000.www2.hp.com/bizsupport/TechSupport/ProductList.jsp?
lang=en&cc=us&taskId=135&prodTypeId=12169&prodSeriesId=471497

So, acording to them versions above 6.0.2 use SMI-S provider = root/eva.

Is that a fact, or this is just a choice they made?

Please guys, add your findings regarding to zenpack - CV version compatibility

RE: HP EVA Monitor

community@zenoss.org — Tue, 25 Jan 2011 18:47:47 GMT

Hi Maciej,

EVA SMI-S provider, provides no performance data for Disk Groups (HPEVA_StoragePool class), so it's not possible to monitor Individual Disk Group Performance.

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 25 Jan 2011 18:58:08 GMT

Hi mlvaovic,

i think your table not 100% correct. CV 8.0 provides root/eva namespace, i think root/pg_interop is one of the standard Pegasus namespaces.

But here you can download SMI-S providers for CV 4.1.X and 5.X

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 25 Jan 2011 19:24:34 GMT

Thanks, I guess I was used to use Storage Essentials and that was there. Your zenpack does really nice job.

RE: HP EVA Monitor

community@zenoss.org — Mon, 31 Jan 2011 08:56:47 GMT

Hi mlvaovic,

i think your table not 100% correct. CV 8.0 provides root/eva namespace, i think root/pg_interop is one of the standard Pegasus namespaces.
But here you can download SMI-S providers for CV 4.1.X and 5.X

Egor

Hi Egor,

thanks for the feedback, okay, i found this table on the web and it could be wrong. It sounded like a mumbo-jumbo to me also but this was all i could find at that point.

Since this technology is strange to me (HP EVA, storage in general), i'm trying to compesate my lack of knowledge there by inspecting the underlying technologies i have some experience with (WBEM, WMI in general). My primary job is infrastructure management and handling management software in general. Yesterday network devices, today storage, tomorrow something else, if you understand me. I don't have a speciality in storage so when i'm trying to manage it and run into problems, then i'm really stuck. So i appreciate any help.

Didn't know i could upload SMI-S to my CV 4.1, i will consider this, thanks for the tip.

Will this register (missing) root/eva in my CV 4.1?

regards

marko

RE: HP EVA Monitor

community@zenoss.org — Mon, 31 Jan 2011 13:45:11 GMT

Egor,

This question might be of topic but you seem to be very knowledgeable about HP storage. Are you aware of any documents or tools to measure performance of HP P2000 G3 MSA SAN? BTW I am running Command View 9.3 now and your ZenPacks are working perfectly on 2x EVA 8100s and EVA4400.

Thank you,

RE: HP EVA Monitor

community@zenoss.org — Mon, 31 Jan 2011 16:46:23 GMT

Hi mlvaovic,

Since this technology is strange to me (HP EVA, storage in general), i'm trying to compesate my lack of knowledge there by inspecting the underlying technologies i have some experience with (WBEM, WMI in general). My primary job is infrastructure management and handling management software in general. Yesterday network devices, today storage, tomorrow something else, if you understand me.

i'm understanding

But I don't have CV 4.1, so i can't test this. Try it yourself.

Egor

RE: HP EVA Monitor

community@zenoss.org — Mon, 31 Jan 2011 16:53:22 GMT

Hi Maciej,

1. i'm NOT a HP (or any other vendor) Storage expert.

2. try SMI-S proxy Provider for Windows - HP StorageWorks 2000 Modular Smart Array

Egor

RE: HP EVA Monitor

community@zenoss.org — Thu, 03 Feb 2011 15:59:59 GMT

Hi mlvaovic,
Since this technology is strange to me (HP EVA, storage in general), i'm trying to compesate my lack of knowledge there by inspecting the underlying technologies i have some experience with (WBEM, WMI in general). My primary job is infrastructure management and handling management software in general. Yesterday network devices, today storage, tomorrow something else, if you understand me.
i'm understanding

But I don't have CV 4.1, so i can't test this. Try it yourself.

Egor

Egor,

i got a newer CV 8.0 (Win Server 2003 R2) to test with one EVA attached and finally i had some success!

Some tips and tricks:

1. SMI-S provider comes with CV and should be installed along with CV, if it wasn't, install it

2. even though SMI-S provider is installed (windows service "HP Storageworks CIM Object Manager" should be there and running), the root/eva namespace still isn't registered by default so we have to register it first by running a script located in <SMI-S install path>\SMI-S\EVAProvider\bin\RegisterEVAProvider.bat

3. after running the script, restart "HP Storageworks CIM Object Manager"win service

4. go to CommandView EVA GUI and install trust certificate (see this pdf, page 59 http://www.solarwinds.com/support/profiler/docs/SMISProvider.pdf )

6. verify you have root/eva namespace registered and functional by running some commands in command prompt:

PATH to command: <SMIS install folder>\ CXWSCimom\bin\

cxmofd.bat -h http://localhost -l username:password -n interop cim_namespace

this should output some stuff, but look for line

... Name = "root/eva"; // key ...

cxmofd.bat -h http://localhost -l username:password -n root/eva -i hpeva_storagesystem

this should give you some info on your storage pulled from root/eva namespace

7. go to your zenoss and add eva as described above in the instructions

I used WWN xxxx-xxxx-xxxx-xxxx format and it went okay as far as modelling goes.

RESULTS:

my EVA Storage system (only one EVA) was discovered okay and all static information and statuses, hardware picture and Device Perf graphs are okay. All static informations for all subcomponents are displayed ok, but some graphs are still NaN (after a few hours of monitoring)

Components graphs for FC Ports, Virtual Disks and Hard Disks are completely NaN, while i get graphs for Disk Groups and Controllers.

I'm trying now to understand why some graphs are empty. There are no alarms or events indicating a collection problem, everything is green, but still some graphs are missing.

I'm thinking several possible reasons:

a) since EVA is a VERY HUGE system, many components and instances (2 controllers, cca 100 virtual disks, cca 100 hard disks, etc) = many perf data to be collected. Maybe the collection interval is too small and zenoss never has a chance to pull the entire data set. How can i control the collection cycle time for EVA template? zCommandCycleTime property or what? Perhaps zCollectorClientTimeout=180 is too short in my case and it times out and never collects all perf data?

b) perhaps the difference between your CV 9.1 and my 8.0 CV is to blame? Maybe you built your Datapoint definitions compatibile to your SMI-S provider, while perhaps CV 8.0 SMI-S provider doesn't respond to the same WBEM queries (wrong WBEM classes perhaps)?

c) perhaps CV 8.0 SMI-S provider simply doesn't provide AT ALL some of those metrics you successfuly pulled in your case (e.g virtual disk write latency. I have a NaN there)? I can't find the way to test the WBEM locally on the server itself to verify a class exists and outputs data. I tried with wbemtest utility on the CV server but can't connect to root/eva namespace! It says "Invalid namespace"!!! But the namespace is definately there (as per point 6 above). HOW to query a root/eva namespace and get some EVA perf metrics on the server itself?

d) maybe something else should be configured on the Command View itself to make it provide the missing data? Something to enable/disable? Perhaps some perf data is simply deactivated somewhere?

e) perhaps i should have discovered my EVA with xxxxxxxxxxx WWN format instead of xxx-xxx-xxx-xxx?! I mean, modelling went fine without any error! But maybe it has some hidden problem there?!

Anyway, the Zenpack looks great, tons of stuff there, all statuses, a lot of graphs...excelent work!

I just have to make all my graphs to function.

Do you have any idea or some answers? Please answer my a) question at least, i need this info (how to increase collect cycle time)...

marko

RE: HP EVA Monitor

community@zenoss.org — Thu, 03 Feb 2011 16:17:50 GMT

i have this error when model the device

ERROR zen.WBEMClient: Received User zenoss is not authenticated/authorized to perform operation GetInstance from query: HPEVA_StorageSystem

RE: HP EVA Monitor

community@zenoss.org — Thu, 03 Feb 2011 16:23:03 GMT

Hi Marko,

try to run zenperfwbem daemon with DEBUG loging level : zenperfwbem run -v10 -d yourevaname

RE: HP EVA Monitor

community@zenoss.org — Thu, 03 Feb 2011 16:34:24 GMT

Hi tychocity,

check CV documentation, you user must be a member of HP Storage Users group or HP Storage Admins group.

RE: HP EVA Monitor

community@zenoss.org — Thu, 03 Feb 2011 17:17:35 GMT

yes the user is member of group HP Storage Admins.

RE: HP EVA Monitor

community@zenoss.org — Thu, 03 Feb 2011 17:22:13 GMT

can you login on CV as 'zenoss' user?

RE: HP EVA Monitor

community@zenoss.org — Fri, 04 Feb 2011 10:20:53 GMT

yes and and also if I tried it with the adminstrator user and both give me the same error

RE: HP EVA Monitor

community@zenoss.org — Fri, 04 Feb 2011 12:10:58 GMT

yes and and also if I tried it with the adminstrator user and both give me the same error

I'm using local CV administrator user (member of Administrators = member of HP Storage Admins and HP Storage Users groups). Administrator by deafult should have all required permissions to view and access and remote access to WMI. If someone messed this up, then man you're in trouble

Zenoss user (even though you made it HP Storage Admins member) doesn't by default have permissions to access WMI remotely i guess (unless it is also an Administrators member)

On top of that, my Zenoss is not local to CV server so i have to go through firewalls. Firewall needs to be open, we opened all TCP ports >= 1024between Zenoss and CV server.

RE: HP EVA Monitor

community@zenoss.org — Fri, 04 Feb 2011 12:21:13 GMT

the cv is a w2k3 server , but no firewall activated.

nmap of cv server

PORT STATE SERVICE

21/tcp open ftp

135/tcp open msrpc

139/tcp open netbios-ssn

445/tcp open microsoft-ds

860/tcp open unknown

1025/tcp open NFS-or-IIS

1027/tcp open IIS

1032/tcp open iad3

1033/tcp open netinfo

2008/tcp open conf

2105/tcp open eklogin

3389/tcp open ms-term-serv

RE: HP EVA Monitor

community@zenoss.org — Fri, 04 Feb 2011 12:44:39 GMT

Hi Marko,
try to run zenperfwbem daemon with DEBUG loging level : zenperfwbem run -v10 -d yourevaname

Egor, i did that and the debug output is HUGE

Okay, what am i looking for in there? It seems okay on the first glance.... The whole process took about 20+ seconds so i guess there IS enough time for collector to gather all it can from EVA. But still, how can i modify WBEM cycle time anyway? What is the current cycle? 5 minutes?

the debug output is to big to post here of course but after some inspecting and greping, I filterred out (for what i think is a final proof of a particualr metric being gathered and processed by the graphing mechanism) only the *Latency* metrics:

2011-02-04 08:49:24,511 DEBUG zen.RRDUtil: /usr/local/zenoss/zenoss/perf/Devices/5000-1FE1-500F-4220/hw/cards/50001FE1500F4220.PBA23F29SW104T/StatisticalData_ReadLatencyTime.rrd: 163365662L

2011-02-04 08:49:24,512 DEBUG zen.RRDUtil: /usr/local/zenoss/zenoss/perf/Devices/5000-1FE1-500F-4220/hw/cards/50001FE1500F4220.PBA23F29SW104T/StatisticalData_WriteLatencyTime.rrd: 37810200L

2011-02-04 08:49:24,655 DEBUG zen.RRDUtil: /usr/local/zenoss/zenoss/perf/Devices/5000-1FE1-500F-4220/hw/cards/50001FE1500F4220.PBA23F29SVY008/StatisticalData_ReadLatencyTime.rrd: 147263125L

2011-02-04 08:49:24,656 DEBUG zen.RRDUtil: /usr/local/zenoss/zenoss/perf/Devices/5000-1FE1-500F-4220/hw/cards/50001FE1500F4220.PBA23F29SVY008/StatisticalData_WriteLatencyTime.rrd: 259342525L

this matches my 2 Controller cards serial numbers and their Read/Write Latencies which are graphed okay.

I can't find such lines for FC Ports, Virtual disks and Hard disks Latencies (which are not graphed anyway) so i guess this indicates Zenoss didn't FIND those values on the CV, right?

Okay, i need Latency metrics for disks, how can i troubleshoot this? How can i check on CV localy that those values are available through root/eva namespace?

Is the root cause for this problem somewhere in Zenoss, somewhere in the data transfer or localy on the CV?

RE: HP EVA Monitor

community@zenoss.org — Fri, 04 Feb 2011 14:13:07 GMT

Use

netstat -a

to see if you have SMI provider LISTENING on ports 5988 and 5989

.....

TCP <CVSERVER>:5988 <CVSERVER>:0 LISTENING
TCP <CVSERVER>:5989 <CVSERVER>:0 LISTENING

....

If not, make sure SMI-S is installed, root/eva is registered and SMI-S is up and running on those ports.

marko

RE: HP EVA Monitor

community@zenoss.org — Sat, 05 Feb 2011 23:46:28 GMT

Hello bigegor,

I'm using Zenoss 3.0.3., HPEVAMon-1.9 and WBEMDataSource 2.10. When I am adding new device and trying to Model Device, there comes this kind of errormessage:

Traceback (most recent call last):
  File "/opt/zenoss/Products/ZenUI3/browser/streaming.py", line 44, in __call__
    self.stream()
  File "/opt/zenoss/Products/ZenUI3/browser/command.py", line 144, in stream
    device.collectDevice(REQUEST=self.request, write=self.write)
  File "/opt/zenoss/Products/ZenModel/Device.py", line 1814, in collectDevice
    perfConf.collectDevice(self, setlog, REQUEST, generateEvents,
AttributeError: 'NoneType' object has no attribute 'collectDevice'


Links from Zenoss to Command View EVA is working properly. Have you any clue what this error might mean and how to fix it?

-Slikki

RE: HP EVA Monitor

community@zenoss.org — Sun, 06 Feb 2011 22:47:34 GMT

Hi Marko,

1. change 'SNMP Performance Cycle Interval' property, if you want modify WBEM cycle interval (i know it's not a perfect solution)

2. Try to isolate a problem. Rename all HPEVA* templates except HPEVAHostFCPort and run zenperfwbem with -v10 option.

Egor

RE: HP EVA Monitor

community@zenoss.org — Sun, 06 Feb 2011 22:54:00 GMT

Hi slikki,

1. restart Zenoss after installing ZenPacks

2. you must add your EVA device to /Devices/CIM/HPEVA device class.

Egor

RE: HP EVA Monitor

community@zenoss.org — Mon, 07 Feb 2011 12:03:17 GMT

egor,

Hi Marko,

1. change 'SNMP Performance Cycle Interval' property, if you want modify WBEM cycle interval (i know it's not a perfect solution)

If you are reffering to CIM/HPEVA performance template -> Configuration properties, then there is no such zProperty!

Here are all available SNMPxxx properties:

zSnmpAuthPassword	password	/
zSnmpAuthType	string	/
zSnmpCommunities	lines	/
zSnmpCommunity	string	/
zSnmpMonitorIgnore	boolean	/CIM/HPEVA
zSnmpPort	int	/
zSnmpPrivPassword	password	/
zSnmpPrivType	string	/
zSnmpSecurityName	string	/
zSnmpTimeout	float	/
zSnmpTries	int	/
zSnmpVer

2. Try to isolate a problem. Rename all HPEVA* templates except HPEVAHostFCPort and run zenperfwbem with -v10 option

Do you mean, rename them in GUI or where? Go to Advanced->Monitoring Templates, pick a HPEVAxxx template and then choose "View and edit details" and change the name of the tamplete in the "name" field?

What will that achieve? Can I make some damage that way?

After i do that, how this will help me after i run

zenperfwbem with -v10 ?

marko

RE: HP EVA Monitor

community@zenoss.org — Mon, 07 Feb 2011 15:53:23 GMT

Hi Marko,

1. http://yourzenossserver:8080/zport/dmd/Monitors/Performance/localhost/editPerformanceConf , note that you also need to change 'Default RRD Create Command'.

2.1. the safest way is to use ZMI for template renaming

2.2. Zenoss will bind components templates based on templates name. So template renaming is simplest way to disable components from monitoring.

2.3. after testing you can rename templates back.

2.4. debug output will be much shorter.

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 08 Feb 2011 09:25:48 GMT

1. OK, i found it

2. OK, i did it, only the HPEVAHostFCPort template was processed (and Device template of course, i didn't dare to change the name of this one ). After running

zenperfwbem run -v10 -d <EVADevice>

the resulting log file is here:

https://docs.google.com/leaf?id=0B40Sd-yGeiktOWI4NGI2YzktMTc1YS00ZjM2LWIwYWItYmVmOGQ1ZTIzODYw&hl=en&authkey=CNHBjqwP

Please advise on the next steps....

I don't understand the root cause:

1) either your template is aiming at a wrong WBEM class (*wrong* related to my particular CV version)

2) or the class is right but my CV SMI-S provider provides no such data???

RE: HP EVA Monitor

community@zenoss.org — Tue, 08 Feb 2011 10:09:11 GMT

OK, i was playing around on CV server with SMI-S command

cxmofd.bat -h http://localhost -l username:password -n root/eva -i hpeva_storagesystem

i tried guessing several other hpeva classes and found something interesting:

for example

C:\Program Files\Hewlett-Packard\SMI-S\CXWSCimom\bin>cxmofd.bat -h http://localhost -l <user:pass> -n root/eva -i hpeva_storagesystemstatisticaldata

results in:

// enumerating "root\\eva:hpeva_storagesystemstatisticaldata"
// 15954 bytes
instance of HPEVA_StorageSystemStatisticalData as $hpeva_storagesystemstatisticaldata0
{
    Description = "EVA System level metrics for: 50001FE1500F4220";
    ElementName = "50001FE1500F4220";
    InstanceID = "50001FE1500F4220";    // key
    StartStatisticTime = "20110208095428.697000+060";
    StatisticTime = "20110208105613.489000+060";
    SampleInterval = "00000000000000.000000:000";
    ElementType = 2;
    TotalIOs = 10209701;
    KBytesTransferred = 181979705;
};

okay, so now i know there is an hpeva_storagesystem and hpeva_storagesystemstatisticaldata classes available.

doing the same for HostFCPorts:

C:\Program Files\Hewlett-Packard\SMI-S\CXWSCimom\bin>cxmofd.bat -h http://localhost -l <user:pass> -n root/eva -i hpeva_hostfcport

produces:

// enumerating "root\\eva:hpeva_hostfcport"
// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport0
{
    Caption = "hostport1";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller A.hostport1";
    Name = "50001FE1500F4228";
    OperationalStatus = { 2 };
    Status = "good";
    EnabledState = 5;
    RequestedState = 12;
    EnabledDefault = 2;
    SystemCreationClassName = "HPEVA_StorageProcessorSystem";   // key
    SystemName = "50001FE1500F4220.PBA23F29SVY008";     // key
    CreationClassName = "HPEVA_HostFCPort";     // key
    DeviceID = "50001FE1500F4228";      // key
    Speed = 4250000000;
    MaxSpeed = 2125000000;
    UsageRestriction = 2;
    PortType = 10;
    LinkTechnology = 4;
    PermanentAddress = "50001FE1500F4228";
    NetworkAddresses = { "010000" };
    FullDuplex = true;
    SupportedFC4Types = { 8 };
    ActiveFC4Types = { 8 };
};

and so on....

Next i realised there must be a class hpeva_hostfcportstatisticaldata

but hey, i see in zenperfwbem log (the one i provided a link for) that the class being queried by HPEVA template is

... '50001FE1500F422E_HPEVAHostFCPort_StatisticalData': [] ...

there is an uderscore '_' there. Maybe this is a problem with my CIM classes?

anyway, running

C:\Program Files\Hewlett-Packard\SMI-S\CXWSCimom\bin>cxmofd.bat -h http://localhost -l <user:pass> -n root/eva -i hpeva_hostfcport_statisticaldata

produces:

// "root\\eva:hpeva_hostfcport_statisticaldata": CIM_ERR_NOT_FOUND
"root\\eva:hpeva_hostfcport_statisticaldata": CIM_ERR_NOT_FOUND
Class hpeva_hostfcport_statisticaldata not found

while running without underscore:

C:\Program Files\Hewlett-Packard\SMI-S\CXWSCimom\bin>cxmofd.bat -h http://localhost -l <user:pass> -n root/eva -i hpeva_hostfcportstatisticaldata

produces:

// enumerating "root\\eva:hpeva_hostfcportstatisticaldata"
// 17739 bytes
instance of HPEVA_HostFCPortStatisticalData as $hpeva_hostfcportstatisticaldata0
{
    Description = "EVA HostFCPort level metrics for 50001FE1500F4220";
    ElementName = "hostport2";
    InstanceID = "50001FE1500F4220.PBA23F29SW104T.2";   // key
    StartStatisticTime = "20110208095427.541000+060";
    StatisticTime = "20110208110244.399000+060";
    SampleInterval = "00000000000000.000000:000";
    ElementType = 6;
    TotalIOs = 407047;
    KBytesTransferred = 7794025;
    KBytesWritten = 4071161;
    ReadIOs = 230246;
    KBytesRead = 3722864;
    WriteIOs = 176801;
    ReadLatencyTime_ms = 891777;
    WriteLatencyTime_ms = 197516;
    QDepth = 0;
    Losig = 0;
    Badrxchar = 0;
    Losync = 0;
    LinkFail = 0;
    ProtErr = 0;
    Rxeofa = 0;
    Disfrm = 0;
    BadCRC = 0;
};

And there is the LATENCY

So, i guess this is a case where your HPEVA template is working fine for your version (CV 9.1) but there are some differencies in CIM class names regarding other versions.

What do you think, i'm i on the right track here? could those class name differencies be the root cause?

If so, where in your template (resources) could i go and change the class names (remove the underscore)?

Please healp me as this is rather urgent and very important!

thanks

RE: HP EVA Monitor

community@zenoss.org — Tue, 08 Feb 2011 11:00:38 GMT

Hi Marko,

change Query in 'StatisticalData' data source in 'HPEVAHostFCPort' template from:

HPEVA_HostFCPortStatisticalData.InstanceID="${device/snmpSysName}.${here/id}"

to:

HPEVA_HostFCPortStatisticalData.InstanceID="${device/snmpSysName}.${here/id}.2"

RE: HP EVA Monitor

community@zenoss.org — Tue, 08 Feb 2011 12:21:29 GMT

Hi Marko,

1. http://yourzenossserver:8080/zport/dmd/Monitors/Performance/localhost/editPerformanceConf

OK, currently 'SNMP Performance Cycle Interval' is set to 300 (seconds=5 minutes)

note that you also need to change 'Default RRD Create Command'.

I don't understand this part. Change to what values?

Currenly these are set to:

RRA:AVERAGE:0.5:1:600
RRA:AVERAGE:0.5:6:600
RRA:AVERAGE:0.5:24:600
RRA:AVERAGE:0.5:288:600
RRA:MAX:0.5:6:600
RRA:MAX:0.5:24:600
RRA:MAX:0.5:288:600

I don't understand the connection between those two things! Please be more specific.

If i change 'SNMP Performance Cycle Interval' property to X, what do i have to change in RDD commands?

RE: HP EVA Monitor

community@zenoss.org — Tue, 08 Feb 2011 13:53:24 GMT

Hi Marko,

change Query in 'StatisticalData' data source in 'HPEVAHostFCPort' template from:
HPEVA_HostFCPortStatisticalData.InstanceID="${device/snmpSysName}.${here/id}"
to:
HPEVA_HostFCPortStatisticalData.InstanceID="${device/snmpSysName}.${here/id}.2"

added .2 but this didn't help.

Okay, i'm loosing it here. Now for some reason all my graphs stopped! (however, it's not connected to this change)

I thought this zenpack was great and all issues will go away after a few posts here, but since i have more and more problems and i can only rely on you to help me, i would really appreciate if you could answer more deeply.

for example, if i add ".2" there, what the hell did i just do?! It's not helping anyway...

If you spare some more time to explain why, i could re-use this understanding and bother you no more, but your answers aim at "fast resolution per-issue" rather than providing enough info for me to get some understanding and try to help myself...

I think the problem lies in class names differencies but i can't find, or i don't know where to look for, the basic mechanism where your zenpack actually calls/uses CIM classes. Okay, i went to WBEMDataSource zenpack, but couldn't link my problem there either.

if i don't start graphing HPEVA performance soon, my management will drop the idea of using zenoss....

RE: HP EVA Monitor

community@zenoss.org — Tue, 08 Feb 2011 18:38:09 GMT

Hi Marko,

1. here http://community.zenoss.org/message/50041#50041 you can read about 'Performance Cycle Interval' changing and 'Default RRD Create Command' property.

2. is looks like in CV 8.x and 9.x was changed 'InstanceID' format for Statistical data, but first of all a little bit of theory.

As Query in WBEMDataSource you can use instance names of CIM class. instance name has format:

HPEVA_HostFCPort.SystemCreationClassName="HPEVA_StorageProcessorSystem",SystemName="50001FE1500F4220.PBA23F29SVY008",CreationClassName="HPEVA_HostFCPort",DeviceID="50001FE1500F4228"

where:

class name is: HPEVA_HostFCPort

keybindings is SystemCreationClassName="HPEVA_StorageProcessorSystem",SystemName="50001FE1500F4220.PBA23F29SVY008",CreationClassName="HPEVA_HostFCPort",DeviceID="50001FE1500F4228"

as you can see, keybindings is a dictionary of key properties (marked with '// key' in your examples) with values.

So, to get performace data you must specify correct class name and key properies with corresponded values of Statistical data class instance. In your case:

HPEVA_HostFCPortStatisticalData.InstanceID = "50001FE1500F4220.PBA23F29SW104T.2"

in CV 9.x InstanceID has format: evaWWN.fcPortWWN,

but in CV 8.x it looks like: evaWWN.controllerSerialNumber.portNumber

to solve this problem you must calculate correct InstanceID, try use this as Query in HPEVAHostFCPort Template:

python:"HPEVA_HostFCPortStatisticalData.InstanceID=\"%s.%s\""%(here.getController().id, here.interfaceName[-1])

sorry, i can not test this right now , but i hope you have enough information to solve your problems. To your manager you can say, that CV version 9.x. is required for this ZenPack.

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 09 Feb 2011 08:41:18 GMT

egor,

1. ok, got it

2. ok, things are MUCH MUCH clearer now! this is what i needed: to understand a (logical) link between a technology and your zenpack. Now i understand where i can try changing things to get it right. thanks egor, i'll play for a while and let you know.

One more thing.

On my CV server, root/eva namespace is registered and is certainly there (otherwise this zenpack couldn't work at all on my CV). However, i used several WMI tools and utilities (wbemtest, wmic, WMI Object Browser from MS WMI Tools package, etc.) and NONE of them can *see* root/eva namespace!!!

I really don't understand that: how can root/eva NOT be there, but also it's there?!

I was hoping i could browse through this namespace (outside zenoss) and find additional metrics perhaps, or simply find out more about HPEVA CIM structure so that i can correct problems like this InstanceID we have up there.

Example (namespace list via wmic on my CV 8.0):

wmic:root\cli>/NAMESPACE:\\root
wmic:root\cli>path __NAMESPACE get Name

Name
ServiceModel
SECURITY
perfmon
RSOP
Cli
aspnet
snmp
MSCluster
WMI
CIMV2
MicrosoftActiveDirectory
Policy
MicrosoftNLB
Microsoft
DEFAULT
directory
subscription

There is no eva namespace. but using SMI-S utilities i can definately prove this namespace is registered available somehow....

Is there any other way i can see the root/eva CIM structure on my CV server? I couldn't find any useful doc on the net either (describing the structure of eva namespace)

regards

marko

RE: HP EVA Monitor

community@zenoss.org — Wed, 09 Feb 2011 18:20:33 GMT

Hi Marko,

CV doesn't used WMI CIMOM it, has its own CIMOM (CXWS).

RE: HP EVA Monitor

community@zenoss.org — Thu, 10 Feb 2011 09:40:05 GMT

egor,

CV doesn't used WMI CIMOM it, has its own CIMOM (CXWS).

OK,now i understand that. So how can i verify that i'm getting the right CV values to zenoss? The only "utility" i could find is this cxmofd.bat script, i'm using it to query eva classes. Let me explain:

Zenoss reports (modells) my EVA system like this:

1 EVA WWN

-> 2 controllers (A and B)

-> 16 FC ports:

------> ControllerA has 8

------> ControllerB has 8

-> Disk groups, Hard disks, etc

Lets see the FC ports. for each controller i have 8 FC ports:

4 with InterfaceName like "hostport1", "hostport2", "hostport3", "hostport4" (type=N)

4 with InterfaceName like "looppair1loopa", "looppair1loopb", "looppair2loopa", "looppair2loopb" (type=NL)

So using your clarification in earlier posts, i made a change in DataSource and got the right InstanceID and managed to get the graphs for FC ports, but only for those with interface names like "hostportX".

Hmmm....let me check on my CV what kind of FC ports i have (i reduced some of the lines):

C:\Program Files\Hewlett-Packard\SMI-S\CXWSCimom\bin>cxmofd.bat -h http://localhost -l <user:pass> -n root/eva -i HPEVA_HostFCPort

// enumerating "root\\eva:HPEVA_HostFCPort"
// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport0
{
    Caption = "hostport1";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller A.hostport1";
    Name = "50001FE1500F4228";
    ...
};

// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport1
{
    Caption = "hostport2";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller A.hostport2";
    Name = "50001FE1500F4229";
    ...
};

// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport2
{
    Caption = "hostport3";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller A.hostport3";
    Name = "50001FE1500F422A";
    ...
};

// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport3
{
    Caption = "hostport4";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller A.hostport4";
    Name = "50001FE1500F422B";
    ...
};

// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport4
{
    Caption = "hostport1";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller B.hostport1";
    Name = "50001FE1500F422C";
    ...
};

// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport5
{
    Caption = "hostport2";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller B.hostport2";
    Name = "50001FE1500F422D";
    ...
};

// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport6
{
    Caption = "hostport3";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller B.hostport3";
    Name = "50001FE1500F422E";
    ...
};

// 49525 bytes
instance of HPEVA_HostFCPort as $hpeva_hostfcport7
{
    Caption = "hostport4";
    ElementName = "\\Hardware\\Rack 1\\Controller Enclosure 5\\Controller B.hostport4";
    Name = "50001FE1500F422F";
    ...
};

So here we have all those 8 FC ports with interface names like "hostportX" (4 for controllerA and 4 for controllerB). But there are no "looppairXloopY" FC ports!!! I'm confused! Why are they missing? Where the heck did they come from and got listed in Zenoss!!!???

So now i'm not so sure wheather my EVA modell is correct or not!

What tool do you use to cross-check eva objects on CV server?

RE: HP EVA Monitor

community@zenoss.org — Thu, 10 Feb 2011 10:07:35 GMT

python:"HPEVA_HostFCPortStatisticalData.InstanceID=\"%s.%s\""%(here.getController().id, here.interfaceName[-1])
sorry, i can not test this right now , but i hope you have enough information to solve your problems.

this actually worked (but only for my InterfaceName like "hostportX" FC ports).

Okay, now using this example from you, and the theory lesson , i got my hands on trying to correct InstanceID construction for Hard Disks and Virtual Disks (also no graphs => also wrond key bindings).

And i wasn't so successful. I don't quite understand this simbolic substitution using {here.X}

If i click on Dard disk, is {here} a selected harddisk or {here} is the entire device (wwn)?

what is the difference between {here.snmpSysName} and {here.snmpIndex}?

Why we sometimes use {here.snmpSysName} and sometimes {here/interfaceName} (a dot "." and a slash "/")?

Is {here.snmpSysName} always equal to EVAWWN? or it depends on the context?

how did you know that you can use "here.getController().id and "here.interfaceName"?

I went to HPEVAHardDisk.py and found some functions there (getEnclosureName and getEnclosure) and some properties there (bay) so i figured i must probably use those...

Because for HardDisks to correct the key bindings, i have to use:

EVAWWN.Enclosure.Bay

Query in HPEVADiskDrive template was:

HPEVA_DiskDriveStatisticalData.InstanceID="${here/snmpindex}"

and i tried:

python:"HPEVA_DiskDriveStatisticalData.InstanceID=\"%s.%s.%s\""%(here.snmpSysName, here.getEnclosureName(), here.bay)

and it WORKS!!!

But this was more a lucky shot than true understanding.

I still have to correct Virtual disk DeviceID calculation and this is going to be a problem for me...

Please help....

I know i'm the pain in the a*ss but i really need this thing to work...

I'll post a fresh post for virtual disk...

RE: HP EVA Monitor

community@zenoss.org — Thu, 10 Feb 2011 10:22:52 GMT

Egor

to correct the virtual disks DeviceID calculation i need your help as key binding is a bit more complicated:

Current HPEVAStorageVolume is:

HPEVA_VolumeStatisticalData.InstanceID="${here/id}"

But, using cxmofd.bat script i get this:

instance of HPEVA_VolumeStatisticalData as $hpeva_volumestatisticaldata95

{

Description = "EVA VDisk level metrics for 50001FE1500F4220";

ElementName = "6005-08B4-0009-6027-0000-7000-03A0-0000";

InstanceID = "50001FE1500F4220.5C200710B408056027600900007000000000A003"; // key EVAWWN.storageVolumeDeviceID

StartStatisticTime = "20110208150906.048000+060";

StatisticTime = "20110209151212.782000+060";

SampleInterval = "00000000000000.000000:000";

ElementType = 8;

TotalIOs = 4216;

KBytesTransferred = 152020;

KBytesWritten = 21146;

ReadIOs = 4214;

ReadHitIOs = 0;

KBytesRead = 4214;

WriteIOs = 2;

ReadHitKBytes = 0;

ReadHitLatencyTime_ms = 0;

ReadMissRequests = 4214;

ReadMissKBytes = 130874;

ReadMissLatencyTime_ms = 30299;

WriteLatencyTime_ms = 4;

FlushRequests = 0;

FlushKBytes = 18930;

MirrorKBytes = 43655;

PrefetchKBytes = 0;

WriteMode = "1";

OnlineToControllerNum = "1";

MirrorState = "1";

GroupId = "1";

};

So the key is EVAWWN.storageVolumeDeviceID

StorageVolumeDeviceID (for this instance) is from a different class:

instance of HPEVA_StorageVolume as $hpeva_storagevolume47
{
    Caption = "Solaris\\ZU_ARHIVA";
    ElementName = "50001FE1500F4220\\\\Virtual Disks\\Solaris\\ZU_ARHIVA\\ACTIVE";
    InstallDate = "20090902134124.000000+120";
    Name = "600508B4000960270000700003A00000";
    OperationalStatus = { 2 };
    StatusDescriptions = { "operating_normally" };
    Status = "good";
    HealthState = 5;
    EnabledState = 5;
    RequestedState = 12;
    EnabledDefault = 2;
    SystemCreationClassName = "HPEVA_StorageSystem";    // key
    SystemName = "50001FE1500F4220";    // key
    CreationClassName = "HPEVA_StorageVolume";    // key
    DeviceID = "5C200710B408056027600900007000000000A003";    // key
    Access = 3;
    BlockSize = 512;
    NumberOfBlocks = 2147483648;
    ConsumableBlocks = 2147483648;
    IsBasedOnUnderlyingRedundancy = false;
    SequentialAccess = false;
    ExtentStatus = { 0 };
    NoSinglePointOfFailure = true;
    DataRedundancy = 1;
    PackageRedundancy = 1;
    DeltaReservation = 0;
    Primordial = false;
    NameFormat = 1;
    NameNamespace = 2;
    RaidType = "vraid5";
    RaidLevel = "vraid5";
    DiskGroupID = "01010710B4080560882409000070000000003800";
    Comment = "";
    VDiskType = "original";
    WriteCachePolicy = "writeback";
    ReadCachePolicy = "enable";
    WriteProtect = "disable";
    OsUnit = 0;
    CreatedTime = "02-Sep-2009 13:41:24";
    PreferredPath = "no_preference";
    MirrorCache = "mirrored";
    CapacityRequested = "1024";
    AllocatedBlocks = 2147483648;
};

So, i don't know where to get Storage Volume DeviceID to pass to HPEVA_VolumeStatisticalData.

In HPEVAStoragevolume.py there are methods getStoragePool() and getDRGroup() and i need StorageVolumeID.

Any ideas?

RE: HP EVA Monitor

community@zenoss.org — Thu, 10 Feb 2011 15:02:48 GMT

Hi Marko,

python:"HPEVA_VolumeStatisticalData.InstanceID=\"%s.%s\""%tuple(eval('(lambda **kwargs: kwargs)(%s)'%here.snmpindex.split('.')[1]).values()[1:3])

RE: HP EVA Monitor

community@zenoss.org — Thu, 10 Feb 2011 15:23:46 GMT

Hi Marko,

And i wasn't so successful. I don't quite understand this simbolic substitution using {here.X}
If i click on Dard disk, is {here} a selected harddisk or {here} is the entire device (wwn)?

{here} is current context. if you will bind template to device, then {here} = device, if you bind template to some component, then {here} = component, if you want address device in components template use {device/attribute}.

what is the difference between {here.snmpSysName} and {here.snmpIndex}?

ONLY in this ZenPack:

{here.snmpSysName} - EVAs WWN
{here.snmpindex} - components instance name

Why we sometimes use {here.snmpSysName} and sometimes {here/interfaceName} (a dot "." and a slash "/")?

"/" - used in TAL class notation

"." - used in python class notation

Is {here.snmpSysName} always equal to EVAWWN? or it depends on the context?

always. But better use {device/snmpSysName}

how did you know that you can use "here.getController().id and "here.interfaceName"?

i'm author of this ZenPack.

OK,now i understand that. So how can i verify that i'm getting the right CV values to zenoss? The only "utility" i could find is thiscxmofd.bat script, i'm using it to query eva classes. Let me explain:

i'm using YAWN

Egor

RE: HP EVA Monitor

community@zenoss.org — Fri, 11 Feb 2011 08:58:30 GMT

Hi Marko,
python:"HPEVA_VolumeStatisticalData.InstanceID=\"%s.%s\""%tuple(eval('(lambda **kwargs: kwargs)(%s)'%here.snmpindex.split('.')[1]).values()[1:3])

Egor,

this is not working

Left it for an hour but still graphs are NaN

any other idea?

RE: HP EVA Monitor

community@zenoss.org — Fri, 11 Feb 2011 09:08:41 GMT

if you want address device in components template use {device/attribute}.

Egor,

what are available /attributes? The ones i see in zenoss:

e.g. in VirtualDisks component table view, "Name", "Disk Group", "Disk type" etc. ?

or the ones registered in component .py class?

i'm author of this ZenPack.

of course...thanks for this good answer

i'm using YAWN

Will try that. YAWN can "see" root/eva namespace?

Anyway, thank you very much for these answers on {here} questions, i understand this better now.

marko

RE: HP EVA Monitor

community@zenoss.org — Fri, 11 Feb 2011 21:50:42 GMT

Marko,

Left it for an hour but still graphs are NaN

any other idea?

run zendmd as zenoss user.

here = find('youreva').os.virtualdisks()[0]
print here.snmpindex
print "HPEVA_VolumeStatisticalData.InstanceID=\"%s.%s\""%tuple(eval('(lambda **kwargs: kwargs)(%s)'%here.snmpindex.split('.')[1]).values()[1:3])

what are available /attributes? The ones i see in zenoss:
e.g. in VirtualDisks component table view, "Name", "Disk Group", "Disk type" etc. ?

1. ZMI

2. in zendmd: find('youreva').os.virtualdisks()[0].__dict__

3. source code

Will try that. YAWN can "see" root/eva namespace?

yes

Egor

RE: HP EVA Monitor

community@zenoss.org — Mon, 14 Feb 2011 08:34:28 GMT

egor,

run zendmd as zenoss user.
here = find('youreva').os.virtualdisks()[0]
print here.snmpindexIt seens
print "HPEVA_VolumeStatisticalData.InstanceID=\"%s.%s\""%tuple(eval('(lambda **kwargs: kwargs)(%s)'%here.snmpindex.split('.')[1]).values()[1:3])

I have done this as you proposed and indeed, InstanceID is constructed okay:

>>> here = find('50001FE1500F4220').os.virtualdisks()[0]

>>> print here.snmpindex

root/eva:HPEVA_StorageVolume.CreationClassName="HPEVA_StorageVolume",

SystemName="50001FE1500F4220",DeviceID="00200710B4080560276009000070000000001000",SystemCreationClassName="HPEVA_StorageSystem"

>>>print "HPEVA_VolumeStatisticalData.InstanceID=\"%s.%s\""%tuple(eval('(lambda **kwargs: kwargs)(%s)'%here.snmpindex.split('.')[1]).values()[1:3])

HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.00200710B4080560276009000070000000001000"

However, graphs are still NaN, something else is obviously bugging VirtualDisks graphs then.

At least now we know InstanceID is well constructed (i guess).

what are available /attributes? 
The ones i see in zenoss,
e.g. in VirtualDisks component table view, "Name", "Disk Group", "Disk type" etc. ?
1. ZMI
2. in zendmd: find('youreva').os.virtualdisks()[0].__dict__
3. source code

Cool, thanks.

Will try that. YAWN can "see" root/eva namespace?
yes

Do you have YAWN installed on Zenoss server?

Is there any problem installing YAWN on zenoss server (because prereq for YAWN are python and apache and stuff like that - i don't want to break zenoss by installing YAWN)?

marko

RE: HP EVA Monitor

community@zenoss.org — Mon, 14 Feb 2011 19:43:41 GMT

Hi Marko,

yes, you can install YAWN on the same server and it doesn't break your zenoss install.

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 15 Feb 2011 14:56:08 GMT

egor

1. can you help me install YAWN? I have downloaded yawn-1.0-19.1.noarch.rpm file from http://download.opensuse.org/repositories/systemsmanagement:/wbem/CentOS_CentOS-5/noarch/

but i'm not sure if this will install everything i need (apache with mod-python, python-pywbem etc.).

Looking at the poor instructions on http://sourceforge.net/apps/mediawiki/pywbem/index.php?title=YAWN i see only the SUSE linux example, and my zenoss is on CentOS....so i'm not sure how to proceed.

Also, this confuses me: it says i have to install apache http server for YAWN. Don't i already have an HTTP server on zenoss? I mean, zenoss provides a web GUI so there must be an HTTP server on zenoss server right?

Anyway, if you could point me in the right direction here, what exactly to download and order of steps to proceed?

2. Regarding VirtualDisks statistical data: i used zendmd and ZMI and tried all combinations, your

python:"HPEVA_VolumeStatisticalData.InstanceID=\"%s.%s\""%tuple(eval('(lambda **kwargs: kwargs)(%s)'%here.snmpindex.split('.')[1]).values()[1:3])

makes InstanceID appear okay in zendmd but still, Datasource for Virtualdisks doesn't pull this data and graphs are still NaN! I don't have any other idea how to troubleshoot! Zenperfwbem debug says:

2011-02-15 14:58:09,029 DEBUG zen.zenperfwbem: Queueing event {'manager': 'localhost.localdomain', 'severity': 0, 'device': '50001FE1500F4220', 'eventClass': '/Status/Wbem', 'component': 'zenperfwbem', 'monitor': 'localhost', 'agent': 'zenperfwbem', 'summary': 'Could not get WBEM Instance'}

3. These latency values we get from i.e. HPEVA_DiskDriveStatisticalData, i don't understant how we can use them!!!

According to mof file found on CV server in SMI-S provider directory, these are COUNTER types od data, and values are like:

WriteLatencyTime_ms = 22598833;

Okay i see ms for miliseconds but this value doesn't make any sense! more than 22 millions miliseconds! Mof file says these are "cumulative latencies...from both controllers....". Cumulative?! Okay, counters, so zenoss pulls latencies every 5 minutes and substracts them, and still gets BIG latencies!!!

Latency as a COUNTER makes no sense to me! It should be a GAUGE-type of value, like via evapef. When you query a value, you get a current latency. What do we do with counters?

Normaly, disk latency should be under 5ms (read) and 15ms (write) but my graphs show latencies average arround 200-300ms and max around 1.2 seconds!

Controller and FC Port latencies (graphed by zenoss) go up to 4-6 seconds!

I know zenoss (or this zenpack) is not to blame, it only graphs what it gets from CV server, but these latency values are worthless presented this way! Other values are okay and are within expected boundairies.

So how do we explain these 300ms - 6s latencies to an experienced storage guy? He will not buy that!

Anybody has any comment or how-to concept or explanation on this issue? Perhaps DERIVE in DataPoint definition should be changed to something else to make it more accurate?

Are you guys happy with these latency values? Or do you have normal latencies, perhaps i have an issue here?

Screenshot of my hard disk latency graph:

https://docs.google.com/leaf?id=0B40Sd-yGeiktNzIzOTVhNmItMGY4MC00ZDdjLWJiOTMtZWM3MTEyZTRjYTVl&hl=en&authkey=CIHasrkI

RE: HP EVA Monitor

community@zenoss.org — Tue, 15 Feb 2011 18:11:56 GMT

Hi Marko,

1. The simplest way to install YAWN is discribed in chapter 'Manual Installation'.

2. You can use WBEM Data Source 'Test' function to check instances names. Create new Template, add WBEM data source with Namespace=root/eva and Query=HPEVA_VolumeStatisticalData to it. Save it and press 'Test' button.

3. it seems like by HP 'ms'='microseconds'

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 16 Feb 2011 09:06:45 GMT

egor

1. The simplest way to install YAWN is discribed in chapter 'Manual Installation'.

OK, thanks, i'll give it a try

2. You can use WBEM Data Source 'Test' function to check instances names. Create new Template, add WBEM data source with Namespace=root/eva and Query=HPEVA_VolumeStatisticalData to it. Save it and press 'Test' button.

Yes, i tried somethin like that already. however, testing a WBEM data source against my "EVAWWN" device produces an error.

Then I added my CV server (next to my existing EVA device) using its IP, created a special class and attached a new template with a WBEM data source defined. Again, CIM_ACCESS_DENIED error.

3. it seems like by HP 'ms'='microseconds'

In what universe "ms" stands for "microseconds" ?!

(microseconds are usualy noted as "us" on computers when there is no micro greek letter)

Anyway, inspecting a mof file found on CV server, it describes Latency_ms as "miliseconds" and "cumulative".

C:\Program Files\Hewlett-Packard\SMI-S\EVAProvider\mof\eva\eva-stats.mof

....

// =====================================================================
// EVA Volume Statistical Data. ElementType=8 (Volume)
// =====================================================================

[Description ("EVA Virtual Disk Performance Statistics")]
class HPEVA_VolumeStatisticalData : CIM_BlockStorageStatisticalData
{
   [override("ElementType"), Required]
   uint16 ElementType = 8;

   uint64 ReadHitKBytes;           // Cummulative count of Read Hits
   uint64 ReadHitLatencyTime_ms;   // Read hit latency in milliseconds
   uint64 ReadMissRequests;        // Cummulative count of Read Miss Requests
   uint64 ReadMissKBytes;          // Cummulative count of Read Miss KBs (1KB = 1024 Bytes)
   uint64 ReadMissLatencyTime_ms; // Read miss latency in milliseconds
   uint64 WriteLatencyTime_ms;     // write latency in milliseconds
   uint64 FlushRequests;           // Cummulative count of Flush Requests
   uint64 FlushKBytes;             // Cummulative count of Flush KBs
   uint64 MirrorKBytes;            // Cummulative count of Mirror KBs
   uint64 PrefetchKBytes;          // Cummulative count of Prefetch KBs
   string WriteMode;               // Write state of the disk.wite Back = 1, Write Through = 0
   string OnlineToControllerNum;   // Which controller this VDisk is online to. 0 = neither controller; 1 = controller A; 2 = controller B
   string MirrorState;             // Mirror state of the disk. Mirrored = 1 Not Mirrored = 0
   string GroupId;                 // Disk Group this Virtual Disk belongs to
};

....

// =====================================================================
// Physical Disk Statistical Data. ElementType=10 (DiskDrive)
// =====================================================================
[
Description ("EVA Disk Drive Statistics")]
class HPEVA_DiskDriveStatisticalData : CIM_BlockStorageStatisticalData
{
   [override("ElementType"), Required]
   uint16 ElementType = 10;

   uint64 DriveQDepth;               // Cummulative count of read/write requests from both controllers
   uint64 DriveLatencyTime_ms;       // Cummulative count of time data is sent to disk and when it is processed
   uint64 ReadLatencyTime_ms;        // Cummulative count of time disk takes to complete read request from each controller
   uint64 WriteLatencyTime_ms;       // Cummulative count of time disk takes to complete write request from each controller
   string GroupId;                   // Disk Group this Virtual Disk belongs to
};

....

Please check if you have this file in your CV server. As you see, latencies have "_ms" and description says "miliseconds", also al latencies are "cumulative" as their values are BIG numbers. FYI, 22 milion "microseconds" is still 22 seconds, which is to big for a latency!

Maybe there is something wrong with my SMI-S provider! Just out of curiosity, can you post here your RAW value of some instance of

HPEVA_VolumeStatisticalData => WriteLatency_ms

(not from zenoss, but an actual value to compare to mine, use your YAWN and post the value here please, i want to see if your values and my values are similar in general size)

Mine is: WriteLatencyTime_ms = 22598833;

thanks,

Marko

RE: HP EVA Monitor

community@zenoss.org — Wed, 16 Feb 2011 09:31:28 GMT

egor,

2. You can use WBEM Data Source 'Test' function to check instances names. Create new Template, add WBEM data source with Namespace=root/eva and Query=HPEVA_VolumeStatisticalData to it. Save it and press 'Test' button

sorry, following your instructions, here are the results of WBEM test:

Preparing Command...

Get WBEM Instance HPEVA_VolumeStatisticalData from https://<CV_IP>:5989/root/eva

InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.7B200710B408056027600900007000000000B005" InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.3C200710B4080560276009000070000000004702" InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.25200710B4080560276009000070000000008B01" InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.37200710B4080560276009000070000000002002" InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.47200710B408056027600900007000000000CF02" InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.68200710B408056027600900007000000000B404" InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.07200710B4080560276009000070000000003A00" InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.5A200710B4080560276009000070000000009603"

... and so on....

DONE in 11 seconds

When query = HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.00200710B4080560276009000070000000001000"

result is:

Preparing Command...

Get WBEM Instance HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.00200710B4080560276009000070000000001000" from https://<CV_IP>/root/eva

InstanceName: root/eva:HPEVA_VolumeStatisticalData.InstanceID="50001FE1500F4220.00200710B4080560276009000070000000001000"

PrefetchKBytes = 0 StartStatisticTime = 2011/02/08 15:09:6.048000 GMT+1 InstanceID = 50001FE1500F4220.00200710B4080560276009000070000000001000 WriteLatencyTime_ms = 1637324 WriteHitIOTimeCounter = None ReadHitKBytes = 0 ReadHitIOTimeCounter = None MaintTimeCounter = None IdleTimeCounter = None KBytesRead = 96937 ElementName = 6005-08B4-0009-6027-0000-7000-0010-0000 ReadHitIOs = 0 Description = EVA VDisk level metrics for 50001FE1500F4220 ReadMissLatencyTime_ms = 779670 ReadMissRequests = 96937 MaintOp = None TotalIOs = 1120710 KBytesTransferred = 24109677 WriteIOTimeCounter = None WriteMode = 1 ReadHitLatencyTime_ms = 0 FlushRequests = 0 ReadIOs = 96937 MirrorKBytes = 36286384 Caption = None IOTimeCounter = None ElementType = Volume KBytesWritten = 20664080 ReadIOTimeCounter = None StatisticTime = 2011/02/16 10:35:7.770000 GMT+1 MirrorState = 1 OnlineToControllerNum = 1 FlushKBytes = 20742762 SampleInterval = 2011/02/16 10:35:7.865336 GMT+1 WriteHitIOs = None ReadMissKBytes = 3445597 WriteIOs = 1023773 GroupId = 1

DONE in 7 seconds

So this looks okay, but still graphs are NaN...

RE: HP EVA Monitor

community@zenoss.org — Wed, 16 Feb 2011 18:44:47 GMT

Hi Marko,

In what universe "ms" stands for "microseconds" ?!
(microseconds are usualy noted as "us" on computers when there is no micro greek letter)
Anyway, inspecting a mof file found on CV server, it describes Latency_ms as "miliseconds" and "cumulative".

i'm also have inspected mof files. You can try to use HP EVAperf utility to get latency and compare result with Zenoss Graph to find right multiplexer.

Egor

RE: HP EVA Monitor

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

You can try to use HP EVAperf utility to get latency and compare result with Zenoss Graph to find right multiplexer.

Yes, i have already done that and that first showed me these differencies between latencies from evaperf and smi-s. I also thought it might be due to the SI unit (mili, micro, etc.) but the values themselves are not similar. Also, evaperf can provide latency for single element, while SMI-S often provides agreggate values (i.e. disk write latency for "both" controllers, etc.).

For example, lookind at a single hard disk latency, at any given time, evaperf gives something like:

WriteLatency = 2,5 ms - this is an actual value of latency in this particular time

On the other hand, SMI-S gives a counter, and you have to take 2 values in times T1 andT2, and substract and then divide by time period. (i guess that's what Zenoss does every 5 minutes and then divides the result by 300).

WriteLatencyTime_ms = 195516687;

WriteLatencyTime_ms = 195519791;

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

Diff: 3104

My tests were for T2-T1=cca 10s

Okay so these 3104, what are these? 3104 miliseconds (3,1 seconds)? What's the latency then 3104ms? Or 3104/10 = 310, 4 ms? Or if these are microseconds then 3104us=0,31ms? .......

At the same time evaperf reports 2,5ms! So 3,1 and 2,5 are not similar regardless of which SI unit should be used.

Anyway, this is very confusing and i don't know how to explain/use these latencies....

RE: HP EVA Monitor

community@zenoss.org — Thu, 17 Feb 2011 16:31:10 GMT

Hi Marko,

set RPN on 'Latency' Graphs to: 100,/

Egor

RE: HP EVA Monitor

community@zenoss.org — Fri, 18 Feb 2011 08:05:01 GMT

egor

Hi Marko,

set RPN on 'Latency' Graphs to: 100,/

Egor

Why?

RE: HP EVA Monitor

community@zenoss.org — Wed, 23 Feb 2011 08:03:28 GMT

Hi Egor

could you please post the following:

1. a screenshot of one of your real latency graph (i.e. FC Port latency, or Controller A latency, or whichever) - if you have any

2. some info on the corresponding DataSource (e.g. WriteLatency data point) - is it DERIVE or something else, do you have RPN set to something, etc.?

I want to compare your graph to mine (compare values), maybe what i'm seeing (abnormal latencies) is due to the CV version again, maybe there is some kind of SMI-S bug in CV 8.0 which is not present in CV 9.X...

Anyway, setting latency graphs RPN to 100,/ or 1000,/ gives no better result as it's not about a value being 1000 times bigger or whatever, rather the number itself is weird. So i'm trying to figure out why Latencies acquired from SMI-S (via WBEM) are SO MUCH different compared to latencies reported by evaperf.exe (localy on CV server) for the same EVA component (i.e. a particular FC port or a particular Hard disk, etc.)

thanks

marko

RE: HP EVA Monitor

community@zenoss.org — Wed, 23 Feb 2011 20:09:38 GMT

Hi Marko,

1. i don't have.

2. check Data Sources from HPEVAMon ZenPack.

it makes no sense to compare RAW Counters (DERIVE is a counter type) data.

Egor

RE: HP EVA Monitor

community@zenoss.org — Thu, 24 Feb 2011 08:02:49 GMT

egor

1. i don't have.

2. check Data Sources from HPEVAMon ZenPack.

No point in doing that, i know already how Datasources are configured in your ZenPack. I know they are DERIVE. I just wanted to *confirm* that the same configuration is *working* for you and that your latencies are *normal* while mine are abnormal. this leaves me with the conclusion that you (or nobody else using this zenpack) didn't ever noticed that latecies reported via SMI-S are totally abnormal. You proposed that i set RPN in latency graphs to 100,/ and i asked "why?" and you didn't answer. This tells me that either you are unfamiliar with an issue or that you did solve this issue on your side with changing RPN, but either way, your not giving me an answer on "why?" doesn't help me understand what's going on. If your zenpack is done and finished and SMI-S is reporting RIGHT latencies, then why on earth would i want to change my Latency number (divide it by 100)?!

So i still can't percieve if

1. either there is a bug in this particular instance of storage i'm testing (my EVA with CV 8.0) and SMI-S is reporting faulty latencies, while your latencies look okay in zenoss (and this issue will go away once we upgrade to CV 9.X)

2. or this is common for all SMI-S provided latencies but nobody noticed the differencies compared to *real* latencies via evaperf.exe (and this issue will still remain even in CV 9.x)

it makes no sense to compare RAW Counters (DERIVE is a counter type) data

I agree, but since your answers don't help me with this issue and there is no other reference to this problem anywhere on the web, i had no other options than to bring troubleshooting down to most unsensible level.

I'm stuck here with an issue and i want to isolate the root cause: 1. is it just *my* environment (my EVA SMI-S reporting unreal latencies) or

2. is it common to all HP EVA environments.

If this other is the case, than you as an author of the zenpack *should* be interested in me reporting to you that there is some kind of data inconsistency which makes your zenpack a little bit less useful. Your zenpack is great and is not to blame if SMI-S is the root cause, but the fact remains that using this zenpack to monitor HP EVA actualy gives some wrong numbers. And that is a big deal.

But i don't know if the cause i s 1. or 2. as you are the only one i can use to compare my EVA environment to yours, and i didn't get the data i requested from you. If you perhaps don't have a functional testing HP EVA environment monitored by zenoss right now, then say so....

However, thank you for your help so far.

regards

marko

RE: HP EVA Monitor

community@zenoss.org — Thu, 24 Feb 2011 20:58:26 GMT

Hi Marko,

You proposed that i set RPN in latency graphs to 100,/ and i asked "why?" and you didn't answer. This tells me that either you are unfamiliar with an issue or that you did solve this issue on your side with changing RPN, but either way, your not giving me an answer on "why?" doesn't help me understand what's going on. If your zenpack is done and finished and SMI-S is reporting RIGHT latencies, then why on earth would i want to change my Latency number (divide it by 100)?!

*Why* not to ask HP: "*Why* in mof file Latency is units is 'milliseconds', but SMI-S reported it in 'ten-microseconds' units?"

*Why* simply not to try proposed solution?

Egor

PS: on my git repository you can find updated Version of this ZenPack. Latency will be displayed in seconds with 'm' and 'u' suffixes.

RE: HP EVA Monitor

community@zenoss.org — Fri, 25 Feb 2011 13:40:46 GMT

Egor

*Why* not to ask HP: "*Why* in mof file Latency is units is 'milliseconds', but SMI-S reported it in 'ten-microseconds' units?"
*Why* simply not to try proposed solution

Aaaah, now this is something! Okay, obviously my MOF from CV 8.0 and your MOF form CV 9.1 are different and that led me in a wrong direction from your direction! So you knew that SMI-S reported it in 'ten-microseconds' units? Then how come this RPN moddification (100,/) is not in your zenpack?

So this should have been the answer to my *why*!

You could have said "Because according to SMI-S, latency units are in 'ten-microseconds' so when you divide it by 100 you get the right number"

Anyway, i just like to know *why* before changing something i don't understand why i'm changing it, i believe you can understand that. I could TRY the proposed solution, but since i don't know what's behind the solution (i don't know the *why* part) i wouldn't be able to re-use the solution it in a similar issue. Would you want to change somethin just because somebody told you to change it, without trying to get a deeper understanding? I doubt it.

But again, i don't understand what kind of unit is "ten-microseconds"?!

If microseconds are 10^-6, then "ten-microsecond" are 10*10^-6=10^-5 ?

then dividing it by 100 gives: 10^-5/10^2=10^-3 = milliseconds?

so dividing by 100000 would yield seconds?

Okay, i'll give it a shot.

I'll inspect your new version, and also we are planning to upgrade CV to 9.3 so i HOPE everything will be correct then.

I can't *ask* HP cause i don't have any direct possibility to contact them on this issue and i couldn't find SMI-S reference on the WEB. Please share a link if you have, WHERE i can find new HP EVA MOF files od EVA provider reference.

...SMI-S reported it in 'ten-microseconds' units...

Is this your conclusion or you actually found this specified somewhere (if yes, where)?

I'm sorry, I know i'm annoying you but this is actually really important to me. I tend to understand my problems as i go along with implementing solutions other people propose.

All this milliseconds, ten-miliseconds stuff makes no sense to me and that's why i'm trying to understand what is going on here....

regards

RE: HP EVA Monitor

community@zenoss.org — Fri, 25 Feb 2011 13:59:55 GMT

Account is :

Administrator/b33chbu66y

RE: HP EVA Monitor

community@zenoss.org — Fri, 25 Feb 2011 14:34:44 GMT

Account is :
Administrator/b33chbu66y

I guess this is posted by mistake?

RE: HP EVA Monitor

community@zenoss.org — Fri, 25 Feb 2011 15:16:26 GMT

Egor,

adding RPN: 100000,/ to Latency graphs solves the issue!

I'm now graphing my latencies in Seconds (Y axis label) and values are automatically convereted to milliseconds by RRD tool. that's it!

I'm sorry i was a bit annoying but finally this is resolved. I also see you applied these changes yesterday in your latest 1.9 zenpack release. Cool, we all learn something day-by-day

Anyway, i have some bugs to report, perhaps they are not caused by your zenpack but you will distinguish is it related to your zenpack or the zenoss in general:

1. When i go to Components->Disk groups i get EVA Disk Groups listed. I choose e.g Unix disk group and in the lower right pane (where graphs usualy are) i choose to display "Volumes". By default, page size is set to 40. I have 71 Volumes, and only 40 presented on the first page. Clicking on the ">" to go to the next page to display next set of volumes does nothing, clicking "Show all" also does nothing, changing Page Size to a bigger value changes nothing.

2. Using "Filter by Name" in component tables (e.g. a list of Virtual disks) is not working properly. Entering anything (one letter "S" or entire word "SOLARIS") presents blank search result

If these are not related to your zenpack, ignore this....

regards

marko

RE: HP EVA Monitor

community@zenoss.org — Sun, 27 Feb 2011 20:22:07 GMT

Hi Marko,

both problem are not related to this ZenPack.

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 02 Mar 2011 23:12:31 GMT

Hi Egor,

I've just installed this Zenpack as per your instructions. All went well up until I attempted to model our EVA 8100, (our CV server is 9.02). At first all seemed normal but then I get a number of these errors when it tries to model the hard disks:

2011-03-03 09:37:19,028 ERROR zen.ZenModeler: Client 5000-1FE1-5014-F6A0 finished with message: [Failure instance: Traceback (failure with no frames): : Traceback (most recent call last):

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

return callable(*args, **kw)

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

if adm._applyDataMap(device, map):

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

changed = self._updateRelationship(tobj, datamap)

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

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

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

rel._setObject(remoteObj.id, remoteObj)

File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 127, in _setObject

self.addRelation(object)

File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 117, in addRelation

ToManyRelationshipBase.addRelation(self, obj)

File "/opt/zenoss/Products/ZenRelations/RelationshipBase.py", line 94, in addRelation

obj.id, obj.__class__.__name__))

ZenSchemaError: harddisks restricted to class HardDisk. 820807100C000820503037CA0000000000000000 is class HPEVADiskDrive

In the end I only end up with HPEVAStorageProcessorCard under "Components".

Any ideas?

Cheers for another amazing ZenPack,

James

RE: HP EVA Monitor

community@zenoss.org — Wed, 09 Mar 2011 12:40:59 GMT

As per your comment:

PS: on my git repository you can find updated Version of this ZenPack. Latency will be displayed in seconds with 'm' and 'u' suffixes.

i have downloaded the 1.10 version, latencies are in seconds (divided by 100000). Then looking at your GIT repository i realised you had several other updates under 1.10 version since the release and since i downloaded and installed v1.10.

Now, how do i know do i have these new sub-enhancements or not? Looking at dates in GIT repository i guess i don't have them. How do i update my 1.10 version with your latest 1.10 fixes? If i download your 1.10 relase NOW, is it updated with newest sub-fixes?

You see, if you add a date to Change History, i could be able to compare the zenpack release date with GIT repository changes and see wheather i already have those sub-fixes or not...

Or does this official 1.10 release (avail. for download) stay unchanged untill you release 1.11 for example?

Because now i don't know do i have your latest "Data Replication Groups Performance Monitoring" (announced for v1.9) or "Storage Groups performance monitoring" (announced for 1.10) features or not. I don't see any new components, graphs or datapoints compared to 1.9 release...

So...

RE: HP EVA Monitor

community@zenoss.org — Wed, 09 Mar 2011 17:35:27 GMT

Hi,

Thanks for the work on this, very nice stuff.

I have a question about performance data...

When you query via WMI for performance counters, you get the value on this specific time, not an average since the last query ?

I mean the performance data could be not exact if you use only instant points and not average data over time.

What is returned via WMI ? instant values or average values since last WMI query ?

Thanks

RE: HP EVA Monitor

community@zenoss.org — Wed, 09 Mar 2011 19:23:18 GMT

Hi Marko,

as you can see here: https://github.com/epuzanov/ZenPacks.community.HPEVAMon/commit/2534bb693e699874b6a10e752655d991e4bbb227

actual Git version of this ZenPack is 1.10.1. If you want use latest version of ZenPack (note: this is a Work-in-Progress version) you must built it by yourself from source.

Egor

RE: HP EVA Monitor

community@zenoss.org — Wed, 09 Mar 2011 19:40:35 GMT

Hi tntteam22,

1. HP CV used WBEM (http/https) as transport but not a WMI (dcom).

2. HP CV returned performance data as COUNTER ( http://oss.oetiker.ch/rrdtool/doc/rrdcreate.en.html )

Egor

RE: HP EVA Monitor

community@zenoss.org — Thu, 10 Mar 2011 07:41:19 GMT

Hi Marko,

as you can see here: https://github.com/epuzanov/ZenPacks.community.HPEVAMon/commit/2534bb693e699874b6a10e752655d991e4bbb227
actual Git version of this ZenPack is 1.10.1. If you want use latest version of ZenPack (note: this is a Work-in-Progress version) you must built it by yourself from source.

Egor

Egor

okay, so additional 1.10.X fixes are not included in 1.10 version available for download, got it.

Next release (etc 1.11) will contain those fixes, okay.

Please consider my proposal of adding a date in Change history section for your next release.

Thanks

marko

RE: HP EVA Monitor

community@zenoss.org — Tue, 22 Mar 2011 21:43:19 GMT

Hi Egor,

I've just updated our Command View to 9.3 but I am still getting errors when I attempt to model our EVA 8100.

Everything goes fine at first until it tries to model the hard disks:

ZenSchemaError: harddisks restricted to class HardDisk. 820807100C000820503037CA0000000000000000 is class HPEVADiskDrive

In the end I only end up with HPEVAStorageProcessorCard under "Components".

Any idea why my disks are being detected as class "HPEVADiskDrive" when they seem to need to be of class "HardDisk"?

(FYI I'm running the WBEM Datasource Zenpack v2.10)

Thanks...

RE: HP EVA Monitor

community@zenoss.org — Tue, 22 Mar 2011 21:50:40 GMT

Hi James,

Try a previous version of this ZenPack (HPEVAMon 1.9)

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 22 Mar 2011 22:42:20 GMT

Hi Egor,

I downgraded to 1.9 and now I'm having a problem when processing community.wbem.HPEVAStorageVolumeMap:

2011-03-23 09:38:51,735 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageVolumeMap for device 50001FE15014F6A0

2011-03-23 09:38:56,588 ERROR zen.ZenModeler: Traceback (most recent call last):

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

return callable(*args, **kw)

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

if adm._applyDataMap(device, map):

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

changed = self._updateRelationship(tobj, datamap)

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

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

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

return self._updateObject(remoteObj, objmap) or changed, remoteObj

File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.9.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 113, in setEnclosure

encl = getattr(self.hw().enclosures, str(encid), None)

AttributeError: enclosures

Traceback (most recent call last):

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

if driver.next():

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

raise ex

RemoteException: Traceback (most recent call last):

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

return callable(*args, **kw)

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

if adm._applyDataMap(device, map):

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

changed = self._updateRelationship(tobj, datamap)

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

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

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

return self._updateObject(remoteObj, objmap) or changed, remoteObj

File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.9.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 113, in setEnclosure

encl = getattr(self.hw().enclosures, str(encid), None)

AttributeError: enclosures

2011-03-23 09:38:56,589 ERROR zen.ZenModeler: Client 50001FE15014F6A0 finished with message: [Failure instance: Traceback (failure with no frames): : Traceback (most recent call last):

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

return callable(*args, **kw)

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

if adm._applyDataMap(device, map):

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

changed = self._updateRelationship(tobj, datamap)

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

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

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

return self._updateObject(remoteObj, objmap) or changed, remoteObj

File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.9.egg/ZenPacks/community/HPEVAMon/HPEVADiskDrive.py", line 113, in setEnclosure

encl = getattr(self.hw().enclosures, str(encid), None)

AttributeError: enclosures

]

2011-03-23 09:38:56,589 INFO zen.ZenModeler: Scan time: 12.75 seconds

2011-03-23 09:38:56,594 INFO zen.ZenModeler: Daemon ZenModeler shutting down

Any ideas?

RE: HP EVA Monitor

community@zenoss.org — Tue, 22 Mar 2011 23:27:15 GMT

Hi James,

it seems like your EVA was created in Zenoss as standard device (Products.ZenModel.Device). This can happen if EVA object was created not in /CIM/HPEVA device class.

So remove your EVA from Zenoss and readd it without initial modeling to /CIM/HPEVA device class. Than model your EVA as usual.

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 22 Mar 2011 23:56:22 GMT

That was it Egor. Thanks again for your help and for all the great Zenpacks!

RE: HP EVA Monitor

community@zenoss.org — Fri, 25 Mar 2011 09:01:21 GMT

Hi guys,

i just want to add that you CAN change the EVA device name *after* you discover it using WWN. You can go to Device Overview page and in "Device Name" field you can change the WWN to a user-firendly EVA name (e.g. MY COMPANY EVA) and there is no negative effect (data collecting and graphing doesn't stop).

Internal Device ID and SNMP SysName will remain unchanged acording to WWN and WWN will still be used in script and DataSource calls.

Also, you can discover EVA using both versions of WWN (with or without "-"), makes no difference:

a) xxxx-xxxx-xxxx-xxxx

b) xxxxxxxxxxxxxxxx

This is confirmed on two separate zenoss 3.1.0 installations managing two different EVAs

HP EVA Monitor 1.10

WBEM Data Source 2.10

CV versions, both 9.3

So perhaps you can edit installation instructions regarding this topic:

"I may have seen an issue involving the renaming of the device from the WWN where graphing stops after the rename...well that's what appears to have happened....so rename at your peril!"

Hope this helps

marko

RE: HP EVA Monitor

community@zenoss.org — Tue, 19 Apr 2011 15:53:23 GMT

Does anyone happen to have a verified procedure for adding multiple EVAs connected to the same CV server? I tried to edit the snmpsysname but the field can't be altered. I also tried adding multiple EVAs under the same device class, but when I do that there are major gaps in reporting. All is fine with a single EVA.

RE: HP EVA Monitor

community@zenoss.org — Wed, 22 Jun 2011 10:00:55 GMT

Hi Bigegor,

Does this ZenPack Version support on the CV6.x?

RE: HP EVA Monitor

community@zenoss.org — Wed, 22 Jun 2011 18:18:29 GMT

hi wilsonlai,

not, CV6 used old DMTF scheme.

Egor

RE: HP EVA Monitor

community@zenoss.org — Fri, 24 Jun 2011 13:50:51 GMT

Thank you! New to Zenoss, but this Zenpack is exactly what I was looking for.

I've installed the Zenpack and it has detected and populated the 'components' items without issue. Graphing is also working great. However whenever I access the 'hardware' menu, I do not see the EVA graphics. Instead I am presented with the following error message:

Site error

An error was encountered while publishing this resource. The requested resource does not exist.
Please click here to return to the Zenoss dashboard

I have tried restarting all Zenoss services and even restarting the CV server. Any advice would be appreciated, but I will continue using your Zenpack with or without the graphics. Thanks again!

RE: HP EVA Monitor

community@zenoss.org — Fri, 24 Jun 2011 15:05:33 GMT

What type of array are you adding and what is your Command View version? Did you install all of the dependencies? Are you recieving any error messages in Event Viewer on your CV server?

RE: HP EVA Monitor

community@zenoss.org — Fri, 24 Jun 2011 15:13:32 GMT

Thanks for the reply.

The array is an EVA4000, Command View is version 9.02. The only depenency I was aware of is WBEM Data Source, which was installed and Zenoss was restarted. The CV server works as expected, without any errors. Zenoss is correctly populating the "Components" -- FC Ports, Disk Groups, Controllers, etc -- this is all graphing as well. Just the "Hardware" section produces the error.

RE: HP EVA Monitor

community@zenoss.org — Fri, 24 Jun 2011 15:38:35 GMT

what is your Zenoss version?

RE: HP EVA Monitor

community@zenoss.org — Fri, 24 Jun 2011 15:43:12 GMT

I know this is off subject but do you have any hints for adding multiple EVAs connected to one CV server? Once I add muliple EVAs I have pretty big gaps in reporting data while one EVA reports just fine. I will assist people when I can with your ZenPack if I could get a bit of help.

RE: HP EVA Monitor

community@zenoss.org — Fri, 24 Jun 2011 15:52:10 GMT

try latest development version of WBEMDataSource with SQLDataSource ZenPacks (http://community.zenoss.org/people/bigegor/blog/2011/06/14/sqldatasource-zenpack-20-beta4), in my tests it works about 4 times faster than old one.

RE: HP EVA Monitor

community@zenoss.org — Fri, 24 Jun 2011 15:57:02 GMT

Zenoss 3.1.0 Core stack install on Debian 6.0.1 AMD64.

RE: HP EVA Monitor

community@zenoss.org — Mon, 27 Jun 2011 15:08:08 GMT

i can't reproduce this error on EVA4400. It can be EVA4000 specific. What is your Storage Enclosures type?

RE: HP EVA Monitor

community@zenoss.org — Mon, 27 Jun 2011 15:23:18 GMT

The storage enclosures are M5314A, controllers are HSV200 CR1363xc3p-6220... I just noticed under "Overview" the "Hardware Model" is incorrectly listed as "EVA6000". I do not see EVA4000 available under the HW Device drop-down.

RE: HP EVA Monitor

community@zenoss.org — Mon, 27 Jun 2011 15:42:54 GMT

hmm, i'm not really understend how to identify EVA4000 and EVA6000, both are using the same HSV200 Controller. But this has nothing to do with your problem.

RE: HP EVA Monitor

community@zenoss.org — Mon, 27 Jun 2011 18:17:58 GMT

From the Z2.log, I'm getting a 404 on the resource "hpevaDeviceHardwareDetail"

127.0.0.1 - Anonymous [27/Jun/2011:14:07:59 -0400] "GET /zport/dmd/Devices/CIM/HPEVA/devices/5000-1FE1-500D-2F10/hpevaDeviceHardwareDetail HTTP/1.1" 404 2651 "http://zenoss:8080/zport/dmd/Devices/CIM/HPEVA/devices/5000-1FE1-500D-2F10/devicedetail"

Going to dig around and see if I can find anything. I'm new to Zope/Zenoss, so I'm not clear on what exactly I am looking for. Thanks for all your assistance.

RE: HP EVA Monitor

community@zenoss.org — Thu, 04 Aug 2011 15:44:14 GMT

Egor,

I have your ZenPack working quite well, however there are a couple small things I would like to work out to get out EVA's monitored with all functionality working.

Here are the issues I am running into:

1. I have an HP EVA 5000 and it Can't be monitored using the WBEM datasource as it cannot find the WBEM instance. It modelled correctly initially, but now it can't Poll the data. It would be really cool to get this working. It looks like it is just a problem witht he namespace nto finding the device. IWBEM Daemon Log is below:

2011-08-04 12:12:19,042 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:12:36,163 ERROR zen.zenperfwbem: Device 50001FE15002B6D0: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:13:42,883 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:13:58,026 ERROR zen.zenperfwbem: Device 50001FE15002B6D0: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:15:45,017 INFO zen.zenperfwbem: 2 devices processed (960 datapoints)
2011-08-04 12:15:45,018 INFO zen.collector.scheduler: Tasks: 2 Successful_Runs: 2 Failed_Runs: 0 Missed_Runs: 0
2011-08-04 12:18:43,016 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:18:57,952 ERROR zen.zenperfwbem: Device 50001FE15002B6D0: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:20:45,024 INFO zen.zenperfwbem: 2 devices processed (1440 datapoints)
2011-08-04 12:20:45,025 INFO zen.collector.scheduler: Tasks: 2 Successful_Runs: 4 Failed_Runs: 0 Missed_Runs: 0
2011-08-04 12:23:43,115 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:23:58,483 ERROR zen.zenperfwbem: Device 50001FE15002B6D0: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:25:45,030 INFO zen.zenperfwbem: 2 devices processed (1920 datapoints)
2011-08-04 12:25:45,030 INFO zen.collector.scheduler: Tasks: 2 Successful_Runs: 6 Failed_Runs: 0 Missed_Runs: 0
2011-08-04 12:28:44,895 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:29:00,024 ERROR zen.zenperfwbem: Device 50001FE15002B6D0: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:30:45,036 INFO zen.zenperfwbem: 2 devices processed (2400 datapoints)
2011-08-04 12:30:45,036 INFO zen.collector.scheduler: Tasks: 2 Successful_Runs: 8 Failed_Runs: 0 Missed_Runs: 0
2011-08-04 12:33:41,304 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:33:57,808 ERROR zen.zenperfwbem: Device 5000-1FE1-5002-B6D0: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:34:50,709 ERROR zen.WBEMClient: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:35:07,031 ERROR zen.zenperfwbem: Device 5000-1FE1-5002-B6D0: Received Instance: isa(HPEVA_StorageSystemStatisticalData) such that {InstanceID="50001FE15002B6D0"} not found from query: HPEVA_StorageSystemStatisticalData
2011-08-04 12:35:45,044 INFO zen.zenperfwbem: 3 devices processed (3360 datapoints)
2011-08-04 12:35:45,044 INFO zen.collector.scheduler: Tasks: 3 Successful_Runs: 6 Failed_Runs: 0 Missed_Runs: 0

2. I also have an HP EVA 8100 and it is ont he same CV server as the 5000, but it can poll data correctly and it has most functionality. The thing I noticed that are not working are the following:

It does nto display all disks in a disk group, but shows all the disks that are ungrouped. it is showing about 60 of 168 disks.
The "Hardware" visual display (on the left hand side not in components) is not displaying any hardware at all. (This is showing on the 5000) It does show the 2 controllers, but not the pretty pictures.

Let me know if you need any additional information, and where to find it as I am somewhat new to Zenoss, but I can find my way around pretty well.

Thanks,

Dane

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 14:26:48 GMT

I am having an issue installing the zen pack on 3.1. I read that this has been tested but I do not see the EVA ZenPacks.community.HPEVAMon-1.11.egg.zip after I unzip and upload to GUI. I restarted the zenoss server two times with no luck. I upload other zen pack and it show up just fine. Am I doing something wrong?

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 14:31:32 GMT

Johnisccp,

Have you installed the dependency, WBEM Datasource?

You have to install the dependency, then do a "zenoss restart" command to allow the daemon to start running, and once that is done then you can install the HPEVAMon ZenPack. Also, make sure you follow the direction exactly to get your devices monitored by this ZenPack.

Dane

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 14:42:05 GMT

Ok I did not do that yet. I follow your instructions and now I see both zen packs. I am newbie using Zenoss. Have you use this EVA zen pack?

Thanks again.

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 14:44:58 GMT

Yes, it works very well. Just make sure to read to the entire "document" about the zenpack before starting the install, because a lot of the zenpacks require you to install prerequisites.

The WBEM Proxy zProperties are the tricky part, so make sure you read the installation directions, and you'll be up and running in no time.

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 15:36:48 GMT

Ok I follow the instructions as describe in the aritcle but I can not seem to get it work work by device Ip or WWN. Here is the error I am getting when I put the WWN as instructed in the article.

I try to enter the CV server ip address when adding device but that did not work as well. I check the configuration properties and have the correct information for teh WBEM proxy (CV server) and the zWinPAssword and zWinUser. Am I suppose to use the WWN of the EVA when adding the device or the ip address of the CV server?

2011-08-05 11:30:22,399 INFO zen.ZenDisc: Connecting to localhost:8789

2011-08-05 11:30:22,421 INFO zen.ZenDisc: Connected to ZenHub

2011-08-05 11:30:22,486 INFO zen.ZenDisc: Looking for 5000-1FE1-501E-D130

2011-08-05 11:30:22,488 ERROR zen.ZenDisc: Error: [Failure instance: Traceback (failure with no frames): : No IP found for name 5000-1FE1-501E-D130

]

2011-08-05 11:30:22,489 INFO zen.ZenDisc: Scan time: 0.00 seconds

2011-08-05 11:30:22,491 INFO zen.ZenDisc: Daemon ZenDisc shutting down

 Job completed at 2011-08-05 11:30:23. Result: success.

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 16:12:35 GMT

You need to use the WWN in the IP Address area, and you can put in whatever you want for the name.

A couple things to remember are the following:

1. Begin by adding a new device to /CIM/HPEVA

2. Add the device with the WWN as the IP Address

- DO NOT Model the device on the initial add

3. Wait for the device to be added to the device class, once it is added continue to #4

4. Put the CommandView EVA server information in for zWbemProxy, zWbemPort, zWbemUseSSL, zWinUser*, zWinPassword* in the Configuration Properties of the newly added device.

* These need to be in the HP Storage Admins, or the HP Storage Users groups

locally on the CV Server.

5. Model the device, and check for errors.

6. Keep the devices in the /CIM/HPEVA device class, otherwise they will not poll the WBEM information correctly, even if placed in a Sub-Class under that.

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 18:39:56 GMT

Ok I follow your instructions and click on the model device but I do not see any information when I click on the name of the EVA. How long does it take for information to show up when model device is completed? Here is what shows in the log when I run the model device.

2011-08-05 14:30:16,503 INFO zen.ZenModeler: Connecting to localhost:8789

2011-08-05 14:30:16,523 INFO zen.ZenModeler: Connected to ZenHub

2011-08-05 14:30:16,582 INFO zen.ZenModeler: Collecting for device 5000-1FE1-501E-D130

2011-08-05 14:30:16,649 INFO zen.ZenModeler: No WMI plugins found for 5000-1FE1-501E-D130

2011-08-05 14:30:16,656 INFO zen.ZenModeler: Python collection device 5000-1FE1-501E-D130

2011-08-05 14:30:16,656 INFO zen.ZenModeler: plugins: community.wbem.HPEVADeviceMap, community.wbem.HPEVAStorageDiskEnclosureMap, community.wbem.HPEVAStoragePoolMap, community.wbem.HPEVAStorageProcessorCardMap, community.wbem.HPEVAHostFCPortMap, community.wbem.HPEVADiskDriveMap, community.wbem.HPEVAConsistencySetMap, community.wbem.HPEVAStorageVolumeMap

2011-08-05 14:33:11,618 INFO zen.ZenModeler: No command plugins found for 5000-1FE1-501E-D130

2011-08-05 14:33:11,619 INFO zen.ZenModeler: SNMP monitoring off for 5000-1FE1-501E-D130

2011-08-05 14:33:11,620 INFO zen.ZenModeler: No portscan plugins found for 5000-1FE1-501E-D130

2011-08-05 14:33:28,362 WARNING zen.ZenModeler: Client 5000-1FE1-501E-D130 timeout

2011-08-05 14:33:28,364 INFO zen.ZenModeler: Scan time: 191.78 seconds

2011-08-05 14:33:28,412 INFO zen.PythonClient: Python client finished collection for 5000-1FE1-501E-D130

2011-08-05 14:33:28,413 INFO zen.ZenModeler: processing community.wbem.HPEVAStoragePoolMap for device 5000-1FE1-501E-D130

2011-08-05 14:33:28,415 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageProcessorCardMap for device 5000-1FE1-501E-D130

2011-08-05 14:33:28,416 INFO zen.ZenModeler: processing community.wbem.HPEVAHostFCPortMap for device 5000-1FE1-501E-D130

2011-08-05 14:33:28,419 INFO zen.ZenModeler: processing community.wbem.HPEVAConsistencySetMap for device 5000-1FE1-501E-D130

2011-08-05 14:33:28,423 INFO zen.ZenModeler: processing community.wbem.HPEVADeviceMap for device 5000-1FE1-501E-D130

2011-08-05 14:33:28,423 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageDiskEnclosureMap for device 5000-1FE1-501E-D130

2011-08-05 14:33:28,425 INFO zen.ZenModeler: processing community.wbem.HPEVADiskDriveMap for device 5000-1FE1-501E-D130

2011-08-05 14:33:28,452 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageVolumeMap for device 5000-1FE1-501E-D130

2011-08-05 14:33:29,224 INFO zen.ZenModeler: Daemon ZenModeler shutting down

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 18:45:56 GMT

It looks like the ZenModeler deamon is timing out when doing the modelling. How did you install Zenoss? Debian Stack install, or RPM, or VMware Appliance?

Message me the logs for ZenModeler, and I'll take a look.

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 18:48:42 GMT

I install using the virtual appliance on ESX4i. I chose linux 5 on 32bit. Is there a way I can fix this?

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 18:52:35 GMT

Okay, what did you give it for Resources? (I think it may not have enough RAM, or Storage to write what it needs, which may be causing the ZenModeler to timeout.)

The reccomendations for sizing are here: http://community.zenoss.org/docs/DOC-10206

One more note, I have mine running on Ubuntu Server 11.04, Stack Install, and it works much better than the appliance in my environment.

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 19:08:14 GMT

I have 2 vCPU with 4GB of memory and I only added 1 device so far. The virtual appliance came with 20 GB.

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 19:14:04 GMT

Go to Advanced and click Daemons then copy the log from the zenmodeler daemon, and also from the zenperfwbem daemon, then Send me a Private message so we don't Fill up this whole thread with log posts.

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 20:09:10 GMT

Hi johnsccp,

everything is Ok with your zenmodeler log. Reload page in your browser and you will see new EVA components.

Egor

RE: HP EVA Monitor

community@zenoss.org — Fri, 05 Aug 2011 20:16:43 GMT

Hi dnairns,

1. sometimes CV WBEM CIMOM hangs. So try to restart your CV server.

2. check collector plugins order, move HPEVADiskDriveMap plugin at the end of list. (or remodel your EVA two times)

Egor

RE: HP EVA Monitor

community@zenoss.org — Tue, 09 Aug 2011 07:32:25 GMT

sorry for the stupid question but... where can I find Comand View Eva?

I tried to find it in hp web site but i found only patch...

thanks

RE: HP EVA Monitor

community@zenoss.org — Thu, 13 Oct 2011 11:49:13 GMT

Hi bigegor,

I am using the hp eva 4400. I found this error when i try to model the device.

HPEVA Moniotr 1.11

WBEMDataSource 2.10

2011-10-13 19:46:11,492 INFO zen.ZenModeler: processing community.wbem.HPEVADiskDriveMap for device 5001-4380-1137-9450
2011-10-13 19:46:11,730 ERROR zen.ZenModeler: Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner
return callable(*args, **kw)
File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 109, in remote_applyDataMaps
if adm._applyDataMap(device, map):
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 198, in _applyDataMap
changed = self._updateRelationship(tobj, datamap)
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 261, in _updateRelationship
objchange, obj = self._createRelObject(device, objmap, rname)
File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 441, in _createRelObject
rel._setObject(remoteObj.id, remoteObj)
File "/usr/local/zenoss/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 127, in _setObject
self.addRelation(object)
File "/usr/local/zenoss/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 117, in addRelation
ToManyRelationshipBase.addRelation(self, obj)
File "/usr/local/zenoss/zenoss/Products/ZenRelations/RelationshipBase.py", line 94, in addRelation
obj.id, obj.__class__.__name__))
ZenSchemaError: harddisks restricted to class HardDisk. 072007100C0017201C4CA8CA0000000000000000 is class HPEVADiskDrive
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/DataCollector/zenmodeler.py", line 658, in processClient
if driver.next():
File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result
raise

RE: HP EVA Monitor

community@zenoss.org — Thu, 13 Oct 2011 14:24:31 GMT

After reinstalling the HP EVA Monitor ZenPack, the modeling ran without any errors.

RE: HP EVA Monitor

community@zenoss.org — Tue, 29 Nov 2011 09:57:36 GMT

Hi,

I recently installed HPEVA Monitor 1.11 and I can't seem to get it work. I've comed to the step that it needs to connect to my EVA but all I get is this error:

zenperfwbem /Status/Wbem Could not get WBEM Instance (tuple index out of range).

I scaned through all of this posts and couldn't find that anybody has similar message. When trying with Yawn everything is just fine and all the resutls are there.

I have this versions installed:

Zenoss 3.2.1, HPEVAMon-1.11, WBEMDataSource-2.10, Python 2.6.2, MySQL 5.1.41, CV 9.4.

Does anyone maybe have idea what could be the problem ?

Thanks.

RE: HP EVA Monitor

community@zenoss.org — Tue, 13 Dec 2011 08:38:12 GMT

Never mind, it just had to run for at couple of days and now it is available. Now its just time I need to see what it can do for me. - I hoped for something like mail-warnings regarding disk-errors etc.

Has anyone this ZenPack working with CV v10.00.00.110909. I cannot get it to show our EVA P6300

RE: HP EVA Monitor

community@zenoss.org — Wed, 14 Dec 2011 12:46:04 GMT

I am having some strange behaviors with this ZenPack. After a few days of nothing in the EVA-container I finally had my EVA P6300. But then the graphs stopped working and the virtual disks did not refresh when I added new disks.

I tried to remodel the device but got a lof of connection refused like

ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageSystemControllerStatisticalData

ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_DiskModule
zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_HostFCPortStatisticalData

ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageVolume

ERROR zen.WBEMClient: Received Socket error: [Errno 111] Connection refused from query: HPEVA_StorageSystem

I desided to remove the EVA and add it again, but nothing happens - no views of it and still a lof of connection refused on the WBEM.??

Any ideas what to do - I am new to this monitoring system and I really like it, but if I cannot trust it to work 100% then...

RE: HP EVA Monitor

community@zenoss.org — Wed, 14 Dec 2011 18:31:35 GMT

Hi Jørgen Staun,

restart your CommandView server.

RE: HP EVA Monitor

community@zenoss.org — Tue, 20 Dec 2011 12:39:47 GMT

Worked like a charm, weird though.

But I still get these errors in the event manager.

Could not get WBEM Instance (Received Socket error: [Errno 111] Connection refused from query: HPEVA_DiskDriveStatisticalData)

RE: HP EVA Monitor

community@zenoss.org — Wed, 14 Mar 2012 12:32:13 GMT

Any ideas why I can't model the EVA 6000?

ERROR zen.ZenModeler: Client 5000-1FE1-5012-CFD0 finished with message: [Failure instance: Traceback (failure with no frames): : Traceback (most recent call last):

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

return callable(*args, **kw)

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

result = inner(map)

File "/opt/zenoss/Products/ZenHub/services/ModelerService.py", line 114, in inner

if adm._applyDataMap(device, map):

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

changed = self._updateRelationship(tobj, datamap)

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

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

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

rel._setObject(remoteObj.id, remoteObj)

File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 125, in _setObject

self.addRelation(object)

File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 116, in addRelation

ToManyRelationshipBase.addRelation(self, obj)

File "/opt/zenoss/Products/ZenRelations/RelationshipBase.py", line 94, in addRelation

obj.id, obj.__class__.__name__))

ZenSchemaError: harddisks restricted to class HardDisk. 130807101D000020A3489C380000000000000000 is class HPEVADiskDrive

Is the problem with WWN I used for "SNMP SysName?

CentOS 5 (2.6.18-274.18.1.el5), Zenoss 3.2.1, Python 2.6.2, WBEMDataSource 2.1, HPEVAMon 1.11

Rok

RE: HP EVA Monitor

community@zenoss.org — Wed, 14 Mar 2012 20:01:15 GMT

Hi Rok,

your EVA device must be created in the /Devices/CIM/HPEVA device class (NOT moved into it), so you must delete your EVA device, and readding it again direct to the /Devices/CIM/HPEVA device class.

RE: HP EVA Monitor

community@zenoss.org — Thu, 15 Mar 2012 13:50:13 GMT

Thank you bigegor, I trully appreciate your time & effort!

I deleted the device and added it again, I guess I added it too soon after installation of zenpacks (wbem & HPeva).

Now modeling succeeded, it shows me the FC ports, Disk groups, Controllers, Virtual Disks, Hard Disks & Enclosures under components, but stills getting errors for everything it tries to access through wbem (for instance):

Could not get WBEM Instance (Received Namespace root/eva has no definition for class HPEVA_StorageSystemControllerStatisticalData from query: HPEVA_StorageSystemControllerStatisticalData)

Could not get WBEM Instance (Received Namespace root/eva has no definition for class HPEVA_VolumeStatisticalData from query: HPEVA_VolumeStatisticalData)

The only graph working is Utilization graph...

Rok

RE: HP EVA Monitor

community@zenoss.org — Fri, 27 Apr 2012 05:04:33 GMT

Running the latest CV EVA 10 and have this error in the Status/PyDBAPI.

Received error ('NoneType' object is not iterable) from query: SELECT KBytesWritten,QDepth,LinkFail,InstanceID,WriteLatencyTime_ms,ReadIOs,KBytesRead,WriteIOs,ReadLatencyTime_ms FROM HPEVA_HostFCPortStatisticalData

I am running HPEVAMon 1.11, SQLDataSource 1.98, and WBEMDataSource 2.84.

It appears to be collecting everything else fine.

Any help appreciated.

RE: HP EVA Monitor

community@zenoss.org — Wed, 02 May 2012 20:24:18 GMT

Hi Serpent,

please, try latest SQLDataSource (2.0) and WBEMDataSource (3.0) ZenPacks.

RE: HP EVA Monitor

community@zenoss.org — Wed, 02 May 2012 20:41:06 GMT

Oh you updated those two. I was looking for those. Sneaky!!

Thanks for the reply. I'll keep you posted if there is still a problem.

Brad

RE: HP EVA Monitor

community@zenoss.org — Wed, 02 May 2012 21:42:00 GMT

Hey Egor. The other issue looks fixed. However here is a couple warnings that came up:

2012-05-02 14:38:01,754 INFO zen.SQLClient: SQL client finished collection for 5000-1FE1-501E-F2E0

2012-05-02 14:38:02,562 WARNING zen.SQLClient: Error in community.wbem.HPEVAConsistencySetMap query "SELECT * FROM HPEVA_ConsistencySet": need more than 0 values to unpack

2012-05-02 14:38:02,562 INFO zen.SQLClient: SQL client finished collection for 5000-1FE1-501E-F2E0

2012-05-02 14:38:02,562 WARNING zen.PythonClient: Error in community.wbem.HPEVAConsistencySetMap: need more than 0 values to unpack

2012-05-02 14:38:03,436 WARNING zen.SQLClient: Error in community.wbem.HPEVAStorageVolumeMap query "SELECT * FROM HPEVA_OrderedMemberOfCollection": need more than 0 values to unpack

2012-05-02 14:38:13,699 WARNING zen.SQLClient: Error in community.wbem.HPEVAStorageVolumeMap query "SELECT * FROM HPEVA_StorageVolume": socket error: The read operation timed out

2012-05-02 14:38:13,699 INFO zen.SQLClient: SQL client finished collection for 5000-1FE1-501E-F2E0

2012-05-02 14:38:13,699 WARNING zen.PythonClient: Error in community.wbem.HPEVAStorageVolumeMap: socket error: The read operation timed out

2012-05-02 14:38:13,700 INFO zen.PythonClient: Python client finished collection for 5000-1FE1-501E-F2E0

ZenPacks.community.HPEVAMon 1.11

ZenPacks.community.SQLDataSource 2.0

ZenPacks.community.WBEMDataSource 3.0

RE: HP EVA Monitor

community@zenoss.org — Thu, 03 May 2012 20:59:32 GMT

Hi Serpent,

you can increase timeout value in file:

ZenPacks.community.SQLDataSource/ZenPacks/community/SQLDataSource/lib/pywbemdb.py, in line 604 change 10 to 25.

RE: HP EVA Monitor

community@zenoss.org — Wed, 09 May 2012 18:55:39 GMT

bigegor,

Updated the timeout and have these errors. Also I can remodel the device and see the components but after a while they go away and I have to remodel them again.

2012-05-09 11:51:47,731 WARNING zen.SQLClient: Error in community.wbem.HPEVAConsistencySetMap query "SELECT * FROM HPEVA_ConsistencySet": need more than 0 values to unpack

2012-05-09 11:51:47,731 INFO zen.SQLClient: SQL client finished collection for 5000-1FE1-501E-F270

2012-05-09 11:51:47,731 WARNING zen.PythonClient: Error in community.wbem.HPEVAConsistencySetMap: need more than 0 values to unpack

2012-05-09 11:51:48,605 WARNING zen.SQLClient: Error in community.wbem.HPEVAStorageVolumeMap query "SELECT * FROM HPEVA_OrderedMemberOfCollection": need more than 0 values to unpack

Any help appreciated.

RE: HP EVA Monitor

community@zenoss.org — Sun, 13 May 2012 20:41:10 GMT

Hi Serpent,

can you check if CV10 CIMOM provides HPEVA_ConsistencySet and HPEVA_OrderedMemberOfCollection classes.

RE: HP EVA Monitor

community@zenoss.org — Wed, 30 May 2012 00:36:52 GMT

bigegor,

I've just installed WBEM 2.10 + HPEVA 1.11, configured the properties according the instructions. The array is an HP 4400 and the CV version is 9.1

When run the modeler, some warnings appeared as follow

2012-05-29 21:34:24,153 INFO zen.ZenModeler: Connecting to localhost:8789

2012-05-29 21:34:24,171 INFO zen.ZenModeler: Connected to ZenHub

2012-05-29 21:34:24,261 INFO zen.ZenModeler: Collecting for device 5001-4380-04C7-B5A0

2012-05-29 21:34:24,328 INFO zen.ZenModeler: No WMI plugins found for 5001-4380-04C7-B5A0

2012-05-29 21:34:24,330 INFO zen.ZenModeler: Python collection device 5001-4380-04C7-B5A0

2012-05-29 21:34:24,331 INFO zen.ZenModeler: plugins: community.wbem.HPEVADeviceMap, community.wbem.HPEVAStorageDiskEnclosureMap, community.wbem.HPEVAStoragePoolMap, community.wbem.HPEVAStorageProcessorCardMap, community.wbem.HPEVAHostFCPortMap, community.wbem.HPEVADiskDriveMap, community.wbem.HPEVAConsistencySetMap, community.wbem.HPEVAStorageVolumeMap

2012-05-29 21:34:30,911 INFO zen.ZenModeler: No command plugins found for 5001-4380-04C7-B5A0

2012-05-29 21:34:30,911 INFO zen.ZenModeler: SNMP monitoring off for 5001-4380-04C7-B5A0

2012-05-29 21:34:30,912 INFO zen.ZenModeler: No portscan plugins found for 5001-4380-04C7-B5A0

2012-05-29 21:34:30,912 WARNING zen.PythonClient: Error in community.wbem.HPEVADeviceMap: tuple index out of range

2012-05-29 21:34:30,912 WARNING zen.PythonClient: Error in community.wbem.HPEVAStorageDiskEnclosureMap: tuple index out of range

2012-05-29 21:34:30,913 WARNING zen.PythonClient: Error in community.wbem.HPEVAStoragePoolMap: tuple index out of range

2012-05-29 21:34:30,913 WARNING zen.PythonClient: Error in community.wbem.HPEVAStorageProcessorCardMap: tuple index out of range

2012-05-29 21:34:30,914 WARNING zen.PythonClient: Error in community.wbem.HPEVAHostFCPortMap: tuple index out of range

2012-05-29 21:34:30,915 WARNING zen.PythonClient: Error in community.wbem.HPEVADiskDriveMap: tuple index out of range

2012-05-29 21:34:30,916 WARNING zen.PythonClient: Error in community.wbem.HPEVAConsistencySetMap: tuple index out of range

2012-05-29 21:34:30,916 WARNING zen.PythonClient: Error in community.wbem.HPEVAStorageVolumeMap: tuple index out of range

2012-05-29 21:34:30,916 INFO zen.PythonClient: Python client finished collection for 5001-4380-04C7-B5A0

2012-05-29 21:34:30,916 INFO zen.ZenModeler: No change in configuration detected

2012-05-29 21:34:30,916 INFO zen.ZenModeler: Scan time: 6.66 seconds

2012-05-29 21:34:30,926 INFO zen.ZenModeler: Daemon ZenModeler shutting down

Any suggestionwill be welcome!

RE: HP EVA Monitor

community@zenoss.org — Thu, 09 Aug 2012 13:12:23 GMT

I have some problems getting the zenmodeler to complete succesfully. When I model the device I get the following output:

2012-08-09 15:08:37,811 INFO zen.ZenModeler: processing community.wbem.HPEVADeviceMap for device 5001-4380-04C6-BEB0

2012-08-09 15:08:37,811 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageDiskEnclosureMap for device 5001-4380-04C6-BEB0

2012-08-09 15:08:37,813 INFO zen.ZenModeler: processing community.wbem.HPEVAStoragePoolMap for device 5001-4380-04C6-BEB0

2012-08-09 15:08:37,814 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageProcessorCardMap for device 5001-4380-04C6-BEB0

2012-08-09 15:08:37,815 INFO zen.ZenModeler: processing community.wbem.HPEVAHostFCPortMap for device 5001-4380-04C6-BEB0

2012-08-09 15:08:37,816 INFO zen.ZenModeler: processing community.wbem.HPEVADiskDriveMap for device 5001-4380-04C6-BEB0

2012-08-09 15:08:37,827 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageVolumeMap for device 5001-4380-04C6-BEB0

2012-08-09 15:08:37,829 INFO zen.ZenModeler: processing community.wbem.HPEVAConsistencySetMap for device 5001-4380-04C6-BEB0

Traceback (most recent call last):

File "/opt/zenoss/lib/python2.7/logging/__init__.py", line 842, in emit

msg = self.format(record)

File "/opt/zenoss/lib/python2.7/logging/__init__.py", line 719, in format

return fmt.format(record)

File "/opt/zenoss/lib/python2.7/logging/__init__.py", line 464, in format

record.message = record.getMessage()

File "/opt/zenoss/lib/python2.7/logging/__init__.py", line 324, in getMessage

msg = str(self.msg)

File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 49, in __str__

return Exception.__str__(self) + self.traceback

TypeError: cannot concatenate 'str' and 'NoneType' objects

Logged from file zenmodeler.py, line 688

2012-08-09 15:08:38,496 ERROR zen.ZenModeler: Client 5001-4380-04C6-BEB0 finished with message: [Failure instance: Traceback (failure with no frames): :

Traceback (most recent call last):

File "/opt/zenoss/lib/python/twisted/python/reflect.py", line 546, in _safeFormat

return formatter(o)

File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 49, in __str__

return Exception.__str__(self) + self.traceback

TypeError: cannot concatenate 'str' and 'NoneType' objects

]

2012-08-09 15:08:38,496 INFO zen.ZenModeler: Scan time: 8.30 seconds

2012-08-09 15:08:38,525 INFO zen.ZenModeler: Daemon ZenModeler shutting down

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

Zenoss version 4.2

CV 10.0

ZenPacks.community.HPEVAMon	community	Egor Puzanov	1.11	Yes
ZenPacks.community.SQLDataSource	community	Egor Puzanov	2.2	Yes
ZenPacks.community.WBEMDataSource	community	Egor Puzanov	3.0	Yes

Any suggestion is welcome.

RE: HP EVA Monitor

community@zenoss.org — Thu, 09 Aug 2012 20:06:53 GMT

Hi kybe,

remove community.wbem.HPEVAConsistencySetMap plugin from collector plugins list

RE: HP EVA Monitor

community@zenoss.org — Fri, 10 Aug 2012 07:26:44 GMT

Hello,

I have experimented with reordering the modules and removing the last one, but the same problem reoccurs:

012-08-10 09:23:00,837 INFO zen.ZenModeler: processing community.wbem.HPEVADeviceMap for device 5001-4380-04C6-BEB0

2012-08-10 09:23:00,837 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageDiskEnclosureMap for device 5001-4380-04C6-BEB0

2012-08-10 09:23:00,839 INFO zen.ZenModeler: processing community.wbem.HPEVAStoragePoolMap for device 5001-4380-04C6-BEB0

2012-08-10 09:23:00,840 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageProcessorCardMap for device 5001-4380-04C6-BEB0

2012-08-10 09:23:00,841 INFO zen.ZenModeler: processing community.wbem.HPEVAHostFCPortMap for device 5001-4380-04C6-BEB0

2012-08-10 09:23:00,843 INFO zen.ZenModeler: processing community.wbem.HPEVADiskDriveMap for device 5001-4380-04C6-BEB0

2012-08-10 09:23:00,855 INFO zen.ZenModeler: processing community.wbem.HPEVAStorageVolumeMap for device 5001-4380-04C6-BEB0

Traceback (most recent call last):

File "/opt/zenoss/lib/python2.7/logging/__init__.py", line 842, in emit

msg = self.format(record)

File "/opt/zenoss/lib/python2.7/logging/__init__.py", line 719, in format

return fmt.format(record)

File "/opt/zenoss/lib/python2.7/logging/__init__.py", line 464, in format

record.message = record.getMessage()

File "/opt/zenoss/lib/python2.7/logging/__init__.py", line 324, in getMessage

msg = str(self.msg)

File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 49, in __str__

return Exception.__str__(self) + self.traceback

TypeError: cannot concatenate 'str' and 'NoneType' objects

Logged from file zenmodeler.py, line 688

2012-08-10 09:23:01,757 ERROR zen.ZenModeler: Client 5001-4380-04C6-BEB0 finished with message: [Failure instance: Traceback (failure with no frames): :

Traceback (most recent call last):

File "/opt/zenoss/lib/python/twisted/python/reflect.py", line 546, in _safeFormat

return formatter(o)

File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 49, in __str__

return Exception.__str__(self) + self.traceback

TypeError: cannot concatenate 'str' and 'NoneType' objects

]

2012-08-10 09:23:01,757 INFO zen.ZenModeler: Scan time: 7.71 seconds

RE: HP EVA Monitor

community@zenoss.org — Fri, 10 Aug 2012 14:07:21 GMT

Hi kybe,

HP has changed something in CV10. Can you check if CV10 CIMOM provides HPEVA_ConsistencySet, HPEVA_StorageVolume and HPEVA_OrderedMemberOfCollection classes?

RE: HP EVA Monitor

community@zenoss.org — Thu, 16 Aug 2012 08:13:58 GMT

Hi bigegor,

thanks for that great ZenPack. I got only one funny issue. It is working nearly fine for both EVA's. Just get a "value error: cannot convert float NaN to integer" when switching in details view to components -> Disk groups (but it nows we have 2 which seems to not include ungrouped disks).

But on one of the EVA's I got these events:

prodState,firstTime,eventClassKey,agent,dedupid,manager,Location,component_url,ownerid,eventClassMapping_url,eventClass,zenoss.device.priority,id,device_title,DevicePriority,facility,eventClass_url,monitor,priority,device_url,DeviceClass,eventKey,evid,eventClassMapping,component,clearid,DeviceGroups,eventGroup,device,Systems,component_title,severity,count,stateChange,ntevid,summary,message,eventState,zenoss.device.device_class,zenoss.device.production_state,lastTime,ipAddress,component_uuid

Production,2012-08-16 09:48:26,,zenmodeler,5001-4380-025B-60D0||/Status/Update|4|Problem while executing plugin community.wbem.HPEVAStorageVolumeMap,B0621S997.bg.eu.jci.com,,,,,/Status/Update,5,0050569e-7691-bbef-11e1-e776c3790207,EVA64_260,Highest,,/zport/dmd/Events/Status/Update,localhost,,/zport/dmd/goto?guid=73ebc966-b0ad-4839-ad9a-2b99fdb1d607,"[{'uid': u'/zport/dmd/Devices/CIM/HPEVA', 'name': u'/CIM/HPEVA'}]",,0050569e-7691-bbef-11e1-e776c3790207,,,,,,5001-4380-025B-60D0,,,4,2,2012-08-16 09:48:26,,Problem while executing plugin community.wbem.HPEVAStorageVolumeMap,"Traceback (most recent call last): File ""/opt/zenoss/Products/DataCollector/zenmodeler.py"", line 634, in processClient datamaps = plugin.process(device, results, self.log) File ""/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.11.egg/ZenPacks/community/HPEVAMon/modeler/plugins/community/wbem/HPEVAStorageVolumeMap.py"", line 91, in process if instance[""_sname""] != sysname: continue KeyError: '_sname'",New,/CIM/HPEVA,1000,2012-08-16 09:57:27,,

Production,2012-08-16 09:48:26,,zenmodeler,5001-4380-025B-60D0||/Status/Update|4|Problem while executing plugin community.wbem.HPEVAConsistencySetMap,B0621S997.bg.eu.jci.com,,,,,/Status/Update,5,0050569e-7691-bbef-11e1-e776c367eb06,EVA64_260,Highest,,/zport/dmd/Events/Status/Update,localhost,,/zport/dmd/goto?guid=73ebc966-b0ad-4839-ad9a-2b99fdb1d607,"[{'uid': u'/zport/dmd/Devices/CIM/HPEVA', 'name': u'/CIM/HPEVA'}]",,0050569e-7691-bbef-11e1-e776c367eb06,,,,,,5001-4380-025B-60D0,,,4,2,2012-08-16 09:48:26,,Problem while executing plugin community.wbem.HPEVAConsistencySetMap,"Traceback (most recent call last): File ""/opt/zenoss/Products/DataCollector/zenmodeler.py"", line 634, in processClient datamaps = plugin.process(device, results, self.log) File ""/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.11.egg/ZenPacks/community/HPEVAMon/modeler/plugins/community/wbem/HPEVAConsistencySetMap.py"", line 61, in process if not instance[""id""].startswith(sysname): continue KeyError: 'id'",New,/CIM/HPEVA,1000,2012-08-16 09:57:27,,

Production,2012-08-16 09:48:26,,zenmodeler,5001-4380-025B-60D0||/Status/Update|4|Problem while executing plugin community.wbem.HPEVADiskDriveMap,B0621S997.bg.eu.jci.com,,,,,/Status/Update,5,0050569e-7691-bbef-11e1-e776c3554d65,EVA64_260,Highest,,/zport/dmd/Events/Status/Update,localhost,,/zport/dmd/goto?guid=73ebc966-b0ad-4839-ad9a-2b99fdb1d607,"[{'uid': u'/zport/dmd/Devices/CIM/HPEVA', 'name': u'/CIM/HPEVA'}]",,0050569e-7691-bbef-11e1-e776c3554d65,,,,,,5001-4380-025B-60D0,,,4,2,2012-08-16 09:48:26,,Problem while executing plugin community.wbem.HPEVADiskDriveMap,"Traceback (most recent call last): File ""/opt/zenoss/Products/DataCollector/zenmodeler.py"", line 634, in processClient datamaps = plugin.process(device, results, self.log) File ""/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.11.egg/ZenPacks/community/HPEVAMon/modeler/plugins/community/wbem/HPEVADiskDriveMap.py"", line 73, in process diskModules[instance['_id']] = instance KeyError: '_id'",New,/CIM/HPEVA,1000,2012-08-16 09:57:27,,

Production,2012-08-16 09:48:26,,zenmodeler,5001-4380-025B-60D0||/Status/Update|4|Problem while executing plugin community.wbem.HPEVAHostFCPortMap,B0621S997.bg.eu.jci.com,,,,,/Status/Update,5,0050569e-7691-bbef-11e1-e776c347dfe4,EVA64_260,Highest,,/zport/dmd/Events/Status/Update,localhost,,/zport/dmd/goto?guid=73ebc966-b0ad-4839-ad9a-2b99fdb1d607,"[{'uid': u'/zport/dmd/Devices/CIM/HPEVA', 'name': u'/CIM/HPEVA'}]",,0050569e-7691-bbef-11e1-e776c347dfe4,,,,,,5001-4380-025B-60D0,,,4,2,2012-08-16 09:48:26,,Problem while executing plugin community.wbem.HPEVAHostFCPortMap,"Traceback (most recent call last): File ""/opt/zenoss/Products/DataCollector/zenmodeler.py"", line 634, in processClient datamaps = plugin.process(device, results, self.log) File ""/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.11.egg/ZenPacks/community/HPEVAMon/modeler/plugins/community/wbem/HPEVAHostFCPortMap.py"", line 121, in process if not instance[""setController""].startswith(sysname): continue KeyError: 'setController'",New,/CIM/HPEVA,1000,2012-08-16 09:57:27,,

Production,2012-08-16 09:48:26,,zenmodeler,5001-4380-025B-60D0||/Status/Update|4|Problem while executing plugin community.wbem.HPEVAStorageProcessorCardMap,B0621S997.bg.eu.jci.com,,,,,/Status/Update,5,0050569e-7691-bbef-11e1-e776c3359063,EVA64_260,Highest,,/zport/dmd/Events/Status/Update,localhost,,/zport/dmd/goto?guid=73ebc966-b0ad-4839-ad9a-2b99fdb1d607,"[{'uid': u'/zport/dmd/Devices/CIM/HPEVA', 'name': u'/CIM/HPEVA'}]",,0050569e-7691-bbef-11e1-e776c3359063,,,,,,5001-4380-025B-60D0,,,4,2,2012-08-16 09:48:26,,Problem while executing plugin community.wbem.HPEVAStorageProcessorCardMap,"Traceback (most recent call last): File ""/opt/zenoss/Products/DataCollector/zenmodeler.py"", line 634, in processClient datamaps = plugin.process(device, results, self.log) File ""/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.11.egg/ZenPacks/community/HPEVAMon/modeler/plugins/community/wbem/HPEVAStorageProcessorCardMap.py"", line 57, in process if not instance[""id""].startswith(sysname): continue KeyError: 'id'",New,/CIM/HPEVA,1000,2012-08-16 09:57:27,,

Production,2012-08-16 09:48:25,,zenmodeler,5001-4380-025B-60D0||/Status/Update|4|Problem while executing plugin community.wbem.HPEVAStoragePoolMap,B0621S997.bg.eu.jci.com,,,,,/Status/Update,5,0050569e-7691-bbef-11e1-e776c31bc6d2,EVA64_260,Highest,,/zport/dmd/Events/Status/Update,localhost,,/zport/dmd/goto?guid=73ebc966-b0ad-4839-ad9a-2b99fdb1d607,"[{'uid': u'/zport/dmd/Devices/CIM/HPEVA', 'name': u'/CIM/HPEVA'}]",,0050569e-7691-bbef-11e1-e776c31bc6d2,,,,,,5001-4380-025B-60D0,,,4,2,2012-08-16 09:48:25,,Problem while executing plugin community.wbem.HPEVAStoragePoolMap,"Traceback (most recent call last): File ""/opt/zenoss/Products/DataCollector/zenmodeler.py"", line 634, in processClient datamaps = plugin.process(device, results, self.log) File ""/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.11.egg/ZenPacks/community/HPEVAMon/modeler/plugins/community/wbem/HPEVAStoragePoolMap.py"", line 58, in process if not instance[""id""].startswith(sysname): continue KeyError: 'id'",New,/CIM/HPEVA,1000,2012-08-16 09:57:27,,

Production,2012-08-16 09:48:25,,zenmodeler,5001-4380-025B-60D0||/Status/Update|4|Problem while executing plugin community.wbem.HPEVAStorageDiskEnclosureMap,B0621S997.bg.eu.jci.com,,,,,/Status/Update,5,0050569e-7691-bbef-11e1-e776c2f52c01,EVA64_260,Highest,,/zport/dmd/Events/Status/Update,localhost,,/zport/dmd/goto?guid=73ebc966-b0ad-4839-ad9a-2b99fdb1d607,"[{'uid': u'/zport/dmd/Devices/CIM/HPEVA', 'name': u'/CIM/HPEVA'}]",,0050569e-7691-bbef-11e1-e776c2f52c01,,,,,,5001-4380-025B-60D0,,,4,2,2012-08-16 09:48:25,,Problem while executing plugin community.wbem.HPEVAStorageDiskEnclosureMap,"Traceback (most recent call last): File ""/opt/zenoss/Products/DataCollector/zenmodeler.py"", line 634, in processClient datamaps = plugin.process(device, results, self.log) File ""/opt/zenoss/ZenPacks/ZenPacks.community.HPEVAMon-1.11.egg/ZenPacks/community/HPEVAMon/modeler/plugins/community/wbem/HPEVAStorageDiskEnclosureMap.py"", line 65, in process sysmodels[instance['_sname']] = instance['sysmodel'] KeyError: 'sysmodel'",New,/CIM/HPEVA,1000,2012-08-16 09:57:27,,

We use CV 9.02.01.100426 currently.

Thanks for the great Zenpack's so far.

Cheers

Daniel

RE: HP EVA Monitor

community@zenoss.org — Thu, 16 Aug 2012 14:03:37 GMT

I am out of the office until 27.08.2012.

Note: This is an automated response to your message "Re: HP EVA Monitor - HP

EVA Monitor" sent on 16.8.2012 10:17:15.

This is the only notification you will receive while this person is away.

RE: HP EVA Monitor

community@zenoss.org — Thu, 06 Sep 2012 18:59:08 GMT

This zenpack doesn't seem to work for zenoss core 4.2, I don't see the device class listed in the instructions and none screen shots attached to the post seem to appear for me.

Any chance you can update this to work with 4.2?

RE: HP EVA Monitor

community@zenoss.org — Fri, 25 Jan 2013 10:45:27 GMT

Hello, thank you for your great work.

I get the following error during the Device Model process:

2013-01-25 13:54:55,049 WARNING zen.SQLClient: Error in community.wbem.HPEVAStorageVolumeMap query "SELECT * FROM HPEVA_StorageVolume": XML parsing error: not well-formed (invalid token)

I've sent zenmodeler daemon log in private message.

RE: HP EVA Monitor

community@zenoss.org — Tue, 26 Mar 2013 09:33:25 GMT

Is there anyway to monitor HP EVA devices without the Command View server?