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

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

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

Chapter Title

AP Management

Results

Updated:
November 30, 2022

Chapter: AP Management

AP Management

AP Crash File Upload

When a converted access point unexpectedly reboots, the access point stores a crash file on its local flash memory at the time of the crash. After the unit reboots, it sends the reason for the reboot to the device. If the unit rebooted because of a crash, the device pulls up the crash file using the existing CAPWAP messages and stores it in the device flash memory. The crash information copy is removed from the access point's flash memory when the device pulls it from the access point:


Note
The system does not generate reports in case of a reload.

During a process crash, the following are collected locally from the device:

  • Full process core

  • Trace logs

  • Cisco IOS syslogs (not guaranteed in case of nonactive crashes)

  • System process information

  • Bootup logs

  • Reload logs

  • Certain types of proc information

All this information is stored in separate files, which are then archived and compressed into one bundle. This makes it convenient to get a crash snapshot in one place, and can be then moved off the box for analysis. This report is generated before the device goes down to ROMMON/bootloader.


Note
Except for the full core and tracelogs, everything else is a text file.

Configuring AP Crash File Upload (CLI)

Procedure

Step 1

enable

Enters privileged EXEC mode.

Step 2

ap name ap-name crash-file get-crash-data

Collects AP crash information. The crash file is uploaded automatically after the AP reloads to ready state. Therefore, this command does not have to be manually executed.

Step 3

ap name ap-name crash-file get-radio-core-dump slot {0 | 1}

Collects the AP core dump file for slot 0 or slot 1.

Step 4

ap name ap-name core-dump tftp-ip crash-file uncompress

Uploads the AP crash coredump file to the given TFTP location.

Step 5

show ap crash-file

Displays the AP crash file, as well as the radio crash file.

Step 6

dir bootflash

Displays the crash file in bootflash with .crash extension.

Information About LED States for Access Points

In a wireless LAN network where there are a large number of access points, it is difficult to locate a specific access point associated with the controller. You can configure the controller to set the LED state of an access point so that it blinks and the access point can be located. This configuration can be done in the wireless network on a global as well as per-AP level.

The LED state configuration at the global level takes precedence over the AP level.

Configuring LED State in Access Points (GUI)

Procedure

Step 1

Choose Configuration > Wireless > Access Points.

Step 2

Click an AP from the AP list.

The Edit AP window is displayed.

Step 3

In the General tab, under the General section, click the box adjacent to the LED State field to enable or disable the LED state.

Step 4

From the LED Brightness Level drop-down list, choose a value from 1 to 8.

Step 5

Click Update & Apply to Device.

Configuring LED State for Access Points in the Global Configuration Mode (CLI)

Procedure

  Command or Action Purpose

Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step 2

ap name Cisco-AP-name led

Example:

Device# ap name Cisco-AP-name led

Enables the LED state for Cisco APs, globally.

Step 3

ap name Cisco-AP-name led-brightness-level 1-8

Example:

Device# ap name Cisco-AP-name led-brightness-level 4

Configures the LED brightness level. Value of the brightness is from 1 to 8.

Configuring LED State in the AP Profile

Procedure

  Command or Action Purpose

Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

ap profile default-ap-profile

Example:

Device(config)#ap profile default-ap-profile

Enters the AP profile configuration mode.

Step 3

led

Example:

Device(config-ap-profile)# led

Enables the LED-state for all Cisco APs.

Verifying LED State for Access Points

To verify the LED state of the access points, use the following command:

show ap name AXXX-APXXXX.bdXX.f2XX config general 

Device# show ap name AXXX-APXXXX.bdXX.f2XX config general 
Cisco AP Name : AXXX-APXXXX.bdXX.f2XX 
=================================================
Cisco AP Identifier : 0cXX.bdXX.65XX
Country Code : Multiple Countries : FR,IN,US
Regulatory Domain Allowed by Country : 802.11bg:-AE 802.11a:-ABDEN
AP Country Code : US - United States
AP Regulatory Domain
802.11bg : -A
802.11a : -B
.
.
.
CAPWAP Preferred mode : IPv4
CAPWAP UDP-Lite : Not Configured
AP Submode : WIPS
Office Extend Mode : Disabled
Dhcp Server : Disabled
Remote AP Debug : Disabled
Logging Trap Severity Level : information
Logging Syslog facility : kern
Software Version : 17.X.0.XXX
Boot Version : 1.1.X.X
Mini IOS Version : 0.0.0.0
Stats Reporting Period : 180
LED State : Enabled
MDNS Group Id : 0
.
.
.

Access Point Support Bundle

An access point (AP) support bundle contains core files, crash files, show run-configuration , configuration commands, msglogs, and traplogs.

This topic describes how you can retrieve the support bundle information of an AP and export it to the controller or to an external server. (Until Cisco IOS XE, Release 17.2.1, you had to log in to the AP console to retrieve the AP support-bundle information.)

The Access Point Support Bundle feature is supported only on Cisco Wave2 APs and Cisco Catalyst APs.

Exporting an AP Support Bundle (GUI)

Procedure

Step 1

Choose Configuration > Wireless > Access Points.

Step 2

Click the corresponding AP name.

The Edit AP window is displayed.

Step 3

Click the Support Bundle tab.

Step 4

From the Destination drop-down list, choose one of the following:

  • This Device: If you choose this, enter the values for the Server IP, Destination File Path, Username, and Password fields.

    Note

     

    When you choose This Device, a bundle is sent through Secure Copy (SCP) to the controller (if you have configured the ip scp server enable command globally on the controller). You can easily retrieve the bundle later from your browser, using the controller file manager.

  • External Server: If you choose this, from the Transfer Mode drop-down list, choose either scp or tftp.

    If you choose the scp transfer mode, enter the values for the Server IP, Destination File Path, Username, and Password fields.

    If you choose the tftp transfer mode, enter the values for the Server IP, and Destination File Path fields.

Note

 
Information about the Last Export Status, such as State, Transfer Mode, Server IP, File Path, and Time of Export, is displayed on the right-hand side of the window.

Step 5

Click Start Transfer.

Exporting an AP Support Bundle (CLI)

Procedure

  Command or Action Purpose

Step 1

enable

Example:

Device> enable

Enables privileged EXEC mode. Enter your password, if prompted.

Step 2

ap name Cisco-AP-name export support-bundle mode { scp | tftp} target ip-address { A.B.C.D | X:X:X:X::X} path file-path

