HP 6125XLG R2306-HP 6125XLG Blade Switch ACL and QoS Configuration Guide - Page 26

Applying the QoS policy, Applying the QoS policy to an interface

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

Step Command 3. Associate a traffic class with a traffic behavior to create a classifier classifier-name behavior class-behavior association in behavior-name [ mode dcbx ] the QoS policy. Remarks By default, a traffic class is not associated with a traffic behavior. Repeat this step to create more class-behavior associations. If a class-behavior association has the mode dcbx keyword, it applies only to the Data Center Bridging Exchange Protocol (DCBX). For more information about DCBX, see Layer 2-LAN Switching Configuration Guide. Applying the QoS policy You can apply a QoS policy to the following destinations: • An interface-The QoS policy takes effect on the traffic sent or received on the interface. • A VLAN-The QoS policy takes effect on the traffic sent or received on all ports in the VLAN. • Globally-The QoS policy takes effect on the traffic sent or received on all ports. • Control plane-The QoS policy takes effect on the traffic received on the control plane. You can modify traffic classes, traffic behaviors, and class-behavior associations in a QoS policy even after it is applied. If a traffic class references an ACL for traffic classification, you can delete or modify the ACL (such as add rules to, delete rules from, and modify rules of the ACL). QoS policies applied to an interface, a VLAN, and globally are in descending order of priority. In other words, the switch first matches the criteria in the QoS policy applied to an interface. If there is a match, the switch executes the QoS policy applied to the interface and ignores the QoS policies applied to the VLAN and globally. Applying the QoS policy to an interface A QoS policy can be applied to multiple interfaces, but only one QoS policy can be applied in one direction (inbound or outbound) of an interface. The QoS policy applied to the outgoing traffic on an interface does not regulate local packets, which are critical protocol packets sent by the local system for operation maintenance. The most common local packets include link maintenance, routing (IS-IS, BGP, and OSPF for example), RIP, LDP, and SSH packets. If both packet filtering with the permit action and a QoS policy are applied to an interface, the car and filter actions in the QoS policy do not take effect. For more information about packet filtering, see "Configuring ACLs." To apply the QoS policy to an interface: Step 1. Enter system view. 2. Enter interface view. Command system-view interface interface-type interface-number Remarks N/A N/A 20

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
20
Step
Command
Remarks
3.
Associate a traffic class with a
traffic behavior to create a
class-behavior association in
the QoS policy.
classifier
classifier-name
behavior
behavior-name
[
mode
dcbx
]
By default, a traffic class is not
associated with a traffic behavior.
Repeat this step to create more
class-behavior associations.
If a class-behavior association has
the
mode dcbx
keyword, it applies
only to the Data Center Bridging
Exchange Protocol (DCBX). For
more information about DCBX, see
Layer 2—LAN Switching
Configuration Guide
.
Applying the QoS policy
You can apply a QoS policy to the following destinations:
•
An interface
—The QoS policy takes effect on the traffic sent or received on the interface.
•
A VLAN
—The QoS policy takes effect on the traffic sent or received on all ports in the VLAN.
•
Globally
—The QoS policy takes effect on the traffic sent or received on all ports.
•
Control plane
—The QoS policy takes effect on the traffic received on the control plane.
You can modify traffic classes, traffic behaviors, and class-behavior associations in a QoS policy even
after it is applied. If a traffic class references an ACL for traffic classification, you can delete or modify the
ACL (such as add rules to, delete rules from, and modify rules of the ACL).
QoS policies applied to an interface, a VLAN, and globally are in descending order of priority. In other
words, the switch first matches the criteria in the QoS policy applied to an interface. If there is a match,
the switch executes the QoS policy applied to the interface and ignores the QoS policies applied to the
VLAN and globally.
Applying the QoS policy to an interface
A QoS policy can be applied to multiple interfaces, but only one QoS policy can be applied in one
direction (inbound or outbound) of an interface.
The QoS policy applied to the outgoing traffic on an interface does not regulate local packets, which are
critical protocol packets sent by the local system for operation maintenance. The most common local
packets include link maintenance, routing (IS-IS, BGP, and OSPF for example), RIP, LDP, and SSH
packets.
If both packet filtering with the
permit
action and a QoS policy are applied to an interface, the
car
and
filter
actions in the QoS policy do not take effect. For more information about packet filtering, see
"
Configuring ACLs
."
To apply the QoS policy to an interface:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type interface-number
N/A