| Configure overload protection | |||
|
| GO | |
|
This topic describes the steps to configure the Lucent CM system for handling overload.
When too many resources in a Lucent CM system are in use, the Lucent CM system goes in overload. In a severe overload situation, there is a risk that existing processes cannot be handled properly.
The Lucent CM system uses overload protection to ensure that running process are handled correctly and to recover from the overload.
When the Lucent CM system detects an overload situation, the system goes into an overload protection status. In an overload protection status, the Lucent CM system rejects incoming requests from client APIs. Rejecting request reduces the load on the system and allows the system to handle existing requests properly.
Lucent CM does not reject administration client API request. Lucent CM only rejects end-user client API requests and enterprise administrator API requests.
Additionally, the Lucent CM system suspends the processing of users' scheduled profiles until the overload situation has cleared. While the Lucent CM system is in an overload protection status, users may experience delayed scheduled profile activations.
The Lucent CM uses resource measurements to monitor how much resources are in use. The resource measurements are the same measurements that are used for performance management.
When the average amount or resources in the last sampling interval exceeds the defined entry level for overload, the Lucent CM goes into overload protection status. During overload protection, the system keeps on monitoring resources. when the average amount or resources in the last sampling interval drops below the defined exit level for overload, the Lucent CM resumes normal operation.
Lucent CM queues or denies user actions to the FS 5000 call server when the FS 5000 responds with 'DELAY' to API commands sent over the WPIF interface.
The overload parameters:
|
Parameter |
Description |
|
Number of Samples Window |
The number of sample intervals that meet the overload entry or overload exit requirement, before the overload status changes. |
|
Entry to Overload Protection (%) |
The minimum percentage of used resources to enter an overload condition. |
|
Exit from Overload Protection (%) |
The minimum percentage of used resources to exit an overload condition. |
Perform the following steps to configure overload control:
1 |
At the Lucent CM Explorer tree view, expand the Services folder and select Interval and overload. |
2 |
Define the Overload related parameters. |
3 |
Click Save. |
4 |
At the Lucent CM Explorer tree view, expand the Services folder and select SNMP TCA. |
5 |
To report the overload to an OSS or other SNMP trap destination, allow the Enter Overload Protection trap and define a threshold and severity. |
6 |
Click Update. End of steps |
|
|
GO | |
|
| © Lucent Technologies | |||