Adding a Tunnel Profile for L2GRE Tunnel Destination

L2GRE tunnels from the DC Edge cluster to L2GRE tunnel endpoints forward client traffic to third‑party devices using L2GRE encapsulation as part of the SD‑LAN service. This mechanism encapsulates Layer 2 Ethernet frames within GRE packets, allowing them to be transported over an IP network and enabling Layer 2 network extension across Layer 3 boundaries.

Complete the following steps to create a Tunnel Profile:

  1. From the navigation bar, select Network Control > Service Catalog.
    The Service Catalog page is displayed.
  2. Click Add in the Tunnel Profile tile.
    The Add Tunnel Profile page is displayed.

    Add Tunnel Profile - L2GRE Tunnel Destination

  3. Complete the following fields:
    1. Profile Name: Enter the name for the tunnel profile.
    2. Tunnel Type: Select L2GRE.
    3. Destination IP Address: Enter the IPv4 address of the third-party, external, upstream device to which the DC cluster will establish a tunnel.
        Note:
      • These profiles are not backward compatible and cannot be used as a default profile.
      • Ensure a Static route is configured to an L2GRE tunnel destination IP address via the Core port on each Edge.
    4. Gateway Path MTU: Enter the value in bytes (allowed values are 1280 through 1450).
    5. Force Fragmentation: When enabled, the Edge device will automatically fragment packets, ignoring the Don't Fragment (DF) bit in the IP header of the packets. Forced packet fragmentation can reduce congestion and improve network throughout, but it may lead to fragment loss, packet reassembly issues, and memory exhaustion. This option is disabled by default. Toggle the switch to enable.
    6. Tunnel Keep Alive Interval: Defines the interval between two consecutive keepalive request messages. Range: 1 through 5 seconds, with a default value of 2 seconds.
    7. Tunnel Keep Alive Retries: Defines the maximum number of consecutive keepalive requests that can fail before the Edge determines the L2GRE server is unreachable. Range: 3 through 5 retries, with a default value of 5.

      When the Edge device reaches the maximum number of retry attempts and determines that the connection to the L2GRE server is down, it generates a down event/alarm and sends it to RUCKUS One. When the connection between Edge and the L2GRE server is restored, Edge triggers an up event.

  4. Click Add.
    The Tunnel Profile is created and is displayed on the Tunnel Profile page.