1 Introduction
This document describes how to stop a threshold monitoring job. In maintenance situations, the user can suspend a threshold monitoring job to avoid forwarding threshold alarms to the management system when the Managed Element (ME) is unstable and already given specific attention. This is also a way to reduce the load on the ME.
1.1 Prerequisites
This section describes the prerequisites, which must be fulfilled before using the procedure.
1.1.1 Conditions
The following conditions must apply:
- The job name is known.
The job name is POT_Thr_Job in this document.
- An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
2 Procedure
To stop a threshold monitoring job:
- Navigate to the PmJob managed object, for example:
>dn ManagedElement=NODE06ST,SystemFunctions=1,Pm=1,PmJob=POT_Thr_Job
- Enter Config mode:
(PmJob=POT_Thr_Job)>configure
- Set the PmJob state to STOPPED:
(config-PmJob=POT_Thr_Job)>requestedJobState=STOPPED
- Commit the PmJob configuration:
(config-PmJob=POT_Thr_Job)>commit
- Verify the result:
(PmJob=POT_Thr_Job)>show -v
The following is an example output:
PmJob=POT_Thr_Job compressionType=[] <empty> currentJobState=STOPPED <read-only> granularityPeriod=FIFTEEN_MIN <default> jobControl=FULL <default> <read-only> jobGroup=[] <empty> jobPriority=MEDIUM <default> jobType=THRESHOLDJOB pmJobId="POT_Thr_Job" reportContentGeneration=CHANGED_ONLY <default> reportingPeriod=FIFTEEN_MIN <default> requestedJobState=STOPPED MeasurementReader=POT_mr

Contents