Configuring ACL-based Simplified PBR
Pre-configuration Tasks
You can configure ACL-based simplified PBR to redirect Layer 3 packets that match ACL rules to a specified next-hop IP address.
Configure link layer attributes of interfaces to ensure proper operation of interfaces.
Configure ACL rules.
Context
To control traffic that enters a network, configure an ACL rule to match packets based on packet information including the source IP address, fragment flag, destination IP address, source port number, and source MAC address, and then configure an ACL-based simplified traffic policy to filter the packets that match the ACL rule. Compared with PBR, ACL-based simplified PBR does not require a traffic classifier, traffic behavior, or traffic policy, resulting in easy configuration. However, ACL-based simplified PBR matches packets only based on ACL rules, so it does not support so many types of matching rules as a traffic policy.
If ACL-based simplified traffic policies are configured in the system view, VLAN view, and interface view, the precedence of these policies is: interface view > VLAN view > system view.
Procedure
- Configure redirection globally.
- Configure redirection in a VLAN.
- Configure redirection on an interface.
- Configure packet filtering in a QoS group.
Verifying the Configuration
Run the display traffic-policy applied-record traffic-redirect [ [ global [ slot slot-id ] | interface interface-type interface-number | vlan vlan-id | qos group group-id ] [ inbound ] ] command to check the application records of a specified traffic policy.
Follow-up Procedure
For the CE12800, if a low-priority traffic policy takes effect before you apply a high-priority traffic policy, ACL rules may be slow to take effect. Consequently, service processing will be delayed. You can run the traffic-policy fast-mode command in the system view to enable fast delivery of ACLs. This ensures that ACL rules take effect rapidly and services can be processed in real time.