Use the following example to create a load control profile on the P-GW/SAEGW/S-GW:

config 
   gtpc-load-control-profile  profile_name 
   end 

Notes:

This section describes how to set weightage percentages for system CPU, memory, and license session utilization as part of a GTP-C load control profile configuration. These settings constitute the basic load control profile for this network element. These parameters allow the P-GW/S-GW/SAEGW to send its load information to a peer GTP control plane node which the receiving GTP control plane peer node uses to augment existing GW selection procedures for the P-GW and S-GW. Load information reflects the operating status of the resources of the originating GTP control plane node.

Use the following example to configure the load control profile weightage settings on the P-GW/SAEGW/S-GW:

config 
   gtpc-load-control-profile  profile_name 
   weightage  system-cpu-utilization percentage  system-memory-utilization  percentage  license-session-utilization  percentage 
   end 

Notes:

Important

All parameters must be specified. The total of all three parameter settings should equal, but not exceed, 100.

This section describes how to set the parameters that determine the inclusion frequency of the Load Control Information Element (LCI) for a GTP-C Load Control Profile configuration. The LCI is a 3GPP-specific Information Element that is sent to peers when a configured threshold is reached. This parameter specifies how often the operator wants to send this information to the node's peers.

Use the following example to configure the load control profile inclusion frequency on the P-GW/SAEGW/S-GW.

config 
   gtpc-load-control-profile  profile_name 
      inclusion-frequency { advertisement-interval interval_in_seconds | change-factor change_factor  } 
      end 

Notes:

This section describes how to configure the minimum threshold value above which P-GW-provided load control information should be utilized for calculating the P-GW effective weight during initial node selection.

Use the following example to configure Load Control Profile threshold on the P-GW.

config 
   gtpc-load-control-profile profile_name 
      threshold  time_in_seconds 
      end 

Notes:

The handling of load control information for the home or visited PLMN can be enabled/disabled via this procedure.

Use the following example to enable/disable load control profile information handling on the SAEGW/S-GW/P-GW.

config 
   gtpc-load-control-profile  profile_name 
      load-control-handling { home | visited } 
      no load-control-handling { home | visited } 
      end 

Notes:

The publishing of load control information can be enabled/disabled for the home or visited PLMN.

Use the following example to enable/disable load control profile information publishing on the P-GW/SAEGW/S-GW.

config 
   gtpc-load-control-profile  profile_name 
      load-control-publishing { home | visited } 
      no load-control-publishing { home | visited } 
      end 

Notes:

In capacity testing and also in customer deployments it was observed that the chassis load factor for the 3GPP R12 Load and Overload Support feature was providing incorrect values even when the sessmgr card CPU utilization was high. The root cause is that when the load factor was calculated by taking an average of CPU utilization of sessmgr and demux cards, the demux card CPU utilization never increased more than the sessmgr card CPU utilization. As a result, the system did not go into the overload state even when the sessmgr card CPU utilization was high.

The 3GPP R12 Load/Overload Control Profile feature has been enhanced to calculate the load factor based on the higher value of similar types of cards for CPU load and memory. If the demux card's CPU utilization value is higher than the sessmgr card's CPU utilization value, then the demux card CPU utilization value is used for the load factor calculation.

Beginning with StarOS release 21, a new CLI command, gtpc-system-param-poll interval , is introduced in Context Configuration Mode to configure different polling intervals for the resource manager so that the demuxmgr can calculate the load factor based on different system requirements. This command sets the time period over which to monitor the chassis level CPU, Memory, and Session count information from the resource manager.

To configure the GTP-C polling parameter interval:

config 
   context context_name 
      gtpc-system-param-poll interval seconds 
      default gtpc-system-param-poll interval 
      end 

• Where seconds is the time period over which to monitor the chassis level CPU, Memory, and Session count information from the resource manager. Valid entries are from 15 to 300 seconds. The default setting is 30 seconds.

• default returns the setting to its default value of 30 seconds.

Caution

Setting the time interval to a low value may impact system performance.

Once the 3GPP R12 GTP-C load control profile is created, it must be associated with an existing P-GW, SAEGW, or S-GW service.

Use the following examples to associate the GTP-C load control profile with an existing P-GW, SAEGW, or S-GW service.

P-GW Service Association:

