lextudio / sharpsnmplib

Sharp SNMP Library- Open Source SNMP for .NET
https://sharpsnmp.com
MIT License
356 stars 152 forks source link

CISCO-EIGRP-MIB cEigrpTopoTable will not walk #598

Closed lextudio-support closed 2 hours ago

lextudio-support commented 2 hours ago

I am having a problem walking a table from a custom mib. I am currenlty not sure what is causing it since I have not been able to do a line capture yet of what is happening when walking this table. Has anyone had any experiance with this MIB and know if this table is supported with #SNMP library? I am trying to get the cEigrpActive status of a Cisco switch.

Loading the CISCO-EIGRP-MIB and all of its dependencies I was unable to walk the cEigrpTopologyInfo tree using the MIB Browser. Does anyone have any ideas what is invalidating the walk of this OID (1.3.6.1.4.1.9.9.449.1.3.1)

This is a great library. Much easier to use than the .net-snmp library.

Thanks,

Original Reported Date: 2010-05-21T13:25:28.84-07:00 Original CodePlex Discussion Thread ID: 213466

lextudio-support commented 2 hours ago

Copied from CodePlex without authors:

Hi,

As I don't have access to such devices, I cannot provide much assistance unless you can share some data, like I advise here under "How to diagnose problems? "

http://sharpsnmplib.codeplex.com/wikipage?title=FAQ&referringTitle=Home

Regards,

Lex

Original Posted Date: 2010-05-21T16:38:07.35-07:00

lextudio-support commented 2 hours ago

Copied from CodePlex without authors:

Lex,

Thanks for the quick reply. I should have a wireshark trace done sometime Monday. I was mostly just trying to see if anyone has seen a similar case where some nodes in a table do not respond to a walk while others do. In my specific case the table for 1.3.6.1.4.1.9.9.449.1 returns a response for walk on nodes 1.3.6.1.4.1.9.9.449.1.1 , 1.3.6.1.4.1.9.9.449.1.2 , and 1.3.6.1.4.1.9.9.449.1.5. and nothing for nodes 3 and 4.

BTW: the MIB Browser.exe is a great tool for looking at OIDs and playing around with MIBs.

I should also have some more comparisons with other snmp libraries to see if my problem persists outside of the #SNMP library.

Again I want to thank everyone for the hard work creating this sweet library!

Thanks

Original Posted Date: 2010-05-22T01:33:21.783-07:00

lextudio-support commented 2 hours ago

Copied from CodePlex without authors:

Hi,

andreabertolotto reported a few facts regarding different SNMP agent implementation on WALK operation,

http://sharpsnmplib.codeplex.com/Thread/View.aspx?ThreadId=208429

It does kind of match what you found from Wireshark capture. You can collect more evidence to see whether that's an agent specific issue.

Regards,

Lex

Original Posted Date: 2010-05-22T04:49:45.983-07:00

lextudio-support commented 2 hours ago

Copied from CodePlex without authors:

Ok,

I finialy figured out what I was doing wrong. The table for the node is not populated untill the connection establishes correctly and fills in the routing table for the router. It just took learning more about how the hardware works. So at least for a topology table it "could" be important for the router to establish a working connection before it will walk the table.

Thanks for the support and the use of this Library.

Michael

Original Posted Date: 2010-05-25T10:46:39.897-07:00

lextudio-support commented 2 hours ago

Marked as Answer Date: 2013-10-06T20:48:23.143-07:00