[c-nsp] WLSM to WiSM

[Childs, Aaron]

Although we didn't convert from a WLSM to WiSM (we just waited until the
WiSM was on the market at the suggestion of our reseller.)  I also have to
disagree with Andrew on two of his points.

WCS is a really cool product and if you are familiar with the web interface
on the WiSM controllers you'll pick up the WCS interface quickly.  The heat
maps in WCS is invaluable (although admittedly tedious to setup), AP
templates and Controller templates save a lot of time in configuring the
devices.  Plus all of the reports and alerts are very helpful as well.

Converting APs from autonomous to lightweight is a piece of cake.  When we
deployed the WiSM's I converted roughly 200 access points in 4 hours.  I
didn't do them all at once, I did a building at a time, walked over checked
connectivity, strength, etc...  Just use Cisco's conversion tool, create the
CSV to tell the tool the IP, u/p of the AP and watch the progress bar go.

Have a good day,
Aaron

-----------
Aaron Childs
Assistant Director, Networking
Westfield State College
http://www.wsc.ma.edu/it/


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Andrew Gabriel
Sent: Friday, April 23, 2010 5:09 AM
To: Clue Store
Cc: Cisco-nsp
Subject: Re: [c-nsp] WLSM to WiSM

WLSM and WiSM are two completely different  architectures, and seamless
mobility between them, if at all possible would probably not be worth the
effort.

Are you going to be converting a lot of APs? I would suggest converting only
recent models like the 1131 or 1242 series and later, trade-in the rest and
buy new lightweight APs for them. If you have 1020 series APs get rid of
them now as they wont work with current versions of the Unified Wireless
software.

I would suggest a clean setup  and cutover with the new WiSM as much as
possible rather than attempting simultaneously have both up and running or
slowly migration.

You can install the WiSM module, connect, prime and test your new APs (you
can disable the radios from the controller interface if needed to prevent
interference with the legacy system). Once all the APs are ready and primed,
set up your WLANs, enable only a test AP's radio and test the WLANs. Once
everything is tested, you can quickly enable the new APs and WLANs and
remove the old.

WCS by my experience is overrated and not so easy to use, given the same
budget I would take Airwave any day.

Converting APs over from autonomous to lightweight is a pain, and also
causes downtime, so budget permitting I would suggest that you trade-in and
replace them as much as possible, especially if they are not n-capable. If a
lot of the new APs you are buying are n-capable, you might also want to
review the AP placement or do a fresh survey, as well as make sure the APs
are connected to gig ports and existing POE/power injector can meet the
power requirements.


Regards,
Andrew Gabriel.
Network Engineer,
Enterprise Data Services

+91 98 41 41 40 19 (Mobile)
www.sanmina-sci.com


On Thu, Apr 22, 2010 at 8:21 PM, Clue Store <cluestore at gmail.com> wrote:

> Hi list,
>
>
> We are planning an upgrade on our 6500 WLSM controllers to the new WiSM
> controllers. We obviously will also be changing out old AP's the don't
> support LWAPP to newer ones that do. We are putting migration plans
> together
> today and plan to deploy within the next month. I have a few questions for
> anyone out there that's already been down this road. We will also be
> implementing the WCS system.
>
> If we have both controllers installed, does mobility work between the
> controllers ??
>
> I found this document http://bit.ly/dletG7 on cisco's site. Is this the
> recommended migration path that others have used??
>
> Any there any tips that would minimize downtime if mobility does not work
> between controllers??
>
> Anything else to consider before/during/after the deployment??
>
> TIA,
> Clue
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

CONFIDENTIALITY
This e-mail message and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged and/or
confidential information. If you are not the intended recipient of this
e-mail message, you are hereby notified that any dissemination, distribution
or copying of this e-mail message, and any attachments thereto, is strictly
prohibited.  If you have received this e-mail message in error, please
immediately notify the sender and permanently delete the original and any
copies of this email and any prints thereof.
ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS NOT
INTENDED AS A SUBSTITUTE FOR A WRITING.  Notwithstanding the Uniform
Electronic Transactions Act or the applicability of any other law of similar
substance and effect, absent an express statement to the contrary
hereinabove, this e-mail message its contents, and any attachments hereto
are not intended to represent an offer or acceptance to enter into a
contract and are not otherwise intended to bind the sender, Sanmina-SCI
Corporation (or any of its subsidiaries), or any other person or entity.
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6834 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20100423/c3224dad/attachment.bin>