GigaSMART Load Balancing

GigaSMART Load Balancing does not require a separate license.
Stateless Load Balancing is included with Base licenses.
Stateful Load Balancing for GTP is included with the GTP Filtering & Correlation license.
Stateful Load Balancing for ASF is included with the Application Session Filtering (ASF) license.
Stateful Load Balancing for tunnel is included with the Advanced Tunneling license (GigaVUE-HD4, GigaVUE-HD8, GigaVUE-HC2, and GigaVUE-HC3), and Tunneling license (GigaVUE-HC1 and GigaVUE-HB1)

Load balancing distributes GigaSMART outgoing traffic to multiple tool ports or multiple tunnel endpoint destinations. In this way, traffic processed by GigaSMART is shared.

Stateful load balancing distributes GigaSMART processed traffic to multiple tool ports or tunnel endpoints based on GigaSMART application-specific flow sessions. Stateless load balancing distributes GigaSMART processed traffic to multiple tool ports or tunnel endpoints based on hash values generated from predefined protocol fields in the packet.

Load balancing operations to tool ports can be assigned to GigaSMART groups consisting of multiple engine ports. Refer to Groups of GigaSMART Engine Ports for details.

The following sections describe the available load balancing schemes:

• Stateful Load Balancing
• Stateless Load Balancing
• Enhanced Load Balancing

Stateful Load Balancing

Stateful load balancing distributes GigaSMART processed traffic to multiple tool ports or tunnel endpoints based on GigaSMART application-specific flow sessions.

With stateful load balancing, packets belonging to the same flow session maintained by GigaSMART applications are forwarded to the same tool port or tunnel endpoint within a port group.

Use the GigaSMART Operations (GSOP) page to configure load balancing. Specify one stateful application within a group of GigaSMART operations and specify a load balancing metric.

GTP, Application Session Filtering (ASF), and tunnel are the currently supported stateful applications.

For information on GTP, refer to GigaSMART GTP Correlation.

For information on ASF, refer to GigaSMART Application Session Filtering (ASF) and Buffer ASF (deprecated).

For information on Layer 2 GRE tunnel encapsulation, refer to GigaSMART Layer 2 GRE Tunnel Encapsulation/Decapsulation.

For details on stateful load balancing, refer to the following sections:

• Stateful Load Balancing Metrics
• Hashing Key Support
• Configuring Stateful Load Balancing

To select stateful load balancing, do the following:

1.   From the device view, select GigaSMART > GigaSMART Operations (GSOP), and then click New.
2. Specify an alias in the Alias field.
3. Click in the GigaSMART Group field and select a GigaSMART Group.
4. Click in the GigaSMART Operations (GSOP) field and select Load Balancing from the drop-down list.
5. Select Stateful.
6. For Type, select one stateful application within a group of GigaSMART operations.

GTP, ASF, and Tunnel are the currently supported stateful applications.

7. Specify a load balancing metric. For example, Hashing as shown in Figure 825: Configuring Stateful Load Balancing.

 

Figure 825: Configuring Stateful Load Balancing

Stateful Load Balancing Metrics

The load balancing metrics available for stateful load balancing are described in the following table.

For weighted metrics, such as Weighted Least Bandwidth, you can either define a weight for each port such as 5,10, 25, 50, or you can use link speed: 1 for 1Gb, 10 for 10Gb, 40 for 40Gb, 100 for 100Gb. Use the Port Groups configuration page to select weight and use the Port configuration page to select link speed.

Note:  Only the traffic from the stateful application (for example, GTP, ASF, or tunnel) is used to perform load balancing. Other traffic in the map that does not match the application's filter rule is excluded.

Metric

Description

Least Bandwidth

A tool port is selected from a port group based on the least bits per second load to the port.

To compensate for bursty traffic, the history of the last 10 second bandwidth is considered on the load balancing decision.

This metric is not supported for tunnel.

Weighted Least Bandwidth

A tool port is selected from a port group based on the least bits per second load to the port, as described under Least Bandwidth.

This metric is not supported for tunnel.

If the following command is enabled, link speed is considered in addition to the bandwidth of the port. If the following command is disabled, the weight configured for each port in the port group is considered in addition to the bandwidth of the port.