Example:

Device> ap name Cisco-AP-name export support-bundle mode scp target ip-address 10.1.1.1 path file-path

Exports the AP support bundle through the SCP or TFTP transfer modes.

If you select the scp , you will be prompted to provide your username and password.

For tftp , username and password is not required.

Monitoring the Status of Support Bundle Export

To monitor the status of a support bundle export, run the following command: 

Device# show ap support-bundle summary
AP Name    Server-IP   Status        Last Successful Time      Path File-name
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
AP_28XXX   81.1.1.10   Copy Success  04/24/2020 07:27:38 UTC   AP_28XXX_support.17.4.0.2.2020.07XXXX.tgz

Information About Access Point Memory Information

With the introduction of the Access Point Memory Information feature, you can view the access point (AP) memory type, the CPU type, and the memory size per AP, after single sign-on authentication. APs share the memory information with the controller during the join phase.

To view the memory information of a specific AP, use the show ap name AP-NAMEconfig general command.

Verifying Access Point Memory Information

To verify the memory information of a specified AP, including the CPU type, memory type and memory size, use the following command: 

Device# show ap name AP-NAME  config general 
Cisco AP Name   : AP-NAME
=================================================
Cisco AP Identifier                             : 00XX.f1XX.e0XX
Country Code                                    : Multiple Countries : FR,IN,US
Regulatory Domain Allowed by Country            : 802.11bg:-AE   802.11a:-ABDEN
AP Country Code                                 : US  - United States
AP Regulatory Domain
  802.11bg                                      : -A
  802.11a                                       : -B
.
.
.
CPU Type                                        : ARMv7 Processor rev 1 (v7l)
Memory Type                                     : DDR4
Memory Size                                     : 1028096 KB
.
.
.

Information About Access Point Tag Persistency

From Cisco IOS XE Bengaluru 17.6.1 onwards, AP tag persistency is enabled globally on the controller. When APs join a controller with tag persistency enabled, the mapped tags are saved on the APs without having to write the tag configurations on each AP, individually.

Configuring AP Tag Persistency (GUI)

Procedure

Step 1

Choose Configuration > Tags & Profiles > Tags.

Step 2

Click the AP tab.

Step 3

In the Tag Source tab, check the Enable AP Tag Persistency check box to configure AP Tag persistency globally.

When APs join a controller with the tag persistency enabled, the mapped tags are saved on the AP without having to write the tag configurations on each AP individually.

Step 4

Click Apply to Device.

What to do next

Save tags on an AP.

Saving Tags on an Access Point (GUI)

Procedure

Step 1

Choose Configuration > Wireless > Access Points.

Step 2

Click an AP from the list.

The Edit AP page is displayed.

Step 3

Click the General tab.

Step 4

In the Tags section, specify the appropriate policy, site, and RF tags that you created in the Configuration > Tags & Profiles > Tags page.

Step 5

From the Policy drop-down list, select a value.

Step 6

From the Site drop-down list, select a value.

Step 7

From the RF drop-down list, select a value.

Step 8

Check the Write Tag Config to AP check box to push the tags to the AP so that the AP can save and remember this information even when the AP is moved from one controller to another.

Step 9

Click Update & Apply to Device.

Deleting Saved Tags on the Access Point

Procedure

Step 1

Choose Configuration > Wireless > Access Points.

Step 2

Click an AP from the list of APs.

The Edit AP window is displayed.

Step 3

In the Edit AP window, choose the Advanced tab.

Step 4

In the Set to Factory Default section, check the Clear Resolved Tag Config check box to clear the saved tags on an AP.

Step 5

Click Update & Apply to Device.

Configuring AP Tag Persistency (CLI)

Before you begin

For an AP to preserve its policy tag, site tag, and RF tag configured from the primary controller, these tags must also exist on the other controllers that the AP connect to. If all the three tags do not exist, the AP applies the default policy tag, site tag, and RF tag. Similarly, the tag policy is applicable even if one or two tags exist. AP tag persistency helps in priming an AP in N+1 redundancy scenarios. For more information about configuring tags, see https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-6/config-guide/b_wl_17_6_cg/m_config_model.html.


Note

After being enabled, AP tag persistency is performed during AP join. Therefore, if there are any APs that are already joined to the controller, those APs must rejoin the controller.

Procedure

  Command or Action Purpose

Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

ap tag persistency enable

Example:

Device(config)# ap tag persistency enable

Configures AP tag persistency.

Step 3

end

Example:

Device(config)# end

Exits configuration mode and returns to privileged EXEC mode.

Verifying AP Tag Persistency

To verify AP tag persistency in the primary controller, use the following command:

Device# show ap tag summary
Number of APs: 1

AP Name         AP Mac           Site Tag Name         Policy Tag Name        RF Tag Name            Misconfigured    Tag Source
--------------------------------------------------------------------------------------------------------------------------------
Cisco01_AP      xxxx.xxxx.xxxx   default-site-tag      OpenRoaming            default-rf-tag         No               Static

Note

If the Tag Source displays Static or Filter, it means that the AP tag mappings were configured on the primary controller. If the source displays Default, it means that the AP received the default tags when joining the controller.

To verify the AP tag persistency in the secondary controller, use the following command:

Device# show ap tag summary
Number of APs: 1

AP Name       AP Mac           Site Tag Name        Policy Tag Name     RF Tag Name       Misconfigured   Tag Source
--------------------------------------------------------------------------------------------------------------------
Cisco01_AP   xxxx.xxxx.xxxx    default-site-tag     OpenRoaming         default-rf-tag     No              AP

Note

If the Tag Source displays AP, it means that the policy tag, site tag, and RF tag match what was configured on the primary controller, indicating that the AP tags have persisted across controllers.

Feature History for AP Power Save

This table provides release and related information for the feature explained in this module.

This feature is also available in all the releases subsequent to the one in which they are introduced in, unless noted otherwise.

Table 1. Feature History for AP Power Save

Release

Feature Information

Cisco IOS XE Cupertino 17.8.1

This feature allows a network administrator to force APs to operate in low-power mode to reduce power consumption.

Cisco IOS XE Cupertino 17.9.1

Feature support for the following APs:

  • Cisco Catalyst 9164 Series Access Points

  • Cisco Catalyst 9166 Series Access Points

Cisco IOS XE Dublin 17.10.1

