ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

False device reboot alarms in Spectrum

book

Article ID: 240098

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

the customer has pair of Cisco ASA 5585 SSP60.  He receives several false "device has been rebooted" events a day. Neither the device has been rebooted nor the SNMP agent was restarted. This can be seen from a sniffer trace and event reports. Because the customer has configured that those events should generate an alarm he receives a lot of false tickets.

Cause

Device reboot calculations are incorrect for the 2 Cisco ASA devices.
We see snmpEngineTime and sysUpTime constantly rising but Spectrum is using the incorrect values in the scratchpad where it mistakes the next value for the previous one and alarms.

enabled reboot debug and see the following which does not match the packet capture.
The previous value quoted in the debug is actually the subsequent value 

https://knowledge.broadcom.com/external/article?articleId=95651

Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHRebootMonitor.cc(496): Checking if reboot event will be generated for model handle = 0x8073040
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHRebootMonitor.cc(497): Previous sratchpad value for 0x230c53 attribute of this model = 10280982
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHRebootMonitor.cc(498): Latest value for 0x230c53 attribute of this model = 10280980
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHsnmpEngineTimeMonitor.cc(317): Current snmpEngineTime value for this model = 10280980
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHsnmpEngineTimeMonitor.cc(321): Previous snmpEngineTime of this model = 10280982
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHsnmpEngineTimeMonitor.cc(324): Creating reboot event  = 0x11db1

Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHRebootMonitor.cc(496): Checking if reboot event will be generated for model handle = 0x8073040
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHRebootMonitor.cc(497): Previous sratchpad value for 0x10245 attribute of this model = 918216700
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHRebootMonitor.cc(498): Latest value for 0x10245 attribute of this model = 918216500
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHsysUpTimeMonitor.cc(220): Current sysUpTime value for this model = 918216500
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHsysUpTimeMonitor.cc(223): Previous sysUpTime value for this model = 918216700
Dec 01 11:50:22 REBOOT NOTIFY DEBUG:  TRACE at IHsysUpTimeMonitor.cc(225): Creating reboot event  = 0x10ff0

This is only happening when Spectrum polls for sysuptime consequentially in less than 5 seconds.  

Environment

Release : 21.2.8

Component : Spectrum Alarm

Resolution

    21.02.08.D56

 

    REQUIREMENTS

        SPECTRUM 21.02.00 and 21.02.08 are the prerequisites for installation of this patch.

 This patch needs to be installed on SpectroSERVER.

    OVERVIEW 

        This is a Debug patch for the following issue:

 DE530779 Details:
   33055142:  False device reboot alarms on 21.2.8
  (DE530779, 33055142)

    
   BILL OF MATERIALS
 
 ReleaseNote.D56.txt 
 runme (Linux)
 uninstall_D56.pl (Linux)
  libmdlsvint.so.1 (Linux)
  libmdlsvutil.so.1 (Linux)