Three wireless networking products designed for indoor, outdoor and large-scale enterprise networks seek to meet 802.11n "mainstream deployment" needs.
Trapeze Networks moved Monday to beef-up its 802.11n offerings by introducing three platforms including its scalable Mobility Exchange 800R that has been designed to accommodate massive enterprise networks.
The MX800R features Control and Provisioning of Wireless Access Points (CAPWAP) and line-rate centralized switching for as many as 128 dual-radio 802.11n APs with 8 Gbps line-rate wireless switching.
"After coverage and capacity concerns of early 802.11n adopters," said Rick Frazee, director of product marketing, in an email. "We now address the 802.11n mainstream deployment needs. With this massive adoption, the main theme is about affordability of very reliable 802.11n wireless networks." Frazee noted that Trapeze prepared for the current offering with its MP-82 AP platform, introduced two years ago.
The firm's new MP-522 is aimed at indoor deployments and has tamper-proof internal antennas and advanced power management capabilities. The platform works with Trapeze Networks' RingMaster planning and management tool, which provides easy and reliable deployment, the company said.
The MP-522E offers external antenna ports designed for hybrid indoor/outdoor usage. Its power over Ethernet (PoE) feature has been designed for outdoor applications and has a climate controlled enclosure and flexible options including a solar panel wit PoE.
Trapeze said the new offerings are priced to be close to the charge of 802.11 a/b/g offerings. "Many Trapeze Networks customers, especially in markets such as healthcare and education, have accelerated their adoption of 802.11n driven by new applications and a foundation of reliable architecture," said Trapeze Networks president Dhrupad Trivedi in a statement.
InformationWeek Tech Digest August 03, 2015The networking industry agrees that software-defined networking is the way of the future. So where are all the deployments? We take a look at where SDN is being deployed and what's getting in the way of deployments.