Cisco Cisco Aironet 1200 Access Point Technical References
Cisco Structured Wireless-Aware Network (SWAN) Implementation Guide
Implementing the Cisco SWAN Framework
36
Cisco Structured Wireless-Aware Network (SWAN) Implementation Guide
OL-6217-01
When the building tool is open, follow the wizard steps to create a new building and import floorplans
for each of the building floors. Consult the CiscoWorks WLSE online help for assistance if necessary.
for each of the building floors. Consult the CiscoWorks WLSE online help for assistance if necessary.
When the buildings are created and floorplans are imported, managed access points are visible in the
lower left-hand pane of the Location Manager. Drag and drop the access points to the appropriate
locations on the floors. Accurate access point placement is important because the CiscoWorks WLSE
radio management tools use the Location Manager access point positions as a reference when making
internal computations.
lower left-hand pane of the Location Manager. Drag and drop the access points to the appropriate
locations on the floors. Accurate access point placement is important because the CiscoWorks WLSE
radio management tools use the Location Manager access point positions as a reference when making
internal computations.
As an optional step, access point antenna parameters can be configured by right-clicking on the access
point in the Location Manager. The antenna parameters include antenna type, azimuth, down-tilt (from
horizon), height, and any estimated cable loss.
point in the Location Manager. The antenna parameters include antenna type, azimuth, down-tilt (from
horizon), height, and any estimated cable loss.
When the buildings are created, the access points are placed, and any access point antenna parameters
are configured, the Cisco SWAN framework is ready for radio management.
are configured, the Cisco SWAN framework is ready for radio management.
Cisco SWAN Radio Management Features
An extensive discussion of the deployment and use of Cisco SWAN framework radio management
features is beyond the scope of this document. This section provides some guidance on the next steps for
Cisco SWAN framework radio management.
features is beyond the scope of this document. This section provides some guidance on the next steps for
Cisco SWAN framework radio management.
The Cisco SWAN framework radio management features use data gathered by three methods: access
point radio scan, client walkabout, and radio monitoring. The access point radio scan and radio
monitoring are required methods, and the client walkabout is an optional procedure.
point radio scan, client walkabout, and radio monitoring. The access point radio scan and radio
monitoring are required methods, and the client walkabout is an optional procedure.
Typically, the first radio management step is to run an access point radio scan. This scan can be run from
the Radio Manager > AP Radio Scan option in the CiscoWorks WLSE or as a step in the assisted site
survey tool. The scan is required to create an initial calibrated path loss model of the RF environment,
which considers path-loss between access points (resulting from natural attenuation factors in the RF
environment, such as walls) and identifies potential sources of contention in the RF environment.
the Radio Manager > AP Radio Scan option in the CiscoWorks WLSE or as a step in the assisted site
survey tool. The scan is required to create an initial calibrated path loss model of the RF environment,
which considers path-loss between access points (resulting from natural attenuation factors in the RF
environment, such as walls) and identifies potential sources of contention in the RF environment.
The client walkabout is an optional process in which a WLAN client walks the coverage environment,
associating with access points, and collecting specific data for the system to use in radio coverage
calculations. The client walkabout can be completed as a step in the assisted site survey tool or through
the Radio Manager > Client Walkabout interface. A good client walkabout requires a thorough
walkthrough of the coverage environment, ideally in a grid pattern. Data points are gathered
symmetrically across the coverage environment. If the client walkabout procedure cannot meet these
basic requirements, you should not do one.
associating with access points, and collecting specific data for the system to use in radio coverage
calculations. The client walkabout can be completed as a step in the assisted site survey tool or through
the Radio Manager > Client Walkabout interface. A good client walkabout requires a thorough
walkthrough of the coverage environment, ideally in a grid pattern. Data points are gathered
symmetrically across the coverage environment. If the client walkabout procedure cannot meet these
basic requirements, you should not do one.
Radio monitoring is a process in which infrastructure access points and optional authenticated and
associated WLAN clients regularly sample the RF environment during normal operations. The sampled
data is gathered by the WDS, aggregated, and passed to the CiscoWorks WLSE. Radio monitoring data
is used in coverage calculations, rogue access point detection, and radio interference detection. Radio
monitoring is required for rogue access point detection, interference detection, self-healing, and assisted
site re-survey.
associated WLAN clients regularly sample the RF environment during normal operations. The sampled
data is gathered by the WDS, aggregated, and passed to the CiscoWorks WLSE. Radio monitoring data
is used in coverage calculations, rogue access point detection, and radio interference detection. Radio
monitoring is required for rogue access point detection, interference detection, self-healing, and assisted
site re-survey.
Radio monitoring options are configured through the interface at Radio Manager > Radio Monitoring.
Both serving and non-serving channels configure access points for radio monitoring. The serving
channel is the normal operating channel for the access point. It is the channel on which associated
WLAN clients are served. When configured to monitor non-serving channels, the access point
periodically jumps off the serving channel to sample a non-serving channel, before resuming normal
WLAN client traffic processing. Non-serving channel radio monitoring typically only has a minimal
impact on normal WLAN data traffic.
Both serving and non-serving channels configure access points for radio monitoring. The serving
channel is the normal operating channel for the access point. It is the channel on which associated
WLAN clients are served. When configured to monitor non-serving channels, the access point
periodically jumps off the serving channel to sample a non-serving channel, before resuming normal
WLAN client traffic processing. Non-serving channel radio monitoring typically only has a minimal
impact on normal WLAN data traffic.
Cisco SWAN framework radio monitoring can also include WLAN clients that support the radio
management features. These clients include Cisco Aironet client adapters and WLAN client adapters
certified to the version 2 Cisco Compatible Extensions specification. When WLAN client monitoring is
management features. These clients include Cisco Aironet client adapters and WLAN client adapters
certified to the version 2 Cisco Compatible Extensions specification. When WLAN client monitoring is