Cisco Cisco Mobility Unified Reporting Administrator's Guide
Configuring Chassis for Mobility Unified Reporting System
▀ Configuration
▄ Cisco Mobility Unified Reporting System Installation and Administration Guide
64
OL-27216-09
file name <file_name> rotation volume <file_size_bytes> rotation time
<file_complete_seconds> rotation num-records <records_number> storage-limit
<storage_limit_bytes> headers reset-indicator edr-format-name trap-on-file-delete
compression gzip file-sequence-number rulebase-seq-num
<file_complete_seconds> rotation num-records <records_number> storage-limit
<storage_limit_bytes> headers reset-indicator edr-format-name trap-on-file-delete
compression gzip file-sequence-number rulebase-seq-num
cdr [ push-interval <interval> | remove-file-after-transfer | transfer-mode { pull
| push primary { encrypted-url <enc_url> | url <url> } [ secondary { encrypted-secondary-
url <enc_sec_url> | url <sec_url> } ] } + | use-harddisk ]
| push primary { encrypted-url <enc_url> | url <url> } [ secondary { encrypted-secondary-
url <enc_sec_url> | url <sec_url> } ] } + | use-harddisk ]
end
Notes:
The
<context_name>
must be the context specified for accounting.
EDR type configuration is optional. The EDR types can be either
charging
or
reporting
. The
charging
keyword is the default setting.
For MUR reporting needs, use the
reporting
keyword for the EDR type.
The
cdr use-harddisk
command is only available on the ASR 5000 platform.
The
cdr use-harddisk
command specifies storing files on the hard disk. The reporting server will download
these files through the SPIO interface on the SMC and will delete the files after successful retrieval.
The
edr-format-name
keyword must be configured to distinguish between different EDRs. The EDR file
name must be configured in an accepted format so that the Offline Subscriber Reporting functionality can be
used effectively. For information on this functionality and the EDR file name configuration recommendations,
see the Cisco Mobility Unified Reporting System Online Help documentation.
used effectively. For information on this functionality and the EDR file name configuration recommendations,
see the Cisco Mobility Unified Reporting System Online Help documentation.
The files will be compressed to save storage and transmission bandwidth.
For the PULL model, an external device like L-ESS is used to pull the EDR files from the chassis via SFTP.
Whereas, for the PUSH model, the chassis is configured to push the files to the required destination.
Important:
The chassis automatically creates /edr and /udr directories on the destined path
on MUR server when you configure it to push the files.
The values recommended for
rotation volume
and
rotation time
keywords are 40 MB and 300 seconds
respectively.
Important:
In RHEL-based deployments, L-ESS is NOT required as the Enhanced Charging Services (ECS)
module can be configured to push the xDRs directly to the MUR reporting server. Push from ASR chassis is the Cisco
recommended deployment model. Currently L-ESS is supported only on Solaris platforms. For information on the L-
ESS installation instructions, refer to the ESS Installation and Administration Guide. Existing deployments where L-
ESS is installed, to pull EDRs from chassis, may continue with their deployment model in the 12.0 version of MUR
Software Release and later.
recommended deployment model. Currently L-ESS is supported only on Solaris platforms. For information on the L-
ESS installation instructions, refer to the ESS Installation and Administration Guide. Existing deployments where L-
ESS is installed, to pull EDRs from chassis, may continue with their deployment model in the 12.0 version of MUR
Software Release and later.
The following is a sample EDR PUSH configuration.
configure
context test
edr-module active-charging-service
reporting