Cisco Wireless 9177 Series Access Point Hardware Installation Guide

PDF

Cisco Wireless 9177 Series Access Point Hardware Installation Guide

Troubleshoot the AP

Updated: July 31, 2026

Want to summarize with AI?

Log in

Details troubleshooting techniques for Cisco access points, including using the reset button, resolving controller join issues, understanding key deployment information, and configuring DHCP option 43 for proper network integration.

Use the troubleshooting information to reset the access point, resolve controller join issues, review key controller-based deployment requirements, and configure DHCP option 43 when needed.

How to use the reset button

All ports and the reset button are covered with protective seal caps upon delivery to maintain the unit's IP67/IP65 environmental rating. You must remove the seal cap to access the reset button. After use, you must reinstall the seal cap and tighten it to the appropriate torque to ensure a watertight seal.

You can use the Reset button to reset the AP to its factory default.

To reset the AP to the default factory-shipped configuration, perform these steps:

  1. Locate the reset button port on the base of the access point and remove the protective seal cap.

  2. Unplug the AP from the power source.

  3. Press and hold the Reset button.

  4. Power on the AP while continuing to hold the Reset button for the required duration as described in the table.

    Duration

    Action

    Zero to five seconds

    The LED blinks green for Cloud (Meraki) mode and blue for On-premises (Cisco Catalyst Wireless Controllers) mode.

    Greater than ten seconds

    The AP undergoes a configuration wipe.

    Greater than twenty seconds

    The AP resets completely and enters maintenance management mode.

    Greater than thirty seconds

    The AP configures FIPS in On-premises (Cisco Catalyst Wireless Controllers) mode.

    Greater than sixty seconds

    The LED turns solid pink, which indicates a factory reset.

    Greater than ninety seconds

    The LED turns off.
Note

Once the reset process is complete, reinstall the seal cap securely to maintain the unit's environmental integrity.

Troubleshooting the access point to Cisco controller join process

Note
Refer to the Cisco Wireless Solutions Software Compatibility Matrix to ensure that your AP is running a supported release.

AP can fail to join a controller for several reasons:

  • a Remote Authentication Dial-In User Service (RADIUS) authorization might be pending

  • certificates that are self-signed may not be enabled on the controller

  • the regulatory domains of the access point and controller may not match

You can configure access points to send all CAPWAP-related errors to a system logging (syslog) server. View all CAPWAP error messages on the syslog server.

If the AP is in Cloud (Meraki) mode, it does not attempt to join the Cisco Catalyst 9800 Series Wireless Controller. For more information, see the Cisco Wireless Global Use Access Points Deployment Guide.

The controller does not maintain the state of the access point. Determining why the discovery request from a specific access point was rejected can be difficult. To troubleshoot these problems, run trace commands on the Cisco Catalyst 9800 Series Wireless Controller.

The controller collects information related to joining for each access point that sends a CAPWAP discovery request. Collection begins when the access point sends its first discovery message and ends when the controller sends its last configuration payload to the access point.

When the controller reaches the maximum number of access points for information related to joining, it does not collect information for additional access points.

By default, the access point sends all syslog messages to the IP address 255.255.255.255.

You can also configure a DHCP server to return a syslog server IP address to the access point using Option seven on the server. The access point then sends syslog messages to this IP address.

When your access point joins a controller for the first time, the controller sends the global syslog server IP address (default: 255.255.255.255) to the access point. The AP sends all syslog messages to this IP address until this configuration overrides it:

  • the access point is still connected to the same controller and the global syslog server IP address configuration on the controller has changed using the syslog host syslog-ip-address command

    To configure the global syslog server IP address, run these commands:

    1. configure terminal

    2. ap profile ap-profile-name

    3. syslog host syslog-ip-address

    4. exit

  • the access point disconnects from the controller and joins another controller; the new controller sends its global syslog server IP address to the access point

  • when a new syslog server IP address overrides the existing one, the access point erases the old address from persistent storage and stores the new address; the access point then sends syslog messages to the new address if it can reach the syslog server

Note
You can configure the syslog server for access points and view access point join information only from the command-line interface (CLI).

Important information for controller-based deployments

Use these guidelines when using the AP.

  • CAPWAP supports only Layer 3 operation. Ensure that the AP obtains an IP address using Layer 3, DHCP, DNS, or IP subnet broadcast. After obtaining an IP address, the AP can discover the controller.

  • The AP console port is enabled for monitoring and debug purposes.

    Note

    The default band rate is 115,200 bps (bits per second).

  • You cannot use configuration commands when the AP is connected to a controller.

Configuring DHCP option 43

You can use DHCP Option 43 to provide a list of controller IP addresses to access points, enabling them to find and join a controller.

This section provides a DHCP Option 43 configuration example for a Windows 2003 Enterprise DHCP server used with Cisco Wireless access points. For other DHCP servers, refer to the product documentation for DHCP Option 43 configuration. Use the IP address of the controller management interface in Option 43.

Note
DHCP Option 43 supports only one access point type per DHCP pool. Configure a separate DHCP pool for each access point type.

Access points use the type-length-value (TLV) format for DHCP Option 43. Program DHCP servers to return the option based on the DHCP Vendor Class Identifier (VCI) string for the access point. The Vendor Class Identifier (VCI) string for the access point is:

This is the format of the TLV block:

  • type—0xf1 (decimal 241)

  • length—number of controller IP addresses x 4

  • value—IP addresses of the wireless controller management interfaces listed sequentially in hex code

To configure DHCP Option 43 in the embedded Cisco IOS DHCP server, complete these steps:

Note

The procedure describes the configuration process for an access point that has completed the initial discovery process. For more information about day zero workflow, visit Global Use Access Points.

Procedure

1.

Enter configuration mode.
2.

Create a DHCP pool and add required parameters, such as default router and name server. This example shows a DHCP scope configuration:


ip dhcp pool <pool name> 
network <IP Network> <Netmask> 
default-router <Default router> 
dns-server <DNS Server>

Here:

<pool name> is the name of the DHCP pool, such as AP917x.

<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.
3.

Add the Option 43 line using this syntax:

option 43 hex <hex string>

The hex string is assembled by concatenating the TLV values: Type + Length + Value.

For example, if you have two controllers with management interface IP addresses 10.126.126.2 and 10.127.127.2, use type f1 (hex). The length is two times four, which equals eight or 08 (hex). The IP addresses translate to 0a7e7e02 and 0a7f7f02. The assembled string is f1080a7e7e020a7f7f02. The resulting Cisco IOS command added to the DHCP scope is option 43 hex f1080a7e7e020a7f7f02.