Техническая Инструкция для Cisco Cisco 2000 Series Wireless LAN Controller
more financially viable, and provide a superset of features and functionality in comparison to a REAP−only
deployment.
deployment.
As with all 1000 Series APs, a single 1030 AP covers approximately 5,000 square feet. This depends on the
radio frequency (RF) propagation characteristics at each site, and the required number of wireless users and
their throughput needs. In most common deployments, a single 1000 Series AP can support 12 users at
512kbps on 802.11b and 12 users at 2 mbps on 802.11a, simultaneously. As with all 802.11−based
technologies, media access is shared. Therefore, when more users join the wireless AP, throughput is shared
accordingly. Again, as user density increases and/or throughput requirements rise, consider the addition of a
local WLC to save on cost−per−user and to increase functionality.
radio frequency (RF) propagation characteristics at each site, and the required number of wireless users and
their throughput needs. In most common deployments, a single 1000 Series AP can support 12 users at
512kbps on 802.11b and 12 users at 2 mbps on 802.11a, simultaneously. As with all 802.11−based
technologies, media access is shared. Therefore, when more users join the wireless AP, throughput is shared
accordingly. Again, as user density increases and/or throughput requirements rise, consider the addition of a
local WLC to save on cost−per−user and to increase functionality.
Note: You can configure the 1030 REAPs to operate identically to other LAPs. Therefore, when WLCs are
added to scale the size of remote sites WLAN infrastructures, existing REAP investments can continue to be
leveraged.
added to scale the size of remote sites WLAN infrastructures, existing REAP investments can continue to be
leveraged.
Deploy REAP
Because the 1030 REAP is designed to be placed at remote sites away from the WLC infrastructure, the
traditional, zero−touch methods LAPs used to discover and join controllers (such as DHCP option 43) are
usually not employed. Instead, the LAP must first be primed in order to allow the 1030 to connect to a WLC
back at a central site.
traditional, zero−touch methods LAPs used to discover and join controllers (such as DHCP option 43) are
usually not employed. Instead, the LAP must first be primed in order to allow the 1030 to connect to a WLC
back at a central site.
Priming is a process where LAPs are given a list of WLCs to which they can connect. Once joined to a single
WLC, LAPs are informed of all controllers in the mobility group and equipped with all the information
needed to join any controller in the group. Refer to Deploying Cisco 440X Series Wireless LAN Controllers
for more information on mobility groups, load balancing, and controller redundancy.
WLC, LAPs are informed of all controllers in the mobility group and equipped with all the information
needed to join any controller in the group. Refer to Deploying Cisco 440X Series Wireless LAN Controllers
for more information on mobility groups, load balancing, and controller redundancy.
In order to perform this at the central site, such as a network operations center (NOC) or data center, REAPs
must be connected to the wired network. This allows them to discover a single WLC. Once joined to a
controller, the LAPs download the LAP OS version that corresponds with the WLAN infrastructure. Then, the
IP addresses of all WLCs in the mobility group are transferred to the APs. This allows the APs, when powered
up at their remote sites, to discover and join the least utilized controller from their lists, provided IP
connectivity is available.
must be connected to the wired network. This allows them to discover a single WLC. Once joined to a
controller, the LAPs download the LAP OS version that corresponds with the WLAN infrastructure. Then, the
IP addresses of all WLCs in the mobility group are transferred to the APs. This allows the APs, when powered
up at their remote sites, to discover and join the least utilized controller from their lists, provided IP
connectivity is available.
Note: DHCP option 43 and Domain Name System (DNS) lookup work with REAPs, as well. Refer to
Deploying Cisco 440X Series Wireless LAN Controllers for information on how to configure DHCP or DNS
at remote sites in order to allow APs to find central controllers.
Deploying Cisco 440X Series Wireless LAN Controllers for information on how to configure DHCP or DNS
at remote sites in order to allow APs to find central controllers.
At this time, the 1030 can be given static addresses if desired. This ensures that the IP addressing scheme
matches the destination remote site. Also, WLCs names can be input in order to detail which three controllers
each LAP will attempt to connect. If these three fail, the automatic load−balancing functionality of LWAPP
allows the LAP to choose the least−loaded AP from the remaining list of controllers in the cluster. The edit of
the LAP configuration can be done through the WLC command−line interface (CLI) or GUI, or with greater
ease, through the WCS.
matches the destination remote site. Also, WLCs names can be input in order to detail which three controllers
each LAP will attempt to connect. If these three fail, the automatic load−balancing functionality of LWAPP
allows the LAP to choose the least−loaded AP from the remaining list of controllers in the cluster. The edit of
the LAP configuration can be done through the WLC command−line interface (CLI) or GUI, or with greater
ease, through the WCS.
Note: 1030 REAPs require the WLCs to which they connect to operate in Layer 3 LWAPP mode. This means
the controllers need to be given IP addresses. Also, the WLCs require a DHCP server to be available at each
remote site, or static addresses must be assigned during the priming process. The DHCP functionality
embedded in controllers cannot be used to provide addresses to 1030s LAPs or their users.
the controllers need to be given IP addresses. Also, the WLCs require a DHCP server to be available at each
remote site, or static addresses must be assigned during the priming process. The DHCP functionality
embedded in controllers cannot be used to provide addresses to 1030s LAPs or their users.
Before you power off the 1030 LAPs to ship out to remote sites, ensure that each 1030 is set to REAP mode.
This is very important because the default for all LAPs is to perform regular, local functionality, and 1030s
need to be set to perform REAP functionality. This can be done at the LAP level through the controller CLI or
This is very important because the default for all LAPs is to perform regular, local functionality, and 1030s
need to be set to perform REAP functionality. This can be done at the LAP level through the controller CLI or