GigaSMART GTP Scaling

GTP can be scaled as follows:

■   GigaSMART Cards in GigaVUE‑HC3
■   GTP Engine Grouping

GigaSMART Cards in GigaVUE‑HC3

Required License: GTP Filtering & Correlation

A total of four GigaSMART SMT-HC3-C05 line cards are supported on a single GigaVUE‑HC3 node. This provides a total of eight GigaSMART engine ports, which increases the amount of GigaSMART processing available on the GigaVUE‑HC3.

The increased number of GigaSMART line cards in the GigaVUE‑HC3 can be used by the following GTP applications: GTP flow filtering, GTP flow sampling, and GTP whitelisting.

GTP Engine Grouping

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 a GTP 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.

GTP Engine Grouping Configuration Example

This is an example of a GTP engine group consisting of two engine ports on a GigaVUE‑HC3 node. This example includes a GigaSMART operation for GTP flow filtering.

Step

Description

Command
1.    

Configure ports as follows:

● one network type of port. This will be used as the from attribute in two first level maps in Step 5 and Step 6.
● one tool type of port for the to attribute in a second level flow filtering map in Step 7.
● one tool type of port for the to attribute in a shared collector map in Step 8.

Then administratively enable the ports.

(config) # port 22/3/x3 type network

(config) # port 22/3/x1 type tool

(config) # port 22/1/x11 type tool

(config) # port 22/3/x3 params admin enable

(config) # port 22/3/x1 params admin enable

(config) # port 22/1/x11 params admin enable
2.  

Configure a GigaSMART group and associate it with two GigaSMART engine ports, to form the GTP engine group.

The GigaSMART group will be used in Step 3 and Step 4.

(config) # gsgroup alias gsg2 port-list 22/2/e1,23/1/e2
3.

For GTP flow filtering, configure a flow filtering GigaSMART operation and assign it to the GigaSMART group. The gsop will be used in the second level flow filtering map in Step 7.

(config) # gsop alias gtp_gsg2 flow-ops flow-filtering gtp port-list gsg2
4.

Configure a virtual port and assign it to the same GigaSMART group. This virtual port will be used as the to attribute in the first level maps in Step 5 and Step 6, as the from attribute in the second level map in Step 7, and as the from attribute in the shared collector map in Step 8.

(config) # vport alias vp1 gsgroup gsg2
5.

Create a first level map that directs GTP control traffic from the physical network port to the virtual port created in Step 4.

Note:  In the rule, 2123 is GTP-c traffic.

This map, with the param traffic control attribute, identifies the GTP-c control traffic needed for GTP engine grouping.

Note:  The order of configuration is important. Configure param traffic control before any map rules.

(config) # map alias gtp_to_vp1-c

(config map alias gtp_to_vp1-c) # type firstLevel byRule

(config map alias gtp_to_vp1-c) # roles replace admin to owner_roles

(config map alias gtp_to_vp1-c) # param traffic control

(config map alias gtp_to_vp1-c) # rule add pass portdst 2123 bidir

(config map alias gtp_to_vp1-c) # to vp1

(config map alias gtp_to_vp1-c) # from 22/3/x3

(config map alias gtp_to_vp1-c) # exit

(config) #
6.

Create another first level map that directs GTP user traffic from the physical network port to the virtual port created in Step 4.

Note:  In the rule, 2152 is GTP-u traffic.

GTP-u traffic corresponding to the same GTP-c traffic will be sent to the same virtual port.

(config) # map alias gtp_to_vp1

(config map alias gtp_to_vp1) # type firstLevel byRule

(config map alias gtp_to_vp1) # roles replace admin to owner_roles

(config map alias gtp_to_vp1) # rule add pass portdst 2152 bidir

(config map alias gtp_to_vp1) # rule add pass ipfrag all-frag-no-first

(config map alias gtp_to_vp1) # to vp1

(config map alias gtp_to_vp1) # from 22/3/x3

(config map alias gtp_to_vp1) # exit

(config) #
7.

Create a second level map for GTP flow filtering that takes traffic from the virtual port, applies the flow filtering GigaSMART operation, matches IMEIs and version specified by the flow rule, and sends matching traffic to a tool port.

(config) # map alias from_vp1

(config map alias from_vp1) # type secondLevel flowFilter

(config map alias from_vp1) # roles replace admin to owner_roles

(config map alias from_vp1) # use gsop gtp_gsg2