configure 
   context  context_name 
      pgw-service pgw_service_name 
         associate gtpc-load-control-profile profile_name 
         no associate gtpc-load-control-profile  
         end 

Notes:

S-GW Service Association:

configure 
   context  context_name 
      sgw-service sgw_service_name 
         associate gtpc-load-control-profile profile_name 
         no associate gtpc-load-control-profile  
         end 

Notes:

SAEGW Service Association::

configure 
   context context_name 
      sgw-service sgw_service_name 
         associate gtpc-load-control-profile profile_name 
         exit 
      pgw-service pgw_service_name 
         associate gtpc-load-control-profile profile_name 
         exit 
      saegw-service saegw_service_name 
         associate sgw-service sgw_service_name 
         associate pgw-service pgw_service_name 
         exit 

Use the following command to view the load control profile configuration settings:

show gtpc-overload-control-profile full name load_control_profile_name 

The output of this command provides the configuration settings of all load control parameters, including:

Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Use the following example to create the GTP-C Overload Control Profile:

configure 
   gtpc-overload-control-profile  profile_name 
   no gtpc-overload-control-profile  profile_name 
   end 

Notes:

This section describes how to configure GTP-C Overload Control weightage parameters. These parameters constitute the basic settings for this GTP-C Overload Control Profile. Communication of these parameters indicate to peers when this network element is becoming or being overloaded. When this occurs, the NE will be able to instruct its peers to gracefully reduce its incoming signaling load by instructing the peers to reduce sending traffic according to its available signaling capacity to successfully process the traffic. A GTP-C entity is in overload when it operates over its signaling capacity, which results in diminished performance (including impacts to handling of incoming and outgoing traffic).

Use the following example to configure the GTP-C Overload Control Weightage settings on the P-GW/SAEGW/S-GW.

configure 
   gtpc-overload-control-profile  profile_name 
      weightage system-cpu-utilization percentage system-memory-utilization percentage license-session-utilization percentage. 
      default weightage   
      end 

Notes:

This section describes how to set the parameters that determine the inclusion frequency of the Overload Control Information Element (OCI) for a GTP-C Load Control Profile configuration. The OCI is a 3GPP-specific IE that is sent to peers when a configured threshold is reached. This parameter specifies how often the operator wants to send this information to the peers.

Use the following example to configure the overload control profile inclusion frequency on the P-GW/SAEGW/S-GW.

configure 
   gtpc-overload-control-profile  profile_name 
      inclusion-frequency { advertisement-interval interval_in_seconds | change-factor change_factor } 
      default inclusion-frequency { advertisement-interval | change-factor } 
      end 

Notes:

This section describes how to configure the overload control validity period. The validity period is the length of time during which the overload condition specified by the overload control information element is to be considered as valid, unless overridden by subsequent new overload control information.

Use the following example to configure the GTP-C Overload Control validity period on the P-GW/SAEGW/S-GW.

configure 
   gtpc-overload-control-profile profile_name 
      validity-period seconds 
      default validity-period  
      end 

Notes:

Use this example to configure GTP-C Overload Control Tolerance limits.

configure 
   gtpc-overlaod-control-profile  profile_name 
      tolerance { initial-reduction-metric percentage | threshold report-reduction-metric percentage self-protection-limit percentage  } 
      default tolerance { initial-reduction-metric | threshold } 
      end 

Notes:

Use this command to configure throttling behavior based on peer's overload reduction-metric by excluding some or all emergency events and/or messages with configured EARP. Message throttling applies only to initial messages. Triggered request or response messages should not be throttled since that would result in the retransmission of the corresponding request message by the sender.

If throttling-behavior is configured, the profile can be associated with an S-GW or P-GW service. If a P-GW specific keyword is configured, and the profile is associated with an S-GW service, the S-GW will ignore the P-GW specific configuration. Only the parameters specific to S-GW or P-GW will be utilized.

Use this example to configure GTP-C overload control throttling behavior on the P-GW/SAEGW/S-GW.

configure 
   gtpc-overlaod-control-profile  profile_name 
      throttling-behavior { earp [ 1 | 2 | 3 | 4 | 5 | 6 | 7 |8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 ]* exclude } | emergency-events exclude }  
      no throttling-behavior [ earp [ 1 |2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 ]* exclude | emergency-events exclude ]  
      end 

Notes:

