DX NetOps shows system Events but no Threshold Violation Events

Products

• DX NetOps
• CA Performance Management - Usage and Administration

Issue/Introduction

CA PC is not showing threshold violation events under the specific threshold profiles in version 22.2.5. I can see the threshold events in 20.2 version.

After a migration from 20.2.x to 22.2.x we see system Events like discovery and rollup activities in DX NetOps Performance Management Portal web UI. We do not see Threshold Violation Events.

The older 20.2 system migrated from still shows the correct data.

The recommended migration path is to upgrade old software to new software on the old systems. Install the new software release on the new hosts. Migrate from old hosts with new software release to new hosts with new software release.

The path followed here involved installing old software on new temporary hosts. Migrate old software/old hosts to old software/new temp hosts. Upgrade new temp hosts. Migrate new software/new temp hosts to new software/new permanent hosts.

During the Data Aggregator old software->new software installs and upgrades on the new temp hosts problems were encountered. They were completely uninstalled and clean new 22.2.x installs were run.

Environment

All support DX NetOps Performance Management releases

Cause

The Data Aggregator upgrade install run problems resulted in two required schema changes to the DR DB alarms table being missed during the upgrade problems. The new DA install with 22.2.x, being a new install, would have assumed the DR DB schema was equally new and clean/correct. Only an upgrade would trigger the schema additions.

The metric_values_min and metric_values_max columns.

As a result when the Data Aggregator sent new Events to the DR DB it failed to write them to the DB due to the missing columns for values the DA provided.

Resolution

This was resolved by adding the missing columns using the following vsql commands.

NOTE: This should only be done at the direction of the Broadcom Support team after validating it will fix the problem at hand. These were the solution for a very specific set of problems.

ALTER TABLE alarm ADD COLUMN IF NOT EXISTS metric_values_min VARCHAR( 128 );
ALTER TABLE alarm ADD COLUMN IF NOT EXISTS metric_values_max VARCHAR( 128 );
ALTER TABLE alarm_clear ADD COLUMN IF NOT EXISTS metric_values_min VARCHAR( 128 );
ALTER TABLE alarm_clear ADD COLUMN IF NOT EXISTS metric_values_max VARCHAR( 128 );