Chassis Down alarms fail to clear in DX Operational Observability (DX O2)

Products

• DX Operational Observability
• DX SaaS

Issue/Introduction

In environments integrating Spectrum with DX Operational Observability (DX O2), certain alarms, specifically 'Chassis Down' or 'Blade Status Unknown', may fail to clear in the DX O2 console even after they are cleared or resolved in Spectrum. This occurs when multiple rapid alarm events cause the connector to misidentify the alarm update target.

Symptoms

• Alarms remain in 'Open' or 'Critical' status in DX O2 while showing as 'Cleared' in Spectrum.
• The DX O2 connector (SPUB) updates alarms based on model name rather than the specific Alarm ID.
• Discrepancies in alarm counts between Spectrum and DX O2.

Environment

• DX Operational Observability (DX O2) On-Premise 26.1
• DX Operational Observability (DX O2) SaaS 26.6.1
• Spectrum Data Publisher (SPUB)

Cause

This issue is caused by a product defect (DE670730) where the connector becomes desynchronized when multiple alarms (such as a Chassis Down followed by a FRU Removal) occur in rapid succession. The connector incorrectly updates an existing alarm record instead of processing the clear for the original Alarm ID.

Resolution

Fixed in release DX O2 OnPrem 26.1 HF#2 and higher.

Additional Information

Techdocs DX O2 OnPremise - Release NOTES