topic Re: Mac Devices failed to connect when AutoQoS is set to Fastlane in Wireless

Mac Devices failed to connect when AutoQoS is set to Fastlane

MUP0 — Mon, 21 Aug 2023 19:44:51 GMT

Hi,

we are running SDA with Wireless. Today I enabled Fastlane checkmark under the SSID setup (Design > Network Settings > Wireless), which basically, does the following, as far as I know:

1. changes the EDCA per band from wmm-default to fastlane, if not already changed.

2. It is also supposed to change the port config, but since this is a FIAB switch with Wired QoS config pushed from DNA, I dont think it changes any port config due to fastlane

3. Changes the QoS per SSID/Policy config as below:

======== BEFORE ENABLING FASTLANE on SSID =========

wireless profile policy Guest-LAB_profile

aaa-override

accounting-list dnac-acct-Guest

no central dhcp

no central switching

description Guest-LAB_profile

dhcp-tlv-caching

exclusionlist timeout 180

fabric Guest-LAB_profile

http-tlv-caching

nac

radius-profiling

service-policy input platinum-up < ================= REMOVED

service-policy output platinum < ================= REMOVED

session-timeout 28800

no shutdown

======== AFTER ENABLING FASTLANE on SSID =========

wireless profile policy Guest-LAB_profile

aaa-override

accounting-list dnac-acct-Guest

autoqos mode fastlane < ================= ADDED

no central dhcp

no central switching

description Guest-LAB_profile

dhcp-tlv-caching

exclusionlist timeout 180

fabric Guest-LAB_profile

http-tlv-caching

nac

radius-profiling

session-timeout 28800

no shutdown

So when this is pushed, Mac devices have issues connecting to the network and this is the error I've got:

%QOS_ERROR_MESSAGE-3-QOS_MSG_BLKLIST_CLIENT: Switch 1 R0/0: wncd: Blacklisting client xxxx.6636.xxxx. Error installing client QOS policy: voice-client-avc in Downstream direction.

Aug 21 08:11:00.319: %CLIENT_EXCLUSION_SERVER-5-ADD_TO_EXCLUSION

Have anyone experienced this?

This is a lab Fabric-in-a-Box switch with embedded wireless. It is a 9300 device running 17.9.3 with the respective 9800 image.

Re: Mac Devices failed to connect when AutoQoS is set to Fastlane

Mark Elsen — Tue, 22 Aug 2023 06:41:04 GMT

- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc42784
- Have try with 17.9.4

Re: Mac Devices failed to connect when AutoQoS is set to Fastlane

MUP0 — Tue, 22 Aug 2023 09:21:43 GMT

Thanks, but I dont think i am hitting that bug, could be some other but:

1. as you can see the client QoS is removed

2. 17.9.3 is listed in the known fixed relieses for that one

Re: Mac Devices failed to connect when AutoQoS is set to Fastlane

Mark Elsen — Tue, 22 Aug 2023 09:28:05 GMT

- Ok, have a try with 17.9.4 anyway ,

Re: Mac Devices failed to connect when AutoQoS is set to Fastlane

BertiniB — Sat, 05 Jul 2025 15:54:01 GMT

@MUP0 Did you ever find a solution for this problem? I am in 17.12.4 and having the exact same problem. Fastlane doesn't work with EWC.

Re: Mac Devices failed to connect when AutoQoS is set to Fastlane

Rich R — Sun, 06 Jul 2025 14:37:07 GMT

@BertiniB have you checked out https://support.apple.com/en-gb/guide/deployment/dep271900868/web ?

Re: Mac Devices failed to connect when AutoQoS is set to Fastlane

Saikat Nandy — Mon, 07 Jul 2025 02:48:42 GMT

most likely you are hitting - https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwi39123

This issue has not been reproduced during internal repro. If you have convenient time to tshoot, please open a TAC case and share this defect. Team will try to figure out the root cause and a fix.

Re: Mac Devices failed to connect when AutoQoS is set to Fastlane

MUP0 — Mon, 07 Jul 2025 10:50:16 GMT

Hi @BertiniB

I have a workaround for my usecase, but it might be different for you, depending what you want to achieve.

For me, the goal was to set the EDCA to Fastlane (which is a global per band setting, not per SSID). And I wanted to do that via "intent-based" setting, not pushing it with a CLI template. I didn't really need to have the Fastlane QoS profile, as I would prefer to define QoS policy myself.

With that said, my workaround was to configure an additional (dead/shutdown/non-broadcasted SSID) with the Fastlane AutoQoS enabled. The sole purpose of that SSID was to set the global EDCA to fastlane 🙂

QoS, as I mentioned, I prefer to define myself, so that is pushed with a Wireless QoS policy from Catalyst Center.

I hope that helps.