Hi hackman, you got the information now in a PM
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?
is it the correct path in the templates? For Collect_SLA.py
It appears that the path is correct.
Travis
Sorry the path was wrong, I am going to fix it now and get back to you.
Travis
Working like a champ!!!!
Travis
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?
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?
|
Follow Us On Twitter »
|
Latest from the Zenoss Blog » |
|
Community | Products | Industries Customers | Services Partners | About Us | |
|
|
|
Copyright © 2005-2010 Zenoss, Inc.
|
||||||