INCORRECT ALARM ATTRIBUTE TYPE after upgrading Spectrum to 24.3+

Products

• Network Observability
• Spectrum

Issue/Introduction

When upgrading Spectrum in a Fault Tolerant environment, the following alarm is generated for all alarms when the Primary SS is started:

INCORRECT ALARM ATTRIBUTE TYPE

Variable which failed: nim event id (varbind id 10)

Expected type was 17, type found was 0

Cause

During upgrade, the standard procedure is to upgrade the primaries first, and then the secondaries.  When the primaries are upgraded and started, they sync the alarms to the secondary SS.  The secondary SS is still running a pre 24.3.3 version of Spectrum and the alarm attribute for NIM Event ID (0x13527) does not yet exist which generates the alarm.

Resolution

Upgrade the secondary SpectroSERVERs to 24.3.+

Once they are upgraded you can manually clear these alarms and since the SpectroSERVERs will be at the same version the alarms will no longer generate.

Preventing this alarm generation (0x10f85) on upgrade for the NIM Event id has been fixed out of the box in 24.3.7.

Additional Information

Release Notes from 24.3.7

 

Symptom: After upgrading to 23.3.3 and higher, users encounter INCORRECT ALARM ATTRIBUTE TYPE alarms for the NIM_Event_ID attribute during Fault Tolerant (FT) alarm synchronization. This issue occurs when alarms are generated on the secondary server while the primary server is being upgraded, and the secondary is still running a lower version.
Resolution: With this fix, Spectrum makes the necessary code changes to ensure that INCORRECT ALARM ATTRIBUTE TYPE alarms are no longer generated during FT alarm synchronization.
(DE166958, 24.3.7)