Sep 2, 2009 11:59 PM
New IP-SLA Enumeration/Monitoring ZenPack
-
Like (0)
Just and FYI,
When you download this zenpack you must rename the egg from ZenPacks-1.ipSLA.SLADevice-1.2-py2.4.egg to ZenPacks.ipSLA.SLADevice-1.2-py2.4.egg.
If you do not it will not install correctly.
Travis Llewellyn
Travis:
Good catch, thanks. Please report any other bugs or suggestions and I'll incorperate them into the upcomming version 2.
OK so after playing with this for awhile, I can not figure out the steps to get it working.
I have one router I am testing with.
I have tried moving it from /devices/network/router/cisco to /devices/network/ipsla.
Then I tried to remodel it and the extra tab does not show up.
Can you describe the process to go through to get this to work?
Travis
First install the zenpack and restart zenoss.
Next, you have to add the device you want to monitor. If its already added, you must remove it. When adding the device be sure to supply the snmp community of the device and to set its class as /devices/network/ipsla. This sets the python class of the device and must be set whent eh device is first added. Once the device has been added, navigate to it. There should be a "Service Level Agreement" tab with the other usual tabs. Next go to the devices collector plugins and add SLADevice. Finally remodel the device to populate the tables. Let me know if you run into any problems.
Thanks Travis,
Travis:
Open each of the templates, each command, and change all referances to $ZENHOME to your zenoss directory. E.x. /opt/zenoss/
Some OS work using $ZENHOME some don't. I'm unsure why.
Keep me posted!
Thanks,
Worked perfectly....
Now to creat some more SLA's .
Thanks
So what do we have to look forward to in version 2?
Travis
Version 2 will have:
->Known bug fixes
->SLA edit ability (to use web gui to modify/create SLA and write to device using smnp)
->Better templates
->No more perl, only python componets
If you have a want/need or suggestion, let me know and I'll add it.
Thanks Travis,
Great it is starting to look really good.
Thanks for all the work you have put into this.
Travis
is is possible to use this under /network/switches and /network/routers?
Sort of have it for all network units and there will be info only if there is availible?
Nick:
Such a task would cause the entire /devices/network structure to use the ipSLA python class. This would cause extra modeling. If you'd like to do this, and the extra modeling isn't a problem, let me know and I'll write instructions.
The code is in there to convert the device to its new class... and it worked after I wrote it. Definitely will need a restart so that the tabs show up correctly.
-EAD
Thanks for your fast response hackman.
It would be great, thank you
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||