we have Scheduled an Upgrade for 2 of our WLC Controllers 4402 From Software Version 6.0.182.0 to 7.0.235.3 Version.
I Have gone through the Cisco Docs for the upgrade procedure, I have an Doubt, When i Downloaded the WLC software 7.0.235.3 , I found another software (Cisco Unified Wireless Network Controller Boot software )
I have Previously Done upgradation from 6.0.182.0 to 7.0.220.0 , but i have not yet remebered uploading the boot Software for upgradation.Boot software also Required for upgrading the Wireless controller ?? Whats need of this software?? OR only Main software is enough for upgradation?
I tried to upgrade the cisco boorloader pf WLC 4402 from version 4 to 7.2. I updated ER.Aes FOR 7.2 (EARLY RELEASE.aes). It was updated perfectly and then I rebooted controller....now i can only see blank screen from connected console.I tried the flash of other lan controller but its not working because the issue is in the ROM as the boadloader file is in the ROM which is corrupted now i want the solution to upgrade the boatloader file inside the ROM.
I wanted to upgrade our three WLC 4402 from software version 5.0.148 to 6.0.202.0. The upgrade on the first controller was working. Unfortunately he lost all the local management users and it's MAC filters, but restoring this was not the problem. After upgrading the second controller.... the device does not boot anymore! The alarm led is RED and I don't know what to do. The only way to get connected to the controller is via the console port. There I can see a "parse error" but I don't know if that is the problem. Please look at the "log" attached. I'm not sure if the red alarm led was there before upgrading the controller software because the device is located to another place. I'm really concerned about upgrading the third controller because it's the most important wlc.
We are trying to upgrade throughput on ACE appliance 4710, getting below mentioned Error. We got license file from Cisco first license is for 0.5 to 1g, 2nd 1g to 2g and 3rd one is for 2g to 4g.
Our environment is critical, hence we are doing upgrade on Secondary appliance first. for that we are first isolating Secondary appliance by disabling up link switch port.
ACE-Shared/Admin# license install disk0:ACE20121016124306914.lic Installing license... failed: Can't install this license with the current count [code]...
I have 2 4402 WLC's and am in the process of deploying 1042 APs out to sites. But The AP's wont recognize the WLC. I have configured the DNS for CAPWAP but still no dice. I have had to serial into each unit and give it a static IP and then I can see it on the WLC. Shoulsnt this be automatic?
Any explanation about this warning from the WLC4402 after the software upgrade to 7.0.96. version? this is the message: Warning: WLC has detected its IP add xx.xx.xx.xx being used by a machine with MAC add xx:xx:xx:xx.and the MAC add found is the the mac add of the dynamic interface of the WLC.
My WLC running 6.0.182.0 suddenly could not accept more than 47 APs! Ihave a 1240 trying to join but failed with no obvious reason (no special errors in debugging).
I unplugged one of the joined and the first one joined!! I replugged the second one but could not join!! I unplugged the first one and replugged the second one: the second joined the controller but the first could not associate again!
Can 3600 series model AP work with WLC 4402 with existing license, we purchased 25 LIC pack and still using only 15. Any recommended Part no on 3600 series with external Antenna
We have two cisco 1262 AP and a 4402 WLC, the AP cannot join the WLC. The AP gets the address from dchp
I cannot ping the AP address from the WLC, but i can ping the default gateway and other VLAN addresses.
I already read the info on the this link : [URL] Still our AP cannot join the WLC no matter what i have tried.
Setup
- VLAN setup on a Cisco 3560 48 port poe Switch - tunk configured btwn the Gi Interface and the Management physical port - WLC mode is configured for Layer 3 - AP Manager and Management are in the same Subnet - Option 43 is configured for the with the AP Manager's IP address - Opotion 60 is also configured with AP Manager's IP address - the port connected to the APs are in the AP Manager VLAN
Our company has a customer with a Cisco 4402 WLC and a code version of 4.2.130.0 . The customer wants to upgrade the code to 7.0.230.0. Is there any flash size requirement when upgrading to 7.0.230.0? (upgrade train: 4.2.130.0 ----> 4.2.209.0 ----> 7.0.230.0), How can I find the flash size?
We got WLC 4402 running software 7.0.235 and would like to backup the configuration and restore on 5508. Is this doable? Do we need to be on the same version as WLC 4402. How to get cisco document to follow the steps if the above is doable,5508 is new with no setup.
I need to install one 5508 and a 4402 together to bring redundancy to a wireless environment.Can I do this?. What are the neccesary steps to perform this?, the idea behind this is to bring redundancy is the primary WLC falls for any reason.
I have two wlc 4402 to control 50 AP 1131. 2 WLC: wlc-01 and wlc-02, wlc-02 config as backup wlc in the same mobility group. Client authentication:EAP with Microsoft IAS/AD.All AP have joined wlc-01. Wireless client work well with wlc-01.For testing I config access point AP01 have primary wlc: wlc-01, secondary: wlc-02 If I change config of AP01 like this: primary wlc: wlc-02, secondary: wlc-01. Client is hard to connect to wlc-02 and it only connect when client set static ip ALL wlc run this softwar image: 7-0-98-0 Should I send wlc-02 to warranty service?
I have WLC 4402 working with AIR-AP1131AG-E-K9. Need to buy another pair. I looked to the side air-ap1041n-e-k9. Tell me whether or not the compatibility of the controller and the AP1041n? One more question. When buying in 1131 is still in the box and power cord to the point. The new 1041, the purchase comes with the point of the power cord?
I am trying to setup a Wireless Network on my WLC that is totaly independent of our internal LAN. Port1 is designated at the .14.0 network and Port2 is the .18.0 network. The 14 network (Port1) will be the guest and 18 network (Port2) the internal wireless.
The issue i am having is nothing is routing to Port1. I have the Guest Wireless set to get DHCP from the WLC and i can get an address but i cant get internet access. I tried configuring a Network Route but it will only let me set the service port as the Gateway and not the IP for Port1.
I am running software version 5.1.151.0 and using this guide as it is the only one i can find. [URL]
We are attempting to use LDAP for web authentication on a WLC 4402.
[URL]
You are able to connect to the SSID and it reidrects you to the login page as it should. When you enter your username and password you get a message that "the username and password combination you have entered is invalid." Based on the following log it looks like the LDAP bind is the issue.
*LDAP DB Task 1: Dec 19 11:19:26.584: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1038 Could not connect to LDAP server 1, reason: 1005 (LDAP bind failed).
We are able to test the following configuration with ldp.exe successfully,
Server: ***.***.***.*** Port Number: 389 Bind Username: CiscoBYOT
My customer has a 4402-25-K9 and need a backup (failover) controller to avoid data transmision break when primary controller goes down.4402 are end of sale so I have a question can I use 5508 to get Controller Failover Protection with 4402 ?
I have an issue with AP Fallback not working with two Cisco 4402-50 WLC's. Here is the senerio:
Site 1 has a 4402 (WLC01) running software 7.0.220.0 with 48 associated access points. AP Fallback is enabled in Controller > General and all 48 AP's are set to Critical failover with WLC01 being the primary controller and WLC02 (at site 2) being the secondary.
Site 2 is the location of WLC02 which is also running software 7.0.220.0 but has 0 ap's associated and also had AP Fallback set to enabled.
Your typical active/passive setup
The problem is when WLC01 goes down all of the AP's fail over to WLC02, however when the connection is restored to WLC01 we have to manually reboot each access point in order for them to reassociate back to the primary controller. Isn't AP Fallback enabled suppose to allow the AP's to move back to the primary controller once connection is reestablished?
I ##have a customer with WLC 4402 in use, running software version 7.0.98.0, and supporting 11 APs at present. The customer wants to enlarge the WLAN, which involves increasing the number of APs. I #####have purchased a new WLC5508, and have installed it onto the network alongside the 4402. the 5508 is running software version 7.0.116.0. Because the wireless network is critical to the user, we want to move the APs over to the new controller while the network is up and running, then remove the 4402.
However, when we set the 5508 as the master controller, or tell one of the APs to use the 5508 as its primary controller, the AP connects to the new controller, downloads the new software version, attempts to load it but reports an error with the unzipped file size of the software and fails to boot. formatting the flash on the AP, then disconnecting the 5508 from the network and rebooting the AP allows it to connect to the 4402, it downloads the older software and boots as normal. A new AP, if connected to the 5508 in a test scenario (ie no 4402) connects, downloads and boots perfectly.
I #have the upgrade software to allow the 4402 to be upgraded to 7.0.116.0, but I am concerned that, if this is installed, the existing APs will then fail to boot from the 4402 or the 5508.all APs are 3502s, running IOS version 12.04(23c)JA when connected to the 4402 and 12.04(23c)JA2 on the 5508.
We have two WLC 4402 WLC in active-active mode in our setup. The issue we see is that a user/laptop gets connected and gets the ip address but there will be no network access. We see a yellow exclamation sign at this time in network icon in tray and we can not ping gateway at this point. We have run debugs at this time for the machine and we could see that was in "RUN" state its only that the machine can not access network.
I 'm trying to upgrade WLC 4402 up from 5.1.151. After upgrade to 5.2 or higher https interface is inaccessible. If I use any other previous version, all is OK. Somewhere I found recomendation to open http before upgrade and use it at first. It works, but what to do next? To stay on http only?
my client claimed that right after thry upgraded their WLC 4402 to version 7.0.220.0 from the version that came preinstalled (factory) the can no longer console into the device. They were able to console into the 4402 before the upgrade but now they can't. I'm thinking that maybe they upgraded straight to the new version and didn't verify to see whether they were allowed to upgrade directly to that version 7.0.220.0 or if they needed to upgrade to a intermediate version , the proceed to upgrade to the 7.0.220.0.
WLC-4402-25-K S/W - Primary and Secondary Controllers were running 4.2.130 to begin with. Customer upgraded remotely using NCS - Primary to 4.2.209 and then to 7.0.230 and all that went fine and is in Production.
Then customer upgraded Secondary also using NCS also from 4.2.130 to 4.2.209 in preparation to upgrade to 7.0.230 and he lost contact with the controller. Sent a technician to site to troubleshoot by connecting to Serial Port. Technician #ESCAPED out of the boot sequence and from the BOOT MENU tried to boot the Primary Image and it failed with CRC error on Flash. He then tried to boot the Backup image and had the same problem. He then tried to manually load 7.0.230 - ER (Boot Software) using TFTPD32.EXE and that went fine. He then tried to load 7.0.230 "aes" S/W - The big over 70 MB file and went through most of the file transfer but failed saying:
ERROR: Transfer Failed.
TFTPD32.EXE said something like "Data Packet too Short or some such thing". Sorry did not write down what TFTPD32.EXE said.
Then we thought "may be" a power cycle of the unit is required after the ER Boot Loader Image was loaded. When we did that the unit died. That is - no communication with the Serial Port. We don't think we have any choice other than RMA - Do we?
Customer says he did read and follow this link - especially Table 10-1. {URL}. He said he used NCS to do the Upgrade. I a not familiar with NCS.
we have a two port 4402 WLC here with only one port currently in use. The topology is bacically the used port uplinks to a dmz switch. Our Intranet and the Internet are accessed via an ASA from the WLC. The WLC also sits in the DMZ. This WLC is only used for guest wireless access. The AP information and traffic is exchagned from a primary WLC on our Intranet and authentication is done via RADIUS. Internet access is handled through the ASA as well on the DMZ. We have a completely independent ISP broadband connection here that was put in long before I was ever here and is used for guest wired web access. All ports are clearly labelled and have bright pink patch cords. What I would like to do is have our wireless guests be on that network rather than our dmz for their web access. I have pulled an ethernet cable from the switch that connects to that broadband connection to the cabinet with the 4402. So the physical is fine right now. I'm not all that familiar with the WLC's, so I'm not sure if everything else can remain the same as it is right now, but just connect the second port to the broadband connection and route guest Internet traffic through there rather than the DMZ.