(config map alias from_vp1) # flowrule add pass gtp imei * version 2

(config map alias from_vp1) # to 22/3/x1

(config map alias from_vp1) # from vp1

(config map alias from_vp1) # exit

(config) #
8.

Add a shared collector for any unmatched traffic from the virtual port and send it to a different tool port than in Step 7.

(config) # map-scollector alias from_vp1_scoll

(config map-scollector alias from_vp1_scoll) # roles replace admin to owner_roles

(config map-scollector alias from_vp1_scoll) # from vp1

(config map-scollector alias from_vp1_scoll) # collector 22/1/x11

(config map-scollector alias from_vp1_scoll) # exit

(config) #

GTP Engine Grouping Configuration Complex Example

This is a more complex example of GTP engine grouping than the previous example. This example has four engine ports on two GigaSMART line cards on the same GigaVUE‑HC3 node. The GigaSMART line cards are in slots 1 and 3.

The GigaVUE‑HC3 node is the cluster leader of a two-node out-of-band cluster.

This example includes GigaSMART operations for GTP flow filtering with load balancing, GTP flow sampling with load balancing, and GTP whitelisting. The whitelist must be associated with the GigaSMART group on the leader, the GigaVUE‑HC3.

Step

Description

Command
1.    

Configure ports on the GigaVUE‑HC3 as follows:

● one network type of port. This will be used as the from attribute in two first level maps in Step 11 and Step 12.
● twelve tool type of ports. There are four tool ports in each of three port groups used for load balancing. The port groups will be created in Step 6.
● five tool type of ports for a GigaStream that will be created in Step 2.
● two tool type of ports for another GigaStream that will be created in Step 2.

Then administratively enable the ports.

(config) # port 23/2/c3 type network

(config) # port 23/3/x1..x4 type tool

(config) # port 23/3/x9..x12 type tool

(config) # port 23/3/x13..x16 type tool

(config) # port 23/3/x20..x24 type tool

(config) # port 23/2/c1..c2 type tool

(config) # port 23/2/c3 params admin enable

(config) # port 23/3/x1..x4 params admin enable

(config) # port 23/3/x9..x12 params admin enable

(config) # port 23/3/x13..x16 params admin enable

(config) # port 23/3/x20..x24 params admin enable

(config) # port 23/2/c1..c2 params admin enable
2.

On the GigaVUE‑HC3, configure one GigaStream using five tool ports. This will be used as the to attribute in the map in Step 11.

Configure another GigaStream to be used in the stack link between the GigaVUE‑HC3 that will be created in Step 5.

(config) # gigastream alias hc3-gs-1 port-list 23/3/x20..x24 params hash advanced

(config) # gigastream alias hc3-80g port-list 23/2/c1..c2 params hash advanced
3.  

Configure ports on the GigaVUE‑HC1-Plus as follows:

● two tool type of ports for a GigaStream that will be created in Step 4.
● one tool type of port that will be used as the to attribute in a map in Step 11.
● four tool type of ports for a GigaStream that will be created in Step 4.

Then administratively enable the ports.

(config) # port 33/2/q1..q2 type tool

(config) # port 33/3/x11 type tool

(config) # port 33/2/x20..x24 type tool

(config) # port 33/2/q1..q2 params admin enable

(config) # port 33/3/x11 params admin enable

(config) # port 33/2/x20..x24 params admin enable
4.

On the GigaVUE‑HC1-Plus, configure a GigaStream using two tool ports. This will be used in the stack link created in Step 5.

Configure another GigaStream using four tool ports. This will be used in the shared collector in Step 17.

(config) # gigastream alias hc3-80g port-list 33/2/q1..q2 params hash advanced

(config) #s gigastream alias hc3-gs-4 port-list 33/2/x20..x24 params hash advanced

5.

Configure the stack link between the GigaVUE‑HC1-Plus and GigaVUE‑HC3.

(config) # stack-link alias hc1p-hc3 between gigastreams hc3-80g and hc1p-80g
6.

Create three port groups and specify four tool ports each, for load balancing. Also, enable load balancing on each port group.

The port groups, hc3-pg-1 and hc3-pg-2, will be used as the to attribute in two second level flow sampling maps in Step 14 and Step 15.

The port group, hc3-q2x24-1-4, will be used as the to attribute in a second level flow filtering map in Step 16.

(config) # port-group alias hc3-q2x24-1-4

(config port-group alias hc3-q2x24-1-4) # port-list 23/4/x1..x4

