Missing graph/datasource for a lag interface that should be graphed?

[jtzako]

Every now and then I find a device which has the wrong lag interface 'traffic' graph. My suspicion is that the device may have had that 'wrong' lag # when it was first turned up, but it was then changed to the correct one.

Cacti will show a traffic graph for that wrong lag # but with no data. However, it does not show a graph for the correct lag # at all.

I have tried going to Management->Device and changing the re-index method to "Index Count" rather than "Uptime" as well as saving that, and clicking the re-index device button.

I also tried setting the max OIDs to 1 and reindexing again, but still I cannot get it to create a traffic graph for lag 165. It seems to know that lag exists, and I'm not getting any timeouts, so I am unsure what is going on here.

Any idea how I get this to sync up?

[TheWitness]

Have you reviewed the verbose query output? What is the index based upon? We like the index to be reliable (not change if possible).