Page History

 

Panel
borderColor green bgColor transparent borderWidth 2
Noprint Back to Table of Contents Back to All Back to All - System Additional sections: Children Display style h6

The congestion objects provide a facility for managing the call congestion on the

Spacevars
0 product

server. Following system congestion levels are defined in this section, with each level representing an increasing severity of congestion within the

Spacevars
0 product

:

...

• CPU utilization on server
• Memory utilization on server

By configuring the Overload Profile appropriately, some of the congestion criteria can trigger a change in the congestion level.

During a sustained system load, the

Spacevars
0 product

accepts calls at a smooth rate, avoiding behavior such as accepting all calls for a short period of time, and then rejecting all calls for the remaining sampling period. This is accomplished with system-level policers. Unlike IP Traffic Policers--which control the allowed rate of incoming IP packets, congestion policers control the allowed rate of incoming calls in a system. Individually configurable bucket sizes (POLICER BUCKETSIZE) control the call burst handling capability. The policer fill rate controls the sustained rate (the rate at which tokens are added to the bucket). In this case, the fill rate is the sustained call rate allowed at calls per second (CPS). Fill rates are not configurable when using congestion policers; instead, they are dynamically adjusted based on resource usage, to maximize those resources.

On SBC main the

Spacevars
0 product

 main screen, go to All > System > Congestion.

The Congestion window is displayed.

Caption
0 Figure 1 System - Congestion
Image Modified

The following fields are displayed:

Caption
0 Table 1 System - Congestion parameters
Parameter Description Mode Mode (adaptive or monitor) of the system overload control. You have the following modes: adaptivestatic

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

Congestion Commands

The

Spacevars
0 series4

detects congestion by monitoring a time-decaying average of the CPU utilization. It also monitors the Internal Round-Trip Time (IRTT) during call setup for determining whether the

Spacevars
0 product

is in congestion. When congestion (for either reason) is detected and the congestion level reaches MC2, the SBC activates a control algorithm which adaptively throttles calls to eliminate the congestion while still maximizing the call throughput.

On SBC main screen, go to All > System > Congestion. The Congestion window is displayed. The Congestion Commands panel appears at the bottom

Caption
0 Figure 1 All - System - Congestion Commands
Image Removed

The following options are displayed:

Caption
0 Table 1 System - Congestion Commands parameters
Parameter Description setSysCongestion Simulates resource (cpu memory) congestion. setDebugSysCongestion Sets the debug flag associated with system congestion setSysIpInstance Directs all the calls of a specific type or SIP registrations to a specific instance of call processing engine. cpuhistory Displays the CPU usage history. memhistory Displays the Memory usage history.

setSysCongestion

This command helps you to simulate resources for appropriate CPU usage.

On the Congestion Commands panel, choose setSysCongestion as the Command from the drop-down list and click Select. A pop up window appears with the respective command parameters.

Caption
0 Figure 1 All - System - Congestion Commands - setSysCongestion
Image Removed

Choose the Resource and the Level at which the congestion should happen and click setSysCongestion.

The result of the action is displayed:

Caption
0 Figure 1 All - System - Congestion Commands - Result
Image Removed

setDebugSysCongestion

This command helps you to set the debug flag along with the system congestion.

On the Congestion Commands panel, choose setDebugSysCongestion as the Command from the drop-down list and click Select. A pop up window appears with the respective command parameters.

Caption
0 Figure 1 All - System - Congestion Commands - setDebugSysCongestion
Image Removed

Select enabled for Debugflag and click setDebugSysCongestion.

The result of the action is displayed:

Caption
0 Figure 1 All - System - Congestion Commands - Result
Image Removed

setSysIpInstance

This command help you to direct all the calls to a specific instance of call processing engine.

On the Congestion Commands panel, choose setSysIpInstance as the Command from the drop-down list and click Select. A pop up window appears with the respective command parameters.

Caption
0 Figure 1 All - System - Congestion Commands - setSysIpInstance
Image Removed

Select the Ip Type from the drop-down list and add the instance value and click setSysIpInstance.

The result of the action is displayed:

Caption
0 Figure 1 All - System - Congestion Commands - Result
Image Removed

cpuhistory

This command helps you to view the CPU usage history.

On the Congestion Commands panel, choose cpuhistory as the Command from the drop-down list and click Select. A pop up window appears with the respective command parameters.

Caption
0 Figure 1 All - System - Congestion Commands - cpuhistory
Image Removed

Select the desired Type from the drop-down list and click cpuhistory.

The result of the action is displayed:

Caption
0 Figure 1 All - System - Congestion Commands - Result
Image Removed

memhistory

This command helps you to view the Memory usage history.

On the Congestion Commands panel, choose memhistory as the Command from the drop-down list and click Select. A pop up window appears with the respective command parameters.

Caption
0 Figure 1 All - System - Congestion Commands - memhistory
Image Removed

Select the desired Type from the drop-down list and click memhistory.

The result of the action is displayed:

...

0	Figure
1	All - System - Congestion Commands - Result

 

Additional topics in this section:

Div
style padding-left:1%; id indent
Children Display depth 2 style h5

Pagebreak

...