wave2 controller, unable to change wlan interface.

[Chris McCann]

Hi Folks,

I have a wave2 controller. I have a guest wifi that is currently using the management interface. I want to change the interface to use the correct one I have created for the guest wifi however every time I do this I get the below error.

The following errors occureed while updating the wlan: request failed--interface ip address is not a valid ip address.

The interface doesnt have an ip address but I have several others which dont have an ip address either and work perfectly well.

Also the above config is currently working fine, ip addresses of clients is correct (using windows dhcp server).

Can anyone shed any light on why I cant change the interface.

regards,

Chris.

[Mark Elsen]

  - @Chris McCann                 Provide the exact controller model and software version used on it.
                                              + What ip address are you trying to use ?

  M.

[Chris McCann]

Hi Mark,

PID: AIR-CTVM-K9,

Software is 8.10.185.0

However I think I see what is wrong. If using an ip address in there (currently blank). Can I use an IP within the scope of the clients for that WLAN? In theory I suppose the IP wouldnt be used for anything?

regards,

Chris.

[Mark Elsen]

    - @Chris McCann                  AIR-CTVM-K9 =  a very old platform which is no longer supported
                                                                             The rest of your answer is a bit confusing.
                                                 Perhaps post a screenshot with what you are trying to do and the
                                                 resulting error message,

    And you should always use the last/latest version for aireos controllers :
                         https://software.cisco.com/download/home/284464214/type/280926587/release/8.10.196.0
    to have the last and ending bug fixes for the platform

  M.

[aleabrahao]

Is the interface a Dynamic Interface?

For a WLAN, AireOS expects the mapped interface to be a dynamic interface with VLAN ID, IP address, Netmask and Gateway configured.

Even if client DHCP is provided by a Windows DHCP server, the interface itself normally still requires a valid controller-side IP address. The reason your WLAN currently works on the Management Interface is because the controller is sourcing traffic from the management interface, which already has an IP.

[aleabrahao · Accepted solution]

Another point, why do you want to use a different interface? The operating mode for SSIDs on the Virtual Controller is FlexConnect, so the client receives an IP based on the VLAN mapped to the SSID, the interface used is irrelevant in this case.

[Chris McCann]

Hi Aleabrahao,

I think what you mentioned above is the type of answer I was hoping for. That the interface is irrelevant as yes we are using flexconnect.

thanks,

Chris.