I have to confess that I haven't poked around the AIX MIB tree that much.  I 
was going to use Zenoss as an excuse to rectify that situation. :)

    I don't know about VACM_VIEW, but taking a look at our cacti configuration 
here it looks like you're on the right track -- at least as far as some of the 
OIDs you're using.   As I said, I don't have anything to test with at the 
moment, so I'm a little handicapped.   I'll share some of the info that a 
colleague of mine used in our cacti configuration, and hopefully that will be 
enough to be a great start for that AIX Zenpack that you're creating.... :)

   BTW, let me know if you need anything else.


kells

    Here's the cacti XML for filesystem info:

<interface>
        <name>Get AIX File Systems</name>
        <description>Queries an AIX host for a list of monitorable File 
Systems</description>
        <oid_index>.1.3.6.1.4.1.2.6.191.6.2.1.1</oid_index>
        <index_order>aixFsIndex:aixFsName:aixFsMountPoint</index_order>
        <index_order_type>numeric</index_order_type>
        <index_title_format>|chosen_order_field|</index_title_format>

        <fields>
                <aixFsIndex>
                        <name>Index</name>
                        <method>walk</method>
                        <source>value</source>
                        <direction>input</direction>
                        <oid>.1.3.6.1.4.1.2.6.191.6.2.1.1</oid>
                </aixFsIndex>
                <aixFsName>
                        <name>Name</name>
                        <method>walk</method>
                        <source>value</source>
                        <direction>input</direction>
                        <oid>.1.3.6.1.4.1.2.6.191.6.2.1.2</oid>
                </aixFsName>
                <aixFsMountPoint>
                        <name>Mount Point</name>
                        <method>walk</method>
                        <source>value</source>
                        <direction>input</direction>
                        <oid>.1.3.6.1.4.1.2.6.191.6.2.1.3</oid>
                </aixFsMountPoint>
                <aixFsSize>
                        <name>Size (Megabytes)</name>
                        <method>walk</method>
                        <source>value</source>
                        <direction>output</direction>
                        <oid>.1.3.6.1.4.1.2.6.191.6.2.1.5</oid>
                </aixFsSize>
                <aixFsFree>
                        <name>Free (Megabytes)</name>
                        <method>walk</method>
                        <source>value</source>
                        <direction>output</direction>
                        <oid>.1.3.6.1.4.1.2.6.191.6.2.1.6</oid>
                </aixFsFree>
                <aixFsNumINodes>
                        <name>Total Inodes</name>
                        <method>walk</method>
                        <source>value</source>
                        <direction>output</direction>
                        <oid>.1.3.6.1.4.1.2.6.191.6.2.1.7</oid>
                </aixFsNumINodes>
                <aixFsUsedINodes>
                        <name>Used Inodes</name>
                        <method>walk</method>
                        <source>value</source>
                        <direction>output</direction>
                        <oid>.1.3.6.1.4.1.2.6.191.6.2.1.8</oid>
                </aixFsUsedINodes>
        </fields>
</interface>


   And here's the XML for paging space:

<interface>
<name>xmdPagSpEntry</name>
<description>Paging space statistics</description>
<oid_index>.1.3.6.1.4.1.2.3.1.2.2.2.1.3.1.1</oid_index>

<fields>
<xmdPagSpIocnt>
<name>Pending IOs for this paging space</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.2.3.1.2.2.2.1.3.1.5</oid>
</xmdPagSpIocnt>
<xmdPagSpEfree>
<name>Free portion of this paging space (percent)</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.2.3.1.2.2.2.1.3.1.4</oid>
</xmdPagSpEfree>
<xmdPagSpSize>
<name>Size of paging space (4K pages)</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.2.3.1.2.2.2.1.3.1.3</oid>
</xmdPagSpSize>
<xmdPagSpInstName>
<name>Instance Name</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.2.3.1.2.2.2.1.3.1.2</oid>
</xmdPagSpInstName>
<xmdPagSpIndex>
<name>Index Number</name>
<method>walk</method>
<source>value</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.2.3.1.2.2.2.1.3.1.1</oid>
</xmdPagSpIndex>
</fields>
</interface>

   And CPU

kernel: .1.3.6.1.4.1.2.3.1.2.2.2.1.1.102.0
user: .1.3.6.1.4.1.2.3.1.2.2.2.1.1.101.0
wait: .1.3.6.1.4.1.2.3.1.2.2.2.1.1.103.0
idle: .1.3.6.1.4.1.2.3.1.2.2.2.1.1.104.0

# of CPUs: .1.3.6.1.4.1.2.3.1.2.2.2.1.1.125.0





akblackwel wrote:
> kpg123, Thanks, you got me pointed in the right direction. Question, you know 
> what setting is used in the VACM_VIEW to expose cpu, drives, tcp? This is my 
> VACM_VIEW. It's returning system and enterprise, but not anything else. Any 
> ideas?
> 
> Kevin
> 
> VACM_VIEW defaultView 1.3.6.1.4.1.2.6.191 - included -
> VACM_VIEW defaultView system - included -
> VACM_VIEW defaultView interfaces - included -
> VACM_VIEW defaultView tcp - included -
> VACM_VIEW defaultView icmp - included -
> VACM_VIEW defaultView internet - included -
> VACM_VIEW defaultView enterprises - included -





-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9372#9372

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to