| Oracle® Communications Measurements Reference Release 46.6 E93320 Revision 1 |
|
 Previous |
 Next |
The enttype=mapscrn entity generates two separate reports per period.
The reports for basic OAM measurements are generated as CSV files in the FTA. The command example generates the following daily measurement reports when the GSMMAP Screening feature is activated:
Daily MAP Screening System Wide Measurements
Daily MAP Screening Measurements Per Server
The command example generates the following daily measurement reports when the GSMMAP/Enhanced GSMMAP Screening feature is activated:
Daily MAP Screening System Wide Measurements
Daily MAP Screening Measurements Per Path
All the FTP reports are listed together.
FTP: rept-ftp-meas:type=mtcd:enttype=mapscrn
Note:
When MTP MAP Screening is enabled and on, the registers in Table 3-81 and Table 3-84 include the sum total of MTP-routed and GTT-routed messages for the particular event.Table 3-81 Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening System Wide Measurements
| Event Name | Description | Unit |
|---|---|---|
| MSCRNPASS |
Total number of messages that Passed MAP screening |
count |
| MSCRNRJNE |
Total number of messages that got Rejected by MAP screening because an entry was not found in the MAP screening table (i.e., rejected as System wide MAP Opcode action is DISCARD) |
count |
| MSCRNRJFP |
Total number of messages that got Rejected by MAP screening due to forbidden parameters in the message. |
count |
| MSCRNPAFP |
Total number of messages that contained the forbidden parameter but were not rejected due to Screening action set as PASS. |
count |
| MSCRNPANE |
Total number of messages, where an entry was not found in the MAP screening table but the Message was not rejected as screening action was marked as PASS (i.e., not rejected as System wide MAP Opcode action is PASS) |
count |
| MSCRNRJOP |
Total number of message that got rejected as Message MAP Opcode was not found in the MAP Opcode table (system wide action - DISCARD for the non matching OPCODEs) |
count |
| MSCRNDUP |
Total number of messages that were selected by MAP Screening for the Duplicate screening action. |
count |
| MSCRNFOR |
Total number of messages thate were selected by MAP Screening for the Forward screening action. |
count |
| MSCRNDAD |
Total number of messages thate were selected by MAP Screening for the Duplicate and Discard screening action. |
count |
| STATUS |
Indication of Data Validity:
|
status |
Server Entity Identification information in Table 3-82 is used to clarify the server. The Maintenance MAP Screening Per Server Measurements are applicable.
Table 3-82 Server Entity Identification
| Entity Name | Description |
|---|---|
| SERVER |
The screened origination address of the calling party address (CGPA) assigned when the GSM MAP screen was entered. |
| NP |
The screened number plan value (NPV) assigned to the server address when the GSM MAP screen was entered. This field is filled with the default identifier * if no value was assigned. |
| NAI |
The screened nature of address value (NAIV) assigned to the server address when the GSM MAP screen was entered. This field is filled with the default identifier * if no value was assigned. |
| OPCODE |
The operation code number assigned when the GSM MAP opcode was entered. |
| Measurements does not report entries created for a range of addresses. |
Server Path Entity Identification information in Table 3-83 is used to clarify the path. The Maintenance MAP Screening Per Path Measurements are applicable.
Table 3-83 Path Entity Identification
| Entity Name | Description |
|---|---|
| PATH |
The screened origination address of the calling party address (CGPA-NP-NAI), or a combination of screened destination address of the called party address (CDPA-NP-NAI) and the screened origination addresses assigned when the GSM MAP screen was entered. The possible fields within the path are delimited as follows to allow for efficient sorting: • When both the origination and destination addresses are present (as either single server entries or provisioned wildcard entries) the origination address is preceded by a carat (^) and the destination address is preceded by a "greater than" sign (>): ^CGPA-NP-NAI>CDPA-NP-NAI • When only the origination address is present (occurs when the CDPA is a default wildcard) it is preceded by a "less than" sign (<): <CGPA-NP-NAI |
| CGPA |
The calling party global title address assigned when the GSM MAP screen was entered. Any or all of the three fields (GTA, NP, NAI) can be filled with the identifier (*) if a wildcard value is assigned for that field. There is no default wildcard value for the CGPA. |
| CDPA |
The called party global title address assigned when the GSM MAP screen was entered. Any or all of the three fields (GTA, NP, NAI) can be filled with the identifier (*) if a wildcard value is assigned for that field. If the CDPA value is not assigned, the default wildcard value, which is not printed, is assumed. |
| NP |
The screened number plan value (NPV) assigned to the path address when the GSM MAP screen was entered. The identifier (*) is used to signify a wildcard NP. |
| NAI |
The screened nature of address value (NAIV) assigned to the path address when the GSM MAP screen was entered. The identifier (*) is used to signify a wildcard NAI. |
| OPCODE |
The operation code number assigned when the GSM MAP opcode was entered. The identifier (*) is used to signify a wildcard opcode. |
Note:
Measurements does not report entries created for a range of addresses.
Measurements does not report default wildcard CDPA address in entries containing them.
There can never be a default wildcard CGPA entry. All wildcard CGPA entries must be explicitly provisioned. There can never be an entry with only a CDPA path listed.
The string formats were designed to allow efficient automated post processing of measurements reports. A brief note explaining the format is included in the report.
Table 3-84 Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening Per Server Measurements
| Event Name | Description | Unit |
|---|---|---|
| MSCRNPASS |
Total number of messages that Passed MAP screening |
count |
| MSCRNRJFP |
Total number of messages that got Rejected by MAP screening due to forbidden parameters in the message. |
count |
| MSCRNDUP |
Total number of messages per server that were selected by MAP Screening for the Duplicate screening action. |
count |
| MSCRNFOR |
Total number of messages per server that were selected by MAP Screening for the Forward screening action. |
count |
| MSCRNDAD |
Total number of messages per server that were selected by MAP Screening for the Duplicate screening action. |
count |
| MSCRNPAFP |
Total number of messages that contained the forbidden parameter but were not rejected due to Screening action set as PASS. |
count |
| STATUS |
Indication of Data Validity:
|
status |
FTA Reports
Daily MAP Screening System Wide Measurements
FTA Example Output File Name: SAT_MAP.csv
FTA Example Output File Format:
"e1061001 10-08-22 00:01:03 EST EAGLE5 42.0.0-63.33.0 " "TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON MAPSCRN SYSTEM" "REPORT PERIOD: LAST" "REPORT INTERVAL: 10-08-21, 00:00:00 THROUGH 23:59:59 " "Measurement data represents an incomplete interval." "MSCRNPASS","MSCRNRJOP","MSCRNRJNE","MSCRNRJFP","MSCRNPAFP","MSCRNPANE","MSCRNFOR","MSCRNDUP","MSCRNDAD", 0,0,0,0,0,0,0,0,0,
Daily MAP Screening Measurements Per Server
Example output File Name: SAT_SERV.csv
Example Output File Format:
"e1061001 10-08-22 00:01:03 EST EAGLE5 42.0.0-63.33.0 " "TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON MAPSCRN PER-SERVER" "REPORT PERIOD: LAST" "REPORT INTERVAL: 10-08-21, 00:00:00 THROUGH 23:59:59 " "Measurement data represents an incomplete interval." "NUMBER OF ENTIDS: 14" "SERVER-NP-NAI-OPCODE","MSCRNPASS","MSCRNRJFP","MSCRNFOR","MSCRNDUP","MSCRNDAD",MSCRNPAFP "123456789012345-*-*-0",0,0,0,0,0,0 "234567890123456-*-*-0",0,0,0,0,0,0 "345678901234567-*-*-0",0,0,0,0,0,0 "456789012345678-*-*-0",0,0,0,0,0,0 "567890123456789-*-*-0",0,0,0,0,0,0 "678901234567890-*-*-0",0,0,0,0,0,0 "789012345678901-*-*-0",0,0,0,0,0,0 "123456789012345-*-*-1",0,0,0,0,0,0 "234567890123456-*-*-1",0,0,0,0,0,0 "345678901234567-*-*-1",0,0,0,0,0,0 "456789012345678-*-*-1",0,0,0,0,0,0 "567890123456789-*-*-1",0,0,0,0,0,0 "678901234567890-*-*-1",0,0,0,0,0,0 "789012345678901-*-*-1",0,0,0,0,0,0
FTP Reports
Daily MAP Screening System Wide Measurements
FTP Example Output File Name: mtcd-map_19990116_2400.csv
FTP Example Output File Format:
"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART", "IVALEND","NUMENTIDS" "e1061001","EAGLE5 42.0.0-63.33.0","2010-08-21","00:00:58","EST ","DAILY MAINTENANCE MEASUREMENTS ON MAPSCRN SYSTEM","LAST","2010-08-20","00:00:00","24:00:00",1 "STATUS","MSCRNPASS","MSCRNRJOP","MSCRNRJNE","MSCRNRJFP","MSCRNPAFP","MSCRNPANE", "MSCRNFOR","MSCRNDUP","MSCRNDAD" "K",0,0,0,0,0,0,0,0,0,
Typical file size is:
Table 3-85 Typical File Size: mtcd-map.csv
| System header | + | Report header | + | Report data | = | File Size |
|---|---|---|---|---|---|---|
| 250 |
+ |
116 |
+ |
60 |
= |
426 bytes |
Daily MAP Screening Measurements Per Path
FTP Example Output File Name: mtcd-path_19990116_2400.csv
FTP Example Output File Format:
"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS" "e1061001","EAGLE5 42.0.0-63.33.0","2010-08-21","00:00:59","EST ","DAILY MAINTENANCE MEASUREMENTS ON MAPSCRN PER-SERVER","LAST","2010-08-20","00:00:00","24:00:00",11 "For a path containing CGPA only, PATH-OPCODE = <CGPA-NP-NAI-OPCODE" "For a path containing both CGPA and CDPA, PATH-OPCODE = ^CGPA-NP-NAI>CDPA-NP-NAI-OPCODE" "STATUS","PATH-OPCODE","MSCRNPASS","MSCRNRJFP","MSCRNFOR","MSCRNDUP","MSCRNDAD","MSCRNPAFP" "K","<123456789012345-*-*-0",0,0,0,0,0,0 "K","<234567890123456-*-*-0",0,0,0,0,0,0 "K","<345678901234567-*-*-0",0,0,0,0,0,0 "K","<456789012345678-*-*-0",0,0,0,0,0,0 "K","<567890123456789-*-*-0",0,0,0,0,0,0 "K","<678901234567890-*-*-0",0,0,0,0,0,0 "K","<789012345678901-*-*-0",0,0,0,0,0,0 "K","<123456789012345-*-*-1",0,0,0,0,0,0 "K","<234567890123456-*-*-1",0,0,0,0,0,0 "K","<345678901234567-*-*-1",0,0,0,0,0,0 "K","<456789012345678-*-*-1",0,0,0,0,0,0
Assuming each data line will be:
4 char status + 40 char PATH-OPCODE + 6*(6 char data) + 2 = 82 chars
For a report of 20 paths, the typical file size is:
Table 3-86 Typical File Size: mtcd-path.csv
| System header | + | Report header | + | Report data | = | File Size |
|---|---|---|---|---|---|---|
| 250 |
+ |
251 |
+ |
1640 |
= |
2141 bytes |
