GTP Correlation Configuration Examples
The following sections provide examples of GTP correlation and GTP load balancing. Refer to the following examples:
Example 1: Identifying High-Value and/or Roaming Subscribers Based on IMSIs
Use GTP correlation to identify high value subscribers based on an IMSI or group of IMSIs. GTP correlation keeps track of the IMSIs that you are interested in monitoring. It correlates them to the corresponding data/user-plane sessions for the subscriber and/or group of subscribers. Filtering on subscriber ID (IMSI) limits the amount of traffic that is sent to monitoring tools.
In Example 1, filter rules are configured to identify and forward all the traffic related to subscribers identified by an IMSI prefix. All traffic specific to the filtered IMSIs 22222222222223*, including GTP-c and GTP-u, is forwarded to a monitoring tool. A shared collector is configured to which traffic not matching the filters is sent.
To access GigaSMART within GigaVUE‑FM, access a device that has been added to GigaVUE‑FM from the GigaVUE‑FM interface. GigaSMART appears in the navigation pane of the device view on supported devices. Refer to Access GigaSMART from GigaVUE‑FM for details.
Task
|
Description
|
UI Steps
|
1
|
Configure one network and two tool type of ports.
|
|
1.
|
Select Ports > Ports > All Ports. |
|
2.
|
Click Quick Port Editor. |
|
3.
|
In the Quick View Editor set one port to Network and two ports to Tool. |
|
4.
|
Select Enable on each port. |
|
6.
|
Close the Quick Port Editor. |
|
2
|
Configure a GigaSMART group and associate it with a GigaSMART engine port.
|
|
1.
|
From the left navigation pane, go to System > GigaSMART >GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. |
|
4.
|
Click in the Port List field and select an engine port. |
|
5.
|
Under GTP Flow set the Timeout. The default is value is 48, which is 480 minutes. |
|
3
|
Configure the GigaSMART operation and assign it to the GigaSMART group to enable GTP correlation.
|
|
1.
|
From the left navigation pane, go to System > GigaSMART >GigaSMART Operations (GSOP > GigaSMART Operation. |
|
2.
|
Type a name for the GigaSMART Group in the Alias field. |
|
3.
|
Click in the GigaSMART Operations (GSOP) field and select Flow Filtering. |
|
4
|
Configure a virtual port and assign it to the same GigaSMART group.
|
|
1.
|
From the left navigation pane, go to System > GigaSMART >Virtual Ports. |
|
3.
|
Type a name for the virtual port in the Alias field. |
|
4.
|
Click in the GigaSMART Groups field, and select the GigaSMART Group created in Task 2. |
|
5
|
Create a first level map that directs GTP traffic from physical network port/s to the virtual port you created in the previous step.
Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic.
|
|
1.
|
Select Maps > Maps > Maps |
|
•
|
Select First Level for Type |
|
•
|
Select By Rule for Subtype |
|
•
|
Select a network port for the Source |
|
•
|
Select the virtual port configured in Task 4 for the Destination |
|
c.
|
Select Bi Directional. |
|
e.
|
Set the source to 2123 |
|
e.
|
Set the source to 2152 |
|
c.
|
Select IPv4 Fragmentation |
|
d.
|
Set Value to allFragNoFirst |
|
6
|
Create a second level map that takes traffic from the virtual port, applies the GigaSMART operation, matches IMSIs specified by the flow rule, and sends matching traffic to physical tool ports.
|
|
1.
|
Select Maps > Maps > Maps |
|
■
|
Select Second Level for Type |
|
■
|
Select Flow Filter for Subtype |
|
■
|
Select the virtual port configured in Task for the Source |
|
■
|
Select the tool port configured in Task 1 for the Destination |
|
■
|
Select the GigaSMART Operation created in Task 3 from the GSOP list. |
|
d.
|
Enter 22222222222223* in the IMSI field. |
|
7
|
Add a shared collector for any unmatched data and send it to the second tool port.
|
|
1.
|
Select Maps > Maps > Maps |
|
■
|
Select Second Level for Type |
|
■
|
Select Collector for Subtype |
|
■
|
Select a the virtual port configured in Task for the Source |
|
■
|
Select the second tool port configured in Task 1 for the Destination |
|
8
|
Display the configuration for Example 1.
|
To display the configuration for the GigaSMART Group:
|
1.
|
From the left navigation pane, go to System > GigaSMART >GigaSMART Groups. |
|
2.
|
Click on the alias for the GigaSMART Group to display the Quick View. |
To display the configuration for the GigaSMART Operation:
|
1.
|
From the left navigation pane, go to System > GigaSMART >GigaSMART Operations (GSOP) > GigaSMART Operation. |
|
2.
|
Click on the alias for the GigaSMART Operation to display the Quick View. |
To display the configuration for the maps:
|
1.
|
Select Maps > Maps > Maps. |
|
2.
|
Click on a map alias to display the Quick View for the map. |
|
Display GTP Correlation Flow Ops Report Statistics
To display GTP correlation statistics associated with the GigaSMART group, select GigaSMART > GigaSMART Operations > Statistics.
Refer to Flow Ops Report Statistics Definitions for GTP on page 635 for descriptions of these statistics.
Example 2: Identifying GTP Versions
As part of GTP correlation, GigaVUE nodes also provide the flexibility to identify GTPv1 and GTPv2 messages. GTP version information is typically exchanged only as part of the control sessions. By correlating the control and user-plane sessions, GigaVUE nodes can identify, filter, and forward all sessions specific to a GTPv1 or v2 to one or more monitoring/analytic tools.
In Example 2, EMEI traffic is distributed based on GTP versions as follows:
|
■
|
Filter and forward GTPv1 to a tool port |
|
■
|
Filter and forward GTPv2 to another tool port |
Task
|
Description
|
UI Steps
|
1
|
Configure one network and two tool type of ports.
|
|
1.
|
Select Ports > Ports > All Ports. |
|
2.
|
Click Quick Port Editor. |
|
3.
|
In the Quick View Editor set one port to Network and two ports to Tool. |
|
4.
|
Select Enable on each port. |
|
6.
|
Close the Quick Port Editor. |
|
2
|
Configure a GigaSMART group and associate it with a GigaSMART engine port.
|
|
1.
|
From the left navigation pane, go to System > GigaSMART >GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. |
|
4.
|
Click in the Port List field and select an engine port. |
|
5.
|
Under GTP Flow set the Timeout. The default is value is 48, which is 480 minutes. |
|
3
|
Configure the GigaSMART operation and assign it to the GigaSMART group to enable GTP correlation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations > GigaSMART Operation. |
|
2.
|
Type a name for the GigaSMART Group in the Alias field. |
|
3.
|
Click in the GigaSMART Operations (GSOP) field and select Flow Filtering. |
|
4
|
Configure a virtual port and assign it to the same GigaSMART group.
|
|
1.
|
From the left navigation pane, go to System > GigaSMART >Virtual Ports. |
|
3.
|
Type a name for the virtual port in the Alias field. |
|
4.
|
Click in the GigaSMART Groups field, and select the GigaSMART Group created in Task 2. |
|
5
|
Create a first level map that directs GTP traffic from physical network ports to the virtual port you created in the previous task.
Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic.
|
|
1.
|
Select Maps > Maps > Maps |
|
o
|
Select First Level for Type |
|
o
|
Select By Rule for Subtype |
|
o
|
Select a network port for the Source |
|
o
|
Select the virtual port configured int Task 4 for the Destination |
|
c.
|
Select Bi Directional. |
|
e.
|
Set the source to 2123 |
|
e.
|
Set the source to 2153 |
|
c.
|
Select IPv4 Fragmentation |
|
d.
|
Set Value to allFragNoFirst |
|
6
|
Create a second level map that takes traffic from the virtual port, applies the GigaSMART operation, matches IMEIs specified by the flow rule, and sends matching traffic to a tool port.
|
|
1.
|
Select Maps > Maps > Maps |
|
o
|
Select Second Level for Type |
|
o
|
Select Flow Filter for Subtype |
|
o
|
Select a the virtual port configured in Task for the Source |
|
o
|
Select the a tool port configured in Task 1 for the Destination |
|
o
|
Select the GigaSMART Operation created in Task 3 from the GSOP list. |
|
d.
|
Enter * in the IMSEI field and set Version to V1 |
|
7
|
Create a second level map that takes traffic from the virtual port, applies the GigaSMART operation, matches IMEIs specified by the flow rule, and sends matching traffic to another tool port.
|
|
1.
|
Select Maps > Maps > Maps |
|
o
|
Select Second Level for Type |
|
o
|
Select Flow Filter for Subtype |
|
o
|
Select a the virtual port configured in Task for the Source |
|
o
|
Select the second tool port configured in Task 1 for the Destination |
|
o
|
Select the GigaSMART Operation created in Task 3 from the GSOP list. |
|
d.
|
Enter * in the IMSI field and set Version to V2 |
|
8
|
Display the configuration for Example 2.
|
To display the configuration for the GigaSMART Group:
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > Maps. |
|
2.
|
Click on the alias for the GigaSMART Group to display the Quick View. |
To display the configuration for the GigaSMART Group:
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operations |
|
2.
|
Click on the alias for the GigaSMART Operation to display the Quick View. |
To display the configuration for the maps:
|
1.
|
Select Maps > Maps > Maps. |
|
2.
|
Click on the map alias to display the Quick View for the map. |
|
Example 3: Same Subscriber, Filter on Different Versions
In this example, traffic from the same subscriber is forwarded to two different load balancing groups based on version. GTP version 1 traffic is sent to one load balancing group and GTP version 2 traffic is sent to another load balancing group.
Task
|
Description
|
UI Steps
|
1
|
Configure one network and multiple tool type of ports.
|
|
1.
|
Select Ports > Ports > All Ports. |
|
2.
|
Click Quick Port Editor. |
|
3.
|
In the Quick View Editor set one port to Network and multiple ports to Tool. For example, set 1/2/g1 as a Network port and ports 1/2/g5 through 1/2/g9 as Tool ports. |
|
4.
|
Select Enable on each port. |
|
6.
|
Close the Quick Port Editor. |
|
2
|
Configure a GigaSMART group and associate it with a GigaSMART engine port.
|
|
1.
|
From the left navigation pane, go to System > GigaSMART >GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. |
|
4.
|
Click in the Port List field and select an engine port. |
|
3
|
Configure the GigaSMART operation and assign it to the GigaSMART group.
|
|
1.
|
From the left navigation pane, go to System > GigaSMART >GigaSMART Operations > GigaSMART Operations. |
|
2.
|
Type a name for the GigaSMART Group in the Alias field. |
|
3.
|
Click in the GigaSMART Operations field and select Flow Filtering. |
|
4.
|
Click in the GigaSMART Operations filed and select Load Balancing. |
|
5.
|
Configure the Load Balancing as follows:. |
|
4
|
Configure a virtual port and assign it to the GigaSMART group.
|
|
1.
|
From the left navigation pane, go to System > GigaSMART >Virtual Ports. |
|
3.
|
Type a name for the virtual port in the Alias field. |
|
4.
|
Click in the GigaSMART Groups field, and select the GigaSMART Group created in Task 2. |
|
5
|
Create two port groups (one for version 1 traffic and one for version 2 traffic) and enable load balancing on the port groups.
|
|
1.
|
Select Ports > Port Groups > All Port Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. For example, pglbv1. |
|
4.
|
Select SMART Load Balancing to enable load balancing |
|
5.
|
Click in the Ports field and select half the tool ports configured in Task 1. |
|
6.
|
Repeat steps 2 through 4, creating a second port group with the other ports configured in Task 1 |
|
6
|
Create an ingress (first level) map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
o
|
Enter an alias. For example, map1_1. |
|
o
|
Select First Level for Type |
|
o
|
Select By Rule for Subtype |
|
o
|
Select a network port for the Source |
|
o
|
Select the virtual port configured in Task 4 for the Destination |
|
4.
|
Click Add a Rule to create a rule. |
|
o
|
Enter a MAC address. For example, 00:a0:d1:e1:02:01 |
|
o
|
Enter a MAC mask. For example, 0000.0000.0000 |
|
7
|
Create a second level map for version1.
|
|
1.
|
Select Maps > Maps > Maps. |
|
o
|
Enter an alias. For example, map2_1. |
|
o
|
Select Second Level for Type |
|
o
|
Select Flow Filter for Subtype |
|
o
|
Select the virtual port configured in Task 4 for the Source |
|
o
|
Select the first port group for Destination |
|
o
|
Select the GigaSMART Operation configured in Task 3 from the GSOP list. |
|
4.
|
Click Add a Rule to create a rule. |
|
o
|
Enter * in the IMSI field |
|
8
|
Create another second level map for version2.
|
|
1.
|
Select Maps > Maps > Maps. |
|
o
|
Enter an alias. For example, map2_2. |
|
o
|
Select Second Level for Type |
|
o
|
Select Flow Filter for Subtype |
|
o
|
Select the virtual port configured in Task 4 for the Source |
|
o
|
Select the second port group for Destination |
|
o
|
Select the GigaSMART Operation configured in Task 3 from the GSOP list. |
|
4.
|
Click Add a Rule to create a rule. |
|
o
|
Enter * in the IMSI field |
|
Example 4: Same Subscriber, Filter on Different Interfaces
In this example, traffic from the same subscriber is forwarded to two different load balancing groups based on interface. In this example, VLANs 1601 and 1602 are from S5/S8 interface and VLANs 1611 and 1612 are from S11/S1-U interface. The first level maps split the VLAN traffic to different virtual ports. The second level maps send the traffic to different load balancing groups.
Task
|
Description
|
UI Steps
|
1
|
Configure one network and multiple tool type of ports.
|
|
1.
|
Select Ports > Ports > All Ports. |
|
2.
|
Click Quick Port Editor. |
|
3.
|
In the Quick View Editor set one port to Network and multiple ports to Tool. For example, set 1/2/g1 as a Network port and ports 1/2/g5 through 1/2/g9 as Tool ports. |
|
4.
|
Select Enable on each port. |
|
6.
|
Close the Quick Port Editor. |
|
2
|
Configure a GigaSMART group and associate it with a GigaSMART engine port.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. |
|
4.
|
Click in the Port List field and select an engine port. |
|
3
|
Configure the GigaSMART operation and assign it to the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations > GigaSMART Operations. |
|
2.
|
Type a name for the GigaSMART Group in the Alias field. |
|
3.
|
Click in the GigaSMART Operations field and select Flow Filtering. |
|
4.
|
Click in the GigaSMART Operations filed and select Load Balancing. |
|
5.
|
Configure Load Balancing as follows: |
|
4
|
Configure virtual ports and associate them with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports. |
|
3.
|
Type a name for the virtual port in the Alias field. |
|
4.
|
Click in the GigaSMART Groups field, and select the GigaSMART Group created in Task 2. |
|
6.
|
Repeat steps 1 through 5 to create a second virtual port. |
|
5
|
Repeat task 4 to create another virtual port.
|
|
6
|
Create two port groups (one for version 1 traffic and one for version 2 traffic) and enable load balancing on the port groups.
|
|
1.
|
Select Ports > Port Groups > All Port Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. For example, pglbv1. |
|
4.
|
Select SMART Load Balancing to enable load balancing |
|
5.
|
Click in the Ports field and select half the tool ports configured in Task 1. |
|
6.
|
Repeat steps 2 through 4, creating a second port group with the other ports configured in Task 1 |
|
7
|
Create a first level map for vport1.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Enter an alias. For example, map1_1. |
|
■
|
Select First Level for Type |
|
■
|
Select By Rule for Subtype |
|
■
|
Select a network port for the Source |
|
■
|
Select the first virtual port configured in Task 4 for the Destination |
|
4.
|
Click Add a Rule to create a rule. |
|
■
|
Enter 1601 for the Min value |
|
■
|
Enter 1602 for the Max value |
|
8
|
Create another first level map for vport2.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Enter an alias. For example, map1_2. |
|
■
|
Select First Level for Type |
|
■
|
Select By Rule for Subtype |
|
■
|
Select a network port for the Source |
|
■
|
Select the second virtual port configured in Task 5 for the Destination |
|
4.
|
Click Add a Rule to create a rule. |
|
■
|
Enter 1611 for the Min value |
|
■
|
Enter 1611 for the Max value |
|
9
|
Create a second level map using vport1.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Enter an alias. For example, map2_1. |
|
■
|
Select Second Level for Type |
|
■
|
Select Flow Filter for Subtype |
|
■
|
Select the virtual port configured in Task 4 for the Source |
|
■
|
Select the first port group for Destination |
|
■
|
Select the GigaSMART Operation configured in Task 3 from the GSOP list. |
|
4.
|
Click Add a Rule to create a rule. |
|
■
|
Enter * in the IMSI field |
|
10
|
Create another second level map using vport2.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Enter an alias. For example, map2_2. |
|
■
|
Select Second Level for Type |
|
■
|
Select Flow Filter for Subtype |
|
■
|
Select the second virtual port configured in Task 5 for the Source |
|
■
|
Select the second port group for Destination |
|
■
|
Select the GigaSMART Operation configured in Task 3 from the GSOP list. |
|
4.
|
Click Add a Rule to create a rule. |
|
■
|
Enter * in the IMSI field |
|
Example 5: EPC Filtering in Scenario1
In this example, traffic for all subscribers on interfaces S11/S1-U and Gn/Gp is sent to the same load balancing group. All other traffic is dropped.
Task
|
Description
|
UI Steps
|
1
|
Configure one network and two tool type of ports.
|
|
1.
|
Select Ports > Ports > All Ports. |
|
2.
|
Click Quick Port Editor. |
|
3.
|
In the Quick View Editor set one port to Network and two ports to Tool. For example, set 1/2/g1 as a Network port and ports 1/2/g5 and 1/2/g6 as Tool ports. |
|
4.
|
Select Enable on each port. |
|
6.
|
Close the Quick Port Editor. |
|
2
|
Configure a GigaSMART group and associate it with a GigaSMART engine port.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. |
|
4.
|
Click in the Port List field and select an engine port. |
|
3
|
Configure the GigaSMART operation and assign it to the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation. |
|
2.
|
Type a name for the GigaSMART Group in the Alias field. |
|
3.
|
Click in the GigaSMART Operations field and select Flow Filtering. |
|
4.
|
Click in the GigaSMART Operations (GSOP) field and select Load Balancing. |
|
5.
|
Configure the Load Balancing as follows. |
|
4
|
Configure a virtual port and assign it to the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports. |
|
3.
|
Type a name for the virtual port in the Alias field. |
|
4.
|
Click in the GigaSMART Groups field, and select the GigaSMART Group created in Task 2. |
|
5
|
Create a port group enable load balancing on the port group.
|
|
1.
|
Select Ports > Port Groups > All Port Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. For example, pglbv1. |
|
4.
|
Select SMART Load Balancing to enable load balancing |
|
6
|
Create an ingress (first level) map.
Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic.
|
|
1.
|
Select Maps > Maps > Maps |
|
■
|
Select First Level for Type |
|
■
|
Select By Rule for Subtype |
|
■
|
Select a network port for the Source |
|
■
|
Select the virtual port configured int Task 4 for the Destination |
|
c.
|
Select Bi Directional. |
|
e.
|
Set the source to 2123 |
|
e.
|
Set the source to 2152 |
|
7
|
Create a second level map that takes traffic from the virtual port, applies the GigaSMART operation, matches IMSIs specified by the flow rules, and sends matching traffic to physical tool ports.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Select Second Level for Type |
|
■
|
Select Flow Filter for Subtype |
|
■
|
Select the virtual port configured in Task 4 for the Source |
|
■
|
Select the port group for Destination |
|
■
|
Select the GigaSMART Operation configured in Task 3 from the GSOP list. |
|
d.
|
Enter * in the IMSI field |
|
e.
|
Select Interface and set it to Gg/Gp |
|
d.
|
Enter * in the IMSI field |
|
e.
|
Select Interface and set it to S11/S1U |
|
Example 6: EPC Filtering in Scenario2
In this example, traffic for all subscribers from all interfaces except S5/S8 is sent to the same load balancing group. Traffic from the S5/S8 interface is dropped.
Step
|
Description
|
UI Steps
|
1
|
Configure one network and two tool type of ports.
|
|
1.
|
Select Ports > Ports > All Ports. |
|
2.
|
Click Quick Port Editor. |
|
3.
|
In the Quick View Editor set one port to Network and two ports to Tool. For example, set 1/2/g1 as a Network port and ports 1/2/g5 and 1/2/g6 as Tool ports. |
|
4.
|
Select Enable on each port. |
|
6.
|
Close the Quick Port Editor. |
|
2
|
Configure a GigaSMART group and associate it with a GigaSMART engine port.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. |
|
4.
|
Click in the Port List field and select an engine port. |
|
3
|
Configure the GigaSMART operation and assign it to the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation. |
|
2.
|
Type a name for the GigaSMART Group in the Alias field. |
|
3.
|
Click in the GigaSMART Operations (GSOP) field and select Flow Filtering. |
|
4.
|
Click in the GigaSMART Operations (GSOP) field and select Load Balancing. |
|
5.
|
Configure Load Balancing as follows: |
|
4
|
Configure a virtual port and assign it to the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports. |
|
3.
|
Type a name for the virtual port in the Alias field. |
|
4.
|
Click in the GigaSMART Groups field, and select the GigaSMART Group created in Task 2. |
|
5
|
Create a port group and enable load balancing on the port group.
|
|
1.
|
Select Ports > Port Groups > All Port Groups. |
|
3.
|
Type a name for the GigaSMART Group in the Alias field. For example, pglbv1. |
|
4.
|
Select SMART Load Balancing to enable load balancing |
|
6
|
Create an ingress (first level) map.
Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic.
|
|
1.
|
Select Maps > Maps > Maps |
|
■
|
Select First Level for Type |
|
■
|
Select By Rule for Subtype |
|
■
|
Select a network port for the Source |
|
■
|
Select the virtual port configured int Task 4 for the Destination |
|
c.
|
Select Bi Directional. |
|
e.
|
Set the source to 2123 |
|
e.
|
Set the source to 2152 |
|
7
|
Create a second level map that takes traffic from the virtual port, applies the GigaSMART operation, matches IMSIs specified by the flow rules, and sends matching traffic to physical tool ports.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Select Second Level for Type |
|
■
|
Select Flow Filter for Subtype |
|
■
|
Select the virtual port configured in Task 4 for the Source |
|
■
|
Select the port group for Destination |
|
■
|
Select the GigaSMART Operation configured in Task 3 from the GSOP list. |
|
d.
|
Enter * in the IMSI field |
|
e.
|
Select Interface and set it to S5/S8 |
|
d.
|
Enter * in the IMSI field |
|
|
|