The following features are supported:

  • Radio spatial streams

  • Flexible PoE profiles

Information About AP Power Save

The power-save mode in APs allows a network administrator to force APs to operate in low-power mode to reduce power consumption.

The AP Power Save feature is supported in the following APs:

  • Cisco Catalyst 9115 Series Access Points

  • Cisco Catalyst 9120 Series Access Points

  • Cisco Catalyst 9130 Series Access Points

  • Cisco Catalyst 9136 Series Access Points

  • Cisco Catalyst 9164 Series Access Points

  • Cisco Catalyst 9166 Series Access Points

  • Cisco Catalyst 9162 Series Access Points

Access Point Power Policy

The access point power policy allows you to define the power budget utilization available for an AP, wherein, you can define a set of policies for different interfaces on an AP. You can manage interfaces such as Wi-Fi radios, USB, and so on, as required.

Use Case for AP Power Policy

The following is the use case of an AP power policy:

  • You can define a power policy for the available power inputs, such as, 802.3af, 802.3at, 802.3bt (for multiple levels), DC power, and so on. With tri-radio and quad-radio APs, the power requirement has gone beyond the capability of the 802.3at Power over Ethernet (PoE) mode. Therefore, with the AP power policy, for example, we statically predefine an AP operation when provided with non-802.3bt power (such, as TX power, radio chains, USB port, SFP, and so on).

Power-Save Mode

The power-save mode enables an AP to switch to a low-power mode when no clients are associated with the AP. For example, when this mode is enabled in workspaces, the AP falls asleep during after hours, thereby saving power consumption of the AP throughout the night.

From Cisco IOS-XE Cupertino 17.10.1 onwards, you can shut down AP radios or lower the radio spatial streams, to reduce usage of power. You can enforce radio speed by configuring the number of spatial streams on the radios. The combinations for radio spatial stream policies are: 1X1, 2X2, 3X3 (only for Cisco Catalyst 9130 Series Access Points), 4X4, and 8X8.

The following are the advantages of the power-save mode:

  • Increases the energy saving per AP: In the power save mode you can reduce AP functions during off-peak hours and save an additional 20% in energy costs compared to the regular idle mode.

  • Enables environmentally conscious purchases: Large enterprises and companies track environmental performance as one of their key indices. They have a centralized energy team to monitor their energy efficiency, which magnifies the importance of the power-save feature.

PoE Profiles

  • Fixed PoE Profile: The APs negotiate the power that is required, from the switches they are connected to. The power required varies from one AP model to another AP model. If an AP is not granted the power it requested, it operates under the power budget. In such conditions, some of the interfaces operate under degraded conditions.

    For example, some radios may operate at 2SS instead of at 4SS, which they are capable of. The operating conditions for each of the AP interfaces differs from one power level to another. These are referred to as fixed PoE profiles. Fixed PoE profiles are applied when the AP is operating in normal mode, that is, nonpower-save mode. When the AP operates in power-save mode, the configured PoE power policies are applied.

  • PoE Power Policy: With power policies or profiles, you can configure interfaces that you want to set at certain speeds. With this policy, you can configure a profile of your choice that will be pushed to the AP based on your calendar or timing. For example, on a group of APs in the second floor, push a profile where you want to turn off all APs, except 2.4-GHz radio, from 7 p.m. to 7 a.m.

  • Flexible PoE Profile: With flexible PoE profiles, you can configure different interfaces and set specific parameter values and states for each interface, instead of following fixed PoE profile rules. If an AP does not get the power it requires, it operates under the power budget by using the flexible PoE profile.

Table 2. AP Power Draw Specifications: Cisco Catalyst 9115, 9120, 9130 Series APs

Access Points

PoE-In-Mode/DC Mode

Consumption @ Power Device

Consumption @ Power Source Equipment

Feature Mode

AP

Worst-Case Cable

Radio 1

Radio 2

Radio 3

Ethernet

USB

Module

PoE-Out

Cisco Catalyst 9115AXI Access Points

.3af

13.0

15.4

2X2

2X2

—

1G

N

—

—

.3at

16.0

18.9

4X4

4X4

—

2.5G

N

—

—

.3at

20.4

24.1

4X4

4X4

—

2.5G

Y(3.75W)

—

—

Cisco Catalyst 9115AXE Access Points

.3af

13.0

15.4

2X2

2X2

—

1G

N

—

—

.3at

17.0

20.1

4X4

4X4

—

2.5G

N

—

—

.3at

21.4

25.3

4X4

4X4

—

2.5G

Y(3.75W)

—

—

Cisco Catalyst 9120AXI/E Access Points

.3af

13.8

15.4

1X1

1X1

Enabled

1G

N

—

—

.3at

20.5

23.2

4X4

4X4

Enabled

2.5G

N

—

—

.3at

25.5

30.0

4X4

4X4

Enabled

2.5G

Y(4.5W)

—

—

Cisco Catalyst 9130AXI/E Access Points

.3af

13.8

15.4

1X1

1X1

Enabled

1G

N

—

—

.3at

25.5

30.0

8X8

4X4

Enabled

5G

N

—

—

.3at

25.5

30.0

Primary 4X4

Secondary Off

4X4

Enabled

5G

Y(4.5W)

—

—

.3at

25.5

30.0

Primary 4X4

Secondary 4X4

Disabled

Enabled

5G

Y(4.5W)

—

—

.3bt

30.5

33.3

8X8

4X4

Enabled

5G

Y(4.5W)

—

—
Table 3. AP Power Draw Specifications: Cisco Catalyst 9136 Series APs

Access Points

PoE-In-Mode

Consumption @Power Device

Consumption @Power Source Equipment

Feature Mode

at AP

Worst-Case Cable

5G Radio

2G Radio

6G Radio

AUX Radio

Mgig0

Mgig1

USB

Module

PoE-Out

Cisco Catalyst 9136 Series Access Points

.3af - Fixed

13.9

15.4

Disabled

Disabled

Disabled

Enabled

1G

Disabled

Disabled

—

—

.3at - Fixed

24.0

27.90

Primary - 4X4

Secondary - Disabled

2X2

2X2

Enabled

2.5G

2.5G (hitless failover standby)

Disabled

—

—

.3bt - Fixed

43.4

54.81

8X8 or Dual

4X4

4X4

4X4

Enabled

5G

5G

Y(9W)

—

—

.3bt - PoE Policy 1

37.3

41.63

8X8 or Dual

4X4

4X4

4X4

Enabled

5G

5G

Disabled

—

—
Table 4. AP Power Draw Specifications: Cisco Catalyst 9166 Series APs

Access Points

PoE-In-Mode

Consumption @Power Device

Consumption @Power Source Equipment

Feature Mode

at AP

Worst-Case Cable

5G Radio

2G Radio

6G Radio

AUX Radio

Mgig0

Mgig1

USB

Module

PoE-Out

Cisco Catalyst 9166 Series Access Points

.3af - Fixed

13.9

15.4

Disabled

Disabled

Disabled

Enabled

1G

—

Disabled

—

—

.3at - Fixed Policy

25.5

30.0

4X4

4X4

4X4

Enabled

5G

—

Disabled

—

—

.3bt - Fixed

30.5

32.8

4X4

4X4

4X4

Enabled

5G

—

Y (4.5 W)

—

—

DC Jack - Fixed

30.5

—

4X4

4X4

4X4

Enabled

5G

—

Y (4.5 W)

—

—
Table 5. AP Power Draw Specifications: Cisco Catalyst 9164 Series APs

Access Points

PoE-In-Mode

Consumption @Power Device

Consumption @Power Source Equipment

Feature Mode

at AP

Worst-Case Cable

5G Radio

2G Radio

6G Radio

AUX Radio

Mgig0

Mgig1

USB

Module

PoE-Out

Cisco Catalyst 9164 Series Access Points

.3af - Fixed

13.9

15.4

Disabled

Disabled

Disabled

Enabled

1G

—

Disabled

—

—

.3at - Fixed

25.5

30.0

4X4

2X2

4X4

Enabled

2.5G

—

Disabled

—

—

.3bt - Fixed

30.1

32.8

4X4

2X2

4X4

Enabled

2.5G

—

Y (4.5 W)

—

—

DC Jack - Fixed

30.1

—

4X4

2X2

4X4

Enabled

2.5G

—

Y (4.5 W)

—

—
Table 6. AP Power Draw Specifications: Cisco Catalyst 9162 Series APs

Access Points

PoE-In-Mode

Consumption @Power Device

Consumption @Power Source Equipment

Feature Mode

at AP

Worst-Case Cable

5G Radio

2G Radio

6G Radio

AUX Radio

Mgig0

Mgig1

USB

Module

PoE-Out

Cisco Catalyst 9162 Series Access Points

.3af

13.3

14.32

1X1

Disabled

1X1

Enabled

1G

—

Disabled

—

—

.3at

20.1

22.67

2X2

2X2

2X2

Enabled

2.5G

—

Disabled

—

—

.3at

25.5

30

2X2

2X2

2X2

Enabled

2.5G

—

Y (4.5W)

—

—

AP Power Save Scenarios

The AP Power Save feature helps APs to enter into a power-save mode or low-power mode by applying a calendar, for example, for after hours, associated with the corresponding power profile. The AP profile is enhanced to associate a PoE power policy with calendar profiles. The following are the scenarios for Eco mode APs:

  • Figure 1. AP in Eco Mode Behavior: Working Days
    This image shows the Access Point in Eco Mode Behaviour in the working day scenario.

    On working days, from 7:00 a.m. to 7:00 p.m, the AP functions in normal mode or fixed mode, when the maximum number of clients are connected to the AP. From 7:00 p.m. to 12:00 a.m., the Cal1 calendar profile timer starts to put the AP in the power-save mode. Likewise, the Cal2 calendar profile timer starts, and extends the power-save mode from 12:00 a.m. to 7:00 a.m. Again, at 7:00 a.m., the AP goes into normal mode.

  • Figure 2. AP in Eco Mode Behavior: Nonworking Days
    This image shows the Access Point in Eco Mode Behavior in the nonworking day scenario

    On nonworking days, the AP goes into power-saving mode from 12:00 a.m. to 11:59:59 p.m. The Cal3 calendar profile is applied here. This profile defines the timer for the power-save mode. This means that there are no clients connected to the AP, and that the AP is asleep.

  • Figure 3. AP in Eco Mode Behavior: With Clients
    This image shows the Access Point in Eco Mode Behavior with Clients

    When clients are connected to the AP, the AP automatically switches to the normal mode. For example, in the calendar profile Cal1, the AP is in normal mode, because wireless clients are connected to the AP. At 8:00 p.m., clients get dissociated from the AP, and the AP goes into power-save mode. When clients enter the AP coverage area at 9:30 p.m., the AP automatically switches from power-save mode to normal mode of operation.

Configuring Power Policy Profile (GUI)

Procedure

Step 1

Choose Configuration > Tags & Profiles > Power Profile.

Step 2

Click Add.

The Add Power Profile window is displayed.

Step 3

Enter a name and description for the power profile. The name must be ASCII characters of up to 128 characters, without leading or trailing spaces.

Step 4

Click Add to add rules for the power profile.

Step 5

In the Sequence number field, enter a unique sequence number to designate the priority in which power should be disabled for the component. The sequence number of 0 indicates that the component should be disabled first.

Step 6

From the Interface and Interface ID drop-down list, choose interface and interface ID to designate to the component for which the power derating rule applies.

Step 7

From the Parameter and Parameter value drop-down list, choose the values depending on the interface you chose in step 6.

For example, if you chose Ethernet as an interface, you can further customize the rule for the interface by choosing the associated speed. This rule ensures that the AP disables power for the Ethernet interface that is operating at a higher speed, and thereby consuming more power.

Step 8

Click the check mark to save and then click Apply to Device.

Configuring a Power Policy Profile (CLI)

Before you begin

You must keep at least one radio interface up and running before you configure a power policy profile.

Procedure

  Command or Action Purpose

Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

wireless profile power power-profile-name

Example:

Device(config)# wireless profile power power-profile-name

Configures the power policy profile.

Step 3

sequence-number ethernet {GigabitEthernet0 | GigabitEthernet1 speed {1000mbps | 100mbps | 2500mbps | 5000mbps} | LAN1 | LAN2 | LAN3 state disable}

Example:

Device(config-wireless-power-profile)# 10 ethernet gigabitethernet1 speed 1000mbps

Configures the power policy for Ethernet.

