Advertisement
Cisco Catalyst 9136I Series Access Points
DHCP server discovery—This feature uses DHCP option 43 to provide controller IP addresses to the access points.
Cisco switches support a DHCP server option that is typically used for this capability. For more information about
DHCP option 43, see the
DNS discovery—The access point can discover controllers through your domain name server (DNS). For the access
point to do so, you must configure your DNS to return controller IP addresses in response to
CISCO-CAPWAP-CONTROLLER.localdomain, where localdomain is the access point domain name. Configuring the
CISCO-CAPWAP-CONTROLLER provides backwards compatibility in an existing customer deployment. When an
access point receives an IP address and DNS information from a DHCP server, it contacts the DNS to resolve
CISCO-CAPWAP-CONTROLLER.localdomain. When the DNS sends a list of controller IP addresses, the access
point sends discovery requests to the controllers.
Deploying the Access Point on the Wireless Network
After you have mounted the access point, follow these steps to deploy it on the wireless network:
Connect and power up the access point.
Step 1
Observe the access point LED (for LED status descriptions, see
Step 2
page
16.
a. When you power up the access point, it begins a power-up sequence that you can verify by observing the
access point LED. If the power-up sequence is successful, the discovery and join process begins. During this
process, the LED blinks sequentially green, red, and off. When the access point has joined a controller, the
LED is green if no clients are associated or blue if one or more clients are associated.
b. If the LED is not on, the access point is most likely not receiving power.
c. If the LED blinks sequentially for more than 5 minutes, the access point is unable to find its primary,
secondary, and tertiary Cisco Wireless Controller. Check the connection between the access point and the
Cisco Wireless Controller, and be sure the access point and the Cisco Wireless Controller are either on the
same subnet or that the access point has a route back to its primary, secondary, and tertiary Cisco Wireless
Controller. Also, if the access point is not on the same subnet as the Cisco Wireless Controller, be sure that
there is a properly configured DHCP server on the same subnet as the access point. See the
DHCP Option 43" section on page 19
Reconfigure the Cisco Wireless Controller so that it is not the master.
Step 3
A master Cisco Wireless Controller should be used only for configuring access points and not in a
Note
working network.
12
Checking the Access Point LEDs
The location of the access point status LED is shown in
Regarding LED status colors, it is expected that there will be small variations in color intensity and hue from
Note
unit to unit. This is within the normal range of the LED manufacturer's specifications and is not a defect.
However, the intensity of the LED can be changed through the controller.
"Configuring DHCP Option 43" section on page
for additional information.
Figure
19.
"Checking the Access Point LEDs" section on
1.
16
"Configuring
Advertisement
