Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Using an Alternate Source Location for a Script

Refreshing a Script from an Alternate Location

In addition to updating a script from the master source defined by the source statement, you also can update a script from an alternate location using the set refresh-from configuration mode command or the request system scripts refresh-from operational mode command. This is convenient when, for example, the master source cannot be accessed due to network issues or other problems.

The update operation occurs as soon as you issue either the set refresh-from configuration mode command or the request system scripts refresh-from operational mode command. When you issue the command, the switch, router, or security device immediately attempts to connect to the specified URL and retrieve a copy of the file. The copy overwrites the local script stored in the scripts directory on the device. If a copy of the source is not available at the remote URL, that script is not updated and a warning is issued. For commit scripts, the updated commit script is executed when you next issue the commit command.

Issuing the set refresh-from command does not add the refresh-from statement to the configuration. Thus the set refresh-from command behaves like an operational mode command by executing an operation, instead of adding a statement to the configuration.

If a device has dual Routing Engines and you want the script to be updated on both Routing Engines, you must issue the set refresh-from command on each Routing Engine separately. The commit synchronize command does not cause the refresh-from statement to update scripts on both Routing Engines. Alternatively, starting with Junos OS Release 13.2, you can refresh the scripts on the requesting Routing Engine and then use either the request system scripts synchronize operational mode command to synchronize scripts to the other Routing Engine or the commit synchronize scripts configuration mode command to synchronize all scripts to the other Routing Engine when you commit and synchronize the configuration. In operational mode, you can use the request system scripts refresh-from command with the sync option to refresh the script on both Routing Engines.

• [edit system scripts commit file filename]user@R1# set refresh-from url
• [edit system scripts op file filename]user@R1# set refresh-from url
• [edit event-options event-script file filename]user@R1# set refresh-from url

• [edit system scripts commit]user@R1# set refresh-from url
• [edit system scripts op]user@R1# set refresh-from url
• [edit event-options event-script]user@R1# set refresh-from url

• user@R1> request system scripts refresh-from (commit | event | op) file filename url url <sync>

• filename—Name of the script.
• url—URL of the remote script or directory. Specify the source as a Hypertext Transfer Protocol (HTTP) URL, FTP URL, or secure copy (scp)-style remote file specification.

refreshing 'nonexistent.slax' from 'http://host1.juniper.net/nonexistent.slax'
fetch-secure: http://host1.juniper.net/nonexistent.slax: Not Found
error: file-fetch failed
error: communication error: rpc failed (file-fetch)
error: error retrieving file http://host1.juniper.net/nonexistent.slax

When you issue the set refresh-from command, Junos OS creates a folder in the /var/tmp directory, which is used for the file transfer. After the transfer and refresh operations are complete, Junos OS deletes the temporary folder.

Example: Refreshing a Script from an Alternate Source

The following example uses an alternate source location to update the local copy of the script on a device running Junos OS. The remote source is defined as an HTTP URL.

• Requirements
• Overview
• Configuration
• Verification

Requirements

• Routing, switching, or security device running Junos OS.

Overview

You can update a script from a location other than that of the master source. This is convenient when, for example, the master source cannot be accessed due to network issues or other problems. You can refresh a single script or all scripts of a given type from the alternate location.

This example enables the op script iso.xsl on a device running Junos OS and then refreshes the script from a location other than the master source location. The remote source for the iso.xsl file is the HTTP URL http://my.example.com/pub/scripts2/iso.xsl.

You refresh the local script by issuing the set refresh-from configuration mode command at the hierarchy level where you configured the script. In this example, you would issue the set refresh-from command at the [edit system scripts op file iso.xsl] hierarchy level.

Configuration

Step-by-Step Procedure

1. Copy the script to the /var/db/scripts/op/ directory on the device.

2. In configuration mode, configure the file statement to enable the iso.xsl script.

   [edit system scripts op]user@R1# set file iso.xsl

3. Issue the commit and-quit command to commit the configuration and exit to operational mode.

   [edit]user@R1# commit and-quit

Results

Verifying the Script

Purpose

Verify that the script is on the device and enabled in the configuration.

Action

/var/db/scripts/op:
total 128
-rw-r--r--  1 root  admin  13897 Feb 10  2011 iso.xsl
...

file iso.xsl

Refreshing the Script from the Alternate Location

Step-by-Step Procedure

1. In configuration mode, issue the set refresh-from command at the [edit system scripts op file iso.xsl] hierarchy level.

   [edit system scripts op file iso.xsl]user@R1# set refresh-from http://my.example.com/pub/scripts2/iso.xsl

Verification

Verifying the Updated Script

Purpose

After refreshing the script, verify that the local copy is updated.

Action

/var/db/scripts/op:
total 128
-rw-r--r--  1 root  admin  14128 May 26  2011 iso.xsl
...