H3C Technologies H3C SR8800 - Manual (Page 92)

83
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter scheduler policy view. qos scheduler-policy sp-name [ id sp-id ] N/A
3. Enter scheduler policy layer view. layer { 1 | 2 } N/A
4. Instantiate a user-defined
forwarding group.
• In match mode:
forwarding-group fg-name match [ extended ]
qos-local-id { local-id-list | local-id1 to
local-id2 }
• In group mode:
forwarding-group fg-name group
Use either
command.
NOTE:
•
When performing forwarding group instantiation, instantiate a parent forwarding group before
instantiating its child forwarding groups. Before removing instances of a parent forwarding group, you
must remove all instances of the child forwarding groups first.
• To instantiate a parent forwarding group and its child forwarding groups in the match mode, the
instantiation rule of the parent node must be the sum of the instantiation rules of the child forwarding
groups, and the instantiation rules of child forwarding groups cannot overlap.
• You can instantiate a forwarding group multiple times, but the instantiation rules must not overlap.
• The pre-defined forwarding group nested in a scheduler policy has been instantiated in the group
mode. You cannot modify or remove the instantiation rule of the pre-defined forwarding group.
You can change the QoS-local ID of a packet by marking the QoS-local ID.
To set the QoS-local ID marking action for a traffic behavior:
Step Command
1. Enter system view. system-view
2. Create a behavior and enter behavior
view.
traffic behavior behavior-name
3. Configure the QoS-local ID marking
action for the traffic behavior.
remark qos-local-id local-id-value
4. Exit behavior view. quit
Applying an scheduler policy to an interface
A scheduler policy can be applied only in the outbound direction of an interface. After being applied,
the scheduler policy can control and manage traffic.
Configuration prerequisites
Before applying a scheduler policy to an interface, complete the following tasks:
• Configure child nodes for all forwarding group nodes nested in the scheduler policy
• Nest forwarding classes in a forwarding group with nested forwarding classes. Forwarding class
nesting of a forwarding group node is considered complete only when all the pre-defined
forwarding classes are nested.
• Instantiate all forwarding group nodes in the scheduler policy tree. A forwarding group node that
has not been instantiated cannot appear in a scheduler policy tree.