Wireless Access

Hello,

 

for a few months now I see the following messages on my syslog server:

 

Message from syslogd@2014 at Jun 24 17:17:23 ...
172.20.90.232 KERNEL(M7A-1OG-AP06@172.20.90.232): [2882429.192087] Watchdog petted by same CPU 1 for 0 seconds. jiffies[1441214379] History[0100110101010101010011010101010101001101010101010101001101010]

Message from syslogd@2014 at Jun 24 19:07:03 ...
172.20.130.80 KERNEL(M7A-3OG-AP06@172.20.130.80): [2889023.887111] Watchdog petted by same CPU 1 for 0 seconds. jiffies[1444511726] History[0101010101010101010101010101010101010011010100110100101101010]

Message from syslogd@2014 at Jun 25 01:05:15 ...
172.20.70.187 KERNEL(G3-EG-AP05@172.20.70.187): [639189.800259] Watchdog petted by same CPU 1 for 0 seconds. jiffies[319594683] History[0101010101010101010101010101010101010101010101010101001101010]

Message from syslogd@2014 at Jun 25 01:18:12 ...
172.20.66.85 KERNEL(G1B-EG-AP01@172.20.66.85): [2911274.715021] Watchdog petted by same CPU 1 for 0 seconds. jiffies[1455637140] History[0011010101010101010101010101010101010101010101010101001101010]

Message from syslogd@2014 at Jun 25 01:22:28 ...
172.20.90.180 KERNEL(M7A-1OG-AP05@172.20.90.180): [2911536.133976] Watchdog petted by same CPU 1 for 0 seconds. jiffies[1455767850] History[0101010101001101010100110101010011010101010101010101001101010]

Message from syslogd@2014 at Jun 25 02:12:29 ...
10.32.60.188 KERNEL(MUC-BOO-UG-AP01@10.32.60.188): [2914527.474276] Watchdog petted by same CPU 1 for 0 seconds. jiffies[1457263520] History[0010101010100110101010101010101010101010101010101010010111010]

Message from syslogd@2014 at Jun 25 02:58:13 ...
172.20.79.142 KERNEL(G3-3OG-AP16@172.20.79.142): [38752.686315] Watchdog petted by same CPU 1 for 0 seconds. jiffies[19376126] History[0100110101010100110101010100110101010101010101010101001011010]

Message from syslogd@2014 at Jun 25 03:46:26 ...
172.20.70.208 KERNEL(G3-EG-AP10@172.20.70.208): [649117.296247] Watchdog petted by same CPU 1 for 0 seconds. jiffies[324558431] History[0010100110100110011010101010100101010011010101010101001101010]

Message from syslogd@2014 at Jun 25 04:14:58 ...
172.20.130.129 KERNEL(M7A-3OG-AP07@172.20.130.129): [2921872.112797] Watchdog petted by same CPU 1 for 0 seconds. jiffies[1460935839] History[0101010101010101010101010101010011010100110101010101001101010]

Message from syslogd@2014 at Jun 25 04:28:21 ...
172.20.90.228 KERNEL(M7A-1OG-AP07@172.20.90.228): [2922695.973942] Watchdog petted by same CPU 0 for 0 seconds. jiffies[1461347770] History[1100110101010101010101010101010101010101010010110101010101001]

Message from syslogd@2014 at Jun 25 07:18:30 ...
172.20.129.56 KERNEL(M7A-3OG-AP01@172.20.129.56): [2932903.732250] Watchdog petted by same CPU 1 for 0 seconds. jiffies[1466451649] History[0101010101010100110101010101010101010101010101010101001101010]

 

The problem is that these messages are being sent out as EMERGENCY messages and therefore appear within everybody's SSH session on the syslog server.

 

I have already removed the ap-debug category from the logging configuration on the controller but this has not made any difference.

 

Is there any way I can suppress these messages from being generated in the first place?

 

cheers,

Harald

#AP225

This is scheduled to be fixed in 6.3.1.9 or 6.4.1.0

 

Good morning.

 

I see the same messages in the log from a 7220 Controller every day.  The controller is running 6.3.1.2.  Can you confirm this is related to some type of bug fixed with a code upgrade?  Is there anything at all to be concerned with aside from updgrading the code?

 

thx

#7220

I upgraded to 6.3.1.9 last week and these syslog messages are gone now. No other issues with this release so I would recommend upgrading.

Yesterday we had ~200 of our APs reboot at the same time. Different buildings, different controllers, different vlans/subnets. If we have 20 APs in a building, maybe 10 of them rebooted, the other 10 were fine. 

 

In the logs on the controller, we see the "Watchdog petted by same CPU 0 for 10 seconds." or CPU 1 message for every AP that rebooted. If an AP didn't reboot, it's not on that list in the logs.

 

Is that expected behavior? That error message signifies an AP reboot? This isn't the first time it has happened, but I don't see the reboots mentioned above. 

I think you should open a case with TAC.  It just seems like you have many more issues going on than a message coming from an AP225 that needs looking at.

We're working on opening a TAC case. I'm more generally asking about what this error message actually means, and if a reboot is a normal component of it occurring. We have ~1500 APs, and it affected ~200 of them. And it has only happened every few months, not frequently. But I can't find any information about what that error message actually signifies. 

The error message itself does not have any real value outside of engineering. It does not automatically mean a reboot. If you want to get to the bottom of your reboot, you need to open a tac case and gather the logs before they roll over.

I am seeing a very very similar error in code that, up thread, we're told, should cotain the fix for this. The AP appears to be functioning correctly, it's just that syslog fills with this convoluted stuff:

 

10.245.17.182 <10.245.17.182 AC:A3:1E:C0:58:9A> KERNEL(ac:a3:1e:c0:58:9a@10.245.17.182): [ 1024.150024] Watchdog petted by same CPU 1 for 10 seconds. jiffies[511858] History[101010101010101010101010101010101010101010101010111111111111].
host 10.245.17.182

Name Aruba Operating System Software
AP Type: 275
Build Time: 2014-08-15 22:19:51 PDT
Version: 6.4.2.0-4.1.1.0_45444