RE: Solaris 10's Net-SNMP requires Unix Domain Sockets

Matt,

I tried some higher port to open TCP socket for agentX but didn't solve
the problem. I would like to get some information from Net-SNMP folks,
whether or not TCP/UDP agentXSocket is really blocked on Sun Solaris-10.

Regards
Birendra

-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Friday, August 01, 2008 8:29 AM
To: Sinha, Birendra (Birendra);
[email protected]; Larry Dickson;
[email protected]; [email protected]
Cc: [email protected]
Subject: Re: Solaris 10's Net-SNMP requires Unix Domain Sockets

Birendra,

I am not sure about Solaris, but there could be a problem running on
privileged ports. You might try running your agent on a higher port
number and see if that works.

Matt
Matthewsacks.com
Sent from my Verizon Wireless BlackBerry


________________________________

From: Sinha, Birendra (Birendra) 
Sent: Thursday, July 31, 2008 12:34 PM
To: 'Larry Dickson'; [email protected];
'[email protected]'
Cc: '[email protected]'
Subject: RE: Solaris 10's Net-SNMP requires Unix Domain Sockets

Larry,
 
I think problem here is something different. Please see the details
below:
 
Solaris 10 is shipped with System Management Agent(SMA) which is an SNMP
agent that is based on Net SNMP. The Net-SNMP version used in SMA is
5.0.9. We are using iReasoning Agent Builder for subagent building.
These are Java based agentX subagents and requires a TCP port on which
the master agent is listening to establish a connection. I tried to
enable TCP AgentX connection on port 705 by adding the following two
lines in the /etc/sma/snmp/snmpd.conf file,
 
master agentx
agentxSocket tcp:localhost:705
 
But this doesnot help. The same thing worked on Linux. Even netstat -an
doesnot show the agent listening on 705 tcp port and my subagent fails
to connect to the Net Snmp master agent.
The snmp log shows the following error,
 
bash-3.00# tail -f /var/log/snmpd.log
seaproxy_sendReq: SEA Master Agent not responding
Turning on AgentX master support.
Error: tcp:localhost:705         transport is not supported, disabling
agentx/master.
NET-SNMP version 5.0.9
 

In SMA, the only allowable AgentX transport is UNIX domain sockets, so
only sessions on UNIX domain sockets are created. It does not allow
subagents to use UDP and TCP ports, refer
http://docs.sun.com/app/docs/doc/817-3155/6mip4hnn0?a=view. As Java is
platform independent and UNIX domain sockets are unix specific, Java
doesnot support Unix domain sockets. 
 
Regards
Birendra

________________________________

From: Larry Dickson [mailto:[email protected]] 
Sent: Tuesday, July 29, 2008 7:40 PM
To: Sinha, Birendra (Birendra)
Cc: [email protected]
Subject: Re: Solaris 10's Net-SNMP requires Unix Domain Sockets


Hi,
 
Check my long thread circa April 18, labeled "5.4.1 won't talk". Recent
versions turned out to have a requirement that older (5.2.1) versions
did not, to make certain setup calls in a certain order or otherwise the
socket connection does not get made. I don't know if this is related to
your problem but it could be.
 
Larry Dickson
Cutting Edge Networked Storage
 
On 7/28/08, Sinha, Birendra (Birendra) <[email protected]> wrote: 


	Hi,
	
	Please see the mail thread below, Mike suggetions didn't solve
my
	problem.
	
	I am using Net SNMP version 5.0.9 shipped with Solaris10 and
iReasoning
	Agent builder for sub agent building. This subagent requires a
TCP port
	on which the master agent is listening to establish a
connection. I
	tried to enable TCP AgentX connection on port 705 by adding the
	following two lines in the /etc/sma/snmp/snmpd.conf file,
	
	master agentx
	agentxSocket tcp:localhost:705
	
	But this doesnot help. The same thing worked on Linux. Even
netstat -an
	doesnot show the agent listening on 705 tcp port and my subagent
fails
	to connect to the Net Snmp master agent.
	
	I also tried the following,
	
	bash-3.00# /usr/sfw/sbin/snmpd -f -L -d -X -x localhost:705
	
	Error: Failed to connect to the agentx master agent: Unknown
host
	(Connection refused)
	
	Sending 46 bytes to 127.0.0.1
	0000: 30 2C 02 01  00 04 06 70  75 62 6C 69  63 A1 1F 02
	0,.....public...
	0016: 04 34 92 C8  F0 02 01 00  02 01 00 30  11 30 0F 06
	.4.........0.0..
	0032: 0B 2B 06 01  04 01 2A 02  0F 0A 01 01  05 00
	.+....*.......
	
	
	Resending 46 bytes to 127.0.0.1
	0000: 30 2C 02 01  00 04 06 70  75 62 6C 69  63 A1 1F 02
	0,.....public...
	0016: 04 34 92 C8  F0 02 01 00  02 01 00 30  11 30 0F 06
	.4.........0.0..
	0032: 0B 2B 06 01  04 01 2A 02  0F 0A 01 01  05 00
	.+....*.......
	
	seaproxy_sendReq: SEA Master Agent not responding dlopen failed:
	ld.so.1: snmpd: fatal: /usr/sfw/lib/amd64/libseaProxy.so: wrong
ELF
	class: ELFCLASS64 dlopen failed: ld.so.1: snmpd: fatal:
	/usr/sfw/lib/amd64/libseaExtensions.so: wrong ELF class:
ELFCLASS64
	/etc/sma/snmp/snmpd.conf: line 105: Warning: Unknown token:
trap2sink.
	NET-SNMP version 5.0.9
	Error: Failed to connect to the agentx master agent: Unknown
host
	(Connection refused)
	Error: Failed to connect to the agentx master agent: Unknown
host
	(Connection refused)
	
	How can I enable the TCP AgentX connector?
	-----Original Message-----
	From: Sinha, Birendra (Birendra)
	Sent: Monday, July 28, 2008 11:56 AM
	To: Thipse, Amruta (Amruta); Chatterjee, Amarnath (Amarnath)
	Subject: FW: Solaris 10's Net-SNMP requires Unix Domain Sockets
	
	
	-----Original Message-----
	From: Mike Ayers [mailto:[email protected]]
	Sent: Friday, July 25, 2008 11:03 PM
	To: Sinha, Birendra (Birendra);
[email protected]
	Subject: RE: Solaris 10's Net-SNMP requires Unix Domain Sockets
	
	> From: [email protected]
	> [mailto:[email protected]] On
Behalf Of
	> Sinha, Birendra (Birendra)
	> Sent: Friday, July 25, 2008 2:41 AM
	
	> I am using iReasoning Agent builder for building the subagent.
	> Solaris 10's Net-SNMP requires Unix Domain Sockets for Agentx.
Java
	> doesn't supprt Unix Domain Sockets, therefore, no Java
subagents for
	> Solaris 10's Net-SNMP.
	
	       The net-snmp AgentX implementation supports TCP
connections.
	See the snmpd.conf manpage for details.  Note that the TCP
AgentX
	connector is known to be insecure, which is why the agent is
usually
	shipped with it turned off.
	
	
	       HTH,
	
	Mike
	
	
------------------------------------------------------------------------
-
	This SF.Net email is sponsored by the Moblin Your Move
Developer's challenge
	Build the coolest Linux based applications with Moblin SDK & win
great prizes
	Grand prize is a trip for two to an Open Source event anywhere
in the world
	http://moblin-contest.org/redirect.php?banner_id=100&url=/
	_______________________________________________
	Net-snmp-coders mailing list
	[email protected]
	https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users