I think that 2a requirement: give a priority for voice traffic in upstream direction on the FastEthernet interface is not necessary, because the designers of the AP assumed that we have a 100 Mbit/sec full-duplex Ethernet link between the AP and the switch, so there is no queue to handle -> so FIFO is good.
Then I think that the web administration interface of the Cisco 1121G access point is misleading, because why to set policies for the FastEthernet outgoing traffic. OK you can set filters, but to set policies, which aim is to apply Class ofe services (putting in different queues)
So to define filters and apply class of services at the fast ethernet interface outgoing direction doesn't serve nothing, in my opinion.
Now my problem is that after defining a new VLAN, and after assigning it to an SSID, I generated traffic from a wireless client connecting to this interface, I sniffed with Ethereal the upstream traffic on the FastEthernet interface. And I expected that there I will see 802.1q VLAN tags in the Ethernet frames. But there are no 802.1q tags. I become more and more unconvinced with this product.
The QoS implementation for wireless LANs differs from QoS implementations on other Cisco devices. With QoS enabled, access points perform the following:
•They do not classify packets; they prioritize packets based on DSCP value, client type (such as a wireless phone), or the priority value in the 802.1q or 802.1p tag.
•They do not construct internal DSCP values; they only support mapping by assigning IP DSCP, Precedence, or Protocol values to Layer 2 COS values.
•They carry out EDCF like queuing on the radio egress port only.
•They do only FIFO queueing on the Ethernet egress port.
•They support only 802.1Q/P tagged packets. Access points do not support ISL.
•They support only MQC policy-map set cos action.
•They prioritize the traffic from voice clients (such as Symbol phones) over traffic from other clients when the QoS Element for Wireless Phones feature is enabled.
•They support Spectralink phones using the class-map IP protocol clause with the protocol value set to 119.
Especially they do not construct ToS/DSCP. What you can do is to set the 802.1Q CoS Bits based on an already existing DSCP setting. So in short: ToS marking is not supported, CoS marking is supported based on existing DSCP.
QoS on WLAN APs is limited compared to a router or switch. But it is still better than not to have any capabilities at all.
Now I would like to concentrate on your statement, that
"CoS marking is supported based on existibg DSCP".
As I understand, this statement has the importance of transferring priority information on the wireless link, because 802.11 frames don't support 802.1Q tags.
I think that CoS marking based on DHCP values has importance only in uplink direction. Is this correct?
During the transmission of traffic in uplink direction, the client application or client network driver or anything writes the DSCP values in the IP header. The AP writes the priority information in the 802.1Q VLAN tag based on the DSCP value and some assignment rules.
The univoque assignment of SSID and VLAN is also an important requirement for this.
If this is correct, then I would like to ask some practical informations: where to set this?
Because in the Services->QoS menu, I can create only policies on:
if a packet matches some requirements based on DSCP, IP Precedence, client type, some filters,
or if it is in a given VLAN (default policy)
(and DSCP, IP Precedence, 802.1Q CoS bits were not already set)
apply Best Effort, Background, Spare, Video, Voice, etc class of Service.
But I don't see from this if it will mark the 802.1Q CoS bits with that priority.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...