GTP Scaling

Required License: GTP Filtering & Correlation

A GigaSMART group (gsgroup) associated with GTP applications can have multiple GigaSMART engine port members. Up to four engine ports can be combined to form an engine group. The engine group provides higher capacity to GTP applications by load balancing GTP user-data plane (GTP-u) traffic among the members of the group. Grouping multiple GigaSMART engine ports increases the effective throughput for GTP applications.

Note:  Software version 5.5 supports a maximum of 6 million GTP subscriber sessions for GigaVUE‑HC2 nodes, whereas, it supports 12 million GTP subscriber sessions for GigaVUE‑HC3 nodes.

GTP engine grouping is supported on GigaVUE‑HC2 nodes.

GTP engine grouping can be used by the following GTP applications: GTP flow filtering, GTP flow sampling, and GTP whitelisting.

The following table lists GTP engine grouping support for GigaVUE nodes:

Keep in mind the following recommendations and restrictions:

Note:  One engine port per GigaSMART group is the default behavior supported in software version 4.5 and prior releases without GTP engine grouping.

Enable the ControlTraffic checkbox when creating a First Level By Rule map, to allow GTP applications to pass GTP control traffic (GTP-c) to all GigaSMART engines in a GTP engine group. GTP-c traffic is sent to all members of the engine group in order to replicate the session tables.

Note:  In the map with the ControlTraffic enabled, only one vport is supported.

Starting in software version 4.7, you can edit the map with ControlTraffic option enabled. For example, Control Traffic can be selected in an existing first level map, or it can be deleted from a first level map. Other editing, such as changing the Source or the Destination in the first level map is also allowed.

To set GTP Control Traffic:

When there is existing GTP configuration with one engine port per GigaSMART group in a pre-4.5 software version, an upgrade from that earlier software version to 4.5 or a higher release will succeed.

However in the 4.5 or higher release, you cannot convert that configuration to multiple engine ports per GigaSMART group. You must delete the configuration and reconfigure it, including the GigaSMART group, GigaSMART operation, virtual port, and maps. This is due to the need for separate maps for GTP control plane and GTP user plane traffic in 4.5 and higher releases.

You can modify the engine ports in a GigaSMART group. For example, you can add an engine port to a GigaSMART group or remove an engine port from a GigaSMART group. After the change, reset all the GigaSMART line cards or modules that have engine ports configured in the GigaSMART group.

You can modify the vport relating to the first level map with Control Traffic enabled. For example, you can change the vport configured in the map. After the change, reset all the GigaSMART line cards or modules that have engine ports configured in the vport.

To display the GigaSMART Group statistics, select GigaSMART > GigaSMART Groups > Statistics.

Refer to GigaSMART Group Statistics Definitions for descriptions of the statistics.