CPU usage issues on AP230's.

[mali]

What are these log entries for? Also "show system proc stat"s hows mdnsd is on the top.

2018-05-17 16:14:47 info   ah_scd: arbitrator ip is updated from 10.119.0.21 to 10.119.0.87

2018-05-17 16:14:47 info   ah_dcd: IDP: arbitrator ip is updated from 10.119.0.21 to 10.119.0.87

2018-05-17 16:14:44 info   ah_dcd: IDP: arbitrator ip is updated from 10.119.0.126 to 10.119.0.21

2018-05-17 16:14:44 info   ah_scd: arbitrator ip is updated from 10.119.0.126 to 10.119.0.21

2018-05-17 16:14:26 info   ah_scd: arbitrator ip is updated from 10.119.0.21 to 0.0.0.0

2018-05-17 16:14:26 info   ah_dcd: IDP: arbitrator ip is updated from 10.119.0.21 to 0.0.0.0

2018-05-17 16:14:17 info   ah_scd: arbitrator ip is updated from 0.0.0.0 to 10.119.0.21

2018-05-17 16:14:17 info   ah_dcd: IDP: arbitrator ip is updated from 0.0.0.0 to 10.119.0.21

2018-05-17 16:14:16 info   amrp2: create node 10.119.0.21(d854:a2cb:xxxx), no_eth_comp_count = 0

2018-05-17 16:14:14 info   amrp2: delete node 10.119.0.21(d854:a2cb:xxxx), no_eth_comp_count = 0

2018-05-17 16:13:42 info   amrp2: create node 10.119.0.21(d854:a2cb:xxxx), no_eth_comp_count = 0

[dsouri]

Hi Mohammad,

Is this behavior still happening? Could you screenshot the following command outputs?

show sys proc state

show forward count int eth0

Ultimately, the best way to get that mDNS load down is to complete a packet capture at one of the ports, and determine what the source of all the traffic is.

Load Average at 2.4 is alarming, because this means the AP is Queuing up more than twice as much as it's handling.

Those outputs would tell a lot more, happy to assist.

David Souri

HiveCommunity Moderator

[mali]

So I disabled Bonjour but had to update the software from 6.5r4 to 8.1r2a to push the config. Now interesting thing is that once the AP's got updated to 8.1r2a mdsnd load went down.

Then after I was able to push the config that load went down on the AP's with 6.5r4 which I was expecting.

Here is a quick screen shot of load average. Looks over 2.

[dsouri]

Hello,

Typically when mdnsd is the top process, it indicates that devices on the network are Multicasting a high rate.

Multicast (mDNS) is common with mobile devices like Apple iPads/Notebooks, Chrome devices, as well as other new devices as Multicast is being utilized more and more.

This may not be an issue though, as the CPU is meant to work (just not over-work). To see if there is anything overloading the CPU, please reference the command 'show system proc state' and the output 'Load Average'. If the Load Average is 0.0 to 1.0, then we'll know this is normal behavior.

Do any of these log entries correlate with connectivity issues on the ground? Are there any reports from Client-Users about connectivity issues?

Hope this helps, happy to assist,

David Souri

Community Moderator