CHAPTER 19. QoS
178
© SAMSUNG Electronics Co., Ltd.
In the above command third set of argument, which specified the classification
type, is optional. If not entered, it is not considered as a valid class for
classification. So in such cases user can enter in to the class context via CLI
command ‘policy-class <class> and then configure the required classification
type. But the classification type at given level must be same as peer classes.
Here is an example of how classes ‘mpls’, ‘mpls-lo’, ‘mpls-hi’, ‘ipv4’, ‘ipv4-
lo’, ‘ipv4-hi’, and ‘def’(ether-type=ANY-OTHER) would be created.
Configure/interface/bundle wan1/qos# add-policy-class mpls
rootout
packet-class mpls
Configure/interface/bundle wan1/qos# add-policy-class mpls-
lo mpls
exp 0
Configure/interface/bundle wan1/qos# add-policy-class mpls-
hi mpls
exp default
Configure/interface/bundle wan1/qos# add-policy-class ipv4
rootout
packet-class ipv4
Configure/interface/bundle wan1/qos# add-policy-class ipv4-
lo ipv4
dscp 0
Configure/interface/bundle wan1/qos# add-policy-class ipv4-
hi ipv4
dscp default
Configure/interface/bundle wan1/qos# add-policy-class def
root-out
packet-class default
In the above commands, ‘packet-class’, ‘exp’, ‘dscp’, and ‘tc’ are the
matching field(classification) types for various rules specified above.
Whenever the matching/ classification field type specified for the first
childclass, which is being created, the search algorithm is decided based on
the matching/classification field type in the policy rule and accordingly the
search function and search structure in the parent class are initialized.
The match values are added to the search structure in the parent class and a
reference to the(matching) child-class is stored in each of those entries. In this
example, when class ‘mpls’ is added, the ‘search_type’ in the parent class
‘root-out’ is set to ‘packet-class’. The search function and search structure
pointers are set to do a hash table lookup based on packet-class value.
Summary of Contents for Ubigate iBG3026
Page 1: ......
Page 16: ...INTRODUCTION XIV SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 32: ...TABLE OF CONTENTS XXX SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 34: ......
Page 64: ...CHAPTER 4 System Logging 30 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 72: ......
Page 94: ...CHAPTER 7 WAN Interfaces 58 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 110: ......
Page 156: ...CHAPTER 15 BGP 118 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 178: ...CHAPTER 17 VRRP 140 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 262: ......
Page 288: ...CHAPTER 23 Firewall NAT 248 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 346: ......
Page 706: ...CHAPTER 36 Management 664 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 718: ...EQBD 000026 Ed 00 ...