Documentation forNetwork Configuration Manager
Managing network configurations is a key capability of Hybrid Cloud Observability Advanced and is also available in a standalone module, Network Configuration Manager (NCM). Hybrid Cloud Observability Advanced and NCM are built on the self-hosted SolarWinds Platform.

Protocols NCM uses to transfer configurations

You can specify the protocols that NCM uses to transfer configurations in the device's connection profile, a global profile, or in global variables. NCM can use the following protocols.

Telnet or SSH

When NCM downloads a configuration using Telnet or SSH (Secure Shell), it logs in to the device and then runs commands on the device to display the configuration. When the device displays the configuration, NCM parses the information and stores it.

To use Telnet or SSH, specify the following options in the connection profile, global profile, or global variables:

  • Select the desired protocol (Telnet or SSH) as the value for the Request Config option.
  • Select the same protocol as the value for the Transfer Config option.

Transfers using Telnet or SSH are direct transfers.

TFTP

When NCM downloads a configuration using TFTP (Trivial File Transfer Protocol), it uses Telnet or SSH to log in to the device and initiate the TFTP session. Then it uses TFTP to transfer the configuration file from the device to the TFTP server. The SolarWinds TFTP server is included with NCM. It is automatically installed on the SolarWinds Platform server and on any additional polling engines.

To use TFTP:

  1. Specify the following options in the connection profile, global profile, or global variables:

    • Select Telnet, SSH, or SNMP as the value for the Request Config option.

      SNMP (Simple Network Management Protocol) can be used only with Cisco devices that support this protocol, and it requires additional configuration. You must configure the SNMP read-write community string on the device and ensure that NCM has been set up with the same string. The device must support the CISCO-CONFIG-COPY-MIB.

    • Select TFTP as the value for the Transfer Config option.
  2. Configure the TFTP server as needed for your environment.

Transfers using TFTP are indirect transfers.

SCP

When NCM downloads a configuration using SCP (Secure Copy Protocol), it uses Telnet or SSH to log in to the device and initiate the SCP session. Then it uses SCP to transfer the configuration file from the device to the SCP server. The SolarWinds SCP server is included with NCM. It is automatically installed on the SolarWinds Platform server and on any additional polling engines. You can also choose to use a third-party SCP server.

Binary device configs can be transferred only with SCP.

To use SCP:

  1. Specify the following options in the connection profile, global profile, or global variables:

    • Select Telnet or SSH as the value for the Request Config option.

      SSH is typically used with SCP.

    • Select SCP as the value for the Transfer Config option.
  2. Configure the SolarWinds SCP server or a third-party SCP server as needed for your environment.

Transfers using SCP are indirect transfers.