Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Exporting Files Using an Op Script

 

The op script in this example uses the Junos XML protocol file-put operation to write to a file on a remote server and on the local device.

Requirements

This example uses a device running Junos OS.

Overview and Op Script

The Junos XML protocol file-put operation creates a file and writes the specified contents to that file. The basic syntax for using the file-put command is as follows:

The following tag elements are used with the file-put command. These tags can be placed in any order with the exception of file-contents. The file-contents tag element must be the last tag in list.

  • delete-if-exist—(Optional) If included, any existing file is overwritten. If the tag is omitted, an error is returned if an existing file is encountered.

  • encoding—(Mandatory) Specifies the type of encoding used. You can use ASCII or base64 encoding.

  • filename—(Mandatory) Within this tag, you include the full or relative path and filename of the file to create. When you use a relative path, the specified path is relative to the user’s home directory. If the specified directory does not exist, the system returns a “directory does not exist” error.

  • permission—(Optional) Sets the file’s UNIX permission on the remote server. For example, to apply read/write access for the user, and read access to others, you would set the permission value to 0644. For a full explanation of UNIX permissions, see the chmod command.

  • file-contents—(Mandatory) The ASCII or base64 encoded file contents to export. This must be the last tag in the list.

XSLT Syntax

The following sample script executes a Junos XML API request and exports the results to a file on a remote device and a file on the local device. The script takes three arguments: the IP address or hostname of the remote device, the filename, and the file encoding. The arguments variable is declared at the global level of the script so that the argument names and descriptions are visible in the command-line interface (CLI).

The script invokes the Junos XML API <get-software-information> request on the local device and stores the result in the result variable. The script declares the fileput variable, which contains the remote procedure call (RPC) for the file-put operation. The command-line arguments define the values for the filename and encoding tag elements. If the mandatory argument myhost is missing, the script issues an error and halts execution. Otherwise, the script prompts for the username and password that will be used to connect to the remote device.

If connection to the remote device is successful, the script executes the RPC within the context of the connection handle. The output of the file-put operation, which is the result of the jcs:execute() function, is stored in the out variable. If the operation encounters an error, the script prints the error to the CLI. If the file-put operation is successful, the contents specified by the file-contents tag element are exported to the specified file on the remote device. The connection to the remote host is then closed. The script also exports the contents to an identical file on the local device.

The sample script includes the optional tag elements permission and delete-if-exist for the file-put operation. By including the delete-if-exist tag, the script overwrites any existing file of the same name on the remote and local hosts. In this example, the permission tag is set to 0644.

SLAX Syntax

Configuration

Step-by-Step Procedure

To download, enable, and test the script:

  1. Copy the XSLT or SLAX script into a text file, name the file export.xsl or export.slax as appropriate, and copy it to the /var/db/scripts/op/ directory on the device.
  2. In configuration mode, include the file statement at the [edit system scripts op] hierarchy level and export.xsl or export.slax as appropriate.

  3. Issue the commit and-quit command.

  4. Execute the op script by issuing the op export operational mode command and include any necessary arguments.

Verification

Verifying the Op Script Arguments

Purpose

Verify that the argument names and descriptions show up in the CLI.

Action

Issue the op exort ? operational mode command. The CLI lists the possible completions for the script arguments based on the definitions within the global arguments variable in the script.

user@host> op export ?

Verifying Op Script Execution

Purpose

Verify that the script behaves as expected.

Action

Issue the op export myhost host encoding encoding filename file operational mode command, and include the appropriate username and password when prompted. If script execution is successful, the result of the <get-software-information> RPC request is written to the file on the remote device and also on the local device. For example:

root@host> op export myhost router1 encoding ascii filename /var/log/host-version.txt

If you fail to supply the IP address or hostname of the remote device in the command-line arguments, the script issues an error and halts execution.

root@host> op export

If you omit the delete-if-exist child tag of the file-put operation, and the specified file already exists, the script reports an error.

root@host> op export myhost router1 encoding ascii filename /var/log/host-version.txt

If you execute the script and include a directory path that does not exist on either the remote or the local host, the script reports an error.

root@host> op export myhost router1 encoding ascii filename /var/test/host-version.txt