topic unable to SSH or HTTPS : wireless controller in Wireless

unable to SSH or HTTPS : wireless controller

jaheshkhan — Mon, 05 Jul 2021 17:38:06 GMT

Wireless controllers are in HA. recently client IT restarted primary WLC Then current secondary become primary and primary become secondary.

After this they cannot SSH or https to the current primary WLC.

current secondary is accessible through SSH.

What could be the reason? how to solve this issue?

Re: unable to SSH or HTTPS : wireless controller

omz — Sat, 29 Jun 2019 19:25:48 GMT

show redundancy summary output?

what does console output show the wlc that ssh is not working?

can they both ping their gateways?

check redundancy port?

reboot the wlc in maintenance window

Re: unable to SSH or HTTPS : wireless controller

Beazle — Thu, 20 Feb 2025 13:18:35 GMT

@jaheshkhan Did you ever find a resolution for this? I am facing a similar issue.

Re: unable to SSH or HTTPS : wireless controller

srimal99 — Thu, 20 Feb 2025 14:45:09 GMT

@jaheshkhan If you can access via ssh or HTTPS , check the port status and give a reboot see if that helps.Can you console to the controller and apply following command
show chassis ha-status local
show chassis
show redundancy
some useful links check troubleshooting guide:
https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213915-configure-catalyst-9800-wireless-control.html
https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/220277-configure-high-availability-sso-on-catal.htmlhigh

Re: unable to SSH or HTTPS : wireless controller

Beazle — Thu, 20 Feb 2025 21:11:59 GMT

The issue was that I put the service port on the same network that my pc uses so that I could do the basic config needed after we had to RMA one of the boxes. Then once it was installed we did not reconnect the service port. It seemed like it was trying to use the service port to respond to my requests because I was on the same subnet that the service port was configured for - even though the service port was not connected. Connecting the service port and then ultimately moving the service port to a different subnet resolved the issue.