06-25-2015 08:30 AM - edited 07-05-2021 03:28 AM
Hi Team,
I am having issue for getting APs on cisco wireless lan controller,
Let me explain,
I am having 2 wlcs,primary and sec,
the sec wlc just received from cisco,its brand new
i configured new wlc like primary wlc i have at site and working.
and during testing ,i removed primary wlc from lan,and this momnet all APs should shift to new secondary wlc,it is not working here
all APs are having primary and sec wlc s addedd
i do see AP s on new wlc but not getting DHCP ip address and the aps are not stable on sec wlc
Here is the details
Primary WLC software ver:4.2.130.0
new secondary wlc:6.0.202.0
I am not seen "LWAAP transport mode" option on secondary wlc under controller tab
At this stage i thought i need to chnage software verison and make similaer like primary for sec wlc
i tried below and received error ,see below,
so my queries?
a) Is it required to chnage software verison on new wlc as match to primary wlc?
b) Is it also required to change " bootloader version" on new wlc?
c) Wht is the correct file for bootloader? for the new wlc?
(NGBO1WLCMDF02) >transfer download filename AIR-WLC4400-K9-4-2-130-0.aes
(NGBO1WLCMDF02) >transfer download start
Mode............................................. FTP
Data Type........................................ Code
FTP Server IP.................................... 10.208.253.100
FTP Server Port.................................. 21
FTP Path......................................... ./
FTP Filename..................................... AIR-WLC4400-K9-4-2-130-0.aes
FTP Username..................................... NOC
FTP Password..................................... *********
This may take some time.
Are you sure you want to start? (y/N) y
FTP Code transfer starting.
FTP receive complete... extracting components.
Failure while validating the signature!
FTP Failure while storing in flash!
(NGBO1WLCMDF02) >
06-25-2015 08:56 AM
a) Yes if you don't have the same version then when the APs failover they will need to download the other WLC's version and then reboot before being usable. The same will happen when they fail back.
b) No
c) I wouldn't worry about the bootloader at this stage.
The reason your FTP failed is you're trying to install an image for a 4400 on a newer WLC model by the looks of it.
Are the APs not getting DHCP because the scope is not on the secondary WLC? Is there an IP Helper needed on your switch with the secondary WLC referenced?
06-25-2015 09:09 AM
Thank you,
For FTP:"The reason your FTP failed is you're trying to install an image for a 4400 on a newer WLC model by the looks of it."
i tried GUI and same,then i tried cli and still same,
i am having external FTP server and code file on it
how to resolve this FTP issue pls? is it due to no free space available to store code?
if yes
how to see free space on wlc in cli? and delete it?
What are your recommadation?
how to come over this 2 issues? below
Failure while validating the signature!
FTP Failure while storing in flash!
Thanks again
06-25-2015 09:12 AM
I think you're misunderstanding...your filename -AIR-WLC4400-K9-4-2-130-0.aes is a file for a 4400 WLC. If you've received a brand new WLC from Cisco it cannot be a 4400 therefore you need a software version for the new WLC and there is not going to be a version 4.x.x.x.aes for a new WLC.
06-25-2015 11:01 AM
Thank you Andy,
so now i am thinking in other way,
i will not go for changing the version on this new wlc.
what is the equivalent option for "LWAAP Transport mode"? on new wlc
i am not seen this option on new controller under Controller tab in GUI.
But this option i see in my primary wlc.
06-26-2015 01:19 AM
This option is not in the later versions. Before you could have the APs in the same network without an IP address and then you didn't need an AP manager configured. Now, give the APs an IP address or DHCP and then they talk to the controller on the management interface using L3.
06-26-2015 06:27 AM
Thank you Andy
I will try few option here
06-26-2015 02:57 AM
04-02-2018 07:45 AM
This gives an overview of the Wireless LAN Controller (WLC) Discovery and Join Process. This document also provides information on some of the issues why a Lightweight Access Point (LAP) fails to join a WLC and how to troubleshoot the issues.
https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: