AccessPoint Disassociated Alarm Does Not Get ClearedBy Associated Trap

book

Article ID: 196476

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction


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 )
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/dx-netops/20-2/Fault-Monitoring-with-DX-Spectrum/managing-network/wlc-manager.html

 

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

 

Environment

Release : 10.4.1, 10.4.2

Component : Spectrum Core / SpectroSERVER

Resolution


This will be corrected in the next BMP fixes for 10.4.1 and 10.4.2

Spectrum 10.4.1
10.04.01.BMP_10.4.102 (~Oct 2020)

Spectrum 10.4.2
10.04.02.BMP_10.4.201 (~Sept 2020)


In addition, the BMP's will also address bsnAPIfUp trap not clearing the bsnAPIfDown alarm

Attachments