GRE Tunnel Groups
ArubaOS supports redundancy of GRE Generic Routing Encapsulation. GRE is an IP encapsulation protocol that is used to transport packets over a network. tunnels for both Layer-2 and Layer-3 GRE Generic Routing Encapsulation. GRE is an IP encapsulation protocol that is used to transport packets over a network. tunnels. This feature enables automatic redirection of the user traffic to a standby tunnel when the primary tunnel goes down.
A tunnel group is identified by a name or number. You can add multiple tunnels to a tunnel group. The order of the tunnels defined in the tunnel-group configuration specifies their standby precedence. The first member of the tunnel-group is the primary tunnel.
A GRE Generic Routing Encapsulation. GRE is an IP encapsulation protocol that is used to transport packets over a network. tunnel group combines two tunnels created on a managed device, where one tunnel is active and the other tunnel is the standby. Traffic forwarding can occur on the active tunnel, and the standby tunnel can become active once the active tunnel is down. When the first tunnel fails, the second tunnel carries the traffic. The third tunnel in the tunnel-group takes over if the second tunnel also fails. In the meantime, if the first tunnel comes up, it becomes the most eligible standby tunnel.
You can also enable or disable preemption as part of the tunnel-group configuration. Preemption is enabled by default. This option automatically redirects the traffic whenever it detects an active tunnel with a higher precedence in the tunnel group. When preemption is disabled, the traffic gets redirected to a higher precedence tunnel only when the tunnel carrying the traffic fails.
When creating a tunnel group, keep in mind the following:
When a tunnel is added to the tunnel group, the tunnel is used for data traffic only if it is the active tunnel in the group.
Standby tunnels do not carry any data traffic. However, all tunnels in the group continue to send and receive keepalive Signal sent at periodic intervals from one device to another to verify that the link between the two devices is working. If no reply is received, data will be sent by a different path until the link is restored. A keepalive can also be used to indicate that the connection should be preserved so that the receiving device does not consider it timed out and drop it. packets.
Only one type of tunnel can be placed into a tunnel group—either Layer-2 or Layer-3. That is, you cannot have a tunnel group consisting of both Layer-2 and Layer-3 tunnels.
The default value of tunnel group type is Layer-3.
All tunnels in a Layer-2 tunnel group must be tunneling the same VLAN Virtual Local Area Network. In computer networking, a single Layer 2 network may be partitioned to create multiple distinct broadcast domains, which are mutually isolated so that packets can only pass between them through one or more routers; such a domain is referred to as a Virtual Local Area Network, Virtual LAN, or VLAN..
A Layer-2 tunnel can only be part of one tunnel group.
The ArubaOS Layer-2 tunnel-group is not interoperable with other vendors. You must set up Layer-2 tunnel groups between Aruba devices only.
The following procedure configures a Layer-2 or Layer-3 tunnel group:
1. In the node hierarchy, navigate to .
2. Click below the table.
3. Specify a name for the tunnel-group in the field.
4. In the text box, click to add one or more tunnel IDs.
5. Select the IDs and click .
6. To enable preemption, select the check box. This option is enabled by default.
7. In the section, identify the tunnel group type as a layer-2 or layer-3 group.
8. Click .
9. Click .
10. In the window, select the check box and click .
The following CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. command configures a Layer-2 or Layer-3 tunnel group:
(host) [mynode] (config) tunnel-group <tungrpname>
(host) [mynode] (config-tunnel-group)#
mode {L2|L3)
preemptive-failover
tunnel <tunnel-id>
