WiSM's Code 4.2.61.0

Hi all and Happy New Year!
In my effort to kick the new year off right, I have decided to upgrade my WiSM's. I really want to have 16 VLAN capability with my wireless network and so I am wanting to know if anyone has gone to the 4.2.61.0 code and if so, what issues have you run into. I have gone through the caveat list in the release notes and the list of issues is long and distinguished.
To tell you a little about my network, I have 4 WiSM modules in two 6509 chassis in two different buildings and approximately 430 access points across 45 locations with over 1200 clients. My goal is to make things operate more smoothly and gain several more VLAN's to help break off some of our more chatty devices.
Thanks in advance for any and all responses.
David Beaver
Spartanburg Regional Medical Center
Spartanburg, SC

Thanks Mark and Randy. I had taken the time to read alot of the posts about issues with 4.2.61.0 dating back before Dec. 1st, but I was just throwing the question out there to see what everyone elses experience was with the 4.2.61.0 code was.
It's very hard to make the move to upgrade, but I definitely want to just for the extra 8 vlans. That will solve so many issues for me right now, and if there are no real configuration issues, then I may go ahead and roll it out. We are getting ready to install the 4th WiSM in about a week and I'm not looking forward to it.
Thanks again for your feedback and keep me up to date if you encounter any issues.
David Beaver
Spartanburg Regional Medical Center
Spartanburg, SC

