Руководство По Проектированию для Cisco Cisco Aironet 350 Mini-PCI Wireless LAN Client Adapter
2-31
Enterprise Mobility 4.1 Design Guide
OL-14435-01
Chapter 2 Cisco Unified Wireless Technology and Architecture
Operation and Maintenance
•
Traffic engineering—Any WLAN traffic that is tunneled to a centralized WLC is then routed from
the location of the WLC to its end destination in the network. Depending on the distance of the
tunnel and location of the WLC, WLAN client traffic may not otherwise follow an optimal path to
a given destination. In the case of a traditional access topology or distributed WLC deployment,
client traffic enters the network at the edge and is optimally routed from that point based on
destination address.
the location of the WLC to its end destination in the network. Depending on the distance of the
tunnel and location of the WLC, WLAN client traffic may not otherwise follow an optimal path to
a given destination. In the case of a traditional access topology or distributed WLC deployment,
client traffic enters the network at the edge and is optimally routed from that point based on
destination address.
With that said, the longer tunnels and potentially inefficient traffic flows associated with a centralized
deployment model can be partially mitigated by positioning the WLCs in that part of the network where
most of the client traffic is destined (for example, a data center). Given the fact that most enterprise
client traffic goes to servers in the data center and the enterprise backbone network is of low latency,
any overhead associated with inefficient traffic flow would be negligible, and would be of no
consequence when considering a centralized deployment model over a distributed one.
deployment model can be partially mitigated by positioning the WLCs in that part of the network where
most of the client traffic is destined (for example, a data center). Given the fact that most enterprise
client traffic goes to servers in the data center and the enterprise backbone network is of low latency,
any overhead associated with inefficient traffic flow would be negligible, and would be of no
consequence when considering a centralized deployment model over a distributed one.
For most enterprises, the introduction of a WLAN does not result in the introduction of new
applications, at least not immediately. Therefore, the addition of a Cisco Unified Wireless network
alone is not likely to have a significant impact on campus backbone traffic volumes.
applications, at least not immediately. Therefore, the addition of a Cisco Unified Wireless network
alone is not likely to have a significant impact on campus backbone traffic volumes.
AP Connectivity
APs should be on different subnets from the end users. This is consistent with general best practice
guidelines that specify that infrastructure management interfaces should be on a separate subnet from
end users. Additionally, Cisco recommends that Catalyst Integrated Security Features (CISF) be enabled
on the LWAPP AP switch ports to provide additional protection to the WLAN infrastructure. (H-REAP
AP connectivity is discussed in
guidelines that specify that infrastructure management interfaces should be on a separate subnet from
end users. Additionally, Cisco recommends that Catalyst Integrated Security Features (CISF) be enabled
on the LWAPP AP switch ports to provide additional protection to the WLAN infrastructure. (H-REAP
AP connectivity is discussed in
DHCP is generally the recommended method for AP address assignment, because it provides a simple
mechanism for providing up-to-date WLC address information for ease of deployment. A static IP
address can be assigned to APs, but requires more planning and individual configuration. Only APs with
console ports permit static IP address configuration.
mechanism for providing up-to-date WLC address information for ease of deployment. A static IP
address can be assigned to APs, but requires more planning and individual configuration. Only APs with
console ports permit static IP address configuration.
In order to effectively offer WLAN QoS within the Cisco Unified Wireless network, QoS should also be
enabled throughout the ‘wired’ network that provides connectivity between LWAPP APs and the WLCs.
enabled throughout the ‘wired’ network that provides connectivity between LWAPP APs and the WLCs.
Operation and Maintenance
This section focuses on general deployment considerations and recommendations for easy operation and
maintenance of a Cisco Unified Wireless deployment.
maintenance of a Cisco Unified Wireless deployment.
WLC Discovery
The different WLC discovery mechanisms for APs (discussed earlier) make initial deployment of
LWAPP APs very simple. Options include:
LWAPP APs very simple. Options include:
•
Staging (priming) LWAPP APs in advance using a WLC in a controlled environment
•
Deploying them straight out of the box by using one of the auto discovery mechanisms (DHCP, DNS
or OTP)
or OTP)