11-02-2023 04:22 PM
Hi,
I have two Cisco 9800-40 Physical WLCs on version 17.9.4 called WLC-1 and WLC-2.
I have configured WLC-1 as the master.
When configuring redundancy, I configured one the RMI-IP addresses incorrectly. I saved the config and reloaded. Now I don't have a HA-Pair due to this wrong IP.
I have tried to edit it but it is greyed out. On the command-line, I have also tried unsuccessfully.
redun-management interface vlan 10 chassis 1 address 10.10.10.12 chassis 2 address 10.10.10.13
!!! modification not allowed, finish the unconfig
Chassis 1 address is current 10.10.10.11 which is the WLC-2's IP address. I need this changed to 10.10.10.12.
Hope you can help.
Thanks
Anthony.
Solved! Go to Solution.
11-02-2023 04:48 PM
The only way to change is to go back. That means you would need to break HA and then change what you need to change and then establish SSO again.
11-02-2023 04:48 PM
The only way to change is to go back. That means you would need to break HA and then change what you need to change and then establish SSO again.
11-02-2023 04:50 PM
Thanks Scot, just did this and now have a HA-Pair.
It's been a long day :-). Thanks for your quick response.
11-02-2023 04:54 PM
No worries... if this is a new setup, you better just practice and get familiar with breaking SSO just in case you have to do that in the future. Best time to document your process also.
11-03-2023 01:19 AM
>...Thanks Scot, just did this and now have a HA-Pair.
- Good work , you can also verify RMI-IP reachability with (CLI) : test wireless redundancy rping
M.
03-31-2025 07:47 AM
Hello Scott,
What about a cluster of 2 x 9800 WLC configured without RMI but only RP.
If I want to configure RMI, do I also have to break the cluster in order to configure it ?
Thanks,
03-31-2025 09:14 AM
@aleopoldie ...If I want to configure RMI,do I also have to break the cluster in order to configure it ?
Even more then that ,you have to reboot both controllers simultaneously ,
Ref : https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/220277-configure-high-availability-sso-on-catal.html
>...
>Step 3. Configure redundancy with RMI + RP pairing type.
>...
>Step 4. Reload controllers.
>...For the HA pair to form and the configuration to be effective, both controllers must be reloaded at the same time once the configuration made at step 3 has been saved.
M.
03-31-2025 11:38 AM
100% @marce1000 reload is required just the sma as when you setup SSO.
04-01-2025 12:28 AM
Thank you for your answer @marce1000
Here is the action plan I had on mind :
- Break the cluster (I assume both WLC will have the primary IP address as WMI so I would have to change the WMI's IP address of the secondary WLC to avoid IP conflict,
- Reconfigure SSO with RMI+RP,
- Reload both WLC at once,
Am I right ?
04-01-2025 01:25 AM
- @aleopoldie Looks good , before rebooting : validate the configuration of the active controller with
the CLI command show tech wireless and feed the output from that into Wireless Config Analyzer
And you may want to do that also , after the standby controller has booted again ,
M.
04-23-2025 01:47 PM
I am running into a similar issue. I have 2 working 9800-80 controllers, we moved to another site/subnet. Before giving them an uplink or connecting them to form an HA pair I tried to use the CLI but it allows no typing in either of the controllers. I rebooted the controller and do see the startup process roll across the window but when I try and type anything after the message "press enter to start" it does nothing. Baud rate was 9600 but found a document to change it to 115200, which I did but it doesn't make a difference, same outcome.
I was finally able to get into the GUI of the primary controller by putting my laptop on the management IP subnet. I made some changes in the GUI CLI and now have access to the mgmt IP address on the network.
During the troubleshooting process I tried to run this command to change the IP of 2nd controller to correct IP/vlan "redun-managment interface vlan96 chassis 1 address x.x.x.x chassis 2 x.x.x.x" but received the error modification not allowed, finish the unconfig
Putting my laptop in the same subnet for controller 2 does not give me access to the GUI.
How can I enable the CLI for both controllers?
I did go ahead and plug in the cable to make them a pair and they paired up, but controller #2 has the wrong IP. Do I need to turn off redundancy --Administration>Device>Redundancy and then reboot to break the HA pair?
Thanks for any guidance!
04-23-2025 11:36 PM
- @leccles >...Do I need to turn off redundancy --Administration>Device>Redundancy and then reboot to break the HA pair?
I would prefer to go that way, perhaps clearing the configuration on the former standby too. And configure HA SSO again with your parameters. Note that CLI access should always work because it is essential for controller management.
(https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/220277-configure-high-availability-sso-on-catal.html)
===>Always validate the configuration of the active controller afterwards with
the CLI command show tech wireless and feed the output from that into Wireless Config Analyzer
M.
04-01-2025 08:01 AM
Make sure you have console access, you can always break the SSO cluster and then shut the ports on the switch that the standby is connected to so that you will not run into any duplicate ip address when they both come back. Then you can change the management ip and no shut the ports.
04-14-2025 04:40 AM
Hello Scott,
Following this documentation, I think it is possible to enable RMI without breaking the cluster, isn't it?
I mean, going on the 9800's GUI, under the Redundancy menu > click on RMI + RP, set the 2 RMI IP addresses and apply ?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide