campus qos design simplifiedd2zmdbbm9feqrf.cloudfront.net/2015/usa/pdf/brkcrs-2501.pdfscavenger...
TRANSCRIPT
Campus QoS Design—Simplified
Tim Szigeti
BRKCRS-2501
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Campus QoS Design Considerations
and Best Practices
What Do You Consider First?
BRKRST-2056: The QoS Paradigm Shift
http://tinyurl.com/ps8yzug
Start by Defining Your QoS StrategyArticulate Your Business Intent, Relevant Applications and End-to-End Strategy
BRKRST-2056: The QoS Paradigm Shift
The Case for Campus QoS
• The primary role of QoS in campus networks is to manage packet loss
• In campus networks, it takes only a few milliseconds of congestion to cause drops
• Rich media applications are extremely sensitive to packet drops
10
80
lin
es o
f H
orizo
nta
l R
eso
lution
1920 lines of Vertical Resolution (Widescreen Aspect Ratio is 16:9)
1080p60
1080 x 1920 lines =
2,073,600 pixels per frame
x 24 bits of color per pixel
x 60 frames per second
= 2,985,984,000 bps
or 3 Gbps Uncompressed!
Cisco (H264/H.265) codecs transmit 3-5 Mbps per 1080p60 video stream
which represents over 99.8% compression (~ 1000:1)
Packet loss is proportionally magnified by compression ratios
Users can notice a single packet lost in 10,000—
Making HD Video One Hundred Times More Sensitive to Packet Loss than VoIP!
Why Is Video So Sensitive to Packet Loss?
Audio
Samples
20 msec
Voice Packets
Bytes
200
600
1000
1400
Time
200
600
1000
1400
33 msec
Video Packets
Video
Frame
Video
Frame
Video
Frame
VoIP vs. HD Video—At the Packet Level
0
20
40
60
80
100
120
140
10
50
90
13
0
17
0
21
0
25
0
29
0
33
0
37
0
41
0
45
0
49
0
53
0
57
0
61
0
65
0
69
0
73
0
77
0
81
0
85
0
89
0
93
0
97
0
KB
yte
sP
er
ms Gbps Line Rate
Campus QoS Design ConsiderationsHow Long Can Queue-Buffers Accommodate Line-Rate Bursts?
GE Linecard Example
Total Per-Port Buffer: 5.4 MB
Total Per-Queue Buffer*: 1.35 MB
Gbps Line Rate: 1 Gbps = 125 MB/s
or 125 KB/ms
Total Per-Queue Buffering Capacity: 10.8 ms
*Assuming (4) equal-sized queues
ms
GE Linecard Example (WS-X6148)
Begin dropping at 11 ms
but overall utilization is only 1%!
1 second
KB
yte
sP
er
ms 10 Gbps Line Rate
Campus QoS Design ConsiderationsHow Long Can Queue-Buffers Accommodate Line-Rate Bursts?
10-GE Linecard Example
Total Per-Port Buffer: 90 MB
Total Per-Queue Buffer*: 11.25 MB
Gbps Line Rate: 10 Gbps = 1.25 GB/s
or 1250 KB/ms
Total Per-Queue Buffering Capacity: 9.0 ms
*Assuming (8) equal-sized queues
ms
0
200
400
600
800
1000
1200
1400
10
50
90
13
0
17
0
21
0
25
0
29
0
33
0
37
0
41
0
45
0
49
0
53
0
57
0
61
0
65
0
69
0
73
0
77
0
81
0
85
0
89
0
93
0
97
0
10 GE Linecard Example (WS-X6908)
1 second
Begin dropping at 9 ms
but overall utilization is only 1%!
Oversubscription in the Campus GE Link
10GE Link
40GE Link
Oversubscription in the Campus
x 11
GE Link
10GE Link
40GE Link
Oversubscription in the Campus GE Link
10GE Link
40GE Link
Oversubscription in the Campus GE Link
10GE Link
40GE Link
Know Your Tools
• Catalyst and Nexus switch hardware
• Software and Syntax
• Global Default QoS Settings
• Trust States and Conditional Trust
• Logical vs. Physical Interface QoS
• Ingress and Egress Queuing Models
Hardware VariesAmerican Version
2015 Cisco Live San Diego
Hardware VariesItalian Version
2015 Cisco Live Milan
Hardware VariesGerman Version
2016 Cisco Live Berlin
Hardware VariesCanadian Version
2015 Cisco Connect Toronto
Software and Syntax Variations• Catalyst 2960-X / 3560 / 3750 are the last platforms to use Multilayer Switch QoS (MLS QoS)
• QoS is disabled by default and must be globally enabled with mls qos command
• Once enabled, all ports are set to an untrusted port-state
• Catalyst 3650/3850 and 4500 use IOS Modular QoS Command Line Interface (MQC)
• QoS is enabled by default
• All ports are trusted at layer 2 and layer 3 by default
• Catalyst 6500/6800 use Cisco Common Classification Policy Language (C3PL) QoS
• QoS is enabled by default (Sup2T) – Disabled by default (Sup720)
• All ports are trusted at layer 2 and layer 3 by default
• C3PL presents queuing policies similar to MQC, but as a defined “type” of policy
• Nexus 7000/7700 use NX-OS QoS
• QoS is enabled by default
• All ports are trusted at layer 2 and layer 3 by default
• NX-OS presents queuing policies similar to MQC, but as a defined “type” and with default class-map names
Untrusted / User-Administered Devicesno mls qos trust
Trusted Centrally-Administered Devicesmls qos trust dscp
Centrally-Administered &
Conditionally-Trusted Devicesmls qos trust device
• cisco-phone
• cts
• ip-camera
• media-player
Trust Boundary
Trust Boundaries
Trust Boundary
Trust Boundary
The trust boundary is the edge where
• Layer 2 (CoS / UP) and/or
• Layer 3 (DSCP)
markings are accepted or rejected
Policy Enforcement Points (PEPs)
• The Policy Enforcement Point (PEP) is the edge where classification and marking policies are enforced
• The PEP may or may not be the same as the trust boundary
• Multiple PEPs may exist for different types of network devices
• e.g. switch PEP vs. router PEP
Trust Boundary
Router
PEP
Switch
PEP
Note: For the sake of simplification, in this deck PEP will refer to
classification and marking policy enforcement points (only)
and will not include other policy enforcement points (e.g. queuing).
Conditional TrustTrust Boundary, PEP and Mapping—Part 1
A Conditional Trust statement is deployed on all access edge switch ports
And a classification policy is applied to all access edge switch
class-map match-all VOICE
match access-group name VOICE
class-map match-all VIDEO
match access-group name VIDEO
class-map match-all BULK-DATA
match access-group name BULK-DATA
…
policy-map MARKING
class VOICE
set dscp ef
class VIDEO
set dscp af41
class BULK-DATA
set dscp af11
…
interface gig 1/1-48
trust device cisco-phone
service-policy input MARKING
PEPTrust Boundary
Conditional TrustTrust Boundary, PEP and Mapping—Part 2
If a Cisco IP Phone is detected
then the trust boundary extends to the IP Phone
The IP Phone sets CoS for Voice and Signaling
and resets all else to 0
The access switch maps CoS-to-DSCP
Note: the Policy Enforcement Point remains at the access switch
PEPTrust Boundary
* Non-Default Mapping
Access Switch
CoS-to-DSCP
Mapping Table
CoS 7 DSCP CS7 (56)
CoS 6 DSCP CS6 (48)
CoS 5 DSCP EF (46)*
CoS 4 DSCP CS4 (40)
CoS 3 DSCP CS3 (24)
CoS 2 DSCP CS2 (16)
CoS 1 DSCP CS1 (8)
CoS 0 DSCP DF (0)
IP Phone
CoS Mapping Table
CoS 6-7 CoS 0
Voice CoS 5
Signaling CoS 3
CoS 0-4 DSCP 0
Policy map is applied to the
physical switch port
VLAN 10 VLAN 20
Physical Ports
VLAN Interfaces
Policy map is applied to the
logical VLAN interface
Per-Port QoSPer-VLAN QoS
VLAN 10 VLAN 20
Physical Ports
VLAN Interfaces
Per-Port QoS vs. Per-VLAN QoS
interface gig 1/1-48
service-policy input MARKING
interface gig 1/1-48
mls qos vlan-based
interface Vlan 10
service-policy input MARKING
DVLAN 10
DVLAN policy map is applied
to the Data VLAN (only)
on a given trunked switch port
VVLAN 110
Trunked Physical Ports
VLAN Interfaces
VVLAN policy map is applied
to the Voice VLAN (only)
on a given trunked switch port
Campus QoS Design ConsiderationsPer-Port/Per-VLAN QoS
EtherChannel QoS
• EtherChannels are comprised of logical (Port-Channel) interfaces and physical (port-member) interfaces
• Ingress QoS policies are usually applied to the logical interfaces (but not always)
• Egress QoS policies (such as queuing) are always applied to the physical port-member interfaces
Platform QoS Policies Applied to the
(Logical) Port-Channel
Interface
QoS Policies Applied to the
(Physical) Port-Member
Interfaces
Catalyst 2960-X Ingress & Egress
Catalyst 3650/3850 Ingress Egress
Catalyst 4500 Ingress Egress
Catalyst 6500 Ingress Egress
Campus QoS Design Best Practices
• Always perform QoS in hardware rather than software when a choice exists
• Classify and mark applications as close to their sources as technically and administratively feasible
• Police unwanted traffic flows as close to their sources as possible
• Enable queuing policies at every node where the potential for congestion exists
Campus Ingress QoS Models
Trust DSCP
Trust Device / Conditional Trust
No Trust (Untrusted)
Ing
res
s Q
ue
uin
g P
olic
ies
(if
req
uir
ed
an
d s
up
po
rted
)
(Optional) Policing Policies
VoIP Policer (<128 kbps)
Signaling Policer (<32 kbps)
MM-Conf Policer (<5 Mbps)
Signaling Policer (<32 kbps)
Trans-Data Policer (<10 Mbps)
Bulk Data Policer (<10 Mbps)
Best Effort Policer (<10 Mbps)
Scavenger Policer (<10 Mbps)
Drop
Drop
Remark to CS1
Remark to CS1
Remark to CS1
Drop
Drop
Drop
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Marking Policies
VoIP Classifier
Signaling Classifier
Multimedia Conferencing Classifier
Signaling Classifier
Transactional Data Classifier
Bulk Data Classifier
Scavenger Classifier
Best Effort (Class-Default)
Mark EF
Mark CS3
Mark AF41
Mark CS3
Mark AF21
Mark AF11
Mark CS1
Mark DF
DVLAN
VVLAN
Trust CoS
1T
Catalyst Hardware Queuing1P3Q1T Example
1 Priority Queue
3 Non-Priority
Queues
1P3Q
Each queue has 1 Drop Threshold
(the tail of the queue)
Catalyst Hardware Queuing1P3Q1T Example
Interrupt
Scheduling
Resume
Scheduling
Weighted Tail Drop (WTD) Operation3T WTD Example
Red Minimum WTD Threshold 1:
Begin tail dropping red packets
Yellow Minimum WTD Threshold 2:
Begin tail dropping yellow packets
Tail of Queue is WTD Threshold 3
Front
of
Queue
Tail
of
Queue
Direction
of
Packet
Flow
Weighted Random Early Detect (WRED) Operation
AF13 Minimum WRED Threshold:
Begin randomly dropping AF13 Packets
AF12 Minimum WRED Threshold:
Begin randomly dropping AF12 Packets
AF11 Minimum WRED Threshold:
Begin randomly dropping AF11 Packets
Maximum WRED Thresholds for AF11, AF12 and AF13 are set to the tail of the queue in this example
Front
of
Queue
Tail
of
Queue
Direction
of
Packet
Flow
Campus Port QoS RolesUntrusted Endpoint Port QoS:
• Port Set to Untrusted State
(or Explicit Policy to Mark to DSCP 0)
• [Optional Ingress Marking and/or Policing]
• [Ingress and] Egress Queuing
Conditionally-Trusted Endpoint Port QoS
• Conditional-Trust with Trust-CoS or DSCP
• [Optional Ingress Marking and/or Policing]
• [Ingress and] Egress Queuing
Trusted Port QoS
• Trust DSCP
(Default on all non-MLS QoS platforms)
• [Ingress and] Egress Queuing
http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/qoscampusaag.pdf
Campus QoS Design—At-A-Glance
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960 QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Cisco Catalyst 2960-XQoS Design
Catalyst 2960-XQoS Roles in the Campus Access
No Trust +
Ingress Queuing +
Egress Queuing
Trust DSCP +
Ingress Queuing +
Egress Queuing
Conditional Trust +
Ingress Queuing +
Egress Queuing
Classification/Marking +
[Optional Policing] +
Ingress Queuing +
Egress Queuing
Distribution
Switches
C2960-X
Access
Switch
Catalyst 2960-X
1. Enable QoS
2. Configure Ingress QoS Model(s):
Trust Models
Conditional Trust Model
Service Policy Models
3. Configure Egress Queuing
QoS Design Steps
Note: Catalyst 2960-X is QoS compatible with the Catalyst 3560 & 3750, with the following exceptions:
• The Catalyst 3560 & 3750 support ingress queuing policies, but the 2960-X does not.
• Similarly, the Catalyst 3560 & 3750 support VLAN-based QoS policies, but the 2960-X does not.
Catalyst 2960-XEnabling QoS and Trust Models
mls qos trust dscp
Trust-DSCP Model Example:
mls qos trust device cisco-phone [or]
mls qos trust device cts [or]
mls qos trust device ip-camera [or]
mls qos trust device media-player
Conditional-Trust Model Example:
mls qos
Enabling QoS:Shaded commands are global
Highlighted commands are interface specificmls qos trust cos
Trust-CoS Model Example:mls qos map cos-dscp 0 8 16 24 32 46 48 56 Key commands/parameters in RED
Note: CoS 5 which is explicitly mapped to DSCP 46
Note: Only one type of device may be configured at a time
mls qos trust device cisco-phone
mls qos trust cos
Catalyst 2960-XConditional Trust Model Example
Conditional Trust Policy to a Cisco IP Phone:mls qos map cos-dscp 0 8 16 24 32 46 48 56
Note: All CoS-to-DSCP values are left at default
(DSCP = CoS * 8)
Except for CoS 5 which is explicitly mapped to DSCP 46
(Expedite Forwarding/EF, per RFC 3246 & 4594). CoS must be
matched as Cisco IP
Phones only remark
at Layer 2
policy-map MARKING-POLICY
class VOIP
set dscp ef
class MULTIMEDIA-CONFERENCING
set dscp af41
class SIGNALING
set dscp cs3
class TRANSACTIONAL-DATA
set dscp af21
class BULK-DATA
set dscp af11
class SCAVENGER
set dscp cs1
class class-default
set dscp default
Catalyst 2960-XMarking Policy Model Example
service-policy input MARKING-POLICY
class-map match-all VOIP
match access-group name VOIP
class-map match-all MULTIMEDIA-CONFERENCING
match access-group name MULTIMEDIA-CONFERENCING
class-map match-all SIGNALING
match access-group name SIGNALING
class-map match-all TRANSACTIONAL-DATA
match access-group name TRANSACTIONAL-DATA
class-map match-all BULK-DATA
match access-group name BULK-DATA
class-map match-all SCAVENGER
match access-group name SCAVENGER
mls qos map policed-dscp 0 10 18 to 8
[class-maps omitted for brevity]
policy-map MARKING&POLICING
class VVLAN-VOIP
set dscp ef
police 128k 8000 exceed-action drop
class VVLAN-SIGNALING
set dscp cs3
police 32k 8000 exceed-action drop
class MULTIMEDIA-CONFERENCING
set dscp af41
police 5m 8000 exceed-action drop
class SIGNALING
set dscp cs3
police 32k 8000 exceed-action drop
class TRANSACTIONAL-DATA
set dscp af21
police 10m 8000 exceed-action policed-dscp-transmit
…
Catalyst 2960-XMarking & Policing Policy Example
service-policy input MARKING&POLICING
[continued]
class BULK-DATA
set dscp af11
police 10m 8000 exceed-action policed-dscp-transmit
class SCAVENGER
set dscp cs1
police 10m 8000 exceed-action drop
class DEFAULT
set dscp default
police 10m 8000 exceed-action policed-dscp-transmit
Note: Remarking is performed by configuring a
policed-DSCP map with the global configuration
command mls qos map policed-dscp, which
specifies which DSCP values are subject to
remarking if out-of-profile and what value these
should be remarked as.
In this example exceeding:
• Best Effort (DSCP 0)
• Bulk (AF11 / DSCP 10)
• Transactional Data (AF21 / DSCP 18)
are remarked to Scavenger (CS1 / DSCP 8).
Catalyst 2960-X1P3Q3T Egress Queuing Model
Network Management
Signaling
Realtime Interactive
Transactional Data
Multimedia Conferencing
Bulk Data
AF2
CS3
CS4
AF4
CS2
AF1
Scavenger CS1
Best Effort DF
Multimedia Streaming AF3
Broadcast Video
VoIP
Application
CS5
EF
Internetwork Control CS6
DSCP
Network Control (CS7)
Q1
Priority Queue
Queue 4
(5%)
Queue 2
(30%)
Default Queue
Queue 3 (35%)
Q2T3
Q2T2
Q4T2
Q4T1
Q2T1
CS6
CS7
EF
CS4
CS3
CS2
DF
CS1
AF1
AF4
AF3
AF2
1P3Q3T
CS5
! This section configures egress buffers and thresholds
mls qos queue-set output 1 buffers 15 30 35 20
mls qos queue-set output 1 threshold 1 100 100 100 100
mls qos queue-set output 1 threshold 2 80 90 100 400
mls qos queue-set output 1 threshold 3 100 100 100 400
mls qos queue-set output 1 threshold 4 60 100 100 400
! This section configures egress CoS-to-Queue mappings
mls qos srr-queue output cos-map queue 1 threshold 3 4 5
mls qos srr-queue output cos-map queue 2 threshold 1 2
mls qos srr-queue output cos-map queue 2 threshold 2 3
mls qos srr-queue output cos-map queue 2 threshold 3 6 7
mls qos srr-queue output cos-map queue 3 threshold 3 0
mls qos srr-queue output cos-map queue 4 threshold 3 1
Catalyst 2960-X1P3Q3T Egress Queuing Model Config—Part 1 of 2
Note: The Catalyst 2960-X can also be configured to use an 8-queue model; however this model is NOT supported in a stack, nor is it supported if AutoQoS is enabled.
Allocates buffers to Q1, Q2, Q3 and Q4
(respectively)
Each queue has 4 thresholds:
• WTD Threshold 1
• WTD Threshold 2
• Reserved Threshold—buffers that may NOT
be shared with adjacent port-queues
• Maximum Threshold—maximum amount of
buffers may be borrowed from common buffer
pools (if available)
If the packet enters the switch on a port that is set
to trust cos then these CoS-to-Queue mappings
will be used to determine how the packet is
queued on egress
Catalyst 2960-X1P3Q3T Egress Queuing Model Config—Part 2 of 2
! This section configures egress DSCP-to-Queue mappings
mls qos srr-queue output dscp-map queue 1 threshold 3 32 40 46
mls qos srr-queue output dscp-map queue 2 threshold 1 16 18 20 22
mls qos srr-queue output dscp-map queue 2 threshold 1 26 28 30 34 36 38
mls qos srr-queue output dscp-map queue 2 threshold 2 24
mls qos srr-queue output dscp-map queue 2 threshold 3 48 56
mls qos srr-queue output dscp-map queue 3 threshold 3 0
mls qos srr-queue output dscp-map queue 4 threshold 1 8
mls qos srr-queue output dscp-map queue 4 threshold 2 10 12 14
! This section configures interface egress queuing parameters
queue-set 1
srr-queue bandwidth share 1 30 35 5
priority-queue out
If the packet enters the switch on a port
that is set to trust dscp then these
DSCP-to-Queue mappings will be used to
determine how the packet is queued on
egress
Enables the PQ Allocates bandwidth to each queue by means of a WRR weight.
Q1 weight is ignored, as it’s operating as a PQ
Platform QoS Policies Applied to the
(Logical) Port-Channel
Interface
QoS Policies Applied to the
(Physical) Port-Member
Interfaces
Catalyst 2960/3560/3750 Ingress & Egress
All QoS policies are configured on the physical port-member interfaces only
Catalyst 2960-XEtherChannel QoS Design
Catalyst 2960-X QoS Design At-A-Glance
AutoQoS SRND4 At-A-Glance
http://www.cisco.com/c/dam/en/us/td/docs/solutions/Enterprise/Video/autoqosmediacampus.pdf
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Cisco Catalyst 3650/3850 QoS Design
Catalyst 3650/3850QoS Roles in the Campus Access
No Trust +
Egress Queuing
Trust DSCP +
Egress Queuing
Conditional Trust +
Egress Queuing
Classification/Marking +
[Optional Policing] +
Egress Queuing
Distribution
Switches
C3650/3850
Access
Switch
Wireless Per-Port / Per-SSID / Per-Client Policies:
[Optional: Classification/ Marking]
[Optional: Policing]
2P2Q+AFD Egress Queuing
Catalyst 3650/3850
1. Configure Ingress QoS Model(s):
Trust DSCP Model*
Conditional Trust Models (wired ports only)
Service Policy Models (wired or wireless ports)
2. Configure Egress Queuing
Wired Queuing Models: 8Q3T or 1P7Q3T or 2P6Q3T
Wireless Queuing Model: 2P2Q+AFD
QoS Design Steps
*Note: Catalyst 3650/3850 IOS MQC trusts all wired ports by default
Prior to IOS XE 3.3, wireless ports were set to an untrusted state by default.
However, this default setting can be globally disabled with the following command:
no qos wireless-default-untrust
Beginning with IOS XE 3.3, wireless ports are also trusted by default
interface GigabitEthernet 1/0/1
trust device cisco-phone
service-policy input CISCO-IPPHONE
Catalyst 3650/3850Conditional Trust Models
class-map match-any VOICE
match cos 5
class-map match-any SIGNALING
match cos 3
policy-map CISCO-IPPHONE
class VOICE
set dscp ef
class SIGNALING
set dscp cs3
class class-default
set dscp default
interface GigabitEthernet 1/0/1
trust device cisco-phone [or]
trust device cts [or]
trust device ip-camera [or]
trust device media-player
Conditional-Trust Models:
Cisco IP Phone Conditional Trust ExampleConditional-Trust (Cisco IP Phone) Example:
Only match-any is supported
(i.e. match-all is not supported)
Only one type of device can be configured for
conditional trust on an interface at a given time
CoS must be
matched as Cisco
IP Phones only
remark at Layer 2
CoS must be
matched as Cisco
IP Phones only
remark at Layer 2
[class-maps omitted for brevity]
policy-map MARKING-POLICY
class VOIP
set dscp ef
class MULTIMEDIA-CONFERENCING
set dscp af41
class SIGNALING
set dscp cs3
class TRANSACTIONAL-DATA
set dscp af21
class BULK-DATA
set dscp af11
class SCAVENGER
set dscp cs1
class default
set dscp default
Catalyst 3650/3850Marking Policy Example
! This section attaches the service-policy
! to a wired interface(s)
interface range GigabitEthernet 1/0/1-48
service-policy input MARKING
! This section attaches the service-policy
! to a wireless interface(s) at the SSID level
wlan EMPLOYEE-WLAN
service-policy input MARKING
! This section attaches the service-policy
! to a wireless interface(s) at the client level
wlan EMPLOYEE-WLAN
service-policy client input MARKING
Inclusion of the client keyword applies
the service-policy at the client level
policy-map MARKING&POLICING
class VVLAN-VOIP
set dscp ef
police 128k
conform-action transmit
exceed-action drop
class VVLAN-SIGNALING
set dscp cs3
police 32k
conform-action transmit
exceed-action drop
class MULTIMEDIA-CONFERENCING
set dscp af41
police 5m
conform-action transmit
exceed-action drop
class SIGNALING
set dscp cs3
police 32k
conform-action transmit
exceed-action drop
…
Catalyst 3650/3850Marking & Policing Policy Example—Part 1 of 2
…[continued]
class TRANSACTIONAL-DATA
set dscp af21
police 10m
conform-action transmit
exceed-action TABLE-MAP
class BULK-DATA
set dscp af11
police 10m
conform-action transmit
exceed-action TABLE-MAP
class SCAVENGER
set dscp cs1
police 10m
conform-action transmit
exceed-action drop
class class-default
set dscp default
police 10m
conform-action transmit
exceed-action TABLE-MAP
table-map TABLE-MAP
map from 0 to 8
map from 10 to 8
map from 18 to 8
All markdown and/or
mapping operations
are configured
through table-maps
Policers can may be set to either remark or drop excess traffic
Policing to remark traffic
is done by referencing
the previously-configured
table-map
! This section attaches the service-policy to a wired interface(s)
interface range GigabitEthernet 1/0/1-48
service-policy input POLICING
! This section attaches the service-policy to a wireless interface(s) at the SSID level
! The policy will be applied to all clients belonging to the SSID at an aggregate level
wlan EMPLOYEE-WLAN
service-policy input POLICING
! This section attaches the service-policy to a wireless interface(s) at the client level
! The policy will be applied to individual clients at an aggregate level
wlan EMPLOYEE-WLAN
service-policy client input POLICING
Service policies applied to the
SSID level are actually
applied to the BSSID
(that is, per SSID/AP pair)
The inclusion of the client keyword
changes the application of the policer
from the SSID-aggregate level to the
client-aggregate level
Catalyst 3650/3850Marking & Policing Policy Example—Part 2 of 2
interface GigabitEthernet 1/0/1
service-policy input VLAN-POLICERS
Catalyst 3650/3850Per-Port/Per-VLAN Policy
class-map VVLAN
match vlan 110
class-map DVLAN
match vlan 10
policy-map VLAN-POLICERS
class VVLAN
police 192k
conform-action transmit exceed-action drop
class DVLAN
police 50m
conform-action transmit exceed-action drop
Individual (trunked) VLANs are
matched by the match vlan command
Individual (trunked) VLANs are
matched by the match vlan command
Policers are applied on a per-VLAN
basisPolicers are applied on a Per-VLAN basis
Per-VLAN policers are then applied on a Per-Port basis
Interrupt
Scheduling
Interrupt
Scheduling
Catalyst Hardware Queuing2P6Q3T Example
PQ1
PQ2
Catalyst 3650/38502P6Q3T with Weighted Tail Drop (WTD) Wired Port Egress Queuing Model
BWR =
Bandwidth
Remaining
WTD =
Weighted
Tail
Drop
PQ Level 2 (20%)
Network Management
Signaling
Realtime Interactive
Transactional Data
Multimedia Conferencing
Bulk Data
AF2
CS3
CS4
AF4
CS2
AF1
Scavenger CS1
Best Effort DF
Multimedia Streaming AF3
Broadcast Video
VoIP
Application
CS5
EF
Internetwork Control CS6
DSCP
Network Control (CS7)
2P6Q3T
PQ Level 1 (10%)EF
CS5
CS4
Q6
(BWR 10%)
CS7 & CS6
CS3 & CS2
Q5
(BWR 10% + WTD)
Q4
(BWR 10% + DSCP-Based WTD)
Q3
(BWR 10% + DSCP-Based WTD)
Q2
(BWR 5% + DSCP-Based WTD)
Q1 (BWR 25%)DF
AF1
CS1
AF2
AF3
AF4
class-map match-any VOICE-PQ1
match dscp ef
class-map match-any VIDEO-PQ2
match dscp cs4
match dscp cs5
class-map match-any CONTROL-MGMT-QUEUE
match dscp cs7 cs6 cs3 cs2
class-map match-any MULTIMEDIA-CONFERENCING-QUEUE
match dscp af41 af42 af43
class-map match-any MULTIMEDIA-STREAMING-QUEUE
match dscp af31 af32 af33
class-map match-any TRANSACTIONAL-DATA-QUEUE
match dscp af21 af22 af23
class-map match-any SCAVENGER-BULK-DATA-QUEUE
match dscp cs1 af11 af12 af13
Catalyst 3650/38502P6Q3T+WTD Wired Port Egress Queuing Config – Part 1of 2
Note: On platforms with shared buffer and TCAM architectures (2960/3560/3750/3650/3850/4500), show policy-map interface commands do not report per-port packets or byte-counters.
This is a limitation of shared hardware architectures.
policy-map 2P6Q3T
class VOICE-PQ1
priority level 1
police rate percent 10
class VIDEO-PQ2
priority level 2
police rate percent 20
class CONTROL-MGMT-QUEUE
bandwidth remaining percent 10
queue-buffers ratio 10
class MULTIMEDIA-CONFERENCING-QUEUE
bandwidth remaining percent 10
queue-buffers ratio 10
queue-limit dscp af43 percent 80
queue-limit dscp af42 percent 90
queue-limit dscp af41 percent 100
…
interface range GigabitEthernet 1/0/1-48
service-policy output 2P6Q3T
[continued]
class MULTIMEDIA-STREAMING-QUEUE
bandwidth remaining percent 10
queue-buffers ratio 10
queue-limit dscp af33 percent 80
queue-limit dscp af32 percent 90
queue-limit dscp af31 percent 100
class TRANSACTIONAL-DATA-QUEUE
bandwidth remaining percent 10
queue-buffers ratio 10
queue-limit dscp af23 percent 80
queue-limit dscp af22 percent 90
queue-limit dscp af21 percent 100
class SCAVENGER-BULK-DATA-QUEUE
bandwidth remaining percent 5
queue-buffers ratio 10
queue-limit dscp values af13 cs1 percent 80
queue-limit dscp values af12 percent 90
queue-limit dscp values af11 percent 100
class class-default
bandwidth remaining percent 25
queue-buffers ratio 25
Two-levels of priority
queuing are supported
Two-levels of priority
queuing are supported Allocates
buffers to
non-PQs
Tunes
WTD to
align to an
AF PHB
Tunes WTD
to align to an
AF PHB
Catalyst 3650/38502P6Q3T+WTD Wired Port Egress Queuing Config – Part 2 of 2
If a PQ is enabled then
non-PQs must use
bandwidth remaining
policy-map 50MBPS-SHAPER
class class-default
shape average 50000000
service-policy 2P6Q3T
Catalyst 3650/3850Hierarchical QoS Policies—Queuing within Shaped Rate Example
interface GigabitEthernet 1/0/1
service-policy output 50MBPS-SHAPER
Defines the sub-line rate (CIR)
Provides back-pressure to the system to
engage the (previously-defined) queuing
policy, so that packets are properly
prioritized within the sub-line rate
Only the Hierarchical Shaping policy is
attached to the interface(s)
Catalyst 3650/3850EtherChannel QoS Design
Platform QoS Policies Applied to the
(Logical) Port-Channel
Interface
QoS Policies Applied to the
(Physical) Port-Member
Interfaces
Catalyst 3850 Ingress Egress
• Ingress QoS policies are configured on the logical Port-Channel interface
Typically these are simply to enable DSCP trust
(which requires no explicit configuration)
• Egress QoS policies are configured on the physical port-member interfaces
Catalyst 3650/3850 QoS Design—At-A-Glance
http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/qoscampuscat3x50aag.html
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Cisco Catalyst 4500 QoS Design
Catalyst 4500QoS Roles in the Campus Distribution
Trust DSCP +
Egress Queuing
Core Switches
Access
Switches Catalyst 4500
Distribution
Switches
Catalyst 4500
1. Configure Ingress QoS Model(s):
DSCP-Trust Model*
Conditional Trust Model
Service Policy Models
2. Configure Egress Queuing
QoS Design Steps
*Note: Catalyst 4500 uses IOS MQC, which trusts by default;
therefore no explicit policy is required for DSCP trust
interface GigabitEthernet 3/1
qos trust device cisco-phone
service-policy input CISCO-IPPHONE
Catalyst 4500Conditional Trust Example
class-map match-all VOICE
match cos 5
class-map match-all SIGNALING
match cos 3
policy-map CISCO-IPPHONE
class VOICE
set dscp ef
class SIGNALING
set dscp cs3
class class-default
set dscp default
Catalyst 4500 supports both match-all (logical AND)
and match-any (logical OR) operators
Conditional trust command (trust device) must be
prefaced by qos on the Catalyst 4500
[class-maps omitted for brevity]
policy-map MARKING-POLICY
class VOIP
set dscp ef
class MULTIMEDIA-CONFERENCING
set dscp af41
class SIGNALING
set dscp cs3
class TRANSACTIONAL-DATA
set dscp af21
class BULK-DATA
set dscp af11
class SCAVENGER
set dscp cs1
class class-default
set dscp default
Catalyst 4500Marking Policy Example
interface GigabitEthernet 3/1
service-policy input MARKING-POLICY
policy-map MARKING&POLICING
class VOIP
police 128k bc 8000
conform-action set-dscp-transmit ef
exceed-action drop
class SIGNALING
police 32k bc 8000
conform-action set-dscp-transmit cs3
exceed-action drop
class MULTIMEDIA-CONFERENCING
police 5m bc 8000
conform-action set-dscp-transmit af41
exceed-action set-dscp-transmit af42
class TRANSACTIONAL-DATA
police 10m bc 8000
conform-action set-dscp-transmit af21
exceed-action set-dscp-transmit af22
Catalyst 4500Marking & Policing Policy Example
interface GigabitEthernet 3/1
service-policy input MARKING&POLICING
class BULK-DATA
police 10m bc 8000
conform-action set-dscp-transmit af11
exceed-action set-dscp-transmit af12
class SCAVENGER
police 10m bc 8000
conform-action set-dscp-transmit cs1
exceed-action drop
class class-default
police 10m bc 8000
conform-action set-dscp-transmit default
exceed-action set-dscp-transmit cs1
Marking/remarking is configured as part of the policing action
(i.e. no table-map or markdown-map is referenced)
interface range GigabitEthernet 2/1-48
qos trust device cisco-phone
vlan 10
service-policy input DVLAN-POLICERS
vlan 110
service-policy input VVLAN-POLICERS
Catalyst 4500Per-Port/Per-VLAN QoS Policy Example
Per-Port/Per-VLAN policies can be applied to
a specific VLAN on a trunked interface via an
interface-VLAN configuration mode
Per-Port/Per-VLAN policies can be applied to
a specific VLAN on a trunked interface
via an interface-VLAN configuration mode
Catalyst 45001P7Q1T+Dynamic Buffer Limiting (DBL) Egress Queuing Model
Network Management
Signaling
Realtime Interactive
Transactional Data
Multimedia Conferencing
Bulk Data
AF2
CS3
CS4
AF4
CS2
AF1
Scavenger CS1
Best Effort DF
Multimedia Streaming AF3
Broadcast Video
VoIP
Application
CS5
EF
Internetwork Control CS6
DSCP
Network Control (CS7)
1P7Q1T (+DBL)
PQ
EF
CS5
CS4
Q7
(BWR 10%)
CS7 & CS6
CS3 & CS2
Q6
(BWR 10%)
Q5
(BWR 10%)
Q4
(BWR 10%)
Q3
(BWR 4%)
Q2 (BWR 1%)
Q1 (25%)DF
AF1
CS1
AF2
AF3
AF4
BWR =
Bandwidth
Remaining
policy-map 1P7Q1T
class PRIORITY-QUEUE
priority
class CONTROL-MGMT-QUEUE
bandwidth remaining percent 10
class MULTIMEDIA-CONFERENCING-QUEUE
bandwidth remaining percent 10
class MULTIMEDIA-STREAMING-QUEUE
bandwidth remaining percent 10
class TRANSACTIONAL-DATA-QUEUE
bandwidth remaining percent 10
dbl
class BULK-DATA-QUEUE
bandwidth remaining percent 4
dbl
class SCAVENGER-QUEUE
bandwidth remaining percent 1
class class-default
bandwidth remaining percent 25
dbl
class-map match-all PRIORITY-QUEUE
match dscp cs4 cs5 ef
class-map match-all CONTROL-MGMT-QUEUE
match dscp cs7 cs6 cs3 cs2
class-map match-all MULTIMEDIA-CONFERENCING-QUEUE
match dscp af41 af42 af43
class-map match-all MULTIMEDIA-STREAMING-QUEUE
match dscp af31 af32 af33
class-map match-all TRANSACTIONAL-DATA-QUEUE
match dscp af21 af22 af23
class-map match-all BULK-DATA-QUEUE
match dscp af11 af12 af13
class-map match-all SCAVENGER-QUEUE
match dscp cs1
Catalyst 45001P7Q1T+DBL Egress Queuing Config
service-policy output 1P7Q1T
Enables the PQ
If PQ is enabled then
bandwidth remaining
must be used
DBL can be enabled on a per-class basis, but
should not be enabled on the PQ or Control
traffic queues.
Enabling DBL on UDP-based queues and/or
Scavenger queue is optional
DBL can be enabled on a per-class basis, but
should not be enabled on the PQ or Control
traffic queues.
Enabling DBL on UDP-based queues and/or
Scavenger queue is optional
DBL can be enabled on a per-class basis,
but should not be enabled on the PQ or Control traffic queues
Enabling DBL on UDP-based queues and/or Scavenger queue
is optional
Catalyst 4500EtherChannel QoS Design
Platform QoS Policies Applied to the
(Logical) Port-Channel
Interface
QoS Policies Applied to the
(Physical) Port-Member
Interfaces
Catalyst 4500 Ingress Egress
• Ingress QoS policies are configured on the logical Port-Channel interface
Typically these are simply to enable DSCP trust
(which requires no explicit configuration)
• Egress QoS policies are configured on the physical port-member interfaces
http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/qoscampuscat4500aag.html
Catalyst 4500 Campus QoS Design At-A-Glance
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Cisco Catalyst 6500 & 6800QoS Design
Cisco Catalyst 6500/6800QoS Roles in the Campus Core
Trust DSCP
+ Ingress Queuing
+ Egress Queuing
Catalyst 6500/6800
Core Switches
Cisco Catalyst 6500/6800QoS Design Steps
1. Configure Ingress Queuing
2. Configure Egress Queuing
Catalyst 6500 IOS C3PL trusts by default;
therefore no explicit policy is required for DSCP trust
BWR =
Bandwidth
Remaining
Network Management
Signaling
Realtime Interactive
Transactional Data
Multimedia Conferencing
Bulk Data
AF2
CS3
CS4
AF4
CS2
AF1
Scavenger CS1
Best Effort DF
Multimedia Streaming AF3
Broadcast Video
VoIP
Application-Class
CS5
EF
Internetwork Control CS6
DSCP
Network Control (CS7)
8Q4T/1P7Q4T
Realtime-Queue
(10% BW/Priority)
EF
CS5
CS4
Control Queue
(10% BW/BWR)
CS7 & CS6
CS3 & CS2
Multimedia-Conferencing Queue
(10% BW/BWR
+ DSCP-WRED)
Multimedia-Streaming Queue
(10% BW/BWR
+ DSCP-based WRED)
Transactional Data
(10% BW/BWR
+ DSCP-based WRED)
Bulk Data
(4% BW/BWR
+DSCP-based WRED)
Scavenger (1% BW/BWR)
Default Queue
(25% BW/BWR
+ WRED)
DF
AF1
CS1
AF2
AF3
AF4
Cisco Catalyst 6500/68008Q4T Ingress & 1P7Q4T Egress Queuing Models (6908-10GE)
Ingress and Egress queuing models varies by line card/module.
Refer to the 6500/6800 QoSConfiguration Guide to ensure that you use the proper queuing module for a given line card.
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-1SY/config_guide/sup2T/15_1_sy_swcg_2T/qos_policy_based_queueing.html
class-map type lan-queuing REALTIME-QUEUE
match dscp cs4 cs5 ef
class-map type lan-queuing CONTROL-QUEUE
match dscp cs2 cs3 cs6 cs7
class-map type lan-queuing MULTIMEDIA-CONFERENCING-QUEUE
match dscp af41 af42 af43
class-map type lan-queuing MULTIMEDIA-STREAMING-QUEUE
match dscp af31 af32 af33
class-map type lan-queuing TRANSACTIONAL-DATA-QUEUE
match dscp af21 af22 af23
class-map type lan-queuing BULK-DATA-QUEUE
match dscp af11 af12 af13
class-map type lan-queuing SCAVENGER-QUEUE
match dscp cs1
Cisco Catalyst 6500/6800Part 1 of 3—Common Ingress & Egress Queuing Class-Maps
Unless specified otherwise, the
default C3PL class-map and
policy-map type is qos
(classification, marking, policing)
Class-maps and policy-maps
used for ingress and/or egress
queuing policies must be explicitly
configured as type lan-queuing
Note: A C3PL interface may support up to 4 QoS policies:• service-policy type qos input
• service-policy type qos output
• service-policy type lan-queuing input
• service-policy type lan-queuing output
Cisco Catalyst 6500/6800Part 2 of 3—8Q4T Ingress Queuing Policy-Map
policy-map type lan-queuing INGRESS-8Q4T
class REALTIME-QUEUE
bandwidth percent 10
class CONTROL-QUEUE
bandwidth percent 10
class MULTIMEDIA-CONFERENCING-QUEUE
bandwidth percent 10
random-detect dscp-based
random-detect dscp af41 percent 80 100
random-detect dscp af42 percent 70 100
random-detect dscp af43 percent 60 100
class MULTIMEDIA-STREAMING-QUEUE
bandwidth percent 10
random-detect dscp-based
random-detect dscp af31 percent 80 100
random-detect dscp af32 percent 70 100
random-detect dscp af33 percent 60 100
[continued]
class TRANSACTIONAL-DATA-QUEUE
bandwidth percent 10
random-detect dscp-based
random-detect dscp af21 percent 80 100
random-detect dscp af22 percent 70 100
random-detect dscp af23 percent 60 100
class BULK-DATA-QUEUE
bandwidth percent 4
random-detect dscp-based
random-detect dscp af11 percent 80 100
random-detect dscp af12 percent 70 100
random-detect dscp af13 percent 60 100
class SCAVENGER-QUEUE
bandwidth percent 1
class class-default
random-detect dscp-based
random-detect dscp default percent 80 100
service-policy type lan-queuing input INGRESS-8Q4T
No PQ support on ingress
Bandwidth remaining is not required
(as no PQ is enabled)
Tunes WRED to better
align to the AF PHB
Policy-map must be defined as type lan-queuing
Cisco Catalyst 6500/6800Part 3 of 3—1P7Q4T Egress Queuing Policy-Map
policy-map type lan-queuing EGRESS-1P7Q4T
class REALTIME-QUEUE
priority
class CONTROL-QUEUE
bandwidth remaining percent 10
class MULTIMEDIA-CONFERENCING-QUEUE
bandwidth remaining percent 10
random-detect dscp-based
random-detect dscp af41 percent 80 100
random-detect dscp af42 percent 70 100
random-detect dscp af43 percent 60 100
class MULTIMEDIA-STREAMING-QUEUE
bandwidth remaining percent 10
random-detect dscp-based
random-detect dscp af31 percent 80 100
random-detect dscp af32 percent 70 100
random-detect dscp af33 percent 60 100
[continued]
class TRANSACTIONAL-DATA-QUEUE
bandwidth remaining percent 10
random-detect dscp-based
random-detect dscp af21 percent 80 100
random-detect dscp af22 percent 70 100
random-detect dscp af23 percent 60 100
class BULK-DATA-QUEUE
bandwidth remaining percent 4
random-detect dscp-based
random-detect dscp af11 percent 80 100
random-detect dscp af12 percent 70 100
random-detect dscp af13 percent 60 100
class SCAVENGER-QUEUE
bandwidth remaining percent 1
class class-default
random-detect dscp-based
random-detect dscp default percent 80 100
service-policy type lan-queuing output EGRESS-1P7Q4T
Policy-map must be defined as type lan-queuing
Enables egress PQ
bandwidth remaining is required
(as PQ is enabled)
Tunes WRED to better align
to the AF PHB
Cisco Catalyst 6500/6800
• Ingress QoS policies are configured on the logical Port-Channel interface
• No ingress policies typically needed for C6500/6800 EtherChannels
(as all ports trust DSCP & CoS by default)
• Egress QoS policies are configured on the physical port-member interfaces
EtherChannel QoS Design
Platform QoS Policies Applied to the
(Logical) Port-Channel
Interface
QoS Policies Applied to the
(Physical) Port-Member
Interfaces
Catalyst 6500/6800 Ingress Egress
http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/qoscampuscat6500sup2taag.html
Cisco Catalyst 6500 QoS Design At-A-Glance
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Cisco Nexus 7000/7700 QoS Design
Cisco Nexus 7000/7700QoS Roles in the Campus Core
Trust DSCP
+ Ingress Queuing
+ Egress Queuing
Cisco Nexus 7000/7700
Campus Core Switches
Cisco Nexus 7000/7700QoS Design Steps
1. Configure Ingress Queuing
2. Configure Egress Queuing
NX-OS trusts by default;
therefore no explicit policy is required for DSCP trust
8e-4q8q-in-q-default
Bandwidth 25%
Queue-Limit 30%
8e-4q8q-in-q4
Bandwidth 5%
Queue-Limit 30%
8e-4q8q-in-q3
Bandwidth 40%
Queue-Limit 30%
Cisco Nexus 7700 (F3)4Q1T Ingress Queuing (CoS-to-Queue) Model
8e-4q8q-in-q1
Bandwidth 30%
Queue-Limit 10 %
Network Management
Signaling
Realtime Interactive
Transactional Data
Multimedia Conferencing
Bulk Data
AF2
CS3
CS4
AF4
CS2
AF1
Scavenger CS1
Best Effort DF
Multimedia Streaming AF3
Broadcast Video
VoIP
Application
CS5
EF
Internetwork Control CS6
DSCP
Network Control (CS7)
4Q1T
CoS 5
CoS 7
CoS 6
CoS 2
CoS 4
CoS 1
DF
CoS 3
CoS 5
CoS 6
CoS
CoS 7
CoS 4
CoS 3
CoS 1
CoS 2
CoS 0
8e-4q8q-in-q-default
Bandwidth 25%
Queue-Limit 30%
8e-4q8q-in-q4
Bandwidth 5%
Queue-Limit 30%
8e-4q8q-in-q3
Bandwidth 40%
Queue-Limit 30%
8e-4q8q-in-q1
Bandwidth 30%
Queue-Limit 10%
Network Management
Signaling
Realtime Interactive
Transactional Data
Multimedia Conferencing
Bulk Data
AF2
CS3
CS4
AF4
CS2
AF1
Scavenger CS1
Best Effort DF
Multimedia Streaming AF3
Broadcast Video
VoIP
Application
CS5
EF
Internetwork Control CS6
DSCP
Network Control (CS7)
4Q1T
CS5
CS7
CS6
AF4
CS3
CS1
CS2
DF
CS4
EF
AF3
AF1
AF2
Cisco Nexus 7700 (F3)4Q1T Ingress Queuing (DSCP-to-Queue) Model
class-map type queuing match-any 8e-4q8q-in-q1
match cos 5
no match dscp 40-63
match dscp 32, 40, 46
class-map type queuing match-any 8e-4q8q-in-q3
match cos 2-4, 6-7
match dscp 16, 18, 20, 22
match dscp 24, 26, 28, 30
match dscp 34, 36, 38
match dscp 48, 56
class-map type queuing match-any 8e-4q8q-in-q4
match cos 1
match dscp 8, 10, 12, 14
class-map type queuing match-any 8e-4q8q-in-q-default
match cos 0
Cisco Nexus 7700 (F3)Part 1 of 2: 4Q1T-Ingress Queuing Class-Maps
Undesired default DSCP-to-Ingress Queue mappings
need to be explicitly removed
NX-OS has (non-configurable) system-defined names
for queuing class-maps
Similar to C3PL, NX-OS allows for multiple types of
QoS policies:
• type qos for classification, marking and policing
• type queuing for ingress and egress queuing
policy-map type queuing CAMPUS-F3-4Q1T-INGRESS
class type queuing 8e-4q8q-in-q1
bandwidth percent 30
queue-limit percent 10
class type queuing 8e-4q8q-in-q-default
bandwidth percent 25
queue-limit percent 30
class type queuing 8e-4q8q-in-q3
bandwidth percent 40
queue-limit percent 30
class type queuing 8e-4q8q-in-q4
bandwidth percent 5
queue-limit percent 30
interface Ethernet 1/1-24
service-policy type queuing input CAMPUS-F3-4Q1T-INGRESS
Cisco Nexus 7700 (F3)Part 2 of 2: 4Q1T-Ingress Queuing Policy-Map
Allocates buffers to queues
Used for Data Center Bridging
Exchange (DCBX) to advertise
QoS capabilities to any DCB-peers
Q2 is the Default Queue
8e-4q8q-out-q1
PQ-Shaped to 30%
8e-4q8q-out-q2
BWR 5%
8e-4q8q-out-q3
BWR 5%
8e-4q8q-out-q4
BWR 20%
8e-4q8q-out-q5
BWR 20%
8e-4q8q-out-q6
BWR 15%
8e-4q8q-out-q7
BWR 10%
8e-4q8q-out-q-default
BWR 25%
Cisco Nexus 7700 (F3)1P7Q1T Egress Queuing (CoS-to-Queue) Model
Network Management
Signaling
Realtime Interactive
Transactional Data
Multimedia Conferencing
Bulk Data
AF2
CS3
CS4
AF4
CS2
AF1
Scavenger CS1
Best Effort DF
Multimedia Streaming AF3
Broadcast Video
VoIP
Application
CS5
EF
Internetwork Control CS6
DSCP
Network Control (CS7)
1P7Q1T
CoS 2
CoS 4
CoS 1
DF
CoS 3
CoS 5
CoS 6
CoS
CoS 7CoS 5
CoS 7
CoS 6
CoS 4
CoS 3
CoS 1
CoS 2
CoS 0
class-map type queuing match-any 8e-4q8q-out-q1
match cos 5
class-map type queuing match-any 8e-4q8q-out-q2
match cos 7
class-map type queuing match-any 8e-4q8q-out-q3
match cos 6
class-map type queuing match-any 8e-4q8q-out-q4
match cos 4
class-map type queuing match-any 8e-4q8q-out-q5
match cos 3
class-map type queuing match-any 8e-4q8q-out-q6
match cos 2
class-map type queuing match-any 8e-4q8q-out-q7
match cos 1
Cisco Nexus 7700 (F3)Part 1 of 2: 1P7Q1T Egress Queuing Class-Maps
Note: These are the default CoS-to-Queue mappings.
As such, this step is optional
(unless current settings are non-default).
policy-map type queuing CAMPUS-F3-1P7Q1T-EGRESS
class type queuing 8e-4q8q-out-q1
priority level 1
shape average percent 30
class type queuing 8e-4q8q-out-q2
bandwidth remaining percent 5
class type queuing 8e-4q8q-out-q3
bandwidth remaining percent 5
class type queuing 8e-4q8q-out-q4
bandwidth remaining percent 20
class type queuing 8e-4q8q-out-q5
bandwidth remaining percent 20
class type queuing 8e-4q8q-out-q6
bandwidth remaining percent 15
class type queuing 8e-4q8q-out-q7
bandwidth remaining percent 10
class type queuing 8e-4q8q-out-q-default
bandwidth remaining percent 25
Cisco Nexus 7700 (F3)Part 2 of 2: 1P7Q1T Egress Queuing Policy-Map
interface Ethernet 1/1-24
service-policy type queuing output CAMPUS-F3-1P7Q1T-EGRESS
Note: Queue-Limits are not supported in egress direction
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Campus WLAN QoS Design Considerations
and Best Practices
The Case for Wireless QoS
• QoS is like a chain
• It’s only as strong as its weakest link
• the WLAN is one of the weakest links in enterprise QoS designs for three primary reasons:
1) Typical downshift in speed
2) Shift from full-duplex to half-duplex media
3) Shift from a dedicated media to a shared media
• WLAN QoS policies control both jitter and packet loss
Wireless QoS-Specific Limitations
• No priority servicing
• No bandwidth guarantees
• Non-deterministic media access
• Only 4 levels of service
LAN QoS WLAN QoS
WLAN QoS Improvements Quantified
Application Original Metric Improved Metric Percentage
Improvement
Voice 15 ms max jitter 5 ms max jitter 300%
3.92 MOS
(Cellular Quality)
4.2 MOS
(Toll Quality)
Video 9 fps 14 fps 55%
Visual MOS:
Good
Visual MOS:
Excellent
Transactional Data 14 ms latency 2 ms latency 700%
http://www.cisco.com/en/US/prod/collateral/wireless/cisco_avc_application_improvement.pdf
Know Your Tools
• IEEE 802.11e
• User Priorities (UP)
• Access Categories (AC)
• Arbitration Inter-frame Spacing (AIFS)
• Contention Windows (CW)
• Enhanced Distributed Coordination Function (EDCF)
• DSCP UP Mapping
• Trust Boundaries
• Policy-Enforcement Points
• Application Visibility and Control (AVC)
IEEE 802.11e User Priority (UP)
3 Bit Field allows for UP values 0-7
IEEE 802.11e UP Values and Access Categories
802.11e
UP Value
802.11e
Access Category
WMM
Designation
Cisco AireOS WLC
Designation
7 AC_VO Voice Platinum
6
5 AC_VI Video Gold
4
3 AC_BE Best Effort Silver
0
2 AC_BK Background Bronze
1
IEEE 802.11e Arbitration Inter-Frame Spacing (AIFS) and Contention Windows (CW)
Access
Category
AIFS
(Slot Times)
Voice 2
Video 2
Best Effort 3
Background 7
Access Category
CWmin
(Slot Times)
CWmax
(Slot Times)
Voice 3 7
Video 7 15
Best-Effort 15 1023
Background 15 1023
• due to the nature of wireless as a shared media, a Congestion Avoidance algorithm (CSMA/CA) must be utilized
• wireless senders have to wait a fixed amount of time (the AIFS)
• wireless senders also have to wait a random amount of time (the Contention Window)
• AIFS and Contention Window timers vary by Access Category
Upstream vs. Downstream QoS Mapping
CAPWAP Tunnels
WLC
AP
802.1p DSCP Payload1
4
AP
AP
802.1Q Trunk
CAPWAP Encapsulated Packet
DSCPDSCPPayload
2
DSCP DSCP Payload
CAPWAP Encapsulated Packet
Upstream
3
802.1Q Encapsulated PacketUP DSCP Payload
802.11e Encapsulated Packet
802.1pDSCPPayload
802.1Q Encapsulated Packet
UPDSCPPayload
802.11e Encapsulated Packet
1
24
3
Downstream
Default DSCP-to-UP Mapping Table
DSCP 802.11e UP WLC QoS Profile
56-63 7 Platinum
(Voice)48-55 6
40-47 5 Gold
(Video)32-39 4
24-31 3 Silver
(Best Effort)0-7 0
16-23 2 Bronze
(Background)8-15 1
46IETF PHB for VoIP: EF
Per RFC 4594 & 3246
Default IETF DSCP to IEEE 802.11e UP MappingSub-Optimal QoS Design Example
Transactional Data
Voice
4-Class Enterprise Model
Based on IETF 4594
Best Effort
Signaling
Voice
Access
Category
Four-Class Wireless Model
Based on IEEE 802.11e
Best Effort
Access
Category
Video
Access
Category
Background
Access
Category
UP 7
UP 5
UP 3
UP 2
UP 6
UP 4
UP 0
UP 1
AF2
EF
DSCP
DF
CS3
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Cisco IOS XE WLC AVC/QoS Design
Cisco IOS XE WLC
• IOS XE WLCs can be deployed in either a Centralized or a Converged Access Deployment Model
• In either model:
• Trust Boundary is at the AP
• PEP is at the AP
QoS Roles in the Wireless LAN Centralized Deployment Model
PEPTrust Boundary
Catalyst
3650/3850
Or 4500-Sup8
CAPWAP Tunnel
PEPTrust Boundary
CAPWAP Tunnel
CT5760 WLC
Converged Access Deployment Model
Cisco IOS XE WLC
1. Enable Application Visibility
a) Create a Flow Record
b) (Optional) Create a Flow Exporter
c) Create a Flow Monitor
d) Apply the Flow Monitor to the WLAN
2. Configure a AVC Policy
3. Configure a AFD Policy
4. (Optional) Configure Custom DSCPUP Table Maps
AVC/QoS Design Steps
Cisco IOS XE WLCEnabling Application Visibility
Step 1: Create a Flow Recordflow record AVC-FLOW-RECORD
description BASIC-AVC-FLOW-RECORD
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port
match flow direction
match application name
match wireless ssid
collect counter bytes long
collect counter packets long
collect wireless ap mac address
collect wireless client mac address
Step 2: (Optional) Create a Flow Exporterflow exporter AVC-FLOW-EXPORTER
destination 10.10.10.10
transport udp 2055
destination 10.20.20.20
transport udp 9991
Step 3: Create a Flow Monitorflow monitor AVC-FLOW-MONITOR
record AVC-FLOW-RECORD
exporter AVC-FLOW-EXPORTER
Step 4: Apply the Flow Monitor to the WLANwlan EMPLOYEE-WLAN
ip flow monitor AVC-FLOW-MONITOR input
ip flow monitor AVC-FLOW-MONITOR output
Note: Lancope collects
Netflow on port 2055
Note: Lancope collects
Netflow on port 2055
Cisco IOS XE WLCConfiguring AVC-Based QoS Policies
class-map match-any VOICE
match protocol cisco-phone
class-map match-any BROADCAST-VIDEO
match protocol cisco-ip-camera
class-map match-any REAL-TIME-INTERACTIVE
match protocol telepresence-media
class-map match-any CALL-SIGNALING
match protocol skinny
match protocol telepresence-control
class-map match-any TRANSACTIONAL-DATA
match protocol citrix
match protocol sap
class-map match-any BULK-DATA
match protocol attribute category email
match protocol attribute category file-sharing
match protocol attribute sub-category backup-systems
class-map match-any SCAVENGER
match protocol attribute category gaming
match protocol attribute application-group skype-group
policy-map AVC-MARKING
class VOICE
set dscp ef
class BROADCAST-VIDEO
set dscp cs5
class REAL-TIME-INTERACTIVE
set dscp cs4
class CALL-SIGNALING
set dscp cs3
class TRANSACTIONAL-DATA
set dscp af21
class BULK-DATA
set dscp af11
class SCAVENGER
set dscp cs1
class class-default
set dscp default
Note: Multiple application protocols can be
identified using attributes, including:
• category
• sub-category
• application-group
Note: Multiple application protocols can be
identified using attributes, including:
• category
• sub-category
• application-group
Note: Multiple application protocols can be
identified using attributes, including:
• category
• sub-category
• application-group
Multicast Queue
Video Queue
Strict
PriorityPolicer
Voice QueuePolicer
Weighted
SchedulingClient VQ SSID VQ Radio VQ
Data Queue
AFD BLOCK
Min or Max BW
Allocation
Default Shaper Radio Agg
Default Shaper
Policer
IOS XE Approximate Fair Drop (AFD)
Wireless Port Egress Queuing
IOS XE WLC AFD2P2Q+Approximate Fair Drop (AFD) Wireless Port Egress Queuing Model
2P2Q with AFD
Signaling
Transactional Data
Interactive Video
Voice
Application Classes
Scavenger
Best Effort
Bulk Data
Network Control
DSCP
Q2
Unicast-
Non-Realtime Queue
(63% BWR)
Q1
Priority Level 2
(Limited to 20% of BW)
Q0
Priority Level 1
(Limited to 10% of BW)
Q3
Multicast Non-Realtime Queue
(7% BWR)
EF
DF
CS1
AF2
AF1
AF4
CS3
CS6
CS3
AF2
AF4
EF
CS1
DF
AF1
CS6
IOS XE WLC AFD2P2Q+AFD Wireless Port Egress Queuing Configclass-map match-any REALTIME-1
match dscp ef
match dscp cs6
match dscp cs3
class-map match-any REALTIME-2
match dscp af41
match dscp af42
match dscp af43
policy-map port_child_policy
class non-client-nrt-class
bandwidth remaining ratio 7
class REALTIME-1
priority level 1
police rate percent 10 conform-action transmit exceed-action drop
class REALTIME-2
priority level 2
police rate percent 20 conform-action transmit exceed-action drop
class class-default
bandwidth remaining ratio 63
Note: This policy is applied automatically to all wireless ports.
Therefore, no explicit service-policy command is required
to attach the policy to a wireless interface(s).
System-defined (but configurable) queuing policy
System defined queue for multicast wireless traffic
Default unicast queue (non-priority queue)
Two-levels of priority queuing are supportedTwo-levels of priority queuing are supported
Cisco IOS XE WLCUnder-the-Hood DSCPUP Mapping
DSCP 802.11e UP WMM Access Category
48-63 7
Voice40-47 6
32-39 5
Video24-31 4
16-23 3
Best Effort0-7 0
8-15 2
Background- 1
IOS XE WLCDefault DSCP-to-UP Mapping Example
Transactional Data
Voice
4-Class Enterprise Model
Based on IETF 4594
Best Effort
Signaling
Voice
Access
Category
Four-Class Wireless Model
Based on IEEE 802.11e
Best Effort
Access
Category
Video
Access
Category
Background
Access
Category
UP 7
UP 5
UP 3
UP 2
UP 6
UP 4
UP 0
UP 1
AF2
EF
DSCP
DF
CS3
Cisco IOS XE WLCCustom DSCPUP Mapping Tables
Step 1: Configure (Downstream)
DSCP-to-UP Table Map
table-map DSCP-to-UP
map from 46 to 6
map from 24 to 4
map from 18 to 3
map from 0 to 1
default 1
Step 2: Configure (Upstream)
UP-to-DSCP Table Map
table-map UP-to-DSCP
map from 6 to 46
map from 4 to 24
map from 3 to 18
default 0
Step 3: Reference These Table-Maps Within Corresponding Policy-Maps
policy-map DSCP-TO-UP-POLICY
class class-default
set wlan user-priority dscp table DSCP-to-UP
policy-map UP-to-DSCP-POLICY
class class-default
set dscp wlan user-priority table DSCP-to-UP
Step 4: Apply the Policy-Maps to the WLANs and Specify Direction
wlan EMPLOYEE-WLAN
service-policy input UP-to-DSCP-POLICY
service-policy output DSCP-TO-UP-POLICY
IOS XE WLCCustomized DSCP-to-UP Mapping Example
Transactional Data
Voice
4-Class Enterprise Model
Based on IETF 4594
Best Effort
Signaling
Voice
Access
Category
Four-Class Wireless Model
Based on IEEE 802.11e
Best Effort
Access
Category
Video
Access
Category
Background
Access
Category
UP 7
UP 5
UP 3
UP 2
UP 6
UP 4
UP 0
UP 1
AF2
EF
DSCP
DF
CS3
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco IOS XE WLC AVC/QoS Design
• Cisco AireOS WLC AVC/QoS Design
• Summary and References
Agenda
Cisco AireOS WLC AVC/QoS Design
Cisco AireOS WLC
• AireOS WLCs are deployed in a Centralized Deployment Model, where:
• Trust Boundary is at the WLC
• PEP is at the WLC
QoS Roles in the Wireless LAN
Centralized Deployment Model
PEPTrust Boundary
CAPWAP Tunnel
AireOS WLC
Cisco AireOS WLC
1. Select and Tune the WLAN QoS Profile
2. Configure an AVC Profile
3. Apply the QoS and AVC Profile to the WLAN and Enable Application Visibility
QoS Design Steps
AireOS WLC
• QoS Profiles are applied to both upstream & downstream flows on egress
• The WLAN QoS Profile defines:
WLAN Maximum Priority
• It recommended to set the Maximum Priority to voice on multiservice WLANs
Unicast and Multicast Default Priority
• Typically these values are recommended to be set to best effort
• QoS Profiles override/control AVC Profiles
Tuning QoS Profiles
AireOS WLC
• AVC Profiles are applied to both upstream and downstream flows on WLC ingress
• an AVC Profile can contain a maximum of 32 application rules
• AVC profiles can be overridden by QoS Profiles
• So be sure to align these!
Creating AVC Profiles
AireOS WLC
• Select the desired QoS and AVC Profiles to apply to the WLAN
• Check the box to enable Application Visibility
Attaching QoS and AVC Profiles and Enabling AVC
Application Class DSCP/PHB 802.11e UP WLC QoS Profile
Internetwork Control 48 / CS6 7 Platinum
(Voice)Voice 46 / EF 6
Multimedia Conferencing 34 / AF41 5 Gold
(Video)Multimedia Streaming 26 / AF31 4
Transactional Data 18 / AF21 3 Silver
(Best Effort)Best Effort 0 / DF 0
Bulk Data 10 / AF11 2 Bronze
(Background)
Cisco AireOS WLCQoS Translation Table
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/configuration-guide/b_cg81/b_cg81_chapter_01010111.html
Cisco AireOS WLCDefault DSCP-to-UP Mapping Example
Transactional Data
Voice
4-Class Enterprise Model
Based on IETF 4594
Best Effort
Signaling
AF2
EF
DSCP
DF
CS3
Voice
Access
Category
Four-Class Wireless Model
Based on IEEE 802.11e
Best Effort
Access
Category
Video
Access
Category
Background
Access
Category
UP 7
UP 5
UP 3
UP 2
UP 6
UP 4
UP 0
UP 1
Cisco AireOS WLCCustomized DSCP-to-UP Mapping Example (Pending AireOS 8.1MR)
Transactional Data
Voice
4-Class Enterprise Model
Based on IETF 4594
Best Effort
Signaling
Voice
Access
Category
Four-Class Wireless Model
Based on IEEE 802.11e
Best Effort
Access
Category
Video
Access
Category
Background
Access
Category
UP 7
UP 5
UP 3
UP 2
UP 6
UP 4
UP 0
UP 1
AF2
EF
DSCP
DF
CS3
Cisco AireOS WLC
• Customizable DSCPUP Mappings will modify QoS Roles:
• Trust Boundary will move to the AP
• PEP will remain at the WLC
QoS Roles in the Wireless LAN (Pending AireOS 8.1MR)
Centralized Deployment Model
PEPTrust Boundary
CAPWAP Tunnel
AireOS WLC
• Campus QoS Design Considerations and Best Practices
• Cisco Catalyst 2960-X QoS Design
• Cisco Catalyst 3650/3850 QoS Design
• Cisco Catalyst 4500 QoS Design
• Cisco Catalyst 6500/6800 QoS Design
• Cisco Nexus 7000/7700 QoS Design
• Campus WLAN QoS Design Considerations and Best Practices
• Cisco AireOS WLC AVC/QoS Design
• Cisco IOS XE WLC AVC/QoS Design
• Summary and References
Agenda
Looking Forward
EasyQoS App
IWAN App
EasyQoS App
APIC-EM QoS AppsIWAN and EasyQoS
Wireless AP
Trust Boundary
PEP
4Q (WMM)
Catalyst 3650
Trust Boundary
PEP
2P6Q3T
Catalyst 4500
1P7Q1T
Catalyst 6500
1P3Q4T
1P7Q4T
2P6Q4T
…
Nexus 7700
F3: 1P7Q1T
WLC
PEP
ASR/ISRs
MQC
Catalyst 2960-X
Trust Boundary
PEP
1P3Q3T
Wireless AP
Trust Boundary
PEP
4Q (WMM)
EM
• QoS design best practices will be used to generate
platform-specific configurations
• QoS features will be selectively enabled if they
directly contribute to expressing the strategic policy on
a given platform
Summary & References
Key Takeaways
• Start by defining your QoS Strategy
• Campus QoS is needed primarily to control packet drops
• WLAN QoS is needed to control both jitter and packet drops
• Know your QoS toolset, as this varies platform-to-platform
• Cisco provides many At-A-Glance guides to get you up and running quickly
• Cisco also provides Cisco Validated Design guides for more detail
Campus QoS Design 4.0—In-Depth
• Enterprise Quality of Service Design 4.0 http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSIntro_40.html
• Campus QoS Design 4.0 http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSCampus_40.html
• WLAN QoS Design (BYOD CVD) http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Borderless_Networks/Unified_Access/BYOD_Design_Guide/BYOD_AVC.html
Comprehensive Design Chapters
Recommended Reading
• Release Date: Jan 2014
• Comprehensive QoS design guidance for PINs and platforms:
• Campus Catalyst 3750/4500/6500
• WLAN WLC 5508 / Catalyst 3850 NGWC
• Data Center Nexus 1000V/2000/5500/7000
• WAN & Branch Cisco ASR 1000 / ISR G2
• MPLS VPN Cisco ASR 9000 / CRS-3
• IPSec VPNs Cisco ISR G2
• ISBN: 1-58714-369-0
Ken Briley
http://www.ciscopress.com/store/end-to-end-qos-network-design-quality-of-service-for-9781587143694
Participate in the “My Favorite Speaker” Contest
• Promote your favorite speaker through Twitter and you could win $200 of Cisco Press products (@CiscoPress)
• Send a tweet and include
• Your favorite speaker’s Twitter handle @tim_szigeti
• Two hashtags: #CLUS #MyFavoriteSpeaker
• You can submit an entry for more than one of your “favorite” speakers
• Don’t forget to follow @CiscoLive and @CiscoPress
• View the official rules at http://bit.ly/CLUSwin
Promote Your Favorite Speaker and You Could Be a Winner
Complete Your Online Session Evaluation
Don’t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive.com/Online
• Give us your feedback to be entered into a Daily Survey Drawing. A daily winner will receive a $750 Amazon gift card.
• Complete your session surveys though the Cisco Live mobile app or your computer on Cisco Live Connect.
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Table Topics
• Meet the Engineer 1:1 meetings
• Related sessions
Thank you