Managers need to use the zfsPoolStatusIndex to correlate the names in the
two tables - e.g.,
snmptable -Ci zfsVFSIOPSTable
will get you 3 columns:
index zfsOperReads zfsOperWrites
and then if you snmpwalk zfsPoolName, you can get the pool name that
corresponds to the index.
Bill
On Fri, Aug 8, 2014 at 7:04 AM, Turbo Fredriksson <tu...@bayour.com> wrote:
> I'd like to bump this question - how exactly should one use AUGMENT?
>
> On Jul 23, 2014, at 1:42 AM, Turbo Fredriksson wrote:
>
> > On Jul 23, 2014, at 1:24 AM, Turbo Fredriksson wrote:
> >
> >> Yes, they are related.
> >
> > Hmm, even making 'zfsVFSIOPSEntry' augment 'zfsPoolStatusEntry' still
> > won't allow me to use 'zfsPoolName' in the sequence:
> >
> > zfsVFSIOPSTable OBJECT-TYPE
> > SYNTAX SEQUENCE OF ZFSVFSIOPSEntry
> > MAX-ACCESS not-accessible
> > STATUS current
> > DESCRIPTION "A list of ZFS VFS IOPS status
> information.
> > This table contains additional
> objects for
> > the zfsPoolStatusTable."
> > ::= { zfsStats 8 }
> >
> > zfsVFSIOPSEntry OBJECT-TYPE
> > SYNTAX ZFSVFSIOPSEntry
> > MAX-ACCESS not-accessible
> > STATUS current
> > DESCRIPTION "An entry containing ZFS ARC
> status values."
> > AUGMENTS { zfsPoolStatusEntry }
> > ::= { zfsVFSIOPSTable 1 }
> >
> > ZFSVFSIOPSEntry ::= SEQUENCE {
> > zfsVFSIOPSIndex CounterIndex,
> >
> > zfsPoolName DisplayString,
> > zfsOperReads Counter32,
> > zfsOperWrites Counter32
> > }
> >
> >
> > BAYOUR-COM-MIB.txt:2215: SEQUENCE element #2 `zfsPoolName' is not a
> child node under `zfsVFSIOPSEntry'
> > BAYOUR-COM-MIB.txt:2215: warning: SEQUENCE element #3 `zfsOperReads'
> does not match order of columnar objects under `zfsVFSIOPSEntry'
> >
> >
> > Did I misunderstand something?
> >
> >
> > Removing the 'zfsPoolName' line, just gives me a broken table:
> >
> > $ snmptable localhost zfsVFSIOPSTable
> > SNMP table: BAYOUR-COM-MIB::zfsVFSIOPSTable
> >
> > zfsOperReads zfsOperWrites
> > 0 0
> > 0 0
> > 0 0
> > 0 0
> > 4 ?
> > "test1" ?
> > "test2" ?
> > "test3" ?
> >
> > I want the pool name 'testX' as the first column, zfsOper* as two and
> three...
> >
> >
> > Should I just NOT output the pool name in the script? Will 'everyone'
> understand
> > that the first line is related to the first line of the output of the
> > 'zfsPoolStatusTable'?
> >
> >
> > $ snmptable localhost zfsPoolStatusTable
> > SNMP table: BAYOUR-COM-MIB::zfsPoolStatusTable
> >
> > zfsPoolName zfsPoolSize zfsPoolAlloc zfsPoolFree zfsPoolCap
> zfsPoolDedup zfsPoolHealth zfsPoolAltRoot zfsPoolUsedBySnaps zfsPoolUsed
> > test1 429496729 967680 429496729 0
> 1.00 online - 0 1532928
> > test2 429496729 137363456 214748364 0
> 1.00 online - 22528 137977856
> > test3 429496729 968704 429496729 0
> 1.00 online - 0 1536000
> > test4 68681728 151552 68576870 0
> 1.00 degraded - 0 119808
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Net-snmp-users mailing list
> Net-snmp-users@lists.sourceforge.net
> Please see the following page to unsubscribe or change other options:
> https://lists.sourceforge.net/lists/listinfo/net-snmp-users
>
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
