WIFITECHBLOG

It has been difficult for me to locate good QoS references in the past...  So at some point, I put together the following cheat sheet which will hopefully help others as well.  It's based on my interpretation of the current Cisco best practices, and since I do not work directly for Cisco - it's a bit of conjecture on my part.  Still, it seems to line up well and has not yet steered me wrong.

So, without further ado:

Cisco AVVID 802.1p UP-Based Traffic Type	Cisco AVVID IP DSCP	Cisco AVVID 802.1p UP	IEEE 802.11e UP (WMM AC)	Notes
Network Control	-	7	-	Reserved for network control only
Inter-Network Control	54	6	7 (AC_VO)	CAPWAP control WLC: Platinum QoS profile
Voice	46 (EF)	5	6 (AC_VO)	WLC: Platinum QoS profile
Video	32 (CS4)	4	5 (AC_VI)	WLC: Gold QoS profile
Voice Control	24 (CS3)	3	4 (AC_VI)	WLC: Gold QoS profile
Best Effort	0 (BE)	0	3 (AC_BE)	WLC: Silver QoS profile
			0 (AC_BE)
Background (Cisco AVVID Gold Background)	16 (CS2)	2	2 (AC_BK)	WLC: Bronze QoS profile
Background (Cisco AVVID Silver Background)	8 (CS1)	1	1 (AC_BK)	WLC: Bronze QoS profile

Should I use GUI, CLI, or both?!

While preparing for the Autonomous AP portion of the CCIE Wireless lab I have come across a puzzling problem - what interface to use to configure the APs!

It's not a simple question, in my mind.  I've always been a command-line guy, as I find it much quicker.  However, in preparing for a test of this nature it becomes obvious that CLI also gives you more to remember...  And while I'm used to configuring wireless bridges using CLI, almost all of the APs I configure these days use GUI (CAPWAP through WLCs).  The GUI is different enough on an autonomous AP that I get a bit lost; for them I have generally stuck to the CLI as much as possible and just referenced the GUI when I get stuck.

I am going to focus on CLI, but ensure that I am comfortable using GUI as well.  If nothing else, it is easier to study CLI on my bus trips to/from work ;)