sequence-number : The power profile settings are ordered by sequence numbers. AP derating takes place as per the sequence number entered. The same combination of interface identifiers and parameter values does not appear in another sequence number. The same interface with the same parameter can appear multiple times with different parameter values.

Note

 

  • The Ethernet interface is used to join the controller. The uplink interface is not disabled even if it is defined in the power policy.

  • Ethernet speed configuration is not operational in Cisco IOS XE Cupertino 17.8.1.

Step 4

sequence-number radio 24ghz {spatial-stream {1 | 2 | 3 | 4} | state shutdown}

Example:

Device(config-wireless-power-profile)# 20 radio 24ghz spatial stream 2

Configures spatail stream for the 2.4-GHz band radio.

Here:

sequence-number : The power profile settings are ordered by sequence numbers. AP derating takes place as per the sequence number entered. The same combination of interface identifiers and parameter values does not appear in another sequence number. The same interface with the same parameter can appear multiple times with different parameter values.

  • 1: Specifies a 1X1 radio spatial stream.

  • 2 : Specifies a 2X2 radio spatial stream.

  • 3 : Specifies a 3X3 radio spatial stream.

  • 4 : Specifies a 4X4 radio spatial stream.

state shutdown : Indicates that the radio state is down.

Step 5

sequence-number radio 5ghz {spatial-stream {1 | 2 | 3 | 4 | 8} | state shutdown}

Example:

Device(config-wireless-power-profile)# 30 radio 5ghz spatial stream 4

Configures spatail stream for the 5-GHz band radio.

Here:

sequence-number : The power profile settings are ordered by sequence numbers. AP derating takes place as per the sequence number entered. The same combination of interface identifiers and parameter values does not appear in another sequence number. The same interface with the same parameter can appear multiple times with different parameter values.

  • 1: Specifies a 1X1 radio spatial stream.

  • 2 : Specifies a 2X2 radio spatial stream.

  • 3 : Specifies a 3X3 radio spatial stream.

  • 4 : Specifies a 4X4 radio spatial stream.

  • 8 : Specifies a 8X8 radio spatial stream.

state shutdown : Indicates that the radio state is down.

Step 6

sequence-number radio secondary-5ghz {spatial-stream {1 | 2 | 3 | 4 | 8} | state shutdown}

Example:

Device(config-wireless-power-profile)# 40 radio 5ghz spatial stream 4

Configures spatail stream for a secondary 5-GHz band radio.

Here:

sequence-number : The power profile settings are ordered by sequence numbers. AP derating takes place as per the sequence number entered. The same combination of interface identifiers and parameter values does not appear in another sequence number. The same interface with the same parameter can appear multiple times with different parameter values.

  • 1: Specifies a 1X1 radio spatial stream.

  • 2 : Specifies a 2X2 radio spatial stream.

  • 3 : Specifies a 3X3 radio spatial stream.

  • 4 : Specifies a 4X4 radio spatial stream.

  • 8 : Specifies a 8X8 radio spatial stream.

state shutdown : Indicates that the radio state is down.

Step 7

sequence-number radio 6ghz {spatial-stream {1 | 2 | 3 | 4 | 8} | state shutdown}

Example:

Device(config-wireless-power-profile)# 50 radio 6ghz spatial stream 2

Configures spatail stream for the 6-GHz band radio.

Here:

sequence-number : The power profile settings are ordered by sequence numbers. AP derating takes place as per the sequence number entered. The same combination of interface identifiers and parameter values does not appear in another sequence number. The same interface with the same parameter can appear multiple times with different parameter values.

  • 1: Specifies a 1X1 radio spatial stream.

  • 2 : Specifies a 2X2 radio spatial stream.

  • 3 : Specifies a 3X3 radio spatial stream.

  • 4 : Specifies a 4X4 radio spatial stream.

  • 8 : Specifies a 8X8 radio spatial stream.

state shutdown : Indicates that the radio state is down.

Step 8

sequence-number usb 0 state disable

Example:

Device(config-wireless-power-profile)# 60 usb 0 state disable

Configures the power policy for USB.

Configuring a Calendar Profile (GUI)

Configure calendar profiles to set up a daily, weekly, or monthly recurrence schedule.

Procedure

Step 1

Choose Configuration > Tags & Profiles > Calendar.

Step 2

Click Add.

The Add Calendar Profile window is displayed.

Step 3

Enter a name for the calendar profile. The name must be ASCII characters of up to 32 characters, without leading or trailing spaces.

Step 4

From the Recurrence drop-down list, choose the schedule for which you want to create a profile.

Step 5

Select the Start Time and the End Time for the recurrence schedule.

Note

 

  • For daily recurrences, you can select the start time and end time. For example, if you want the AP to derate the power on certain interfaces between 7 p.m. to 7 a.m. daily, or if you want the controller to not allow any clients to be associated during this period, you can set up this daily recurrence schedule.

    To cover this timespan, you must create two calendar profiles, one for 7 p.m. till 23:59:59, and another one from midnight to 7 a.m. of the next calendar day, and map it to the same power profile. After this, assign it to the AP Join profile.

  • For weekly recurrences, select the specific days of the week along with the start and end time.

  • For monthly recurrence, select the specific days of the month along with the start and end time.

Step 6

Click Apply to save the configuration.

Configuring a Calendar Profile (CLI)

Procedure

  Command or Action Purpose

Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

wireless profile calendar-profile name calendar_profile_ap_power

Example:

Device# wireless profile calendar-profile 
name ap_power_calendar

Configures a calendar profile. Enters the calendar profile configuration mode.

Here, name refers to the name of the calendar profile.

Step 3

recurrence daily

Example:

Device(config-calendar-profile)# recurrence daily

Configures daily recurrence for daily profile.

Step 4

start start-time end end-time

Example:

Device(config-calendar-profile)# start 16:00:00 
end 20:00:00

Configures the start time and end time for calendar profile.

Step 5

end

Example:

Device(config-calendar-profile)# end

Returns to privileged EXEC mode.

Configuring a Power Policy in an AP Join Profile (GUI)

Power policy supports the use of a power profile or a mapped configuration of a power profile and a calendar profile that are pushed to an AP during an AP join session. You can map a maximum of five combination profiles (calendar and power) per AP profile.

Before you begin

Ensure that the power profile and calendar profile are created and displayed in the respective drop-down lists in the GUI.

Procedure

Step 1

Choose Configuration > Tags & Profiles > AP Join.

The Add AP Join Profile window is displayed.

Step 2

Click the AP tab.

Step 3

Under the AP tab, click the Power Management tab.

Step 4

From the Regular Power Profile drop-down list, choose the power profile.

The AP applies these settings to derate the power based on the configured priority list.

Note

 
If you want the AP to apply the power profile configuration during a specific time period, choose the Calendar Profile and map it to the power profile from the drop-down list.

Step 5

Click the check mark to associate the mapping.

Step 6

Click Apply to Device to save the configuration.

Mapping a Power Profile Under an AP Profile (CLI)

Before you begin

Ensure that you have defined a calendar profile in the wireless profile, before you map the calendar profile to an AP join profile.

Procedure

  Command or Action Purpose

Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

ap profile ap-profile-name

Example:

Device(config)#  ap profile  ap-profile-name

Configures an AP profile and enters AP profile configuration mode.

Step 3

power-profile power-profile-name

Example:

Device(config-ap-profile)#  power-profile  power-profile-name

Configures the AP power profile.

This power profile is used during non-calendar hours to meet the power budget provided by the switch connected to the AP.

Step 4

calendar-profile calendar-profile-name

Example:

Device(config-ap-profile)#  calendar-profile  ap-calendar-profile

Maps a calendar profile to the AP profile. Enters the AP profile calendar configuration mode.

Step 5

[no] action power-saving-mode power-profile power-profile-name

Example:

Device(config-ap-profile-calendar)# action power-saving-mode 
power-profile power-profile1

Maps a specific power profile to a specific calendar profile. Maps the power-saving mode action for the calendar profile. Use the no form of this command to disable the command.

Note

 

You can have more than one mapping of calendar profile to power profile.

Configuration Example of Power Profile

The following example shows how to define a power save policy:

wireless profile power power-save
            10 radio 5ghz state shutdown
            20 radio secondary-5ghz state shutdown
            30 radio 6ghz state shutdown
            40 usb 0 state disable

The following example shows how to define a calendar profile:

wireless profile calender-profile name eve-to-midnight
            recurrence daily
            start 19:00:00 end 23:59:59
wireless profile calender-profile name midnight-to-morning
            recurrence daily
            start 00:00:00 end 07:00:00
wireless profile calender-profile name weekends
            recurrence weekly
            day Saturday
            day Sunday
            start 00:00:00 end 23:59:59

The following example shows how to define an AP join profile and map a calendar profile to a power profile:

ap profile wireless-prof-site1
	                calendar-profile eve-to-midnight
		                action power-saving-mode power-profile power-save
	                calendar-profile midnight-to-morning
		                action power-saving-mode power-profile power-save
	                calendar-profile weekends
		                action power-saving-mode power-profile power-save

Verifying Access Point Power Policy (GUI)

To verify the applied configuration on the GUI, follow these steps:

Procedure

Step 1

Choose Monitoring > AP Statistics.

Step 2

Click a Cisco Catalyst 9136 series AP from the list of APs.

The General window is displayed.

Step 3

Click the Power tab.

The Power Operational Status and the AP Fixed Power Policy details are displayed.

Step 4

Click OK.

To verify the AP fixed power policy details from the list of configured APs, follow these steps:

Procedure

Step 1

Choose Configuration > Access Points.

Step 2

Click a Cisco Catalyst 9136 series AP from the list of APs.

The Edit AP window is displayed.

Step 3

Click the Interfaces tab.

The AP Fixed Power Policy details are displayed.

Step 4

Click Update & Apply.

Verifying the Access Point Power Profile

To view the calendar profile and its mapping, run the following command:

Device# show ap profile name default-ap-profile detailed
AP Profile Name                     : default-ap-profile
Description                         : default ap profile
Power profile name                  : power_prof_day
AP packet capture profile           : Not Configured
AP trace profile                    : Not Configured
Mesh profile name                   : default-mesh-profile
Power profile name                  : Not Configured
Calendar Profile
    Profile Name                   : cal47
    Power saving mode profile name : pow_da
    ----------------------------------------------------
    Profile Name                   : cal48
    Power saving mode profile name : pow23
    ----------------------------------------------------

To view the operational details of the AP, run the following command:
Device# show ap name cisco-ap power-profile summary
AP power derate Capability      : Capable

Power saving mode
Power saving mode profile        : pow2
Associated calendar profile      : cal1

AP power profile status         : Insufficient De-rating

Interface    Interface-ID       Parameter        Parameter value    Status
---------------------------------------------------------------------------------------
Radio        5 GHz              State            DISABLED           Success             
Radio        6 GHz              State            DISABLED           Not Applicable      
Ethernet     LAN1               State            DISABLED           Not Applicable      
Radio        2.4 GHz            State            DISABLED           Success             
Ethernet     Gig0               Speed            5000 MBPS          Fixed Policy

AP power derate capability is displayed in the output as Capable only for those APs that support power policy. For the other APs, it is displayed as Not Capable.

In the show ap name cisco-ap power-profile summary output, in the power saving mode, the status of the interface configured in the power profile (for example, pow2) is applied on the AP, and the AP sends the details (that are displayed in the show command) such as, the name of the power saving profile and the associated calendar profile.

The table that is displayed shows the interfaces and the parameter status of the power saving profile. The AP sends the information as to which of the interfaces are disabled. For example, if the AP does not have a 6-GHz radio interface, the Status is displayed as Not Applicable. If the interfaces are applied without any errors, then Success is displayed.


Note

When the AP uses the fixed power policy, due to inactive calendar or client connectivity, the interfaces are not displayed in the power profile summary if their status is UP on the AP.

Verifying Radio Spatial Streams

To view the configuration and operational details of radio spatial stream rules in the power profile, run the following commands:
Device# show wireless profile power detailed wireless_pow_profile_name 
Power profile name             : wireless_pow_profile_name
-------------------------------------------------
Description                    : 
.
.
Seq No       Interface    Interface-id       Parameter        Parameter value
-------------------------------------------------------------------------------
100          Radio        6 GHz              Spatial Stream   2 x 2             
200          Radio        5 GHz              Spatial Stream   8 x 8             
400          USB          USB0               State            DISABLED          
500          Ethernet     Gig0               Speed            100 MBPS          
600          Radio        6 GHz              State            DISABLED          
700          Radio        2.4 GHz            State            DISABLED          
900          Radio        5 GHz              State            DISABLED          
Device# show ap name cisco-ap-name power-profile summary
AP power derate Capability      : Capable

