Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Back up Cisco UCSM Config files using SCP

Back up Cisco UCSM Config files using SCP

Table of contents

Updated 10/9/2017


This article provides information on how to create scripts to SCP transfer a Config file for Cisco UCSM files within NCM.


  • All NCM versions


  1.  Create the backup operation either on the device's CLI or through an execute:
    1. example command syntax:
  2. After the backup is created, create multiple scripts to change the ConfigFilename.bak file name and the configuration backup-type using two set commands to desire config file, enable it and commit to SCP the file to the SCP server root directory.
    1. example command syntax:
    • scope system
    • scope backup SCPhostnameOrIPAddress
    • set remote-file /SCPRootDirectory/ConfigFilename.bak
    • set type config backup-type
    • enable
    • SCPpassword
    • commit-buffer


See setting up the SCP/SFTP server for more information.


Configure the SCPuser, SCPhostnameOrIpAddress, and SCPpassword in the SCP/SFTP server on the Orion server, or you can use a third-party SCP/SFTP server. 


If you still have questions, contact your Vendor Support on the commands used for the Cisco UCSM, create a case with NCM Support, or review the Cisco UCSM guide.   (© 2015 Cisco, available at, obtained on 10/9/2017.) 


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified