Configure GigaSMART IP Encapsulation/Decapsulation
This section contains the following topics:
-
Configure Both Ends of GigaSMART Tunnel
-
Configure Sending End of Tunnel: GigaVUE‑HC1 in Reno
-
Configure Receiving End of Tunnel: GigaVUE‑HC2 with GigaSMART in San Francisco
Creating a GigaSMART tunnel requires configuration on both the sending and receiving ends:
Sending End of Tunnel |
Receiving End of Tunnel |
||||||||||||||||||||||||||||||||||||
The sending end of a GigaSMART tunnel can be either a GigaVUE-VM deployment or a GigaSMART-enabled GigaVUE H Series node. Sending Data from a GigaSMART-Enabled GigaVUE H Series Node
Sending Data from GigaVUE-VM/GigaVUE‑FM When you provision a vMap for a GigaVUE-VM node in GigaVUE‑FM, in addition to selecting the virtual traffic to be forwarded, you also specify the destination to which traffic should be tunneled with the following settings:
Sending Data from GigaVUE-2404/GigaSMART-6X
|
|
Keep in mind the following when configuring GigaSMART operations with encapsulation/decapsulation components:
Feature |
Description |
Viewing Statistics |
Use the show tunneled-port commands to see statistics related to ongoing tunnel operations. Refer to View GigaSMART Statistics for more information. |
Packet Order |
Packer sequence is not preserved if the packets are reordered while traversing the Internet. The receiving GigaSMART delivers them in the same order received. |
GMIP Header |
The GMIP header is 46 bytes consisting of 14 Ethernet + 20 IP + 8 UDP + 4 tunnel version. |
Tunnel Decap Type GMIP portdst |
Use the GigaSMART Operations page to specify the UDP port on which the P interface that is associated with a network port on the receiving GigaVUE HC Series is listening. Use this option when decapsulating traffic from a either GigaSMART-enabled node or a GigaVUE-VM deployment. The setting must match the configuration of the portdst configured on the sending end of the tunnel. |
GigaSMART Engine Ports |
GigaSMART operations with a tunnel component can be assigned to GigaSMART groups consisting of multiple GigaSMART engine ports. Refer to Groups of GigaSMART Engine Ports for more information. |
The following figures demonstrate how to create a sample IP tunnel between a sending GigaVUE‑HC1 in Reno and a receiving GigaVUE H Series cluster in San Francisco. First, the overall tunnel is summarized, followed by configuration descriptions for the sending and receiving ends.
The GigaVUE‑HC1 in this location has an IP interface configured on tool port 1/1/g1 with an IP address of 11.1.9.75. Maps to this port that use a tunnel encapsulation GigaSMART operation can send data over the Internet. The following table summarizes the commands necessary to configure the sending end of the tunnel in the GigaVUE-FM:
Task |
UI Steps |
||||||||||||||||||||||||||||||||||||||||||||||||
Start by designating port 1/1/g1 as a tool port. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Use the IP Interfaces page to set up the network parameters for 1/1/g1. This page sets the IP address, subnet mask, default gateway, and MTU for the IP interface associated with a tool port on port 1/1/g1. Notice that the GigaSMART group in this example has the alias gsport1. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Now, create a tunnel encapsulation GigaSMART operation (tunnelencap) that will send traffic to IP address 21.2.9.75 on destination UDP port 10000 from source port 5000. The operation has the alias tunnelenc. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Once you have the tunnel encapsulation operation, you can include it as part of a map rule. This map rule matches IPv4 packets and sends them to 21.2.9.75:10000 (the socket specified by the GigaSMART operation named tunnelencap that you created in the previous step). |
|
Now we need to configure the receiving end of the tunnel with an IP interface associated with network port. The GigaVUE‑HC2 in this location will have an IP interface associated with network port configured on network port 5/1/x2 with an IP address of 21.2.9.75 and a GigaSMART decapsulation operation that listens on UDP port 10000.
The following table summarizes the steps necessary to configure the receiving end of the tunnel using the UI:
Task |
UI Steps |
|||||||||||||||||||||||||||||||||||||||||||||
Start by designating port 5/1/x2 as a network port. |
|
|||||||||||||||||||||||||||||||||||||||||||||
Use the IP Interfaces page to set up the network parameters for 5/1/x2. This command sets the IP address, subnet mask, default gateway, and MTU for the IP interface associated with network port on port 5/1/x2. Note that this port uses the same IP address to which the GSOP in Reno is configured to send data (21.2.9.75). |
|
|||||||||||||||||||||||||||||||||||||||||||||
Now, create a tunnel decapsulation GigaSMART operation (tunnel-decap) that will decapsulate traffic received on UDP port 10000. Recall that we configured the sending end of the tunnel to send to that UDP port. The operation has the alias hd-decap1. |
|
|||||||||||||||||||||||||||||||||||||||||||||
Once you have your tunnel decapsulation operation, you can include it as part of a map rule. This map decapsulates all traffic arriving at 5/1/x2 from IP address 21.2.9.25 (the start of the tunnel) and sends it to port 1/1/x5. This is a tool port on the chassis with box ID 1 in this cluster. |
|