Go to primary content
Oracle® Communications EAGLE Measurements Reference
Release 46.7
E97337 Revision 1
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

ENUM MTCD Report

The ENUM measurements specify the entity type enum and include four daily reports:

The retention period is 24 hours.

FTP Example Command:

rept-ftp-meas:type=mtcd:enttype=enum

Table 3-117 Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM System Level Measurements

Event Name Description Unit
ENUMQRYRX Total number of ENUM queries received Peg count
ENUMNAPTRRX Total number of NAPTR queries received Peg count
ENUMNSRX Total number of NS queries received Peg count
ENUMCNAMERX Total number of CNAME queries received Peg count
ENUMQRYRJTD Total number of ENUM queries rejected by ENUM server Peg count
ENUMCNGDISC Total number of ENUM queries discarded due to congestion Peg count
ENUMACLDISC Total number of ENUM queries discarded due to ACL validation failure Peg count
ENUMTXRC0 Total number of successful ENUM responses sent Peg count
ENUMTXRC1 Total number of ENUM error responses sent due to ENUM query format error Peg count
ENUMTXRC2 Total number of ENUM error responses sent due to ENUM server failure Peg count
ENUMTXRC3 Total number of ENUM error responses sent due to non-existent domain error Peg count
ENUMTXRC4 Total number of ENUM error responses sent due to not implemented error Peg count
ENUMTXRC5 Total number of ENUM error responses sent due to refusal by ENUM server Peg count
ENUMTXDEFPR Total number ENUM responses sent with default ENUM profile Peg count

STATUS

Indication of Data Validity:
  • K indicates good data
  • I indicates incomplete interval
  • N indicates data not current

Status

Table 3-118 Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Card Level Measurements

Event Name Description Unit
ENUMCQRYRX Total number of ENUM queries received Peg count
ENUMCNAPTRX Total number of NAPTR queries received Peg count
ENUMCNSRX Total number of NS queries received Peg count
ENUMCCNAMRX Total number of CNAME queries received Peg count
ENUMCQRRJTD Total number of ENUM queries rejected by ENUM server Peg count
ENUMCCNGDSC Total number of ENUM queries discarded due to congestion Peg count
ENUMCACLDSC Total number of ENUM queries discarded due to ACL validation failure Peg count
ENUMCTXRC0 Total number of successful ENUM responses sent Peg count
ENUMCTXRC1 Total number of ENUM error responses sent due to ENUM query format error Peg count
ENUMCTXRC2 Total number of ENUM error responses sent due to ENUM server failure Peg count
ENUMCTXRC3 Total number of ENUM error responses sent due to non-existent domain error Peg count
ENUMCTXRC4 Total number of ENUM error responses sent due to not implemented error Peg count
ENUMCTXRC5 Total number of ENUM error responses sent due to refusal by ENUM server Peg count
ENUMCTXDEFP Total number ENUM responses sent with default ENUM profile Peg count

STATUS

Indication of Data Validity:
  • K indicates good data
  • I indicates incomplete interval
  • N indicates data not current

Status

Table 3-119 Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Entity Level Measurements

Event Name Description Unit

ENUMENTMSGS

Total number of ENUM queries received or ENUM responses sent per entity

Peg count

STATUS

Indication of Data Validity:
  • K indicates good data
  • I indicates incomplete interval
  • N indicates data not current

Status

Table 3-120 Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM ACL Level Measurements

Event Name Description Unit
ENUMACLQRCV Total number of ENUM queries received Peg count
ENUMACLQRJD Total number of ENUM queries rejected by ENUM server Peg count
ENUMACLRC0 Total number of successful ENUM responses sent Peg count
ENUMACLRC1 Total number of ENUM error responses sent due to ENUM query format error Peg count
ENUMACLRC2 Total number of ENUM error responses sent due to ENUM server failure Peg count
ENUMACLRC3 Total number of ENUM error responses sent due to non-existent domain error Peg count
ENUMACLRC4 Total number of ENUM error responses sent due to not implemented error Peg count
ENUMACLRC5 Total number of ENUM error responses sent due to refusal by ENUM server Peg count

STATUS

