1. Code : STM#550 Samsung Electronics Co., Ltd. OfficeServ 7400 QoS Configuration Distribution EnglishED01

2. © Samsung Electronics Co., Ltd. 2 Objectives After successful completion of the course the trainees should be able to execute the following activities.

3. © Samsung Electronics Co., Ltd. 3 Contents General General GWIM QoS GWIM QoS GSIM QoS GSIM QoS

4. © Samsung Electronics Co., Ltd. 4 General General

5. © Samsung Electronics Co., Ltd. 5 L3/L2 QoS Functions GWIM HTBQ SPQ GSIM L2 and L3 Integrated QoS Support. Classification, DSCP Marking, Policing, Buffer Management (WRED-like) IEEE 82.1p marking, CoS Mapping Scheduling GLIMP CoS Mapping, Scheduling

6. © Samsung Electronics Co., Ltd. 6 VoIP QoS Auto-QoS supported by the DSMI (Data Server Module Interface) module. GWIM Auto-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 traffics auto-configuration of DSCP Marking for VoIP traffics. auto-configuration of IEEE 82.1p marking, CoS Mapping for VoIP traffics. GLIMP Currently auto-QoS not supported.

7. © Samsung Electronics Co., Ltd. 7 Auto QoS for VoIP INTERNE T Auto- QoS Auto-Firewall Auto- NAPT Service DSMI

8. © Samsung Electronics Co., Ltd. 8 GWIM QoS GWIM QoS

9. © Samsung Electronics Co., Ltd. 9 QoS 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)

10. © Samsung Electronics Co., Ltd. 10 QoS Internal (I) Linux kernel TC provides 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 …

11. © Samsung Electronics Co., Ltd. 11 QoS Internal (II) HTBQ (Hierarchical Token Bucket Queuing) 3 types of class : root, inner, leaf Only 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

12. © Samsung Electronics Co., Ltd. 12 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.

13. © Samsung Electronics Co., Ltd. 13 Sample Scenario Scenario Eth0 used as WAN interface QoS support is needed for VoIP traffic transmitted via eth0. Total throughput 200Mbps = 25Mbyte/s VoIP (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/s Data Traffic (class Data) AR = Total throuput – VoIP Traffic = 24 Mbyte/s, CR = 25Mbyte/s TCP (class data_tcp) –AR = 10Mbyte/s, CR = 25Mbyte/s, prio = 2 Etc (default class) –AR = 14Mbyte/s, CR = 25Mbyte/s prio = 3

14. © Samsung Electronics Co., Ltd. 14 HTBQ Class Diagram Device Interface pFIFO Rate: 1MB/s Ceil: 25MB/s Rate: 3MB/s Ceil: 25MB/s Rate: 25 MB/s class Qdisc Root Data VOIP tcp default pFIFO SignalVoice pFIFO Rate: 1000KB/s Ceil: 25MB/s Pri: 1 Rate: 20KB/s Ceil: 25MB/s Pri: 1 Rate: 2MB/s Ceil: 25MB/s Pri: 2 Rate: 1MB/s Ceil: 25MB/s Pri: 3

15. © Samsung Electronics Co., Ltd. 15 Common Configuration : IP and Port Groups

16. © Samsung Electronics Co., Ltd. 16 Common Configuration : VoIP Filter Groups

17. © Samsung Electronics Co., Ltd. 17 Common Configuration : Data Filter Group Notice If a packet matches more than one filters, a filter of higher priority (lower value) will be selected.

18. © Samsung Electronics Co., Ltd. 18 HTBQ Configuration – Root and Inner Classes Note bps, 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.

19. © Samsung Electronics Co., Ltd. 19 HTBQ Configuration – VoIP Classes (I)

20. © Samsung Electronics Co., Ltd. 20 HTBQ Configuration – VoIP Classes (II)

21. © Samsung Electronics Co., Ltd. 21 HTBQ Configuration – Data Classes

22. © Samsung Electronics Co., Ltd. 22 HTBQ Configuration – Default Classes

23. © Samsung Electronics Co., Ltd. 23 HTBQ Configuration – Class Group List Note Set 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.

24. © Samsung Electronics Co., Ltd. 24 Applying HTBQ Policy

25. © Samsung Electronics Co., Ltd. 25 Running HTBQ

26. © Samsung Electronics Co., Ltd. 26 SPQ Configuration : VOIP class

27. © Samsung Electronics Co., Ltd. 27 SPQ Configuration : Data class

28. © Samsung Electronics Co., Ltd. 28 SPQ Configuration – Root Class

29. © Samsung Electronics Co., Ltd. 29 SPQ Configuration – Class Group List

30. © Samsung Electronics Co., Ltd. 30 Applying SPQ Policy

31. © Samsung Electronics Co., Ltd. 31 Running SPQ

32. © Samsung Electronics Co., Ltd. 32 VoIP Service Interoperation GWIM GWIMGWIM P1P1 P2P2 P3P3 SIOSIO V35V35 HSSIHSSI RUNRUN V35V35 HSSIHSSI P1P1 P2P2 P3P3 RSTRST GLIMPGLIMP P1P1 P2P2 P3P3 P4P4 P5P5 P6P6 P7P7 P8P8 P9P9 P10P10 P11P11 P12P12 P13P13 P14P14 LNKLNK ACTACT LNKLNK ACTACT RSTRST GLIMPGLIMP P1P1 P2P2 P3P3 P4P4 P5P5 P6P6 P7P7 P8P8 P9P9 P10P10 P11P11 P12P12 P13P13 P14P14 LNKLNK ACTACT LNKLNK ACTACT RSTRST GPLIM MGI64 P1P1 P6P6 P2P2 P7P7 P3P3 P8P8 P4P4 P9P9 P5P5 P10P10 LNKLNK ACTACT SIOSIO 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.

33. © Samsung Electronics Co., Ltd. 33 GSIM QoS GSIM QoS

34. © Samsung Electronics Co., Ltd. 34 GSIM 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) DROP Marking Mapping drop_pre ECN Ingress Egress

35. © Samsung Electronics Co., Ltd. 35 Ingress Ingress

36. © Samsung Electronics Co., Ltd. 36 Configuration : Creating Class map (1) Layer2 to Layer4 classification is supported.

37. © Samsung Electronics Co., Ltd. 37 Configuration : Creating Class Map (2) Note if a class_map is created, it implicitly contains a class_entry as configured.

38. © Samsung Electronics Co., Ltd. 38 Configuration : Creating Class Entry Note New 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).

39. © Samsung Electronics Co., Ltd. 39 Configuration : Creating Policy Map (1) Note Previously 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 sequence number is applied.

40. © Samsung Electronics Co., Ltd. 40 Configuration : Creating Policy Map (2) Note Default action for all class_maps associated with a policy_map is permit as confirm action. User can add/delete/modify actions.

41. © Samsung Electronics Co., Ltd. 41 Configuration : Policy Actions (1)

42. © Samsung Electronics Co., Ltd. 42 Configuration : Policy Actions (2) Note Shaping 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 confirm actions are selected.

43. © Samsung Electronics Co., Ltd. 43 Configuration : Policy Actions (3)

44. © Samsung Electronics Co., Ltd. 44 Configuration : Service Policy

45. © Samsung Electronics Co., Ltd. 45 Egress Egress

46. © Samsung Electronics Co., Ltd. 46 Configuration : CoS Mapping Note A 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.

47. © Samsung Electronics Co., Ltd. 47 Configuration : Scheduler 3 types scheduler modes Strict-priority Round-robin Weighted-round-robin Weight value means packet count.

48. Samsung Electronics Co., Ltd.