Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide, Cisco IOS XE 26.1.x

PDF

Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide, Cisco IOS XE 26.1.x

AP device package

Updated: April 10, 2026

Want to summarize with AI?

Log in

Explains how AP device packages use the SMU infrastructure to extend wireless network support for new AP hardware without controller upgrades.

An AP device package is a software module that

  • allows new AP hardware models to connect to an existing wireless network

  • uses the SMU infrastructure to deliver new AP images, and

  • enables flexible, out-of-cycle support for new AP devices independent of controller major releases.

AP Service Pack (APSP)

When a new AP hardware model is introduced, it is shipped along with the corresponding controller related major software version. Subsequently, you must wait for the release of a controller version compatible with the new AP model before upgrading the entire network.

Starting with version 16.11.1, you can add new AP models to your wireless network using the SMU infrastructure, without upgrading the controller version. This solution is called AP Device Package (APDP).

SMU Process or Workflow

The SMU process builds APDP to detect code changes and to build APDP. You can add new AP image files to APDP and include AP images as needed.

The workflow is as follows:

  • install add

  • install activate

  • install commit

For more details, see Managing AP Device Package.

Warning: Commit changes within six hours of activation or deactivation

To complete the APSP or APDP activation or deactivation process, always run the install commit command within six hours after executing either install activate or install deactivate .

If you do not commit the changes within this window, the system reverts to the previous commit state automatically. Potential issues include:

  • service interruptions, especially over low bandwidth links where image transfers may not finish in time, and

  • rollbacks for remote deployments with slow transfer rates.

To avoid these risks:

  • Run the install commit command immediately after activation or deactivation.

  • Monitor the progress of the image transfer.

  • Plan to have sufficient time available at remote sites.

SMU package and AP image changes

SMU Package

A SMU package is a software metadata unit that:

  • contains AP model and capability-related details

  • is updated when new AP models are introduced, and

  • is bundled into APDP packages for deployment.

AP Image Changes

When new AP models are introduced, there may or may not be corresponding new AP images. AP images are mapped to the AP model families. If a new AP model belongs to an existing AP model family there will be existing AP image entries (for example: ap3g3 and ap1g5). If an AP model belongs to either ap3g3 or ap1g5, update the respective image file with the correct AP image location. The corresponding metadata file is also updated with the new AP model capability information.

If a new AP model belongs to a new AP model family and requires a new image file, create a new image entry file in the correct AP image location. The corresponding metadata file is updated with the new AP model capability information.

Note

The APDP images must not be renamed to prevent impact on its functionality.

Install AP device package (GUI)

Add or upgrade AP device support in your network.

Procedure

1.

Choose Administration > Software Management.
2.

Click AP Device Package (APDP) tab.
3.

Click Add.
4.

From the Transport Type drop-down list, select the transfer type to transfer the software image to your device as TFTP, SFTP, FTP, Device, or Desktop (HTTP).

  1. If you choose TFTP as the Transport Type, enter the Server IP Address (IPv4/IPv6), File path and select a File System from the drop-down list.

  2. If you choose SFTP as the Transport Type, enter the Server IP Address (IPv4/IPv6), SFTP Username, SFTP Password, File path and select a File System from the drop-down list.

  3. If you choose FTP as the Transport Type, enter the Server IP Address (IPv4/IPv6), FTP Username, FTP Password, File path, and select a File System from the drop-down list.

  4. If you choose Device as the Transport Type, enter the File path and select a File System from the drop-down list.

  5. If you choose Desktop (HTTPS) as the Transport Type, select a File System from the drop-down list.

  6. Click Select File to navigate to the Source File Path.
5.

Enter the File Name and click Add File.
6.

From the AP Upgrade Configuration section, select the percentage of APs to be included from the AP Upgrade per iteration drop-down list.
7.

Click Apply.

Install AP device package (CLI)

Install and activate new AP device packages on the controller using the CLI.

Procedure

1.

Extract AP images from APDP and place them in SMU or APDP specific mount location.

Example:

Device# install add file bootflash filename
Note

Here, the SMU does not trigger the Wireless module.
2.

Add the AP software in APDP to the existing current active AP image list.

Example:

Device# install activate file bootflash filename

Also, update the capability information for the new AP models in the controller .

Note

Even if the new AP module supports new hardware capabilities, the controller recognizes only the capability information that its base version supports.

At this point, the controller accepts the new connection from the new AP model. The new AP model then joins the controller .
3.

Commit the new AP software to be persistent across reloads.

Example:

Device# install commit

The commit occurs after activation when the system is up, or after the first reload. If a package is activated but not committed, it remains active after the first reload but becomes inactive after the second reload.
4.

(Optional) Deactivate an active APDP, update the package status, and trigger a process to restart or reload.

Example:

Device# install deactivate file bootflash filename
5.

Display the image version on the device.

Example:

Device# show version

Verify APDP on the Controller

To verify the status of APDP packages on the controller , use the command:

Device# show install summary

[ Chassis 1 ] Installed Package(s) Information:
State (St): I - Inactive, U - Activated & Uncommitted, C - Activated & Committed, D - Deactivated & Uncommitted
--------------------------------------------------------------------------------
Type  St   Filename/Version    
--------------------------------------------------------------------------------
APDP  I    bootflash:apdp_CSCvp12345.bin
IMG   C    17.1.0.0                                                      
--------------------------------------------------------------------------------
Auto abort timer: inactive
--------------------------------------------------------------------------------
Note

The output of this command varies based on the packages, and the package states that are installed.