Ok guys,

If no one can recommend anything, please can you let me know what you are running to give me an idea.

Thanks,

Matt

ummm....still no response!

There doesn't appear to be any help on this forum! :-(

Not ideal.

Recommend using WCS 4.2.110.0

Thanks!

What would you recommend for the WLC? We have a number of 4404's and WiSM's.

Thanks,

Matt

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

http://www.cisco.com/en/US/netsol/ns779/networking_solutions_program_category_home.html

WCS 4.2.110

WLC 4.2.130

LA 3.1.42.0

Mark

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.

dvr0 -

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 4.2.130.0. So in your opinion, what issues were you having and what is it about 4.2.176.0 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?

Regards,

Scott

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 4.2.130.0. 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 4.2.130.0 will be alright, or if I should upgrade to 4.2.176.0. 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.

Regards,

Scott

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.