Go to primary content
Oracle® Communications Measurements Reference
Release 46.6
E93320 Revision 1
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

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:

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.