cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1455
Views
0
Helpful
10
Replies

WLC 5508 - management frames without DSCP marking

Heinz Kern
Level 4
Level 4

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

10 Replies 10

Scott Fella
Hall of Fame
Hall of Fame

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

-Scott

-Scott
*** Please rate helpful posts ***

good input

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 ? 

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________

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

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. 

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________

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

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________

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 inner DSCP packet or the outer capwap DSCP marking ?

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________

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

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

Review Cisco Networking for a $25 gift card