Measurements Platform/E5-OAM Integrated Measurements Feature Reports

Measurements Platform and E5-OAM Integrated Measurements reports have the following characteristics.

Report Files

Report files are divided into three sections:

1. System header

   The system header size varies depending on embedded data. A typical size of 250 bytes is used in all calculations in the examples in this manual.

2. Individual report header

   The report header size varies depending on the report type, but is always the same size for an individual report type. The size of the report data section varies depending on the number of entities being reported, and the particular data items being reported for each entity (for example, a count of 0 versus a large count).

3. Report data

   For the estimates given in this manual, 6 characters are assumed for each data item, including the comma delimiter. Other variable quantities, such as the number of entities in the report, are stated with each example.

The output file sizes calculated in this manual are rough estimates only. They are not intended to be an exact representation of output file size, which could vary significantly depending on the configuration of a particular system.

Table 2-3 Measurements Platform and E5-OAM Integrated Measurements Feature System Header

Field Name	Description	Unit
CLLI	The Common Language Location Identifier for the STP	ASCII Text
SWREL	The software release currently running on the STP	ASCII Text
RPTDATE	The date on which the report was generated	YYYY-MM-DD
RPTIME	The time at which the report was generated (24-hour clock)	HH:MM:SS
TZ	An abbreviation for the time zone	ASCII Text
RPTTYPE	The type of report being generated	ASCII Text
RPTPD	The period of the report	ASCII Text
IVALDATE	The date for the report interval	YYYY-MM-DD
IVALSTART	The starting time of the report interval	HH:MM:SS
IVALEND	The ending time of the report interval	HH:MM:SS
NUMENTIDS	The number of entities contained in the report	Integer

Example header format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE",
"IVALSTART","IVALEND","NUMENTIDS"<cr><lf>
"tekelecstp","31.3.0-39.1.0","1999-01-17","15:51:37","EST",
"STP SYSTEM TOTAL MEASUREMENTS ON STP","LAST","1999-01-17","15:00:00","15:30:00",1<cr><lf>
<cr><lf>

File Naming Conventions

File names consist of fields separated by underscores and followed by the .csv extension. This format allows the files to be readily identified as a comma-separated value (CSV) format. Due to the overall length of the file names, long file names (beyond 8.3 format) are utilized.

• CLLI-based Names Disabled

  These file names consist of three fields identified as follows:

  • Up to 13 characters for the report type (sched-entity, for example, systot-stp or mtcdth-lnkset)

  • 8 characters for the report date (yyyymmdd). This reflects the date the data is generated.

  • 4 characters for the ending report time (hhmm). This is defined as the common boundary between the end of the last period and the beginning of the next period. For example, the half hour from 2:00PM to 2:30PM would end at 1430. A day-to-hour period ends on the hour. A daily period or specific request for the final hour or half-hour of a day ends at 2400, midnight.

  Examples of output file names:

  • Half hourly STP system totals generated 1999-02-24 at 15:22:00 for the last period would be (the period from 1430 to 1500 on 02/24/99):

    systot-stp_19990224_1500.csv

  • Maintenance daily linkset report generated 2001-07-17 at any time would be (the period from 0000 to 2400 on 07/16/01):

    mtcd-lnkset_20010716_2400.csv

  • Maintenance day-to-hour link report generated 2003-04-29 at 08:32:00 would be (the period from 0000 to 0800 on 04/29/03):

    mtcdth-link_20030429_0800.csv

  • Half hourly STP system totals generated 1999-02-23 at 00:15:20 for the specific end time 0030 would be (the period from 0000 to 0030 on 02/23/99):

    systot-stp_19990223_0030.csv

  • Half hourly STP system totals generated 1999-02-24 at 00:15:30 for the specific end time 2330 would be (the period from 2300 to 2330 on 02/23/99):

    systot-stp_19990223_2330.csv

  • Half hourly STP system totals generated 1999-02-24 at any time for the specific end time 2400 or 0000 would be (the period from 2330 to 2400 on 02/23/99):

    systot-stp_19990223_2400.csv

  Some applications will reformat fields when opening the .csv file. Use a text editor when opening .csv files to examine file content as presented in the output file examples in this document.

• CLLI-based Names Enabled

  These file names consist of four fields identified as follows:

  • Up to 11 characters for the CLLI of the EAGLE.

  • Up to 13 characters for the report type (sched-entity, for example, systot-stp or mtcdth-lnkset)

  • 4 characters for the report date (mmdd). This reflects the date the data is generated.

  • 4 characters for the ending report time (hhmm). This is defined as the common boundary between the end of the last period and the beginning of the next period. For example, the half hour from 2:00PM to 2:30PM would end at 1430. A day-to-hour period ends on the hour. A daily period or specific request for the final hour or half-hour of a day ends at 2400, midnight.

  Examples of output file names:

  • Half hourly STP system totals generated 02-24 at 15:22:00 for the last period would be (the period from 1430 to 1500 on 02/24:

    wnrtpaah01w_systot-stp_0224_1500.csv

  • Maintenance daily linkset report generated 07-17 at any time would be (the period from 0000 to 2400 on 07/16:

    wnrtpaah01w_mtcd-lnkset_0716_2400.csv

  • Maintenance day-to-hour link report generated 04-29 at 08:32:00 would be (the period from 0000 to 0800 on 04/29:

    wnrtpaah01w_mtcdth-link_0429_0800.csv

  • Half hourly STP system totals generated 02-23 at 00:15:20 for the specific end time 0030 would be (the period from 0000 to 0030 on 02/23):

    wnrtpaah01w_systot-stp_0223_0030.csv

  • Half hourly STP system totals generated 02-24 at 00:15:30 for the specific end time 2330 would be (the period from 2300 to 2330 on 02/23):

    wnrtpaah01w_systot-stp_0223_2330.csv

  • Half hourly STP system totals generated 1999-02-24 at any time for the specific end time 2400 or 0000 would be (the period from 2330 to 2400 on 02/23/99):

    wnrtpaah01w_systot-stp_0223_2400.csv

  Some applications will reformat fields when opening the .csv file. Use a text editor when opening .csv files to examine file content as presented in the output file examples in this document.

Measurement Interval Status Criteria

The STATUS Event Name in the measurement reports provides the reported collection status, as described in Table 2-4.

Table 2-4 Measurement Interval Status Criteria

Event Name

Description

STATUS

Indication of Data Validity K indicates good data. The basic rule to mark a measurement report as K is that the registers are pegged for the complete interval and the cards collecting the registers are IS-NR for the entire interval. I indicates an incomplete interval. This indicates that the registers were not pegged for the complete interval or the cards collecting the registers were not IS-NR for the entire interval. There can be a case in which OAM or MCPM sends measurement collection requests to the LIM or SERVICE cards, but the cards did not collect any data and/or failed to send that data to the OAM or MCPM for the complete interval. In such a case the reports are generated and stored with zeroes for the register values, which indicates that measurements are running on the EAGLE but that the LIM/SERVICE cards are ISOLATED or OOS-MT-DSBLD. N indicates data not current, no data was collected. All register values will contain zeros, which are to be interpreted as unknown.