Maipu Administration Guide

Configure Flow Classification

Flow classification adopts some rule to identify the packets that comply with one feature, divides the packets of different features to multiple classes, and then uses the corresponding QoS mechanism to provide different services for different classes. Therefore, the flow classification is the premise and basis of providing different services.

Configuration Condition

Before configuring the flow classification, first complete the following task:

Configure the ACL.

Configure Counter

Configuring counting action in the action group aims to count the number of the matched packets.

Table 1-4 Configure the counter

Step	Command	Description
Enter the global configuration mode	configure terminal	-
Configure the L3 action group and enter the L3 action group configuration mode	l3-action-group l3-action-group-name	Either After entering the L3 action group configuration mode, the subsequent configuration just takes effect in the current L3 action group; After entering the L2 action group configuration mode, the subsequent configuration just takes effect in the current L2 action group; After entering the egress action group configuration mode, the subsequent configuration just takes effect in the current egress action group
Configure the L2 action group and enter the L2 action group configuration mode	l2-action-group l2-action-group-name
Configure the egress action group and enter the egress action group configuration mode	egr-action-group egr-action-group-name
Configure the counter	count { all-colors }	Mandatory By default, packets are not counted in the action group.

Configure Meter

Configure the meter in the action group to limit the rate or mark the matched packets. When configuring a nonexistent meter, the meter takes effect immediately when the specified meter is configured. When no meter is configured in the action group, all matched packets are considered as green packets. When a meter is configured in the action group for coloring the packets, the packets will be marked in green and yellow according to the packet traffic, and then the counter will count the number of the packets of different colors.

Table 1-5 configure the meter

Step	Command	Description
Enter the global configuration mode	configure terminal	-
Configure the meter and enter the meter mode	traffic-meter traffic-meter-name	Mandatory By default, the packets in yellow are dropped and the meter mode is not configured. After entering the meter configuration, a complete meter configuration contains meter actions for packets in yellow and meter mode configuration. An incomplete configuration will not take effect.
Configure the meter actions	meter action yellow { drop \| transmit }	Optional By default, the packets in yellow are dropped.
Configure the meter mode	meter mode { srtcm cir cbs ebs \| trtcm cir cbs pir pbs }	Mandatory By default, the meter mode is not configured.
Enter the global configuration mode	exit	-
Configure the L3 action group and enter the L3 action group configuration mode	l3-action-group l3-action-group-name	Either After entering the L3 action group configuration mode, the subsequent configuration just takes effect in the current L3 action group; After entering the L2 action group configuration mode, the subsequent configuration just takes effect in the current L2 action group; After entering the egress action group configuration mode, the subsequent configuration just takes effect in the current egress action group
Configure the L2 action group and enter the L2 action group configuration mode	l2-action-group l2-action-group-name
Configure the egress action group and enter the egress action group configuration mode	egr-action-group egr-action-group-name
Configure the binding meter	meter traffic-meter-name	Mandatory By default, no meter is bound.

If the ACL bound to the objects is configured with the action group and the action group is configured with a meter for limiting the rate, conflicted rate limitation actions may exist. When the rate limitation is applied, the packets in red and yellow are dropped. For example, port 0/1 belongs to VLAN1, the ACL on port 0/1 permits the packets of the source IP address 1.1.1.1 to pass, and the traffic is configured within 5 Mbps. The ACL of VLAN1 permits the packets of the source IP address 1.1.1.1 to pass and the traffic is configured within 1 Mbps. In this situation, the minimum rate in the packet channel will take effect and the traffic is configured within 1 Mbps. Specially, due to the hardware limitation, the actual traffic for multi-level rate limitation will be less than the minimum rate in the packet channel. Therefore, multi-level rate limitation is not recommended when an accurate rate limitation is needed.
The meter in the egress action group does not support the remark lp or remark dotlp-lp action.
You cannot re-mark the yellow packet.
The meter is based on the chips. That is, the meter on each chip limits the traffic rate over the port. If the meter exists in two different chips under the link aggregation port, a meter exists in each chip and thus the rate limitation has the effect twice of the expected rate limitation effect.
If a meter is applied to the VLAN, the meter takes effect for each chip on each line card. VLAN objects are limited within 10 Mbps. If five single-core line cards exist on the device, the 10 Mbps traffic takes effect for a pair of line cards. That is, the traffic on each line card complying with the VLAN rate limitation is 10 Mbps. If two chips exist on a line card, the traffic for each chip on the line card is 10 Mbps.

Configure Flow Mirror

Configuring the flow mirror in the action group aims to specify the matched packet to the port.

Table 1-6 Configure the flow mirror

Step	Command	Description
Enter the global configuration mode	configure terminal	-
Configure the L3 action group and enter the L3 action group configuration mode	l3-action-group l3-action-group-name	Either After entering the L3 action group configuration mode, the subsequent configuration just takes effect in the current L3 action group; After entering the L2 action group configuration mode, the subsequent configuration just takes effect in the current L2 action group.
Configure the L2 action group and enter the L2 action group configuration mode	l2-action-group l2-action-group-name
Configure the flow mirror	mirror interface interface-name	Mandatory By default, the flow mirror is not configured.

Configure Re-direct

Configuring the packet re-direct in the action group aims to redirect the matched packets to the specified port or the specified next hop.

Table 1-7 Configure the re-direct

Step	Command	Description
Enter the global configuration mode	configure terminal	-
Configure the L3 action group and enter L3 action group configuration mode	l3-action-group l3-action-group-name	Either After entering the L3 action group configuration mode, the subsequent configuration just takes effect in the current L3 action group; After entering the L2 action group configuration mode, the subsequent configuration just takes effect in the current L2 action group.
Configure the L2 action group and enter the L2 action group configuration mode	l2-action-group l2-action-group-name
Configure the re-direct	redirect { interface interface-name \| interface link-aggregation link-aggregation-id}	Mandatory By default, the packet re-direct is not configured.

Configure Re-marking l2-priority

Configuring packet re-marking in the action group aims to classify the matched packets to facilitate users to adopt different QoS policies in the subsequent data communications.

Table 1-8 Configure re-marking l2-priority

Step	Command	Description
Enter the global configuration mode	configure terminal	-
Configure the L3 action group and enter the L3 action group configuration mode	l3-action-group l3-action-group-name	Either After entering the L3 action group configuration mode, the subsequent configuration just takes effect in the current L3 action group; After entering the L2 action group configuration mode, the subsequent configuration just takes effect in the current L2 action group; After entering the egress action group configuration mode, the subsequent configuration just takes effect in the current egress action group
Configure the L2 action group and enter the L2 action group configuration mode	l2-action-group l2-action-group-name
Configure the egress action group and enter the egress action group configuration mode	egr-action-group egr-action-group-name
Configure re-marking l2-priority	remark l2-priority { dscp dscp-value \|{{ dot1p \| dot1p-lp \| lp } { priority-value \| precedence }}}	Mandatory By default, re-marking l2-priority is not configured.

In the action group, the priority field in the TOS of IP packet cannot be used to retag the 802.1p priority in the VLAN tag.
The egress action group does not support the remark action.

Configure Re-marking l3-priority