Use label field in EVPN routes as 24-bit value when encapsulation is VXLAN
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.0 |
Fix Committed
|
High
|
Nischal Sheth | |||
R2.1 |
Fix Committed
|
High
|
Nischal Sheth | |||
R2.20 |
Fix Committed
|
High
|
Nischal Sheth | |||
Trunk |
Fix Committed
|
High
|
Nischal Sheth |
Bug Description
When EVPN routes are advertised with VXLAN encapsulation, the ethernet
tag field is set to the VNI value. Further, the label is also set to
the VNI value by Contrail and JUNOS.
Reading of https:/
was that the VNI would be encoded as a 20-bit label value consistent
with how MPLS labels are encoded. However, it turns out that we need
to use the entire 24 bits as the label when the encapsulation is VXLAN.
Note that the bottom 4 bits of the label field in the EVPN route are ignored when we use it to carry an MPLS label.
JUNOS currently treats the label as a 20-bit value but will change to
using it as a 24-bit value before the EVPN + VXLAN code is released.
This is required to interoperate with other vendors.
Since the VNI value is already carried in the ethernet tag field we can
make the change from 20-bit to 24-bit labels in a backward compatible
manner with JUNOS as follows. When the encapsulation is VXLAN, if the
ethernet tag is non-zero use that as the label value, else honor the
label. JUNOS already has this logic in place.
description: | updated |
Changed in juniperopenstack: | |
milestone: | none → r2.30-fcs |
information type: | Proprietary → Public |
tags: | added: contrail-control |
description: | updated |
description: | updated |
description: | updated |
Review in progress for https:/ /review. opencontrail. org/11570
Submitter: Nischal Sheth (<email address hidden>)