Cisco Cisco Aironet 1310 Access Point Bridge

Página de 26
 
12
Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 12.4(21a)JA1
OL-20668-01
  Important Notes
9.
The Install LED starts to blink amber to show that the bridge is searching for a root bridge.
10.
When the bridge associates to a root bridge, the Install LED turns amber.
11.
When the bridge becomes a root bridge and is waiting for a nonroot bridge to associate, the Install 
LED blinks green.
12.
When the root bridge has a nonroot bridge associated, the Install LED turns green.
Bridge Cannot Detect Simultaneous Image Downloads
Do not attempt to load software images into the bridge from both a Telnet session and a console session 
simultaneously. The bridge cannot detect that two images are being loaded at the same time. For best 
results, use the archive download command in the CLI.
Bridge Cannot Detect Invalid Software When Using copy Command 
The bridge sometimes cannot detect invalid software images when you load software using the copy 
command. For best results, use the archive download command in the CLI to load new software.
Telnet Session Sometimes Hangs or Will Not Start During Heavy Traffic
When the bridge is transmitting and receiving heavy traffic, you sometimes cannot start a Telnet session 
and some existing Telnet sessions halt. However, this behavior is expected because the bridge gives top 
priority to data traffic and a lower priority to Telnet traffic.
Important Notes
This section describes important information about access points and bridges.
Access Point Creates File When Radar is Detected on a DFS Channel
When an access point detects a radar on a DFS channel, the access point creates a file in its flash memory. 
The file is based on the 802.11a radio serial number and contains the channel numbers on which the radar 
is detected. This is an expected behavior and you should not remove this file.
Access Points Send Multicast and Management Frames at Highest Basic Rate
Access points running recent Cisco IOS versions are transmitting multicast and management frames at 
the highest configured basic rate, and is a situation that could causes reliability problems.
Access points running LWAPP or autonomous IOS should transmit multicast and management frames at 
the lowest configured basic rate. This is necessary in order to provide for good coverage at the cell's 
edge, especially for unacknowledged multicast transmissions where multicast wireless transmissions 
may fail to be received. 
Since multicast frames are not retransmitted at the MAC layer, stations at the edge of the cell may fail 
to receive them successfully. If reliable reception is a goal, then multicasts should be transmitted at a 
low data rate. If support for high data rate multicasts is required, then it may be useful to shrink the cell 
size and to disable all lower data rates.