Indication of Data Validity:
  • K indicates good data
  • I indicates incomplete interval
  • N indicates data not current

Status

Example Output File Names:

Daily ENUM system totals measurements report mtcd-enumsys_yyyymmdd_2400.csv
Daily ENUM per card measurements report mtcd-enumcard_yyyymmdd_2400.csv
Daily ENUM per entity measurements report mtcd-enument_yyyymmdd_2400.csv
Daily ENUM per acl measurements report mtcd-enumacl_yyyymmdd_2400.csv

FTP example output file format for system total report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"
"tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:32","MST ","DAILY MAINTENANCE MEASUREMENTS ON ENUM 
SYSTEM","LAST","2014-08-22","00:00:00","24:00:00",1

"STATUS","ENUMQRYRX","ENUMNAPTRRX","ENUMNSRX","ENUMCNAMERX","ENUMQRYRJTD","ENUMCNGDISC","ENUMACLDISC",
"ENUMTXRC0","ENUMTXRC1","ENUMTXRC2","ENUMTXRC3","ENUMTXRC4","ENUMTXRC5","ENUMTXDEFPR"
"K",2134,0,2134,0,0,0,0,2134,0,0,0,0,0,0

Assuming each data line will be:

4 char status + 14 * (6 char data) + 2 = 90 chars

Typical file size is:

Table 3-121 Typical File Size: mtcd-enumsys.csv

System header   Report header   Report data = File Size

250

+

189

+

90 bytes

=

529 bytes

FTP example output file format for per card report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"
"tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:35","MST ","DAILY MAINTENANCE MEASUREMENTS ON ENUM 
PER-CARD","LAST","2014-08-22","00:00:00","24:00:00",2

"STATUS","LOC","ENUMCQRYRX","ENUMCNAPTRX","ENUMCNSRX","ENUMCCNAMRX","ENUMCQRRJTD","ENUMCCNGDSC","ENUMCACLDSC",
"ENUMCTXRC0","ENUMCTXRC1","ENUMCTXRC2","ENUMCTXRC3","ENUMCTXRC4","ENUMCTXRC5","ENUMCTXDEFP"
"K","1101",2134,0,2134,0,0,0,0,2134,0,0,0,0,0,0
"K","1105",0,0,0,0,0,0,0,0,0,0,0,0,0,0

Assuming each data line will be:

4 char status + 7 char (card) + 14 * (6 char data) + 2 = 95 chars

Typical file size is:

Table 3-122 Typical File Size: mtcd-enumcard.csv

System header   Report header   Report data (250 card) = File Size

250

+

203

+

23750 bytes

=

24203 bytes

FTP example output file format for per entity report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"
"tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:33","MST ","DAILY MAINTENANCE MEASUREMENTS ON ENUM 
PER-ENTITY","LAST","2014-08-22","00:00:00","24:00:00",2

"STATUS","ENTITY ID","SDN","EDN","ENUMENTMSGS"
"K","123456789012345","","",0
"K","123456789123456","","",2134

Assuming each data line will be:

4 char status + 3* (18 char Entity ID/SDN/EDN) + (6 char data) + 2 = 66 chars

Typical file size is:

Table 3-123 Typical File Size: mtcd-enument.csv

System header   Report header   Report data (1024 entries) = File Size

250

+

48

+

67584 bytes

=

67882 bytes

FTP example output file format for per ACL report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"
"tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:34","MST ","DAILY MAINTENANCE MEASUREMENTS ON ENUM 
PER-ACL","LAST","2014-08-22","00:00:00","24:00:00",1

"STATUS","IP ADDRESS","ENUMACLQRCV","ENUMACLQRJD","ENUMACLRC0","ENUMACLRC1","ENUMACLRC2","ENUMACLRC3",
"ENUMACLRC4","ENUMACLRC5"
"K","10.*.*.*",2134,0,2134,0,0,0,0,0

Assuming each data line will be:

4 char status + 18 char (IP Address) + 8 * (6 char data) + 2 = 72 chars

Typical file size is:

Table 3-124 Typical File Size: mtcd-enumacl.csv

System header   Report header   Report data (100 entries) = File Size

250

+

129

+

7200 bytes

=

7579 bytes