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.
No new data in the alarminfo table of the reporting database
Article ID: 237295
Updated On:
Products
DX NetOps
CA Spectrum
Issue/Introduction
Even though the SRM is processing the alarm events, they are not added to the alarminfo table.
There are no errors logged about the handling in tomcat.
The problem is alarm_key 0 is used for new records, so I don't know why the SRM determines 0 as the key.
Checked the alarminfo table, latest alarms are during reboot time.
I investigated with MySQL what is up.
Cause
The 0x10701 and 0x10702 event codes were customized and they are no longer recorded to the historical database.
Environment
Release : 20.2
Component : Spectrum Reporting
Resolution
Remove the customization done on the 0x10701 and 0x10702 event codes.
Attachments
Feedback
Yes
No
Powered by
