Oracle® Communications EAGLE Measurements Reference Release 46.7 E97337 Revision 1 |
|
![]() Previous |
![]() Next |
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.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.
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.