RE: IPv6 support not enabled on Solaris 9 when building Net-SNMP_5.3.1
rahul_k...@agilent.com
>I can reproduce your problem and confirm that this is a bug. I've checked >in a
>fix for CVS MAIN that should allow you to build net-snmp on Solaris (and >AIX,
>Tru64, ...) with support for the UDPIPv6/TCPIPv6 transports. The mibII/ipv6 >MIB
>module still won't be supported, though, so you have to build with
> ./configure --enable-ipv6 --with-out-mib-modules="mibII/ipv6" ...
>Can you please grab a CVS MAIN snapshot from
>http://www.net-snmp.org/nightly/tarballs/ and give it a try? (Please >uninstall
>5.3.1 for the duration of the test.)
Hi,
As suggested, we used following software versions
1) Net-SNMP 5.4.dev (taken from http://www.net-snmp.org/nightly/tarballs/)
2) GCC 3.3
3) Solaris 5.9
The steps as follows
1) Running configure
--------------------
./configure --prefix=/net/tcsnas01/vol/nxqa/qa/local/net-snmp_sol --enable--ipv6 --with-out-mib-modules=mibII/ipv6 --with-cc=gcc --with-persistent-directory=/net/tcsnas01/vol/nxqa/qa/local/net-snmp_sol/var/net-snmp --with-logfile=/net/tcsnas01/vol/nxqa/qa/local/net-snmp_sol/log/snmpd.log
When we look inside config.log we find following details ...
...
configure:23290: checking ipv6 stack type
conftest.c:49:45: /usr/local/v6/include/sys/types.h: No such file or directory
conftest.c:49:22: features.h: No such file or directory
configure:23441: result: postponed
...
configure:23535: checking ipv6 stack type
configure:23559: result: "generic, yes, using libc"
...
2) We run make, make test, make install
---------------------------------------
make runs successfully
make test passes all test cases (2 cases out of 59 failed)
(54: testing 1st CPU on Solaris using HOST-RESOURCES... FAIL)
(57: testing swap on Solaris using HOST-RESOURCES... FAIL)
make install runs successfully
3) We start the snmp agent
--------------------------
We prepare snmpd.conf file as follows
rocommunity SNMP_COMMUNITY-1
rwcommunity SNMP_COMMUNITY-2
rocommunity6 SNMP_COMMUNITY-61
rwcommunity6 SNMP_COMMUNITY-62
We start the agent using following command ./snmpd -d -p udp:161,udp6:161
The snmpd.log says following when agent is started
NET-SNMP version 5.4.dev
Important to note that in Net-SNMP_5.4.dev we do not get Unknown Token error for rocommunity6 and rwcommunity6.
Also when checked through "./snmpd -H" we fine that rocummunity6 and rwcommunity6 are listed as known directives.
4) We Execute snmpget commands
------------------------------
IPv4:
a) snmpget -v1 -c SNMP_COMMUNITY-1 kaveri sysName.0 -> Response - OK
b) snmpget -v1 -c SNMP_COMMUNITY-2 kaveri sysName.0 -> Response - OK
c) snmpget -v1 -c SNMP_COMMUNITY-3 kaveri sysName.0 -> Timeout - OK
IPv6:
a) snmpget -v1 -c SNMP_COMMUNITY-61 udp6:[fe80::203:baff:fe2a:a645] sysName.0 -> No match - NOT OK
b) snmpget -v1 -c SNMP_COMMUNITY-62 udp6:[fe80::203:baff:fe2a:a645] sysName.0 -> No match - NOT OK
5) Support Information
----------------------
Output of "netstat -a -P udp" command as follows
UDP: IPv4
Local Address Remote Address State
-------------------- -------------------- -------
...
*.* Unbound
*.snmp Idle
*.* Unbound
UDP: IPv6
Local Address Remote Address State
-------------------- -------------------- -------
...
SNMP not shown
...
We suspect that agent is not coming up with udp6.
We also tried following commands
./snmpd -d -p udp6:161
But agent did not come up with udp6 it was always bound under UDP:IPv4
Please consider the given information.
Sincerely,
Rahul K
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-coders mailing list
Net-snm...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Thomas Anders
> IPv6:
> a) snmpget -v1 -c SNMP_COMMUNITY-61 udp6:[fe80::203:baff:fe2a:a645] sysName.0 -> No match - NOT OK
> b) snmpget -v1 -c SNMP_COMMUNITY-62 udp6:[fe80::203:baff:fe2a:a645] sysName.0 -> No match - NOT OK
What exactly is the output here?
Anyway, I'm sorry to conclude that you'll probably need to fire up a
debugger and step through snmplib/snmpUDPIPv6Domain.c to find out
where/why it breaks. I don't have access to an IPv6-enabled
Solaris/HP-UX machine to assist myself. If you can come up with
something, please let us know.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
rahul_k...@agilent.com
The output is "No match".
For example
COMMAND -> snmpget -v1 -c SNMP_COMMUNITY-61 udp6:[fe80::203:baff:fe2a:a645] sysName.0
OUTPUT -> No match
We will try using debugger and get back to you with information.
Sincerely,
Rahul K
rahul_k...@agilent.com
Do we need to use gdb on snmpd?
Or we need to use it on snmpget?
Can you please please clarify the steps we need to perform?
rahul_k...@agilent.com
The results of using quotes as follows
% snmpget -v1 -c SNMP_COMMUNITY-61 'udp6:[fe80::203:baff:fe2a:a645]:1161' sysName.0
Timeout: No Response from udp6:[fe80::203:baff:fe2a:a645]:1161.
Now we do not get "No match". Perhaps it was due to shell.
Starting of snmp agent
----------------------
We prepare snmpd.conf file as follows
rocommunity SNMP_COMMUNITY-1
rwcommunity SNMP_COMMUNITY-2
rocommunity6 SNMP_COMMUNITY-61
rwcommunity6 SNMP_COMMUNITY-62
We started agent using following command
./snmpd -d -p udp:161,udp6:1161
The snmpd.log says following when agent is started NET-SNMP version 5.4.dev Important to note that in Net-SNMP_5.4.dev we do not get Unknown Token error for rocommunity6 and rwcommunity6.
Also when checked through "./snmpd -H" we fine that rocummunity6 and rwcommunity6 are listed as known directives.
Support Information
-------------------
Output of "netstat -a -P udp" command as follows
UDP: IPv4
Local Address Remote Address State
-------------------- -------------------- ------- ...
*.* Unbound
*.snmp Idle
*.* Unbound
UDP: IPv6
Local Address Remote Address State
-------------------- -------------------- ------- ...
(*.snmp NOT PRESENT)
...
We suspect that agent is not coming up with udp6 as shown by netstat output and this is the reason why we are now getting timeout.
Sincerely,
Rahul K
-----Original Message-----
From: dave....@googlemail.com [mailto:dave....@googlemail.com] On Behalf Of Dave Shield
Sent: Wednesday, September 06, 2006 1:23 PM
To: rahul_k...@agilent.com
Cc: net-snm...@lists.sourceforge.net; suni...@agilent.com
Subject: Re: IPv6 support not enabled on Solaris 9 when building Net-SNMP_5.3.1
On 06/09/06, rahul_k...@agilent.com <rahul_k...@agilent.com> wrote:
> The output is "No match".
> For example
>
> COMMAND -> snmpget -v1 -c SNMP_COMMUNITY-61 udp6:[fe80::203:baff:fe2a:a645] sysName.0
> OUTPUT -> No match
That feels like a shell error, rather than an SNMP one.
I suspect that snmpget is never getting as far as ever sending the request.
Try quoting the address:
snmpget .... 'udp6:[fe80::203:baff:fe2a:a645]' sysName.0
Dave
Thomas Anders
> ./snmpd -d -p udp:161,udp6:1161
Why "-p"? This option is meant to be used for
-p FILE store process id in FILE
which means that "udp:161,udp6:1161" would be treated as a filename
rather than a transport identifier. Please try again with
./snmpd -d -f -Le -Dnetsnmp_udp6 udp:161,udp6:1161
> UDP: IPv6
> Local Address Remote Address State
> -------------------- -------------------- ------- ...
> (*.snmp NOT PRESENT)
In the netstat output, look for "1161" rather than *.snmp for IPv6
because you've started it on a non-default port!
If it still fails, post the output of the agent. If it isn't helpful
enough, run snmpd under gdb and step through snmplib/snmpUDPIPv6Domain.c
to find out where it fails.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------------------------
rahul_k...@agilent.com
Contents of snmpd.conf file
===========================
rocommunity SNMP_COMMUNITY-1
rwcommunity SNMP_COMMUNITY-2
rocommunity6 SNMP_COMMUNITY-61
rwcommunity6 SNMP_COMMUNITY-62
Starting of snmpd
-----------------
./snmpd -d -f -Le -Dnetsnmp_udp6 udp:161,udp6:1161
Output of netstat -a -P udp
===========================
UDP: IPv4
Local Address Remote Address State
-------------------- -------------------- -------
...
*.snmp Idle
*.1161 Idle
...
UDP: IPv6
Local Address Remote Address State
-------------------- -------------------- -------
*.1161 Idle
Command Execution
=================
IPv6:
% snmpget -v1 -c SNMP_COMMUNITY-61 'udp6:[fe80::203:baff:fe2a:a645]:1161' sysName.0
Timeout: No Response from udp6:[fe80::203:baff:fe2a:a645]:1161
Output On Agent Console
=======================
netsnmp_udp6: fmtaddr: t = 0, data = 2297c8, len = 32
netsnmp_udp6: recvfrom fd 6 got 54 bytes (from UDP/IPv6: [fe80::203:baff:fe2a:a645]:-22606)
netsnmp_udp6: fmtaddr: t = 23a460, data = 2297c8, len = 32
Received 54 bytes from UDP/IPv6: [fe80::203:baff:fe2a:a645]:-22606
0000: 30 34 02 01 00 04 11 53 4E 4D 50 5F 43 4F 4D 4D 04.....SNMP_COMM
0016: 55 4E 49 54 59 2D 36 31 A0 1C 02 04 49 D9 6C 6E UNITY-61....I.ln
0032: 02 01 00 02 01 00 30 0E 30 0C 06 08 2B 06 01 02 ......0.0...+...
0048: 01 01 05 00 05 00 ......
netsnmp_udp6: fmtaddr: t = 23a460, data = 2297c8, len = 32
Received SNMP packet(s) from UDP/IPv6: [fe80::203:baff:fe2a:a645]:-22606
GET message
-- SNMPv2-MIB::sysName.0
netsnmp_udp6_getSecName: resolve <"SNMP_COMMUNITY-61", fe80::203:baff:fe2a:a645>
netsnmp_udp6_getSecName: compare <"SNMP-COMMUNITY-61", 0x/0x000000000000000000000000ffbfed00>... nope
netsnmp_udp6_getSecName: compare <"SNMP_COMMUNITY-62", 0x/0x000000000000000000000000ffbfed00>... nope
(repeats for retries...)
Sincerely,
Rahul K
-----Original Message-----
From: Thomas Anders [mailto:thomas...@blue-cable.de]
Sent: Wednesday, September 06, 2006 2:03 PM
To: rahul_k...@agilent.com
Cc: D.T.S...@csc.liv.ac.uk; net-snm...@lists.sourceforge.net; suni...@agilent.com
Subject: Re: IPv6 support not enabled on Solaris 9 when building Net-SNMP_5.3.1
rahul_k...@agilent.com
I have some breakthrough.
Contents of snmpd.conf
======================
rocommunity SNMP_COMMUNITY-1
rocommunity6 SNMP-COMMUNITY-61
rwcommunity SNMP_COMMUNITY-2
rwcommunity6 SNMP_COMMUNITY-62
Agent Startup
=============
./snmpd -d -f -Le -Dnetsnmp_udp6 udp:161,udp6:1161
Commands
========
IPv4:
1) snmpget -v1 -c SNMP_COMMUNITY-1 -r 0 146.208.148.62:161 sysName.0 -> OK
2) snmpget -v2c -c SNMP_COMMUNITY-1 -r 0 146.208.148.62:161 sysName.0 -> OK
3) snmpget -v1 -c SNMP_COMMUNITY-2 -r 0 146.208.148.62:161 sysName.0 -> OK
4) snmpget -v2c -c SNMP_COMMUNITY-2 -r 0 146.208.148.62:161 sysName.0 -> OK
IPv6:
5) snmpget -v1 -c SNMP_COMMUNITY-61 -r 0 'udp6:[fe80::203:baff:fe2a:a645]:1161' sysName.0 -> NOT OK (Timeout)
6) snmpget -v2c -c SNMP_COMMUNITY-61 -r 0 'udp6:[fe80::203:baff:fe2a:a645]:1161' sysName.0 -> NOT OK (Timeout)
7) snmpget -v1 -c SNMP_COMMUNITY-62 -r 0 'udp6:[fe80::203:baff:fe2a:a645]:1161' sysName.0 -> OK
8) snmpget -v2c -c SNMP_COMMUNITY-62 -r 0 'udp6:[fe80::203:baff:fe2a:a645]:1161' sysName.0 -> OK
Seems like rocommunity6 directive is creating problems.
Agent Console Output (Command #5 from above)
============================================
netsnmp_udp6: fmtaddr: t = 0, data = 2297c8, len = 32
netsnmp_udp6: recvfrom fd 6 got 54 bytes (from UDP/IPv6: [fe80::203:baff:fe2a:a645]:-22382)
netsnmp_udp6: fmtaddr: t = 23a460, data = 2297c8, len = 32
Received 54 bytes from UDP/IPv6: [fe80::203:baff:fe2a:a645]:-22382
0000: 30 34 02 01 00 04 11 53 4E 4D 50 5F 43 4F 4D 4D 04.....SNMP_COMM
0016: 55 4E 49 54 59 2D 36 31 A0 1C 02 04 45 C1 6C FE UNITY-61....E.l.
0032: 02 01 00 02 01 00 30 0E 30 0C 06 08 2B 06 01 02 ......0.0...+...
0048: 01 01 05 00 05 00 ......
netsnmp_udp6: fmtaddr: t = 23a460, data = 2297c8, len = 32
Received SNMP packet(s) from UDP/IPv6: [fe80::203:baff:fe2a:a645]:-22382
GET message
-- SNMPv2-MIB::sysName.0
netsnmp_udp6_getSecName: resolve <"SNMP_COMMUNITY-61", fe80::203:baff:fe2a:a645>
netsnmp_udp6_getSecName: compare <"SNMP-COMMUNITY-61", 0x/0x000000000000000000000000ffbfed00>... nope
netsnmp_udp6_getSecName: compare <"SNMP_COMMUNITY-62", 0x/0x000000000000000000000000ffbfed00>... nope
Am I doing some mistake in snmpd.conf file...
Sincerely,
Rahul K
-----Original Message-----
From: Thomas Anders [mailto:thomas...@blue-cable.de]
Sent: Wednesday, September 06, 2006 7:18 PM
To: rahul_k...@agilent.com
Cc: net-snm...@lists.sourceforge.net; suni...@agilent.com
Subject: Re: IPv6 support not enabled on Solaris 9 when building Net-SNMP_5.3.1
rahul_k...@agilent.com wrote:
> netsnmp_udp6_getSecName: resolve <"SNMP_COMMUNITY-61", fe80::203:baff:fe2a:a645>
> netsnmp_udp6_getSecName: compare <"SNMP-COMMUNITY-61", 0x/0x000000000000000000000000ffbfed00>... nope
> netsnmp_udp6_getSecName: compare <"SNMP_COMMUNITY-62", 0x/0x000000000000000000000000ffbfed00>... nope
This is what needs investigation. Please fire up a debugger and find out
why the masked_address_are_equal() call in
snmplib/snmpUDPIPv6Domain.c:netsnmp_udp6_getSecName() (around line 1285
in MAIN) is failing.