how can I import 200 devices to cacti?
Moderators: Developers, Moderators
how can I import 200 devices to cacti?
exist any script to make a automatic import of multiples cisco devices? to cacti?
i've just started working with cacti this week, and i need to monitor about 30 machines, growing to 90 in the next few months.p_a_l_o wrote:I need to solve similar problem.
I want to import around 2500 radio devices and 100 managed switches for monitoring traffic, latency and quality of signal.
Is it possible to do this easily?
seems like a freaking nightmare to point & click, dropdown, point & click over and over and over again...
i don't think cacti scales well in this regard. what i'd like to do is figure some way to hack the cacti db in mysql and be able to write a script to create all my devices, but that looks awful and i can find any docs on it.
at this point, i'm thinking about not using cacti, but instead just writing my own simple web front-end to graphs made with rrdtool.
Here is a hint :
http://forums.cacti.net/viewtopic.php?t=7683
It can add devices to Cacti from command line.
With some lines of perl, you could use a .csv file or something and call the script to add a lot of device (that's what I have done).
You will still need to add datasources and graphs for each device manually.
http://forums.cacti.net/viewtopic.php?t=7683
It can add devices to Cacti from command line.
With some lines of perl, you could use a .csv file or something and call the script to add a lot of device (that's what I have done).
You will still need to add datasources and graphs for each device manually.
I did pretty much what exo7 did, except I didn't use the command line option, i just wrote up a quick perl script to insert into the db. The script I had would also go as far as creating default graphs for all named interfaces in a cisco device. (Notice I said HAD, lost that in a new computer move...)
but, just getting the device in the system is the largest step as far as user input (and also the easiest to automate), so you may want to consider that route...
but, just getting the device in the system is the largest step as far as user input (and also the easiest to automate), so you may want to consider that route...
Who is online
Users browsing this forum: No registered users and 1 guest