Hi,
I have a problem with snmpd daemon running on FreeBSD and Suse Linux
servers. Ideally snmpd daemon should open just 1 port i.e 161 for udp but it
is opening multiple ports on my machine. I have not configured it or used
options to open multiple ports but still it is opening multiple udp ports.
Thanks Prasanna..
From: Prasanna Varadharajan [mailto:[email protected]]
Sent: Thursday, August 20, 2009 3:38 PM
To: Dey, Rajnish; [email protected]
Subject: RE: How to extract index value from *request (netsnmp_request_info)?
Hi Rajnish,
Please refer the definition
Thanks Dave. I saw the FAQ and that had the solution. Now I can set the IP
for Alert destination for object ...AlertDestinationIP
snmpset -v1 -c public 192.168.2.112 OID a 192.168.2.152
Here type 'a' is of type IPaddress. once the agent will start to support
ipv6, I will try to set ipv6 and find
[CCing the -coders list again; please keep conversations on the list]
> On Fri, 21 Aug 2009 11:45:38 -0400, Daniel Savard
> said:
DS> I did preliminary work and found that the old SMIv1 traps definitions are
DS> ignored by the @foreach $n notifications@ loop. Only those specified as pe
I could not find this in the bug list. Apologies if I have missed it.
When a subagent sends a message (e.g. registering a MIB portion) to the
AgentX master, it looks for its response by checking the PacketID of all
incoming packets. If the PacketID matches, it assumes that it will be
the respon
