ONT10第五章无线QOSS06L01.pptVIP

Implement Wireless Scalability Implementing WLAN QoS WLAN and LAN Wireless LAN (WLAN) as an extension to wired LAN The Need for QoS Wireless QoS extension to 802.11 to provide more consistent and quality RF transmission for: Voice Video WLAN QoS Queuing Overview WLAN QoS RF Backoff Timing Lightweight Access Point—Split MAC Architecture QoS WLAN Deployment Issues Wireless RF is a Layer 2 technology and therefore based on 802.11e or WMM, versus Layer 3 DSCP. Layer 2 marking will be lost in end-to-end transient, losing QoS information. Access points connect to switches as access ports versus trunks and lack 802.1p trunk tagging. The goal is to utilize the Layer 3 DSCP information to preserve end-to-end QoS in the absence of Layer 2 QoS information. QoS Description WLAN data is tunneled between the access point and WLAN controller via LWAPP. QoS settings of the encapsulated data packet are mapped to the Layer 2 (802.1p) and Layer 3 (IP DSCP) fields of the outer tunnel packet. QoS Implementation Overview QoS Implementation—Ethernet to Controller Feature: QoS Packet-Marking Translations From Access Point to Wireless Client From Client to Access Point Traffic from Access Point to Controller The access point will not send tagged packets on a nontrunk port destined for the controller; therefore, the access point will not copy the 802.11e client incoming priority value to the 802.1p (outer) destined for the switch. From Controller to Ethernet Switch QoS Implementation 802.1p or DSCP-tagged packets received from LAN: Tag is propagated to LWAPP frame. WLAN ID-configured QoS takes priority for assigned access category; if tag is lower than configured QoS, access point will queue packet at lower access category. AAA override can be applied to Cisco IBNS WLAN clients. Untagged packets received from LAN: WLAN ID-configured QoS will be applied for access category. AAA override can be applied to Cisco IBNS WLAN clients. QoS Implementation (Cont.) 802.11e QoS packets received from