Topology job ran that long.
I removed these few switches from NAV.
This I can understand, but is it possible to run different jobs for some switches? I do like topo job generally, but I cannot run it for just a few of them.
By basic traffic monitoring - I mean to do inventory (to get a list of ports) and then traffic port statistics
Brgds
Mat -----Original Message----- From: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sent: Thursday, April 10, 2014 11:05 AM To: JABUREK Martin Cc: nav-users@uninett.no Subject: Re: Problem retrieving port statistics
On Tue, 8 Apr 2014 10:33:53 +0000 "martin.jaburek@cah.cz" martin.jaburek@cah.cz wrote:
So it did not help. Statistics just showed, that it ran for 11300 sec. It screwed all other switches.
What ran for 11300 seconds?
I removed them from nav now.
The settings or the switches?
Is it possible to do some lightweight monitoring (excluding LLDP and other extended functionality, just basic traffic monitoring) If it would help, then we can keep adding features (MAC, vlans, etc.)
ipdevpoll's jobs are fully configurable through ipdevpoll.conf. Each job consists basically of a series of collector plugins to run, and an interval for each job run per device.
Job names can be edited, or you can disable jobs entirely by commenting them out or changing the name of the job section to something that doesn't begin with `job_` (I personally like to prefix the name with an underscore to disable it).
The list of plugins run by each job can also be edited, but its best to understand what each plugin does before experimenting with it. Switch forwarding tables (cam), CDP and LLDP are all collected by the topo job, and each one has a separate plugin, so editing the plugin list here should be easy enough.
When it comes to the inventory job, it all depends on what you mean by "basic traffic monitoring".
-- Morten Brekkevold UNINETT