GigaSMART GTP Whitelisting and GTP Flow Sampling Examples
Refer to the following examples:
Example 1: GTP Whitelisting |
Example 2: GTP Whitelisting with Multiple Maps |
Example 3: GTP Flow Sampling |
Example 4: GTP Whitelisting, GTP Flow Sampling, and Load Balancing |
Example 5: GTP Flow Sampling with Multiple Maps |
Example 6: APN for GTP Whitlelisting, GTP Flow Sampling |
Example 7: APN for FTP Whitelisting, APN and QCI for GTP Flow Sampling |
Example 1 is a GTP whitelisting configuration example. Traffic from network ports go to the three first level maps (GTP-Control, GTP-User, and Fragments-Not_First) and then to the virtual port (vport1). If there is a match to an IMSI in the whitelist (MyIMSIs), it is forwarded to a port.
Task |
Description |
UI Steps |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1. |
Configure a GigaSMART group and associate it with a GigaSMART engine port. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2. |
Create a virtual port. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3. |
Create the GTP whitelist. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4. |
Fetch whitelist files from a specified location to populate the GTP whitelist. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 |
Associate the GigaSMART group to the GTP whitelist. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6. |
Configure the GigaSMART operation for GTP whitelisting. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7. |
Configure three first level maps. Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8. |
Configure a second level map for GTP whitelisting, the whitelist map. If there is a match to an IMSI in the whitelist (MyIMSIs), it is forwarded to a port. |
|
Example 2 is a GTP whitelisting configuration example that includes multiple GTP whitelisting maps, which provide a more granular selection of tool ports.
Traffic from network ports go to the three first level maps (GTP-Control, GTP-User, and Fragments-Not-First) and then to the virtual port (vport1). Two whitelist maps are configured. The first map specifies a rule for version 1 traffic. The second map specifies a rule for version 2 traffic.
Task |
Description |
UI Steps |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a GigaSMART group and associate it with a GigaSMART engine port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create a virtual port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Fetch whitelist files from a specified location to populate the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5. |
Associate the GigaSMART group to the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP whitelisting. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure three first level maps. Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic. |
Configure the first map.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure one second level map for GTP whitelisting, the first whitelist map. If there is a match to version 1 and if the IMSI is present in the whitelist (MyIMSIs), it is forwarded to the specified port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure another second level map for GTP whitelisting, the second whitelist map. If there is a match to version 2 and if the IMSI is present in the whitelist (MyIMSIs), it is forwarded to the specified port. |
|
Example 3 is a GTP flow sampling configuration example. Traffic from network ports go to the three first level maps (GTP-Control, GTP-User, and Fragments-Not_First) and then to the virtual port (vport1). The traffic flow is sampled based on the rules in one flow sampling map (GTP-Sample-01). The flow sampling rules specify IMSI, IMEI, and MSISDN numbers, as well as the percentage to sample. Packets are then accepted or rejected. Accepted packets are forwarded to a port. Rejected packets are dropped. Packets that do not match a rule will be passed to subsequent maps.
Task |
Description |
UI Steps |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a GigaSMART group and associate it with a GigaSMART engine port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create a virtual port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure three first level maps. Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP flow sampling. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP flow sampling, the flow sampling map. The traffic flow is sampled based on the rules in this map. |
|
Example 4 combines the GTP whitelisting configuration from Example 1 with the GTP flow sampling configuration from Example 3, and adds GigaSMART load balancing.
In Example 4, traffic from network ports go to the three first level maps (GTP-Control, GTP-User, and Fragments-Not-First) and then to the virtual port (vport1). If there is a match to an IMSI in the whitelist (MyIMSIs), it is forwarded to the port group (PG-Whitelist) for load balancing.
Note: In Example 4, the tool ports in the port group are on the same node as the GigaSMART group and GigaSMART operation.
If there is not a match to an IMSI in the whitelist, the traffic flow is sampled based on the rules in the flow sampling map (GTP-Sample-01). The flow sampling rules specify IMSI, IMEI, and MSISDN numbers, as well as the percentage to sample. Packets are then accepted or rejected. Accepted packets are forwarded to the port group (PG-Sample) for load balancing. Rejected packets are dropped. Packets that do not match a rule will be passed to subsequent maps.
Task |
Description |
UI Steps |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create port groups and specify the tool ports and enable load balancing. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a GigaSMART group and associate it with a GigaSMART engine port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create a virtual port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure three first level maps. Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Fetch whitelist files from a specified location to populate the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
(Optional) Add a single IMSI to the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Associate the GigaSMART group to the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP whitelisting. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP whitelisting, the whitelist map. If there is a match to an IMSI in the whitelist (MyIMSIs), it is forwarded to a load balancing port group. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP flow sampling. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 a load balancing port group. |
|
Example 5 includes multiple GTP flow sampling maps, which provide a more granular selection of tool ports for flow sampling.
In Example 5, traffic from network ports go to the three first level maps (GTP-Control, GTP-User, and Fragments-Not_First) and then to the virtual port (vport1). If there is a match to an IMSI in the whitelist (VoLTE_1MM), it is forwarded to the port-group (PG-Whitelist-1) for load balancing.
Note: In Example 5, the tool ports in the port group are on the same node as the GigaSMART group and GigaSMART operation.
If there is not a match to an IMSI in the whitelist, the traffic flow is sampled based on the rules in the four flow sampling maps (GTP-Sample-1 to GTP-Sample-4).
The flow sampling rules in each map specify IMSI, IMEI, and MSISDN numbers, as well as the percentage to sample. Packets are then accepted or rejected. Accepted packets are forwarded to the port-group (PG-Sample-1 to PG-Sample-4) for load balancing. Rejected packets are dropped. Packets that do not match a rule will be passed to subsequent maps, in this example, to a shared collector.
Task |
Description |
UI Steps |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create port groups, specifying the tool ports and enabling load balancing. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a GigaSMART group and associate it with a GigaSMART engine port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create a virtual port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure three first level maps. Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Fetch whitelist files from a specified location to populate the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
(Optional) Add a single IMSI to the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Associate the GigaSMART group to the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP whitelisting. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP whitelisting, the whitelist map. If there is a match to an IMSI in the whitelist (VoLTE_1MM), it is forwarded to a load balancing port group. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP flow sampling. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP flow sampling, the first flow sampling map. This map has 12 rules. Traffic flow is sampled based on the rules in this map. Accepted packets are forwarded to a load balancing port group. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP flow sampling, the second flow sampling map. This map has 12 rules. Traffic flow is sampled based on the rules in this map. Accepted packets are forwarded to a load balancing port group. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP flow sampling, the third flow sampling map. This map has 5 rules. Traffic flow is sampled based on the rules in this map. Accepted packets are forwarded to a load balancing port group. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP flow sampling, the fourth flow sampling map. This map has one rule. Traffic flow is sampled based on the rules in this map. Accepted packets are forwarded to a load balancing port group. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a collector map for any packets that do not match other rules. |
|
Example 7 specifies APN patterns for GTP whitelisting and GTP flow sampling.
In Example 7, traffic from network ports go to the two first level maps (gtp_to_v1_c and gtp_to_v1_u) and then to the virtual port (v1).
In the whitelist map, if there is a match to the APN pattern and if the IMSI is present in the whitelist (IMSI), packets are forwarded to a tool port.
If there is not a match to an IMSI in the whitelist, the traffic is flow sampled based on the APN pattern in the flow sampling map. Accepted packets are forwarded to the same tool port as specified in the whitelist map.
Any unmatched traffic goes to a shared collector that sends it to a different tool port.
Task |
Description |
UI Steps |
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a network port and two tool ports and enable them. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a GigaSMART group and associate it with two GigaSMART engine port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create a virtual port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure two first level maps, one for control traffic and one for user traffic. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Fetch whitelist files from a specified location to populate the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
(Optional) Add a single IMSI to the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Associate the GigaSMART group to the GTP whitelist. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP whitelisting. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP whitelisting, the whitelist map. If there is a match to the APN pattern and if IMSI is present in the whitelist (IMSI), it is forwarded to a tool port. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP flow sampling. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 APN pattern in this map. Accepted packets are forwarded to the same tool port as specified in the whitlelist map |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Add a shared collector for any unmatched traffic from the virtual port and send it to a different tool port. |
|
Example 6 specified APN patterns for GTP whitelisting and GTP flow sampling. It also specifies QCI for GTP flow sampling.
In Example 7, traffic from network ports go to the two first level maps (gtp_to_v1_c and gtp_to_v1_u) and then to the virtual port (v1).
In the whitelist map, if there is a match to the APN pattern and if the IMSI is present in the whitelist (IMSI), packets are forwarded to a tool port.
If there is not a match to an IMSI in the whitelist, the traffic is flow sampled based on the APN pattern and QCI value in the flow sampling map. Accepted packets are forwarded to the same tool port as specified in the whitelist map. Only 50% of traffic with QCI 5 is sent to the tool port.
Any unmatched traffic goes to a shared collector that sends it to a different tool port.
Task |
Description |
UI Steps |
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a network port and two tool ports and enable them. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a GigaSMART group and associate it with two GigaSMART engine ports |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create a virtual port. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure two first level maps, on for control traffic and one for user traffic |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Associate the GigaSMART group to the active GTP Whitelist |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP whitelisting. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure a second level map for GTP whitelisting, the whitelist map. If there is a match to the APN pattern and if the IMSI is present in the whitelist (IMSI), packets are forwarded to a tool port. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Configure the GigaSMART operation for GTP flow sampling. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 APN pattern in this map. Accepted packets are forwarded to the same tool port as specified in the whitelist map. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Add a shared collector for any unmatched traffic from the virtual port and send it to a different tool port. |
|