Nov 24, 2008 2:16 PM
Hardware Tab - CPU/Memory/Swap info?
-
Like (0)
_______________________________________________
V2.3
(Devicename) Hardware Tab
Can anyone provide info on how the CPU, Memory and Swap fields under the "Hardware" tab get populated?
Is it obtained through SNMP? Where is it defined?
thanks
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users
"tec" wrote:
I don't see any settings that relate to those fields.
Can you provide the path so I can navigate to the config settings?
V2.3
(Devicename) Hardware Tab
Can anyone provide info on how the CPU, Memory and Swap fields under the "Hardware" tab get populated?
Is it obtained through SNMP? Where is it defined?
thanks
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org ([email]zenoss-users@zenoss.org[/email])
http://lists.zenoss.org/mailman/listinfo/zenoss-users
I'm curious about where these values are set as well. A couple of
my machines are reporting incorrect values on the hardware tab, but
when I query the UCD-SNMP-MIB::memTotalSwap.0 oid, it reports
correctly.
I'm looking through the collector plugins and have yet to find one
other than the UCDHardDiskMap that attempts to set the swap space.
Can one of the Zenoss dev's comment on where these values are probed
from?
On Jan 5, 2009, at 2:52 PM, Trey Sheldon wrote:
I'm curious about where these values are set as well. A couple of
my machines are reporting incorrect values on the hardware tab, but
when I query the UCD-SNMP-MIB::memTotalSwap.0 oid, it reports
correctly.
I'm looking through the collector plugins and have yet to find one
other than the UCDHardDiskMap that attempts to set the swap space.
Can one of the Zenoss dev's comment on where these values are probed
from?
This information is collected by the HRFileSystemMap modeler plugin.
If you snmpwalk to the .1.3.6.1.2.1.25.2.3.1 on a system with the Net-
SNMP agent on it you will see that it includes information about all
of the file systems along with physical memory and swap. The source
for this modeler plugin can be found at ZENHOME/Products/
DataCollector/plugins/zenoss/snmp/HRFileSystemMap.py.
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org ([email]zenoss-users@zenoss.org[/email])
http://lists.zenoss.org/mailman/listinfo/zenoss-users
Then that's interesting.....
a walk of 1.3.6.1.2.1.25.2.3.1 on the box in question returns:
HOST-RESOURCES-MIB::hrStorageIndex.10 = INTEGER: 10
HOST-RESOURCES-MIB::hrStorageType.10 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap space
HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 15631236
HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 2784
Resetting the detected swap size and remodeling the box enters 32830689280 in the os.totalSwap property.
Is there a chance that the HRFileSystemMap is adding values anywhere? The reason I ask is there's two partitions that are detected as "hrStorageVirtualMemory", but the partition sizes don't add up to the weird 32830689280 number. (I've append the full walk below for the curious people.
<begin paste>
HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1
HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3
HOST-RESOURCES-MIB::hrStorageIndex.6 = INTEGER: 6
HOST-RESOURCES-MIB::hrStorageIndex.7 = INTEGER: 7
HOST-RESOURCES-MIB::hrStorageIndex.8 = INTEGER: 8
HOST-RESOURCES-MIB::hrStorageIndex.10 = INTEGER: 10
HOST-RESOURCES-MIB::hrStorageIndex.31 = INTEGER: 31
HOST-RESOURCES-MIB::hrStorageIndex.32 = INTEGER: 32
HOST-RESOURCES-MIB::hrStorageIndex.33 = INTEGER: 33
HOST-RESOURCES-MIB::hrStorageIndex.34 = INTEGER: 34
HOST-RESOURCES-MIB::hrStorageType.1 = OID: HOST-RESOURCES-TYPES::hrStorageRam
HOST-RESOURCES-MIB::hrStorageType.3 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageType.6 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.7 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.8 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.10 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageType.31 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.32 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.33 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.34 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: Physical memory
HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: Virtual memory
HOST-RESOURCES-MIB::hrStorageDescr.6 = STRING: Memory buffers
HOST-RESOURCES-MIB::hrStorageDescr.7 = STRING: Cached memory
HOST-RESOURCES-MIB::hrStorageDescr.8 = STRING: Shared memory
HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap space
HOST-RESOURCES-MIB::hrStorageDescr.31 = STRING: /
HOST-RESOURCES-MIB::hrStorageDescr.32 = STRING: /usr
HOST-RESOURCES-MIB::hrStorageDescr.33 = STRING: /var
HOST-RESOURCES-MIB::hrStorageDescr.34 = STRING: /mw
HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.6 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.7 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.8 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.31 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.32 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.33 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.34 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: 16429984
HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 32061220
HOST-RESOURCES-MIB::hrStorageSize.6 = INTEGER: 7620
HOST-RESOURCES-MIB::hrStorageSize.7 = INTEGER: 10217220
HOST-RESOURCES-MIB::hrStorageSize.8 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 15631236
HOST-RESOURCES-MIB::hrStorageSize.31 = INTEGER: 962573
HOST-RESOURCES-MIB::hrStorageSize.32 = INTEGER: 3366154
HOST-RESOURCES-MIB::hrStorageSize.33 = INTEGER: 3366154
HOST-RESOURCES-MIB::hrStorageSize.34 = INTEGER: 131613872
HOST-RESOURCES-MIB::hrStorageUsed.1 = INTEGER: 16169268
HOST-RESOURCES-MIB::hrStorageUsed.3 = INTEGER: 16169268
HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageUsed.31 = INTEGER: 72470
HOST-RESOURCES-MIB::hrStorageUsed.32 = INTEGER: 550869
HOST-RESOURCES-MIB::hrStorageUsed.33 = INTEGER: 129215
HOST-RESOURCES-MIB::hrStorageUsed.34 = INTEGER: 54250398
On Mon, Jan 5, 2009 at 3:35 PM, Chet Luther <cluther@zenoss.com ([email]cluther@zenoss.com[/email])> wrote:
On Jan 5, 2009, at 2:52 PM, Trey Sheldon wrote:
I'm curious about where these values are set as well. A couple of
my machines are reporting incorrect values on the hardware tab, but
when I query the UCD-SNMP-MIB::memTotalSwap.0 oid, it reports
correctly.
I'm looking through the collector plugins and have yet to find one
other than the UCDHardDiskMap that attempts to set the swap space.
Can one of the Zenoss dev's comment on where these values are probed
from?
This information is collected by the HRFileSystemMap modeler plugin.
If you snmpwalk to the .1.3.6.1.2.1.25.2.3.1 on a system with the Net-
SNMP agent on it you will see that it includes information about all
of the file systems along with physical memory and swap. The source
for this modeler plugin can be found at ZENHOME/Products/
DataCollector/plugins/zenoss/snmp/HRFileSystemMap.py.
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org ([email]zenoss-users@zenoss.org[/email])
http://lists.zenoss.org/mailman/listinfo/zenoss-users
Actually, may be on to something..... looks like the collector is grabbing the first "hrStorageVirtualMemory" entry, but on this machine this doesn't represent the swap space. .... now to find out what it actually represents.
thanks!
-trey
On Mon, Jan 5, 2009 at 4:30 PM, Trey Sheldon <glsheldo@gmail.com ([email]glsheldo@gmail.com[/email])> wrote:
Then that's interesting.....
a walk of 1.3.6.1.2.1.25.2.3.1 on the box in question returns:
HOST-RESOURCES-MIB::hrStorageIndex.10 = INTEGER: 10
HOST-RESOURCES-MIB::hrStorageType.10 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap space
HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 15631236
HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 2784
Resetting the detected swap size and remodeling the box enters 32830689280 in the os.totalSwap property.
Is there a chance that the HRFileSystemMap is adding values anywhere? The reason I ask is there's two partitions that are detected as "hrStorageVirtualMemory", but the partition sizes don't add up to the weird 32830689280 number. (I've append the full walk below for the curious people.
<begin paste>
HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1
HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3
HOST-RESOURCES-MIB::hrStorageIndex.6 = INTEGER: 6
HOST-RESOURCES-MIB::hrStorageIndex.7 = INTEGER: 7
HOST-RESOURCES-MIB::hrStorageIndex.8 = INTEGER: 8
HOST-RESOURCES-MIB::hrStorageIndex.10 = INTEGER: 10
HOST-RESOURCES-MIB::hrStorageIndex.31 = INTEGER: 31
HOST-RESOURCES-MIB::hrStorageIndex.32 = INTEGER: 32
HOST-RESOURCES-MIB::hrStorageIndex.33 = INTEGER: 33
HOST-RESOURCES-MIB::hrStorageIndex.34 = INTEGER: 34
HOST-RESOURCES-MIB::hrStorageType.1 = OID: HOST-RESOURCES-TYPES::hrStorageRam
HOST-RESOURCES-MIB::hrStorageType.3 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageType.6 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.7 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.8 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.10 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageType.31 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.32 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.33 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.34 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: Physical memory
HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: Virtual memory
HOST-RESOURCES-MIB::hrStorageDescr.6 = STRING: Memory buffers
HOST-RESOURCES-MIB::hrStorageDescr.7 = STRING: Cached memory
HOST-RESOURCES-MIB::hrStorageDescr.8 = STRING: Shared memory
HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap space
HOST-RESOURCES-MIB::hrStorageDescr.31 = STRING: /
HOST-RESOURCES-MIB::hrStorageDescr.32 = STRING: /usr
HOST-RESOURCES-MIB::hrStorageDescr.33 = STRING: /var
HOST-RESOURCES-MIB::hrStorageDescr.34 = STRING: /mw
HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.6 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.7 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.8 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.31 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.32 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.33 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.34 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: 16429984
HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 32061220
HOST-RESOURCES-MIB::hrStorageSize.6 = INTEGER: 7620
HOST-RESOURCES-MIB::hrStorageSize.7 = INTEGER: 10217220
HOST-RESOURCES-MIB::hrStorageSize.8 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 15631236
HOST-RESOURCES-MIB::hrStorageSize.31 = INTEGER: 962573
HOST-RESOURCES-MIB::hrStorageSize.32 = INTEGER: 3366154
HOST-RESOURCES-MIB::hrStorageSize.33 = INTEGER: 3366154
HOST-RESOURCES-MIB::hrStorageSize.34 = INTEGER: 131613872
HOST-RESOURCES-MIB::hrStorageUsed.1 = INTEGER: 16169268
HOST-RESOURCES-MIB::hrStorageUsed.3 = INTEGER: 16169268
HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageUsed.31 = INTEGER: 72470
HOST-RESOURCES-MIB::hrStorageUsed.32 = INTEGER: 550869
HOST-RESOURCES-MIB::hrStorageUsed.33 = INTEGER: 129215
HOST-RESOURCES-MIB::hrStorageUsed.34 = INTEGER: 54250398
On Mon, Jan 5, 2009 at 3:35 PM, Chet Luther <cluther@zenoss.com ([email]cluther@zenoss.com[/email])> wrote:
On Jan 5, 2009, at 2:52 PM, Trey Sheldon wrote:
I'm curious about where these values are set as well. A couple of
my machines are reporting incorrect values on the hardware tab, but
when I query the UCD-SNMP-MIB::memTotalSwap.0 oid, it reports
correctly.
I'm looking through the collector plugins and have yet to find one
other than the UCDHardDiskMap that attempts to set the swap space.
Can one of the Zenoss dev's comment on where these values are probed
from?
This information is collected by the HRFileSystemMap modeler plugin.
If you snmpwalk to the .1.3.6.1.2.1.25.2.3.1 on a system with the Net-
SNMP agent on it you will see that it includes information about all
of the file systems along with physical memory and swap. The source
for this modeler plugin can be found at ZENHOME/Products/
DataCollector/plugins/zenoss/snmp/HRFileSystemMap.py.
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org ([email]zenoss-users@zenoss.org[/email])
http://lists.zenoss.org/mailman/listinfo/zenoss-users
So after much digging, I'm not sure what that first entry represents- looks to be a sum of the physical ram & the swap space. However, it appears that Gentoo & OpenSuse both have hrStorageVirtualMemory entries that don't correspond directly to the Swap space. Centos and RedHat EL5 both report correctly though.
Maybe one of the dev's can comment on the possibility of changing the swap detection system so that it looks for the hrStorageDescr entry of "Swap space" instead of the hrStorageType?
I may work on a patch, but this looks like the appropriate way to go.
-trey
On Mon, Jan 5, 2009 at 4:42 PM, Trey Sheldon <glsheldo@gmail.com ([email]glsheldo@gmail.com[/email])> wrote:
Actually, may be on to something..... looks like the collector is grabbing the first "hrStorageVirtualMemory" entry, but on this machine this doesn't represent the swap space. .... now to find out what it actually represents.
thanks!
-trey
On Mon, Jan 5, 2009 at 4:30 PM, Trey Sheldon <glsheldo@gmail.com ([email]glsheldo@gmail.com[/email])> wrote:
Then that's interesting.....
a walk of 1.3.6.1.2.1.25.2.3.1 on the box in question returns:
HOST-RESOURCES-MIB::hrStorageIndex.10 = INTEGER: 10
HOST-RESOURCES-MIB::hrStorageType.10 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap space
HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 15631236
HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 2784
Resetting the detected swap size and remodeling the box enters 32830689280 in the os.totalSwap property.
Is there a chance that the HRFileSystemMap is adding values anywhere? The reason I ask is there's two partitions that are detected as "hrStorageVirtualMemory", but the partition sizes don't add up to the weird 32830689280 number. (I've append the full walk below for the curious people.
<begin paste>
HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1
HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3
HOST-RESOURCES-MIB::hrStorageIndex.6 = INTEGER: 6
HOST-RESOURCES-MIB::hrStorageIndex.7 = INTEGER: 7
HOST-RESOURCES-MIB::hrStorageIndex.8 = INTEGER: 8
HOST-RESOURCES-MIB::hrStorageIndex.10 = INTEGER: 10
HOST-RESOURCES-MIB::hrStorageIndex.31 = INTEGER: 31
HOST-RESOURCES-MIB::hrStorageIndex.32 = INTEGER: 32
HOST-RESOURCES-MIB::hrStorageIndex.33 = INTEGER: 33
HOST-RESOURCES-MIB::hrStorageIndex.34 = INTEGER: 34
HOST-RESOURCES-MIB::hrStorageType.1 = OID: HOST-RESOURCES-TYPES::hrStorageRam
HOST-RESOURCES-MIB::hrStorageType.3 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageType.6 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.7 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.8 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.10 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory
HOST-RESOURCES-MIB::hrStorageType.31 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.32 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.33 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageType.34 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: Physical memory
HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: Virtual memory
HOST-RESOURCES-MIB::hrStorageDescr.6 = STRING: Memory buffers
HOST-RESOURCES-MIB::hrStorageDescr.7 = STRING: Cached memory
HOST-RESOURCES-MIB::hrStorageDescr.8 = STRING: Shared memory
HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap space
HOST-RESOURCES-MIB::hrStorageDescr.31 = STRING: /
HOST-RESOURCES-MIB::hrStorageDescr.32 = STRING: /usr
HOST-RESOURCES-MIB::hrStorageDescr.33 = STRING: /var
HOST-RESOURCES-MIB::hrStorageDescr.34 = STRING: /mw
HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.6 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.7 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.8 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.31 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.32 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.33 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.34 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: 16429984
HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 32061220
HOST-RESOURCES-MIB::hrStorageSize.6 = INTEGER: 7620
HOST-RESOURCES-MIB::hrStorageSize.7 = INTEGER: 10217220
HOST-RESOURCES-MIB::hrStorageSize.8 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 15631236
HOST-RESOURCES-MIB::hrStorageSize.31 = INTEGER: 962573
HOST-RESOURCES-MIB::hrStorageSize.32 = INTEGER: 3366154
HOST-RESOURCES-MIB::hrStorageSize.33 = INTEGER: 3366154
HOST-RESOURCES-MIB::hrStorageSize.34 = INTEGER: 131613872
HOST-RESOURCES-MIB::hrStorageUsed.1 = INTEGER: 16169268
HOST-RESOURCES-MIB::hrStorageUsed.3 = INTEGER: 16169268
HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageUsed.31 = INTEGER: 72470
HOST-RESOURCES-MIB::hrStorageUsed.32 = INTEGER: 550869
HOST-RESOURCES-MIB::hrStorageUsed.33 = INTEGER: 129215
HOST-RESOURCES-MIB::hrStorageUsed.34 = INTEGER: 54250398
On Mon, Jan 5, 2009 at 3:35 PM, Chet Luther <cluther@zenoss.com ([email]cluther@zenoss.com[/email])> wrote:
On Jan 5, 2009, at 2:52 PM, Trey Sheldon wrote:
I'm curious about where these values are set as well. A couple of
my machines are reporting incorrect values on the hardware tab, but
when I query the UCD-SNMP-MIB::memTotalSwap.0 oid, it reports
correctly.
I'm looking through the collector plugins and have yet to find one
other than the UCDHardDiskMap that attempts to set the swap space.
Can one of the Zenoss dev's comment on where these values are probed
from?
This information is collected by the HRFileSystemMap modeler plugin.
If you snmpwalk to the .1.3.6.1.2.1.25.2.3.1 on a system with the Net-
SNMP agent on it you will see that it includes information about all
of the file systems along with physical memory and swap. The source
for this modeler plugin can be found at ZENHOME/Products/
DataCollector/plugins/zenoss/snmp/HRFileSystemMap.py.
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org ([email]zenoss-users@zenoss.org[/email])
http://lists.zenoss.org/mailman/listinfo/zenoss-users
I have reopened this discussion under a new thread (as this one seems to have huge code appends).
Cheers,
Jane
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||