RE: v5.4.1 traps generated at snmpd startup

"Ron Rader" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <6BA04340F278EB47AB42AAF2EED9CBBA03322A43@dellserver.cipheroptics.local>
> From: Dave Shield [mailto:[email protected]]

> > later, it generated authenticationFailure, and a whole host of
> > linkUp/Down traps for all interfaces in the stack.
> 
> It might be worth commenting out the two monitor directives,
> and see whether you still get the authFail trap.
>    (i.e. are these two linked, or independent).

  I tried commenting out the two monitor lines are restarted the agent.  This prevented BOTH the authenticationFailure and linkUp/Down traps.  Interesting.

  Could the authenticationFailure trap have something to do with my internal user setup (required as far as I can tell for the monitors, which use V3)?

> >  Does snmpd.conf handle any comment delimiters?
> 
> Yes - see the example snmpd.conf file.

  '#' worked just fine, thanks for the tip.  This gives me additional options on our application side (I use snmpd.conf for provisioned data storage).

  Thanks,

  Ron



The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting all copies. Thank you.

------------------------------------------------------------------------------
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.