Non-Transport Tunnel Termination

Non-transport tunnel termination applies to packets that do not have destination MAC address within the chassis MAC address range and considered “not destined to us.”

Type of headers to be decapsulated can be configured using CLI or gNMI commands. Non-transport tunnel termination supports header decapsulation for VXLAN, IPGRE, nvGRE, GTP-U, and IP-in-IP.

For VXLAN, GTP-U, and nvGRE packets, a key or identifier can be configured for termination. For example, in VXLAN, a particular VNID can be configured to match for termination. If a key or identifier is not configured for traffic types, all packets are matched irrespective of the key or identifier they ingresses with.

The non-transport tunnel termination parameters can be configured through ingress-group CLI command. Tunnel termination takes the configured action on incoming GRE, GTP, IP-in-IP, NVGRE, and VXLAN packets:

• Terminate or Decapsulate: The encapsulation header is decapsulated and the remaining packets are processed in further blocks. This results in shifting the scope of the headers to inner headers automatically.

  Terminate or decapsulate can also be done using route-map or listener-policy.

• Scope-shift: There is no header decapsulation and the scope of the header is shifted to inner headers. This results in further blocks in the packet processing pipeline using inner headers of the packet.

  Scope-shift can also be done using route-map.

• No-operation: There is no decapsulation or scope shift, only packet classification is done. In ingress group, this results in further processing blocks processing all headers in the packet.

Non-transport tunnel termination in terminate mode

Non-transport tunnel termination in scope-shift mode

Non-transport tunnel termination in no-op mode

Note

All VXLAN packets without a VLAN-Tag are considered as Transport tunnel packets even if the transport header destination MAC address does not match the chassis MAC.