Load Balancing Based on the MPLS Label Information

To load-balance based on the Multiprotocol Label Switching (MPLS) label information, include the family mpls statement at the [edit forwarding-options hash-key] hierarchy level:

family mpls { 

    label-1;

    label-2;

    payload {

        ip;

    }

}

This is for aggregated Ethernet and aggregated SONET/SDH interfaces, as well as for multiple equal-cost MPLS next hops.

To include the first label in the hash key, include the label-1 option. This is used for a one-label packet.

To include the first and second label in the hash key, include both the label-1 and label-2 options. This is used for a two-label packet. The router provides hashing on the first and second labels by default. If both labels are specified on an M-series router, the entire first label and the first 16 bits of the second label are hashed. If both labels are specified on a T-series routing platform, the first 16 bits of the first label and the first     16 bits of the second label are hashed.

Hashing may include IP addresses to provide better distribution of traffic to aggregated interfaces.

To include the bits in the IP address of the IPv4 or IPv6 payload as well as the first label in the hash key, include the family mpls statement at the [edit forwarding-options hash-key] hierarchy level:

[edit forwarding-options hash-key]

family mpls { 

    label-1;

    payload {

        ip;

    }

}

(For T-series routing platforms only) To include the bits of the IP address of the IPv4 or IPv6 payload as well as both the first label and the second label in the hash key, include the family mpls statement at the [edit forwarding-options hash-key family mpls] hierarchy level:

[edit forwarding-options hash-key family mpls]

family mpls { 

    label-1;

    label-2;

    payload {

        ip;

    }

}