Yann
I think you may have chopped the end of the message, the number that is incrementing is a timestamp - there should be stuff after it, example:
Apr 23 01:07:24 KERNEL(ap225-sales@10.74.32.131): [149815.906120] <64:76:ba:ae:2f:7e> [wlc_dotxstatus@40810]:sent data packet dcae8900, seqnum 0x568, pkttag->seq = 0x568, was_acked 1, supr_status 0
Apr 23 01:07:24 KERNEL(ap225-sales@10.74.32.131): [149816.061422] <64:76:ba:ae:2f:7e> [wlc_dotxstatus@40810]:sent data packet dcae8900, seqnum 0x568, pkttag->seq = 0x568, was_acked 1, supr_status 0
Apr 23 15:28:31 KERNEL(ap225-sales@10.74.32.131): [201483.270693] chan dur ibss obss interf time
Apr 23 15:28:31 KERNEL(ap225-sales@10.74.32.131): [201483.353060] 161 1002 4 0% Low 139 13% Medium 8305 828% High 201480
Apr 23 15:28:31 KERNEL(ap225-sales@10.74.32.131): [201483.438514] 161 1000 9 0% Low 55 5% Low 21 2% Low 201479
Apr 23 15:28:31 KERNEL(ap225-sales@10.74.32.131): [201483.522918] 161 1000 8 0% Low 80 8% Low 24 2% Low 201478
It appears R&D has decided to start sending the ap console log messages from the AP to the controller into the system log. I am trying to find out if this is really what they wanted to do as it's going to create consternation for customers and these messages come with zero information outside of R&D - will update when I learn something, hopefully in next 48 hours.
I should add - these messages are probably just informational, despite some often scary sounding language - please post a snapshot of them here so we can try to make a judgement if you need a TAC case too. You can also find these logs in "show ap debug log ap-name <>"
regards
-jeff