On 16/07/07, Need Help <[EMAIL PROTECTED]> wrote:
>  Does the following "netstat" output seem reasonable?

No.



> Here is "netstat -an" output after starting the master agent on port 705
> only:


> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State
> tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN
     :

> Active UNIX domain sockets (servers and established)
> unix  2      [ ACC ]     STREAM     LISTENING     6490   localhost:705


The master agent is not listening on TCP port 705 as expected.
It's listening on a named socket called "localhost:705"

In one sense, this doesn't matter, because the subagent is connecting
to the same named socket.   But it will be incredibly confusing for the
poor sod that has to look after this mess once you move on to pastures new.

Robert's already pointed out that your system doesn't seem to recognise
the name "localhost", and that you should use "127.0.0.1" instead.
I'd propose that you set the AgentX socket to be  "tcp:127.0.0.1:705"
(for both master and subagent).



> 1) /usr/local/bin/snmpwalk -v1 -c mycommunity_ro ocStbHostAVInterfaceTable

You have forgotten to specify the destination host.
The syntax is
                  snmpwalk   ADMIN_SETTINGS     HOST     OID(s)

You've just got
                  snmpwalk   ADMIN_SETTINGS                    OID


>    getaddrinfo: ocStbHostAVInterfaceTable Name or service not known
>    snmpwalk: Unknown host (ocStbHostAVInterfaceTable) (No such file or
> directory)

So snmpwalk it treating the OID (ocStbHostAVInterfaceTable) as the name
of the host to query, and complaining because it doesn't exist.


> 2) /usr/local/bin/snmpget -v 1 -c mycommunity_ro localhost
> ocStbHostAVInterfaceType.1

That's better - you've remembered to include the name of the host.
But as Robert has pointed out, this system doesn't actually recognise
this name.


> 3) /usr/local/bin/snmpget -v 1 -c mycommunity_ro localhost:705
> ocStbHostAVInterfaceType.1

No.
You do *NOT* send SNMP requests to the AgentX port.
This is purely for communication betweent the master and subagent.
You should not attempt to query this directly.

AgentX and SNMP are two different protocols, and you will just
confuse the agents (as well as yourself) if you try to mix them.



Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to