Measurements

Introduction to Measurements

This section describes EAGLE measurements. Measurements provide support for:

STP performance management
SS7 traffic monitoring and engineering
Specific feature performance analysis

Measurements provide operations and maintenance personnel with network performance and STP performance data in accordance with:

Telcordia GR-82-CORE
Telcordia GR-310-CORE
Telcordia GR-478-CORE
Telcordia GR-778-CORE

Measurements can be collected and reported with the following collection methods:

The primary functions of Measurements are as follows:

Collection

Measurements are collected in 5-minute, 30-minute, and 60-minute intervals. An option exists for the default 30-minute measurements to be collected every 15 minutes. Many 30-minute measurements intervals are accumulated into daily intervals.
Storage

Measurements are stored in dedicated RAM tables and/or disks after collection. Most are retained for 24 hours. Measurements for some features are retained for 7 days.
Retrieval

Measurements data is retrieved from the RAM storage area and/or disk. ACTIVE measurement data is retrieved and reported from the application cards except for SCP SMCs. Registers collected from SCP SMCs are not supported for ACTIVE measurements and will be reported as zero in an ACTIVE measurement report. An ACTIVE linkset report requires all links in the linkset to be available in order to provide the report.

Reporting

Measurement reports are available on-demand/scheduled as shown in Table 2-1.

Table 2-1 Demand and Scheduled Reporting

Reporting Interval	Measurements Platform		E5-OAM Integrated Measurements
Reporting Interval	Demand	Scheduled	Demand	Scheduled
5-minute	Yes	Yes	Yes	Yes
15-minute (optional)	Yes	Yes	Yes	Yes
30-minute	Yes	Yes	Yes	Yes
Day-to-hour	Yes	No	Yes	No
Hourly	Yes	Yes	Yes	Yes
Daily	Yes	Yes	Yes	Yes

Scheduled measurements are directed to the Traffic Unsolicited Output Message group. No other unsolicited output is sent to this output group.

Note that the collection of measurements is a separate task from reporting. Measurements collection is activated automatically upon system power-up, or through administrative commands. Collection is organized by ENTTYPE and reporting period. Collection occurs per link every 5 minutes, and separately every 30 minutes. Measurements are generated on the application cards and periodically collected by the UI and stored for later retrieval, unless the Measurements Platform is enabled, whereas the information is collected and stored by the dedicated MPCM cards.

Refer to the Commands User's Guide for descriptions of commands used to generate, schedule, and transfer measurements reports.

Refer to the Database Administration - System Management User's Guide for information and procedures to provision basic OAM measurements, the Measurements Platform feature and E5-OAM Integrated Measurements feature.

Obsolete OAM Measurements and FTA

Basic OAM measurements are no longer supported from Release 46.3 onward. For measurement collection to occur, either the Measurements Platform feature or the E5-OAM Integrated Measurements feature must be used. To enable the E5-OAM Integrated Measurements feature, use the following commands:

ENABLE-CTRL-FEAT:partnum=893037301
CHG-CTRL-FEAT:partnum=893037301:status=ON

OAM-based measurements are collected by an E5-OAM MASP and are stored on the E5-TDM card.

For OAM-based measurements and the Measurements Platform feature, the rept-meas command sends measurements reports for the NP, GSM MAP screening, LNP, G-Port, A-Port, and IS41 GSM Migration (IGM) features to the file transfer area (FTA). Applications measurements (INP, GSM MAP screening, and LNP) are now supported only by the FTP reporting capability.

The FTA measurements reporting capability is replaced with the FTP reporting capability.

EAGLE continues to support retrieval of the ACTIVE PERIOD for links/linkset for troubleshooting purposes. All the entity types that supported the ACTIVE PERIOD collection without enabling the Measurements Platform feature or the E5-OAM Integrated Measurements feature are still supported.

The EAGLE UI display of measurement reports via the chg/rept-meas and rtrv-meas-sched commands is still supported; either the Measurements Platform or E5-OAM Integrated Measurements must be enabled.

Basic OAM Measurements