Least Packet Rate

A tool port is selected from a port group based on Least Packet Rate.

To compensate for bursty traffic, the history of the last 10 second packet count is considered on the load balancing decision.

Weighted Least Packet Rate

A tool port is selected from a port group based on Least Packet Rate, as described under Least Packet Rate.

With Weighted Least Packet Rate, if a port has a higher weight, it will be sent more traffic.

If the following command is enabled, link speed is considered with packet rate. If the following command is disabled, the weight configured for each port in the port group is considered with packet rate.

Round Robin

A tool port is selected from a port group based on round robin.

Weighted Round Robin

A tool port is selected from a port group based on least packet rate, as described under Round Robin.

If the following command is enabled, link speed is considered with Round Robin. If the following command is disabled, the weight configured for each port in the port group is considered with Round Robin.

Least Connection

A tool port is selected from a port group based on the current Least Connection assigned to each tool port. The port with the least number of connections assigned is selected.

Note:  The meaning of connection is defined by the application.

Weighted Least Connection

A tool port is selected from a port group based on the current Least Connection assigned to each tool port, as described under Least Connection.

If the following command is enabled, link speed is considered with Least Connection. If the following command is disabled, the weight configured for each port in the port group is considered with Least Connection.

Note:  The meaning of connection is defined by the application.

Least Cumulative Traffic

A tool port is selected from a port group based on the least total bytes sent to each tool port. The port with the least number of connections assigned is selected.

Note:  The meaning of connection is defined by the application.

Weighted Least Cumulative Traffic

A tool port is selected from a port group based on the least total bytes sent to each tool port, as described under Least Cumulative Traffic.

If the following command is enabled, link speed is considered with least cumulative traffic. If the following command is disabled, the weight configured for each port in the port group is considered with Least Cumulative Traffic.

Hashing

A tool port is selected from a port list based on hashing of data provided by the GSOP application, which is normally extracted from the packet.

The values for hashing key are: IMSI GTP key (imsi), IMEI GTP key (imei), and MSISDN GTP key (msisdn). The hashing key only applies to the GTP stateful application. Refer to Hashing Key Support on page 672 for details.
Hashing Key Support

The following table describes the support for GTP hashing key.

GTP Key

Hashing

(Weighted) Least Bandwidth

(Weighted) Least Packet Rate

(Weighted) Least Round Robin

(Weighted) Least Connection

(Weighted) Least Cumulative Traffic

IMSI

Supported

Supported

Supported

Supported

Supported

Supported

IMEI

Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported

MSISDN

Supported

Not Supported

Not Supported

Not Supported

Not Supported

Not Supported
Configuring Stateful Load Balancing

Use the Port Group page to specify the list of tool ports or tunnel endpoints for stateful load balancing and to enable load balancing in a port group.

To enable load balancing in a port group, do the following:

1.   Select Ports > Port Groups > All Port Groups.
2. Click New.
3. In the Alias filed, enter an alias. For example, load-balgrp.
4. Select SMART Load Balancing.
5. Use the Ports field to select the ports for this port group as shown in Figure 826: Port Group Page to Set Ports for Load Balancing. Click Save when you are done.

 

Figure 826: Port Group Page to Set Ports for Load Balancing

NOTES:x

• Up to 50 load balancing port groups are supported, with a maximum of 256 ports for each group.
• Ports within port groups must be on the same chassis.
• Ports within port groups can have different rates.

Refer to the following examples:

• Example 1: GigaSMART Stateful Load Balancing
• Example 2: GigaSMART Stateful Load Balancing

For an example of load balancing on L2GRE encapsulation tunnel, refer to Example 2 – GigaSMART L2GRE Tunnel Encap Stateful LB.

Example 1: GigaSMART Stateful Load Balancing

Example 1 configures stateful load balancing of GigaSMART GTP traffic among tool ports 1/1/x6, 1/1/x7, 1/2/x3, and 1/2/x4 based on bandwidth with different weights for each port. The same subscriber (imsi) traffic will be forwarded to the same tool port. GTP-c packets are replicated to all tool ports.

 

Task

Description

UI Steps
1.    

