Cisco WAP121 Administration Manual page 62

Wireless Settings
Radio
Cisco Small Business WAP121 and WAP321 Wireless-N Access Point with PoE
interval from the a and g definition of 800 nanoseconds to 400 nanoseconds.
Reducing the guard interval can yield a 10% improvement in data
throughput.
The client with which the WAP device is communicating must also support
the short guard interval.
Select one of these options:
- Yes—The WAP device transmits data using a 400 ns guard Interval
when communicating with clients that also support the short guard
interval.
- No—The WAP device transmits data using an 800 ns guard interval.
• Protection —The protection feature contains rules to guarantee that 802. 1 1
transmissions do not cause interference with legacy stations or applications.
By default, these protection mechanisms are enabled (Auto). With protection
enabled, protection mechanisms will be invoked if legacy devices are within
range of the WAP device.
You can disable (Off) these protection mechanisms; however, when
protection is off, legacy clients or APs within range can be affected by
802. 1 1n transmissions. Protection is also available when the mode is
802. 1 1b/g. When protection is enabled in this mode, it protects 802. 1 1b
clients and APs from 802. 1 1g transmissions.
This setting does not affect the ability of the client to associate with
NOTE
the WAP device.
• Beacon Interval—The interval between the transmission of beacon frames.
The WAP device transmits these at regular intervals to announce the
existence of the wireless network. The default behavior is to send a beacon
frame once every 100 milliseconds (or 10 per second).
Enter an integer value from 20 to 2000 milliseconds.
• DTIM Period—The Delivery Traffic Information Map (DTIM) period. Enter an
integer from 1 to 255 beacons.
The DTIM message is an element included in some Beacon frames. It
indicates which client stations, currently sleeping in low-power mode, have
data buffered on the WAP device awaiting pick-up.
The DTIM period that you specify indicates how often the clients served by
this WAP device should check for buffered data still on the WAP device
awaiting pickup.
5
62