Cisco Cisco 5508 Wireless Controller 기술 참조
5
Application Visibility and Control Feature Deployment Guide rel 7.4-8.3
Loading AVC Protocol Pack–Phase 2
AVC and QoS Interaction on the WLAN
The AVC/NBAR2 engine on the controller interoperates with the QoS settings on the specific WLAN. The NBAR2
functionality is based on the DSCP setting. The following occurs to the packets in Upstream and Downstream directions
if AVC and QoS are configured on the same WLAN:
functionality is based on the DSCP setting. The following occurs to the packets in Upstream and Downstream directions
if AVC and QoS are configured on the same WLAN:
Upstream
1.
Packet comes with or without inner DSCP from wireless side (wireless client).
2.
AP will add DSCP in the CAPWAP header that is configured on WLAN (QoS based configuration).
3.
WLC will remove CAPWAP header.
4.
AVC module on the controller will overwrite the DSCP to the configured marked value in the AVC profile and send it
out.
out.
Downstream
1.
Packet comes from switch with or without inner DSCP wired side value.
2.
AVC module will overwrite the inner DSCP value.
3.
Controller will compare WLAN QoS configuration (as per 802.1p value that is actually 802.11e) with inner DSCP
value that NBAR had overwritten. WLC will choose the lesser value and put it into CAPWAP header for DSCP.
value that NBAR had overwritten. WLC will choose the lesser value and put it into CAPWAP header for DSCP.
4.
WLC will send out the packet to AP with QoS WLAN setting on the outer CAPWAP and AVC inner DSCP setting.
5.
AP strips the CAPWAP header and sends the packet on air with AVC DSCP setting; if AVC was not applied to an
application then that application will adopt the QoS setting of the WLAN.
application then that application will adopt the QoS setting of the WLAN.
AVC Operation with Anchor/Foreign Controller’s Setup
In the case of Anchor and Foreign controller’s configuration, the AVC has to be configured where the application control
essentially is required. In most cases in Anchor/Foreign setups the AVC should be enabled on the Anchor controller. AVC
profile enforcement will happen on the WLAN on the Anchor controller. If Anchor controller is release 7.4 or higher the
above mentioned setup will work.
essentially is required. In most cases in Anchor/Foreign setups the AVC should be enabled on the Anchor controller. AVC
profile enforcement will happen on the WLAN on the Anchor controller. If Anchor controller is release 7.4 or higher the
above mentioned setup will work.
Loading AVC Protocol Pack–Phase 2
Loading of Protocol Packs is supported only via the command line interface. The command to load a protocol pack is
shown in the example below:
shown in the example below:
(Cisco Controller) >transfer download datatype avc-protocol-pack
(Cisco Controller) >transfer download start
Mode.............................. FTP
Data Type......................... AVC Protocol Pack
FTP Server IP..................... A.B.C.D
FTP Server Port................... 21
FTP Path.......................... /
FTP Filename..................... pp-unified-wng-152-4.S-13-4.1.1.pack
FTP Username...................... cisco