Wireless QoS Profiles

Is anyone running Wireless QoS using 5508's? I have been reading lots of info, but still struggle with some of this. I have not dealt with QoS much on a wired network and never on a wireless network. I know there has to be a shared comfiguration between both. The whole point of QoS is end to end. When looking into the Wireless QoS profiles in the WLC, the Gold profile, which is stated for video doesnt even have any values configured? So even selecting this profile for the WLAN SSID, the values not being configured, tell me its not benifitting me at all.
Now can someone give me "slimmed" down info on ToS, CoS, and DSCP?
Another question I have is does my application need these values configured? In my video encoder there is an area for ToS and the value is 0, do I need to configure this for the traffic to be noticed on the network?

Steven
There is a lot to QOS on the network. There are three main points to keep in mind when working on QOS.
COS = Layer 2 packet markings
DSCP = Layer 3 packet markings
1. Marking
2. Trusting
3. Queuing
I suggest doing the research on what's important to your business and marking the more important traffic higher then the not so important traffic. If you are using Cisco Switches, I suggest using 4 classes because you only get 4 queues with most Cisco switches.
You need to trust DSCP for your Controller based AP's. You should trust DSCP on all of your switch uplinks.
Egress Queuing is very important. You need to allocate bandwidth to the queues on your ports. This assures that each queue gets the bandwidth that you want it to have.
Wireless QOS is a bit different. The client needs to set the DSCP value, then the controller needs to allow the DSCP value to be set to a specific level. You need to set the "platinum" profile to a 802.1p Tag to 6, this will allow packets to be marked with a COS value of 5 (I don't understand why Cisco did it this way, but it's how it is). Then you need to apply Platinum to your voice vlan.
Here is a link to my forum where I have posted a lot more regarding QOS. I hope this helps.
http://goatnetworking.com/forum/viewforum.php?f=8&sid=7e3372e32d3b9a20f9391696f7bed442

Similar Messages

WLC QoS Profiles not applying egress

In regards to QoS profiles on the WLC. I have applied a profile to a newly created WLAN and set the Per User Bandwidth to 512k and it seems to be kicking in on the ingress only, does anyone know if this is supposed to work ingress AND egress or is it just designed to work one way? I have a 4402-25 with Cisco 3500 AP's and am running the 7.0.98 code.
If it is designed to work one way only is there a different way to apply it ingress and egress simultanenously off the WLC?

Hello,
WLC QoS bandwidth policies do in fact only apply in the downstream direction. Clients will still be able to upload at an unlimited speed.
You will need to look at another solution if you need to limit upload speeds -- one example would be user-based rate limiting on the 6500 platform:
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_white_paper0900aecd803e5017.html
There are likely other solutions available as well.
-Patrick Croak
Wireless TAC

Apply QoS profile using RADIUS attributes

Hi all,
Anyone delved into the use of RADIUS attributes to apply QoS values (DSCP/802.1p) to wireless users via a WLC?
With the emergence of ISE and the concept of a shared SSID for several user types I may want to apply QoS profiles by user rather than SSID.
Do you need to apply the maximum value to the SSID for the attribute-derived value to work?
Can non-WMM client traffic be marked using this approach?
Plenty to think about here...
Any discussion welcome!
Cheers
Rob

Yo can apply QoS RADIUS override.
http://www.cisco.com/en/US/products/ps6307/products_tech_note09186a0080870334.shtml
Yes it would be best to apply the wlan max qos value to the level that you intend to use with the radius override. for example if you want to apply platinum qos for voice clients on the ssid, i would map the wlan to platinum qos.
i am not sure on the next question. I think u can assign a DSCP/802.1p to a non WMM clients but I dont think the non wmm clients will benefit from it as they will not tag their traffic and hence the AP and subsequently the wired network will treat it as best effort (untagged).
Thanks,

Wireless QoS - DSCP to 802.11e translation

