On 16 February 2011 09:31, Steve (Telsat Pacific) <st...@telsat.vu> wrote:
> ... this was the only output I got from [the agent]:
> wcs001:~# snmpd -f -Le
> Turning on AgentX master support.
> NET-SNMP version 5.6.1
> ^CReceived TERM or STOP signal... shutting down...
> wcs001:~#
OK - so it's not complaining about anything.
That's a good start.
So there are two possible reasons why you're not
getting a response to your query:
- either the agent isn't receiving the request, or
- the agent gets the request, but refuses to process it.
To determine which, try running the agent using
snmpd -f -Le -d
and then query it again.
You should see dumps of the incoming (?and outgoing)
request packets. Do you see this or not?
If not, then I'd suspect access control problems.
What is the exact command you are using to test with?
If you do see incoming packets (but nothing outgoing),
then that's almost certainly access control.
What is the exact command you are using to test with?
What are the contents of the snmpd.conf file?
(If you see both incoming and outgoing packets, that's
a more unusual situation. But we'll cross that bridge
when we come to it!)
> It seems as if somehow, someway, the installation's been messed up.
Not necessarily.
We can't really say that until we've tracked down what is actually wrong.
> I would have thought the setup of the snmp service would have been
> done by the 'make install'.
Unfortunately, things aren't quite that simple.
The Net-SNMP suite is designed to run on a range of different operating
systems, all of which have different mechanisms for starting services.
Even within the Linux world, the /etc/init.d mechanism is not necessarily
consistent across all distributions - let alone when you include Solaris,
HP-UX, etc (not to mention Windows with Cygwin and/or MinGW)
(And looking more closely, the dist/snmpd-init.d script seems to be
designed for Solaris, so may not work directly on Linux systems!)
Trying to handle all of this automatically within the "make install"
system is non-trivial. Particularly since this could be installed in
parallel to a vendor-supplied version. We cannot simply over-write
the files from an RPM- or deb- package
The only "safe" approach is to install the basic software, and let
the network or system administrator take care of integration issues.
Dave
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