Basic OAM measurements are collected by the E5-MCAP control card and are stored on the E5-TDM card. For EAGLE nodes with up to 700 links, measurement reports can be generated either to a User Interface (UI) serial terminal or through the File Transfer Area (FTA), depending on the feature or function.

Basic OAM measurements are available when the E5-OAM Integrated Measurements feature and the Measurements Platform feature are not used in the system.

When basic OAM measurements are in use, the rept-meas command sends measurements reports for TYPE=MTCH (as well as some MTCD reports) to the file transfer area (FTA) rather than to an EAGLE terminal.

When basic OAM measurements are in use, turning on any unsupported feature disables hourly collection for ALL features. The features not supported are:

AIQ
ATINP/PATINP
EGMS
EIR
ENUM
GTT Actions
LNP 384
SIP
S13 EIR
VFLEX

Reports can be scheduled or generated on demand using the following commands:

chg-meas: Used to turn measurement collection on and off, and to schedule automatic generation of measurements reports to a UI terminal.
rept-meas: Used to generate measurements reports on demand.
rtrv-meas-sched: Used to display the measurements collection status and the list of measurements reports currently scheduled to be automatically generated to a UI terminal.

Note:

If a new entity is provisioned in place of a deleted entity, then the measurements for the deleted entity are set to zero. The reported peg counts apply only to the new entity.

The File Transfer Area function supports the transfer of file data between an EAGLE and a remote computer. The function provides the capability to download files from the EAGLE using a data communications link and the following commands:

Activate File Transfer: act-file-trns
Copy to or from Transfer Area: copy-fta
Delete Entry from File Transfer Area: dlt-fta
Display File Transfer Area: disp-fta-dir

Extracting measurements from the FTA requires:

A computer with a VT320 or KSR connection to the system
A communication program that both emulates VT terminals and supports Kermit file transfer
A spreadsheet program that can import Comma Separated Value (CSV) text files

A personal computer running ProComm^© for Windows and Microsoft Excel^© meets these requirements.

Measurements Platform

For an EAGLE node with more than 700 links, either the Measurements Platform or the E5-OAM Integrated Measurements feature must be used to collect measurements. The Measurements Platform must be used to collect measurements for an EAGLE node with more than 2400 links. The Measurements Platform provides a dedicated processor for collecting and reporting measurements data for EAGLE functions, EPAP-related features that collect measurements, GSM MAP Screening, and LNP.

Note:

If the 15-Minute Measurements feature is turned on, then the Measurements Plaform is required for support of more than 1200 links.

Links that are supported by the Measurements Platform and E5-OAM Integrated Measurements feature include IP associations as shown:

Each low-speed link (LSL) counts as 1 link
Each ATM high speed link (HSL) counts as 1 link
Each SE-HSL counts as 1 link
For IPLIM, each association counts as 1 link
For IPGW, 1 link per card
For IPSG, each association counts as 1 link

The Measurements Platform feature requires the following hardware and provisioning in the system:

Two MCPM cards

The platform consists of multiple Measurement Collection and Polling Module (MCPM) cards in a primary/secondary configuration, in which the primary MCPM performs all collection and reporting functions. The secondary MCPM card serves as backup for the primary. The EAGLE interface is via the standard IMT bus and allows communications with the network elements and the OAM. The interface to the customer's network supports the FTP transfer of Measurements reports to an FTP server.

The Primary MCPM maintains constant communication with the Secondary card as a way of each monitoring the health status of the other. If the primary MCPM fails before or during collection, the secondary MCPM card assumes the Primary role and begins/continues collection.
The Measurements Platform feature turned on
The Measurements Platform enable option turned on in the MEASOPTS table
A provisioned customer FTP server
The EAGLE OA&M IP Security feature, and Secure Shell FTP (SFTP) as a client, if secure transfer is used

Enabling the Measurements Platform feature (feature bit is turned on), allows the Measurements Platform to be provisioned and tested without transferring measurement functionality from the OAM to the Measurements Platform. After the Platform hardware, software, and Ethernet connections have been provisioned and verified, the transfer of measurements functionality from the OAM to the Measurement Platform is initiated by setting the Measurements Platform Enabled bit, which is set by the system only one time. From the point that theMeasurements Platform Enabled bit is set and initial data transfer has occurred, the measurements functionality of the OAM is limited to operator interface for measurement configuration and on-demand report requests. The Measurements Platform assumes the collection duties and stores the collected data in MCPM RAM.

