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

Example: Defining Destinations for File Archiving by Event Policies

Requirements

This example uses a device running Junos OS. No additional configuration beyond device initialization is required before configuring this example.

Overview

The destination-name is a user-defined identifier, which is referenced by event policies. You can define multiple destinations with different archive sites.

For each destination, configure one or more archive site URIs, which are the actual sites to which the files are uploaded. If you specify multiple archive site URIs for a given destination, the device attempts to transfer to the first archive site in the list, moving to the next site in the list only if the transfer fails. Optionally, you can specify a plain-text password for login into an archive site.

• file:<//host>/path
• ftp://username@host:<port>url-path
• pasvftp://username@host:<port>url-path
• scp://username@host:<port>url-path
• <path>/<filename>

The format for the destination filename is device-name_filename_YYYYMMDD_HHMMSS.

The transfer-delay statement allows you to specify the number of seconds the event process (eventd) waits before beginning to upload a file or multiple files to that destination. A transfer delay allows you to ensure that a large file, such as a core file, is completely generated before the upload begins. For more information, see Configuring the Delay Before Files Are Uploaded by an Event Policy.

This example configures a new archive destination named mgmt-archives, which can be referenced in event policies for file archiving. The example configures two archive sites for this destination. The first site is the Secure Copy URI "scp://username@example.com/test" for which a password is configured. The second site is a directory on the local device. The device attempts to transfer to the first archive site in the list, moving to the next site only if the transfer to the first site fails. The example configures a transfer delay of five seconds for all files uploaded to the mgmt-archives archive site.

Configuration

CLI Quick Configuration

Step-by-Step Procedure

1. Configure the identifier and associated archive sites for each destination.

   The device transfers to the first archive site in the list, moving to the next site only if the transfer to the first site fails.

   [edit event-options destinations]user@host# set mgmt-archives archive-sites scp://username@example.com/testuser@host# set mgmt-archives archive-sites /var/log

2. If authentication is required to access any of the archive sites, configure the required plain-text password for that site.

   [edit event-options destinations]user@host# set mgmt-archives archive-sites scp://username@example.com/test password PaSsWoRd

3. (Optional) Configure the transfer delay associated with each destination. The mgmt-archives destination has a transfer delay of five seconds.

   [edit event-options destinations]user@host# set mgmt-archives transfer-delay 5

4. Commit the configuration.

   user@host# commit
5. You can reference configured destinations in an event policy. For information about referencing destinations in event policies, see Example: Configuring an Event Policy to Upload Files and Configuring an Event Policy to Execute Operational Mode Commands.

Verification

Verifying the Configuration

Purpose

Issue the show configuration event-options operational mode command to review the resulting configuration.

Action

Meaning

In the sample output, the mgmt-archives destination has two archive sites and a transfer delay of five seconds. You can now reference this destination in event policies. When you reference the mgmt-archives destination in an event policy, specified files are uploaded to the first archive site after a five second delay. If the transfer to the first archive fails, the device attempts to upload the files to the /var/log archive site. For more information about referencing destinations in event policies, see Example: Configuring an Event Policy to Upload Files.

Note that although the plain-text password is visible when you configure it, the configuration displays the encrypted password.