1572 not showing Gi4 in Mesh tab on 9800 WLC running 17.12.3

[lecabral]

Hi,

After migrating a 1572 from an AireOS controller to a 9800 running 17.12.3 we noticed that when opening the AP configuration page, we see all interfaces, 0 thru 4, in the Interfaces tab, but we only see interfaces 0 thru 3 under the Mesh tab, hence we can't modify the interface configuration. Has anyone seen this and sorted out? Don't worry in suggesting to replace the AP with a newer model, that will happen but will take some more time.

 

Thank you,

LC.

[marce1000]

 - Everything the GUI offers can be done trough the CLI too , actually for the 9800 the CLI is the primary configuration tool,
   the GUI is only  a 'comfort tool'. So it could be a GUI bug , check if you can do it with the CLI.
   If you want to know which commands you need ; then checkout Find CLI commands executed by webinterface

                 Once you know the commands , you can try with the CLI,

 M.

[lecabral]

Hi @marce1000 thank you for your suggestion. I tried it, but unfortunately, the CLI also ignores the existence of Gi4:

myWLC#ap name my152AP mesh ethernet ?
0 Configures Ethernet Port 0 of the AP
1 Configures Ethernet Port 1 of the AP
2 Configures Ethernet Port 2 of the AP
3 Configures Ethernet Port 3 of the AP

myWLC#ap name my152AP mesh ethernet 3 ?
mode Mode of the interface Access/Trunk

myWLC#ap name my152AP mesh ethernet 4 ?
% Unrecognized command
myWLC#ap name my152AP mesh ethernet 4 mode trunk vlan native 333
^
% Invalid input detected at '^' marker.

So if we ever need to change something in Gi4, I guess we'll have to send the 1572 back to an AireOS, make the change, and send it back to the 9800.

[marce1000]

 - Ok, good option to try, yet the 9800 may change it's software image (again) when it joins. Not sure if there will be an impact,

 M.

[lecabral · Accepted solution]

As I mentioned in the original post, the 1572 was migrated from an AireOS WLC to the 9800 WLC and the Gi4 configuration survived the migration somehow. 

Thanks all for your comments.

[Rich R]

Aha so looks like you have found the best available solution for yourself - though far from ideal.  Evidently the AP is still retaining the base CAPWAP config from AireOS.

[lecabral]

This response was helpful, but should not be considered the solution.

[Rich R]

The 1572 is end of life, and almost end of support:
https://www.cisco.com/c/en/us/products/collateral/wireless/aironet-1570-series/eos-eol-notice-c51-743780.html
It reached End of SW Maintenance November 13, 2021 which means that since then "Cisco Engineering will no longer develop, repair, maintain, or test the product software".  So that bug in the GUI is not going to be fixed.

So @marce1000 is right - your only option is to try configuring it via the CLI.