Login
- Table of Contents
-
- 06-Layer 3—IP Services Configuration Guide
- 00-Preface
- 01-ARP configuration
- 02-IP addressing configuration
- 03-DHCP configuration
- 04-DNS configuration
- 05-NAT configuration
- 06-NAT66 configuration
- 07-IP forwarding basics configuration
- 08-Fast forwarding configuration
- 09-Multi-CPU packet distribution configuration
- 10-Adjacency table configuration
- 11-IP performance optimization configuration
- 12-UDP helper configuration
- 13-IPv6 basics configuration
- 14-DHCPv6 configuration
- 15-IPv6 fast forwarding configuration
- 16-AFT configuration
- 17-Tunneling configuration
- 18-GRE configuration
- 19-ADVPN configuration
- 20-WAAS configuration
- 21-Web caching configuration
- 22-HTTP proxy configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 09-Multi-CPU packet distribution configuration | 42.93 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. A data flow can be identified by the five-tuple: Source IP address, destination IP address, source port number, destination port number, and protocol number.
· 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.
Specifying a packet distribution policy
1. Enter system view.
system-view
2. Specify a packet distribution policy.
forwarding policy { per-flowe [ enhance ] | per-packet }
By default, the flow-based policy is used.
|
|
NOTE: The enhance keyword takes effect only on the FIP-680, FIP-260, FIP-380, FIP-660, and SAP-XP4GE32 modules. |
