6 Measurements
This chapter describes the measurements that can be collected and generated for the G-Flex feature, and the methods that can be used for generating reports for G-Flex measurements.
6.1 G-Flex Measurements
- OAM-based (UI) measurements collection - G-Flex measurements are available using the File Transfer Area (FTA) and not directly to EAGLE UI terminals, when the E5-OAM Integrated Measurements feature is not on.
- The Measurements Platform feature enabled and the Measurements Platform collection option on
- The E5-OAM Integrated Measurements feature enabled and on and the E5-OAM Integrated Measurements collection option on
15 Minute Measurements can be used with the Measurements Platform or E5-OAM Integrated Measurements
Refer to Measurements Reference for descriptions of collection methods, measurements, and measurements reports
Refer to Commands User's Guide for descriptions of the commands used to enable and turn on features, turn on measurements collection options, and schedule and generate measurements reports.
Refer to the procedures in the Database Administration - System Management User's Guide to configure the Measurements Platform feature or E5-OAM Integrated Measurements feature for use with G-Flex.
The G-Flex MSU measurements shown in Table 6-1 are supported for the G-Flex feature. No G-Flex measurements are counted when the G-Flex service is OFFLINE.
Table 6-1 G-Flex MSU Measurements
| Event Name | Description |
|---|---|
|
GFGTMATCH |
G-Flex GTTs with Match – The total number of G-Flex Global Title Translation successfully completed. |
|
GFGTNOMCH |
G-Flex GTTs No Match – The total number of G-Flex Global Title Translations completed that did not match an entry in the RTDB. |
|
GFGTNOLKUP |
G-Flex GTTs No Look-up – The total number of G-Flex Global Title Translations that could not be looked up in the RTDB because of some error. Note: This counter is not available using |
The measurement events shown in Table 6-2 are included in the STP Daily Maintenance (MTCD) and STP Day-to-Hour (MTCDTH) measurement reports and include peg counts for G-FLEX MSUs. These reports are similar to those used for GTT.
The existing GTT/SCCP measurements are used for both GTT and G-Flex and appear in the same reports. This implementation does not discriminate between the MSSCCPFL, GTTUN0NS, GTTUN1NT, or GTTPERFD pegs for G-Flex or GTT applications. For example, a search failure could result from a problem in either the RTDB or GTT database. G-Flex SCCP Service Re-Route Capability will count GTT measurements if GTT is performed.
Table 6-2 STP Daily and Day-to-Hour Measurements that include Counts for G-Flex MSUs
| Event Name | Description |
|---|---|
| MSSCCPFL |
MSUs discarded due to SCCP routing failure. Also includes G-Flex MSUs that got a match from either the RTDB or GTT database, but cannot be routed because of PC (Point Code) or SS (Subsystem) congestion, PC or SS unavailable, SS unequipped, or an unqualified error. |
| GTTUN0NS |
GTT unable to perform; no such type. Also includes G-Flex GTT MSUs that did not match on new selectors (GTI, NP, NAI) in addition to ones not matching on TT. |
| GTTUN1NT |
GTT unable to perform: no translation on this address. Also includes G-Flex MSUs that fell through to GTT, obtained a selector match but still did not get a match on the GTA. |
| GTTPERFD |
Number of GTTs performed. Also includes G-Flex MSUs that got a match in either the RTDB or GTT database. These measurements can also be used to determine the following:
|