After collection of the measurements, scheduled reports are automatically generated and transferred from an MCPM card to a customer FTP server using the FTP interface.

Existing FTP file server reports are overwritten by subsequent requests that produce the identical file name.

Reports can be scheduled or generated on demand. Scheduled and on-demand reports are accessible by the following commands:

chg-measopts: Used to:
- Enable Measurements Platform collection
- Turn on or turn off the 15 Minute Measurements collection function
- Enable or disable the automatic generation and FTP transfer of scheduled measurements reports to the FTP server
- Turn on or off the CLLI-based file name option for measurements reports files.
- Turn on or off the unchannelized link label option
chg-mtc-measopts: Used to enable or disable the automatic generation and FTP transfer of scheduled measurement reports to the FTP server.
rept-stat-meas: Reports the status of the Measurements subsystem including card location and state, Alarm level, and Subsystem State.
rept-ftp-meas: Manually initiates generation and FTP transfer of a measurements report from the MCPM card to the FTP server.
rtrv-measopts: Displays the status of Measurements Platform collection, scheduled reports, 15-Minute Measurements collection, CLLI-based file names, and the unchannelized link label.
rtrv-mtc-measopts: Displays the enabled or disabled status of hourly and daily maintenance scheduled reports.

Note:

If a new entity is provisioned in place of a deleted entity, then the measurements for the deleted entity are set to zero. The reported peg counts apply only to the new entity.

E5-OAM Integrated Measurements

The E5-OAM Integrated Measurements feature provides full measurements support for an EAGLE node with up to 2400 links without requiring dedicated cards. The Measurements Platform is required for support of more than 2400 links.

Note:

If the 15-Minute Measurements feature is turned on, then the E5-OAM Integrated Measurements feature supports measurements up to 1200 links, and the Measurements Plaform is required for support of more than 1200 links.

Links that are supported by the Measurements Platform and E5-OAM Integrated Measurements feature include IP associations as shown:

Each low-speed link (LSL) counts as 1 link
Each ATM high speed link (HSL) counts as 1 link
Each SE-HSL counts as 1 link
For IPLIM, each association counts as 1 link
For IPGW, 1 link per card
For IPSG, each association counts as 1 link

The E5-OAM Integrated Measurements feature requires the following hardware and provisioning in the system:

E5-based control cards (E5-MASP cards and E5-MDAL cards)
Ethernet port A provisioned on the E5-MCAP card portions of the E5-MASP cards
The E5-OAM Integrated Measurements feature enabled and turned on
The E5-OAM Integrated Measurements collection option turned on in the MEASOPTS table
A provisioned customer FTP server
To mitigate network failures that could cause lost reports, it is recommended that you provision up to three FTP servers for E5-OAM Integrated Measurements. Refer to the Database Administration - System Management User's Guide for information about configuring the FTP servers for E5-OAM Integrated Measurements. If a network failure is on or near the EAGLE OAM IP link, then a loss of reports on the server is possible. The E5-OAM card will not switch activity if the IP link is unavailable on the active MASP. An alarm is generated, but the role change is a manual action. You can run on-demand reports to retrieve the data.
The EAGLE OA&M IP Security feature, and Secure Shell FTP (SFTP) as a client, if secure transfer is used

After collection of the measurements, scheduled reports are automatically generated and transferred from an E5-MASP card to a customer FTP server using the FTP interface. Existing FTP file server reports are overwritten by subsequent requests that produce the identical file name.

Reports can be scheduled or generated on demand using the following commands:

