Cisco Cisco Packet Data Interworking Function (PDIF) Guida Alla Risoluzione Dei Problemi
UDR Module Configuration Mode Commands
▀ cdr
▄ Cisco ASR 5000 Series Command Line Interface Reference
OL-22948-01
Usage
Use this command to configure how charging data records (CDR) are moved and stored.
On the ASR 5000 chassis, run this command only from the local context. Running in any other context would
fail and deliver an error message.
The
On the ASR 5000 chassis, run this command only from the local context. Running in any other context would
fail and deliver an error message.
The
keyword is only available on the ASR 5000 system. This command can be run only in
a context where CDRMOD is running. Configuring in any other context will result in failure with the
message ―Failure: Please Check if CDRMOD is running in this context or not.‖
This config can be applied either in the EDR/UDR module, but will be applicable both to the EDR and UDR
modules. Configuring in one of the modules prevents the configuration to be done in the other module.
If PUSH transfer mode is selected, the L-ESS server URL to which the CDR files need to be transferred to
must be specified. The configuration allows a primary and a secondary server to be configured. Configuring
the secondary server is optional. Whenever a file transfer to the primary server fails for four consecutive
times, the files will be transferred to the secondary server. The transfer will switch back to the original
primary server when:
message ―Failure: Please Check if CDRMOD is running in this context or not.‖
This config can be applied either in the EDR/UDR module, but will be applicable both to the EDR and UDR
modules. Configuring in one of the modules prevents the configuration to be done in the other module.
If PUSH transfer mode is selected, the L-ESS server URL to which the CDR files need to be transferred to
must be specified. The configuration allows a primary and a secondary server to be configured. Configuring
the secondary server is optional. Whenever a file transfer to the primary server fails for four consecutive
times, the files will be transferred to the secondary server. The transfer will switch back to the original
primary server when:
Four consecutive transfer failures to the secondary server occur
After switching from the primary server, 30 minutes elapses
When changing
from pull to push, disable the PULL from L-ESS and then change the
transfer mode to push. Make sure that the push server URL configured is accessible from the local context.
Also, make sure that the base directory that is mentioned contains udr directory created within it.
When changing
Also, make sure that the base directory that is mentioned contains udr directory created within it.
When changing
from push to pull, after changing, enable PULL on the L-ESS. Any of the
ongoing PUSH activity will continue till all the scheduled file transfers are completed. If there is no PUSH
activity going on at the time of this configuration change, all the PUSH related configuration is nullified
immediately.
activity going on at the time of this configuration change, all the PUSH related configuration is nullified
immediately.
Example
The following command configures the system to retain a copy of the data file after it has been transferred to the storage
location:
The following command configures the system to retain a copy of the data file after it has been transferred to the storage
location: