[c-nsp] lack of snmp parity with cli

Nathan Ward cisco-nsp at daork.net
Thu Jan 7 07:24:18 EST 2016

Hi Mike,

Not the answer you’re looking for, but what sort of router? If it’s an ASR9k you can use the XML API to get better and faster data out of the router, without having to parse CLI output. It’s a very effective way to pull out this sort of data.

Also worth noting, Cisco Prime logs in to routers and runs a bunch of show commands rather than using SNMP. It needs all the data so it can model the routers on the server(s), and it can’t get what it needs from SNMP. I think if Cisco themselves aren’t using SNMP, we can presume that it’s limited.

They’re also not using the XML API either, but, trust me - it’s certainly better than using the CLI!

Nathan Ward

> On 8/01/2016, at 00:13, Mike <mike-cisconsplist at tiedyenetworks.com> wrote:
> Hello group,
> I have a tool I developed in house which polls a cisco router terminating PPPoE sessions in order to get a complete picture of each active pppoe session. Most of what I want is available via snmp such as user name, ip address, the user mac address, and such. However, PPPoE Intermediate Agent tags - CircuitID and RemoteID - are apparently not available anywhere in snmp. That information apparently only shows up using the cli command "show pppoe session all", and so my tool polls with snmp first, and then follows up with a text login to the router and parses the cli output, finally stitching it all together at the end. Its quite hairy.
> This seems silly that there would be something important like these tags that can only be seen from the cli and not from snmp. I've went thru cisco's snmp object navigator quite a bit and I came up empty. I've also spent lots of time doing some pretty deep walks of the snmp tree trying to just pick out the right info but again it just doesn't seem to be implemented. Im sort of resigned to the idea that, yeah, they just don't make that available via snmp. Id just like some confirmation from others that my situation here isn't actually unusual and parsing the output from the cli for certain info is an accepted practice?
> Mike-
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list