Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos] Archiving configuration using "transfer-interval" statement

0

0

Article ID: KB27993 KB Last Updated: 14 May 2020Version: 2.0
Summary:

This article explains Junos OS behavior when archiving a configuration using the transfer-interval statement.

 

Symptoms:

Junos OS allows you to archive configuration to a remote server or in the local system under the edit system archival configuration hierarchy.

Under this hierarchy, there are two options to specify when the configuration needs to be archived:

  1. transfer-on-commit

  2. transfer-interval

Note: This article focuses on the transfer-interval option only.

 

Solution:

transfer-interval is a value in seconds between 15 and 2,880 minutes. When this value is specified, the configuration is archived every time according to the configuration. For example, if the transfer interval is specified as 15, then the active configuration file is archived every 15 minutes, with the exception of the first file that is archived.

The time when the first archive file is saved depends upon when the last commit happened on the router and the router's up-time when the commit happened.

For example, the following configuration is committed on Aug 10 at 20:49:31:

lab@R1-RE0# show | compare

[edit system]
archival {
    configuration {
        transfer-interval 15;
        archive-sites {
            "ftp://lab:1Matrix@10.209.74.132:21";
        }
    }
}

[edit]
lab@R1-RE0# commit
Aug 10 20:49:31
commit complete
During this time, the system up-time is as follows:
lab@R1-RE0# run show chassis routing-engine
Aug 10 20:49:31
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 43 degrees C / 109 degrees F
CPU temperature 50 degrees C / 122 degrees F
DRAM 3584 MB
Memory utilization 16 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 4 percent
Interrupt 0 percent
Idle 96 percent
Model RE-S-2000
Serial ID 9009022163
Start time 2013-08-02 11:49:43 UTC
Uptime 8 days, 3 hours, 30 minutes, 36 seconds
Last reboot reason Router rebooted after a normal shutdown.
Load averages: 1 minute 5 minute 15 minute
0.01 0.03 0.00

Junos OS takes the system up-time converted to seconds. According to the above output, the system up-time is calculated at 703836 seconds (8d 3h 30m 36s).

According to the above configuration, the active configuration should be archived every 15 minutes, so the next run time (that is, when the configuration would be archived) from 8d 3h 30m 36s is 8d 3h 30m 45th second. The difference is 864 seconds (that is, 14.24 minutes). So the first archive will happen at 14.24 minutes from when the last configuration was committed that is, 14:24 minutes from Aug 10 20:49:31, which is 21:03:55.

It is confirmed that the first file is archived at 21:03:55 on Aug 10 from the FTP server, and from the first file, the archival happens every 15 mins as specified in the transfer-interval statement, which can also be confirmed from the following.

The file name should be read as Hostname_juniper.conf.gz_YYYYMMDD_HHMMSS.

-rw-r--r-- 1 lab staff 1947 Aug 10 21:03 R1-RE0_juniper.conf.gz_20130810_210355
-rw-r--r-- 1 lab staff 1947 Aug 10 21:18 R1-RE0_juniper.conf.gz_20130810_211855
-rw-r--r-- 1 lab staff 1947 Aug 10 21:33 R1-RE0_juniper.conf.gz_20130810_213355
-rw-r--r-- 1 lab staff 1947 Aug 10 21:48 R1-RE0_juniper.conf.gz_20130810_214855
-rw-r--r-- 1 lab staff 1947 Aug 10 22:03 R1-RE0_juniper.conf.gz_20130810_220355
-rw-r--r-- 1 lab staff 1947 Aug 10 22:18 R1-RE0_juniper.conf.gz_20130810_221855
-rw-r--r-- 1 lab staff 1947 Aug 10 22:33 R1-RE0_juniper.conf.gz_20130810_223355
-rw-r--r-- 1 lab staff 1947 Aug 10 22:48 R1-RE0_juniper.conf.gz_20130810_224855

 

Modification History:

2020-05-14: Article checked for accuracy; article valid and relevant, no changes made

 

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search