Unable to Access Controller via HTTPS or SSH – Only Standby IP Ac

[athan1234]

Hi 

I am trying to access Controller 5500, but I’m having trouble because I don’t have access via HTTPS or SSH to the management or primary IP addresses. I only have SSH access to the standby (secondary) IP.

This controller has reached its maximum license capacity, and there are many access points trying to connect, so it might be overloaded or unresponsive.

I need to access it via HTTPS, but when I try to connect via SSH to the management or primary IP, I can reach the login prompt. However, after entering the username, it seems to freeze when I type the password, as if the controller is stuck.Do you have any suggestions for accessing it via HTTPS? Is there any way to manage it or run commands from the secondary IP, since I can access it via SSH?

[Rich R]

Correct - AIR-LAP1242AG-E-K9 is not supported on 8.5

[athan1234]

Therefore, I cannot proceed with the upgrade. I must keep the controller running on the current versionProduct Version.................................. 8.0.152.0

[athan1234]

I take advantage of this post to ask: I need to delete the DHCP pool on the controller, but some access points (APs) are currently getting their IPs from that DHCP pool. The idea is to assign fixed IPs to the APs. What is the best practice to do this? Should I first assign static IPs to all the access points and, once all of them have their fixed IPs, remove the DHCP pool from the controller? Or is it better to first remove the DHCP pool from the controller and then assign static IPs to the APs?

[Rich R]

Best practice is to use DHCP not static.
APs can fallback to DHCP automatically anyway if they can't find a WLC using static.
If you must use static then assign static IPs before removing DHCP.

[athan1234]

Yes, I know, but the project was originally designed with fixed IPs. Now, there are some APs using DHCP and they are getting their IPs from the controller’s DHCP pool. For this reason, I need to delete the pool and assign static IPs to all APs, just like the rest of the headquarters.Furthermore, we have only taken control of the controller and the AP. I cannot manage the customer's switches, and the AP's name matches its IP address

[eglinsky2012]

---

@athan1234 wrote:

Yes, I know, but the project was originally designed with fixed IPs. Now, there are some APs using DHCP and they are getting their IPs from the controller’s DHCP pool. For this reason, I need to delete the pool and assign static IPs to all APs, just like the rest of the headquarters.

---

Could you use DHCP reservations to ensure each AP gets assigned the same IP every time? If the WLC itself is providing DHCP to the APs, I don't think it's possible to make reservations on the controller, so consider running DHCP on another device/server if not. That way, the APs can continue to run DHCP while also maintaining the same IP addresses over time.

As for the original issue at hand, agreed with marce1000, sounds like your only choice at this point is to power-cycle the primary unit and the secondary will take over, and hopefully everything remains functional/accessible after. Once that's resolved, you can consider moving DHCP off the WLC and to a device or server that supports reservations. One thing at a time.

[Mark Elsen]

 - @athan1234   Assigning fixed addresses to APs is a VERY BAD IDEA! Not only does it become difficult to manage but APs  will also revert to DHCP when they cannpt find a controller! Stick to standard practices : APs must use DHCP with option 43 provisioned for the particular pool , so that they can find the correct controller,

 M.