topic good input in Wireless

WLC 5508 - management frames without DSCP marking

Heinz Kern — Mon, 05 Jul 2021 09:20:09 GMT

hello,

we are facing an issue that our wireless lan controller (5508 with version 7.6.100) doesn´t mark management frames (e.g. reassociation repsonse - necessary for roaming) with CS6. therefore some of them are dropped leaving the clients not to roam...

does anybody have an idea? in my view it can only be a biug because it´s noit possible to reconfigure this....

thx

That was a short lived code.

Scott Fella — Fri, 23 Jan 2015 12:53:43 GMT

That was a short lived code. You should upgrade to v7.6.130.0 as that was the stable release of v7.6.

-Scott

good input

Heinz Kern — Fri, 23 Jan 2015 13:20:29 GMT

good input

I'm curious is your WLC

George Stefanick — Fri, 23 Jan 2015 13:29:36 GMT

I'm curious is your WLC configured with the management vlan of the wlc to native and on the ports to the controller are you trusting cos ?

no it´s trunked on a port

Heinz Kern — Fri, 23 Jan 2015 13:48:27 GMT

no it´s trunked on a port-channel. nevertheless we are trusting dscp

Likly you are losing 802.1p

George Stefanick — Fri, 23 Jan 2015 14:13:19 GMT

Likly you are losing 802.1p tag because you aren't trusting cos and then it gets written down on dscp. Trust cos on the trucks to the wlc and test again.

That aside I don't think

George Stefanick — Fri, 23 Jan 2015 14:15:10 GMT

That aside I don't think management frames actually get marked .. I need to check on that

we are seeing managemt frames

Heinz Kern — Fri, 23 Jan 2015 17:51:22 GMT

we are seeing managemt frames getting marked on Wism. i strongly believe they were marked in the past also on 5508. moreover frames are getting marked when they arinitiated by the AP

if we trust CoS frames are getting marked because it contains the dot1p tag. the switch generates the dscp-value out of it. but we want to trust dscp.

we see also a very strange behaviour when trusting COS that sometimes a reassociation request has dot1p value 2 and the next one has 5. so it seems that the tag is there, but not working properly.

changing to CoS in general would mean testing the whole infrastructure for voip over wireless lan again. and i don´t want to do that

Are you referring to the

George Stefanick — Fri, 23 Jan 2015 17:54:27 GMT

Are you referring to the inner DSCP packet or the outer capwap DSCP marking ?

we are talking about

Heinz Kern — Fri, 23 Jan 2015 18:23:22 GMT

we are talking about management frames. they have only one dscp value

upgrade to 7.6.130 - the same

Heinz Kern — Sun, 25 Jan 2015 19:57:15 GMT

upgrade to 7.6.130 - the same behaviour

downgrade to 7.3.112 - DSCP values existing correctly

we didn´t test 7.6.100 deeply for QoS as we did for 7.3.112....not the best approach