Skip navigation
1 ... 5 6 7 8 9 Previous Next 759850 Views 132 Replies Latest reply: Mar 16, 2011 4:23 PM by kchengva RSS Go to original post
  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    90. Jan 19, 2010 4:29 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Hi hackman, you got the information now in a PM

  • travisll Rank: White Belt 16 posts since
    May 29, 2008
    Currently Being Moderated
    91. Jan 26, 2010 6:32 PM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    So have either of you all figured out what the problem is?

    I just now was able to instlal ver 2 and configure it.

     

     

    My results

     

    python Collect_SLA.py -d ogerouter.comfedcu.org -c private -k 1 -t V
    OK| key=1 rttMonLatestRttOperCompletionTime=24 rttMonLatestRttOperSense=1 rttMonLatestRttOperApplSpecificSense=0 rttMonLatestRttOperTime=182759446 rttMonLatestJitterOperAvgJitter=2 rttMonLatestJitterOperIAJIn=0 rttMonLatestJitterOperIAJOut=0 rttMonLatestJitterOperICPIF=1 rttMonLatestJitterOperMOS=434

     

    No graphs at all.

     

    Nothing created in /usr/local/zenoss/zenoss/perf/Devices/ogerouter.comfedcu.org/ipSLAs

     

    Where can I look next?

  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    92. Jan 27, 2010 4:25 AM (in response to travisll)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    is it the correct path in the templates? For Collect_SLA.py

  • travisll Rank: White Belt 16 posts since
    May 29, 2008
    Currently Being Moderated
    93. Jan 27, 2010 7:50 AM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    It appears that the path is correct.

     

    Travis

  • travisll Rank: White Belt 16 posts since
    May 29, 2008
    Currently Being Moderated
    94. Jan 27, 2010 10:16 AM (in response to travisll)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Sorry the path was wrong, I am going to fix it now and get back to you.

     

    Travis

  • travisll Rank: White Belt 16 posts since
    May 29, 2008
    Currently Being Moderated
    95. Jan 27, 2010 12:49 PM (in response to travisll)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Working like a champ!!!!

     

    Travis

  • djpetro Rank: White Belt 9 posts since
    Apr 8, 2008
    Currently Being Moderated
    96. Feb 8, 2010 12:31 PM (in response to travisll)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Hello all,

     

    I've installed this zenpack, but it looks  like the routers aren't returning any rtt info:

     

    zenoss@zenoss:/opt/zenoss/zenoss/ZenPacks/ZenPacks.ipSLA.SLADevice-2.0-py2.4.egg/ZenPacks/ipSLA/SLADevice$  python ./Collect_SLA.py --device=RTR01 --community=snmp -k 1 -t V
    zenoss@zenoss:/opt/zenoss/zenoss/ZenPacks/ZenPacks.ipSLA.SLADevice-2.0-py2.4.egg/ZenPacks/ipSLA/SLADevice$

     

    Nothing  returned.  Also, when I model a device in /Network/IPSLA:

     

    2010-02-08  11:47:53    INFO      zen.ZenModeler    processing SLADevice for device  RTR01
    2010-02-08 11:47:53    INFO     zen.ZenModeler    SLA (entries) results:  ({}, {'MonOperEntry': {}})

     

    I've tried on several  different model routers, all Cisco.  I also confirmed through the Cisco  mib navigator that I have the correct mibs loaded, and the IOS images  support rtt.

     

    What am I missing on the router side?

  • djpetro Rank: White Belt 9 posts since
    Apr 8, 2008
    Currently Being Moderated
    97. Feb 8, 2010 2:48 PM (in response to djpetro)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    I don't think my router supports the OIDs the zenpack relys on:

     


    zenoss:~# snmpwalk -v 2c -c snmpc RTR01 1.3.6.1.4.1.9.9.42
    SNMPv2-SMI::enterprises.9.9.42.1.1.1.0 = STRING: "2.2.0 Round Trip Time MIB"
    SNMPv2-SMI::enterprises.9.9.42.1.1.2.0 = INTEGER: 16384
    SNMPv2-SMI::enterprises.9.9.42.1.1.3.0 = Timeticks: (0) 0:00:00.00
    SNMPv2-SMI::enterprises.9.9.42.1.1.4.0 = INTEGER: 10270
    SNMPv2-SMI::enterprises.9.9.42.1.1.5.0 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.6.0 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.1 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.2 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.5 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.6 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.7 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.8 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.9 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.11 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.12 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.13 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.2 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.3 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.24 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.25 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.26 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.27 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.29 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.30 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.32 = INTEGER: 1
    SNMPv2-SMI::enterprises.9.9.42.1.1.10.0 = INTEGER: 10270
    SNMPv2-SMI::enterprises.9.9.42.1.1.11.0 = INTEGER: 14314919
    SNMPv2-SMI::enterprises.9.9.42.1.1.12.0 = ""
    SNMPv2-SMI::enterprises.9.9.42.1.1.13.0 = INTEGER: 2
    zenoss:~#

     

    We're running the spservices code on the router, and I notice the screenshot in the zenpack page is running enterprise base.  Could this account for it?

  • dbenson Rank: White Belt 10 posts since
    Jul 1, 2010
    Currently Being Moderated
    98. Jul 1, 2010 5:19 PM (in response to Matt Ray)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    All,

     

    First off let me say thanks for sharing this excellent pack. It works like a charm and gives myself and I am sure many many others visibility into their network that they have always wanted and have never had (I would rather thank you guys then Cisco!).  With that I had a question about a feature that would be very helpful. 

     

    For FTP gets, if the Admin knows the size of the file being gotten, then with the RTT we could report throughput, something that could be very helpful to me.

     

    Has anyone done this?  Is it an easy additional graph point that a newbe like myself needs to know how to build? 

     

    Thanks again.

     

    //db

  • kchengva Rank: White Belt 66 posts since
    Aug 4, 2010
    Currently Being Moderated
    99. Oct 29, 2010 4:47 PM (in response to dbenson)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Does ZenPacks.ipSLA.SLADevice-2.0.1-py2.6.egg work on zenoss 3.0.2 ?

     

    It did pick up SLADevice plugin, and it created ipcheck_LOSS.rrd and ipcheck_RTA.rrd, but no ipSLAs directory under $ZENHOME/perf/Devices/{host}/

     

    I manually created one "isSLAs" directory and remodel the device, there is still no data.

     

    BTW, where do I look for "Service Level Agreement" tag on zenoss 3.0.2?

     

    Thanks.

  • zenorr Rank: White Belt 67 posts since
    May 6, 2010
    Currently Being Moderated
    100. Jan 28, 2011 7:12 AM (in response to Matt Ray)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Your ZenPack is excellent work. Maybe it needs some installation instructions, I will post them when done.

     

    Small typo :

     

    --- ipSLAsPerformance.pt.old    2011-01-28 11:46:09.289311098 +0100
    +++ ipSLAsPerformance.pt    2011-01-28 11:46:29.109311203 +0100
    @@ -101,7 +101,7 @@
             <td colspan="11" style="background-color:#555555"></td>
    </tr>
    <tr>
    -        <td colspan="1" align=right>Srting 5</td>
    +        <td colspan="1" align=right>String 5</td>
             <td colspan="1" align=right>Admin Mode</td>
             <td colspan="1" align=right>Vrf Name</td>
             <td colspan="1" align=right>Codec Type</td>

  • zenorr Rank: White Belt 67 posts since
    May 6, 2010
    Currently Being Moderated
    101. Jan 28, 2011 7:58 AM (in response to Matt Ray)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    We are using Zenoss 2.5.2 (stack) on Ubuntu 10.4 LTS.

     

    The "ip sla" entries we defined on the router are discovered finely, and I see them in the tab. However, no RRD files are created, so I get no graphs. I have done

     

    mkdir $ZENHOME/perf/Devices/[device name]/ipSLAs

     

    as user zenoss, restarted zenoss, remodeled the device, no way.

     

    Shall I create deeper directories under ipSLAs/ ? if yes, how should I name them ?

     

    Collect_SLA.py seems to work fine :

     

    zenoss@server:/opt/zenoss/zenoss/ZenPacks/ZenPacks.ipSLA.SLADevice-2.0.1-py2.4.egg/ZenPacks/ipSLA/SLADevice$ python ./Collect_SLA.py --device=slarouter --community=stuff -k 1 -t V
    OK| key=1 rttMonLatestRttOperCompletionTime=1 rttMonLatestRttOperSense=1 rttMonLatestRttOperApplSpecificSense=0 rttMonLatestRttOperTime=34731356 rttMonLatestJitterOperAvgJitter=0 rttMonLatestJitterOperIAJIn=0 rttMonLatestJitterOperIAJOut=0 rttMonLatestJitterOperICPIF=0 rttMonLatestJitterOperMOS=0

     

    Help wanted,

    Charles

  • zenorr Rank: White Belt 67 posts since
    May 6, 2010
    Currently Being Moderated
    102. Feb 1, 2011 10:28 AM (in response to zenorr)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    OK; the error appear to be in the data source definition :

     

    ${here/ZenPackManager/packs/ZenPacks.zenoss.ipSLA/path}/Collect_SLA.py -d ${here/manageIp} -c ${here/zSnmpCommunity} -k ${here/instance}

     

    If I replace all variables by fix values (script path included), it works nicely.

     

    By using fix values but a variable for -k ${here/instance} :

     

    Type: KeyError
    Value: 'instance'

    Traceback (innermost last):

    • Module ZPublisher.Publish, line 119, in publish
    • Module ZPublisher.mapply, line 88, in mapply
    • Module ZPublisher.Publish, line 42, in call_object
    • Module Products.ZenModel.BasicDataSource, line 184, in manage_testDataSource
    • Module Products.ZenModel.RRDDataSource, line 207, in getCommand
    • Module zope.tales.expressions, line 261, in __call__
    • Module zope.tales.expressions, line 217, in __call__
    • Module Products.PageTemplates.Expressions, line 131, in _eval
    • Module zope.tales.expressions, line 124, in _eval
    • Module Products.PageTemplates.Expressions, line 80, in boboAwareZopeTraverse
    • Module OFS.Traversable, line 301, in restrictedTraverse
    • Module OFS.Traversable, line 284, in unrestrictedTraverse
      __traceback_info__: ([], 'instance')

    KeyError: 'instance'

     

    Advice welcome...

    Charles

  • kchengva Rank: White Belt 66 posts since
    Aug 4, 2010
    Currently Being Moderated
    103. Feb 1, 2011 11:46 AM (in response to zenorr)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    yes, "instance" option is not working well.

    Since I have only one sla tag, I hard coded the command template ".... -k 10 -t V"

    sla RRD data have been collected, but I don't have graph report, it was working one time then failed.

  • zenorr Rank: White Belt 67 posts since
    May 6, 2010
    Currently Being Moderated
    104. Feb 2, 2011 4:58 AM (in response to kchengva)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    What do you mean by "instance" option is not working well ?

     

    By hardcoding the instance number, I get it to work (collect data, create the RRD files and create the graph. Of course, that hardcoding is wrong.

     

    I can't get this {here/instance} to work, and I have to. I will soon have a single SLA-measurement router that will poll up to 500 targets, so I will have up to 500 instances.

1 ... 5 6 7 8 9 Previous Next

More Like This

  • Retrieving data ...