Format for Specifying Filenames and URLs in Junos OS CLI Commands
In some CLI commands and configuration statements—including file copy, file archive, load, save, set system login user username authentication load-key-file, and request system software add—you can include a filename. On a routing matrix, you can include chassis information (for example, lcc0, lcc0-re0, or lcc0-re1) as part of the filename.
A routing matrix is a multichassis architecture composed of either one TX Matrix router and from one to four T640 routers connected to the TX Matrix router, or one TX Matrix Plus router and from one to four T1600 routers connected to the TX Matrix Plus router. From the perspective of the user interface, the routing matrix appears as a single router. On a routing matrix composed of the TX Matrix router and T640 routers, the TX Matrix router controls all the T640 routers. On a routing matrix composed of a TX Matrix Plus router and T1600 routers, the TX Matrix Plus router controls all the T1600 routers.
Starting with Junos OS Release 15.1, the sslv3-support option is not available for configuration with the set system services xnm-ssl and file copy commands. SSLv3 is no longer supported and available.
For all releases prior to and including Junos OS Release 14.2, SSLv3 is disabled by default at runtime. The sslv3-support option is hidden and deprecated in Junos OS Release 14.2 and earlier releases. However, you can use the set system services xnm-ssl sslv3-support command to enable SSLv3 for a Junos XML protocol client application to use as the protocol to connect to the Junos XML protocol server on a router, and you can use the file copy source destination sslv3-support command to enable the copying of files from an SSLv3 URL.
Using SSLv3 presents a potential security vulnerability, and we recommend that you not use SSLv3. For more details about this security vulnerability, go to https://kb.juniper.net/InfoCenter/index?page=content&id=JSA10656.
You can specify a filename or URL in one of the following ways:
filename—File in the user’s current directory on the local CompactFlash card (not applicable on the QFX Series). You can use wildcards to specify multiple source files or a single destination file. Wildcards are not supported in FTP.
Wildcards are supported only by the file (compare | copy | delete | list | rename | show) commands. When you issue the file show command with a wildcard, it must resolve to one filename.
path/filename—File on the local flash disk.
/var/filename or /var/path/filename—File on the local hard disk. You can also specify a file on a local Routing Engine for a specific T640 router or a T1600 router in a routing matrix:
user@host> file delete lcc0-re0:/var/tmp/junk
a:filename or a:path/filename—File on the local removable media. The default path is / (the root-level directory). The removable media can be in MS-DOS or UNIX (UFS) format.
hostname:/path/filename, hostname:filename, hostname:path/filename, or “
scp://hostname/path/filename”—File on an
scp/sshserver. This form is not available in the worldwide version of Junos OS. The default path is the user’s home directory on the remote system. You can also specify
ftp://hostname/path/filename—File on an FTP server. You can also specify
username:password@hostname. The default path is the user’s home directory. To specify an absolute path, the path must start with
%2F; for example,
//hostname/%2Fpath/filename. To have the system prompt you for the password, specify
promptin place of the password. If a password is required and you do not specify the password or
prompt, an error message is displayed:
user@host> file copy ftp://firstname.lastname@example.org/filename
file copy ftp.hostname.net: Not logged in.
user@host> file copy ftp://username:email@example.com/filename
Password for firstname.lastname@example.org:
http://hostname/path/filename—File on an HTTP server. You can also specify hostname as username@hostname or username:password@hostname. If a password is required and you omit it, you are prompted for it.
You cannot specify a HTTP(s) URL for a file as a destination, because HTTP(s) URLs are not writable. However you can specify HTTP(s) URL for a file as a source.
re1:/path/filename—File on a local Routing Engine. You can also specify a file on a local Routing Engine for a specific T640 router or a T1600 router in a routing matrix:
user@host> show log lcc0-re1:chassisd