CHAPTER 10. QoS
184
© 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.
Содержание Ubigate iBG2016
Страница 1: ......
Страница 16: ...INTRODUCTION XIV SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 34: ......
Страница 42: ...CHAPTER 1 Basic Configuration 8 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 62: ...CHAPTER 4 System Logging 28 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 70: ......
Страница 108: ......
Страница 126: ...CHAPTER 1 Layer 2 Switching 90 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 140: ...CHAPTER 4 RIP 104 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 156: ...CHAPTER 6 BGP 120 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 176: ...CHAPTER 7 MultiCast Protocols 140 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 180: ...CHAPTER 8 VRRP 144 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 264: ...CHAPTER 10 QoS 228 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 270: ...CHAPTER 11 VLAN forwarding with QoS 234 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 272: ......
Страница 278: ...CHAPTER 1 Authentication Authorization Accounting 228 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 298: ...CHAPTER 3 Firewall NAT 248 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 356: ...CHAPTER 5 IPSEC 306 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 358: ......
Страница 390: ...CHAPTER 2 VoIP Gateway Management 336 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 514: ...CHAPTER 4 H 323 Gateway Management 460 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 670: ...CHAPTER 8 Routing and Digit Manipulation 616 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Страница 744: ...EQBD 000071 Ed 00 ...