Southbound Gateway integration creating duplicate EventModel models after upgrading to Dx NetOps 20.2.10 (10.4.3)

Products

• CA Spectrum
• DX NetOps

Issue/Introduction

We have several southbound gateways configured on both landscapes. All of them are exhibited this problem.

Since the completion of the upgrade from 10.4.1 to 20.2.10 all of the SBGWs have been generating new EventModels when an existing EventModel already exists. 

Environment

Release : 20.2.3 and above

Component : Spectrum Integrations / Southbound Gateway

Cause

There appears to be a bug when saving a trap varbind to event variable 106 in the AlertMap file. For example:

1.3.6.1.4.1.9999.6.3  0xfff01cc9 1.3.6.1.4.1.9999.1(106,0)\
                                 1.3.6.1.4.1.9999.2(1,0)

When the first trap comes in, if no EventModel model exists with a model name the same as the values received from varbind 1 in the trap, a new EventModel model will be created with that model name.

If another trap comes in with the same value for varbind 1 but a different value for varbind 106 from the previous trap, a new EventModel model will be created even though there is already an EventModel model with the same model name.

Resolution

As a work around, modify the AlertMap to save the trap varbind to an event variable other than 106. For example:

1.3.6.1.4.1.9999.6.3  0xfff01cc9 1.3.6.1.4.1.9999.1(110,0)\
                                 1.3.6.1.4.1.9999.2(1,0)

Additional Information

The resolution to this issue will be included in Spectrum 22.2.11. No specific release date set at the time this article was published.