![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Table Of Contents
Database Tables: Formats and Field Contents
Database Tables: Formats and Field Contents
Each Raw Data Record (RDR) is sent to the Cisco Service Control Management Suite (SCMS) Collection Manager (CM). On the CM, adapters convert the RDRs and store them in database tables. There is a separate table for each RDR type. This chapter presents these tables and their columns (field names and types).
For additional information, such as RDR structure, RDR column and field descriptions, and how the RDRs are generated, see Raw Data Records Overview .
Database Tables Overview
Each RDR is routed to the appropriate adapter—the JDBC Adapter or the Topper/Aggregator (TA) Adapter—converted, and written into a database table row. There is a separate table for each RDR type, with a column designated for each RDR field.
In addition to the RDR fields that are specific to each RDR type, the tables RPT_NUR, RPT_SUR, RPT_PUR, RPT_LUR, and RPT_TR contain two universal columns: TIME_STAMP and RECORD_SOURCE. The following values are placed in these two universal columns (field numbers 1 and 2, respectively):
•
TIME_STAMP—The RDR time stamp assigned by the SCMS-CM. The field is in UNIX time_t format, which is the number of seconds since midnight of 1 January 1970.
•
RECORD_SOURCE—Contains the IP address of the Service Control Engine (SCE) platform that generated the RDR.
The IP address is in 32-bit binary format (displayed as a 4-byte integer).
Table RPT_NUR
Database table RPT_NUR stores data from SUBSCRIBER_USAGE_RDRs.
Note
This table is not part of the default configuration.
These RDRs have the tag 4042321920 .
Table RPT_SUR
Database table RPT_SUR stores data from REALTIME_SUBSCRIBER_USAGE_RDRs.
These RDRs have the tag 4042321922 .
Table RPT_PUR
Database table RPT_PUR stores data from PACKAGE_USAGE_RDRs.
These RDRs have the tag 4042321924 .
Table RPT_LUR
Database table RPT_LUR stores data from LINK_USAGE_RDRs.
These RDRs have the tag 4042321925 .
Table RPT_TR
Database table RPT_TR stores data from TRANSACTION_RDRs.
These RDRs have the tag 4042321936 .
Table RPT_MEDIA
Database table RPT_MEDIA stores data from MEDIA_FLOW_RDRs.
These RDRs have the tag 4042323052 .
Table RPT_MALUR
Database table RPT_MALUR stores data from MALICIOUS_TRAFFIC_PERIODIC_RDRs.
These RDRs have the tag 4042322000 .
Table RPT_TOPS_PERIOD0
The Topper/Aggregator (TA) Adapter generates database table RPT_TOPS_PERIOD0 for its shorter aggregation interval (by default, one hour).
Table 4-8 Columns for Table RPT_TOPS_PERIOD0
Field Name TypeRECORD_SOURCE
Number
METRIC_ID
Number
SUBS_USG_CNT_ID
Number
TIME_STAMP
DateTime
AGG_PERIOD
Number
SUBSCRIBER_ID
String
CONSUMPTION
Number
For each Top Report, the TA Adapter sorts the subscriber/consumption pairs from the highest consumption to lowest. At the end of each report is a statistic giving the sum of all subscribers for this metric.
If the report is empty, typically when no traffic was reported for the designated service/metric pair during the aggregation period, the DB will still be updated, but the only row in the report will be the final row showing a total consumption of zero. The DB is updated to avoid the perception in the Cisco Service Control Application (SCA) Reporter that the report is not there because of a malfunction.
The possible values for the field METRIC_ID are presented in the following table.
Table 4-9 Metric_ID Values
Metric_ID Metric0
Up Volume
1
Down Volume
2
Combined Volume
3
Sessions
4
Seconds
Table RPT_TOPS_PERIOD1
The Topper/Aggregator (TA) Adapter generates database table RPT_TOPS_PERIOD1 for its longer aggregation interval (by default, 24 hour).
For each Top Report, the TA Adapter sorts the subscriber/consumption pairs from the highest consumption to lowest. At the end of each report is a statistic giving the sum of all subscribers for this metric.
If the report is empty, typically when no traffic was reported for the designated service/metric pair during the aggregation period, the DB will still be updated, but the only row in the report will be the final row showing a total consumption of zero. The DB is updated to avoid the perception in the SCA Reporter that the report is not there because of a malfunction.
The possible values for the field METRIC_ID are presented in the following table.
Table 4-11 Metric_ID Values
Metric_ID Metric0
Up Volume
1
Down Volume
2
Combined Volume
3
Sessions
4
Seconds
Table INI_VALUES
Database table INI_VALUES is updated whenever the service configuration is applied to the SCE platform. This table contains, for each SCE IP address, mappings between numeric identifiers and textual representation for services, packages, and other service configuration components. The mapping is represented as a standard properties file in string form, where each mapping file is stored in one row. The SCA Reporter uses the mappings contained in this table.
Table VLINK_INI
Database table VLINK_INI is updated when the CM utility
update_vlinks.sh
is run. This table contains the name and id of each virtual link defined in the SCE platform. The SCA Reporter uses the mappings contained in this table for the Virtual Links reports.
Table CONF_SE_TZ_OFFSET
Database table CONF_SE_TZ_OFFSET contains the time-zone offset in minutes for each SCE platform's clock as configured by the
select-sce-tz.sh
script.
Table 4-14 Columns for Table CONF_SE_TZ_OFFSET
Field Name TypeTIME_STAMP
DateTime
OFFSET_MIN
Number
Posted: Thu May 31 05:47:31 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.