quote:Originally posted by dclecompteWe think we have a solution. We are currently testing that solution. We want to be sure that it will actually fix the problem and will not break anything else.As soon as we're confident, we plan to release a patch. I won't promise a date because if this fix is not a real fix, we'll have to go back to the drawing board.No rush, I was just wondering what the status is. I am glad that you may have a fix, and will patiently await the patch. Glad to know that you guys at least see the same thing MarkS.Denny LeCompteSr. Product Manager, OrionSolarWinds
quote:Originally posted by BryanBeckerNot sure if this is related or not but I'm seeing alot of graph gapping with my custom mib polling. I see the custom mibs doing this but the other items it's polling looks fine.Is this related?BB
I worked with a SolarWinds engineer on a similar problem, I wanted to get the ifDescr (1.3.6.1.2.1.2.2.1.2) field information to compile a Cisco CDP neighbor table. I could create the custom poller and retrieve the ifDescr feilds when setting up the poller by clicking the test button. When I applied the poller to devices it would never return any interface data. The verdict was that since I was not monitoring any interfaces on the device NPM was filtering all of my results. If I monitored interfaces on the device then the interface information would show up for the interfaces NPM was monitoring. I was told this was implimented to stop people from circumventing the licencing by monitoring devices based on the ifDescr table.
I suggested that they build a resource that would allow the web pages to display cdp neighbor information that did not hit this limitation. All we can do is hope.
Edited: found the answer to the question I had posted.