Configuration Guidelines; Qos Configuration Procedures; Qos Policy Configuration Procedure - HP 830 Series Configuration Manual

Poe+ unified wired-wlan switch switching engine web-based
Hide thumbs Also See for HP 830 Series:
Table of Contents

Advertisement

Input DSCP value
40 to 47
48 to 55
56 to 63
In the default DSCP to DSCP mapping table, an input value yields a target value equal to it.

Configuration guidelines

When you configure QoS, follow these guidelines:
When you configure rate limit and traffic policing for a behavior, make sure the ratio of CBS to CIR
is more than 100:16. Otherwise, the handling for bursty traffic may be affected.
If the outgoing port configured for a traffic redirecting action is bound to a NAT virtual interface,
packets are redirected to the L3 NAT card, which can cause traffic redirecting failure.
If an ACL is referenced by a QoS policy for defining traffic classification rules, packets matching the
referenced ACL rule are organized as a class and the behavior defined in the QoS policy applies
to the class regardless of whether the referenced ACL rule is a deny or permit clause.
If a QoS policy is applied in the outbound direction of a port, the QoS policy cannot influence local
packets. Local packets refer to the critical protocol packets that maintain the normal operation of the
device. QoS must not process such packets to avoid packet drop. Commonly used local packets are:
link maintenance packets, ISIS packets, OSPF packets, RIP packets, BGP packets, LDP packets,
RSVP packets, and SSH packets and so on.
When you configure queuing for a traffic behavior:
In a policy, a traffic behavior with EF configured cannot be associated with the default class,
while a traffic behavior with WFQ configured can only be associated with the default class.
In a policy, the total bandwidth assigned to the AF and EF classes cannot be greater than the
available bandwidth of the interface to which the policy applies. The total bandwidth
percentage assigned to the AF and EF classes cannot be greater than 100%.
In the same policy, the same bandwidth unit must be used to configure bandwidth for AF classes
and EF classes, either absolute bandwidth value or percent.

QoS configuration procedures

QoS policy configuration procedure

A QoS policy includes the following components: class, traffic behavior, and policy. You can associate
a class with a traffic behavior using a QoS policy.
1.
Class:
Classes identify traffic.
A class is identified by a class name and contains match criteria.
You can define a set of match criteria to classify packets. The relationship between criteria can be
and or or.
and—The device considers a packet belongs to a class only when the packet matches all the
criteria in the class.
Local precedence (Queue)
5
6
7
477
CoS
5
6
7

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents