Cisco Cisco Aironet 1240 AG Access Point Notas de publicación
6
Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 12.4(10b)JA1
OL-15533-01
Installation Notes
Using a Switch That Does Not Support IEEE 802.3af Power Negotiation
If you use a switch to provide Power over Ethernet (PoE) to the access point and the switch does not
support the IEEE 802.3af power negotiation standard, select Pre-Standard Compatibility on the
System Software: System Configuration page.
support the IEEE 802.3af power negotiation standard, select Pre-Standard Compatibility on the
System Software: System Configuration page.
Using a Power Injector
If you use a power injector to provide power to the access point, select Power Injector on the System
Software: System Configuration page, and enter the MAC address of the switch port to which the access
point is connected.
Software: System Configuration page, and enter the MAC address of the switch port to which the access
point is connected.
Antenna Installation
For instructions on the proper installation and grounding of external antennas for 1240 series access
points, refer to the National Fire Protection Association’s NFPA 70, National Electrical Code, Article
810, and the Canadian Standards Association’s Canadian Electrical Code, Section 54.
points, refer to the National Fire Protection Association’s NFPA 70, National Electrical Code, Article
810, and the Canadian Standards Association’s Canadian Electrical Code, Section 54.
Warning
Do not install the antenna near overhead power lines or other electric light or power circuits, or
where it can come into contact with such circuits. When installing the antenna, take extreme care
not to come into contact with such circuits, as they may cause serious injury or death.
where it can come into contact with such circuits. When installing the antenna, take extreme care
not to come into contact with such circuits, as they may cause serious injury or death.
1400 Series Bridge
This section contains installation information for the 1400 series bridge.
Default SSID and Distance Settings Change When You Change Role in Radio Network
If the bridge’s SSID has not been changed from the default setting and you select Install Automatic
Mode as the bridge’s role in radio network setting, the SSID automatically changes from tsunami to
autoinstall. When you change the role in radio network from Install Automatic Mode to Root or
Non-Root, the SSID changes automatically from autoinstall back to tsunami. However, if you change
the SSID from its default setting, changing the role in radio network setting does not change the SSID.
Mode as the bridge’s role in radio network setting, the SSID automatically changes from tsunami to
autoinstall. When you change the role in radio network from Install Automatic Mode to Root or
Non-Root, the SSID changes automatically from autoinstall back to tsunami. However, if you change
the SSID from its default setting, changing the role in radio network setting does not change the SSID.
In Install Automatic Mode, the default distance setting is 61.5 mi. (99 km). When you change the role
in radio network from Install Automatic Mode to Root or Non-Root, the distance setting changes
automatically from 61.5 mi. (99 km) to 0 mi. (0 km).
in radio network from Install Automatic Mode to Root or Non-Root, the distance setting changes
automatically from 61.5 mi. (99 km) to 0 mi. (0 km).
Default Encryption Key 2 Is Set by Bridge
The encryption key in slot 2 is the transmit key by default. If you enable WEP with MIC, use the same
WEP key as the transmit key in the same key slot on both root and non root bridges.
WEP key as the transmit key in the same key slot on both root and non root bridges.
Limitation to PAgP Redundancy on Switches Connected by Bridge Links
When two switches configured for Port Aggregation Protocol (PAgP) are connected by redundant
wireless bridge links, the PAgP change-over takes at least 30 seconds, which is too slow to maintain TCP
sessions from one port to another.
wireless bridge links, the PAgP change-over takes at least 30 seconds, which is too slow to maintain TCP
sessions from one port to another.