In the R12 GTP-C Load Overload control feature, it is possible to apply message throttling, (when a peer indicates it is overloaded), based on message priority. To apply message prioritization it is necessary to configure the percentage of two groups of messages that each node (P-GW or ePDG) is expected to generate. The operator can define the expected number of messages as a percentage for each message group.

Use the following example to configure message prioritization.

configure 
   gtpc-overload-control-profile profile_name 
      message-prioritization  group1 percentage group2 percentage 
      no message-prioritization 
      default message-prioritization 
      end 

Notes:

This functionality enables the operator to configure APN names and EARP priority level values for self-protection mode so that incoming request messages for emergency packet data node (PDN) connections and/or configured EARP priority values are not rejected even if the system is under self-protection mode.

Use this example to configure GTP-C overload control self-protection behavior.

configure 
   gtpc-overload-control-profile profile_name 
      self-protection-behavior  { apn  apn_name*  exclude  | earp { 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15* } exclude } } 
      no self-protection-behavior  { apn  apn_name*  exclude  | earp { 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15* } exclude } } 
      end 

Notes:

Use this command to enable/disable the handling of overload control information for the home or visited PLMN.

configure 
   gtpc-load-control-profile profile_name 
      overload-control-handling { home | visited } 
      no overload-control-handling { home | visited } 
      default overload-control-handling 
      end   

Notes:

Enables or disables the publishing of load control information towards the home or visited PLMN.

configure 
   gtpc-overload-control-profile profile_name 
      overload-control-publishing { home | visited }   
      no overload-control-publishing { home | visited }   
      default overload-control-publishing  
      end 

Notes:

In capacity testing and also in customer deployments it was observed that the chassis load factor for the 3GPP R12 Load and Overload Support feature was providing incorrect values even when the sessmgr card CPU utilization was high. The root cause is that when the load factor was calculated by taking an average of CPU utilization of sessmgr and demux cards, the demux card CPU utilization never increased more than the sessmgr card CPU utilization. As a result, the system did not go into the overload state even when the sessmgr card CPU utilization was high.

The 3GPP R12 Load/Overload Control Profile feature has been enhanced to calculate the load factor based on the higher value of similar types of cards for CPU load and memory. If the demux card's CPU utilization value is higher than the sessmgr card's CPU utilization value, then the demux card CPU utilization value is used for the load factor calculation.

Beginning with StarOS release 21, a new CLI command, gtpc-system-param-poll interval , is introduced in Context Configuration Mode to configure different polling intervals for the resource manager so that the demuxmgr can calculate the load factor based on different system requirements. This command sets the time period over which to monitor the chassis level CPU, Memory, and Session count information from the resource manager.

To configure the GTP-C polling parameter interval:

config 
   context context_name 
      gtpc-system-param-poll interval seconds 
      default gtpc-system-param-poll interval 
      end 

• Where seconds is the time period over which to monitor the chassis level CPU, Memory, and Session count information from the resource manager. Valid entries are from 15 to 300 seconds. The default setting is 30 seconds.

• default returns the setting to its default value of 30 seconds.

Caution

Setting the time interval to a low value may impact system performance.

Once the 3GPP R12 overload control profile has been configured, it must be associated with an existing P-GW, SAEGW, or S-GW service.

Use the following examples to associate the overload control configuration to an existing service.

P-GW Service Association:

configure 
   context context_name 
      pgw-service pgw_service_name 
         associate gtpc-overload-control-profile profile_name 
         no associate gtpc-overload-control-profile  
         end 

Notes:

S-GW Service Association:

configure 
   context context_name 
      sgw-service sgw_service_name 
         associate gtpc-overload-control-profile profile_name 
         no associate gtpc-overload-control-profile  
         end 

Notes:

SAEGW Service Association::

configure 
   context context_name 
      sgw-service sgw_service_name 
         associate gtpc-overload-control-profile profile_name 
         exit 
      pgw-service pgw_service_name 
         associate gtpc-overload-control-profile profile_name 
         exit 
      saegw-service saegw_service_name 
         associate sgw-service sgw_service_name 
         associate pgw-service pgw_service_name 
         exit 

Use the following command to view the overload control configuration settings.

show gtpc-overload-control-profile full name  overload_control_profile_name 

The output of this command provides all overload control profile configuration settings, including:

Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.