Sitescope generating false ICMP Alert

Hello Friends,

 

We have SIS 11.24 32 bit on Win 2012 64 bit OS. We received an event from Sitescope "Log Event Health Monitor" stating that "Node ddci-sis1.sys is probably down or unreachable".

 

However, Sitescope server is always available. We would like to understand the reason behind Sitescope generating false alert for its own reachability.

 

Can someone please shed some light on this.

 

 

Cheers,

Tags:

Parents
  • Is ddci-sis1.sys the SiS server? Can you check error.log and RunMonitor.log to track down the message that is setting the health monitor into error status?

  • Hello Kenneth,

     

    Yes, ddci-sis1 is our Sitescope server name. I had a look at error.log and RunMonitor.log for the time period when we receive a message "Node ddci-sis1.sys is probably down or unreachable" in OML, but can see only following.

     

    2015-04-21 14:26:26,907 [Monitor Scheduler] (AtomicMonitor.java:1952) ERROR - skipped #1, monitor still running: SiteScope/201721443/201735160/19:( qm-spnode1.qidc.sys 10.1.102.69 ), start executing a task in a process from the process pool...

     

    What else we could do to find the root cause behind Sitecope unreachable event, which we received in OML.

     

     

    Cheers,

Reply
  • Hello Kenneth,

     

    Yes, ddci-sis1 is our Sitescope server name. I had a look at error.log and RunMonitor.log for the time period when we receive a message "Node ddci-sis1.sys is probably down or unreachable" in OML, but can see only following.

     

    2015-04-21 14:26:26,907 [Monitor Scheduler] (AtomicMonitor.java:1952) ERROR - skipped #1, monitor still running: SiteScope/201721443/201735160/19:( qm-spnode1.qidc.sys 10.1.102.69 ), start executing a task in a process from the process pool...

     

    What else we could do to find the root cause behind Sitecope unreachable event, which we received in OML.

     

     

    Cheers,

Children
  • That doesn't seem related. What's the source of this event in OML, the Log Event Health monitor? That event message doesn't seem to comply with new OM integration event mapping, how are you sending events from SiS?

  • That doesn't seem related. What's the source of this event in OML, the Log Event Health monitor? That event message doesn't seem to comply with new OM integration event mapping, how are you sending events from SiS?

  • That doesn't seem related. What's the source of this event in OML, the Log Event Health monitor? That event message doesn't seem to comply with new OM integration event mapping, how are you sending events from SiS?

  • Hello Kenneth,

     

    Yes, source of this event in OML is indeed Log Event Health monitor.  We have checked following settings in Sitescope -> Integration Preferences.

     

    Enable HP Operations Manager metrics integration

    Enable Metrics reporting for new monitors

     

    Does the issue is related with Sitescope -> OML Integration, I doubt it !!

     

     

    Cheers,

     

     

  • Can you check if you have integrated to OML with new OM integration settings in Integration Preferences?  That is, sending events via OA installed in SiS server using Common Event Mapping preferences.

     I don't think this is the case as the event format doesn't match OOTB event mapping, but check if the event raw data is written to logs/HPSiteScopeOperationsManagerIntegration.log

     

    Another posibility is that you're using old and unsupported integration via script alerts calling to opcsendmsg.

     

    You need to track down how the Health monitor is sending this event.

     

  • Can you check if you have integrated to OML with new OM integration settings in Integration Preferences?  That is, sending events via OA installed in SiS server using Common Event Mapping preferences.

     I don't think this is the case as the event format doesn't match OOTB event mapping, but check if the event raw data is written to logs/HPSiteScopeOperationsManagerIntegration.log

     

    Another posibility is that you're using old and unsupported integration via script alerts calling to opcsendmsg.

     

    You need to track down how the Health monitor is sending this event.

     

  • Can you check if you have integrated to OML with new OM integration settings in Integration Preferences?  That is, sending events via OA installed in SiS server using Common Event Mapping preferences.

     I don't think this is the case as the event format doesn't match OOTB event mapping, but check if the event raw data is written to logs/HPSiteScopeOperationsManagerIntegration.log

     

    Another posibility is that you're using old and unsupported integration via script alerts calling to opcsendmsg.

     

    You need to track down how the Health monitor is sending this event.