close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

request vmhost remote-file-copy

date_range 03-Jul-24

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
request vmhost remote-file-copy
                 interface {
                       (in-band | out-of-band);
                       }                    
                   source source-path; 
                   destination destination-path;             

Description

Enable remote file copy between the hypervisor and a remote fileserver. The configuration allows creating an external network interface directly on the hypervisor and associating an IPv4 address with it.

The remote file copy feature allows upload or download operations from or into the NFX device. These operations are initiated from the NFX device, not from the remote fileserver.

Options

in-band—Enable external network access through one of the front panel revenue ports.
out-of-band—Enable external network access through the front panel management interface.
source source-path—Name of the source path from which the file is to be copied. The source path should refer to a specific filename, not a directory, and without any wild cards. If the source-path is local, the file-copy is an upload operation. If the source-path is remote, the file-copy is a download operation.
destinationdestination-path—Name of the destination path to which the host file is copied. The destination path must refer to a specific filename.

Additional Information

Either source-path or destination-path must be remote while the other should be local. Consider the following guidelines while creating a local path:

Local path should refer to a file under /var/public/ directory.
Avoid special characters. You can include alphanumeric characters, hyphen, underscore, and dot.
Avoid relative path components .. and /./
Avoid ending the path with /.

Following are the examples of a local path:

/var/public/myfile
/var/public/mydir/my_file
/var/public/12-hours.data

Consider the following guidelines while creating a local path:

A remote path must be in the following format: [<remote_user>[:<remote_user_pwd>]@]<protocol>://<remote_ip>[:<remote_port>]:<remote_path>
The protocols supported are, SCP, HTTP, HTTPS, and FTP.
remote_user is optional, depending on protocol and the remote fileserver configuration.

For example, remote_user is required when scp protocol is used whereas remote_user is unnecessary when HTTP protocol is used.
Depending on the protocol and the remote fileserver configuration, when remote_user is specified, you might have to specifyremote_user_pwd.

For example, when ftp is used, username and password are required.
remote_port is optional and could be skipped if the remote fileserver is reachable on a standard port for the specified protocol.

Following are the examples of a remote path:

content_copy zoom_out_map
user@scp://10.10.10.2:22:/home/user/myfile
user@scp://10.10.10.2:/home/user/myfile
http://10.10.10.2:80:/myfile
https://10.10.10.2:80:/myfile
user:user@ftp://10.10.10.2:21:/home/user/myfile
user@ftp://10.10.10.2:21:/home/user/myfile

Required Privilege Level

Maintenance

Sample Output

request vmhost remote-file-copy (To upload a file from an NFX device to remote fileserver using an in-band interface and scp protocol, with user interaction)
request vmhost remote-file-copy (To upload a file from an NFX device to remote fileserver using an out-of-band interface and scp protocol, with user interaction)
request vmhost remote-file-copy (To download a file from the remote fileserver to an NFX device using an in-band interface and http protocol)
request vmhost remote-file-copy (To download a file from the remote fileserver to an NFX device using an in-band interface and https protocol)
request vmhost remote-file-copy (To upload a file from an NFX device to the remote fileserver using an in-of-band interface and ftp protocol, with user interaction)
request vmhost remote-file-copy (To upload a file from an NFX device to the remote fileserver using an in-band interface and ftp protocol, without user interaction)