Afternoon all,
We've had Bluesocket for many years but are now phasing out (we've become disillusioned with their direction and development) for ProCurve AP's using WESM modules on their 8200 series core switches. We're just completing a major refit at our Harrow site which will see ProCurve from core to edge to wireless. It's about 83 AP's to cover the site. The plan is to migrate the rest of our sites as part of our regular rolling upgrade process. We'll be using PCM and IDM to manage and secure the service.
Regards,
Lee.
_________________________________
Lee Rose
Information Systems Network Manager
University of Westminster
115 New Cavendish Street
London W1W6UW
E: [log in to unmask]
P: 020 7911 5000 ext 3757
F: 020 7911 5093
W: www.wmin.ac.uk
_________________________________
This e-mail and its attachments are intended for the above named only and may be confidential. If they have come to you in error you must not copy or show them to anyone, nor should you take any action based on them, other than to notify the error by replying to the sender.
please consider the environment - do you really need to print this email?
> -----Original Message-----
> From: Wireless Issues in the JANET community [mailto:WIRELESS-
> [log in to unmask]] On Behalf Of Matthew Newton
> Sent: 14 March 2008 16:15
> To: [log in to unmask]
> Subject: Re: Quick question
>
> Hi,
>
> We are using two Cisco 4404 Wireless controllers, with a
> Bluesocket box for web auth. The Cisco boxes and APs have been
> performing well. We don't use the WCS software at the moment as it
> seemed quite buggy in evaluation.
>
> The Bluesocket box has been going a bit downhill recently since
> their 5.x and 6.x software releases. If you used them as AP
> controllers too then they might be better as this seems to be
> where they are aiming. It used to be rock solid on 4.x, but since
> upgrading we've had several crashes and problems, which are slowly
> getting fixed. It would help a lot if they would let us have a
> shell on the box, too... :-(
>
> On Fri, Mar 14, 2008 at 03:40:30PM +0000, Kevin Hayton wrote:
> > We are finding that the management of the wireless network is easy with
> > these units, but we suspect that we will need WCS to make a single
> > management platform available. Currently we have to adjust configs on each
> > unit.
>
> I tend to use clusterssh [1] for command-line management of both
> WLC boxes at the same time. We script some things by pulling data
> with SNMP. You can generate commands and then paste them into cssh if
> you need to apply to both controllers.
>
> We maintain the main config off the boxes (you can get a basic
> config to work from, albeit slightly broken at the moment, with
> show running-config). This makes adding a new WLC easy - ssh in
> and paste the config. That's how we added the second one and
> deployment took ~20 minutes.
>
> > We have 170 APs with a further 50 to come on stream in the next 3 months.
> > Migration from fat to thin AP (LWAPP) is not totally straightforward, but
> > we have a procedure which seems to work well.
>
> We have around 50-60 APs and growing quite fast. Users are around
> 300 unique per day (100 concurrant) and increasing even faster.
>
> To convert Cisco APs to thin APs I wrote a perl script to auto
> upgrade the IOS and then flash the LWAP firmware. It made moving
> APs fairly easy, and then we just repatched them from their old
> connections to the main network. About 10 minutes downtime per AP.
> New APs are trivial - register in the DHCP servers and plug into
> the network.
>
> Cheers,
>
> Matthew
>
>
>
> [1] http://clusterssh.wiki.sourceforge.net/Main+Page
>
> --
> Matthew Newton, Ph.D. <[log in to unmask]>
>
> Systems Architect (UNIX and Networks), Network Services,
> I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom
>
> For IT help contact helpdesk extn. 2253, <[log in to unmask]>
--
The University of Westminster is a charity and a company limited by
guarantee. Registration number: 977818 England. Registered Office:
309 Regent Street, London W1B 2UW, UK
|
