Back in 2002, when the University of British Columbia in Vancouver decided it needed wireless classroom connectivity for enabling Internet-assisted teaching, the idea of “wireless switching” was a gleam in the industry’s eye.

For context, the university began deploying its Cisco 1200 Series-based distributed wireless LAN in September 2002 - the very same month that Symbol Technologies announced the industry’s first enterprise wireless switch. At that time, Cisco was still years away from acknowledging the potential benefits of centralized, switched WLAN architectures, preferring an architecture using stand-alone, intelligent access points (AP) that were provisioned and managed individually.

But when the university found itself under-budget on a fiber cabling project, it diverted the leftover funds to building the Cisco WLAN. Initially segregated from the wired network, the Wi-Fi network spanned 400 buildings and 1,000 acres to serve 35,000 full-time students, explains Marilyn Hay, manager of the university’s network management center. That 1,400-AP infrastructure is now migrating to the lightweight APs and switched architecture Cisco inherited from Airespace, which it acquired early last year.

UBC - which has since expanded to include another campus in Kelowna, B.C. - is also now using the Cisco Catalyst 6500 Wireless Services Module (WiSM) to converge its wireless and wired networks.

“We’re seeing lower costs to converge deployment of wired and wireless services to each building,” Hay says. For example, she says the university - which participates in Cisco’s beta programs - saved about $10,000 last fall in network management costs using the pre-release WiSM to configure networks in a new building with about 400 wired ports.

AP installation is faster and easier, she says. Previously, field technicians would assign an IP address to each AP, configure each for which channels to use for communication and management, and configure a Service Set Identifier (SSID) number.

“They'd do all that manually, then physically go to the location, install the AP and test for client-to-AP and AP-to-network connectivity,” Hay explains. “If the wrong IP address was assigned or an AP had to move to a different building, it would have to be physically reconfigured with the right IP address.”

Whitepapers

• The Trend from UNIX to Linux in SAP(r) Data Centers
• Best Practices for HP Servers and HP Enterprise Virtual Array in a Microsoft Exchange
• Best Practices for WAN Optimization with Data Replication
• Demonstrating the Business Value of Mobile Device Management in the Enterprise
• Managing Mobility: An IT Perspective
• The Quest For Competitiveness: Business Mobility And The Agile Organization

View more WIRELESS & MOBILE whitepapers

Webcasts

• Mobile Data Security
• Key Considerations for a Successful 802.11n Deployment
• The High-Touch Remote Helpdesk: Centralized Support for the Decentralized Organization
• From Wired to Wireless with Confidence - On Demand
• High Availability for SQL Server 2005 Using Array-Based Replication and Host-Based Mirroring Technologies
• Technical Overview of Exchange Server 2007 with HP Servers and Storage

View more WIRELESS & MOBILE webcasts

Special Reports

• Ehternet Services: WAN options mature

View more WIRELESS & MOBILE special reports