Hi,
Would appreciate some advice, I am using a 5508 controller, I have an SSID that has WMM enabled and platinum QoS profile applied, with default settings. I have 802.11p set to none as we are not doing layer 2 QoS on the switches.
I found that when pinging a wireless client with DSCP set to EF the packets (all packets in fact) are being sent from the AP to the client with 802.11e set to zero. I verified this via AirPCAP.
Can someone confirm why the AP is not taking the DSCP marking from the outer LWAPP IP header and translating it to an 802.11e value?
My best guess is that I need to enable 802.11p on the QoS profile in order for the AP to start translating DSCP to 802.11e. The thing is that I don't particularly want to mark 802.11p as we will not be enabling QoS on the switches, and my understanding is that it's not really required in order for DSCP to be translated from the outer LWAPP IP header to the 802.11e field.
I've reviewed the Cisco documentation on wireless QoS, including the diagram showing the packet flow and copying of QoS markings at each step....
Thanks in advance,
Pete

Hi Pete,
If you are not enable QoS & disable re-write of DSCP on your switches, pretty much you will get the incoming packet DSCP when it leaves any switchport. Therefore WLC should get DSCP EF packets & outer CAPWAP should have DSCP EF. I have done a quick test to simulate your issue. WLAN configured for platinum QoS profile with 802.1p set to none. Wired PC - RTP traffic mark to EF in my case (as windows 7 does not correctly classify traffic).
1. Wired PC (IPCommunicator) ->Switch with no QoS -> AP -> Wireless client (7921 phone)
2. Wired PC (IPCommunicator) ->Switch with no QoS -> AP -> Wireless client (Laptop with IPC)
When I capture traffic for Cisco wireless phone I can see wireless frame is having UP value of "6-Voice". But when I do the testing for wirless laptop client I observed wireless frame are having UP of "0 - Best Effort" (as you observed as well). I would expected in both cases wireless frame UP to be zero. Not sure why behaviour differnt for Cisco 7921 phone.
Then I enabled QoS on the switch & trust DSCP on AP & wired PC connected port & CoS on WLC connected switch port. But left QoS profile 802.1p tag as " None". This time in both scenarios I have observed WMM_UP value "0-Best Effort" in wireless frames even though the AP received outer CAPWAP as EF. This is normal behaviour as QoS profile set to 802.1p to none & therefore outer CAPWAP will not translate to UP=6 as it is. It will cap to max of 802.1p configured (presumed none mean 0)
Finally when I set 802.1p tag to 6 on QoS profile & conduct the same test. I expected in both scenarios UP=6 for EF marked traffic to wireless client (cisco phone or wireless laptop). As expected Cisco phone received wireless frame had UP=6 Voice, but wireless laptop received frame had UP=0 best effort.
I am geussing this due to some kind of WMM incompatibility of different devices (not sure though). I will try to do this with some other clients ( jabber in iPhone & Galaxy SIII) & see any common behaviour.
As per the VoWLAN 4.1 design guide (page 2-18,19) 802.1p classification in QoS profile controll two behaviours
1. Determine what class of service (CoS) value is used for packets initiated from the WLC.
2. Determine the maximum CoS value that can be used by clients connected to that WLAN.
Regarding the QoS profile & traffic mapping, If you set your QoS profile to "Silver with 802.1p Tag of 3" & your wilreless clients' EF marked traffic (ie WMM_UP of 6) will translate into outer CAPWAP DSCP value of AF21 by AP. Same applicable to any video traffic from wireless clients (as it comes with WMM_UP of 4 or 5). But original packet's inner DSCP value remain as it is because of CAPWAP encapsulation from AP -> WLC. Due to this within wired network (at least from AP to WLC) you cannot differentiate Voice , Video packets as all having same DSCP value (AF21). Anyway in your case this won't matter as you do not do any prioratization of your traffic within your switch network.
Just for curiosity why do not you use qos on your switches ? is there any reason ? How do you prioratize your voice traffic over any other type of traffic in your network ?
I am running WLC 4402 with code 7.0.116. What is the software version you are running on your WLC ?
When it comes to software version 7.4 code, cisco introduced "Application Visibilty & Control" feature where you can classify traffic at the WLC as you normally do in wired switches. This will allow reclassify, markdown, drop traffic according to traffic categories.
HTH
Rasika

Upstream bandwidth QoS profile 5508 WLC

Hello,
Is it possible, through a QoS profile, to control how much bandwidth a user gets to use for upstream traffic? I can easily set limits for downstream traffic, via the per user bandwidth contracts, but it is not obvious to me on how to control upstream traffic.
Any and all info is appreciated!
Thanks

