1
|
Configure ports on the GigaVUE‑HC3 as follows:
|
■
|
One network type of port. This will be used as the Source attribute in two first level maps in Task 11 and Task 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 Task 6. |
|
■
|
Five tool type of ports for a GigaStream that will be created in Task 2. |
|
■
|
Two tool type of ports for another GigaStream that will be created in Task 2. |
Then administratively enable the ports.
|
|
1.
|
On the GigaVUE‑HC3, select Ports > Ports > All Ports |
|
2.
|
Click Quick Port Editor. |
|
3.
|
Configure one network port for Task 11 and Task 12. For example, 23/2/c3. |
|
4.
|
Configure 12 tool ports for three port groups in Task 6. For example, 23/3/x1..x4 for the first port group, 23/3/x9..x12 for the second tool group, and 23/3/x13..x16 for the third port group. |
|
5.
|
Configure five tool ports for a GigaStream in Task 2. For example, 23/3/x20..x24. |
|
6.
|
Configure two tool ports for another GigaStream in Task 2. For example, 23/2/c1..c2 type tool. |
|
7.
|
Select enable for each port. |
|
9.
|
Close the Quick Port Editor. |
|
2
|
On the GigaVUE‑HC3, configure one GigaStream using five tool ports. This will be used as the Destination attribute in the map in Task 11.
Configure another GigaStream to be used in the stack link between the GigaVUE‑HC3 and GigaVUE‑HC2 that will be created in Task 4.
|
|
1.
|
Select Ports > Port Groups > GigaStreams |
|
2.
|
Configure a GigaStream with five tool ports. |
|
b.
|
Type hc3-gs-1 in the Alias field. |
|
c.
|
Select Tool GigaStream. |
|
d.
|
Click in the Ports field and select the five tool ports configured in Task 1. |
|
e.
|
Click Advanced Hash Settings and use the Default setting. |
|
7.
|
Configure another GigaStream with two tool ports. |
|
b.
|
Type hc3-80g in the Alias field. |
|
c.
|
Select Tool GigaStream. |
|
d.
|
Click in the Ports field and select the two tool ports configured in Task 1. |
|
e.
|
Click Advanced Hash Settings and use the Default setting. |
|
3
|
Configure ports on the GigaVUE‑HC2 as follows:
|
■
|
Two tool type of ports for a GigaStream that will be created in Task 4. |
|
■
|
One tool type of port that will be used as the Destination in a map in Task 11. |
|
■
|
Four tool type of ports for a GigaStream that will be created in Task 4. |
Then administratively enable the ports.
|
|
1.
|
On the GigaVUE‑HC2, select Ports > Ports > All Ports |
|
2.
|
Click Quick Port Editor. |
|
3.
|
Configure two tool ports for a GigaStream in Task 4. For example, 33/2/q1..q2 |
|
4.
|
Configure one tool ports for the map in Task 11. For example, 33/3/x11. |
|
5.
|
Configure four tool ports for a GigaStream in Task 4. For example, 33/2/x20..x24. |
|
6.
|
Select Enable for each port. |
|
8.
|
Close the Quick Port Editor. |
|
4
|
On the GigaVUE‑HC2, configure a GigaStream using two tool ports. This will be used in the stack link created in Task 5.
Configure another GigaStream using four tool ports. This will be used in the shared collector in Task 17.
|
|
1.
|
Select Ports > Port Groups > GigaStreams |
|
2.
|
Configure a GigaStream with five tool ports. |
|
b.
|
Type hc2-gs-4 in the Alias field. |
|
c.
|
Select Tool GigaStream. |
|
d.
|
Click in the Ports field and select the five tool ports configured in Task 1. For example, 33/2/x20..x25. |
|
e.
|
Click Advanced Hash Settings and use the Default setting. |
|
7.
|
Configure another GigaStream with two tool ports. |
|
b.
|
Type hc3-80g in the Alias field. |
|
c.
|
Select Tool GigaStream. |
|
d.
|
Click in the Ports field and select the two tool ports configured in Task 1. For example, 33/2/q1..q2. |
|
e.
|
Click Advanced Hash Settings and use the Default setting. |
|
5
|
Configure the stack link between the GigaVUE‑HC2 and GigaVUE‑HC3.
|
|
1.
|
Select Ports > Port Groups > Stack Links |
|
3.
|
Select Stack GigaStream. |
|
4.
|
For First Member select hc3-80g. |
|
5.
|
For Second Member select hc2-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 Destination in two second level flow sampling maps in Task 14 and Task 15.
The port group, hc3-q2x32-1-4, will be used as the Destination in a second level flow filtering map in Task 16
|
|
1.
|
Select Ports > Port Groups > All Port Groups. |
|
2.
|
Create the first port group. |
|
b.
|
Type hc3-pg-1 in the Alias field. |
|
c.
|
Select SMART Load Balancing. |
|
d.
|
Click in the Ports field and select four tool ports. For example, 23/4/x9..x12. |
|
6.
|
Create the second port group. |
|
b.
|
Type hc3-pg-1 in the Alias field. |
|
c.
|
Select SMART Load Balancing. |
|
d.
|
Click in the Ports field and select four tool ports. For example, 23/4/x13..x16 |
|
6.
|
Create the second port group. |
|
b.
|
Type hc3-q2x32-1-4 in the Alias field. |
|
c.
|
Select SMART Load Balancing. |
|
d.
|
Click in the Ports field and select four tool ports. For example, 23/4/x13..x16 |
|
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 Task 8, Task 9, and Task 10.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type hc3scale-4engines-slots1and3. |
|
4.
|
Click in the Port List and select the engine ports. For example, 3/1/e1,23/1/e2,23/3/e1,23/3/e2. |
Go to Task 8.
|
8
|
Associate the GigaSMART group to an existing GTP forward list.
Note: The forward list is only supported on the cluster leader, which is the GigaVUE‑HC3 in this example.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
2.
|
Under GTP Whitelist, select the alias of an existing forward list. For example, gtp-whitelist. |
|
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 Task 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 Task 15 and Task 16.
For GTP forward listing, configure a whitelisting GigaSMART operation, and assign the GigaSMART operation to the GigaSMART group. (This GigaSMART operation is not load balanced.) The hc3-scale-wl gsop will be used in the second level forward listing map in Task 13.
|
|
1.
|
Configure a Flow Filtering operation. |
|
a.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation. |
|
c.
|
Type hc3-scale-ff-lb in the Alias field. |
|
d.
|
Select hc3scale-4engines-slots1and3 from the GigaSMART Groups list. |
|
e.
|
Select Flow Filtering from the GigaSMART Operations (GSOP) list. |
|
7.
|
Configure a Flow Sampling operation. |
|
a.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation. |
|
c.
|
Type hc3-scale-fs-lb in the Alias field. |
|
d.
|
Select hc3scale-4engines-slots1and3 from the GigaSMART Groups list. |
|
e.
|
Select Flow Sampling from the GigaSMART Operations (GSOP) list. |
|
f.
|
Select Flow Sampling -GTP |
|
8.
|
Configure a Forward listing operation. |
|
a.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation. |
|
c.
|
Type hc3-scale-wl in the Alias field. |
|
d.
|
Select hc3scale-4engines-slots1and3 from the GigaSMART Groups list. |
|
e.
|
Select GTP Whitelist from the GigaSMART Operations (GSOP) list. |
|
f.
|
Select Enabled (default). |
|
10
|
Configure a virtual port and assign it to the same GigaSMART group. This virtual port will be used as the Destination in the first level maps in Task 11 and Task 12, as the Source in the second level maps in Task 13, Task 14, Task 15, Task 16, and as the Source in the shared collector in Task 17.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports |
|
3.
|
Type vp-hc3scale-4engines-slots1and3 in the Alias field. |
|
4.
|
Select hc3scale-4engines-slots1and3 from the GigaSMART Groups list. |
|
11
|
Create a first level map that directs GTP control traffic from the physical network port to the virtual port created in Task 10.
Note: In the rule, 2123 is GTP-c traffic.
This map, with the Control Traffic enabled, identifies the GTP-c control traffic needed for GTP engine grouping.
In addition to the virtual port, traffic is also sent to a GigaStream and a tool port.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Type to_hc3_gtpc in the Alias field |
|
■
|
Select First Level for Type. |
|
■
|
Select By Rule for Subtype |
|
■
|
Select a network port for the Source. For example, 23/3/q6. |
|
■
|
Select the GigaStream port hc3-gs-1, the virtual port p-hc3scale-4engines-slots1and3, and a tool port (for example, 23/7/q6) for the Destination. |
|
b.
|
Select Pass and Bi Directional. |
|
c.
|
Select Port Destination for the rule. |
|
d.
|
Enter 2123 for the port value. |
|
12
|
Create another first level map that directs GTP user traffic from the physical network port to the virtual port created in Task 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.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Type to_hc3_gtpu_1 in the Alias field |
|
■
|
Select First Level for Type. |
|
■
|
Select By Rule for Subtype |
|
■
|
Select a network port for the Source. For example, 23/7/q6. |
|
■
|
Select the virtual port vp-hc3scale-4engines-slots1and3 for the Destination. |
|
b.
|
Select Pass and Bi Directional. |
|
c.
|
Select Port Destination for the rule. |
|
d.
|
Enter 2152for the port value. |
|
c.
|
Select IPv4 Fragmentation for the rule. |
|
d.
|
Enter 2152for the port value. |
|
e.
|
Select allFragNoFirst for Value. |
|
13
|
Configure a second level map for GTP whitelisting, the forward list map, that takes traffic from the virtual port, applies the forward listing GigaSMART operation, and sends traffic to the remote GigaVUE‑HC2 node through a GigaStream.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Type from_hc3_wl in the Alias field |
|
■
|
Select Second Level for Type. |
|
■
|
Select By Rule for Subtype |
|
■
|
Select the virtual port vp-hc3scale-4engines-slots1and3 for the Source. |
|
■
|
Select the GigaStream hc2-gs-1 for the Destination. |
|
■
|
Select hc3-scale-wl from the GSOP list. |
|
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.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Type from_hc3_fs_v2 in the Alias field |
|
■
|
Select Second Level for Type. |
|
■
|
Select Flow Sample for Subtype |
|
■
|
Select the virtual port vp-hc3scale-4engines-slots1and3 for the Source. |
|
■
|
Select the port group hc3-pg-2 for the Destination. |
|
■
|
Select hc3-scale-fs-lb from the GSOP list. |
|
c.
|
Enter 60 for Percentage. |
|
d.
|
Enter 5* in the IMSI field. |
|
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.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Type from_hc3_fs_v1 in the Alias field |
|
■
|
Select Second Level for Type. |
|
■
|
Select Flow Sample for Subtype |
|
■
|
Select the virtual port vp-hc3scale-4engines-slots1and3 for the Source. |
|
■
|
Select the port group hc3-pg-1 for the Destination. |
|
■
|
Select hc3-scale-fs-lb from the GSOP list. |
|
c.
|
Enter 60 for Percentage. |
|
d.
|
Enter 5* in the IMSI field. |
|
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-q2x32-1-4.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Type from_hc3_ff in the Alias field |
|
■
|
Select Second Level for Type. |
|
■
|
Select Flow Filter for Subtype |
|
■
|
Select the virtual port vp-hc3scale-4engines-slots1and3 for the Source. |
|
■
|
Select the port group hc3-pg-1 for the Destination. |
|
■
|
Select port group hc3-q2x32-1-4 from the GSOP list. |
|
c.
|
Enter * in the IMSI field. |
|
d.
|
Select Any for Version |
|
17
|
Add a shared collector for any unmatched traffic from the virtual port and send it to a GigaStream.
|
|
1.
|
Select Maps > Maps > Maps. |
|
■
|
Type s_coll_hc3 in the Alias field |
|
■
|
Select Second Level for Type. |
|
■
|
Select Collector for Subtype |
|
■
|
Select the virtual port vp-hc3scale-4engines-slots1and3 for the Source. |
|
■
|
Select GigaStream hc2-gs-4 for the Destination. |
|