GTP Overlap Flow Sampling Maps Example
This section contains:
Example 1: GTP Overlap Mode
Example 1 is a GTP overlap mapping mode example.
In Example 1, traffic from a single network port goes to a single first level map (mapLevel1-GTP) which directs GTP-Control, and GTP-User traffic to a virtual port (VP31). Traffic from VP31 is replicated to two GTP whitelisting maps (WLMAP1 and WLMAP2) and two GTP flow sampling maps (FSMAP1 and FSMAP2), which then forward accepted traffic to the final port-group destinations, pg1 and pg2, for load balancing (refer to Figure 1 GTP Overlap Mode Example 1).
Figure 33 | GTP Overlap Mode Example 1 |
Note: In Example 1, the tool ports and GigaStreams in the port group are on the same node as the GigaSMART group and GigaSMART operation.
Within each GTP whitelisting and flow sampling pair, if there is not a match to an IMSI in the whitelist map, the traffic flow is sampled based on the rules in the flow sampling map. The flow sampling rules specify IMSI, IMEI, and MSISDN numbers, as well as the percentage to sample.
Within each map pair, packets are then accepted or rejected. Accepted packets are forwarded to the port groups for load balancing. Rejected packets are dropped.
Use the following steps to configure example 1.
Task |
Description |
UI Steps |
1 |
Create GigaStreams that will be part of the port groups |
|
2 |
Create port groups and specify the tool ports and assign GigaStreams to the port groups. The port groups will also be load balanced. |
|
3 |
Configure a GigaSMART group and associate it with a GigaSMART engine port. |
|
4. |
Create a virtual port. Note: You must enable GTP Overlap when configuring a virtual port for GTP overlap mapping. |
|
5. |
Create the GTP Whitelist |
|
6. |
Fetch whitelist files from a specified location to populate the GTP whitelist. |
|
7. |
Associate the GigaSMART group to the GTP whitelist. |
|
8. |
Configure the GigaSMART operation for GTP whitelisting. |
|
9. |
Configure the GigaSMART operation for GTP flow sampling. |
|
10. |
Configure the first level maps. In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic. |
|
11. |
Configure the first second level GTP overlap map for GTP whitelisting If there is a match to an IMSI in the whitelist for GTP version 1 traffic, it is then forwarded to load balancing port group pg1. |
|
12. |
Configure a second level map for GTP flow sampling, the flow sampling map. If there is not a match to an IMSI in the whitelist, the traffic flow is sampled based on the rules in this map. Accepted packets are forwarded to load balancing port group pg1. |
|
13. |
Configure the next second level GTP overlap map for GTP whitelisting If there is a match to an IMSI in the whitelist for GTP version 2 traffic, it is then forwarded to load balancing port group pg2. |
|
14. |
Configure the next second level map for GTP flow sampling. If there is not a match to an IMSI in the whitelist as evaluated by the second level GTP whitelisting map WLMAP2, the traffic flow is sampled based on the rules in this map. Accepted packets are forwarded to load balancing port group pg2. |
|
15. |
Configure a map group. Add the GTP whitelisting and the two GTP flow sampling maps configured in previous steps. |
|