search cancel

The "LRAD_DISASSOCIATED" alarm is not getting cleared when an AP is moved from one controller to another

book

Article ID: 229511

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

When an AP is moved from one controller to another, the "LRAD_DISASSOCIATED" alarm is asserted on the AP model. However, the "LRAD_DISASSOCIATED" is not cleared as expected.

   

Environment

Release : 21.2

Component : Spectrum Alarm & Event Management

Cause

The traps are received at the controller device model.

For the bsnAPDisassociated trap, Spectrum takes the value of the bsnAPName varbind and looks for an AP model associated with the controller device model with the same name. If found, Spectrum generates the 0x04b60007 event on the AP model and asserts a minor alarm.

For the ciscoLwappApAssociated trap, Spectrum takes the value of the cLApName varbind and looks for an AP model associated with the controller device model with the same name. If found, Spectrum generates the 0x00210e0c event on the AP model. If that AP model has a minor alarm generated from the 0x04b60007 event previously, that alarm is cleared.

This functionality works IF both traps are received on the same controller device model.

The issue is when an AP is moved from one controller to another, the bsnAPDisassociated trap is sent from the old controller device and the ciscoLwappApAssociated trap is sent from the new controller device.

When the ciscoLwappApAssociated trap is received by Spectrum, the AP model is not yet associated with the new controller device model.

The trap is sent by the new controller device before the AP model in Spectrum is associated to the new controller model.

Resolution

There is no resolution to this issue because the ciscoLwappApAssociated trap is sent before Spectrum can associate the AP to the new controller model.