1 Alarm Description
The alarm is raised when the memory use exceeds a threshold.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
System overload |
The system is overloaded |
The system is overloaded |
System dimensioning |
Service downtime or reduced service capacity when the problem is too often detected or when it persists |
|
One or more processes leak memory |
One or more processes leak memory |
A software component has an implementation defect |
Software component |
Software crash leading to service downtime or reduced service capacity depending on redundancy |
- Note:
- This alarm can appear as a result of a maintenance activity.
2 Procedure
2.1 Handle Alarm LOTC Memory Usage
Prerequisites
- This instruction references the following document:
- No tools are required.
- The following condition must apply:
- The alarm is raised.
Steps
- Log on to the host to access a Linux® shell, for example:
ssh <user>@<hostname> -p 7022
The hostname is part of alarm attribute Source.
- Synchronize the data on the disk with the memory:
>sync
- Wait one minute.
- Is the alarm cleared?
Yes: Continue with the next step.
No: Proceed with Step 7.
- Is this alarm occurring at least once a day?
Yes: Continue with the next step.
No: Proceed with Step 9.
- This can be a scaling issue. Contact the planning organization. Proceed with Step 9.
- Perform data collection, refer to Data Collection Guideline.
- Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
- Job is completed.

Contents