Contents

Basic IP forwarding on the device··································································· 2

FIB table········································································································································· 2

Displaying FIB table entries·············································································································· 2

Configuring load sharing··················································································· 4

Configuring per-packet or per-flow load sharing················································································ 4

Configuring load sharing based on bandwidth··················································································· 4

Basic IP forwarding on the device

The device uses the destination IP address of a received packet to find a match from the forwarding information base (FIB) table. It then uses the matching entry to forward the packet.

FIB table

A device selects optimal routes from the routing table, and puts them into the FIB table. Each FIB entry specifies the next hop IP address and output interface for packets destined for a specific subnet or host.

For more information about the routing table, see Layer 3—IP Routing Configuration Guide.

Use the display fib command to display FIB table entries. The following example displays the entire FIB table.

<Sysname> display fib

Destination count: 4 FIB entry count: 4

Flag:

  U:Useable   G:Gateway   H:Host   B:Blackhole   D:Dynamic   S:Static

  R:Relay     F:FRR

Destination/Mask   Nexthop         Flag     OutInterface/Token       Label

10.2.0.0/16        10.2.1.1        U        GE2/0/1                  Null

10.2.1.1/32        127.0.0.1       UH       InLoop0                  Null

127.0.0.0/8        127.0.0.1       U        InLoop0                  Null

127.0.0.1/32       127.0.0.1       UH       InLoop0                  Null

A FIB entry includes the following items:

·     Destination—Destination IP address.

·     Mask—Network mask. The mask and the destination address identify the destination network. A logical AND operation between the destination address and the network mask yields the address of the destination network. For example, if the destination address is 192.168.1.40 and the mask 255.255.255.0, the address of the destination network is 192.168.1.0. A network mask includes a certain number of consecutive 1s. It can be expressed in dotted decimal format or by the number of the 1s.

·     Nexthop—IP address of the next hop.

·     Flag—Route flag.

·     OutInterface—Output interface.

·     Token—MPLS Label Switched Path index number.

·     Label—Inner label.

Displaying FIB table entries

Execute display commands in any view.

Configuring load sharing

If a routing protocol finds multiple equal-cost best routes to the same destination, the device forwards packets over the equal-cost routes to implement load sharing.

Configuring per-packet or per-flow load sharing

Load sharing can be implemented in one of the following ways:

·     Per-packet—The device forwards packets over equal-cost routes.

·     Per-flow—The device forwards flows over equal-cost routes. Packets of one flow travel along the same routes. You can configure the device to identify a flow based on the following criteria: source IP address, destination IP address, source port number, destination port number, IP protocol number, and ingress port.

In a complex network, when the five tuples cannot distinguish flows, you can use the algorithm keyword to specify an algorithm to identify flows.

To configure per-flow or per-packet load sharing:

Configuring load sharing based on bandwidth

This feature load shares flow traffic among multiple output interfaces based on their load percentages. The device calculates the load percentage for each output interface in terms of the interface expected bandwidth.

Devices that run load sharing protocols, such as Locator/ID Separation Protocol (LISP), implement load sharing based on the ratios defined by these protocols.

To configure load sharing based on bandwidth: