About L2GRE Tunnel Termination
Figure 583: L2GRE Tunnel Termination illustrates the L2GRE tunnel termination on a GigaVUE device located in a site that is remote to the device from where the traffic was routed across the cloud.
Figure 583: L2GRE Tunnel Termination
In this diagram, traffic is tapped on a GigaVUE H Series device at a remote site, and then it is tunneled through L2GRE encapsulation across the network before it reaches the GigaVUE H Series device at the main office site, which is connected to the actual tools. The traffic from a GigaVUE V Series appliance running on an AWS platform is tunneled through L2GRE encapsulation across the cloud, and the L2GRE tunneled traffic hits the GigaVUE H Series device at the main office site. The tunnel termination is executed on an ingress circuit port (IP interface). After tunnel termination the packet is presented to the flow mapping module to filter based on map rule parameters.
L2GRE Tunnel Termination—Rules and Notes
Keep in mind the following rules and notes when working with L2GRE tunnel termination:
| • | L2GRE tunnel termination is supported only on GigaVUE-HC1, GigaVUE-HC2 CCv2, GigaVUE-HC3, GigaVUE-TA40, GigaVUE-TA100, and GigaVUE-TA200 devices. |
| • | A maximum of 1500 L2GRE IDs are supported. |
| • | Flow mapping that is configured on the circuit port used for L2GRE decapsulation will filter only the inner packet attributes along with L2GRE-ID. Any other non-tunneled packets that ingress on this circuit port will not be filtered or redirected to tool ports, even if it matches the rules configured on the map. |
| • | IPv6 is not supported with L2GRE tunnels. |
| • | L2GRE tunnel termination do not support reassembly of packets. |
| • | L2GRE tunnel termination is supported only on encapsulated packets that are not tagged. |
| • | Map-passall is not supported for the circuit port that decapsulates the L2GRE packet. |
| • | Inner VLAN qualifier is not supported on the port in which the L2GRE tunnel termination is enabled. |
| • | L2GRE ID qualifier is available as part of existing static templates. Following table provides details about the platforms for which the static templates are available: |
|
Template |
Platform |
|
|
GigaVUE-HC2 (CCv2)/GigaVUE-HC1/GigaVUE-TA40 |
GigaVUE-HC3/GigaVUE-TA100 |
|
|
IPv4 |
No |
Yes |
|
IPv6 |
Yes |
Yes |
|
IPv4+UDA |
No |
Yes |
|
IPv4+MAC |
Yes |
Yes |
|
UDA |
Yes |
Yes |
MORE INFORMATION 
