I'm currently running both a WCS appliance and a windows server WCS on version 188.8.131.52
They are managing around 1000 AP's that are in a Hospital environment. They are using Vocera badges.
The controllers are all running v184.108.40.206
What are my best upgrade options for both WCS and the controllers? I'm looking for stability, improvements and fixes.
Any ideas folks??
Seems WLC v4.2.130 is pretty much stable from what I've read so far?
Also, thinking of upgrading WCS to 4.2.110
Good or bad?
Vocera only recommends using code version 4.2.130 only (Vocera KB Article #735). The tech support wouldn't even talk with us until after we downgraded to 4.2.130.
I would go with the "assurewave" controller software
We've had better luck with 4.2.176 as there have been several critical bugs fixed since 4.2.130, that were impacting us. We have Vocera, Spectralink and 7921.
Would you care to elaborate on what you had better luck with? From the release notes, it would appear as though no new features were introduced, and only one open caveat was resolved since 220.127.116.11. So in your opinion, what issues were you having and what is it about 18.104.22.168 that solved them? In addition, you are using Vocera, Spectralink and 7921s. Were any of your issues targeted to one client device type vs. the others?
We ran a pretty stable 4.0.217 for about a year with no big issues that I can remember. We started getting 1252s and needed to upgrade. We finally jumped in with 4.2.130 and had some pain. We started having issues with Vocera roaming, and Dell 1470/90 adapters had issues also. We've seen the following issues (CSCsm65043, CSCsi26248, CSCsi72578, CSCsq57697, CSCsu44970, CSCsr40109, CSCsv21441, and CSCsv21464). Some have been fixed in 4.2.173/176, but with the latest security advisory, it makes sense to run 4.2.176.
With 19 pages of open caveats in 4.2.176, it's a crap shoot for sure, but probably the best you can do as it's a MD release. Also we have depreciated the Spectralink and only run 7921 and Vocera.
Thanks for the reply, I appreciate it. I'll have to look up what bug issues you experienced with 22.214.171.124. I'm going to assume in your environment that you are using L3 roaming? How many Vocera badges and were they on multiple VLANs? I'm curious b/c I'm about to deploy a single controller Vocera deployment, and I'm trying to decide for myself if 126.96.36.199 will be alright, or if I should upgrade to 188.8.131.52. Are your Vocera badges B1000A or the newer B2000A? Are they configured for subnet roaming? B1000A are NOT configured for subnet roaming by default, whereas B2000A are.
The Vocera environment is at two 400 bed hospitals. Each facility has it's own WISM and dedicated Vocera subnet terminated on the WISM. 120 AP at SiteA and 220 AP at SiteB. Around 100 badges at one site and 50 at the other, with a mix of 1000 and 2000 badges. Subnet roaming is off as this is handled by L3 LWAPP. I might add we've seen some of the 1000 badges not associate to 1252's. We have TAC working on it but so far no answers, seems to be sporadic. Let me know if you have additional questions.