Managing Wireless N+1 redundancy Configuration

[tcp_analysis_flags_eq_1]

Hello,

I am running WLC HA using N+1 solution wherein the configuration are managed seperately. Current problem is I need to ensure that the changes I have on WLC1 should also be performed on WLC2.

What options are available to manage the configuration without doing manual work, eg. DNAC(intent), Compliance etc. so when there is a difference in profiles for the WLC I can quickly identifiy

[marce1000]

 - The disadvantage  of N+1 versus HA SSO is that the configurations must be synced manually , 

 M.

[tcp_analysis_flags_eq_1]

Okay provided that it is manual, any other monitoring compliance checks can be done to easily spot the differences

[marce1000]

  - You could have a look at https://meldmerge.org/#     (e.g.)
     If we talk about compliance then you also can have the configuration(s) of a 9800 platform 
     evaluated by the Wireless Config Analyzer  by using the command show tech wireless and
     feed the output from that in the mentioned link (tool). Do not use a simple show tech as input
     for this procedure.
     This is more elaborated , but very useful and recommended for 9800 controllers , it can point
     out differences for the N+1 controllers too but is more elaborated

 M.

[Haydn Andrews]

DNAC intent will work, but u need to provision both WLCs at same time to not get out of sync

[tcp_analysis_flags_eq_1]

So, this will not work for brownfield devices wherein there is already existing configuration without having to migrate to intent DNAC managed and provision right?

[Leo Laohoo]

We use Notepad++ with the Compare plugin and compare the config. 

Another option is to check the file size of the config.text files of both units. 

Finally, use the command "sh run".  If someone has changed the config, the first three lines of the output will provide the username and the time-and-date.