Cisco Cisco Aironet 1522 Lightweight Outdoor Mesh Access Point Guía De Diseño

Descargar
Página de 271
 
111
Cisco Mesh Access Points, Design and Deployment Guide, 7.2
OL-21848-03
  Connecting the Cisco 1500 Series Mesh Access Point to Your Network
Step 1
Enter configuration mode at the Cisco IOS CLI.
Step 2
Create the DHCP pool, including the necessary parameters such as the default router and name server. 
The commands used to create a DHCP pool are as follows: 
ip dhcp pool 
pool name 
network 
IP Network Netmask 
default-router 
Default router 
dns-server 
DNS Server 
where:
pool name is the name of the DHCP pool, such as AP1520
IP Network is the network IP address where the controller resides, such as 10.0.15.1
Netmask is the subnet mask, such as 255.255.255.0
Default router is the IP address of the default router, such as 10.0.0.1
DNS Server is the IP address of the DNS server, such as 10.0.10.2
Step 3
Add the option 60 line using the following syntax: 
option 60 ascii “
VCI string
For the VCI string, use one of the values below. The quotation marks must be included.
For Cisco 1550 series access points, enter “Cisco AP c1550”
For Cisco 1520 series access points, enter “Cisco AP c1520”
For Cisco 1240 series access points, enter “Cisco AP c1240”
For Cisco 1130 series access points, enter “Cisco AP c1130”
Step 4
Add the option 43 line using the following syntax: 
option 43 hex 
hex string 
The hex string is assembled by concatenating the TLV values shown below: 
Type Length Value 
Type is always f1(hex). Length is the number of controller management IP addresses times 4 in hex. 
Value is the IP address of the controller listed sequentially in hex. 
For example, suppose that there are two controllers with management interface IP addresses 
10.126.126.2 and 10.127.127.2. The type is f1(hex). The length is 2 * 4 = 8 = 08 (hex). The IP addresses 
translate to 0a7e7e02 and 0a7f7f02. Assembling the string then yields f1080a7e7e020a7f7f02.
The resulting Cisco IOS command added to the DHCP scope is listed below:
option 43 hex f1080a7e7e020a7f7f02
Backup Controllers
A single controller at a centralized location can act as a backup for mesh access points when they lose 
connectivity with the primary controller in the local region. Centralized and regional controllers need 
not be in the same mobility group. Using the controller GUI or CLI, you can specify the IP addresses of 
the backup controllers, which allows the mesh access points to fail over to controllers outside of the 
mobility group.
You can also configure primary and secondary backup controllers (which are used if primary, secondary, 
or tertiary controllers are not specified or are not responsive) for all access points connected to the 
controller as well as various timers, including the heartbeat timer and discovery request timers.