Thanks to efscommguy for posting a great new universal poller.
Hey, is there a way to assign the correct interface and map-class via this poller, I don't see any support on this UP, I know you can retrieve the interface and class-map info via snmp.
tks
HM
Have you tried creating your own UnDP to gather what you are specifically looking for?
I'm basically new to this UnDP stuff, however is there a dev guide or white paper available I could read over, I was actually sent this UnDP by a SW support tech, and he only knew how to install the poller.
I have some developer background, so if I could get some documentation I'm sure I could make it work.
Thanks for your response.
No worries, he is an online tutorial on many things, including UnDP. Do you think that UnDP will do what you want? If so, this thread would be useful on how to apply -
Let me know if this helps
Well I have the UnDP installed and it graphs the cbwfq oid's, however it doesn't label the interfaces that is uses, it uses what the snmpget returns 2347.3115, [CBQoS code]. so you would have to know that 2347 is ATM4/0.250, and 3115 is class EF.
Make Sense?
I have attached a jpeg showing how this UnDP labels in SolarWinds, as you will see, you would need a spreadsheet to keep up with what code is what interface and what code is what class.
SHM
I think this use case is going to be tough to accomplish because the relevant data is spread across multiple tables and require joins across those tables, which at this time the UnDP does not support.
How soon before it supports joining data across multiple tables? I have 3 critical use cases for this functionality that are quickly pushing me towards different tools.
I don't think these guys have the skill set to make this work, I would probably look for another tool to perform this...
The reason we didn't support this in the UnDP out of the gate is that it greatly increases the complexity of the tool. We expect to support the table-join scenario in the future, but it needs to be designed so that it doesn't make the UnDP too complicated for the much more common single-table case.