Skip navigation
14887 Views 7 Replies Latest reply: Jul 18, 2012 10:41 AM by jnalley RSS
Matt Ray Rank: Zen Master 2,484 posts since
Apr 5, 2008
Currently Being Moderated

Jul 17, 2009 1:20 PM

New Community NetApp ZenPack

Thanks to Zenoss Community member David Nicklay for the new Community
NetApp ZenPack. This ZenPack rolls up the previous 3 NetApp ZenPacks:
• Sys-Netapp
• NetApp Volume
• NetApp NFSv3 Statistics

The Zenpack monitors Netapp devices under /Storage/NetApp and collects
volume-related information, including NFSv3 statistics and adds
additional functionality to the previous 3 ZenPacks.

NetApp: http://www.zenoss.com/community/projects/zenpacks/netapp
Community ZenPack Repository: http://community.zenoss.org/trac-zenpacks/wiki/ZenPackscommunityNetApp

Thanks David!

Thanks,Matt Ray
Zenoss Community Manager
community.zenoss.com
mray@zenoss.com





_______________________________________________
zenoss-zenpacks mailing list
zenoss-zenpacks@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-zenpacks
  • gwb235 Newbie 5 posts since
    Nov 13, 2009
    Currently Being Moderated
    1. Jul 5, 2010 4:46 PM (in response to Matt Ray)
    Re: New Community NetApp ZenPack

    I think it's a known problem when looking at an interface, i.e.

     

    /Devices /Storage /NetApp /rosen /os /e0a

     

    the "Throughput" graph is incorrect.  I believe this is due to the template being used for the interfac (ethernetCsmacd) which uses these OIDs:

     

    ifInErrors1.3.6.1.2.1.2.2.1.14SNMPTrue
    ifInOctets1.3.6.1.2.1.2.2.1.10SNMPTrue
    ifInUcastPackets1.3.6.1.2.1.2.2.1.11SNMPTrue
    ifOperStatus.1.3.6.1.2.1.2.2.1.8SNMPTrue
    ifOutErrors1.3.6.1.2.1.2.2.1.20SNMPTrue
    ifOutOctets1.3.6.1.2.1.2.2.1.16SNMPTrue
    ifOutUcastPackets1.3.6.1.2.1.2.2.1.17SNMPTrue

     

    Based on what I read from the NetApp MIB, these are the correct OIDs to poll for throughput:

     

    The netapp specific OIDs are

    .1.3.6.1.4.1.789.1.22.1.2.1.25
    The total number of octets received on the interface, including framing  characters.
    This object returns all of the 64 bit unsigned integer.

    .1.3.6.1.4.1.789.1.22.1.2.1.31
    The total number of octets transmitted out of the interface, including  framing characters.
    This object returns all of the 64 bit unsigned integer.

    .1.3.6.1.4.1.789.1.22.1.2.1.26
    The number of subnetwork-unicast packets delivered to a higher-layer  protocol.
    This object returns all of the 64 bit unsigned integer.

    .1.3.6.1.4.1.789.1.22.1.2.1.32
    The total number of packets that higher-level protocols requested be  transmitted to a subnetwork-unicast address, including those that were  discarded or not sent. This object returns all of the 64 bit unsigned   integer.

    .1.3.6.1.4.1.789.1.22.1.2.1.29
    The number of inbound packets that contained errors preventing them from  being deliverable to a higher-layer protocol. This object returns all  of the 64 bit unsigned integer.

    .1.3.6.1.4.1.789.1.22.1.2.1.35
    The number of outbound packets that could not be transmitted because of  errors. This object returns all of the 64 bit unsigned integer.

    note these are different than the 64bit counters used by  ethernetCsmacd_64.

     

    I've worked around this by copying the ethernetCsmacd to the local hierarchy, but might be worthwhile to roll into zenpack.

  • Jo Rhett Rank: White Belt 42 posts since
    Feb 13, 2012
    Currently Being Moderated
    2. Apr 10, 2012 7:44 PM (in response to Matt Ray)
    Re: New Community NetApp ZenPack

    Matt, it doesn't seem like anyone is fixing the issues with this. What is the process for getting the patches integrated if I take on the work of fixing it?

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010
    Currently Being Moderated
    3. Apr 10, 2012 7:47 PM (in response to Jo Rhett)
    Re: New Community NetApp ZenPack

    Not sure if Matt will still be engaged on this thread as he is no longer with Zenoss Inc. The process for getting patches integrated would be to fork https://github.com/zenoss/ZenPacks.community.NetApp, apply your updates, and then issue a pull request to Zenoss to have them merge your pull request.

  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    4. Jul 17, 2012 4:59 PM (in response to dpetzel)
    Re: New Community NetApp ZenPack

    Sorry to resurrect an old thread but here's a full list of the 64bit network OIDs for NetApp, in case anyone else is looking for them...

     

    if64InOctets          1.3.6.1.4.1.789.1.22.1.2.1.25

    if64InUcastPkts          1.3.6.1.4.1.789.1.22.1.2.1.26

    if64InNUcastPkts     1.3.6.1.4.1.789.1.22.1.2.1.27

    if64InDiscards          1.3.6.1.4.1.789.1.22.1.2.1.28

    if64InErrors          1.3.6.1.4.1.789.1.22.1.2.1.29

    if64InUnknownProtos     1.3.6.1.4.1.789.1.22.1.2.1.30

    if64OutOctets          1.3.6.1.4.1.789.1.22.1.2.1.31

    if64OutUcastPkts     1.3.6.1.4.1.789.1.22.1.2.1.32

    if64OutNUcastPkts     1.3.6.1.4.1.789.1.22.1.2.1.33

    if64OutDiscards          1.3.6.1.4.1.789.1.22.1.2.1.34

    if64OutErrors          1.3.6.1.4.1.789.1.22.1.2.1.35

     

    We'll have to make sure that they make their way in to the community NetApp ZenPack at some point and that we create a new interface modeler plugin for it which collects the speed from a better OID if there is one.  The ifSpeed values aren't generally correct.

  • jnalley Newbie 5 posts since
    Apr 4, 2012
    Currently Being Moderated
    5. Jul 17, 2012 11:27 PM (in response to Ryan Matte)
    Re: New Community NetApp ZenPack

    when I query the if64InOctets, for instance, I get several seemingly undocumented child OIDs that I can't seem to find documented anywhere, including in the bowels of the customer support site within NetApp. In example:

     

    SNMPv2-SMI::enterprises.789.1.22.1.2.1.25.1 = Counter64: 0

    SNMPv2-SMI::enterprises.789.1.22.1.2.1.25.2 = Counter64: 0

    SNMPv2-SMI::enterprises.789.1.22.1.2.1.25.3 = Counter64: 15851864159121

    SNMPv2-SMI::enterprises.789.1.22.1.2.1.25.4 = Counter64: 840

    SNMPv2-SMI::enterprises.789.1.22.1.2.1.25.5 = Counter64: 235384063

    SNMPv2-SMI::enterprises.789.1.22.1.2.1.25.6 = Counter64: 6693276

    SNMPv2-SMI::enterprises.789.1.22.1.2.1.25.7 = Counter64: 0

    SNMPv2-SMI::enterprises.789.1.22.1.2.1.25.8 = Counter64: 0

     

    .5 and .6 seem like good candidates for the actual realtime metric you'd typically be looking for. Anyone have any thoughts or ideas?

  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    6. Jul 18, 2012 10:35 AM (in response to jnalley)
    Re: New Community NetApp ZenPack

    Those should correspond with the index ids for each interface.  For example, if you snmpwalk ifName or ifAlias or ifDescr you'll see what I mean.  Each of those values is a value for a separate interface, they aren't different data types.

  • jnalley Newbie 5 posts since
    Apr 4, 2012
    Currently Being Moderated
    7. Jul 18, 2012 10:41 AM (in response to Ryan Matte)
    Re: New Community NetApp ZenPack

    Yeah i realized that about 10 minutes before you responded. I'm a moron. Sorry.

More Like This

  • Retrieving data ...