Cisco Wireless :: Software Upgrade Of WISM / 4400 / WCS
May 4, 2013I want to upgrade software of the {WISM(Forign controllers 6.0.196) 4400(Anchore controllers 6.0.196) and WCS 5.2.0} to 7.0 code for all,
View 1 RepliesI want to upgrade software of the {WISM(Forign controllers 6.0.196) 4400(Anchore controllers 6.0.196) and WCS 5.2.0} to 7.0 code for all,
View 1 RepliesI want to upgrade all my controllers (a mix of 4400 and 5508) to 7.2.103.0 from 7.0.116.0. Can I make that jump or should I do incremental?
View 7 Replies View Relatedis there a way for pre deploying the new ap images? We have around 500 APs and my inspection windows isnt long enough to upgrade via controller......
View 6 Replies View RelatedI upgraded my WISM software to v. 7.0.116.0. The upgrade went smoothly. Most of my WAPs are H-REAP and they are working fine. I have a few local mode WAPs that are stuck in a downloading state. They will try to download, reboot, then try to download again. This is happening only with the WAPs in local mode. These WAPs were working before the upgrade.
View 2 Replies View RelatedI have to upgrade a couple of 4400s to support 1142 APs. The controllers currently support 1131s, and are on version 4.0.179.11. (I know, way back there...)
Seeing this huge gap between the level we're on and the most current version, thought I'd better find out what's recommended.
The available MD versions are 4.2 and 6.0
The available 4.2 versions are:
4.2.209.0(md)
[code]....
The next MD release is 6.0.202.0 .
We are currently upgrading from WISM-1's to individual 5508 WLC's. Is it possible to export the config from controller on the WISM to the 5508?
View 5 Replies View RelatedI dont think my cards are faulty (4 cards in 2 6500 switches),I connect directly to my WISM cards, boot them (insert them), I see it turning on, enabling services, and as soon as the "username:" prompt apears, the Status led turns off and I lose console. [code]
View 21 Replies View Relatedwe have two wisms in a cat6500, I wonder how can you log into the wism from the switch. to be more specifically, how can I know the processor number?
View 4 Replies View RelatedWe have Cisco WiSM modules on our 6500 switch. I tried to register a 1142 access point to the WiSM. Is there any difference in the way an AP registers and appears on the WiSM as compared to the Wireless Lan controller?
I could see the AP get an ip from dhcp pool ( configured on the switch ) and Ap was visible on the cdp neighbor of switch.
However, i could not locate the new AP on the WiSM module. Do i need to add MAC address to the WiSM as same as WLC.
I have a facility, where all the access points almost 250 of them are connected to two WisM's (One in each core switch ) . They are running in 6.0.199 firmware . These two WisM's are managed by WCS , which is running 6.0.188.
As i need to add more access points and to make fully redundant , 5500 controller was ordered and it has with firmware 7.0 installed. Couple of queries related with it .
1. Can 5500 be added in the WLC group, so that existing Access Points can be configured to use primary controller as 5500 and secondary / tertiary controller as WISM ?
2. Will 5500 be able to be detected by WCS , as the version of 5500 is 7.0 and WCS version is 6.0.188 ?
3. As WCS was already deployed and live, is it possible to upgrade, if the client has support contract like SUSA ?
WISM v7.0 VLAN Select. If the VLANs subnet to be configured under interface group MUST be having the same subnet.
Eg. VLAN1 - mask 255.255.255.248
VLAN2 - mask 255.255.255.120
Would these two VLANs be able to work together in interface grouping?
WiSM WLAN Service Module WS-SVC-WISM-1-K9 in 6509e running VSS IOs s72033-ipservicesk9_wan-mz.122-33.SXI2a.bin having trouble to get the IP from service-vlan DHCP.The pertinent config is as follows.
!
vlan 300
name WiSM_Service_Vlan
!interface Vlan300
description *** WiSM Service-Vlan
ip address 192.168.200.1 255.255.255.0
[code]....
The service IP is supposed to have been populated with an address from the dhcp pool. I am also unable to connect to it by doing a session switch 1 slot 4 processor 1. I get the following upon attempting to do so:
HO2NET0001##session switch 1 slot 4 proc 1
The default escape character is Ctrl-^, then x. You can also type 'exit' at the remote prompt to end the session Trying 0.0.0.0 ...
What this card is and what is it used for?
from show module command, it appears that it is a sub-module of the wism blade.
what is it's primary function?
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 ?
We have a WISM in a 6509. The 6509 lost power (the UPS failed) and upon reboot the WISM isn't allowing AP's to connect. The WISM is blade 4. Upon consoling in, I get this error message for all 8 ports: 42w6d: %EC-SP-5-CANNOT_BUNDLE2: Gi4/1 is not compatible with Po407 and will be suspended (trunk mode of Gi4/1 is dynamic, Po407 is trunk)
View 13 Replies View RelatedI have a WiSM installed in WS-6504E, vesion 6.0.182. It can't function normally after upgrading to version7.0.220.When it was unstable, I found three strange condition 1. A lot of log looks like this*osapiReaper: Mar 10 14:53:39.282: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/1059/stat.(erno 24)*osapiReaper: Mar 10 14:53:39.282: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'fmcHsTask'2. Internal Temperature was showed "sensor failed"3. CPU User load is Zero?
View 8 Replies View RelatedThe Samsung SCH-i569 Wi-Fi can't work at the LAP1131G with WiSM. It can associate to AP and get the ip address but about one minutes ago it had deauthentication and the phone's Wi-Fi status will show scanning. The phone can work at the Autonoumous mode or other 3rd party Fat AP.
View 1 Replies View RelatedSetting up a multi floor WLAN using a 6500 WISM Controller. Each floor has an AP group with the floor WAPs assigned. Each floor has a VLAN and the WLC has an interface configured. Each floor has a WLAN configured with the same SSID and the only change is the interface on the WLAN per floor.DHCP is remote on AD servers and each floor as a scope configured.Each floor works fine - we can get connected and get assigned to correct IP address. The issue we had with this setup was moving between floors. When we move up a floor the client loses connection to the inital floor (coverage - as expected). if we disconnect and reconnect it connects to the new floor SSID and gets an IP from DHCP.When looking into this - I then created an interface group and added all the floor interfaces into the group. I then applied the interface group to each floor WLAN and did soem testing - it worked as expected. I could now move between floors.The issue with this is though. When I was testing I already had an IP address assigned from DHCP - before I changed to interface groups. The issue is that the intial DHCP assignment no longer works and we cant connect to the WLAN anymore,
View 2 Replies View RelatedI have a WiSM installed in WS-6504E, vesion 6.0.182. It can't function normally after upgrading to version7.0.220. [code]
View 1 Replies View RelatedI am looking to install 2 1552I outdoor AP's. I can't find what the minimum code version is on the WISM controller that supports this AP.I am running 7.0.98.0 on the WISM. Where can I find this information?
View 4 Replies View RelatedI have a customer buys 12 x WISM and build up a mobility, when I add the final WLC to mobility, it prompts that there mobility group has reached the max of mobility member, but the total member is 23, according the configuration guide, it should be allow to 24 member, do I hit some bug? My using version is 7.0.98.0.
View 5 Replies View RelatedI have been having some issues trying to stand up an older WiSM that has been incorrectly configured by my predecesssor and has a bad Mgt IP so I am unable to telnet or SSH into it, nor can I console or session into it.
What I would like to do is to change the Mgt address for the WiSM controllers (1 and 2) by way of the Sup (not sure that is possible) because as it stands they are set to 169.254.1.1 and are unreachable even when directly consoled into them.
Core-A#sh wism status
Service Vlan : 52, Service IP Subnet : 10.104.52.2/255.255.255.0
WLAN
Slot Controller Service IP Management IP SW Version Status
-------------------------------------------------------------------------------------------------------
3 1 10.104.52.3 169.254.1.1 4.0.217.0 Oper-Up
3 2 10.104.52.4 169.254.1.1 4.0.217.0 Oper-Up
Core-B#sh wism status
Service Vlan : 52, Service IP Subnet : 10.104.52.1/255.255.255.0
WLAN
Slot Controller Service IP Management IP SW Version Status
-------------------------------------------------------------------------------------------------------
3 1 10.104.52.50 10.104.30.254 7.0.116.0 Oper-Up
3 2 10.104.52.51 10.104.30.250 7.0.116.0 Oper-Up
I hope to get this WiSM setup on Core A and get it configured like I have my Core B and then run them in a dual failover design with load balancing between the two.
although cisco sw advisor said that the best IOS for my hardware 6509 Sup720 IOS: (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF16 suits the WiSM; And I tested it already with WiSM version 5.0 but when I've upgraded the WiSM to version 6.0 the service interface from the switch side says:
B5_Noc2_CS1(config)#int gig 4/9
% This interface cannot be modified
as the customer refuse to upgrade the switch IOS & He wants to use the latest ED WiSM sw 6.0;
The problem is WiSM module not coming in OPER-UP status , it’s in Started-Keepalive status.I did run debug wism events on cat6509 and seeing below logs:
[code]...
It’s receiving garp request from controller and assign ip to controller but then keepalive time expired and it’s put the controller in started-keeplaive status.
how we can make guest access to our network like hotels by using our WISM v 7.0.220 and wireless control system and ACS ?
View 1 Replies View RelatedI'm trying to upload a new software image (~86mb) from my PC to the WiSM2 controller on a 6513 chassis.
Midway through the transfer, the transfer stopped and I got this error on the log:
*TransferTask: Jan 01 00:28:33.124: %UPDATE-3-FTP_TRANSFER_FAIL: updcode.c:4508 Error FTP file Transfer [ftp_get], <28>, No space left on device.
How to access the memory on the wism to delete the old boot image?
We have a new SSID that needs to be added to an AP through a 4400 Controller with software version
7.0.116.0
All AP's are configured as Lightweight.
I have a 4400 WLC for 100APs running the 7.0.98.0software version. Now, only 48 APs are joined, and the WLC dont accept new joins. The log below are from my WLC but appear for all others APs:
%LOG-6-Q_IND: spam_lrad.c:1440 Discarding discovery request in LWAPP from AP 00:3a:98:ae:e3:f0 supporting CAPWAP%LWAPP-6-CAPWAP_SUPP_VER: spam_lrad.c:1440 Discarding discovery request in LWAPP from AP 00:3a:98:ae:e3:f0 supporting CAPWAP%CAPWAP-3-TX_ERR: capwap_ac_sm.c:1966 Failed to transmit discovery response to AP 00:3a:98:ae:e3:f0%CAPWAP-3-ENCODE_ERR: capwap_ac_sm.c:2269 Failed to encode Discovery (code)
Is Ciscoworks LMS 3.2 supports WISM 2?
View 3 Replies View Relatedi have a existing wireless network setup in my office existing wlc in 4402 and LAPs are 1130 & 1242 all are working fine but we are now planning to use new 5500 series controllers for the same access points,i want to ask that how i can done this job with very minore downtime and users disconnectivity + zero error results??
View 2 Replies View RelatedWe have a WLC4400 controller with about 30 LAP. We moving to a new IP scope and was wondering what is the best way to change the IP address of the controller. We have tried doing this via GUI however we have to power cycle the controller to get it back online using the old ip address.
View 3 Replies View RelatedLike the way you do with the Cisco IOS.
ie show start | i router
Does CSCua29504 affect 4400 series WLCs as well? Bug toolkit mentions just 5500, so want to get a confirmation.
View 2 Replies View Related