Controller Based WLANs

Problem:

Whenever you attempt to run a RRM Analysis manually, the below error is generated:

You will also see these events in the system logging:

Mar 14 13:58:53.697        debug   44:1E:A1:C2:58:5C rfmgr_sc: Entering severe interference state.

Mar 14 13:58:53.712        debug   44:1E:A1:C2:58:5C rfmgr_sc: [94:57:A5:89:82:A0] Severe Interference: Send provisional channel (108) ext (1), with delay metric of (0.042387), goToMax=0, AP metric=0.359245.

Mar 14 13:58:53.755        debug   44:1E:A1:C2:58:5C rfmgr_sc: [94:57:A5:89:82:A0] HandleChannelChangedEvent: Cause=[LocalInterference], OldChannel=[108], NewChannel=[108].

Mar 14 13:58:53.756        debug   44:1E:A1:C2:58:5C rfmgr_sc: [94:57:A5:89:82:A0] Severe interference handled.

Mar 14 13:58:54.365        debug   44:1E:A1:C2:58:5C rfmgr_sc: Exiting severe interference state.

Bigger environmental sites will most likely experience this issue more frequently. This is because the Severe Interference Detection/Mitigation feature is enabled more often.

This feature’s main function is to detect interference and will change the radio reconfiguration to use a new/different channel.

This changes the system’s status as “Not Stable” and thus, prevents the analysis to execute.

This behavior is expected.

It is recommended to:

• disable the Severe Interference Mitigation feature
• re-run the analysis and then
• apply the baseline

The customer will have to decide if they should do this occasionally or leave the Severe Interference Mitigation feature disabled.