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.

SRM is missing NCM config detail


Article ID: 207482


Updated On:


CA Spectrum


SRM is processing NCM buckets but is missing NCM config data so the configs that are in SRM are out of date.  There are scripts that data mine the configs and if the config needs to be updated from what is seen in the SRM data, it will be. There are configs that have been updated that are not showing in the ncm_config table of SRM.


Massive amounts of text in the config change event which is 0x82105a.  There were devices with over 50,000 lines of text in the event between the config detail and the event also includes the policies that are in violation as well as compliance.


Release : 20.2

Component : Spectrum Reporting


This is tentatively scheduled to be fixed in NetOps release 20.2.7 due out in March of 2021:

32369198  - SRM is missing NCM config detail

You will also need to increase the SRM db mysql table for this text:

Navigate in a shell to $SPECROOT/mysq/bin:

./mysql -uroot -proot reporting;

./mysql --defaults-file=../my-spectrum.cnf -uroot -proot reporting;

Run these commands:
alter table ncm_config modify violated_policies varchar(100000);
alter table ncm_config modify compliant_policies  varchar(100000);