Skip to main content
NetApp Knowledge Base

Subscribed syslog EMS events not appearing AIQUM set up with Kyiv Timezone

  1. Last updated
  2. Save as PDF
Views:
28
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • ActiveIQ Unified Manager (AIQUM) 9.x
  • All OS platforms
  • Syslog EMS

Issue

  • Some of the subscribed syslog EMS events not appearing AIQUM
  • Alerts appear for other EMS events shows future timestamp in AIQUM GUI
  • ONTAP/AIQUM server timezone appears correct
  • Errors present on ocumserver.log while subscribing an event wafl.vvol.offline and testing the same from ONTAP:

     DEBUG [vldshka] [default task-24] [service.ems.SubscribeEmsDataAccessService|loadData] [org.dozer.fieldmap.FieldMap] Getting ready to invoke write method on the destination object. Dest Obj: SubscribedEmsDto, Dest value: wafl.vvol.offline
     DEBUG [vldshka] [default task-24] [service.ems.SubscribeEmsDataAccessService|loadData] [org.dozer.MappingProcessor] MAPPED: SubscribedEms.messageName --> SubscribedEmsDto.messageName    VALUES: wafl.vvol.offline --> wafl.vvol.offline    MAPID:
     DEBUG [vldshka] [default task-24] [service.ems.SubscribeEmsDataAccessService|loadData] [org.dozer.fieldmap.FieldMap] Getting ready to invoke write method on the destination object. Dest Obj: SubscribedEmsDto, Dest value:
     DEBUG [vldshka] [default task-24] [service.ems.SubscribeEmsDataAccessService|loadData] [org.dozer.MappingProcessor] MAPPED: SubscribedEms.description --> SubscribedEmsDto.description    VALUES:  -->     MAPID:
     DEBUG [vldshka] [default task-24] [service.ems.SubscribeEmsDataAccessService|loadData] [org.dozer.fieldmap.FieldMap] Getting ready to invoke write method on the destination object. Dest Obj: SubscribedEmsDto, Dest value: Invalid
     DEBUG [vldshka] [default task-24] [service.ems.SubscribeEmsDataAccessService|loadData] [org.dozer.MappingProcessor] MAPPED: SubscribedEms.status --> SubscribedEmsDto.status    VALUES: Invalid --> Invalid    MAPID:

     DEBUG [oncommand] [SyslogServer: udp] [o.s.t.jta.JtaTransactionManager] Participating in existing transaction
     DEBUG [oncommand] [SyslogServer: udp] [o.s.jdbc.datasource.DataSourceUtils] Fetching JDBC Connection from DataSource
     ERROR [oncommand] [SyslogServer: udp] [c.n.d.e.i.o.f.ClusterEntityManager] ERROR while retriving cluster id for the BGP LIF
     DEBUG [oncommand] [SyslogServer: udp] [o.s.t.jta.JtaTransactionManager] Participating in existing transaction
     INFO  [oncommand] [SyslogServer: udp] [c.n.d.o.o.s.OntapOutboundServiceFactory] Getting serviceType EMS_SERVICE and clientType REST from service registry
     DEBUG [oncommand] [SyslogServer: udp] [o.s.t.jta.JtaTransactionManager] Participating transaction failed - marking existing transaction as rollback-only
     DEBUG [oncommand] [SyslogServer: udp] [o.s.t.jta.JtaTransactionManager] Setting JTA transaction rollback-only
     INFO  [oncommand] [SyslogServer: udp] [com.netapp.dfm.collector.LockUtils] Releasing ems-processing lock(java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock@139764ee[Locked by thread SyslogServer: udp]) for 18
     DEBUG [oncommand] [SyslogServer: udp] [o.s.t.jta.JtaTransactionManager] Initiating transaction rollback
     ERROR [oncommand] [SyslogServer: udp] [c.n.dfm.impl.ems.SysLogEventHandler] Problems with Syslog Invalid get collection request with cause : "\"36\" is an invalid value for field \"message.name\" (<Message Name>)":null. On Cluster:<Node_Management_IP>

  • Error suggests that AIQUM cant get the cluster details from node management LIF

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.