(config port-group alias hc3-q2x24-1-4) # smart-lb enable

(config port-group alias hc3-q2x24-1-4) # exit

(config) # port-group alias hc3-pg-1

(config port-group alias hc3-pg-1) # port-list 23/4/x9..x12

(config port-group alias hc3-pg-1) # smart-lb enable

(config port-group alias hc3-pg-1) # exit

(config) # port-group alias hc3-pg-2

(config port-group alias hc3-pg-2) # port-list 23/4/x13..x16

(config port-group alias hc3-pg-2) # smart-lb enable

(config port-group alias hc3-pg-2) # exit
7.  

Configure a GigaSMART group and associate it with four GigaSMART engine ports, two in slot 1 and two in slot 3, to form the GTP engine group.

The GigaSMART group will be used in Step 8, Step 9, and Step 10.

(config) # gsgroup alias hc3scale-3engines-slots1and3 port-list 23/1/e1,23/1/e2,23/3/e1,23/3/e2
8.

Associate the GigaSMART group to an existing GTP whitelist.

Note:  The whitelist must be associated with the GigaSMART group on the leader, which is the GigaVUE‑HC3 in this example.

(config) # gsparams gsgroup hc3scale-4engines-slots1and3 gtp-whitelist add 500-1
9.

For GTP flow filtering, configure a flow filtering GigaSMART operation, specify load balancing, and assign the GigaSMART operation to the GigaSMART group. The hc3-scale-ff-lb gsop will be used in the second level flow filtering map in Step 16.

For GTP flow sampling, configure a flow sampling GigaSMART operation, specify load balancing, and assign the GigaSMART operation to the GigaSMART group. The hc3-scale-fs-lb gsop will be used in the two second level flow sampling maps in Step 14 and Step 15.

For GTP whitelisting, configure a whitelisting GigaSMART operation, and assign the GigaSMART operation to the GigaSMART group. The hc3-scale-wl gsop will be used in the second level whitelisting map in Step 13. (This GigaSMART operation is not load balanced.)

(config) # gsop alias hc3-scale-ff-lb flow-ops flow-filtering gtp lb app gtp metric hashing key imsi port-list hc3scale-4engines-slots1and3

(config) # gsop alias hc3-scale-fs-lb flow-ops gtp-flowsample lb app gtp metric hashing key imsi port-list hc3scale-4engines-slots1and3

(config) # gsop alias hc3-scale-wl flow-ops gtp-whitelist port-list hc3scale-4engines-slots1and3
10.

Configure a virtual port and assign it to the same GigaSMART group. This virtual port will be used as the to attribute in the first level maps in Step 11 and Step 12, as the from attribute in the second level maps in Step 13, Step 14, Step 15, Step 16, and as the from attribute in the shared collector in Step 17.

(config) # vport alias vp-hc3scale-4engines-slots1and3 gsgroup hc3scale-4engines-slots1and3
11.

Create a first level map that directs GTP control traffic from the physical network port to the virtual port created in Step 10.

Note:  In the rule, 2123 is GTP-c traffic.

This map, with the param traffic control attribute, identifies the GTP-c control traffic needed for GTP engine grouping.

Note:  The order of configuration is important. Configure param traffic control before any map rules.

In addition to the virtual port, traffic is also sent to a GigaStream and a tool port.

(config) # map alias to_hc3_gtpc

(config map alias to_hc3_gtpc) # type firstLevel byRule

(config map alias to_hc3_gtpc) # roles replace admin to owner_roles

(config map alias to_hc3_gtpc) # param traffic control

(config map alias to_hc3_gtpc) # rule add pass portdst 2123 bidir

(config map alias to_hc3_gtpc) # to hc3-gs-1,vp-hc3scale-4engines-slots1and3,33/3/x11

(config map alias to_hc3_gtpc) # from 23/3/q6

(config map alias to_hc3_gtpc) # exit

(config) #
12.

Create another first level map that directs GTP user traffic from the physical network port to the virtual port created in Step 10.

Note:  In the rule, 2152 is GTP-u traffic.

GTP-u traffic corresponding to the same GTP-c traffic will be sent to the same virtual port.

(config) # map alias to_hc3_gtpu_1

(config map alias to_hc3_gtpu_1) # type firstLevel byRule

(config map alias to_hc3_gtpu_1) # roles replace admin to owner_roles