upstream traffic needs to be defined at L3, via your QoS settings. As you've said, the profile on the WLC is downstream only.
HTH,
Steve
Sent from Cisco Technical Support iPad App

Assigned a QoS profile based on client identity

A client can be assigned a QoS profile based on its identity, through AAA, but how?

You need a RADIUS server.
Make sure the AAA override is enabled on the WLAN then try to use the folloiwng RADIUS attribute on the RADIUS server:
RADIUS-Cisco Airespace -> Airespace-QOS-Level
return the value of the QOS level in this attribute to the usres based on their identity.
HTH
Amjad
p.s: never tried the above. so tell us if it worked correctly with you.
Rating useful replies is more useful than saying "Thank you"

Wireless QoS - CAPWAP getting tagged DSCP 26 while inner packet is DSCP 24.

Hello,
I'm facing an issue regarding QoS and wireless. I've attached a drawing of my set up as well.
My set up consists of a Cisco wireless 7925 phone, a 3702i access point, and a WISM2 controller (running newest 7.6 code).
My access point is connected to a 3750 switch, the switchport is in access mode, and is trusting the dscp values from the access point (mls qos trust dscp). QoS is also enabled on the switch (mls qos).
Please see my attached picture of a visual representation to what I'm going to describe.
In my particular scenario I'm looking at SKINNY traffic between the phone and the call manager. Per our Wired QoS design SKINNY traffic is tagged with DSCP 24 or CS3. Traffic from the call manager to the phone is being tagged correctly all the way through (from the wired segment, to the controller and from the controller to the access point) the inner packet and the CAPWAP header is tagged correctly with DSCP 24.
Return traffic from the phone to the call manager is a different story. The phone is clearly tagging the SKINNY traffic with DSCP 24 as well, this is evident by looking at the inner packet in captures. However, the CAPWAP header is being tagged DSCP 26 for some reason. Basically it looks like the access point is building the CAPWAP header with the value of 26 despite the fact that the original packet is marked 24.
I'd like to further understand why this is happening in only one direction (from AP to the controller) and if there is any way to change the behavior.
One thing I might have stumbled on is how the 802.11e values map to DSCP values. Looking at the binary representations of 24 and 26, they both end up mapping back to the 802.11e value 3. My current thinking is the access point just sees this 802.11e value #3 and then tags it to 26 automatically instead of 24. I'm not sure why the access point can't read the correct DSCP value of the inner packet (being tagged by the phone) and simply map that same value to the CAPWAP header.
Any help or further insight into this would be greatly appreciated.
Thanks!

Return traffic from the phone to the call manager is a different story. The phone is clearly tagging the SKINNY traffic with DSCP 24 as well, this is evident by looking at the inner packet in captures. However, the CAPWAP header is being tagged DSCP 26 for some reason. Basically it looks like the access point is building the CAPWAP header with the value of 26 despite the fact that the original packet is marked 24.
Note that when AP receives packet, it will only see the wireless header UP (user prioroity) value & not inner IP packet DSCP header. So all mapping of outer CAPWAP DSCP is based on UP value. Refer this table & UP3 will map to AF31 (DSCP value 26)
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/emob73dg/emob73/ch5_QoS.html#_Ref167257742
I'd like to further understand why this is happening in only one direction (from AP to the controller) and if there is any way to change the behavior.
When it comes from UCCM side, signaling traffic already marked with CS3. So when WLC map that to CAPWAP, it will simply use that IP packet DSCP value to derive the outer CAPWAP DSCP. So packet goes as CS3 in that direction.
If you want to change this behavior (client to AP-> WLC), you can apply a qos service policy to re-write DSCP26 to CS3 on your 3750 switch where AP connects.
http://mrncciew.com/2012/11/30/understanding-wireless-qos-part-2/
Refer this post from Jerome to see background of this AF31 or CS3 debate when classifying voice control traffic.
http://wirelessccie.blogspot.com.au/2011/02/wired-qos-for-voice-control-af31-dscp.html
HTH
Rasika
**** Pls rate all useful responses ****

Platinum QoS profile limits data traffic

