Configuring Load Balancing Based on the Inner IP Header of GTP Packets

Configuration Guide

This configuration process is supported only by the admin VS.

Usage Scenarios

On a P node in an L3VPN, a GTP packet carries double MPLS labels and the inner IP header. Load balancing is typically performed based on the outer IP header's source and destination IP addresses and the tunnel endpoint identifier (TEID). However, because the source and destination IP addresses of the inner IP header change frequently but those of the outer IP header do not, load balancing is uneven. To address this problem, run the command to enable load balancing for GTP packets carrying the inner IP header based on the inner IP header's source and destination IP addresses and the TEID. If the inner IP header is completely present in the packet window, this header and the TEID are obtained for hash calculation. If the inner IP header is not completely present in the packet window and deep hash is not configured, the outer IP header and TEID are obtained according to the original process for hash calculation. If the inner IP header is not completely present in the packet window and deep hash is configured, the packet window is moved to obtain the inner IP header and TEID for hash calculation.