×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Important

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.
TrueSight Network Automation 8.9 ... Administering Performing network administration tasks

Managing remote file servers

A remote file server is used to define where device OS images might be stored outside of the TrueSight Network Automation local database. Normally, OS image snapshot and deploy actions use the local database to store the OS image files. The file is transferred between the TrueSight Network Automation server and the device agent, and between the device agent and the device. Because image files can be large, transferring them might increase the traffic load on your network in an undesirable way. You can choose to store your image files on a remote host instead, where this host is remote from the TrueSight Network Automation server and agent systems, but is local to, or physically co-located with the device.

Note

If a device is configured to use a remote file server and the device is using a device agent which is configured to use a proxy file server, and while performing Deploy OS Image and Snapshot OS Image actions you choose the From Remote File Server option, the remote file server is used to perform the actions.

A remote file server defines the host name or IP address of the host system, and the file transfer servers available on that system, with credentials for using FTP and SCP. Once one or more such servers are defined, you can then associate each device with its remote file server, run OS image snapshot actions to copy OS image files from the device to the remote file server, and run OS image deploy actions to copy OS image files from the remote file server to the device.

Note

TrueSight Network Automation cannot determine the files you have stored on a remote file server. Thus, for an Deploy OS Image action, you must know the exact file name for the image file, its size (in bytes), and MD5 checksum. Because TrueSight Network Automation does not store the image file in its image library, you cannot later redeploy from the library. The same is true for image snapshot; TrueSight Network Automation does not add the file to the OS image library and thus you cannot later deploy the image from the library.

The following topics describe how to add and edit remote file servers, and view the list of remote file servers:

Was this page helpful? Yes No Submitting... Thank you
Last modified by Sulekha Gulati on Oct 25, 2018
viewing remote_file_servers contributor-updated os_image

Comments

Log in or register to comment.

Viewing the OS image library
Adding or editing a remote file server
© Copyright 2013 - 2019 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.