Hello,
I have WLC which controls a WLAN that hosts data traffic and VoIP traffic.
I have enabled Platinum QoS profile and the throughput of the WLAN decreases to approximately 10 Mbps (With bronze QoS profile throughput was like 22~25 Mbps).
I would like to know how does the QoS profile limit the throughput of the WLAN? WLC gives a warning that data traffic will be affected but that doesn't tell much about the actual mechanism of traffic limiting.
I used iperf software sending UDP data @ 500 Mbps to measure the throughput.
BR
Olli Karhunen

I think this url might help
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/vowlan/41dg/vowlan_ch2.html

Disable Wireless in Profile manager

Is there a way to disable the wireless adaptor in Profile Manager?

Hi
That may be a way of doing it although I would have disabled wireless when setting up a deployable image.
What you could try is log into Profile Manager. Select a Device Group you've created and have populated with desired devices or computers. Or simply select an enrolled device/computer. Under the OSX Section select Custom Settings. Click Configure and click Add Item.
For the key, type in - DisableAirPort
For the type, select Boolean
For the Value, tick the box
Test with the client machine.
It's been a while since I did this and unfortunately I have no way of testing it at the moment so it might not work?
HTH?
Tony

How do you delete your verizon wireless community profile?

How do you delete a profile on this thing?

You can't; you can edit it, but you can't delete it.

Question about QoS in Wireless

Hi,
I've spent some time reading about QoS in Wireless but can't get my head around a few things. QoS is a confusing subject.
In the WLANs -> Edit WLAN you can set a QoS profile, from Bronze to Platinum, as shown in the picture.
1) Does this level tag ALL traffic on the WLAN to Platinum if the client does not tag the traffic itself to other values? In other words, is Platinum the default level?
2) I've read that this setting is the maximum level of QoS permitted on the WLAN, in that case I should set it to Platinum if I have VOIP traffic and regular DATA traffic on the same WLAN? For instance Lync/Skype?
3) How does this relate to AVC profiles? I've prioritized certain apps (lync gets DSCP 46) and down-prioritized others (youtube gets DSCP 10), will the values I've defined be tagged with Platinum since I set the WLAN QoS profile to Platinum? Or will they retain their original value as I defined in AVC Profiles.
4) Which clients are not WMM compatible? It seems almost all regular computers support WMM.
Can someone confirm the following QoS is true for the wired infrastructure: WLC ports are mls qos trust cos and AP ports are mls qos trust dscp. But what about trunks between switches and the uplink to your ISP? trust dscp?
Will be thankful if someone can shed some light on this.

1) Does this level tag ALL traffic on the WLAN to Platinum if the client does not tag the traffic itself to other values? In other words, is Platinum the default level?
NO
2) I've read that this setting is the maximum level of QoS permitted on the WLAN, in that case I should set it to Platinum if I have VOIP traffic and regular DATA traffic on the same WLAN? For instance Lync/Skype?
Yes, this is max level allowed. you should tag to platinum if you have VOIP clients. i dont think skype sends data with priority voice. not sure about lync.
3) How does this relate to AVC profiles? I've prioritized certain apps (lync gets DSCP 46) and down-prioritized others (youtube gets DSCP 10), will the values I've defined be tagged with Platinum since I set the WLAN QoS profile to Platinum? Or will they retain their original value as I defined in AVC Profiles.
wlan setting takes precedence over AVC if i recall correctly
4) Which clients are not WMM compatible? It seems almost all regular computers support WMM.
yes all modern clients are WMM compatible. you need WMM compatibility for 11n/ 11ac rates
Can someone confirm the following QoS is true for the wired infrastructure: WLC ports are mls qos trust cos and AP ports are mls qos trust dscp. But what about trunks between switches and the uplink to your ISP? trust dscp?
trunks are usually trust cos and access ports are usually trust dscp. you need to make sure end to end qos is configured properly.

Windows 8.1 Group Policy based Wireless Profiles do not appear to be working

