Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

family mpls

Syntax

Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

no-label-1-exp option introduced in Junos OS Release 8.0.

label-3 and no-labels options introduced in Junos OS Release 8.1.

ether-pseudowire statement introduced in Junos OS Release 9.1 (M320 and T Series routers only); support extended to M120 and MX Series routers in Junos OS Release 9.4.

Description

For aggregated Ethernet and SONET/SDH interfaces only, configure load balancing based on MPLS labels and payload. Only the IPv4 protocol is supported.

Options

label-1—Use this to include the first MPLS label in the hash key. Used for one-label packet.

label-2—Use this to include the second MPLS label in the hash key. Configure this when you want to include the second MPLS label in the hash key. If both label-1 and label-2 are specified, the entire first label and the first 16 bits of the second label are hashed.

label-3—Use this to include the third MPLS label in the hash key. You must configure the label-1, label-2, and label-3 statements in order to include the third label.

no-labels—Use this to omit MPLS labels from the hash key.

no-label-1-exp—Use this to omit the EXP bit of the first label from the hash calculation. Use this to avoid complications from reordering.

payload—Use this to incorporate bits from the IP payload in the hash key.

ether-pseudowire (M120, M320, MX Series, and T Series routers)—Load-balance IPv4 traffic over Layer 2 Ethernet pseudowires.

ip—Use this to include the IP address of the IPv4 or IPv6 payload in the hash key.

layer-3-only—Use this to include only Layer 3 IP information from the IP payload data.

port-data—Use this to include the source and destination port field information. By default, the most significant byte and least significant byte of the source and destination port fields are hashed. To select specific bytes to be hashed, include one or more of the source-msb, source-lsb, destination-msb, and destination-lsb options at the [edit forwarding-options hash-key family mpls payload ip port-data] hierarchy level. To prevent all four bytes from being hashed, include the layer-3-only statement at the [edit forwarding-options hash-key family mpls payload ip] hierarchy level.

destination-lsb—Use this to include the least significant byte of the destination port.

destination-msb—Use this to include the most significant byte of the destination port.

source-lsb—Use this to include the least significant byte of the source port.

source-msb—Use this to include the most significant byte of the source port.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.