Q: Things to be checked when mDNS Process Consumes 100% CPU utilization
A: Things to be checked when mDNS Process Consumes 100% CPU utilization
=========================================================
The mDNS process could consume 100% CPU utilization because of multiple reasons. To diagnose why the mDNS process consumes 100% CPU utilization, perform the following checks:
1: Check the status of the current credits by issuing the show airgroup global-credits command.
The following is the sample output of the show airgroup global-credits command where the current credits are high:
(host) #show airgroup global-credits
Global Credits - Default
------------------------
Type Value
---- -----
Query Packets 800
Response Packets 300
Global Credits - Current
------------------------
Type Value
---- -----
Query Packets 30
Response Packets 10
Note
=====
The credits are used within a predefined time window. For example, if the credits are set to 900 and 300 for query packets and response packets respectively, they are used within 30 seconds (predefined time window). At the end of the predefined time window, the credits are renewed and are available for the next predefined time window. Based on the rate of queries and responses, the credits could be used unevenly within the predefined time window. This may lead to the availability of high credits for the remaining time of the predefined time window which may lead to higher CPU utilization.
2:If the current credits are high, reconfigure the credits by issuing the airgroup global-credits command in the config mode.
The following is the output of the airgroup global-credits command:
(host) #configure terminal
(host) (config) #airgroup global-credits 700 200
The following is the sample output of the show airgroup global-credits command after reconfiguring the credits:
(host) #show airgroup global-credits
Global Credits - Default
------------------------
Type Value
---- -----
Query Packets 700
Response Packets 200
Global Credits - Current
------------------------
Type Value
---- -----
Query Packets 50
Response Packets 30
3: Check if the allowall service or Any undesired services are enabled .
(host) #show airgroup status
AirGroup Feature
----------------
Status
------
Enabled
AirGroup- MDNS Feature
----------------------
Status
------
Enabled
AirGroup- DLNA Feature
----------------------
Status
------
Enabled
AirGroup Location Discovery
---------------------------
Status
------
Enabled
AirGroup Active Wireless Discovery
----------------------------------
Status
------
Enabled
AirGroup Enforce Registration
-----------------------------
Status
------
Disabled
AirGroup IPV6 Support
---------------------
Status
------
Disabled
AirGroup Service Information
----------------------------
Service Status
------- ------
airplay Enabled
airprint Enabled
itunes Enabled
remotemgmt Disabled
sharing Disabled
chat Disabled
googlecast Enabled
DIAL Enabled
DLNA Media Disabled
DLNA Print Disabled
allowall Disabled
clearpass Enabled
4:Disable any undesired service by issuing the airgroup service <service name> disable command in the config mode (where <service name> is the name of the undesired service).
Eg
(host) #configure terminal
(host) (config) #airgroup service itunes disable
5:Enable location policies on the servers for efficient cache management by issuing the autoassociate command for the desired service in the config mode.
The following is the sample output of the autoassociate command for the airplay service:
(host) #configure terminal
(host) (config) #airgroupservice airplay
(host) (config-airgroupservice) #autoassociate
If not Use CPMM to Actively manage the devices with the location policies.