On Mon, 2008-09-29 at 14:22 -0400, Nicholas Jones wrote:
> I am looking at snmpd. I noticed that if you pass a LISTENING
> ADDRESSES it will still listen on port 161. Why not just have the
> listening address override the default ports? I am thinking that I
> would like to install an adapter betwe
Hi ,
Then how to start the Agent with out using snmpd.conf file. (normally
I will start Agent using " snmpd -c /path/snmpd.conf " )
On Fri, Oct 3, 2008 at 7:04 AM, Wes Hardaker <[EMAIL PROTECTED]
> wrote:
> > On Wed, 1 Oct 2008 22:47:51 -0700, "kumar undurthi" <
> [EMAIL PROTECTED]> said
Hi All,
>
>> Thank's for ur help.
>> I have attached the snmpd.conf file. In the snmpd.conf file I am
>> using "public" as community string , so my agent and subagent will start
>> with that snmpd.conf, ( by using :: snmpd -Lo -f -c /path/snmpd.conf
>> ).Later I will start my su
On Sun, 5 Oct 2008 10:36:16 -0700 (PDT)
Amit Kumar <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> how to restrict the manager to contact to particular agent Ip
> address ?
> is agentaddress in snmpd.conf is for that ?
>
> I have a requirement , if the snmp agent IP 255.255.255.255 then a
Hi All,
how to restrict the manager to contact to particular agent Ip
address ?
is agentaddress in snmpd.conf is for that ?
I have a requirement , if the snmp agent IP 255.255.255.255 then any snmp
manager can connect to our snmp agent . but if the snmp agent is having some
differ