Configuring MF Classification-based Traffic Policies for IP Packets

This section describes how to configure MF classification-based traffic policies for IP packets.

Context

As networks rapidly develop and services become increasingly diversified, multiple service flows share the same network resource. In some scenarios, incoming or ongoing traffic on a network needs to be classified. For example, voice, video, and data services must be allocated different bandwidths because they have different requirements on delay. Traffic from different users must be distinguished and allocated different bandwidths and priorities. BA classification-based traffic policies fail to meet such requirements.

MF classification-based traffic policies for IP packets provide differentiated services according to parameters such as the DSCP value, protocol type, IP address, and port number in packets, which can meet the requirements of different services on bandwidth and delay.

Typically, MF classification-based traffic policies are configured on routers at the network edge, and BA classification-based traffic policies are configured on core routers.

MF classification-based traffic policies for IP packets is in conflict with Flow Influence.

Pre-configuration Tasks

Before configuring MF classification-based traffic policies for IP packets, you need to complete the following tasks:

Configure the physical parameters of interfaces.
Configure the link layer attributes of interfaces.
Configure IP addresses for interfaces.
Enable the routing protocol for communication between devices at the network layer.

Defining a Traffic Classifier: You need to configure a traffic classifier before configuring class-based QoS. The traffic classifier can be configured based on the ACL rule, IP precedence, MAC address, protocol address, and so on.

Defining a Traffic Behavior and Configuring Actions: This section describes the traffic behaviors supported by the device and how to configure actions for a traffic behavior.

(Optional) Enabling the IPv6 QoS Local ID Matching Mode: If a matching rule based on the IPv6 QoS policy ID is defined, the rule can take effect only after the IPv6 QoS local ID matching mode is enabled.

Defining a Policy and Specifying a Behavior for a Classifier in the Policy: After traffic classifiers and traffic behaviors are defined, a traffic policy needs to be configured to associate the traffic classifiers with the traffic behaviors.

Applying a Traffic Policy: A class-based policy does not take effect unless it is applied to an interface.

(Optional) Enabling Statistics Collection of a Traffic Policy: The function to collect statistics of a traffic policy needs to be enabled in prior to viewing statistics of this traffic policy.

(Optional) Enabling the Logging of the First Packet that Matches an ACL Rule: When packets match an ACL, information about the first matching packet can be logged, including the name of the inbound/outbound interface, source IP address, destination IP address, protocol number, source port number, destination port number, time when the first packet is received (millisecond-level), and number of packets within a specified period.

Verifying the Configuration of MF Classification-based Traffic Policies for IP Packets: After class-based QoS is successfully configured, you can view the traffic classifiers, traffic behaviors, binding between traffic classifiers and behaviors in a specified traffic policy, and the configurations and running status of traffic policies and queues.