Create a port group, specify the tool ports for load balancing, and weights for each tool port.
a. Select Ports > Port Groups.
b. Click New
c. Type portgrp1 in the Alias field.
d. Select SMART Load Balancing
e. Click in the Ports field to select the tool ports for the group. For example, 1/1/x6,1/1/x7,1/2/x3, and 1/2/x4.
f. Specify the weights for each port as follows:

weight 1/1/x6 5

weight 1/1/x7 10

weight 1/2/x3 20

weight 1/2/x4 10

g. Click Save.
2.  

Create a GigaSMART group and specify a port and enable replicate GTP-c packets to all tool ports in the load balancing port group.
a. From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups.
b. Click New.
c. Type gsgrp1 in the Alias field.
d. Select the engine port. For example 1/3/e1.
e. Under the Load Balance, select Replicate GTP-c.
f. Click Save.
3.  

Create a GSOP, including GTP application and load balancing metric.
a. From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation.
b. Click New.
c. Type gsop1 in the Alias field
d. Select gsgrp1 from the GigaSMART Groups list.
e. Select the GigaSMART Operation Flow Filtering
f. Select the GigaSMART Operation Load Balancing and set the operation as follows:
- Select Stateful.
- Select GTP for Type.
- Select Weighted Least Bandwidth for the metric.
4.  

Create a virtual port and associate it with the GigaSMART group.
a. From the device view, select GigaSMART > GigaSMART Operations (GSOP) > Virtual Ports.
b. Click New.
c. Type vp1 in the Alias field.
d. Select gsgrp1 from the GigaSMART Group list.
e. Click Save.
5.  

Create an ingress (first level) map.

Note the following:

• You can specify only one port group as part of the map tool port in the to statement.
• You can define the same load balancing port group in multiple maps, however, the load balancing metrics defined in the GSOPs on those maps have to be the same.
• You cannot use a shared collector map for load balancing.

Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic.
a. Select Maps > Maps > Maps.
b. Click New.
c. Type map11 in the Alias field.
d. Select First Level for Type and By Rule for Subtype.
e. Select port 1/1/x1 for the Source.
f. Select virtual port vp1 for the Destination.
g. Add Rule 1.
- Click Add a Rule
- Select Pass
- Select Port Destination for the condition.
- Set the port value to 2123.
h. Add Rule 2.
- Click Add a Rule
- Select Pass
- Select Port Destination for the condition.
- Set the port value to 2125.
i. Click Save.
6.  

Create a second level map.
a. Select Maps > Maps > Maps.
b. Click New.
c. Type map22 in the Alias field.
d. Select Second Level for Type and By Rule for Flow Filter.
e. Select virtual port vp1 for the Source.
f. Select port group portgrp1 for the Destination.
g. Select gsop1 from the GSOP list.
h. Click Add a Rule
- Select Pass
- Select GTP IMSI for the condition.
- Enter 234567* for IMSI.
- Select Any for Version.
i. Click Save.
Example 2: GigaSMART Stateful Load Balancing

Example 2 configures stateful load balancing of GigaSMART GTP traffic among tool ports 1/1/x6, 1/1/x7, 1/2/x3, and 1/2/x4 based on hashing of the imei value. The same device ID (imei) traffic will be forwarded to the same tool port. GTP-c packets are replicated to all tool ports.

 

Step

Description

Command
1.    

Create a port group and specify the tool ports for load balancing.
a. Select Ports > Port Groups.
b. Click New
c. Type portgrp1 in the Alias field.
d. Select SMART Load Balancing
e. Click in the Ports field to select the tool ports for the group. For example, 1/1/x6,1/1/x7,1/2/x3, and 1/2/x4.
f. Click Save.
2.  

Create a GigaSMART group and specify ports and enable replicate GTP-c packets to all tool ports in the load balancing port group.
a. From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups.
b. Click New.
c. Type gsgrp1 in the Alias field.
d. Select the engine port. For example 1/3/e1.
e. Under the Load Balance, select Replicate GTP-c.
f. Click Save.
3.  

Create a GSOP, including GTP application and load balancing metric.
a. From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operations.
b. Click New.
c. Type gsop1 in the Alias field
d. Select gsgrp1 from the GigaSMART Groups list.
e. Select the GigaSMART Operation Flow Filtering
f. Select the GigaSMART Operation Load Balancing.
g. Configure Load Balancing as follows:
- Select Stateful.
- Select GTP for Type.
- Select Hashing for the metric.
- Select IMEI
h. Click Save.
4.  

Create a virtual port and associate it with the GigaSMART group.
a. From the device view, select GigaSMART > GigaSMART Operations (GSOP) > Virtual Ports.
b. Click New.
c. Type vp1 in the Alias field.
d. Select gsgrp1 from the GigaSMART Groups list.
e. Click Save.
5.  

Create an ingress (first level) map.

Note the following:

• You can specify only one port group as part of the map tool port in the to statement.
• You can define the same load balancing port group in multiple maps, however, the load balancing metrics defined in the GSOPs on those maps have to be the same.
• You cannot use a shared collector map for load balancing.

Note: In the rules, 2123 is GTP-c traffic and 2152 is GTP-u traffic.
a. Select Maps > Maps > Maps.
b. Click New.
c. Type map11 in the Alias field.
d. Select First Level for Type and By Rule for Subtype.
e. Select port 1/1/x1 for the Source.
f. Select virtual port vp1 for the Destination.
g. Add Rule 1.
- Click Add a Rule
- Select Pass
- Select Port Destination for the condition.
- Set the port value to 2123.
h. Add Rule 2.
- Click Add a Rule
- Select Pass
- Select Port Destination for the condition.
- Set the port value to 2125.
i. Click Save.
6.  

Create a second level map.
a. Select Maps > Maps > Maps.
b. Click New.
c. Type map22 in the Alias field.
d. Select Second Level for Type and By Rule for Flow Filter.
e. Select virtual port vp1 for the Source.
f. Select port group portgrp1 for the Destination.
g. Select gsop1 from the GSOP list.
h. Click Add a Rule
- Select Pass
- Select GTP IMSI for the condition.
- Enter 234567* for IMSI.
- Select Any for Version.
i. Click Save.

Stateless Load Balancing

Stateless load balancing distributes GigaSMART processed traffic to multiple tools based on predefined protocol fields in the packet.

Unlike stateful load balancing, stateless load balancing can be configured together with most other GigaSMART operations or as a separate GigaSMART operation to provide more flexible traffic distribution options over what is available from a tool GigaStream. Packets processed by stateless load balancing are forwarded to a tool port within a port group.

Stateless load balancing supports packets with MPLS encapsulation and IEEE 802.1 Q-in-Q VLAN tags.

For details on stateless load balancing, refer to the following sections:

• Stateless Load Balancing Metrics
• Configuring Stateless Load Balancing

To select stateless load balancing, do the following:

1.   From the device view, select GigaSMART > GigaSMART Operations (GSOP) GigaSMART Operation, and then click New.
2. Type an alias in the Alias field.
3. From the GigaSMART Groups drop-down list, select a GigaSMART group.
4. From the GigaSMART Operations (GSOP) drop-down list, select Load Balancing.
5. Configure Load Balancing:
• Select Stateless
• Specify a load balancing metric. For example, IP Only as shown in Figure 825: Configuring Stateful Load Balancing.
6. Click Save.

 

Figure 827: Selecting Stateless Load Balancing

For more information, refer to the following sections:

• Stateless Load Balancing Metrics
• Configuring Stateless Load Balancing
Stateless Load Balancing Metrics

The load balancing metrics available for stateless load balancing are described in the following table.

A tool port is selected from a port list based on hashing. The fields to be hashed are described in the table.

To specify a metric for stateless load balancing:

1.   From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation.
2. Click New to create a new GigaSMART Operation or Edit to modify an existing one.
3. Select Load Balancing from the GigaSMART Operations (GSOP) drop-down list and configure load balancing as follows.
a. Select Stateless
b. Select one of the hashing metrics: IP Only, IP & PORT, Five Tuple, or GTPU-TEID.

Table 1: Stateless Load Balancing Metrics describes each of the metrics.

4. Click Save.

 

Table 1: Stateless Load Balancing Metrics

Metric

Description

IP Only

The source IP and destination IP addresses.

IP & Port

The source IP and destination IP addresses, and Layer 4 source port and destination port numbers.

Five Tuple

The source IP and destination IP addresses, source port and destination port numbers, and protocol field in the IP header.

GTPU-TEID

The GTP-u tunnel identifier (ID).

Note:  There is no inner or outer field location for GTPU-TEID.

outer

The first occurrence of header or field. For example, IP Only outer is the first IP header in the packet, which could be IPv4 or IPv6.

inner

The second occurrence of header or field. For example, ip-only inner is the second IP header in the packet. The first IP header could be IPv4 or IPv6, as follows:

• IPv4-IPv4—IP Only inner is the IP addresses in the second IPv4 header
• IPv6-IPv4—IP Only inner is the IP addresses in the IPv4 header
• IPv4-IPv6—IP-Only inner is the IP addresses in the IPv6 header

The supported IP encapsulation types are: IP-in-IP, VXLAN, GTP, GRE, and ERSPAN.
Configuring Stateless Load Balancing

To configure stateless load balancing, specify the group of tool ports and enable load balancing in a port group.

1.   Select Ports > Port Groups > All Port Groups.
2. Click New.
3. Type an alias in the Alias field. For example, load-balgrp.
4. Select SMART Load Balancing.
5. Use the Ports field to select the ports for this port group as shown in Figure 826: Port Group Page to Set Ports for Load Balancing. Click Save when you are done.

 

Figure 828: Port Group Page to Set Ports for Load Balancing

Notes:

• Up to 50 load balancing port groups are supported, with a maximum of 256 ports for each group.
• Ports within port groups must be on the same chassis.
• Ports within port groups can have different rates.

Refer to the following examples:

• Example 1: GigaSMART Stateless Load Balancing
• Example 2: GigaSMART Stateless Load Balancing
• Example 3: GigaSMART Stateless Load Balancing

For an example of load balancing on L2GRE encapsulation tunnel, refer to Example 3 – GigaSMART L2GRE Tunnel Encap Stateless LB.

Example 1: GigaSMART Stateless Load Balancing

Example 1 configures stateless load balancing of traffic among tool ports 1/1/x6,
1/1/x7, 1/2/x3, and 1/2/x4 after slicing the packet to an offset of 70 bytes.

 

Step

Description

Command
1.    

Create a port group and specify the tool ports for load balancing.
a. Select Ports > Port Groups.
b. Click New
c. Type portgrp1 in the Alias field.
d. Select SMART Load Balancing
e. Click in the Ports field to select the tool ports for the group. For example, 1/1/x6,1/1/x7,1/2/x3, and 1/2/x4.
f. Click Save.
2.  

Configure a GigaSMART group and associate it with GigaSMART engine ports.
a. From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups.
b. Click New.
c. Type gsgrp1 in the Alias field.
d. Select the engine ports. For example 1/3/e1 and 1/3/e2.
e. Click Save.
3.  

Create a GSOP, with load balancing.
a. From the device view, select GigaSMART > GigaSMART Operations (GSOP) > Operations.
b. Click New.
c. Type lbiponlyouter in the Alias field
d. Select gsgrp1 from the GigaSMART Groups list.
e. Select the GigaSMART Operation Slicing.
f. Configure Slicing as follows:
- Select Stateful.
- Select None for protocol
- Set Offset to 70.
g. From the device view, select GigaSMART Operation Load Balancing.
h. Configure Load Balancing as follows:
- Select Stateless
- Select IP Only Outer for the hash metric
i. Click Save.
4.  

Create a first level map.

Note the following:

• You can specify only one port group as part of the map tool port in the to statement.
• You can define the same load balancing port group in multiple maps, however, the load balancing metrics defined in the GSOPs on those maps have to be the same.
• You cannot use a shared collector map for load balancing.
a. Select Maps > Maps > Maps.
b. Click New.
c. Type map1 in the Alias field.
d. Select First Level for Regular and By Rule for Subtype.
e. Select port 1/1/x1 for the Source.
f. Select port group portgrp1 for the Destination.
g. Select lbiponlyouter from the GSOP list.
h. Click Add a Rule
- Select Pass
- Select IP Version for the condition.
- Select v4 for Version.
i. Click Save.
Example 2: GigaSMART Stateless Load Balancing

Example 2 configures stateless load balancing of GTP traffic among tool ports 1/1/x6,
1/1/x7, 1/2/x3, and 1/2/x4. Data packets with the same GTP-u tunnel ID will be forwarded to the same tool port.

 

Step

Description

Command
1.    

Create a port group and specify the tool ports for load balancing.
a. Select Ports > Port Groups.
b. Click New
c. Type portgrp1 in the Alias field.
d. Select SMART Load Balancing
e. Click in the Ports field to select the tool ports for the group. For example, 1/1/x6,1/1/x7,1/2/x3, and 1/2/x4.
f. Click Save.
2.  

Configure a GigaSMART group and associate it with GigaSMART engine ports.
a. From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups.
b. Click New.
c. Type gsgrp1 in the Alias field.
d. Select the engine ports. For example 1/3/e1 and 1/3/e2.
e. Click Save.
3.  

Create a GSOP, including load balancing metric.
a. From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operations.
b. Click New.
c. Type gsop1 in the Alias field
d. Select gsgrp1 from the GigaSMART Groups list.
e. Select the GigaSMART Operation Load Balancing.
f. Configure Load Balancing as follows:
- Select Stateless
- Select GTPU-TEID for the hash metric
g. Click Save.
4.  

Create first level maps.

Note the following:

• You can specify only one port group as part of the map tool port in the to statement.
• You can define the same load balancing port group in multiple maps, however, the load balancing metrics defined in the GSOPs on those maps have to be the same.
• You cannot use a shared collector map for load balancing.

Create the first map:

a. Select Maps > Maps > Maps.
b. Click New.
c. Type map1 in the Alias field.
d. Select First Level for Regular and By Rule for Subtype.
e. Select port 1/1/x1 for the Source.
f. Select port group portgrp1 for the Destination.
g. Click Add a Rule, and then select Pass
h. Select IPv4 Protocol for the first condition.
i. Select UDP for Value
j. Select Port Destination for the second condition.
k. Enter 2123 for the port value.
l. Click Save.

Create the second map:

a. Select Maps > Maps > Maps.
b. Click New.
c. Type map1 in the Alias field.
d. Select First Level for Regular and By Rule for Subtype.
e. Select port 1/1/x1 for the Source.
f. Select port group portgrp1 for the Destination.
g. Select gsop1 from the GSOP list.
h. Click Add a Rule, and then select Pass
i. Select IPv4 Protocol for the first condition.
j. Select UDP for Value
k. Select Port Destination for the second condition.
l. Enter 2152 for the port value.
m. Click Save.
Example 3: GigaSMART Stateless Load Balancing

Example 3 configures stateless load balancing of HTTP on GTP traffic among tool ports 1/1/x6, 1/1/x7, 1/2/x3, and 1/2/x4. Data packets with the same inner IP will be forwarded to the same tool port.

 

Step

Description

Command
1.    

Create a port group and specify the tool ports for load balancing.
a. Select Ports > Port Groups.
b. Click New
c. Type portgrp1 in the Alias field.
d. Select SMART Load Balancing
e. Click in the Ports field to select the tool ports for the group. For example, 1/1/x6,1/1/x7,1/2/x3, and 1/2/x4.
f. Click Save.
2.  

Configure a GigaSMART group and associate it with GigaSMART engine ports.
a. From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups.
b. Click New.
c. Type gsgrp1 in the Alias field.
d. Select the engine ports. For example 1/3/e1 and 1/3/e2.
e. Click Save.
3.  

Create a GSOP, including load balancing metric.
f. From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation.
g. Click New.
h. Type gsop1 in the Alias field
i. Select gsgrp1 from the GigaSMART Groups list.
j. Select the GigaSMART Operation Load Balancing.
- Select Stateless
- Select IP Only Inner for the hash metric
k. Click Save.
4.  

Create first level maps.

Note the following:

- You can specify only one port group as part of the map tool port in the to statement.
- You can define the same load balancing port group in multiple maps, however, the load balancing metrics defined in the GSOPs on those maps have to be the same.
- You cannot use a shared collector map for load balancing.

Create the first map:

a. Select Maps > Maps > Maps.
b. Click New.
c. Type map1 in the Alias field.
d. Select Regular for Type and By Rule for Subtype.
e. Select port 1/1/x1 for the Source.
f. Select port group portgrp1 for the Destination.
g. Click Add a Rule, and then select Pass
h. Select IPv4 Protocol for the first condition.
i. Select UDP for Value
j. Select Port Destination for the second condition.
k. Enter 2123 for the port value.
l. Click Save.

Create the second map:

a. Select Maps > Maps > Maps.
b. Click New.
c. Type map1 in the Alias field.
d. Select First Level for Regular and By Rule for Subtype.
e. Select port 1/1/x1 for the Source.
f. Select port vp1 for the Destination.
g. Select gsop1 from the GSOP list.
h. Click Add a Rule, and then select Pass
i. Select IPv4 Protocol for the first condition.
j. Select UDP for Value
k. Select Port Destination for the second condition.
l. Enter 2152 for the port value.
m. Click Save.
5.  

Create the second level map.

Create the third map:

a. Select Maps > Maps > Maps.
b. Click New.
c. Type map22 in the Alias field.
d. Select Second Level for Type and By Rule for Subtype.
e. Select virtual vp1 for the Source.
f. Select port group portgrp1 for the Destination.
g. Select gsop1 from the GSOP list.
h. Click Add a Rule, and then select Pass
i. Select IPv4 Destination for the first condition.
j. Enter 80 for the destination value.
k. Select 2 for position.
l. Click Save.

Enhanced Load Balancing

GigaSMART Enhanced Load Balancing supports evenly distributed traffic among multiple tool ports based on one or more user defined fields. When a tool port fails, the traffic is redistributed just for that tool port to other member tool ports. When the failed tool port recovers, the traffic that was redistributed is restored to the recovered tool port. Traffic across other member tool ports remain undisturbed during this process.

Traffic Handling and Load Balancing Distribution
• Non GTP traffic and (subsequent) fragmented packets to be load balanced to all tool ports based on outer IP.
• Rebalance traffic when the following occurs:
• Tool port goes up or down
• Tool port group membership changes
• When a tool port fails redistribute the traffic just for that tool port and when the failed tool port recovers restore traffic just for that tool port
• No tool port within the port group receives more than 5% of average traffic based on the enhanced load balancing metric defined
Enhanced Load Balancing Metrics

GigaSMART provides configuration support for a new enhanced load balancing (enhanced-lb) app. The enhanced-lb app allows users to define the fields used for load balancing.

Enhanced Load Balancing supports the following hashing metrics:

• inner IP address
• outer IP address
• inner L4 port
• outer L4 port
• GPRS Tunnel Endpoint Identifier (TEID)
Configuring Enhanced Load Balancing

To configure enhanced load balancing, do the following:

1.   Select >Physical.
2. Click on a node you want apply enhance load balancing.
3. Select GigaSMART>Enhanced Load Balancing. The enhance load balance screen displays.

 

4. Click New. The enhanced load balancing screen appears.

 

5. Enter an Alias.
6. Select the Hash Field Name. The following options are available:

- IP

- L4 Port

- GTP-U TEID

7. Select Hash Field Location. Options:

- inner

- outer

Note:  Use the “+” or “-” icons to add and delete hash fields.

Hash Field Name

Hash Field Location

IP

Inner

IP

Outer

L4 Port

Outer

L4 Port

Inner

GTP-U TEID

None

You can configure up to five (5) different hash fields and location.

8. Click OK.

Note:  To view details about the enhanced load balancing parameters, click the Alias. The detail/edit dialog box displays.

 

Configure GigaSMART Operation (GSOP)

1.   Select > Physical.
2. Select GigaSMART > GSOP.
3. Click New.
4. Enter Alias.
5. Select a GSOP Group.
6. Select a GSOP type: Load Balancing.
7. Select GSOP type: Enhance load balancing. The Load Balancing dialog appears.

 

8. Select Enhanced.
9. Select an Enhanced Load Balance Alias from the drop-down. This is the enhanced load balance you previously created.

10. Click OK. The enhanced load balance GSOP is now available on the GSOP page.