WISM to WISM2 upgrade?

Hi, next week I am going to a customer and upgrade his wireless installation. From a WISM / WCS system to a WISM2 / Cisco Prime Infrastructure system. Does anyone have any best practice advice in such scenarios? Exchange the WISM with the WISM2 first or upgrade the WCS to Cisco Prime Infrastructure first? Or just start over from scratch :-)
Hans Jørgen

What I would do, is migrate the WiSM to WiSM2 first. Put the WiSM2 on the same code version as WiSM, and move the AP's. Run in parallel for a bit just to make sure everything is stable.
Join the WiSM2 to WCS, hopefully the code supports it. Once you have that done, then use the export command to pull the data out of WCS. Load up your VM, medium or large no point doing a small, and import the data from WCS.
What I've found is that 1.2 does not have the import availability, so it would be two staged to get from WCS to Prime. WCS to NCS 1.1, then upgrade 1.1 to 1.2.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Similar Messages

Planning WISM to WISM2

Hello,
I hope my english is comprehensible. I have an environment with 2 WISM (4 logical controller) and about 450 APs. Both WISMs have the same configuration. Now I want to migrate the whole thing on 2 WISM-2. I've designed the following scheme and I would like to have confirmed whether this can work this way. The migration should take place during operations, but single APs can fail at short times.
-First, move all the APs on 3 logic controllers, so that one controller is empty
-then update the firmware of the empty controller from version 7.0.116.0 to 7.0.230.0 (bring the WISM-2 on the same version 7.0.230.0, too)
-export the configuration of the empty WISM and import it on the WISM-2
-updating the firmware version of the WISM-2 to the current version (7.2.x.x)
-then change the APs with older version 7.0.116.0 bit by bit from the 3 WISMs to the new WISM-2 with version 7.2.x.x (if it works)
Is that possible, and to recommend, or is there a better alternative for the migration?

Because upgrading the WiSM-2 FUS takes about 20 minutes, I'd be leaving the WAPs with the WiSM-1 and upgrading the WiSM-2 FUS and the firmware to 7.2.110.0.
Once the WiSM-2 upgrades are complete, swing the WAPs across.
Now I know that by doing it this way, the WAPs will go offline because of the software upgrades from the WiSM-2 but I believe it's better this way because it's the same anyway. Whether you use the orignal method or not, the WAPs will still reboot.
This changes if, say, you the WiSM-2 in the same code level as the WiSM-1.

WiSM2 upgrade and HA

hello, experts!!!
seeking advise....
wism2 and wism2-HA with code 7.3
should i upgrade to 8.0 prior to HA config?
thanks in advance!

