RE: Reg: How to do netsnmp snmp walk for IPv6 TCP/UDP mibs

[Mike Ayers]

> From: Arulkumar Ponnusamy [mailto:paru...@gmail.com]
> Sent: Tuesday, July 27, 2010 10:04 PM

> I have installed the net-snmp5.5 on my windows machine and
> configured the snmp agent.
> My snmp agent is running fine. When i try to do snmpwalk for IPv6
> related mibs i am getting
> the following error.
> C:\usr\bin> snmpwalk -v 2c -c default 127.0.0.1 1.3.6.1.2.1.6.16
> TCP-MIB::tcp.16 = No Such Object available on this agent at this
> OID

This could be security:

http://www.net-snmp.org/docs/FAQ.html#I_can_see_the_system_group__but_nothing_else___Why_

Beyond that, the IPv6 table may not have been built into your agent. I don't even know if the IPv6 table was implemented for Windows. Wish I could be of more help.

Mike

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Net-snmp-users mailing list
Net-snm...@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

[Dave Shield]

On 29 July 2010 00:53, Mike Ayers <mike_...@tva.tvworks.com> wrote:
>>       C:\usr\bin> snmpwalk -v 2c -c default 127.0.0.1 1.3.6.1.2.1.6.16
>>       TCP-MIB::tcp.16 = No Such Object available on this agent at this OID

In general, I'd suggest walking 1.3.6.1.2.1.6 (i.e. the 'tcp' group)
This would show whether the IPv4-related TCP information was visible or not.
If not, then this would tend to indicate the "system group only" issue that Mike
mentions.

However, in this case, Mike has hit the nail on the head with the following:

>  I don't even know if the IPv6 table was implemented for Windows.

Looking at the 'netsnmpmibs' Visual C++ project file, this makes reference
to 'mibII\tcpTable.c' (which is IPv4 only), but not the newer 'tcp-mib'
implementation (which includes the IPv6 support).

It *might* be possible to use the winExtDLL mechanism to make use of the
Windows SNMP service information - see README.win32 for more details.
But I've no experience of doing this, and don't actually know whether this
would help here.

Dave