Issue with configuring management ethernet port for WLC 9800-40

[kmart1287]

Hello,

I am a Junior - Intermediate level Network engineer.

I am currently trying to configure our 9800 WLC management Ethernet ports purely for SSH purposes. We have 2 WLC 9800-40 running HA.

I am looking for guidance or ideas on how to configure the primary and secondary management ports to have different IP address. I believe this was easily possible upon configuring out of the box, but it was not deployed this way.

The thing is I cant find a way to separate these management ports because the controllers share the configuration. When I make a change it reflects on both WLCs. So when I configure the Primary WLC to have an management ip of 10.x.x.1, it is also configured on the secondary and vise-versa. I am trying to find a way to accomplish the task without breaking the HA.

Things I have tried -

-I have tried to console in directly to the secondary
-Tried forcing a switchover and configuring the secondary with a different management IP address, but then the configuration is reflected on the primary as well.
-

any help or ideas is greatly appreciated.

[balaji.bandi]

You start with the video :

https://www.youtube.com/watch?v=UhZedbZ1pIA

https://www.youtube.com/watch?v=sff26rgzY_I

For HA look at the below guide : (this is for reference, depends on code you using use appropriate steps)

https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213915-configure-catalyst-9800-wireless-control.html

[marce1000]

 - The  idea of HA is that the controller appear as a single entity ,hence there is only one management address , for configuration reviews and or advisories use  the CLI command : show  tech   wireless , have the output analyzed by  https://cway.cisco.com/tools/WirelessAnalyzer/  , please note do not use classical show tech-support (short version) , use the command denoted in green for Wireless Analyzer.   

 M.

[Rich R]

@marce1000 is correct - think of 9800 SSO HA a bit like a switch stack.   The management IP is for the cluster not a specific chassis.  Whichever chassis is active will 'own' and respond on that management IP.