Will,

Is your mgmt server using an RFC 1918 address, or is it using localhost?

-Si

On Thu, Aug 17, 2023 at 2:13 PM Will Conrad <wcon...@hivelocity.net.invalid>
wrote:

> H K,
>
> Thanks for responding.
>
> Not a communication issue. The traps are not being sent. I've turned up
> tcpdump on the mgmt host and monitored for traffic to our trap receiver. No
> trap ever leaves the server.
>
> Regards,
>
> Will
>
>
>
> On Thu, Aug 17, 2023 at 3:06 PM K B Shiv Kumar <s...@indiqus.com.invalid>
> wrote:
>
> > Sorry didn't go through it fully. Most likely an SNMP communication
> issue.
> > I hope your SNMP server is enabled to support version 2c and it is not
> > disabled. Nowadays v3 is the default I believe.
> >
> > Regards,
> > Shiv
> > (Sent from mobile device. Please excuse brevity and typos.)
> >
> > On Fri, 18 Aug 2023, 00:32 K B Shiv Kumar, <s...@indiqus.com> wrote:
> >
> > > Hi Will
> > >
> > > Is your community "public"? Any info in the logs? Did you try Syslog?
> Why
> > > I'm asking is to zero in on SNMP traps vs Syslog or the alerting
> > mechanism
> > > itself.
> > >
> > > Regards,
> > > Shiv
> > > (Sent from mobile device. Please excuse brevity and typos.)
> > >
> > > On Thu, 17 Aug 2023, 23:17 Will Conrad, <wcon...@hivelocity.net
> .invalid>
> > > wrote:
> > >
> > >> Hi All,
> > >>
> > >> Bump
> > >>
> > >> Any word on this? Does anyone know how to get SNMP working in
> > cloudstack?
> > >>
> > >> On Tue, Aug 8, 2023 at 7:37 AM Will Conrad <wcon...@hivelocity.net>
> > >> wrote:
> > >>
> > >> > I followed the cloudstack documentation here:
> > >> >
> > >> >
> > >> >
> > >>
> >
> https://docs.cloudstack.apache.org/en/4.18.0.0/adminguide/management.html?highlight=snmp#configuring-snmp-and-syslog-managers
> > >> >
> > >> > to get SNMP traps working, however, no traps are being sent. I don't
> > see
> > >> > any related errors logged. I see no instances of failed library
> loads,
> > >> but
> > >> > I do not see. Do I need to manually install the libsnmp4j library
> > >> myself?
> > >> >
> > >> > I know it's reading the log4j config as I get this notification in
> the
> > >> > management server log:
> > >> >
> > >> > 2023-08-07 18:20:42,842 INFO  [c.c.u.LogUtils] (main:null) (logid:)
> > >> log4j
> > >> > configuration found at /etc/cloudstack/management/log4j-cloud.xml
> > >> >
> > >> > Here is the log4j config for the SNMP appender (note that I have
> > >> > configured syslog as well, and that is working).
> > >> >
> > >> >  <appender name="SNMP"
> > >> > class="org.apache.cloudstack.alert.snmp.SnmpTrapAppender">
> > >> >
> > >> >       <param name="Threshold" value="WARN"/>
> > >> >
> > >> >       <param name="SnmpManagerIpAddresses" value="<redacted>"/>
> > >> >
> > >> >       <param name="SnmpManagerPorts" value="162"/>
> > >> >
> > >> >       <param name="SnmpManagerCommunities" value="public"/>
> > >> >
> > >> >       <layout
> > >> > class="org.apache.cloudstack.alert.snmp.SnmpEnhancedPatternLayout">
> > >> >
> > >> >          <param name="PairDelimiter" value="//"/>
> > >> >
> > >> >          <param name="KeyValueDelimiter" value="::"/>
> > >> >
> > >> >       </layout>
> > >> >
> > >> >    </appender>
> > >> >
> > >> > Any insight will be greatly appreciated.
> > >> >
> > >> > Regards,
> > >> >
> > >> > Willard
> > >> >
> > >>
> > >
> >
> > --
> > This message is intended only for the use of the individual or entity to
> > which it is addressed and may contain confidential and/or privileged
> > information. If you are not the intended recipient, please delete the
> > original message and any copy of it from your computer system. You are
> > hereby notified that any dissemination, distribution or copying of this
> > communication is strictly prohibited unless proper authorization has been
> > obtained for such action. If you have received this communication in
> > error,
> > please notify the sender immediately. Although IndiQus attempts to sweep
> > e-mail and attachments for viruses, it does not guarantee that both are
> > virus-free and accepts no liability for any damage sustained as a result
> > of
> > viruses.
> >
>

Reply via email to