- Table of Contents
-
- 14-Layer 3—IP Services Configuration Guide
- 00-Preface
- 01-IP addressing configuration
- 02-IP forwarding basics configuration
- 03-ARP configuration
- 04-IPv6 fast forwarding configuration
- 05-DHCPv6 configuration
- 06-Multi-CPU packet distribution configuration
- 07-Adjacency table configuration
- 08-Web caching configuration
- 09-DNS configuration
- 10-Fast forwarding configuration
- 11-DHCP configuration
- 12-IPv6 basics configuration
- 13-IP performance optimization configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 06-Multi-CPU packet distribution configuration | 43.26 KB |
Configuring multi-CPU packet distribution
About multi-CPU packet distribution
Restrictions and guidelines: Multi-CPU packet distribution configuration
Specifying a packet distribution policy
Configuring multi-CPU packet distribution
About multi-CPU packet distribution
On a multi-CPU device, packets can be distributed among CPUs based on one of the following policies:
· Flow-based policy—Forwards packets of a flow to one CPU or multiple CPUs. The CPU processes flow packets by following the first-in first-out rule. The device supports using the source IP address, destination IP address, source port number, destination port number, and protocol number to identify a flow.
· Packet-based policy—Forwards packets in sequence to different CPUs, even though they are the same flow. This policy does not ensure packet order.
Restrictions and guidelines: Multi-CPU packet distribution configuration
If a service requires packets of a flow to be received by the same CPU, you must use the flow-based policy.
As a best practice, do not configure a packet distribution when you use the NAT or AFT service.
The following firewalls support only the flow-based policy: F5000-AI-160-G, F5000-AI-130-G, F5000-AI-120-G, F5000-AI-110-G, F5000-AI-55-G, F5000-AI-15-G, F5000-CN160-G, and F5000-E-G.
Specifying a packet distribution policy
1. Enter system view.
system-view
2. Specify a packet distribution policy.
forwarding policy { per-flow [ three-tuple | mode { source-ip | destination-ip | source-port | destination-port } ] | per-packet }
By default, the device uses the flow-based policy that identifies a flow by source IP address, destination IP address, source port number, destination port number, and protocol number.
