I have quick question about wlc software version upgrade : currect version of 5500 WLC : 184.108.40.206,However i am planning to upgrade to version 220.127.116.11,currectly all remote site AP's are connected to this WLC , nearly 150 AP's all are in H-reap mode however once i upgrade to 18.104.22.168 version , all default should come into Flexconnect mode.Do i need to make any configuration or any changes in AP's to get Flexconnect mode or will it be default mode as Flexconnect mode in new version of WLC ?
upgrade on the wireless controller 2504 from 7.0 to 7.4 is direct upgrade.My customer faced problem by upgrading the software 7.0 to 7.4 directly and the image hang.how should proceed recover the image 7.4/
We are looking to upgrade our 5508 wireless controller from 22.214.171.124 to 126.96.36.199. Reason being, we have experienced a lot of access points disassociating from the controller as well as client authentication issues. Upgraded from 188.8.131.52 to 184.108.40.206 and any issues during the upgrade or after the upgrade?
I have an AIR-AP1242AG-E-K9 which had c1240-k9w8-mx.124-21a.JA loaded, I followed the link below and upgraded with Cisco’s upgrade tool to c1240-rcvk9w8-mx with no problems at all, after the upgrade I could then see the LWAP on the 4402 controller and had it working a treat.Now the problems begin, I brought it into the office where we have 5508 controllers, plug in the LWAP into our management switch and boot it up I get an IP assigned from the DHCP server and the AP goes into discovery mode but never finds the controller.I have logged the boot process but this does not give much away, our other 1100 series AP’s boot fine,
Console Boot Log. Xmodem file system is available. flashfs: 9 files, 3 directories flashfs: 0 orphaned files, 0 orphaned directories flashfs: Total bytes: 15998976
And that is where she sits and does nothing more, I have noticed the DNS problems but the other 1100 series LWAP’s boot up after show that same issue.
Any online 2504 controller crash after upgrade to the point where even console port does not put anything out? Perfectly working 2504 running 7.0.116 ran upgrade through web GUI to 7.2. GUI showed perfect transfer, save etc... Asked for save before reboot. Select yes. Controller reboot and now it sits with following status lights:Power-greenSYS - amber blinkingALM - amber solidNothing out of console.
I am in the midst of trying to update the controller firmware of a cisco wireless lan contoller 4402, and having some issues getting the file to transfer to the controller. i am currently running verison 5.0.148 on the controller and attempting to upgrade to the latest version of 7.0.230 and for whatever reason it continues to not transfer. I have tried all 3 methods of cli, gui and using wcs software. all the no avail , I have tried tftp32 and 3cdaemon with the same results.
The error that i am getting from 3cdaemon is got socket timeout aborting code 10054, failing at 66MB transfered. I increased the timeouts both on the wlc and the tftp client to no avail
the error i get on the wlc is Code file transfer failed - Error while writing output file
I have a 5508 controller, just upgraded from 6.0.182 to 220.127.116.11. Also LAG was switched off directly after upgrade.
Since the upgrade none of the 1142 LAPs are associating with the controller. I can see they are being issued IPs by the internal DHCP but putting a console cable and watching I am getting:
Not in Bound state. *May 4 11:41:17.759: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !! *May 4 11:41:17.759: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
One Ap prior to the upgrade was on a static IP and that connected through without any problem, (it was an 1131 though, but I dont think that is the issue...)
I have two Windows 7 computers and neither one will successfully upgrade a 1242 AP to LWAP. However, I go to a coworker's XP machine and run the tool without issues. On Windows 7 I keep receiving the error message of ACL or Firewall is blocking. I have added rules and then even tried disabling the firewalls completely on both computers and still no success.
Region : Others Model : TL-WR1043ND Hardware Version : V1 Firmware Version : 1.8 ISP :
Region : Israel Model : TL-WR1043ND Hardware Version (On the back cover): V1.8 From web interface: Firmware Version:3.13.4 Build 110429 Rel.36959n Hardware Version:WR1043ND v1 00000000 ISP : Free
1. about USB Printer Controller
I connect my printer HP office jet 5610 All in one, his drivers installed on my computer (windows 7 ultimate, 32 bit). Irun the software "USB Printer Controller" and i didn't seeing anything. Can not click on any button. BTW, i changed the IP range from 192.168.1.1 to 10.0.0.100-10.0.0.139 and my router web interface at 10.0.0.140, if it's changing something.
2. About upgrade the router's firmware, it's safe that I'll upgrading it?
I have a wireless controller that works perfect but because we have some new access-points 1602i that is only supported bij software version 18.104.22.168. So I need to upgrade the controller because I now have version 22.214.171.124. I have read in release notes of version 126.96.36.199 that I first need to upgrade to 188.8.131.52 to avoid losing those VLAN settings.
Note If you have VLAN support and VLAN mappings defined on H-REAP access points and are currently using a 7.0.x controller software release that is prior to 184.108.40.206, we recommend that you upgrade to the 220.127.116.11 release and then upgrade to 18.104.22.168 to avoid losing those VLAN settings.
But I also read something about Field Upgrade Software. If you are using a Cisco 2500 Series controller and you intend to use the Application Visibility and Control (AVC) and Net Flow protocol features, you must install Wireless LAN Controller Field Upgrade Software for Release 22.214.171.124-FUS. This is not required if you are using other controller hardware models. For more information, see [URL] .....
Here is the system information of my controller: Manufacturer's Name.............................. Cisco Systems Inc.Product Name..................................... Cisco Controller Product Version.................................. 126.96.36.199Bootloader Version............................... 1.0.16Field Recovery Image Version..................... 1.0.0Firmware Version................................. PIC 16.0 Build Type....................................... DATA + WPS System Name...................................... WIFI-WLC-01System Location.................................. System [Code] ....
I was thinking of the following steps: 1. Backup the current config 2. Upgrade to version 188.8.131.52 3. Test and backup the config 4. Upgrade to version 184.108.40.206 5. Test and backup the config 6. Upgrade Field Upgrade Software 220.127.116.11 7. Test
We are trying to navigate the waters in choosing between a in-house, controller-based, wireless network solution or a cloud-based solution. We have been presented with the usual suspects in cloud-based (Aerohive, Meracki, etc) and with Cisco (5500) and Aruba on the other side. We are a multi-campus organization with approx. 200 APs.Any hard reasons why go with a controller-based vs. cloud-based solution? If we must keep the conversation limited to Cisco, why go Meracki over Cisco's WLC solutions or vise versa?
I have one instance of WCS 18.104.22.168 (on a Linux host) and a fleet of WiSMs that I'm upgrading from 22.214.171.124 to 126.96.36.199. Every time I run thru the upgrade process from within WCS (scheduled to run overnight, off peak hours) all of the controllers that were upgraded then show as "unreachable". Grepping thru wcs-0-0.log shows messages that the controllers are unreachable via SNMP but running an "snmpget" from the command line to any of the affected controllers works just fine. The only way I've found to remedy this is to stop and restart the WCS service. Considering how long that takes with my deployment...I'd rather not do that every time .
I'm trying to upgrade the VDSL firmware on a 887VA. I've uploaded the file vdsl.bin-A2pv6C035d_d23j to the router. I understand this file has to be renamed with a .bin extension in order to be recognized after a reboot, but the attempts I have made have not worked. What must this file be renamed to in order to load the new firmware into the VDSL controller?
Here is the current firmware information. I've tried several of the obvious file names.
I'm about to upgrade a 5508 controller so I can do the pre-download to the access points, but in every doc I find, it says to disable the WLAN's before upgrading. This makes no sense. I'm just moving code over, why do I have to disrupt my wireless network in order to move code?
Is it possible to upgrade the CSACS-1121-UP-K9 to be a non upgrade part? We were going to upgrade from a Windows 4.x to the above Appliance (version 5.x) but there is now a reason to keep the old Windows version running therefore we cannot give the new Appliance the old ACS's licenses?!So we should have (with hindsight) bought a fresh version of the ACS 5.x rather than an upgrade.
I have two 5500-controllers and one WCS-server. Now I will have to move the WCS-server to another subnet and change the IP, but it will keep the name.Will that effect the connection between the controllers and the WCS?Do I have the change anything in the configuration on the controllers or the WCS-server?
I am working on a project that will involve 5500 controllers managing 1260 series N rate A/Ps. There may be a requirement for MESH but my previous experience using Motorola 802.11a radios is that random, intermittent radio detections resulted in the MESH network having to keep re-forming resulting in less than 100% availability.
What's peoples experience in the UK is 802.11a outdoors?
Ideally i would prefer to use 2.4GHz and repeater access points for those areas not serviced with data connection but I cant find any info' so far on how whether the 5500 controller is able to manage repeater access points.
While configuring a 5500 wireless controller, i came across this option of DHCP proxy under Advanced tab of Controller Option.It asks for the dhcp option 82 remote id format & the dhcp timeout.
1. What is the significance of this & when do we use it?
2. Also, under each wlan ssid that we create, there is an option of dhcp address required under the advanced tab. Do we need to use this option, if we are defining a normal dhcp pool in our controller for that ssid.
I have 5500 controller with firmware 7.0 installed from the factory. Due to some reasons, I understood that other existing wireless infrastructure runs on firmware 6.0, and hance i need to downgrade the 5500 series to 6.0 . During the bootup, i could see there is another image called backup recovery image, which is running on version 6.0. How can i reboot controller to use the older image , which is from backup recovery image. I couldnt find it in the configuration guide.
Is it possible to regain the PSK from the security tab from a 5500 controller in clear text?I need to check the current used password without resetting it, but I fail to find the password in the configuration (CLI & web interface)Obviously I do have admin access to my controller.
The Release Notes for 188.8.131.52 of WLC 5500 has a table which title is "Client Type", and it shows wireless adapters. My question is, what kind of customer means? Wireless clients or clients for an specific application? If it was the first option, does it mean tha just this adapters could connect to my wireless network?
i have cisco CAP 3602e series access point to work with 5500 series controller with code 7.0i did not find VCI option 60 for this type of APs to configure DHCP. How I can let these APs will join the controller, i mean through which process DNS discovery methode and what about if i need to configure option 60 and 43 in dhcp for ap joining process to controllers.
in one of the sites, the client has an exisiting 4402 controller which he moved to the DMZ in order to set it as an anchor & he purchased two new 5508 controllers to control the corporate APs. I configured all the parameters needed for the guest anchoring & then I tested the connection but there was an issue. (all the controllers are running the same firmware version)after testing the setup, the guest users could get an IP from the internal DHCP of the anchor controller (in DMZ), but then they cannot reach the internet or anything outside the anchor controller.Cisco confirmed that the 4400 is fully compatible with the 5500 to work in an anchor-foreign secnario as long as they are running the same firmware version. yet, when I temporarily used one of the 5500 controller in the DMZ as an anchor & I applied the exact same configurations on it as the 4400, it worked perfectly without any issues.
note: on the anchor controller (4400), the management & AP-manager interfaces reside on the same subnet & the wireless guest SSID is also mapped to the management interface. (may be this setup is causing the issue) but on the 5500 it is working just fine?