[Contents] [Prev] [Next] [Index] [Report an Error]

Defining Destinations for File Archiving

To upload information for analysis, first you define a destination for the information to be archived. To define destinations, include the following statements at the [edit event-options] hierarchy level:



[edit event-options] 

destinations {



destination-name {

transfer-delay seconds;



archive-sites {

url password password;
}


}


}

After you define a destination, you can reference the destination in an event policy. For information about referencing destinations, see Uploading Files and Executing Operational Mode Commands.

The optional 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. A transfer delay allows you to make sure a large file, such as a core file, is completely generated before the upload begins.

In the archive-sites statement, you can specify a destination as a Hypertext Transfer Protocol (HTTP) URL, FTP URL, or secure copy (scp)-style remote file specification. URLs of the type file:// are not supported; however, local router directories are supported (for example, /var/tmp/). When you specify the archive site, do not add a forward slash (/) to the end of the URL. The format for the destination filename is router-name_filename_YYYYMMDD_HHMMSS.

Optionally, you can specify a plain-text password for login into an archive site.

For a configuration example, see Correlating Events Based on Receipt of Other Events Within a Specified Time Interval.

[Contents] [Prev] [Next] [Index] [Report an Error]