Configuring Preferential Forwarding of Local Traffic in a CSS
On a network where a CSS and an Eth-Trunk are used, configuring the Eth-Trunk to preferentially forward local traffic increases bandwidth use efficiency between devices in the CSS and improves traffic forwarding efficiency.
Context
You can configure an Eth-Trunk to preferentially forward local traffic (or not) according to the following guidelines:
- If active interfaces in the local Eth-Trunk have sufficient bandwidth to forward traffic on the local device, configure the Eth-Trunk to preferentially forward local traffic. This improves traffic forwarding efficiency and increases bandwidth use efficiency between devices in the CSS.
- If active interfaces in the local Eth-Trunk do not have sufficient bandwidth to forward traffic on the local device, do not configure the Eth-Trunk to preferentially forward local traffic. A portion of the traffic on the local device is then forwarded through member interfaces of an Eth-Trunk on another device, preventing packet loss.
Pre-configuration Tasks
Before configuring an Eth-Trunk to preferentially forward local traffic, complete the following tasks:
Create an Eth-Trunk and add physical interfaces to the Eth-Trunk.
Establish a CSS.
- Ensure that member interfaces of the local Eth-Trunk have sufficient bandwidth to forward local traffic.
Procedure
- Run:
system-view
The system view is displayed.
- Run:
interface eth-trunk trunk-id
The view of an Eth-Trunk is displayed.
- Run:
local-preference enable
The Eth-Trunk is configured to preferentially forward local traffic.
By default, an Eth-Trunk forwards traffic preferentially through local member interfaces.
This function is only valid for known unicast packets, and does not work with unknown unicast packets, broadcast packets, and multicast packets.