I'm wondering if anyone else out there has run into the same issue as I am seeing. The environment is all Server 2012(not R2), with Windows 8.1 clients.
I configure a GPO that is linked to the entire domain/authenticated users and contains a Windows Vista and Later wireless network profile. Let's call it "GPO_Wireless. It is configured to automatically connect it to a specific SSID, the
encryption settings are unimportant, as I've tried numerous approaches. In our case, we're trying to do EAP-TLS with the NPS role. We have the CA rolled out, NPS has a proper cert, and the clients are auto-enrolling for both Computer and User certs.
This is all verified as working. We've also tried straight password authentication.
I refresh group policy on a Windows 8.1 client and see that Computer Policy "GPO_Wireless" is being applied to the client. I restart the computer, but it does not connect to the wireless network.
I run "netsh wlan show profiles" and under "Group Policy Profiles(read only)" it is blank.
I run gpresult /r /scope computer again, and it shows "GPO_Wireless" is being applied.
The last note is that Windows 7 clients can connect to the wireless just fine.

Hi，
For the client side, I would like to know if the windows 7 as you mentioned used the same Group Police like Windows 8.1.
Meanwhile, I suggest you try using script as a workaround.
Regards,
Kelvin hsu
TechNet Community Support

Order of profiles for netcfg-auto-wireless

Hi fellow Archers,
I'm running Arch Linux with netcfg 2.5.4 on my laptop, and have several wireless network profiles set up. Amongst other things, I have three profiles for my University WLAN. The reason for this is that the University offers three different wireless networks, one for Staff, one for Students and one unencrypted with a password-protected HTTP proxy. I have access to all three, but I want netcfg to attempt to connect to the networks in that order.
I have tried to name the profiles as such:
UniversityAStaff
UniversityBStudent
UniversityCOpen
But that doesn't seem to make any difference; it still connects to the Student network by default.
Is there any way of setting the priority of the wireless networks that netcfg-auto-wireless tries to connect to?
Jon

if you make your profiles like in /etc/network.d/examples/wireless-wpa-configsection you can put a priority falue in the wpa_supplicant section this should do the trick
edit because of typo
Last edited by parintachin (2010-03-08 14:48:44)

Qos - giving wired connections priority over wireless connections

I have a WRT54G with revised firmware. I have one wireless connection and one wired connection. I'd like to set it up so that the wired connection uses the majority of the bandwidth. This way the resource intensive programs I use for work (CAD, GIS, etc accessing files remotely) will be guaranteed to have available more bandwith than my daughter on her laptop using IM, web cam and WOW-type game play. I don't mind her using these programs, but I have to make my work a priority.
It seems that I can shape traffic if each were a WIRED connection and also that the single QoS option for wireless will enhance WiFi MultiMedia. How can I assign a preference to the WIRED connection and provide a smaller but usable portion of bandwith to the wireless connection?
Thanks in advance.

Thanks for the input, although I still am a bit lost. I apologize if my questions appear repetitive.
You wrote:
==========
Make the Upstream Bandwidth service "manual" with the Kbps speed you want to dedicate to that application........
==========
What do you mean by "dedicate to that application?" Do you mean the apps I am trying to give bandwidth priority too? If so, how much of the 512 kbs upstream bandwidth do I enter here? How does this affect the wireless connections?
You wrote:
==========
You can provide priority to Devcie with MAC address & also the Etherent Port on four ports with different priority .....
Use application name also .....
=============
Won't these only apply to the different ethernet ports and wired MAC addresses? I am trying to limit bandwith to the wireless side...
You wrote:
==========
Under Wireless QoS .... enable the service
==========
Won't this provide the wireless connection with more efficient throughput? How will this help me in limiting the bandwith allocated to the wireless connection?
Thanks for your reply.

QoS binding limited to IP address range and SSID on WLAN

Our VLAN id 2 is used only by a WLAN SSID
Defining a QoS profile as using VLAN id 2 did not work. No upper rate limitation worked
Only using the IP address range of the VLAN or the SSID appeared to work.
It does not appear consistent, when a VLAN id can be specified on a WLAN in the Wireless Basic Setting Table
It is also inconsistent, that the proper SSIDs are not listed in the drop down box on the
Add / Edit Profile Binding Configuration page. They only appear as AP-1, AP-2 etc.

Has this been fixed under firmware 1.0.4.17? I cannot get this work with any type of Traffic Selector (IP/MAC/VLAN/DSCP/SSID).
Any suggestions are greatly appreciated. Thanks!

Wireless QoS Profiles

Similar Messages

Maybe you are looking for