Keys to Enterprise WLAN Reliability
•Download as PPT, PDF•
0 likes•1,065 views
Mark Cowtan, Director of Marketing at Trapeze Networks discusses how to achieve wire-like reliability on Wireless LANs
![Today’s Speakers ,[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Keys to Enterprise WLAN Reliability
Similar to Keys to Enterprise WLAN Reliability (20)
Recently uploaded
Recently uploaded (20)
Keys to Enterprise WLAN Reliability
- 1. Keys to Enterprise WLAN Reliability How to Achieve Wire-like Reliability Over the Air October 28, 2010
- 4. WLAN Reliability – The Tipping Point Reliability Unwired Enterprise a b a/b/g Outdoor Access Mobility WIDS/WIPS Voice RTLS Telemetry Asset Management Multi Media Guest Access Security Management LAN Extension Performance Scalability Complete Coverage
- 5. Rapid Growth in Devices and Utilization Rapid Device Proliferation (SmartPhones and Other Clients) CAGR 90% CAGR 25% CAGR 44% Source: Gartner 04/2010 Spring Summer Break Fall 3x Growth in Sessions (Multiple Devices per Student) ~50,000 Students 3x Source: UoM 10/2010
- 7. Is Wire-like Reliability Achievable? LAN Access Stationary user Dedicated bandwidth Fixed capacity WLAN Access Mobile user Shared bandwidth Variable capacity
- 16. Distributed Cryptography Scales with APs Clear Encrytped Centralized Cryptography Distributed Cryptography Clear Mgmt Tunnel WPA2 etc
- 27. Tradeoff: Coverage or Capacity Coverage Capacity $/Mbps 100 Users 40 MHz Channels Identical area $/Sq. Ft. $/Mbps $/Sq. Ft. $/Mbps 3x Access points 2x Total cost 7x Avg throughput
- 28. Client Balancing Across APs and Bands 5 Ghz 1 2 2.4 Ghz Point of Entry Most clients default to 2.4Ghz on the AP with strongest signal
- 31. Separate Management for Everything! Closed system, independent services, limited integration INTERNET COMMUNICATION SURVEILLANCE ASSET TRACKING
- 33. Fully Integrated Services Enables SLAs WIDS/WIPS Server RF Firewall Location Appliance FCAPS Management WIDS/WIPS Server RF Firewall Location Appliance FCAPS & Services Management Typical WLAN Management Unified WLAN Management Guest Server Guest Server
Editor's Notes
- The traditional approach to redundancy is to have a fully-loaded, fully-configured device ready to back up any other device which may fail. But many-to-one redundancy is inefficient, as ninety nine percent of the time, the back up device sits idle. And by the time you need it, chances are, it has the wrong configuration anyway, because no-one has time to test disaster recovery! Configuring redundancy, one device at a time - each with a unique configuration - is also extremely complex and time consuming, and requires constant maintenance whenever there are adds, moves or changes. Trapeze’s approach is different. Think of it as “controller virtualization ”. Controllers are configured as a cluster, not one by one, and they all get a common configuration that allows each controller to act as a backup for any other. This many-to-many redundancy keeps all devices in service , so you know they work. This approach accommodates device or network failures, enables instant capacity scaling and allows in-service upgrades, all with zero downtime – this is simply not possible with other vendors systems. Amazingly, configuration management is also much easier, taking less than 20% of the time of traditional one-to-one, or many-to-one redundancy configuration. With Trapeze’s clustered approach a single configuration containing all service profiles, is loaded to only one controller – no matter how large the network. After that, the network configures itself, automatically.
- In normal operation, you want APs to boot from nearby controllers to avoid wasting backbone or WAN bandwidth. But in a fail over condition, the APs should use different controllers, elsewhere in the network. This is done by having multiple “Affinity Groups” each of which contains only a subset of all the controllers that make up a virtual controller cluster. For example, imagine a large campus in which the primary data center is experiencing power problems. This “AP Affinity” feature allows an AP that normally boots from controllers in Affinity Group 1 in the unstable “primary data center”, to fail over to Affinity group 2 located in the stable “alternate data center”. This provides complete protection against Data Center or Wiring-Closet black-out.
- DONE
- DONE
- Most Wi-Fi devices default to 2.4Ghz (better range) Increases contention for spectrum, while 5Ghz virtually unused We steer 5Ghz-capable clients (802.11a/n) to 5Ghz Completely transparent - No duplication of SSID, VLAN required Reserves 2.4Ghz for Phones, Tags, Scanners, and legacy clients Trapeze has hosted the SuperComputing show in 2006 and 2007. In 2007 we implemented this feature and immediately saw over 50% of 1100 concurrent clients moving from 2.4Ghz to 5Ghz.
- But today, all mobility services are separately installed, configured, and managed. Instead of collaborating, they are competing for resources, unaware of each other or user context User mobility, literally makes resource management a moving target – that’s hard enough, but if you also ignore information that you already have access to, because its too cryptic, or you have no way to correlate it, then its easy to see that existing solutions will never be able to honor SLAs when the network is saturated, or the air space is dirty, or part of the network has failed.
- DONE FMC - NEW IMAGE FOR PDA Hospitals are deploying advanced clinical applications for their mobile workforce for 4 main reasons: COMPLIANCE To meet regulatory compliance requirements of JHACO, Sarbannes Oxley, and HIPAA. COST CONTROL To maximize profitability by reducing cost, and increasing efficiency of their clinical staff. PHYSICIAN RETENTION In addition by taking these measures they are also hoping to attract and retain the best physicians by offering them the most efficient place to work. PATIENT CARE Hospitals are deploying EMR systems and advanced clinical applications to reduce medical errors and improve patient care. But their success depends on those applications being mobile. While most hospitals have already begun deploying wireless LANs, many are finding that wireless mobility is more elusive than they expected. Unfortunately, without medical-grade mobility most of these initiatives are doomed to mediocrity, leaving physicians frustrated, and costing hundreds of '000s to fix.