cdr
This command allows you to configure EDR/UDR file transfer parameters.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration > UDR Module Configuration
configure > context context_name > udr-module active-charging-service
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-udr)# Syntax
cdr { purge { storage-limit storage_limit | time-limit time_limit } [ max-files max_records_to_purge ] | push-interval push_interval | push-trigger space-usage-percent trigger_percentage | remove-file-after-transfer | transfer-mode { pull [ module-only ] | push primary { encrypted-url encrypted_url | url url } [ [ max-files max_records ] [ max-tasks task_num ] [ module-only ] [ secondary { encrypted-secondary-url encrypted_secondary_url | secondary-url secondary_url } ] [ source-address ip_address ] [ via local-context ] + ] | use-harddisk }
default cdr [ purge | push-interval | push-trigger space-usage-percent | remove-file-after-transfer | transfer-mode [ pull [ module-only] | push primary via ] | use-harddisk ] +
no cdr [ purge | remove-file-after-transfer | use-harddisk ] + | [cdr push-count push_count default cdr push-count] default
Configures the default setting for the specified keyword(s):
-
purge : Disabled
-
push-interval : 300 seconds
-
push-trigger : 80 percent
-
remove-file-after-transfer : Disabled
-
transfer mode : Pull
-
push via : line cardMIO is used for push
-
use-harddisk : Disabled
 Important |
The use-harddisk keyword is only available on ASR 5000 chassis. |
no
If previously configured, disables the specified configuration:
-
purge : Disables purging of records.
-
remove-file-after-transfer : Retains a copy of the file even after it has been pushed or pulled to another server.
-
use-harddisk : Disables data storage on the SMC hard disk.
Important
The use-harddisk keyword is available only on the ASR 5000 chassis.
-
push-count push_count : Specifies the number of EDR/CDR/UDR files transferred in each EDR/UDR push SFTP session. Default value is "1". push_count is configured as an integer value between 1 and 32, inclusive.
purge { storage-limit storage_limit | time-limit time_limit } [ max-files max_records_to_purge ]
Specifies to purge/delete the UDR records based on "time" or "volume" limit.
When the configured threshold limit is reached on the hard disk drive, the records that are created dynamically in the /mnt/hd-raid/data/records/ directory are automatically deleted. Files that are manually created should be deleted manually.
-
storage-limit storage_limit : Specifies to start deleting files when the specified megabytes of space is used for storage.
storage_limit specifies the volume limit for the record files, in megabytes, and must be an integer from 10 through 143360.
-
time-limit time_limit : Specifies to start deleting files older than the specified time limit.
time_limit specifies the time limit for the record files, and must be an integer from 600 through 2592000.
-
max-files max_records_to_purge : Specifies the maximum number of records to purge.
max_records_to_purge can be 0, or an integer from 1000 through 10000. If the value is set to 0, during each cycle, the records will be deleted until the purge condition is satisfied. If the value is set between 1000 and 10000, during each cycle, the records will be deleted until either the purge condition is satisfied or the number of records deleted equals the configured max-files value.
Default: 0
push-interval value
Specifies the transfer interval (in seconds) to push UDR/EDR files to an external file server.
value must be an integer from 60 through 3600.
Default: 300
push-trigger space-usage-percent trigger_percentage
Specifies the UDR/EDR disk space utilization percentage, upon reaching which an automatic push is triggered and files are transferred to the configured external server.
trigger_percentage specifies the UDR/EDR disk utilization percentage for triggering push, and must be an integer from 10 through 80.
Default: 80%
remove-file-after-transfer
Specifies that the system must delete UDR/EDR files after they are transferred to the external file server.
Default: Disabled
transfer-mode { pull [ module-only ] | push primary { encrypted-url encrypted_url | url url } [ [ max-files max_records ] [ max-tasks task_num ] [ module-only ] [ secondary { encrypted-secondary-url encrypted_secondary_url | secondary-url secondary_url } ] [ source-address ip_address ] [ via local-context ] + ]
Specifies the UDR/EDR file transfer mode.
-
pull : Specifies that the external storage is to pull the UDR files.
-
push : Specifies that the system is to push UDR files to the configured external storage.
-
max-files max_records : Specifies the maximum number of files sent per iteration based on configured file size.
Default: 4000
-
max-tasks task_num : Specifies the maximum number of tasks (child processes) that will be spawned to push the files to the remote server. The task_num must be an integer from 4 through 8.
Default: 4
Important
Note that increasing the number of child processes will improve the record transfer rate. However, spawning more child will consume additional resource. So, this option needs to be used with proper resource analysis.
-
module-only : Specifies that the transfer-mode is only applicable to the UDR module; if not configured it is applicable to both EDR and UDR modules. This enables support for individual record transfer-mode configuration for each module.
-
primary encrypted-url encrypted_url : Specifies the primary location in encrypted format to which the system pushes the UDR files.
encrypted_url must be the primary location name in an encrypted format, and must be an alphanumeric string of 1 through 1024 characters.
-
primary url url : Specifies the primary location to which the system pushes the UDR files.
url must be the primary location, and must be an alphanumeric string of 1 through 1024 characters in the format: //user:password@host:[port]/directory .
-
secondary encrypted-secondary-url encrypted_secondary_url : Specifies the secondary location in encrypted format to which the system pushes the UDR files when the primary location is unreachable or fails.
encrypted_secondary_url must be the location in an encrypted format, and must be an alphanumeric string of 1 through 1024 characters.
-
secondary secondary-url secondary_url : Specifies the secondary location to which the system pushes the UDR files when the primary location is unreachable or fails.
secondary_url must be the secondary location, and must be an alphanumeric string of 1 through 1024 characters in the format: //user:password@host:[port]/directory .
-
source-address ip_address : Configures the source IP address to be used to establish the connection for the SFTP/SSH file-transfer operation.
-
via local-context : Selects the LC/SPIO for transfer of UDRs. The system pushes the UDR files via SPIO in the local context.
-
via local-context : Selects the MIO for transfer of UDRs. The system pushes the UDR files via the MIO in the local context.
use-harddisk
Important |
The use-harddisk keyword is available only on the ASR 5000 chassis. |
Specifies that on an ASR 5000 chassis, the hard disk on the SMC will be used to store UDR/EDR files. When configured to use the hard disk for UDR/EDR storage, UDR/EDR files are transferred from packet processing cards to the hard disk on the SMC.
Specifies that on an ASR 5500 chassis, the hard disk array on the FSCs will be used to store UDR/EDR files. On configuring to use the array for UDR/EDR storage, UDR/EDR files are transferred from DPCs to the array.
Default: Disabled
+
Indicates that more than one of the previous keywords can be entered within a single command.
push-count push_count
Specifies the number of EDR/CDR/UDR files transferred in each EDR/UDR push SFTP session. Default value is "1". push_count is configured as an integer value between 1 and 32,inclusive.
Note |
When push_count is set to “1”, file transfer operation is functionally identical to legacy behavior. |
Usage Guidelines
Use this command to configure how UDRs are moved and stored.
On the ST16 chassis, run this command only from the context where the UDR/EDR module is configured. Running this command in any other context will fail and deliver an error message.
On the ASR 5000ASR 5500 chassis, run this command only from the local context. Running in any other context would fail and deliver an error message.
If PUSH transfer mode is configured, the external storage server URL to which the UDR 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 the transfer-mode from pull to push, disable the PULL from external storage 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 the transfer-mode from push to pull, after changing, enable PULL on the external storage. 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.
The cdr use-harddisk command is available only on the ASR 5000ASR 5500 chassis. 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."
The cdr use-harddisk command can be configured either in the UDR or EDR module, but will be applicable to both record types. Configuring in one of the modules will prevent the configuration to be applied in the other module. Any change to this configuration must be done in the module in which it was configured, the change will be applied to both record types.
The VPNMgr can send a maximum of 4000 files to the remote server per iteration. However if the individual file size is big (say when compression is not enabled), then while transferring 4000 files SFTP operation takes a lot of time. To prevent this, the cdr transfer-mode push command can be configured with the keyword max-files , which allows operators to configure the maximum number of files sent per iteration based on configured file size.
Example
no cdr remove-file-after-transfer 
Feedback