code : stm#550 samsung electronics co., ltd. officeserv 7400 qos configuration distribution...
TRANSCRIPT
Code : STM#550Code : STM#550
Samsung Electronics Co., Ltd.
OfficeServ 7400 QoS Configuration OfficeServ 7400 QoS Configuration
Distribution
EnglishED01
© Samsung Electronics Co., Ltd. 2
ObjectivesObjectives
After successful completion of the course the trainees should be able to execute the following activities.
© Samsung Electronics Co., Ltd. 3
ContentsContents
GeneralGeneral
GWIM QoSGWIM QoS
GSIM QoSGSIM QoS
© Samsung Electronics Co., Ltd. 4
GeneralGeneral
© Samsung Electronics Co., Ltd. 5
L3/L2 QoS FunctionsL3/L2 QoS Functions
GWIMHTBQ
SPQ
GSIM L2 and L3 Integrated QoS Support.
Classification, DSCP Marking, Policing, Buffer Management (WRED-like)
IEEE 82.1p marking, CoS Mapping
Scheduling
GLIMPCoS Mapping, Scheduling
© Samsung Electronics Co., Ltd. 6
VoIP QoSVoIP QoS
Auto-QoS supported by the DSMI (Data Server Module Interface) module.
GWIMAuto-configuration of NAPT for MCP and MGIs.
Auto – Firewall and auto-QoS support under development.
GSIM Auto-QoS supported.
auto-configuration of classification for VoIP trafficsauto-configuration of DSCP Marking for VoIP traffics.auto-configuration of IEEE 82.1p marking, CoS Mapping for VoIP traffics.
GLIMPCurrently auto-QoS not supported.
© Samsung Electronics Co., Ltd. 7
Auto QoS for VoIPAuto QoS for VoIP
INTERNEINTERNETT
INTERNEINTERNETT
Auto- QoSAuto-Firewall
Auto- NAPT ServiceDSMI
© Samsung Electronics Co., Ltd. 8
GWIM QoSGWIM QoS
© Samsung Electronics Co., Ltd. 9
QoS Function OverviewQoS Function Overview
SPQ (Strict Priority Queuing)Highest class served first. Only if the waiting list in the highest class is empty, other classes can be served.
HTBQ (Hierarchical Token Bucket Queuing) Supports the classification/shaping/queuing functions
Less complexity than CBQ.
guarantee of configured bandwidth(Rate) and the on-demand distribution of excess bandwidth(BW Sharing)
© Samsung Electronics Co., Ltd. 10
QoS Internal (I)QoS Internal (I)
Linux kernel TCprovides various Queuing Disciplines(Qdisc)
SPQ, HTBQ, CBQ,…
Root Qdisc is attached to device(interface). Arbitrary class tree can be created and attached to the Root Qdisc. Recursively, leaf classes can own another Qdisc as its own queuing policy.
If Packet is to transmit through one interface, it is classified as one of leaf classes according to configured filter rules and put into Qdisc attached to the leaf class. Iteratively, the packet is classified …
Queueing Discipline
Filter
Filter
Filter
Class
Class
Queueing Discipline
Queueing Discipline
© Samsung Electronics Co., Ltd. 11
QoS Internal (II)QoS Internal (II)
HTBQ (Hierarchical Token Bucket Queuing)
3 types of class : root, inner, leafOnly leaf classes actually shape
packets; packets are only delayed in these leaf classes. The inner classes (all the way up to the root class) exist to define how borrowing/lending occurs.
2 token buckets per class : 1 for AR (Assured Rate), 1 for CR (Ceil Rate)
rate limiting (shaping) in only leaf classes.
BW borrowing up to CR from parent class by borrowing tokens (parent’s tokens).
If excess BW of the parent class is not available, the parent class attempt to borrow BW from parent of it. This can continue to reach Root class.
excess BW of inner class is distributed in the proportion of Quantum of demanding classes with highest priority.
Quantum = Rate / R2Q ; calculated automatically
© Samsung Electronics Co., Ltd. 12
QoS Internal (III)QoS Internal (III)
SPQ (Strict Priority Queuing)PRIO qdisc used
doesn’t actually shape, only subdivides traffic based on how filters are configured.
3 types of class : high, middle, low => bands
priomap without tc filters, decide how to enqueue traffic according to TC_PRIO priority. GWIM supports only TC filters, so just ignore.
By default, each class contains pure FIFO qdisc. However, it can be replaced with any qdisc.
GWIM does not support this feature.
© Samsung Electronics Co., Ltd. 13
Sample ScenarioSample Scenario
ScenarioEth0 used as WAN interfaceQoS support is needed for VoIP traffic transmitted via eth0.Total throughput 200Mbps = 25Mbyte/sVoIP (class VOIP)
RTP, RTCP – G.729 call with voice payload size of 20 bytes (20 ms)– (14 bytes of Ethernet header + 40 bytes of IP(20)/UDP(8)/RTP(12) headers +
20 bytes voice payload + 4 bytes of Ethernet CRC)* 8 bits per byte * 50 pps = 31.2 Kbps
– 31.2 * 256 (Assuming number of simultaneous calls)– AR = 8000 kbps (1000kbyte/s), CR = 2Mbyte/s, Priority = 1 (highest)
Signal– SIP, H.323, SPNet(Samsung Proprietary Networking) – Assuming 160 kbps = 20 KB/s (AR), CR = 40kbyte/s, Priority = 1 (highest)
AR = 8 Mbps (1Mbyte/s), CR = 3Mbyte/sData Traffic (class Data)
AR = Total throuput – VoIP Traffic = 24 Mbyte/s, CR = 25Mbyte/sTCP (class data_tcp)
– AR = 10Mbyte/s, CR = 25Mbyte/s , prio = 2Etc (default class)
– AR = 14Mbyte/s, CR = 25Mbyte/s prio = 3
© Samsung Electronics Co., Ltd. 14
HTBQ Class DiagramHTBQ Class Diagram
Device Interface
pFIFO
Rate: 1MB/sCeil: 25MB/s
Rate: 3MB/sCeil: 25MB/s
Rate: 25 MB/s
class
Qdisc
Root
DataVOIP
tcp default
pFIFOpFIFO
Signal Voice
pFIFORate: 1000KB/s
Ceil: 25MB/sPri: 1
Rate: 20KB/sCeil: 25MB/s
Pri: 1
Rate: 2MB/sCeil: 25MB/s
Pri: 2
Rate: 1MB/sCeil: 25MB/s
Pri: 3
© Samsung Electronics Co., Ltd. 15
Common Configuration : IP and Port GroupsCommon Configuration : IP and Port Groups
© Samsung Electronics Co., Ltd. 16
Common Configuration : VoIP Filter Groups Common Configuration : VoIP Filter Groups
© Samsung Electronics Co., Ltd. 17
Common Configuration : Data Filter Group Common Configuration : Data Filter Group
NoticeIf a packet matches more than one filters,
a filter of higher priority (lower value) will be selected.
© Samsung Electronics Co., Ltd. 18
HTBQ Configuration – Root and Inner Classes HTBQ Configuration – Root and Inner Classes
Notebps, Kbps, and Mbps, which are the unit of the Rate and Ceil options,
mean 8 bits/s, 8 Kbits/s, and 8 Mbits/s respectively.
© Samsung Electronics Co., Ltd. 19
HTBQ Configuration – VoIP Classes (I)HTBQ Configuration – VoIP Classes (I)
© Samsung Electronics Co., Ltd. 20
HTBQ Configuration – VoIP Classes (II)HTBQ Configuration – VoIP Classes (II)
© Samsung Electronics Co., Ltd. 21
HTBQ Configuration – Data ClassesHTBQ Configuration – Data Classes
© Samsung Electronics Co., Ltd. 22
HTBQ Configuration – Default ClassesHTBQ Configuration – Default Classes
© Samsung Electronics Co., Ltd. 23
HTBQ Configuration – Class Group ListHTBQ Configuration – Class Group List
NoteSet the rate of the parent class rate not to be less than a total of that of all child classes.
Set the ceil of the parent class not to be less than the maximum value of that of all child classes.
© Samsung Electronics Co., Ltd. 24
Applying HTBQ Policy Applying HTBQ Policy
© Samsung Electronics Co., Ltd. 25
Running HTBQ Running HTBQ
© Samsung Electronics Co., Ltd. 26
SPQ Configuration : VOIP classSPQ Configuration : VOIP class
© Samsung Electronics Co., Ltd. 27
SPQ Configuration : Data classSPQ Configuration : Data class
© Samsung Electronics Co., Ltd. 28
SPQ Configuration – Root ClassSPQ Configuration – Root Class
© Samsung Electronics Co., Ltd. 29
SPQ Configuration – Class Group ListSPQ Configuration – Class Group List
© Samsung Electronics Co., Ltd. 30
Applying SPQ PolicyApplying SPQ Policy
© Samsung Electronics Co., Ltd. 31
Running SPQRunning SPQ
© Samsung Electronics Co., Ltd. 32
VoIP Service InteroperationVoIP Service Interoperation
GWIMGWIM
P1
P2
P3
SIO
V35
HSSI
RUN
V35
HSSI
P1
P2
P3RST
GLIMP
P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
P14
LNK
ACTL
NK
ACT
RST G
LIMP
P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
P14
LNK
ACTL
NK
ACT
RST
GPLIMGPLIM
MGI64
P1
P6
P2
P7
P3
P8
P4
P9
P5
P10
LNKACTSIO
GSIM
MP40
MGI64
INTERNET
VOIP(ToS 0xa0]
Data(ToS 0x0]
* Classification between VOIP and Data is done by GSIM (FFP hardware based) efficiently.
→ ToS byte of VoIP traffic (signal and media) is marked 0xa0.(DSCP = 40)
→ ToS byte of Data traffic (non-VoIP) is marked 0x0.(DSCP = 0)* Using this, GWIM needs only one ToS filter to classify VoIP traffic.
© Samsung Electronics Co., Ltd. 33
GSIM QoSGSIM QoS
© Samsung Electronics Co., Ltd. 34
GSIM QoS Architectures – based on BCM5696GSIM QoS Architectures – based on BCM5696
MASKing(Mask Table)
FILTERing(Rule Table)
Classification
METERing(Metering Table)
Full match
Marking & Policing
Actions(Rule Table)
Out-Actions(Rule Table)
In-profile out-of-profile
Buffer Manager(drop precedence packet/cell limit)
Queue Scheduler(SP, RR, WRR)
Shaper(per egress port)Packet out
Partial match
NO_MATCH_ACTION(Mask Table)
DROPMarkingMapping
drop_preECNIngress
Egress
© Samsung Electronics Co., Ltd. 35
IngressIngress
© Samsung Electronics Co., Ltd. 36
Configuration : Creating Class map (1) Configuration : Creating Class map (1)
Layer2 to Layer4 classification is supported.Layer2 to Layer4 classification is supported.
© Samsung Electronics Co., Ltd. 37
Configuration : Creating Class Map (2) Configuration : Creating Class Map (2)
Noteif a class_map is created, it implicitly contains a class_entry as configured.
© Samsung Electronics Co., Ltd. 38
Configuration : Creating Class EntryConfiguration : Creating Class Entry
NoteNew class entry’s match rule is inherited from that of its class map. So, only selected fields for the class map can be configured for class map entries. Especially, it is mandatory to configure range of IP or/and port fields of a class entry using the same bit-mask values as the class map. For above example, if netmask of class map for src/dest ip is 0xffffff00(/24), netmask of class entry for ip src/dest must be same. Also, this holds for port range. For above example, Mask value of source port is 0xfff0(/12).
© Samsung Electronics Co., Ltd. 39
Configuration : Creating Policy Map (1)Configuration : Creating Policy Map (1)
NotePreviously configured class maps can be associated with a new policy map. An incoming packet is searched against class_maps in the ascendant manner. 10 is lowest (highest priority) sequence.If multiple class_maps are matched, incremental processing will be done but in case of conflicts (permit of one class_map, deny of the other), policy of class_map of lower se
quence number is applied.
© Samsung Electronics Co., Ltd. 40
Configuration : Creating Policy Map (2)Configuration : Creating Policy Map (2)
NoteDefault action for all class_maps associated with a policy_map is permit as confirm action.
User can add/delete/modify actions.
© Samsung Electronics Co., Ltd. 41
Configuration : Policy Actions (1)Configuration : Policy Actions (1)
© Samsung Electronics Co., Ltd. 42
Configuration : Policy Actions (2)Configuration : Policy Actions (2)
NoteShaping by Token bucket. Limit (token rate), burst (bucket size)
If rate-limit is configured, actions are determined whether rate of traffic of this class is above limit or not.
traffic rate > limit => exceed actions are selected.
traffic rate <= limit => confirm actions are selected.
© Samsung Electronics Co., Ltd. 43
Configuration : Policy Actions (3)Configuration : Policy Actions (3)
© Samsung Electronics Co., Ltd. 44
Configuration : Service PolicyConfiguration : Service Policy
© Samsung Electronics Co., Ltd. 45
EgressEgress
© Samsung Electronics Co., Ltd. 46
Configuration : CoS MappingConfiguration : CoS Mapping
NoteA priority value for packet determined by 802.1p priority or configured priority by policy actions is mapped to a CoS queue according to CoS mapping. Multiple priority values can be mapped to one queue.
Threshold of WRED is configurable. Generally, CoS queue with low priority has shorter threshold than that of high priority. If CoS queue length is larger than threshold, packets with drop precedence as 1 are dropped.
© Samsung Electronics Co., Ltd. 47
Configuration : SchedulerConfiguration : Scheduler
3 types scheduler modes Strict-priority
Round-robin
Weighted-round-robin
Weight value means packet count.
Samsung Electronics Co., Ltd.