hmmm... bootstrap and firmware...
firmware upgrade to 8.0 MR1 i can do...
but bootstrap upgrade to 1.9.0., no idea...:( any links with procedure? we are talkin' about bootstrap for the WiSM2, right?
the download page for WiSM2 does not seem to have any 'bootstrap' for download.
Thanks!

WISM1 (WLC 6.0.182) to WISM2 (WLC 7.2.115.1) migration

Hi all,
I plan to replace 2 x WISM1 (WLC 6.0.182) by 2 x WISM2 (WLC 7.2.115.1). One WISM in each Catalyst 6500. I am sorry it is a little long but I have no lab and I need your advice.
Summarized migration plan is the following :
Upgrade of the 4 WLC (WISM1) from 6.0.182 to 7.0.240
AP pre-download from the 4 WLC (WISM1)
Transfert WLC 7.0.240 image to the 4 WLC (last compatible version)
Transfert WLC 7.0.240 image from the 4 WLC to AP and swap AP primary and secondary image
So, AP primary image is 7.0.240, AP secondary image is 6.0.182
Scheduled reboot of the 4 WLC
So, 4 WLC (WISM1) and AP are running WLC 7.0.240
Move AP from the 2 WLC of the1st WISM1 to the 2 WLC of 2sd WISM1 Swap AP primary and secondary controller with NCS
Backup the configuration file
of one WLC of the 1st WISM1
of one WLC of the 2st WISM1
Replace the 1st WISM1 by one WISM2
WISM2 upgrade from the current WLC version to 7.0.240
Import the saved configuration file (WISM1) to WISM2 (7.0.240)
Check the configuration via HTTPS
Move AP from the 2 WLC of the 2sd WISM1 to the 1st WISM2 Swap AP primary and secondary controller with NCS
Replace the 2sd WISM1 by one WISM2
WISM2 upgrade from the current WLC version to 7.0.240
Import the saved configuration file (WISM1) to WISM2 (7.0.240)
Check the configuration via HTTPS
Upgrade WISM2 from 7.0.240 to 7.2.115.1
AP pre-download etc.
etc.
Please, what do you think about this migration plan ?
Do you have a better/simplier solution ?
Thanks

Also you would enable Authorize MIC APs against auth-list to avoid AP's fallback to the WiSM1. So, if I understand you, it would be enable on WISM1. This way AP's trying to fallback to the WISM1 will be refused and reconnect to the WISM2 that's right ?
Yes... this will prevent access point from joining the WiSM1... AP's that are already on WiSM1 will stay, it just prevents any AP's that has already been migrated to WiSM2 to fail to WiSM1.
How can I get the configuration from WiSM1 to the WiSM2 ?
Well you would backup your config and open it up in a text editor... then you would edit the file, by changing the hostname and ip address, etc. Make sure you have a trailing space at the end of each command that you change. This is important or else the config will not take. Also you will have to edit the password for the management since it is encrypted in the backup config. replace it with:
config mgmtuser password
Save the config and do a restore on the WiSM2 and verify that the setting are okay prior to moving all the ap's over. I would move one to test your wlans and make sure its fine before moving more.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Unable to access WEB UI of WiSM2

Bear with me as this is my first install of a 6500 and WiSM module.
The backgroud is that we are small, but management used to be in networking and basically forced the the purchase of a 6509E. Most of my experience is with 3560X and 2950 switches.
I have followed the basic deployment guide here:http://www.cisco.com/c/en/us/support/docs/interfaces-modules/catalyst-6500-series-7600-series-wireless-services-module-wism/112968-wism2-deploy-guide-00.html. My problem is that I have a flat network (see why I didn't want a 6500) so the management network and the production network is on VLAN 1. Yes I know how bad this is, but apparently wireless is more important than adhering to good security practices.
My problem is I am unable to access the Web UI of the controller. I am however able to ping the address for the management IP. I will give as much output as I can think would be helpful right now (and more if needed), but any assistance I can get would be appreciated.
#show module
Mod Ports Card Type Model Serial No.
2 4 WiSM 2 WLAN Service Module WS-SVC-WISM2-K9 SAL172579DM
6 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL1706YCQJ
Mod MAC addresses Hw Fw Sw Status
2 30f7.0d0b.9820 to 30f7.0d0b.982f 1.1 12.2(18r)S1 15.1(1)SY1 Ok
6 ccef.4838.97d5 to ccef.4838.97dc 1.4 12.2(50r)SYS 15.1(1)SY1 Ok
Mod Sub-Module Model Serial Hw Status
6 Policy Feature Card 4 VS-F6K-PFC4 SAL17299W2L 2.1 Ok
6 CPU Daughterboard VS-F6K-MSFC5 SAL1706YBTQ 1.5 Ok
Mod Online Diag Status
2 Pass
6 Pass
#sh wism module 2 controller 1 st
WiSM Controller 1 in Slot 2 configured with auto-lag
Operational Status of the Controller : Oper-Up
Service VLAN : 50
Service Port : 3
Service Port Mac Address : 6c20.562c.2c61
Service IP Address : 192.168.2.51
Management IP Address : 40.96.0.2
Software Version : 7.0.116.0
Port Channel Number : 403
Allowed-vlan list : 1
Native VLAN ID : 1
WCP Keep Alive Missed : 0
#do sh wism st
Service Vlan : 50, Service IP Subnet : 192.168.2.1/255.255.254.0
WLAN
Slot Controller Service IP Management IP SW Version Controller Type Status
----+-----------+----------------+----------------+------------+------------------+---------------
2 1 192.168.2.51 40.96.0.2 7.0.116.0 WS-SVC-WISM-2-K9 Oper-Up
HQR1#sh ip int brief
Interface IP-Address OK? Method Status Protocol
TenGigabitEthernet2/1 unassigned YES unset up up
TenGigabitEthernet2/2 unassigned YES unset down down
GigabitEthernet2/3 unassigned YES unset up up
GigabitEthernet2/4 unassigned YES unset administratively down down
GigabitEthernet6/1 unassigned YES unset up up
GigabitEthernet6/2 unassigned YES unset down down
GigabitEthernet6/3 unassigned YES unset down down
TenGigabitEthernet6/4 unassigned YES NVRAM administratively down down
TenGigabitEthernet6/5 unassigned YES NVRAM administratively down down
Port-channel403 unassigned YES unset up up
Vlan1 40.96.0.1 YES NVRAM up up
Vlan50 192.168.2.1 YES NVRAM up up

Well I feel stupid, apparrently, either by default or by my commands "Web mode" and Secure Web Mode" was disabled. after enabling, it works.

WiSM controllers reload scheduler???

WCS 4.2.62.11
WiSM controllers 4.1.185
Is there any way to schedule a WiSM controller's upgrade? We would like to upgrade our WiSM controllers from 4.1.185.0 to 4.2.99.0 through some kind of scheduler. We could download the new image to the WiSM blades the day before, but we would like to schedule a controller reload for some time around 5 in the morning. We are aware that the APs will download a new image and it would take a bit for them to be operational, but we have enough time before production hours.
Through Ciscoworks we could schedule a module reset which will bring the new image to active (we would set the primary image load value ahead of time), but we would like something a bit more gracious. I haven't been able to find anything under ciscoworks or WCS where one could schedule a controller reload.
Perhaps there is a CLI command on WCS that I could cron.
Any ideas are appreciated.
Thanks.
Jorge Jiles

We have used expect scripting in the pass, but for security reason we stopped. In any case, in the script what would the command be to reload a wireless controller from a WiSM blade??? I could reload the blade, but I can do this from Ciscoworks as well.
Thanks.
Jorge.

CAPWAP tunnel flapping

A couple of weeks ago we did an upgrade to controller code 7.0.235.3 on our WiSM's and upgraded WCS to 7.0.230.0.
Since then, I have one AIR-LAP1252AG-A-K9 that will not stay up.
AP04
CAPWAP Up Time
4 h 13 m 46 s
CAPWAP Join Taken Time
1 m 22 s
Users keep complaining about getting kicked off or not being able to join.
There is another 1252 AP on the same switch that feeds this one that seems to be working ok, so I don't think it's a network issue.
AP03
CAPWAP Up Time
6 d 3 h 27 m 41 s
CAPWAP Join Taken Time
25 s
Any idea if the code upgrade would have anything to do with this? Could it be a hardware issue or a cabling issue?
Users did not report this problem until after the upgrade.

Joe -- I might open a TAC case for this. As this is impacting your user performance.
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

POODLE and WLC's

If you drilll down in the POODLE security advisory ( Advisory ID: cisco-sa-20141015-poodle) into the Affected products and then to the vulnerable produst and almost at the end you find
Cisco Wireless LAN Controller (WLC) [CSCur27551]
If you open up this bug report it ONLY identifies and lists the 5508. So... does this mean that none of the other controllers such as the 4400.2500, WiSM and WiSM2 are effected? Kind of difficult to beleive since they are are interrelated (at least the 5508 and WiSM2).
Anyone know?
Thanks!

Hmmm, two answers for which WLC's are vulnerable, both marked correct and contradicting each other. I have to wonder why Cisco only listed the 5508 in the bug report and only listed 2 versions of RTOS. I hate to make assumptions even if they seem to make sense so hopefully Cisco will update and revise the advisory...
Thanks!

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 7.0.235.0 post-upgrade problem?

I upgraded one of our WISM-1 modules from 7.0.98.0 to 7.0.235.0 last night. For some reason, APs don't join with it unless I tell them specifically to do so. We haven't specified primary & secondary controllers on purpose, allowing the APs to determine from DHCP & the controllers' responses and decide on one based on load. This has always worked great for us.
After upgrading, I couldn't get an AP to join the upgraded wism even after I specified the controller in the AP config. So then I changed my 6506 load balancing to src-dst-mac since that is a known (although seldom seen) issue with APs joining a controller for the first time. We usually keep it set at
src-dst-mixed-ip-port. That worked & the AP joined the upgraded wism. Then I reset the load-balancing algorithm on the 6506, removed the specific controller from the AP's config, rebooted the AP, and all is fine. I thought that solved it. Not.
Any other AP that I reboot tries to join the upgraded wism since it has only 1 AP connected, but it fails and the AP joins the other wism running 7.0.98.0. Even if I change the load balancing algorithm to src-dst-mac, src-dst-ip, or src-mac, it won't join unless I specify the upgraded controller, which I don't want to do. I can see the wism responding to the join requests, but the APs still end up on the other controller. It soulds like the years-old load balancing algorithm issue, but that doesn't seem to be the whole answer this time.
I hope this information makes sense to those that are aware of the issues I bring up. Any ideas why the 7.0.235.0 wism isn't getting APs to join it successfully without my specifying that controller? The config hasn't changed, except for what new or changed defaults exist. I suspect it might have to do with one of those.... Or could it be the two different controller versions returning confusing and different responses to the initial query?
Thanks.
Bill

We're not using the built-in DHCP service on the WISMs.
A wise decision.
I've upgrade our WiSM-1's to this version and we don't have any issues.
However, in the past, we use to host our DHCP server for the WAPs and the clients on a plain Linux box and we noticed that the Linux box took a painfully long, long time to dish out IP addresses to around 1k WAPs. We later moved our DHCP server to InfoBlox and the problems go away.
Any other AP that I reboot tries to join the upgraded wism since it has only 1 AP connected, but it fails and the AP joins the other wism running 7.0.98.0. Even if I change the load balancing algorithm to src-dst-mac, src-dst-ip, or src-mac, it won't join unless I specify the upgraded controller, which I don't want to do. I can see the wism responding to the join requests, but the APs still end up on the other controller. It soulds like the years-old load balancing algorithm issue, but that doesn't seem to be the whole answer this time.
Never saw this problem at all.

I need Upgrade WiSM to 7.0.235.3

I have a 6509-E with Sup WS-SUP720-3B IOS (s72033-ipservicesk9_wan-mz.122-18.SXF7)
And i need upgrade my Wism to software version 7.0.235.3, and i have a question:
I have to update the ios Supervisor? or can i upgrade to 7.0.235.3 with Supervisor IOS version 12.2(18).SXF7?
Thanks

Hi Juan,
No I did not find any specific documents about there compatibility.
The firmware of the IOS does not decide your 6500 Supervisor. If you want to use WiSM-1, regardless of the firmware you have inside, then your supervisor card should be a Sup720 running IOS version SXF2.
So dont worry about this and go ahead with wism software upgrade.
wism last support is 7.0.x .
Regards
Dont forget to rate helpful posts

WiSM can't function normally after upgrading from vesion 6.0.182 to 7.0.220.

I 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
Anybody can tell me what wrong with the wireless controller ?

Could be a hardware failure.

WiSM software upgrade

Hi All,
We would required upgrade our WiSM from version 5.1.151.0 to 7.0.98.0. So as cisco says we will have to first upgrade the software from 5.1.151.0 to 5.2 then we will be uprading to 7.0.98.0. The current Bootloader version is 3.2.202.0. Should we have to upgrade the Bootloader too to 5.2.157.0 ER.aes ? If so which one should we upgrade first? first the Bootloader or the IOS?
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 5.1.151.0
RTOS Version..................................... Linux-2.6.10_mvl401
Bootloader Version............................... 3.2.202.0
Build Type....................................... DATA + WPS
Pls Advice.
Irshad.

Hi All,
Thanks for all your support. last night we have successfully upgraded the WiSM to verion 7.0.98.0 .
Just wanna share some of the key points to be noted.
Existing System information on the WiSM
Product Version             :           5.1.151.0
RTOS Version               :           Linux-2.6.10_mvl401
Boot loader Version        :           3.2.202.0
Build Type                     :           DATA + WPS
System Name               :           wism-a
System Object              :           1.3.6.1.4.1.14179.1.1.4.4
IP Address                    :           10.226.231.4
System Up Time           :           145 days 17 hrs 56 mins 22
Existing System information on AP
Product/Model Number               :          AIR-LAP1041N-E-K9
Software Version                       :          12.4(23c)JA
There are two WCSs inside the wism. so we have to upgrade both seperatly. Also you cannot go directly to verson 7.0. you'll have to first upgrade the 5.1 to 5.2 then upgrade to 7.0. once you upgraded to intermediate version 5.2 wait for some time till all the APs get connected to WISm and download the new version. Once all APs got the latest version you can start upgarding to 7.0. you can check all APs image version by issuing sh ap image all command.
As Surendra mentioned you can follow his hyperlink for more information.
Many thanks for all
Regards
Irshad

Wism upgrade to 7.0.68.0

Have recently upgraded 6500 Wism from ver 6.0.196.0 to 7.0.98.0.
Upgrade process was successful but noticed that secondary image still is in the previous version (6.0.196.0).
I have read that to upgrade it we must use ER Boot release image,
but the latest ER Boot image but latest available is only 5.2.157.0.
Q1. Is it acceptable to leave it as is?
Q2. If not, What ER (Boot) image is recommended ?
Please advise.
Tnx in advance.

Hi Stephen.
Thanks for your reply. Still leads me to other questions.
What is the difference between ER & BOOT images?
(Attached is taken from Cisco Wism Download page)
Is it safe to claim that the secondary image (6.0.196.0) is better/stable than it's earlier release?
Is there a need to have an ER release as secondary image ?
What is Cisco's recommendation about Wism secondary image?
Is the a write-up about it?
Sorry for the flood of questions.

Upgrade cisco WiSM running in HA mode

Hello everyone,
I have to upgrade a VSS (2 chassis 6509 WiSM that are in HA mode) to code 8.0.110.0
If I upgrade the active one, the second one will be also upgraded ? Just like for the 5508 models ? Or do I need to break the HA, upgrade both WLCs and then configure the HA again ?
Is there some particular things i need to know for this upgrade ? I never did an upgrade on Cisco WiSM...
Thank you by advance,
Alexis.

It depends on whom you talk to if its recommended or not. You don't look at what is posted on the downloads as that is not going to tell you how stable your environment will be. Recommended code versions change so much and its due to the length of time the code has been out. As far as the AP1700's, yes you are stuck on the v8.0 and to be honest, thats when you need to use the latest code, because in reality, the older codes had issues.
-Scott

WISM to WISM2 upgrade?

Similar Messages

Maybe you are looking for