Cisco Cisco Aironet 350 Wireless Bridge Guía De Información

Descargar
Página de 9
Q. Can a wireless bridge support Netflow, just like Cisco routers?
A. No. Cisco Aironet Wireless Bridges do not support Netflow. However, you can use SNMP
MIBs to report the number of input and output packets and bytes.
Q. Can a Cisco 1410 Wireless Bridge support Wi−Fi Protected Access2
(WPA2) or Advanced Encryption Standard (AES)?
A. No. The Cisco 1410 Wireless Bridge does not support WPA2 or AES.
Q. What is the maximum range covered by a 1310 Wireless Bridge when
acting in bridge mode as well as in access point (AP) mode?
A. The 1310 series has the antenna built into the unit. If the bridge acts in the bridge mode, it
can give a bridge − bridge range of several kilometers. If the bridge acts in AP mode, then
you will be restricted to the range that the clients can achieve.
The client might see the bridge even from 1 kilometer away. However, it will not have the
power to reach back and connect to the bridge. A wireless client can access and reach an
802.11g AP or 1310 that acts as an AP at about 200 meters maximum, or probably a lesser
distance.
Q. Is it possible to combine the wall mount kit with an internal antenna
on the 1300 Bridge?
A. No. The internal antenna would point into the wall when you use the wall mount. Also, the
wall mount can accommodate the antenna.
Q. Is it possible to adjust a 1310 Wireless Bridge with an internal antenna
that is installed on a wall mount kit, or is it fixed?
A. It is a fixed solution. Therefore, you should use an external antenna when you use a wall
mount kit.
Related Information
Password Recovery Procedure for the Cisco Aironet Equipment
• 
Troubleshooting Problems Affecting Radio Frequency Communication
• 
Troubleshooting Connectivity in a Wireless LAN Network
• 
Cisco Aironet 350 Series Tech Notes
• 
Cisco Wireless Downloads (
 registered customers only
)
• 
Technical Support & Documentation − Cisco Systems
• 
Contacts & Feedback | Help | Site Map
© 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
Updated: Oct 19, 2009
Document ID: 16041