Präsentation zum Thema: "Meru Networks Virtualisiertes Wireless Lan"— Präsentation transkript:
1 Meru Networks Virtualisiertes Wireless Lan 2011 | Harald Röder, Systems Engineer D-A-CH
2 Meru Networks Firmenüberblick Gegründet in 2002, Sunnyvale, KalifornienVertrieb in Nordamerika, Asien, Pazifik, Europa und Mittlerer Osten / 300+ MitarbeiterNASDAQ notiert – “MERU”Leitsatz: Wir liefern “Wireless-like-Wire™“ Technologie in UnternehmenVirtualisierung in kabellosen NetzwerkenÜber 4000 Kunden in 55 Ländern weltweitTechnologieführerVorreiter bei n in UnternehmenBeste Sprach- und VideointegrationHohe Dichte an Endgeräten und WLAN BenutzerUnterbrechungsfreie und nahtlose MobilitätNow let’s talk a little about Meru.Founded in 2002 in Sunnyvale, we now have operations in North America, APAC, EMEA. We recently became a public company, listed on the NASDAQ.Our mission is both simple and complex: To deliver wireless like wire, both in terms of experience and performance. That’s what Meru does. We deliver wireless like wire.We now have over 3500 customers in 44 countries. Our customers tend to be medium-to-large enterprises. Since introduction of our first products, we have established leadership in several areas:- first enterprise vendor to introduce n- designed our architecture from day one with latency-intolerant applications in mind- this makes us undisputed leader in wireless VoIP, high-definition video- have the ability to support converged applications at high scale: video, voice and data at high QoS with large numbers of users, stationary or mobile- entered market for fixed-mobile convergence early on (2005), now the leader in production FMC deploymentsleadership in delivering service assurance, meeting the same service expectations that customers have from a wired environment
3 Meru Wireless Lan Virtualisiert und optimiert die Ressourcen Früheres ModellMeru-ModellMehrwertMikrozellenVirtualisiertNeue Access Points werden ohne Konfiguration oder Funkfeldmessung einfach hinzugefügtUnterbrechungsfreies Umschalten zwischen AP´sHubSwitchVerteilungEigener “Access Point” pro EndgerätÜbertragungszeit wird anhand des Endgerätes festgelegtQuality of Service per ApplikationOne question that many people have is: What’s the difference between the Meru architecture and the other architectures available from other vendors.The Meru system uses what we call a Virtualized Wireless LAN architecture. This is fundamentally different from legacy wireless LANs.The legacy wireless LAN on the left uses what is called a microcell architecture. The Meru Virtualized wireless LAN is on the right.In the legacy architecture, each access point cannot be on the same channel as its neighbor. So there is an elaborate site survey and planning process to try to solve an intractable problem, which is: How do you place the access points not so far apart that there’s a gap in coverage but not so close that they interfere with each other?It’s an intricate process. You start with a design or a plan, then deploy the access points. If there’s a gap in coverage, you deploy a new access point, but you need to find a new channel for it so that it doesn’t interfere with neighboring access points. So you repeat the site survey: find new channels and power settings for each access point.You need to do the same if you need more capacity: Adding more access points means you have to redo the site survey and calculate new channel and power settings. You also need to repeat the site survey if the RF characteristics of an area change: if there are new walls, new furniture or more people. It’s a time-intensive, laborious process.Meru came up with a way to coordinate access points so that every access point is on the same channel as its neighbors. To deploy a Meru Virtualized Wireless LAN, you just decide to install an access point every 20,30 or 40 feet, then plug them in and power them up. If there’s a gap in coverage, just stick up another access point. It’s as simple as screwing in a light bulb.Eventually you have the whole floor covered. And because we don’t have to play with the power levels, you can run the access points at full power. This means you need fewer access points than with a microcell architecture, typically around 30% fewer.This is called a single channel approach because all of the APs are on one channel. If you want to add capacity, you can just add another set of APs on another channel. You can do this for every channel that’s available, layering channel after channel. By doing this, we harness every MHz and create an RF pool.Layering channels is very similar to stacking Ethernet switches. In a wired environment, you add capacity by buying a new switch and stacking it on top of the first. In a Meru wireless environment, you just add another single channel layer.In the legacy microcell architecture, the client has control. In a Meru Virtualized Wireless LAN architecture, the infrastructure is in control.Why is this important? If you think about when Ethernet hubs were first introduced, you would connect a desktop system to a hub and there was a free-for-all: Each desktop would try to grab as much bandwidth as it could. That’s OK with 3 or 4 devices, but it doesn’t scale. More devices mean chaos.In the 80s, the dominant enterprise networking architecture was IBM SNA. Hubs came in and made some impact on the enterprise at the departmental level, but no enterprise was going to run its business on Ethernet hubs. Then switches were introduced in the 90s.The big difference between hubs and switches was that switches took control away from the client. They gave each desktop its own port, almost its own network. Control went back into the infrastructure, letting IT shape bandwidth, security and everything else. That’s exactly what we do at Meru.The Meru architecture is like a cellular network. As smart as a smart phone is, it has no control over when to hand off from one base station to the next. Everything is controlled by the infrastructure.The infrastructure has global knowledge of the network, so it is much better placed than a client to make connectivity decisions. This lets the network carry a much higher load, deliver quality-of-service, deliver seamless mobility.At Meru, we take control away from the device and we give each device a Virtual Port. With that Virtual Port, we can shape the bandwidth that the device gets, support different security profiles, determine which client’s traffic gets priority.Just like switched Ethernet, all this is done on a per-client basis. We have eliminated the disorder and chaos that happens in the hub-like environment of legacy microcell networks and delivered Ethernet switch-like predictability and reliability.Our competitors sometimes talk about single channel or virtualization, so you have to peel back the marketing and look at the architecture. Their architecture is still microcell-based.To recap, what did we do?- We virtualized the RF space so that we could coordinate APs and deploy them in a single channel.- Then we created a resource pool by layering these channels to harness every MHz in the enterprise.- And with the virtual Port capability, we partitioned the RF space in an optimal fashion to deliver the highest quality-of-service for each device and application.We virtualize and then we optimize. Meru is absolutely unique in doing that.
4 Die Meru Networks “Virtual Cell” Technologie Alle Endgeräte “sehen” nur eine virtualisierte WLAN ZelleFunktionenNetzwerk KontrolleOptimierte ReichweiteStörungsfreies RoamingBessere SpektrumaufteilungVorteileSchnelle KonfigurationHohe BelastbarkeitMöglichkeit Interferenzen zu umgehenBeste Mobilität
5 Die Weiterentwicklung: Meru Networks “Virtual Port” Technolgie Jedes Endgerät bekommt seinen eigenen virtuellen APFunktionenNoch bessere KontrolleIsolierung der EndgeräteMultimedia pro EndgerätVorteileGrosse Dichte an StationenStabilitätWireless wird berechenbarHohe Performance
6 Unsere Antwort auf Skalierbarkeit: …für extrem hohe Anforderungen an Bandbreite und vielen EndgerätenMikrozellen AnsatzKanal ÜberlagerungCh. 1Ch. 11Channel LayerCh. 11Ch. 11Ch. 6Ch. 1Channel LayerCh. 1Ch. 11Ch. 6Channel LayerCh. 1Meru’s single channel architecture enables better performance and a dramatic reduction in installation and IT management costs:Fewer AP’s, wired infrastructure and cable pullsElimination of channel planning for site surveyOperating and maintenance costs related to adds and changesUsing all three non-overlapping channels at any location**, Meru’s 4th generation architecture achieves far higher system capacity than our competitors with far lower complexity:Channels can be stacked as needed to add capacity802.11n ready without a forklift upgradeNeue Planung mit mehr ZellenHinzufügen einer neuen Kanalebene
7 Der Test: Perfekte Unterstützung bei vielen Endgeräten mit virtualisiertem WLAN Meru setzte als erster Hersteller ein Szenario auf, dass gleichzeitig 500 Endgeräte auf einer Fläche von 150 m2 mit WLAN vernetzte. .Meru conducted an industry first WLAN 500TM demonstration, where 500 client devices (laptops, smartphones, tablets, etc.) ran voice, video and data applications simultaneously in a 500 square foot area. Meru’s WLAN 500 demo proved that Meru’s virtualized WLAN solution supports customer locations where highly dense areas, resulting in zero disruption or dropped calls. Simply, the Meru WLAN 500 demonstration avoided the effects of interference that are inherent in microcell wireless LANs.Besuchen Sie die Meru Webseite oder suchen Sie bei YouTube nach “WLAN 500 Demo”
8 Verteilte Unternehmen Das ProduktportfolioNetwork Manager / E(z) RFZentrale VerwaltungSecurity ServicesService ModuleScaled portfolio to meet your needs; value on the software side for management – need another slides on management, ease of app, deployment, performance – picture of man on the beach – catch the criminals before it happens..EZ-RF: this is how we deliver service assurance..Meru System DirectorKleine AussenstellenZweigstellen1-30AP’sRegional Büros1-150 AP’sNiederlassungCampus1-300 AP’sVerteilte Unternehmen1,000+ APs8
9 E(z) RF, Network Manager Eine Plattform – viele FunktionenWie kann ich das Netzwerk effizient überwachen?EzRF Compliance ManagerKann das Netzwerk proaktiv getestet werden?Wie sieht aktuell meine Funkaus-leuchtung aus?Kann ich mir den Sicherheitszustand des Netzwerkes anzeigen lassen?Bleiben Verbindungsprobleme in der Vergangenheit auch aktuell darstellbar?Wie werden Störungen z. B. von Mikrowellen oder Dect-Geräten erkannt?Gibt es die Möglichkeit “Compliance-Reports” zu erstellen?EzRFVisualization ManagerCompliance ManagerSpectrum AnalyzerServices Assurance ManagerTroubleshooting ManagerWireless Intrusion Prevention SystemNetwork Manager
10 Danke! Harald Röder firstname.lastname@example.org +49 89 21557931 Danke!