Skip navigation
1 ... 3 4 5 6 7 ... 9 Previous Next 759834 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
    60. Dec 8, 2009 8:43 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Hi hackman

     

    Been looking to change the timeout value, cant find it in 2.0

     

    Could you lend me a hand on where it is?

     

    its working good when there aint long responsetimes so far.

     

    Good work

  • Shane Scott ZenossMaster 1,373 posts since
    Jul 6, 2009
    Currently Being Moderated
    61. Dec 8, 2009 8:53 AM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Nickname:

     

    I didnt implement a timeout parameter in to the collection python script. Have you tried increasing the zencommand timeout? If that doesnt help, I'll implement a timeout flag.

  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    62. Dec 8, 2009 9:19 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Got it on 120, and they still timeout :/

     

    /

    Nickname

  • Shane Scott ZenossMaster 1,373 posts since
    Jul 6, 2009
    Currently Being Moderated
    63. Dec 8, 2009 9:23 AM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Nickname:

     

    Damn, I was hoping that would fix it! :-D I'll investigate and implement a timeout flag to address this problem. Thanks for the report.

  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    64. Dec 8, 2009 9:25 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Any time hackman.

     

    The ping SLA's are working fine, it's the http that timeout.

     

    /

    Nickname

  • Shane Scott ZenossMaster 1,373 posts since
    Jul 6, 2009
    Currently Being Moderated
    65. Dec 8, 2009 9:28 AM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Nickname:

     

    Only the HTTPs? Does it always timeout or just sometimes? Is there a pattern or just random?

     

    Thanks again!

  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    66. Dec 8, 2009 9:31 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Just installed the 2.0.

     

    But so far, it seems when the responsetimes go up, it fails.

     

    Local in Sweden it works fine, but between Stockholm, Sweden and Toronto, Canada it fails, current rtt is 250ms

     

    /

    Nickname

  • Shane Scott ZenossMaster 1,373 posts since
    Jul 6, 2009
    Currently Being Moderated
    67. Dec 8, 2009 9:45 AM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Nickname:

     

    Interesting. I'll check into it. I only have local HTTP tests, so I never had any long response times.

  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    68. Dec 9, 2009 4:17 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Hi hackman

     

    Now it seems non of the http or jitter tests works, just ping.

     

    Just to make sure, its just one collector file in 2.0? in my case /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.ipSLA.SLADevice-2.0-py2.4.egg/ZenPacks/ipSLA/SLADevice/Collect_SLA.py

     

    And it should be for all templates? So I didn’t screw that up

     

    Get a error report form when I test the different sla templates against a SLA unit.

  • Shane Scott ZenossMaster 1,373 posts since
    Jul 6, 2009
    Currently Being Moderated
    69. Dec 10, 2009 7:59 AM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Nickname:

     

    Sorry I didnt reply yesterday, blizzard here in the N.E. US yesterday.

     

    When you get a chance, check the following:

     

    VoIP template should look like {path to Collect_SLA.py}/Collect_SLA.py -d ${here/manageIp} -c ${here/zSnmpCommunity} -k ${here/instance} -t V

    HTTP template should look like {path to Collect_SLA.py}/Collect_SLA.py -d ${here/manageIp} -c ${here/zSnmpCommunity} -k ${here/instance} -t W

    Regular RTT template should look like {path to Collect_SLA.py}/Collect_SLA.py -d ${here/manageIp} -c ${here/zSnmpCommunity} -k ${here/instance}

     

    The -t {opt} at the end has the script collect more of a specific type.

     

    Let me know if that was the problem.

  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    70. Dec 11, 2009 4:01 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Hi hackman

     

    That didn't solve the problem, I had the same lines.

     

    Might it be that it doesn’t create the SLA folders under perf/Devices//iPSLAs/ ?

     

    It create the ones for PING but there is no folders for the other 2 tests.

     

    /

    Nickname

  • Shane Scott ZenossMaster 1,373 posts since
    Jul 6, 2009
    Currently Being Moderated
    71. Dec 11, 2009 10:59 AM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Nickname:

     

    Thats possible. I've seen cases where the directories are created automatically and others where they arent. I really dont know why, I which I could figure a way to fix that. Try creating those dir's using the zenoss user and let me know what happens.

     

    Also, if possible, post the results of the following commands:

     

     

    su zenoss
    locate Collect_SLA.py
    cd {result location of Collect_SLA.py}
    python Collect_SLA.py -d {your 2800 IP} -c {your community string}
    python Collect_SLA.py -d {your 2800 IP} -c {your community string} -t W
    python Collect_SLA.py -d {your 2800 IP} -c {your community string} -t V
    

     

    Thanks Nickname

  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    72. Dec 14, 2009 5:33 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    This is what I get from the commands you gave me. Directories for PING and the iPSLAs directories creates as it should, not the other tests. I created a testfolder for jitter and it didn’t create any RRD files.

     

     

    python Collect_SLA.py -d site-s01.company.com -c companyro

    OK| key= 1 RttOperCompletionTime= 226 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337033434

    OK| key= 3 RttOperCompletionTime= 218 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337034696

    OK| key= 2 RttOperCompletionTime= 228 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337034129

    OK| key= 5 RttOperCompletionTime= 2012 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337035887

    OK| key= 4 RttOperCompletionTime= 218 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337035291

    OK| key= 7 RttOperCompletionTime= 50 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337037298

    OK| key= 6 RttOperCompletionTime= 57 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337036632

    OK| key= 8 RttOperCompletionTime= 338 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337037975

     

    python Collect_SLA.py -d site-s01.company.com -c companyro -t W

    OK| key= 1 RttOperCompletionTime= 226 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337033434

    OK| key= 3 RttOperCompletionTime= 218 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337034696

    OK| key= 2 RttOperCompletionTime= 228 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337034129

    OK| key= 5 RttOperCompletionTime= 2012 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337035887

    OK| key= 4 RttOperCompletionTime= 218 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337035291

    OK| key= 7 RttOperCompletionTime= 50 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337037298

    OK| key= 6 RttOperCompletionTime= 57 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337036632

    OK| key= 8 RttOperCompletionTime= 338 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337037975

     

    python Collect_SLA.py -d site-s01.company.com -c companyro -t V

    OK| key= 1 RttOperCompletionTime= 226 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337033434

    OK| key= 3 RttOperCompletionTime= 218 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337034696

    OK| key= 2 RttOperCompletionTime= 228 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337034129

    OK| key= 5 RttOperCompletionTime= 2012 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337035887

    OK| key= 4 RttOperCompletionTime= 218 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337035291

    OK| key= 7 RttOperCompletionTime= 50 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337037298

    OK| key= 6 RttOperCompletionTime= 57 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337036632

    OK| key= 8 RttOperCompletionTime= 338 RttOperSense= 1 ApplSpecificSense= 0 RttOperTime= 337037975

  • Shane Scott ZenossMaster 1,373 posts since
    Jul 6, 2009
    Currently Being Moderated
    73. Dec 14, 2009 8:00 AM (in response to nickname)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Nickname:

     

    Looks like the output of -t W and -t V are bad.

     

    -t V output:

    OK| key=5061 rttMonLatestRttOperCompletionTime=4 rttMonLatestRttOperSense=1 rttMonLatestRttOperApplSpecificSense=0 rttMonLatestRttOperTime=618627498 rttMonLatestJitterOperAvgJitter=1 rttMonLatestJitterOperIAJIn=0 rttMonLatestJitterOperIAJOut=0 rttMonLatestJitterOperICPIF=1 rttMonLatestJitterOperMOS=434

     

    -t W output:

    OK| key=1 rttMonLatestRttOperCompletionTime=12 rttMonLatestRttOperSense=1 rttMonLatestRttOperApplSpecificSense=0 rttMonLatestRttOperTime=618651496 rttMonLatestHTTPOperRTT=12 rttMonLatestHTTPOperDNSRTT=0 rttMonLatestHTTPOperTCPConnectRTT=3 rttMonLatestHTTPOperTransactionRTT=9 rttMonLatestHTTPErrorSenseDescription=1

     

    With no -k (SLA index key) specificed, its just does a bulk RTT. I accidently missed the -k ${here/instance} in the two templates command datasources- not sure how. Here is how to fix it.

     

     

    For VoIP: python [path to Collect_SLA]/Collect_SLA.py -d ${here/manageIp} -c ${here/zSnmpCommunity} -k ${here/instance} -t V

     

    For Web: python [path to Collect_SLA]/Collect_SLA.py -d ${here/manageIp} -c ${here/zSnmpCommunity} -k ${here/instance} -t W

     

    For regular RTT: python [path to Collect_SLA]/Collect_SLA.py -d ${here/manageIp} -c ${here/zSnmpCommunity} -k ${here/instance}

     

    Hope this fixes it! I'll fix this now!

  • nickname Rank: White Belt 67 posts since
    Sep 28, 2009
    Currently Being Moderated
    74. Dec 14, 2009 8:34 AM (in response to Shane Scott)
    Re: New IP-SLA Enumeration/Monitoring ZenPack

    Hi hackman, thanks again for your fast reponses.

     

    It solved http but voip still dosesnt work.

     

    python /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.ipSLA.SLADevice-2.0-py2.4.egg/ZenPacks/ipSLA/SLADevice/Collect_SLA.py -d ${here/manageIp} -c ${here/zSnmpCommunity} -k ${here/instance} -t V

     

    Did I made a misstake with the above one?

1 ... 3 4 5 6 7 ... 9 Previous Next

More Like This

  • Retrieving data ...