chg-measopts:
- Turns on the E5-OAM Integrated Measurements collection option
- Turns on or turn off the 15 Minute Measurements collection function
- Enables or disables the automatic generation and FTP transfer of scheduled measurements reports to the FTP server
- Turns on or off the CLLI-based file name option for measurements reports files
- Turn on or off the unchannelized link label option
chg-meas: Enables report generation. The complete command that you must enter so that measurement reports are generated is chg-meas:collect=on.
chg-mtc-measopts: Enables or disables the automatic generation and FTP transfer of scheduled daily and hourly measurement reports to the FTP server.
rept-stat-meas: Reports the status of the measurements subsystem including card location and state, E5-MASP and IP link state, Alarm level, and Subsystem State.
rept-ftp-meas: Manually initiates generation and FTP transfer of a measurements report from the E5-MASP card to the FTP server.
rtrv-measopts: Displays the status of E5-OAM Integrated Measurements collection, scheduled reports, 15-Minute Measurements collection, CLLI-based file names, and unchannelized link label.
rtrv-mtc-measopts: Displays the enabled or disabled status of all FTP scheduled measurements reports.

Note:

If a new entity is provisioned in place of a deleted entity, then the measurements for the deleted entity are set to zero. The reported peg counts apply only to the new entity.

When the E5-OAM Integrated Measurements feature is used in the system,

The rept-meas command cannot be used for the lnp, np, and mapscrn entity types, because the file transfer area (FTA) is disabled. Use the rept-ftp-meas command for those entity types.
Scheduled UI reports are allowed if the system has up to 700 links, and are disabled it the system has more than 700 links.

Data Mirroring

The measurements data that is collected at interval, as well as the derived data that is periodically computed, is stored on the active/primary collection platform and mirrored on the standby/secondary platform. Any MEAS reports generated after the role change are identical to the reports generated before the role change. The duplication of the collected data provides an additional measure of reliability for the Measurements Subsystem.

In the event that the standby/secondary platform is unavailable when the mirroring occurs, that data is retained on the active/primary, but it is not retained on the standby/secondary. If a role change occurs, any data collected while the standby/secondary was unavailable will not be available for reporting. A second role change is required if it is necessary to report the missing data.

Optional 15-Minute Measurements

Optional 15-minute measurements are available when the 15-minute measurement option is on and either the Measurements Platform is configured or the E5-OAM Integrated Measurements feature is turned on. This option can change the duration for 30-minute reports to 15 minutes. The Measurements Platform and the E5-OAM Integrated Measurements feature have the capability to collect and report STP, link, and linkset measurements on a 15-minute basis. All of the measurements available for 30-minute collection are available every 15 minutes when the feature option is operational.

Note:

Scheduled UI reports are disabled when the 15-minute measurements feature is enabled.

The feature is controlled by a measurement option. Turning on the feature requires a part number. The feature cannot be turned off once turned on. It is a Permanently ON feature. Upon turn on, the collection period defaults to the 30-minute option. Refer to the Database Administration - System Management User's Guide for details on implementing the 15-minute measurements feature.

The feature becomes operational when the collection period has been changed to 15 minutes. The collection period is changed from 30 minutes to 15 minutes (and vice versa) by using the chg-measopts:collect15min command. Refer to the Commands User's Guide for detailed usage information. When the 30-minute option is selected, measurements data is collected and reported each half-hour at hh:00 and hh:30. When the 15-minute option is selected, measurements data is collected and reported four times each hour at hh:00, hh:15, hh:30, and hh:45. The current state of the option is displayed with the Measurements Platform and E5-OAM Integrated Measurements feature options. Report types supported by 15-minute measurements are:

systot (STP system totals)
comp (Component)
gtwy (Gateway)
avl (Availability)

After 15-minute measurements collection and reporting is operational, 15-minute reports are retrieved using rept-meas or rept-ftp-meas commands. Refer to the Commands User's Guide for detailed usage information.

Data Collection

The various scenarios for making 15-minute collection operational, and the impact on data collection are shown in Table 2-2. The first column specifies the four quarter-hour intervals during which 15-minute collection could be made operational. The second column identifies the impact of making 15-minute collection operational during the specified time window. If 15-minute collection is made operational during the first or third quarter hour, there is no impact on the collected data. If 15-minute collection is made operational during the second or fourth quarter hour, the data that is collected and stored for that quarter-hour actually represents 30 minutes of data. This is not an error and no measurements data is lost. Rather it is a side effect of making 15-minute collection operational after the previous quarter-hour boundary has already passed.

Table 2-2 Enabling 15-Minute Measurements - Impacts

Time Window for Making 15-Minute Measurements Operational	Impact on Data Collection	Data Loss
xx00 to xx15	15 minutes of data will be collected for the quarter-hour xx15	None
xx15 to xx30	The xx15 interval will contain no data. The xx30 interval will contain 30 minutes of data	None
xx30 to xx45	15 minutes of data will be collected for the quarter-hour xx45	None
xx45 to xx00	The xx45 interval will contain no data. The xx00 interval will contain 30 minutes of data	None

Some quarter-hour measurements data may not be available for 24 hours after making 15-minute collection operational. This condition exists for quarter-hour intervals for which 15-minute collection has not yet occurred. Data that was collected on a 30-minute basis is available for reporting for up to 24 hours after it is collected. After the 15-minute collection option is enabled, this data remains available on a half-hour basis (xx00 and xx30) but is not available on a quarter-hour basis (xx15 and xx45). After the 15-minute collection option has been enabled for 24 hours, all 15-minute measurements data is available on a quarter-hour basis (xx00, xx15, xx30, and xx45).

In addition, full 30-minute data coverage will not be available until 24 hours after making 15-minute collection not operational. Reports for specific periods will always contain the amount of data collected for that period. If SEAS reporting is enabled, for 24 hours after 15-minute measurements are made not operational, 30-minute demand SEAS reports for time periods prior to feature status change will only contain 15 minutes of data, and SEAS will not support reporting at the xx15 and xx45 times.

Also note that in the exception case of making 15-minute collection not operational, if the feature is made not operational in the first 15 minutes of a half-hour (xx00-xx15 or xx30-xx45) and a demand report is requested in the second 15 minutes of a half-hour (xx15-xx30 or xx45-xx60) for period=last (or period unspecified), the report given will be the last 15-minute interval (xx00-xx15 or xx30-xx45), not the last collected 15-minute interval (xx45-xx00 or xx15-xx30). Note that collection did not occur during this 15-minute period, and Measurements data not current will be issued. To get a report for the last collected 15-minute interval, period=specific has to issued with the command with the correct QH/HH value.

If the feature control status of 15-minute measurements is turned on and a report is requested for the active interval (period=active) prior to the next scheduled measurements collection (based on the current 15-minute measurements status), then the data will be correct but the starting time for the period shown in the report will be incorrect. As soon as the next scheduled collection occurs, then active reports will show the correct data and the correct starting time.

A similar limitation also exists for period=last. If the feature control status of 15-minute measurements is turned on and a report is requested for the last interval prior to the next scheduled measurements collection (based on the current 15-minute measurements status), then the start and end times for the period shown in the report will be incorrect. The data presented in the report will correspond to the start and end times. As soon as the next scheduled collection occurs, then period=last reports will show the correct start and end times and the corresponding data for that interval.

If collection has not occurred since changing the operation status, then period=specific needs to be issued to get the last period collected.

Reports

Reports can be scheduled or printed on-demand. Scheduled and on-demand reports are accessible by the following administrative commands:

chg-measopts: Used to enable or disable the automatic generation and FTP transfer of scheduled measurement reports to the FTP server.
rept-ftp-meas: Manually initiates generation and FTP transfer of a measurements report from the MCPM to the FTP server (Measurements Platform) or from the E5-MASP to the FTP server (E5-OAM Integrated Measurements).
rtrv-measopts: Generates a user interface display showing the enabled/disabled status of all FTP scheduled reports.
chg-mtc-measopts: Enables or disables the automatic generation and FTP transfer of scheduled maintenance measurements reports to the FTP server.
rtrv-mtc-measopts: Shows the enabled/disabled status of all hourly and daily scheduled maintenance measurements reports.

Refer to the Commands User's Guide for more information on how to use measurement commands.

Characteristics

Reports have the following characteristics.

Categories
The following are the categories and types of measurement reports collected by the EAGLE:
- Traffic Engineering Reports
  - STP system totals (SYSTOT)
  - Component measurements (COMP)
  - Network management (NM)
- Error Tracking/Troubleshooting Reports
  - Daily availability (AVLD)
  - Day-to-hour availability (AVLDTH)
  - Availability (AVL)
- Maintenance Reports
  - Daily maintenance measurements (MTCD)
  - Day-to-hour maintenance measurements (MTCDTH)
  - Hourly maintenance measurements (MTCH)
- Network Usage Reports
  - Gateway (GTWY)
  - Record Base (RBASE)
- Maintenance Status Reports
  - Maintenance Status Indicators (MTCS)

Entity Types
The following entity types may be reported for a particular category type.
- AIQ: ANSI41 AIQ
- ATINPQ: Any-Time Interrogation Number Portability Query
- DEIR: S13 EIR Interface
- EIR: Equipment Identity Register
- ENUM: EAGLE ENUM Mobile Number Portability and Tier One Address Resolution
- GTTAPATH: GTT Actions per path
- IDPR: IDP Pre-paid Relay Query
- LINK: Signaling link
- LNKSET: Linkset
- LNP: Local number portability
- LSDESTNI: Linkset destination network identifier
- LSONISMT: Per link set, per originating network identifier, per ISUP message type measurements
- LSORIGNI: Linkset originating network identifier
- MAPSCRN: Global Systems for Mobile Communications Mobile Application Part Screening Measurements
- NP: Intelligent network application part-based number portability
- ORIGNI: Originating network identifier
- ORIGNINC: Originating network identifier for network cluster
- SCTPASOC: Per association SCTP layer
- SCTPCARD: Per card SCTP layer
- SFTHROT: SS7 Firewall Throttling GTT Action
- SIP: SIP Number Portability
- STP: All nodes
- TT: Translation type
- UA: Per Application Server/Association UA layer
- VFLEX: Voice Mail Router measurements

Accessible Periods
There are four accessible periods for which measurements may be reported:
1. Last is used to access the previous collection interval.
2. Specific is used to access a specific interval (for example, one of the previous 48 half-hour intervals).
3. Active is used to access measurements for the current collection interval.
4. All is used to access measurements for all collection intervals retained.

LSL and SE-HSL Reports

As of Release 44.0, low-speed MTP2 links and high-speed unchannelized MTP2 links can be identified separately in the relevant reports.

The standard link label is "MTP2", and is applicable to all types of MTP2 links, regardless of the link speed. When the unchlinklabel functionality is provisioned to ON in the chg-measopts command, unchannelized links are labeled with "MTP2-UNCH", while low-speed links retain the "MTP2" label. The -UNCH label is also applied to linksets that contain unchannelized MTP2 links.

The label appears in scheduled and on-demand reports, for UI and FTP.

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:

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.
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).
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.

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.

Report Limitations

The measurement registers of a system total report can store a maximum count of 4294967295 (size of the register), after which the register will roll over to 0. This limitation puts constraint on the number of the following cards that can run at the maximum card TPS in the system, or on the value of maximum TPS that can be processed by the maximum number of those cards allowed in the system:

ENUM
- Up to 12 ENUM cards can run at the maximum advertised TPS (4000) in the system without exceeding the count capacity.
- The maximum allowed 16 ENUM cards can run at a maximum of 3100 TPS in the system without exceeding the count capacity.
- The maximum allowed 16 ENUM cards running at maximum card TPS of 4000 can run for 18 hours before the count capacity is exceeded.
SIP
- Up to 12 SIP cards can run at the maximum advertised TPS (4000) in the system without exceeding the count capacity.
- The maximum allowed 16 SIP cards can run at a maximum of 3100 TPS in the system without exceeding the count capacity.
- The maximum allowed 16 SIP cards running at maximum card TPS of 4000 can run for 18 hours before the count capacity is exceeded.
S13
- Up to six S13 cards can run at the maximum advertised TPS (8000) in the system without exceeding the count capacity.
- The maximum allowed 16 S13 cards can run at a maximum of 3100 TPS in the system without exceeding the count capacity.
- The maximum allowed 16 S13 cards running at maximum card TPS of 8000 can run for nine hours before the count capacity is exceeded.

These limitations do not affect the processing of traffic. If the limitations are exceeded, then the value of the measurements register will roll over after reaching its maximum value and the pegging will be incorrect.