Similar Messages

  • AIR-CAP1552I Minimum WISM Support Code

    I 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?

    Maybe you are looking for this:
    http://www.cisco.com/en/US/docs/wireless/technology/mesh/7.0/design/guide/MeshAP_70.html#wp1623290

  • Vlan Select and DHCP reservations on a WISM with code 7.0.116.0

    We went to using vlan select this semester and have had a couple of issues where clients (printers) wont pull their reserved ip from dhcp. From what I've read vlan select can handle static ip addresses but can it handle dhcp reservations if the current vlan selected in the round robin function is not the vlan that the ip is reserved in?

    George,
    Are you talking about a dhcp mac reservation for a device on all vlans in the bundle? If so, you can... The issue I ran into is that clients had to connect to a wireless printer and a wireless projector and they connected to it via ip address. So it became a nightmare with users. They just kept complaining that it works some days and other days it doesn't. Some devices were powered off after it was used. It would be nice if you can import a list of Mac address and specify what interface it is allowed on... That would make it easy.
    Sent from my iPhone

  • 1142 AP disassociate from WISM code 7.0.116.0

    We see different 1142 APs disassociate from wisms from time to time. When it happens, we have to do shutdown and no shutdown on the switch port to bring the APs back. It just starts to happen after we upgraded wisms to code 7.0.116.0 and it only happens to c1142 APs. It does not happen very often (about 2 issues each week). Anyone see this issue as well?
    Zhenning

    Any ideas why we need to upgrade the bootstrap?
    There are some issues with the 1140.  This is why it's only this model that a boostrap is an optional install (autonomous or capwap use).  I'd recommend, if you have the time, to do so.
    Unfortunately, I have no idea how you "force" the bootstrap upgrade if you have CAPWAP/LWAP.  The only way I can think of is downgrade to autonomous, upgrade the boostrap and convert to CAPWAP/LWAP.  Long process.

  • Does WiSM 6.0.196.0 suport AIR-LAP1131AG-N-K9 in H-REAP mode

    Hello,
    I have WiSMs running code version 6.0.196.0. I have to deploy AIR-LAP1131AG-N-K9 in H-REAP mode.
    Q1. Does AIR-LAP1131AG-N-K9 require CAPWAP or can run off of LWAPP?
    Q2. Does anyone know how to find out if a WLC is running LWAPP or CAPWAP?
    Q3. If one has to convert LWAPP to CAPWAP, how is it done?
    Thanks
    Bo

    Hi,
    Q1. Does AIR-LAP1131AG-N-K9 require CAPWAP or can run off of LWAPP?
    A1. The AP will run CAPWAP as soon the WLC is running a CAPWAP image. There is nothing special to do on the AP, once it joins the WLC, the WLC will check the image on the AP and if using a diferent one, the WLC will push the correct image to the AP that matchs the WLC version.
    Q2. Does anyone know how to find out if a WLC is running LWAPP or CAPWAP?
    A2. CAPWAP was introuduced in WLC version 5.2 and all versions above are running CAPWAP software.
    •If  your firewall is currently configured to allow traffic only from access  points using LWAPP, you must change the rules of the firewall to allow  traffic from access points using CAPWAP.
    •Make  sure that the CAPWAP UDP ports 5246 and 5247 (similar to the LWAPP UDP  ports 12222 and 12223) are enabled and are not blocked by an  intermediate device that could prevent an access point from joining the  controller.
    •If  access control lists (ACLs) are in the control path between the  controller and its access points, you need to open new protocol ports to  prevent access points from being stranded.
    Q3. If one has to convert LWAPP to CAPWAP, how is it done?
    A1. On the APs nothing has to be done. Once the WLC is running CAPWAP software, it will automatically push the corresponding AP software to the AP.
    WLC runs CAPWAP if the software version is earlier then 5.2. WLC version 5.2 and all versions above are running CAPWAP software.
    HTH,
    Tiago
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • WiSM- Latest Software version

    I am using a WiSM controller with software version 7.0.116.0. Can this work with netflow. And if the answer is no, which software version can?

    Here is a matrix of all wireless devices and code support. The WiSM last code support is v7.0.x.
    Like the others mentioned, you need to purchase the WiSM2 or go with a WLC like the 5508 in order to use a code that supports netflow.
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
    Sent from Cisco Technical Support iPhone App

  • Wism2 in High Availability - FUS Upgrade

    Hello all,
    what is the procedure to be followed when upgrading the FUS on a WISM-2 in HA cluster?
    Is it the same procedure that applies when upgrading the wism's code in HA?
    Thank you
    Edited:
    The procedure is exactly the same as upgrading. First upgrade the image and then FUS.make sure that you are connected using console connection and definitely perform this within a maintenance window of at least 1 hour. 

    Hi,
    Thanks for sharing this info.
    Snipped from this guide also explains how its done:
    https://supportforums.cisco.com/discussion/12190806/wism2-high-availability-fus-upgrade
    The FUS image can be upgraded while the controllers have HA enabled. The secondary controller will 
    get upgraded just like it does when upgrading the regular code. However, when you initiate the reboot 
    on the primary controller both controllers will be unreachable until the FUS upgrade completes on both 
    the active and the standby in the HA pair. This process will take around 30 to 40 minutes to complete 
    just like in a non-HA FUS upgrade.

  • WiSM 4.2.130 Code

    Currently running 4.2.112 code on our WiSM. Wondering if it is ok to move up to 4.2.130. When doing so is there a procedure you follow with a number of AP1131s on each controller?
    Since school started the other day we have been getting calls about wireless being down in certain room. A reboot of the AP solves the issue. Reading release notes for 4.2.130 but not sure if there is anything in there for this issue.
    Craig

    It is okay to upgrade to 4.2.130 since it has the gold stamp from Cisco. If you do the upgrade, I would suggest you move all your ap's from the WLC you with to upgrade first. Set the primary to the other WLC and disable ap fallback. You don't want the ap's to join the WLC when the upgrade is done. After the upgrade, move 6 ap's at a time by changing the primary back to the upgraded WLC. You can reset the ap an let the ap find the primary and then it will download the code. Wait for the ap to come up and then you can move onto the next 6. I have seem issues if more than 6 ap's try to join and download code at the same time. Be safe so you are not visiting ap's that got hung from the upgrade.
    Also, what issues were you seeing that indicated that you need to reboot the ap?

  • LEAP wireless clients work, then fail, Using WISM blades HELP

    I am at a complete loss. Calls to Cisco, working with different vendors, nothing has worked to solve the problem. This is what we see, and we see this at every single one of our hospital sites.
    All hospitals used to run just IOS code on their AP's. Some hospitals used the older 1200 series AP's, which have been upgraded from B only radios to A/B/G. Some hospitals were rolled out with newer 1240 series AP's. Every single hospital was just fine when using IOS code on the AP's. Users never disconnected or disassociated. They were fine. Clients run a mixture of the old Cisco 350 series cards, or Ubiquiti A/B/G cards.
    Now, fast forward and we started installing WISM blades in all the 6509 distribution switches at each hospital. AP's were then upgraded to lightweight code and at first everything seemed great. Then the calls started.
    All clients at all hospitals will just disassociate. It is completely random. Some machines can see it once, others 50 times a day, then tomorrow, totally different. I have witnessed the same thing with my laptop. We have 3 WLAN's in the hospitals. One that uses LEAP authentication, one that uses Certificates, and one that is our Patient WiFi. Both LEAP and Certs have the issue. I have never been kicked off of the Patient WiFi system. Not once.
    LEAP clients use the same exact ACS servers they have always used. Nothing changed in the configs. Same goes for the clients using certificates.
    I have upgraded code on the WISM blades 3 times now. Currently we are using the 5.187 code. I have tried forcing all AP's to use only B/G radios, tried using only A, doesn't matter. Same problem happens.
    What is even worse, when this event happens, 50% of the time you have to actually reboot the workstation to get it to log back onto the wireless network. It fails the attempt and it just stops. This is not everyone at the same time either. There seems to be no event that I can find where all clients have the problem at the exact same time. I can have two devices side by side, same exact NIC, same software, everything. One will disassociate, the other is just fine.
    I am out of ideas. Everyone I talk to at Cisco says never heard of this before. I just can't believe we are the only ones that have ever seen this problem.
    I can take the same workstation that is breaking left and right on our wireless networks using the WISM blades, go to a site with AP's still in IOS mode, it will never disassociate and disconnect.
    Has anyone heard of this, have any ideas of something I could try. Would you like to see any other information about this? I can post whatever you like to help. I am looking for any assistance on this.
    I have been trying to do some searches on this forum, but for whatever reason it seems to be very slow so thought I might post my issue as I search around, maybe if it has already come up and there is a fix, someone could direct me right too it.
    Thank you in advance.

    I tried that in the beginning. Put all ap power and channel as hard set. It did not change anything. I am not sure if we have tried the 4.2.207 code. I know we went through several 4.x.x codes in testing. Cisco recommended the lastest one that we are on now.
    What really gets me is how everything worked just fine until the WISM upgrade. No AP placement changed, no additional AP installs, we just installed the WISM blades, migrated code to lightweight and everything started flaking out.
    What other NIC's do people use? Maybe the brand we use is not any good? I have been up and down with the vendor, tried different drivers, nothing seemed to change anything.
    It looks to me like the WISM sends out some kind of response that the workstation NIC's do not understand, so they just sit there. On wireless sniffer traces, you can see where the request goes out to the workstation, but the workstation just never responds, hence the lockup so to speak. It will just sit there until a reboot of the PC.

  • Adding a secure WLAN - WISM and WCS

    I have a setup including a WISM and WCS which currently only runs a guest service using webauth to get online. The service (by request) is not secured over the air. I would like to implement a second SSID with security but before going the whole way with 802.1x I wanted to implement a half way house. Service will still only be a guest service but I want the air traffic secured.
    So I guess my options are WEP (forget it) or WPA/WPA2.
    My question is do I have to run this service with a shared secret that I then need to inform all users of in order for them to be able to connect to the service or is there a way to implement a WPA service that uses some kind of credential check against the already configured RADIUS (ACS) servers?
    And if this is possible I assume there is no longer need for a webauth as this just seems to duplicate the login process.
    Thanks for any pointers in advance
    Paul

    The best thing you can do is start with the Configuration Guides.  If you don't have a test environment and have SMARTNET on the WiSMs/ WCS, utilize TAC to help you get up and going.  I would also suggest utilizing a Cisco Partner to help with the initial implementation as well.
    I would recommend upgrading your WiSMs and WCS to the latest versions and making sure configurations are the same across modules.  I upgraded our WiSMs from 4.x to 7.0.98.0 and WCS to 7.x.  Ran into a bug here and there but that is expected.  Just make sure the wireless devices support those versions.  If you are unsure, you can always work towards the AssureWave tested code.  WCS 7.x should be backwards compatible (check the release notes just to verify).  The Design Zone and Release Notes are your friend too.
    -Rick

  • WEB AUTH problem on WISM

    HiGuys We are facing issue in authenticating guest user via web authentication on WiSM.We have WiSM with 270 APs. We have guest ssid with web-auth enabled.we are running 4.2.061 code. It was working fine till last week, now suddenly it keeps getting off. Users are not getting web-auth login page. We had to disable the web-auth & reenable it then it again starts working. I dont know wht to do in this case. didnt find any log..whts going on in background.
    need help to resolve it.
    Thanks
    NK

    I had the same basic issue and after reseaching found caveat CSCsk54969 which is a pretty close match. This caveat has been fixed in release 4.2.130. I have just upgraded to this release over the week end so to soon to tell yet.... fingers crossed...

  • WiSM-A and -B communication problem

    I am deploying a 6509-WISM with 120 x 1130 APs running 4.1.181.0. Both controllers (A and B) are configured as LWAPP Layer 3 mode with he same mobility and RF domain. The APs use DHCP to obtain their IP through option 43. All APs register only to WiSM-B and none go to WiSM-A. I even tried configuring the Primary and Secondary Controller with WISM-A only and the APs are still only registering to WiSM-B only. Any advice would be greatly appreciated.

    Hi Chris,
    Since I restarted both controllers this morning, here are the only messages that show up in the log.... There should be more than that as far as I am concerned.+
    Aug 24 15:20:39.932 hwutils.c:2159 INIT-0-MSGTAG007: Security Module not found.
    Aug 24 15:20:39.161 bootos.c:874 INIT-0-MSGTAG001: Starting code...
    We are also looking at the arp table on the default gateway and there is a MAC that is not making sense. On WISM-A ap-manager interface, the AMC shows up as being 001b.243d.a9f6 which is a Quanta Computer MAC..... but should be showing as a Cisco one. Will let you know.
    Any thoughts?
    Thanks

  • WiSM PortChannel Issue?

    I'm running a WiSM on a 6504E using supervisor code s72033-ipservices_wan-mz.122-33.SXI2.bin. When I add a statement configuring the allowed VLANs on the WiSMs, I get the following errors:
    *Aug 5 16:56:35.202: %EC-SP-5-CANNOT_BUNDLE2: Gi2/6 is not compatible with Po404 and will be suspended (trunk mode of Gi2/6 is dynamic, Po404 is trunk)
    *Aug 5 16:56:35.826: %EC-SP-5-CANNOT_BUNDLE2: Gi2/5 is not compatible with Gi2/7 and will be suspended (trunk mode of Gi2/5 is trunk, Gi2/7 is dynamic)
    *Aug 5 16:56:36.138: %EC-SP-5-CANNOT_BUNDLE2: Gi2/6 is not compatible with Gi2/8 and will be suspended (trunk mode of Gi2/6 is trunk, Gi2/8 is dynamic)
    Keep in mind that I don't have the option to configure these gigabit interfaces as they are auto-provisioned by the version of code being run on the switch.
    Here are some show commands that may be of interest:
    ###-###-mdf#sh etherchannel summary
    Flags: D - down P - bundled in port-channel
    I - stand-alone s - suspended
    H - Hot-standby (LACP only)
    R - Layer3 S - Layer2
    U - in use N - not in use, no aggregation
    f - failed to allocate aggregator
    M - not in use, no aggregation due to minimum links not met
    m - not in use, port not aggregated due to minimum links not met
    u - unsuitable for bundling
    d - default port
    w - waiting to be aggregated
    Number of channel-groups in use: 2
    Number of aggregators: 2
    Group Port-channel Protocol Ports
    ------+-------------+-----------+-----------------------------------------------
    403 Po403(SU) - Gi2/1(P) Gi2/2(P) Gi2/3(P)
    Gi2/4(P)
    404 Po404(SU) - Gi2/5(P) Gi2/6(P) Gi2/7(P)
    Gi2/8(P)
    ###-###-mdf#show wism status
    Service Vlan : 3015, Service IP Subnet : 10.139.255.1/255.255.255.0
    WLAN
    Slot Controller Service IP Management IP SW Version Status
    ----+-----------+----------------+----------------+-----------+---------------
    2 1 0.0.0.0 10.137.139.2 5.2.178.0 Service Port Up
    2 2 0.0.0.0 10.137.139.4 5.2.178.0 Service Port Up
    ###-###-mdf#show etherchannel load-balance
    EtherChannel Load-Balancing Configuration:
    src-dst-ip
    mpls label-ip
    EtherChannel Load-Balancing Addresses Used Per-Protocol:
    Non-IP: Source XOR Destination MAC address
    IPv4: Source XOR Destination IP address
    IPv6: Source XOR Destination IP address
    MPLS: Label or IP

    Do you have qos enabled globally? This was an issue with IOS a while back, but should be fine in SXI
    how6506A#sh ver
    Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9-M), Version 12.2(33)SXI1, RELEASE SOFTWARE (fc3)
    maybe they broke it again in SXI2
    show6506A#sh mls qos
    QoS is enabled globally
    Policy marking depends on port_trust
    QoS ip packet dscp rewrite enabled globally
    Input mode for GRE Tunnel is Pipe mode
    Input mode for MPLS is Pipe mode
    QoS Trust state is CoS on the following interface:
    Gi4/1 Gi4/2 Gi4/3 Gi4/4 Gi4/5 Gi4/6 Gi4/7 Gi4/8 Po407 Po408
    Vlan or Portchannel(Multi-Earl) policies supported: Yes
    Egress policies supported: Yes
    ports listed in above command are my wism ports

  • Migrating data from 4404 to WiSM

    Hello,
    Is it possible to download configuration data created from a 4404 into a WiSM in order to migrate the configs into the blade? If not, how is the migration performed?
    I'm going to be putting in a WiSM to replace my two 4404's, so any information or tips on the migration process would be appreciated.

    Hi Peter,
    As far as WISM is concerned it is exactly 4404 controller with LAG enabled. So if you current 4404 is configured with LAG and both 4404 and WISM are running same Controller code you are good to go. I believe you just need to take care of the IPs configured on old 4404 controller if you are completely taking your 4404 out then its ok or else you have to configure new ip range either on your existing 4404 or else on WISM.
    Just make sure WISM is up and running and are showing OK status when you issue "sh wism status" command on sup engine.
    HTH
    Ankur
    *Pls rate all helpfull post

  • How to override LWAP/WiSM PoE ignorance

    I have a LAP-1130AG plugged into a 3750G port. As the 3750G is non-PoE, the LWAP has an AC power-pack/brick plugged in, but still generates this error in the WiSM syslog:
    LWAPP-3-AP_POWER_ERR, and refuses to power up the radios.
    A search on cisco.com for this error code tells me to search on cisco.com for an answer. Duh.
    How to I tell the AP that it truly does have enough Power to turn on the radios?
    On an autonomous AP, you can do a power inline overide command.
    I have a WiSM, and WCS (former WLSE).
    Thanks.

    Another option (esp. if you are using 3rd-party mid-span injectors) with Cisco Non-PoE switches is to disable CDP (Cisco Discovery Protocol).
    This is because, although the Cisco switch does not have PoE, it knows about it it from a CDP standard. So, when the AP/LWAP initially powers up (with radios off for minimal power draw), it asks about the PoE capability of the Cisco switch using CDP. The Cisco switch says, I don't have any.
    So the LWAP stays half-powered (LWAP is on and can be remotely managed, but its radios are off). For Cisco 1131 LWAP access points, The indication of this half-power state is a rather bizarre solid orange color on the color ring of the 1131 (which Cisco describes as "Amber"). Once CDP is disabled (by either disabling it from the access point or the Cisco non-PoE ethernet switch) all you need to do is power down and power up the access point (or the power injector) and you are ready to go.
    (Thanks to earlier post by ron_mckie - Dec 24, 2006, 5:57am PST)
    - John
    (Please remember to rate helpful posts)

Maybe you are looking for