In Spectrum 10.4.1, the code was improved to assign AccessPoint-related alarms to the AccessPoint rather than to the Wireless Controller that sends them.
(referring to last paragraph of )
The "LRAD_DISASSOCIATED" 0x04b60007 alarm successfully creates on the AP however this alarm does not clear when the AP comes back. When the
access point comes back up and a ciscoLwappAssociated trap is received it generates an Associated alarm on the controller and does not clear the disassociated alarm
example: "LRAD_DISASSOCIATED" 0x04b60007 on the Access Point
Example: ciscoLwappAssociated event still generated on the controller
Release : 10.4.1, 10.4.2
Component : Spectrum Core / SpectroSERVER
This is addressed in Spectrum 10.4.1 and 10.4.2 with the following BMP patches:
10.04.01.BMP_10.4.102 (~Oct 2020)
10.04.02.BMP_10.4.201 (~Sept 2020)
In addition, the BMP's will also address bsnAPIfUp trap not clearing the bsnAPIfDown alarm.
This issue is also addressed in Spectrum 10.4.2.1 ad higher.