Cisco :: Controller Unreachable In WCS 7.0.172.0 After Code Upgrade?
Sep 13, 2011
I have one instance of WCS 7.0.172.0 (on a Linux host) and a fleet of WiSMs that I'm upgrading from 7.0.98.0 to 7.0.116.0. 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 am getting an alarm on WCS where a one controller is down, unreachable from WCS, while the other one is reachable on the same WiSM module. Upon investigation, Status of controller is shown as "Oper-Up" for all controllers on Supervisory engine. Hardware platform is Cisco 6509-E.
WLAN Slot Controller Service IP Management IP SW Version Status ----+-----------+----------------+----------------+-----------+--------------- 2 1 192.167.10.11 172.19.47.65 6.0.196.0 Oper-Up 2 2 192.167.10.12 172.19.47.66 6.0.196.0 Oper-Up
However, I can not ping the managment interface of the down controller while the other controller management interface is pingable. All these interfaces are in the same VLAN.
ping 172.19.47.65 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.19.47.65, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
Problem is fixed when I reboot the problematic Controller. However, this problem re-appears after some time. I am not able to figure out why controller is not able to ping its default-gateway which is an SVI interface on Supervisory card on the same chassis, and showing status UP/UP. Is it a software bug or backplane fault or any other reason ?
I'm having an issue where when I upgrade from 8.2(5) to 8.4(2) on an active/passive asa 5585 running in transparent mode I can no longer reach the standby ip. The BVI interface appears to be created properly, the device IP and standby IP are listed in the config under the BVI interface and my inside and outside interfaces are both joined to BVI1-group.
I am having a Wism on 6500 chassis with software code 7.2.103.0 Now......... I use to have 7.2.111.3 on the Wism before but for some reason I had to downgrade the code to an older version (some compatibility issues with the NCS)......
Now before all the APs were having 7.2.111.3 version running as soon as I downgraded the controller IOS most of them downgraded the code but a few still did not show up...... so I picked one of them and did a factory reset on the AP and was guessing that it might get the new code from the controller this way but unfortunately since than I have tried a lot of things but no luck. I have switches configured on layer 3..... other APs connected to this switch are working fine,........ when I reset the AP to factory default it doesnot take an IP obviously so I manually define the IP,,, you would find that configuration below too.... but than after a while it trys to locate the controller and could not find it.... where as, as i said other APs on teh same switch works fine......
the only thing i notice is that it does not release the IOS .. it is still having 7.2.111.3.....
using MCNG ddr static values from serial eeprom ddr init done Running Normal Memtest... Passed. IOS Bootloader - Starting system.
I have 2 4402 WLC running 7.x.x.x code. I also have some 1510 Mesh- L WAPs that require an old version of code. I need 4.1.192.22M for those. Is it possible to bring up a 3rd controller running this old code with the other 2 4402's running modern code? What will break? I know that anchoring and mobility might get messed up. What are the other caveats?
Any chance the filtering features on the 5508 controller code will make it into WCS at some poiint? Being able to sort these lists would be invaluable.
I just upgraded a stack of 4 3750s from 12.2(53)SE2 to 15.0(1)SE2. The stack took awhile to come back online (about 20 min). I wanted to make sure this isn't a compatibility issues with the Boot Loader which is (C3750X-HBOOT-M) Version 12.2(53r)SE2, RELEASE SOFTWARE (fc1).
I have a Cisco 1841 running IOS Image C1841-advsecurityk9-mz.124-3i and the following feature sets: IP, Firewall, VPN, IPS and NAC. I am having an issue viewing the Additional Task tab under the Configure menu in the GUI. Without doing much research i assumed this is an browser issue and new code would fix it. When i look on the download software there are many different codes availible and i am unsure which i need to get to update the software on my IOS.
Here are the ones i am look at and not sure which one to choose from.
I am planning to upgrade the WLC code and I have about 133 RAPs/MAPs/1131 APs that already joined the WLC. Will I have a problem with my MAPs when the WLC starts upgrading the code. Some MAPs will have 3 hops to connect to a RAP.
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.
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?
i'm going to upgrade a 5508 wlc code from 7.0.116.0 to 7.1.91.0 to add 3600 series access points having it all manageable via WCS ver 7.0.230.0 it seems to be possible, as it is explained in the compatibility matrix found on [URL]now I have to download the file to the controller...
before doing that I'd like to know if I will loose my configuration on the controller i'm concerned about that because the release document is not clear:
- We highly recommend that you back up your controller's configuration files prior to upgrading the controller software. Otherwise, you must manually reconfigure the controller.
- For busy networks, controllers on high utilization, or small controller platforms it is advisable to disable the 802.11a/b/g networks as a precautionary measure.
- Step 5 Disable any WLANs on the controller. - Step 19 Re-enable the WLANs...... - Step 22 If desired, reload your latest configuration file to the controller. (reload config after reenabling wlans?another controller another question .....: a cisco wlc 2100
I am looking to upgrade a 5510 that is currently on code version 8.0(4) to code version 9.1. I know I will have to upgrade to 1gb ram, but can i just upgrade straight to version 9.1 or do I need to follow an upgrade path? This is a standalone device so I am planning on downtime.
I am facing an issue with several ACS appliances (some other work well) when upgrading to version 5.2.0.26.8.
When I launch the command acs patch install, I receive the following error message (we use FTP):
Failed to copy file '5-2-0-26-8.tar.gpg' from repository PatchRepository (Error -302) % Error: patch install 5-2-0-26-8.tar.gpg from repository PatchRepository - transfer failed (code 1)
This happens on three appliances but I could successfully upgrade 4 other appliances.
What is the reason behind this error code ? What could I do solve it ? I have already tried to create another repository on another server, without success.
I have a wireless controller that works perfect but because we have some new access-points 1602i that is only supported bij software version 7.4.100.0. So I need to upgrade the controller because I now have version 7.0.116.0. I have read in release notes of version 7.4.100.0 that I first need to upgrade to 7.0.240.0 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 7.0.240.0, we recommend that you upgrade to the 7.0.240.0 release and then upgrade to 7.4.100.0 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 1.8.0.0-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.................................. 7.0.116.0Bootloader 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 7.0.240.0 3. Test and backup the config 4. Upgrade to version 7.4.100.0 5. Test and backup the config 6. Upgrade Field Upgrade Software 1.8.0.0 7. Test
A customer has wireless LAN controller with version 4.2.205.0 and i want to upgrade it to version 7.do i need to upgrade the controller to intermediate version or i cant directly upgrade it.
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 7.0.98.0 to 7.0.220.0. Reason being, we have experienced a lot of access points disassociating from the controller as well as client authentication issues. Upgraded from 7.0.98.0 to 7.0.220.0 and any issues during the upgrade or after the upgrade?
I have been searching through the cisco docs for a while and i just cant seem to find this info. Can I run aironet 1600's with my wism running 7.0.116? Also, could I run my 1130 series ap's with a wism2? Basically, what is the minimum code level for a lightweight 1600, and what is the maximum code level for a lightweight 1130?
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,
[URL]
Console Boot Log. Xmodem file system is available. flashfs[0]: 9 files, 3 directories flashfs[0]: 0 orphaned files, 0 orphaned directories flashfs[0]: Total bytes: 15998976
[code]....
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.
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?
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 have a 5508 wireless controller running version 6.0.199.4 (the image installed when the device was shipped) and I am trying to install by tftp version 7.3.112.0
The issue is when using tftpd32 gets to 82% transfered then fails with the error "% Error: Code file transfer failed - Error while writing output file"
I should upgrade ASA 5550 with nat controller enabled, from 7.2 to 8.x, I've been reading nat is differently configured up from release 8.3. So I choosed to upgrade to 8.2 release.
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
We have Cisco 4402 Wireless Lan Controller with Software Version 3.2.171.6 and we want to upgrade it to latest version.
What is the latest version to upgrade the WLC?
Also since WLC is running on very lower version is it possible to upgrade to the latest version directly or we have to move it step by step to upgrade this to latest version?
I have a 5508 controller, just upgraded from 6.0.182 to 7.0.98.0. 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...)
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?