(config map alias to_hc3_gtpu_1) # rule add pass portdst 2152 bidir

(config map alias to_hc3_gtpu_1) # rule add pass ipfrag all-frag-no-first

(config map alias to_hc3_gtpu_1) # to vp-hc3scale-4engines-slots1and3

(config map alias to_hc3_gtpu_1) # from 23/7/q6

(config map alias to_hc3_gtpu_1) # exit

(config) #
13.

Configure a second level map for GTP whitelisting, the whitelist map, that takes traffic from the virtual port, applies the whitelisting GigaSMART operation, and sends traffic to the remoteGigaVUE‑HC1-Plus node through a GigaStream.

(config) # map alias from_hc3_wl

(config map alias from_hc3_wl) # type secondLevel flowWhitelist

(config map alias from_hc3_wl) # roles replace admin to owner_roles

(config map alias from_hc3_wl) # use gsop hc3-scale-w

(config map alias from_hc3_wl) # to hc3-gs-1

(config map alias from_hc3_wl) # from vp-hc3scale-4engines-slots1and3

(config map alias from_hc3_wl) # exit

(config) #
14.

Configure a second level map for GTP flow sampling. This is the first of two flow sampling maps.

This map filters for version 2. It takes traffic from the virtual port and applies the flow sampling GigaSMART operation.

Traffic flow is sampled based on the flow sampling rule in this map. Accepted packets are forwarded to load balancing port group hc3-pg-2.

(config) # map alias from_hc3_fs_v2

(config map alias from_hc3_fs_v2) # type secondLevel flowSample

(config map alias from_hc3_fs_v2) # roles replace admin to owner_roles

(config map alias from_hc3_fs_v2) # use gsop hc3-scale-fs-lb

(config map alias from_hc3_fs_v2) # flowsample add gtp imsi 5* version 2 percentage 60

(config map alias from_hc3_fs_v2) # to hc3-pg-2

(config map alias from_hc3_fs_v2) # from vp-hc3scale-4engines-slots1and3

(config map alias from_hd3_fs_v2) # exit

(config) #
15.

Configure a second level map for GTP flow sampling. This is the second of two flow sampling maps.

This map filters for version 1. It takes traffic from the virtual port and applies the flow sampling GigaSMART operation.

Traffic flow is sampled based on the flow sampling rule in this map. Accepted packets are forwarded to load balancing port group hc3-pg-1.

(config) # map alias from_hc3_fs_v1

(config map alias from_hc3_fs_v1) # type secondLevel flowSample

(config map alias from_hc3_fs_v1) # roles replace admin to owner_roles

(config map alias from_hc3_fs_v1) # use gsop hc3-scale-fs-lb

(config map alias from_hc3_fs_v1) # flowsample add gtp imsi 5* version 1 percentage 60

(config map alias from_hc3_fs_v1) # to hc3-pg-1

(config map alias from_hc3_fs_v1) # from vp-hc3scale-4engines-slots1and3

(config map alias from_hc3_fs_v1) # exit

(config) #
16.

Create a second level map for GTP flow filtering that takes traffic from the virtual port, applies the flow filtering GigaSMART operation, matches IMSIs specified by the flow rule, and sends matching traffic to load balancing port group hc3-q2x24-1-4.

(config) # map alias from_hc3_ff

(config map alias from_hc3_ff) # type secondLevel flowFilter

(config map alias from_hc3_ff) # roles replace admin to owner_roles

(config map alias from_hc3_ff) # use gsop hc3-scale-ff-

(config map alias from_hc3_ff) # flowrule add pass gtp imsi *

(config map alias from_hc3_ff) # to hc3-q2x24-1-4

(config map alias from_hc3_ff) # from vp-hc3scale-4engines-slots1and3

(config map alias from_hc3_ff) # exit

(config) #
17.

Add a shared collector for any unmatched traffic from the virtual port and send it to a GigaStream.

(config) # map-scollector alias s_coll_hc3

(config map-scollector alias s_coll_hc3) # roles replace admin to owner_roles

(config map-scollector alias s_coll_hc3) # from vp-hc3scale-4engines-slots1and3

(config map-scollector alias s_coll_hc3) # collector hc3-gs-4

(config map-scollector alias s_coll_hc3) # exit

(config) #
18.  

Display the configuration for this example.

(config) # show gigastream

(config) # show stack-link

(config) # show port-group

(config) # show gsgroup

(config) # show vport

(config) # show gsop

(config) # show map