Login
- Table of Contents
-
- 13-Layer 3—IP Services Configuration Guide
- 00-Preface
- 01-IP addressing configuration
- 02-IP forwarding basics configuration
- 03-Fast forwarding configuration
- 04-ARP configuration
- 05-IPv6 basics configuration
- 06-IPv6 fast forwarding configuration
- 07-DHCP configuration
- 08-DHCPv6 configuration
- 09-DNS configuration
- 10-IP performance optimization configuration
- 11-Multi-CPU packet distribution configuration
- 12-Adjacency table configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 11-Multi-CPU packet distribution configuration | 40.32 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.
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.
Support for the three-tuple and mode keywords depends on the device model. For more information, see the command reference.
