Traffic Classifier
|
The traffic classifier is based on ACL, but it differs from ACL. The former matches the next behavior to the traffic that conforms to the policies, but the latter has the behaviors of deny and permit. In addition, the matching ranges are different. The range of the traffic matched by the traffic classifier is greater or equal to an ACL. The matching range of an ACL is a subset in the traffic classifier. For example, at present, the match of the VLAN ID is not used in the ACL. For the MF rules, at present, the NE20/20E product defines the rules based on the following information: l The source MAC address, destination MAC address, link layer protocol ID, and the priority of the packets with the TAG in the Ethernet packet header l The IP priority or DSCP or ToS field value, prefix of the source IP address, prefix of the destination IP address, TCP or UDP protocol number carried by the IP packet, fragment mark, TCP-SYN mark, source port number or interface range of TCP or UDP, and the destination port number or interface range of TCP or UDP in the IPv4 packets The ACL rules can be defined for the MF. If the behaviors in the ACL and the QoS policy delivering are combined, the permit or deny behavior in the ACL are not considered. The behaviors in the traffic classifier are taken as the standards. Multiple matching rules can be defined in a traffic classifier. The default relationship between there rules is "and", that is, the packets must match these rules at the same time, so that the corresponding behaviors can be implemented. The relation between these rules can be set through the parameter "operator". This is similar to the ACL rules. If an ACL includes multiples rules, the relationship between these rules is "or", and the relationship between the ACLs is "and" |

Favorite (0)