AP fixed power policy
---------------------

Interface    Interface-ID       Parameter        Parameter value    Status
---------------------------------------------------------------------------------------
Ethernet     Gig0               Speed            5000 MBPS          Fixed Policy        
Radio        2.4 GHz            Spatial Stream   4 x 4              Fixed Policy        
Radio        5 GHz              Spatial Stream   8 x 8              Fixed Policy        
Radio        Sec 5 GHz          Spatial Stream   4 x 4              Fixed Policy        
USB          USB0               State            DISABLED           Fixed Policy

Information About Access Point Real-Time Statistics

From Cisco IOS XE Bengaluru 17.5.1 onwards, you can track the CPU utilization and memory usage of an AP, and monitor the health of an AP, by generating real-time statistics for an AP.

SNMP traps are defined for CPU and memory utilization of APs and the controller. An SNMP trap is sent out when the threshold is crossed. The sampling period and statistics interval can be configured using SNMP, YANG, and CLI.

Statistics interval is used to process the data coming from an AP, and the average CPU utilization and memory utilization is computed over time. You can also configure an upper threshold for these statistics. When a statistic value surpasses the upper threshold, an alarm is enabled, and an SNMP trap is triggered.

From Cisco IOS XE Cupertino 17.7.1 release onwards, for radio monitoring, you can reset the radios based on the statistics sent by the AP for a sampling period. When you configure the radios in the controller, if there is no increment in the Tx or Rx statistics when the radio is up, then the radio reset is triggered.

Feature History for Real Time Access Point Statistics

This table provides release and related information for the feature explained in this module.

Table 7. Feature History for Real Time Access Point Statistics

Release

Feature

Feature Information

Cisco IOS XE Cupertino 17.7.1

Real Time Access Point Statistics

This feature is enhanced with the implementation of AP threshold values between 0 and 50 to trigger an alarm.

Restrictions for AP Radio Monitoring Statistics

You cannot reset the radio firmware from the controller. The controller will shut and unshut the radio if the Rx or Tx count is not incremented for a radio slot in a specified period.

Configuring Access Point Real Time Statistics (GUI)

Procedure

Step 1

Choose Configuration > Tags & Profiles > AP Join.

Step 2

Click Add. The Add AP Join Profile page is displayed.

Step 3

Under the AP tab, click the AP Statistics tab.

Step 4

In the System Monitoring section:

  1. Enable Monitor Real Time Statistics to get calculated statistics and alarms of the AP.

  2. To receive an alarm when the upper threshold is surpassed for parameters such as CPU utilization and memory, enable Trigger Alarm for AP.

  3. Enter the threshold percentage for CPU and memory usage in the CPU Threshold to Trigger Alarm field and Memory Threshold to Trigger Alarm fields, respectively. The valid range is between 0 to 50. An SNMP trap is sent out when this threshold is crossed.

  4. In the Interval to Hold Alarm field, enter the time for which the alarm is held before it gets triggered. The valid range is between 0 and 3600 seconds.

  5. In the Trap Retransmission Time field, enter the time between retransmissions of the alarm. The valid range is between 0 and 65535 seconds.

  6. To define how often data should be collected from the AP, enter a value in the Sampling Interval field. The valid range is between 720 and 3600 seconds.

  7. To define the interval at which AP statistics are to be calculated, enter a value in the Statistics Interval field. The valid range is between 2 and 900 seconds.

  8. To automatically reload the AP when there is high CPU and memory usage in the defined sampling interval, select the Reload the AP check box.

Step 5

Under the Radio Monitoring section:

  1. Select the Monitoring of AP Radio stuck check box to verify that the Tx and Rx statistics of the AP are updated each time the payloads are coming in from the AP to the controller.

  2. To generate an alarm for the radio of the AP when there is no increment in the Tx and RX statistics for the payloads, select the Alarms for AP Radio stuck check box.

  3. Select the Reset the stuck AP Radio check box to recover the radio from the bad state. A radio admin state payload will be sent from the controller to toggle the radio and the radio will be shut when there is no increment in the Tx and Rx statistics.

  4. To define how often data should be collected from the radio, enter a value in the Sampling Interval field. The valid range is between 720 and 3600 seconds.

Step 6

Click Apply to Device to save the configuration.

Configuring Real-Time Access Point Statistics (CLI)

Procedure

  Command or Action Purpose

Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

ap profile ap-profile-name

Example:

Device(config)# ap profile doc-test

Configures the AP profile. The default AP join profile name is default-ap-profile.

Step 3

stats-timer frequency

Example:

Device(config-ap-profile)# stats-timer 60

(Optional) Configures the statistics timer. This command is used to change the frequency of the statistics reports coming from the AP. The valid values range between 0 and 65535 seconds.

Step 4

statistics ap-system-monitoring enable

Example:

Device(config-ap-profile)# statistics ap-system-monitoring enable

(Optional) Enables monitoring of AP real-time statistics (CPU and memory).

Step 5

statistics ap-system-monitoring alarm-enable

Example:

Device(config-ap-profile)# statistics ap-system-monitoring alarm-enable

Enables alarms for AP real-time statistics (CPU and memory).

Step 6

statistics ap-system-monitoring alarm-hold-time duration

Example:

Device(config-ap-profile)# statistics ap-system-monitoring alarm-hold-time 400

Defines the alarms for AP real-time statistics (CPU and Memory). The valid values range between 0 and 3600 seconds.

Step 7

ap-system-monitoring alarm-retransmit-time duration

Example:

Device(config-ap-profile)# ap-system-monitoring alarm-retransmit-time 100

Defines the interval between retransmissions of the trap alarm. The valid values range between 0 and 65535 seconds.

Step 8

statistics ap-system-monitoring cpu-threshold percentage

Example:

Device(config-ap-profile)# statistics ap-system-monitoring cpu-threshold 30

Defines the threshold for CPU usage on the AP (percentage) to trigger alarms.

Note

 

From Cisco IOS XE Cupertino 17.7.1 release onwards, the valid threshold value for CPU on the AP to trigger the alarms is between 0 and 50.

Step 9

ap-system-monitoring mem-threshold percentage

Example:

Device(config-ap-profile)# ap-system-monitoring mem-threshold 40

Defines the threshold for memory usage on AP to trigger alarms. The percentage of threshold for memory usage on the AP to trigger is between 0 and 100.

Note

 

From Cisco IOS XE Cupertino 17.7.1 release onwards, the valid threshold value for memory usage on the AP to trigger the alarms is between 0 and 50.

Step 10

ap-system-monitoring sampling-interval duration

Example:

Device(config-ap-profile)# statistics ap-system-monitoring sampling-interval 600

(Optional) Defines the sampling interval. The valid values range between 2 and 900 seconds.

Step 11

exit

Example:

Device(config-ap-profile)# exit

Exits from AP profile configuration mode and returns to global configuration mode.

Step 12

trapflags ap ap-stats

Example:

Device(config)# trapflags ap ap-stats

Enables sending AP-related traps. Traps are sent when statistics exceed the configured threshold.

Example


    Device(config)# ap profile default-policy-profile
    Device(config-ap-profile)# statistics ap-system-monitoring enable
    Device(config-ap-profile)#statistics ap-system-monitoring sampling-interval 90
    Device(config-ap-profile)#statistics ap-system-monitoring stats-interval 120
    Device(config-ap-profile)#statistics ap-system-monitoring alarm-enable
    Device(config-ap-profile)#statistics ap-system-monitoring alarm-hold-time 3
    Device(config-ap-profile)#statistics ap-system-monitoring alarm-retransmit-time 10
    Device(config-ap-profile)#statistics ap-system-monitoring cpu-threshold 90
    Device(config-ap-profile)#statistics ap-system-monitoring mem-threshold 90
    Device(config)# trapflags ap ap-stats

Configuring AP Radio Monitoring Statistics

Procedure

  Command or Action Purpose

Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

ap profile profile-name

Example:

Device(config)# ap profile test1

Configures an AP profile and enters the AP profile configuration mode.

Step 3

statistic ap-radio-monitoring enable

Example:

(config-ap-profile)#statistic ap-radio-monitoring enable

Enables the monitoring of AP radio stuck statistics.

Step 4

statistic ap-radio-monitoring alarm-enable

Example:

(config-ap-profile)#statistic ap-radio-monitoring alarm-enable

(Optional) Enables the alarm for AP radio stuck statistics.

Step 5

statistic ap-system-monitoring action reload-ap interval duration

Example:

(config-ap-profile)# statistic ap-radio-monitoring action reload-ap interval850

(Optional) Specifies the sampling interval in seconds. The valid values range between 720 and 3600 seconds.

Step 6

statistic ap-radio-monitoring action radio-reset

Example:

(config-ap-profile)# statistic ap-radio-monitoring action radio-reset

(Optional) Generates an alarm and resets the radio if the radio is stuck.

Step 7

statistic ap-system-monitoring action reload-ap

Example:

(config-ap-profile)# statistic ap-system-monitoring action reload-ap

Reloads the AP.

Example


    Device(config)# ap profile test1
    Device(config-ap-profile)# statistics ap-radio-monitoring enable
    Device(config-ap-profile)#statistic ap-radio-monitoring alarm-enable
    Device(config-ap-profile)#statistic ap-radio-monitoring sampling-interval 750
    Device(config-ap-profile)# statistic ap-radio-monitoring action radio-reset
    Device(config-ap-profile)#statistic ap-system-monitoring action reload-ap

Monitoring Access Point Real-Time Statistics (GUI)

Procedure

Step 1

Choose Monitoring > Wireless > AP Statistics.

Step 2

Click the General tab.

Step 3

Click an AP name. The General window is displayed.

Step 4

To view the AP Statistics data, click the AP Statistics tab.

The following information is displayed:

  • Memory alarm last send time: Displays the time of the last memory trap sent.

  • Memory Alarm Status: Displays the state of the memory alarm. An alarm can be ACTIVE, INACTIVE, INACTIVE_SOAKING, ACTIVE_SOAKING. An alarm is soaked until the configured hold time has passed.

  • Memory alarm raise time: Displays the last time the memory alarm was active.

  • Memory alarm clear time: Displays the last time the memory alarm was inactive.

  • Last statistics received: Displays the time of the last statistics report received from the AP.

  • Current CPU Usage: Displays the latest percentage of CPU usage reported.

  • Average CPU Usage: Displays the average CPU usage calculated.

  • Current Memory Usage: Displays the latest percentage of memory usage reported.

  • Average Memory Usage: Displays the average memory usage calculated.

  • Current window size: Displays the window size. The window size is calculated by dividing the statistics interval by the sampling interval. The average CPU and memory usage is calculated by the window size.

  • CPU alarm last send time: Displays the time of the last CPU trap sent.

  • CPU Alarm Status: Displays the state of the CPU alarm. An alarm can be ACTIVE, INACTIVE, INACTIVE_SOAKING, ACTIVE_SOAKING. An alarm is soaked until the configured hold time has passed.

  • CPU alarm raise time: Displays the last time the CPU alarm was active.

  • CPU alarm clear time: Displays the last time the CPU alarm was inactive.

Step 5

Click OK.

Verifying Access Point Real-Time Statistics

To verify AP real-time statistics, run the show ap config general | section AP statistics command: 

Device# show ap config general | section AP statistics
!Last Statistics 
AP statistics : Enabled
Current CPU usage : 4
Average CPU usage : 49
Current memory usage : 35
Average memory usage : 35
Last statistics received : 03/09/2021 15:25:08
!Statistics Configuration
Current window size : 1
Sampling interval : 30
Statistics interval : 300
AP statistics alarms : Enabled
!Alarm State - Active, Inactive, Inactive_Soaking, Inactive_Soaking
Memory alarm status : Active
Memory alarm raise time : 03/09/2021 15:24:29
Memory alarm clear time : NA
Memory alarm last send time : 03/09/2021 15:24:59
CPU alarm status : Inactive
CPU alarm raise time : 03/09/2021 15:24:25
CPU alarm clear time : 03/09/2021 15:25:05
CPU alarm last send time : 03/09/2021 15:25:05
!Alarm Configuration
Alarm hold time : 6
Alarm retransmission time : 30
Alarm threshold cpu : 30
Alarm threshold memory : 32

To verify the statistics reporting period, run the show ap config general | i Stats Reporting Period command: 

Device# show ap config general | i Stats Reporting Period
Stats Reporting Period : 10

Was this Document Helpful?

FeedbackFeedback

Contact Cisco