для Cisco Cisco ASR 5000
EDR Module Configuration Mode Commands
cdr ▀
Command Line Interface Reference, StarOS Release 18 ▄
3663
use-harddisk
Important:
The
use-harddisk
keyword is available only on the ASR 5000 and ASR 5500 chassis.
ASR 5000: Specifies that on the ASR 5000 chassis the hard disk on the SMC be used to store EDR/UDR
files. On configuring to use the hard disk for EDR/UDR storage, EDR/UDR files are transferred from packet
processing cards to the hard disk on the SMC. Default: Disabled
ASR 5500: Specifies that on the ASR 5500 chassis the hard disk the FSC hard disk array be used to store
EDR/UDR files. On configuring to use the hard disk for EDR/UDR storage, EDR/UDR files are transferred
from DPCs to the hard disk array. Default: Disabled
files. On configuring to use the hard disk for EDR/UDR storage, EDR/UDR files are transferred from packet
processing cards to the hard disk on the SMC. Default: Disabled
ASR 5500: Specifies that on the ASR 5500 chassis the hard disk the FSC hard disk array be used to store
EDR/UDR files. On configuring to use the hard disk for EDR/UDR storage, EDR/UDR files are transferred
from DPCs to the hard disk array. Default: Disabled
+
Indicates that more than one of the previous keywords can be entered within a single command.
Usage
Use this command to configure how the EDRs are moved and stored.
On the ASR 5000 or ASR 5500 chassis, you must run this command only from the local context. If you run
this command in any other context it will fail and result in an error message.
If PUSH transfer mode is configured, the L-ESS (for ASR 5000) or external server (for ASR 5500) URL to
which the EDR 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:
On the ASR 5000 or ASR 5500 chassis, you must run this command only from the local context. If you run
this command in any other context it will fail and result in an error message.
If PUSH transfer mode is configured, the L-ESS (for ASR 5000) or external server (for ASR 5500) URL to
which the EDR 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 the L-ESS (for ASR 5000) or
external server (for ASR 5500) 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 L-ESS (for
ASR 5000) or external server (for ASR 5500). 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
external server (for ASR 5500) 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 L-ESS (for
ASR 5000) or external server (for ASR 5500). 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 5000 and ASR 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
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 EDR or UDR 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
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
The following command retains a copy of the data file after it has been transferred to the storage location: