GT AX-6000 (Merlin): acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER message every 20 minutes

[pgershon]

New GT AX-6000 router running latest Merlin. Still getting bugs out of set-up. This message flashes every 20 minutes or so in log. What is going on and how do I correct? Thanks for the input...

 

[Tech9]

Automatic Channel Selection. If you fix the channel it will stop. Not sure about your 160MHz wide channel, may or may not work - Wi-Fi environment specific. Your router also has shorter range with 160MHz wide channel enabled. May be a problem with clients closer to the edges of usable signal.

 

[ColinTaylor]

That's a fairly normal message when you have Auto channel selected on the 5GHz band. Every 20 minutes acsd looks to see if there's a better channel to switch to.

If you think there's a problem with your router we'd need to see all of the messages in the syslog to understand the context.

 

[pgershon]

Here is the whole log since we left the house yesterday. First entry is my cellphone being dropped. Not sure what this entry means? I am assuming it is a device connected to one of the physical hardwired ports:

Jun 18 13:53:02 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jun 18 13:53:46 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 10 mbps half duplex
Jun 18 13:55:15 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jun 18 13:55:19 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 100 mbps full duplex


Jun 17 20:56:35 wlceventd: wlceventd_proc_event(530): eth7: Auth 8C:EC:7B:07:81:35, status: Successful (0), rssi:-69
Jun 17 20:56:35 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc 8C:EC:7B:07:81:35, status: Successful (0), rssi:-69
Jun 17 20:56:52 roamast: [EXAP]Deauth old sta in 1 0: 8C:EC:7B:07:81:35
Jun 17 20:56:52 roamast: eth7: disconnect weak signal strength station [8c:ec:7b:07:81:35]
Jun 17 20:56:52 roamast: eth7: remove client [8c:ec:7b:07:81:35] from monitor list
Jun 17 20:56:53 wlceventd: wlceventd_proc_event(511): eth7: Disassoc 8C:EC:7B:07:81:35, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 17 21:05:53 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 17 21:39:19 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 17 22:13:00 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 17 22:46:21 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 17 23:19:40 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 17 23:52:57 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 00:26:19 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 00:59:46 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 01:33:04 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 02:06:32 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 02:39:57 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 03:13:19 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 03:46:42 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 04:20:05 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 04:53:26 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 05:26:51 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 06:00:12 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 06:33:30 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 07:06:53 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 07:40:11 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 08:13:33 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 08:46:54 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 09:20:15 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 09:53:36 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 10:26:54 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 11:00:14 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 11:33:35 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 12:06:57 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 12:40:13 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 13:13:37 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 13:53:02 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jun 18 13:53:46 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 10 mbps half duplex
Jun 18 13:55:15 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jun 18 13:55:19 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 100 mbps full duplex
Jun 18 14:20:20 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 14:53:43 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 15:27:02 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 15:43:55 BWDPI: [BWMON] Revert process and free memory (pid=5992)
Jun 18 16:00:22 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 16:33:43 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 18 17:07:08 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER

 

[sfx2000]

That's a fairly normal message when you have Auto channel selected on the 5GHz band. Every 20 minutes acsd looks to see if there's a better channel to switch to.

I agree - looks like Asus left some debug turned on, so one will see events like this...

 

[ColDen]

I have a GT-AX6000 with Wireless Mode on Auto on the 5GHz band and never saw this message so far.

 

[ColinTaylor]

I have a GT-AX6000 with Wireless Mode on Auto on the 5GHz band and never saw this message so far.

Thanks for the extra info. It's possible that the log level of those messages has changed. The same messages were mentioned in this post about the GT-AX6000.

@pgershon Have you changed the syslog levels in System Log - General Log?

 

[ColDen]

Thanks for the extra info. It's possible that the log level of those messages has changed. The same messages were mentioned in this post about the GT-AX6000.

@pgershon Have you changed the syslog levels in System Log - General Log?

Hi Colin,

You may be on something as I have just noticed that the OP posted log (and from DAOWAce in your linked post) seem to be from the basic "General Log" and not like mine which is enhanced by Scribe:

 

[pgershon]

I am pretty sure that the general log is unchanged. The only change I made to the router was to upgrade the firmware to latest Merlin 388.2.2 ROG version. I attached my wifi setup page. Two differences I see are (1) I have auto select channel including DFS checked, and ColDen does not; and (2) I enable target wake time, and ColDen disabled (I have no idea what that does).

Also, the "kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN." messages I got seem to be my old Apple Airport Express V2 crapping out and resetting itself.

 

[ColinTaylor]

@pgershon Your screenshot shows you using channel 157 but in your initial post it was trying to use channel 100. Have the messages in the log now changed?

 

[ColDen]

I am pretty sure that the general log is unchanged. The only change I made to the router was to upgrade the firmware to latest Merlin 388.2.2 ROG version. I attached my wifi setup page. Two differences I see are (1) I have auto select channel including DFS checked, and ColDen does not; and (2) I enable target wake time, and ColDen disabled (I have no idea what that does).

Also, the "kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN." messages I got seem to be my old Apple Airport Express V2 crapping out and resetting itself.

Please note that I am using the proposed default settings (no customization).

 

[pgershon]

@pgershon Your screenshot shows you using channel 157 but in your initial post it was trying to use channel 100. Have the messages in the log now changed?

The last message I got said 100/160, just like all the others. Not sure why the difference.

But I should note that, as I was posting screenshots last night, I noticed that QoS was switched on, and I turned it off. I have 1000/1000 internet and do not believe it is useful (I get faster speeds with Speedtest with QoS off) for me. Since switching off QoS, I have not gotten any ACSD messages (last at 11:48 PM last night).

 

[pgershon]

Jun 18 13:53:02 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jun 18 13:53:46 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 10 mbps half duplex
Jun 18 13:55:15 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Jun 18 13:55:19 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 100 mbps full duplex

I have verified. These entries are my Airport Express router reseting itself and needing to be reinitialized. It has happened 4 time over last 72 hours. Time to replace the 2010 unit. Was only being used to send Airplay music to my whole house speaker system (Concerto) - will get a new AirPlay 2 wireless preamp device to replace it.

 

[ColDen]

The last message I got said 100/160, just like all the others. Not sure why the difference.

But I should note that, as I was posting screenshots last night, I noticed that QoS was switched on, and I turned it off. I have 1000/1000 internet and do not believe it is useful (I get faster speeds with Speedtest with QoS off) for me. Since switching off QoS, I have not gotten any ACSD messages (last at 11:48 PM last night).

For your information, I also have QoS off.

 

[pgershon]

I have a feeling the message is somehow linked to QoS, as it stopped as soon as I turned off QoS.

 

[ColDen]

I have a feeling the message is somehow linked to QoS, as it stopped as soon as I turned off QoS.

This is why, before customizing a router, I always wait a few days with the default settings to make sure that whatever spotted suspious/error messages were not caused by them (I also usually make one customization at a time to simplify the troubleshooting).

 

[pgershon]

ASCD messages came back every 30 mins or so for a 2.5 hour period this evening, then stopped (still 100/160). Very odd I think. Came up when no devices were roaming on and off their locations. When I look at wireless page now, it says I am currently at 157, as it did last I looked:

Jun 19 19:24:26 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 5C:3E:1B4:C1:1D, status: 0, reason: Disassociated due to inactivity (4), rssi:-91
Jun 19 19:26:37 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 19 19:59:55 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 19 20:33:12 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 19 21:06:29 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 19 21:39:48 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 19 22:13:05 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 19 22:46:25 acsd: acs_set_chspec: 0xe872 (100/160) for reason ACS_CSTIMER
Jun 19 23:02:02 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind B4:B0:24:B4:6C:AB, status: 0, reason: Disassociated due to inactivity (4), rssi:-49