Archived community.zenoss.org | full text search
Skip navigation
Up to Discussions in zenoss-windows
4945 Views 7 Replies Latest reply: Oct 12, 2012 10:49 AM by cordeos RSS
Alexey Bobov Newbie
Alexey Bobov
5 posts since
Jan 5, 2012
Currently Being Moderated

Aug 30, 2012 10:24 AM

Logical volumes issue v 4.2.0 zenoss

Hi,

there is a little issue with logical volumes when upgrading to version 4.2.0.

Component 'File Systems', if there are several logical volumes, zenoss don't succeed to count

Used Bytes, Free Bytes, %Util

 

Device: Device

Component: zen.winperf.PerfRpc
Severity: Warning
Time: 2012/08/30 17:04:24.000
Message:
Bad counter for device 192.168.11.46: \LogicalDisk(\\?\Volume{69126123-19da-11e0-92d2-806e6f6e6963})\Free Megabytes

 

....
Bad counter for device 192.168.11.46: \LogicalDisk(\\?\Volume{69126123-19da-11e0-92d2-806e6f6e6963})\Disk Write Bytes/sec

 

.....

Bad counter for device 192.168.11.46: \LogicalDisk(\\?\Volume{69126123-19da-11e0-92d2-806e6f6e6963})\Disk Read Bytes/sec



 

Does anybody has the same issue, or are there any resolve for it.

Thanks.file_systems_utilization.jpg

Tags: wmi
  • stwainer Rank: White Belt
    stwainer
    76 posts since
    Dec 14, 2007
    Currently Being Moderated
    1. Sep 18, 2012 5:34 PM (in response to Alexey Bobov)
    Re: Logical volumes issue v 4.2.0 zenoss

    I'm not getting the error messages you are, but I'm ceratainly not getting any data from WMI about any of my Windows servers volumes.

  • Bernhard Marx Newbie
    Bernhard Marx
    3 posts since
    Sep 18, 2012
    Currently Being Moderated
    2. Sep 19, 2012 9:38 AM (in response to Alexey Bobov)
    Re: Logical volumes issue v 4.2.0 zenoss

    Hi,

     

    I have the same issue with the system-partitio (this 100 MB thing)...

    But no hint except disable monitoring. But modeling the device every 12 hours, enables the check again :-(

     

    Bernhard

  • svenjacobs Rank: White Belt
    svenjacobs
    14 posts since
    Mar 16, 2012
    Currently Being Moderated
    3. Sep 26, 2012 7:21 AM (in response to Alexey Bobov)
    Re: Logical volumes issue v 4.2.0 zenoss

    Have the same problems ... :-(

  • crock Rank: White Belt
    crock
    12 posts since
    Jul 21, 2008
    Currently Being Moderated
    4. Sep 28, 2012 11:46 AM (in response to svenjacobs)
    Re: Logical volumes issue v 4.2.0 zenoss

    Look at this about how to get rid of the alerts

    thread/16187

     

    Mentions a bit 2/3 down about a transform on the event which seems to work OK for me on 4.2

     

    Question I've got is that I've got a clustered shared volume on a Hyper-v cluster which returns the same sort of missing data, problem here is that it's a real volume not the crappy 100mb hidden partition and I really really need to see the % usage on it. It never gets a drive letter though as it's effictively mounted as a junction point.,

    Any clever ideas?

  • cordeos Rank: White Belt
    cordeos
    15 posts since
    Oct 11, 2012
    Currently Being Moderated
    5. Oct 12, 2012 10:16 AM (in response to crock)
    Re: Logical volumes issue v 4.2.0 zenoss

    We have built a quick python code fix for this in the FileSystemMap module...

    message/69103#69103

     

    this might help (might.. )

  • crock Rank: White Belt
    crock
    12 posts since
    Jul 21, 2008
    Currently Being Moderated
    6. Oct 12, 2012 10:34 AM (in response to cordeos)
    Re: Logical volumes issue v 4.2.0 zenoss

    Just tried this and it does get rid of the annoying 100mb partition but doesn't help my main problem.

    Cluster shared volumes only appear with the //?/ name so this gets rid of those as well.

     

    Good work though, I realise I'm in the minority using Hyper-v not VMWare

  • cordeos Rank: White Belt
    cordeos
    15 posts since
    Oct 11, 2012
    Currently Being Moderated
    7. Oct 12, 2012 10:49 AM (in response to crock)
    Re: Logical volumes issue v 4.2.0 zenoss

    We have this same problem with some special, non-lettered drives.  We decided to get rid of these special drive zenoss WMI components altogether in the Windows WMI modelling because the OS currently does not provide any framework for WMI, perfmon or SNMP to gather any reasonable info from them.  Most of the current storage units we are using have pretty good SNMP or SSH onboard which provide much better "from the source" information about the current state of the arrays/volumes - so we decided to scrap any modeling through windows and get it from the storage units themselves.

     

    In your current setup i dont think there is any way you will be able to get WMI modeled stats from your drives as the volume connections are through proprietary drivers which have no perfmon counters included.

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points