Start Measurement Collection Job

1	Introduction
1.1	Prerequisites
2	Procedure

1 Introduction

This document describes how to start a measurement collection job.

A measurement collection job is started to enable collection of performance data for the corresponding measurement types. This is usually done when the managed element is operational and manageable as part of the normal operations.

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_15min_Job in this document.
currentJobState for the job is STOPPED.
An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2 Procedure

To start a measurement collection job:

Navigate to the PmJob Managed Object (MO), for example:
>dn ManagedElement=NODE06ST,SystemFunctions=1,Pm=1,PmJob=POT_15min_Job
Enter Config mode:
(PmJob=POT_15min_Job)>configure
Set the PmJob state to ACTIVE:
(config-PmJob=POT_15min_Job)>requestedJobState=ACTIVE
Commit the PmJob configuration:
(config-PmJob=POT_15min_Job)>commit

Verify that currentJobState is changed to ACTIVE:

(PmJob=POT_15min_Job)>show -v

The following is an example output:

PmJob=POT_15min_Job
   compressionType=[] <empty>
   currentJobState=ACTIVE <read-only>
   granularityPeriod=FIFTEEN_MIN <default>
   jobControl=FULL <default> <read-only>
   jobGroup=[] <empty>
   jobPriority=MEDIUM <default>
   jobType=MEASUREMENTJOB <default>
   pmJobId="POT_15min_Job"
[...]
   requestedJobState=ACTIVE <default>
   MeasurementReader=POT_mr

Wait up to 5 minutes after the end of the granularity period.
Navigate to the FileGroup MO where all performance measurement files are exposed, for example:
(PmJob=POT_15min_Job)>dn ManagedElement=NODE06ST,SystemFunctions=1,FileM=1,LogicalFs=1,FileGroup=PerformanceManagementReportFiles

Verify that the FileGroup MO corresponding to the created performance measurement report file exists:

(FileGroup=PerformanceManagementReportFiles)>show -v

The following is an example output:

FileGroup=PerformanceManagementReportFiles
   internalHousekeeping=false
   files="A20141124.1045+0100-1100+0100_NODE06ST.xml"
      fileName="A20141124.1045+0100-1100+0200_NODE06ST.xml"
      fileType="xml"
      modificationTime="2014-11-24T01:26:00"
      size=1388
[...]

Note:: This output means that file A20141124.1045+0100-1100+0100_NODE06ST.xml exists in the file system. The + sign is rendered as ?? by the ECLI.
The file can contain additional performance measurement data corresponding to other jobs with the same granularity period.