VXLAN Layer 2 gateway payload tag processing

An SLX-OS device provides the following modes for the processing of the payload tag that is received on the attachment-circuit packets:

VXLAN RFC-compliant mode
Enhanced payload tag transport mode

VXLAN RFC-compliant mode

In RFC-compliant mode, the VLAN tag in a packet is not carried in the packet and must be stripped at the ingress device before the VXLAN encapsulated packet is sent into the network.

To configure RFC-compliant mode, configure the bridge domain in raw mode as shown in the following example.

pw-profile test
    vc-mode raw

bridge-domain 10 p2mp
   pw-profile test

Then extend the bridge domain in the overlay gateway, as shown in the following example.

overlay-gateway gateway1
type layer2-extension
ip interface loopback 1
map bridge-domain 10 vni 999
site vcs1
 ip address 10.67.67.1
 extend bridge-domain add 10

Note

An SLX-OS device supports RFC-compliant mode with the bridge domain-based VXLAN service only.

Enhanced payload tag transport mode

In enhanced payload tag transport mode, one VLAN tag from the traffic is carried as part of the VXLAN encapsulated packet as an inner payload tag. This tag can carry the PCP value to include the priority information and also can interoperate with other devices. This tag is removed in the remote device capable of this behavior.

Note

This mode does not interoperate with RFC-compliant mode.

This mode is supported for VLAN-based VXLAN service and bridge domain-based VXLAN service with tag mode.

To configure enhanced payload tag transport mode, configure the bridge domain in tagging mode as shown in the following example.

pw-profile test
    vc-mode tag

bridge-domain 10 p2mp
   pw-profile test

Then extend the bridge domain in the overlay gateway, as shown in the following example.

overlay-gateway gateway1
type layer2-extension
ip interface Loopback 1
map bridge-domain 10 vni 999
site vcs1
 ip address 10.67.67.1
 extend bridge-domain add 10