switch-back-time
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Mobility Release 11.2W.
Description
The CDF transmits the CDRs to the peer, which is of highest priority. The priority is determined by the peer-order configuration. If for any reason this peer goes down, the CDF transmits the CDRs to the next high-priority peer and so on. If none of the peers are up, then the CDRs are transmitted to the local RE disk, if it is configured. During this transmission, it is possible that a peer or a peer that is higher in priority might come up. Instead of immediately switching over the transmission of the CDRs to the peer that recently came up, you can configure the duration that the CDF must wait to transmit the CDRs to the highest priority peer that becomes available after this duration.
 | Note:
If all the peers are down, in order not to lose any CDR
data, you may want to configure the local storage on the RE disk using
the following command: However, even if the RE disk is not configured for storage, the CDR data is not lost because it gets buffered in the Service PICs. Service PICs can buffer up to a maximum of 2 GB of data after which a Call Admission Control (CAC) is triggered. In the meantime, if one or multiple peers come alive, then CDF waits for the configured switch-back-time duration and routes the CDRs to the highest priority peer that is alive after this duration. The CDRs that were getting stored previously on the RE disk are not routed to the charging gateway (peer) and continue to remain on the disk. You need to SFTP it from the /opt/mobility/charging/ggsn/final_log location on the disk. |
Options
seconds | — | Time, in seconds, CDF waits before transmitting the CDRs to the highest priority peer. |
Range: 0 through 300 seconds
Default: 30 seconds
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
