Timeout while adding snmp interfaces

[Klosse]

Hello people!

Cacti is really a great piece of software. Everything works great except for something that has started to happen more and more often; when I add a host to 'SNMP Interfaces' that has many interfaces, for example an ATM router with 'many' subinterfaces (over 200), the operation times out. I can get maybe 70-80 interfaces mapped and then it stops with showing me the standard Internet Explorer "Page Cannot Be Displayed"-page.
Now, is this related to Internet Explorer or is it something else? Has anyone else experienced something similar? I'm running cacti 0.6.8a on a Linux machine..

Thanks..

Klosse Wistbacka
Multi.fi

[elias1884]

I have the same Problem. Since every virtual circuit is fetched as an index I never get the whole index in time, before php max execution time is reached. I think, there is another problem than execution time as well! I have set all php timeouts to 10 minutes and get the same result. To ilustrate what I am talking about: 1) SNMP - Interface Statistics (Verbose Query) Uptime Goes Backwards Success [78832 Items, 11901 Rows].

Well I would have trouble finding the interfaces I am interested in within these 11901 Rows anyway, but however, it would be nice, if it would work anyhow.

I guess there is a better approach to this though, what might that be? Can you give me a tip on how I can work around that problem?

[TheWitness]

Try increasing the timeout (aka MaxExecutionTime) in php.ini and rework. As far as 11k interfaces is concerned, I am baffled by anything that large. Ian refers to those things as "Corner Cases".

TheWitness

[elias1884]

The router is used as an adsl headend. I already have a timeout of 10 minutes and fetching the information with another snmp util does not take that long! php mem is set to 64mb, that should be sufficient too.

I have read several articles in this forum which report sort of the same problem 400 interfaces still seem to be enough to get this error.

Anyhow, actually I can hardly imagine anyone wanting stats for all those interfaces. Me for example, I only need the stats for the first 10 interfaces. So I suggest to implement some feature so I can specify that I only want to fetch the first 10 or whatever number of interfaces.

Another or additional feature would be to let me specify at the point of the interface query what exact interfaces I want to retrieve.

A combination of both would be best:
1. I try the normal approach,
2. I reduce the number of interfaces to fetch to e.g. 20
3. I find out that I also need the interface with 341, so I specify that one to be fetched additionally to the first 20.

Wouldn't that be cool?

[TheWitness]

Please place a feature request at http://bugs.cacti.net

TheWitness

[elias1884]

already filed as bug # 0000445:
SNMP query times out when to many interfaces on router

[TheWitness]

That should have been fixed in 0.8.6d. Are you running that version?

TheWitness

[nevet5m]

I thought I'd add my five cents worth ...

I have the same issue on a number of adsl head end routers. ATM will create up to 3 different ifTable interfaces for each virtual circuit. It's a bit of a pain because the ifTable immediately triples in size! When you're terminating lots of adsl customers on one router it's very common to see thousands of interfaces. This is not a 'corner case' for any large organisation running ATM.

I think that having the ability to get stats on these is valuable and not an unwanted feature - for example, you can monitor ip traffic for a particular adsl customer to aid troubleshooting etc. I am currently monitoring ATM sub-interfaces (AAL5 layer) for this very reason.

I can mostly manage to generate and view the entire list of interfaces using 0.8.6d, - it just takes forever to display the interface list. It would be very handy to retrieve for example 100 interfaces on a page or even have the option to enter an IfIndex manually (as suggested already in another post).

[TheWitness]

nevet5m,

I agree. This is currently an unavoidable Java Script issue. I don't like Java for that reason, but it's the development environment that provides us the type of support we need unfortunately. So, until we get that feature implemented, you will either have to turn down the number of JavaScript rows in Settings->Visual, or wait.

Sorry,

TheWintess