Documentation forNetwork Configuration Manager
Managing network configurations is a key capability of SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) and is available in the Advanced edition. Network Configuration Manager (NCM) is also available in a standalone module.

Configure nodes to use device-level login credentials for NCM connections

When a node is configured to use device-level login credentials, the connection profile for that node specifies the login credentials and other connection information NCM uses to connect to that node. By default, the connection profile for each NCM node uses a set of global variables to define the value of each field, as shown below. You can specify a different value for any field.

To configure devices to use device-level login credentials, complete the following tasks.

For information about other configuration options, see Options for specifying NCM connection information.

Gather information

Before you begin:

  • Locate the login credentials for the node you want to add to NCM.
  • Determine whether NCM communicates with the device by way of Telnet or SSH.
  • Identify the Telnet or SSH ports used for communication.

Review values for global variables

Review the values for global variables and change them if necessary. See Specify values for global variables.

Override default settings for a specific node

If the value of a global variable is not appropriate for a specific node, edit that node's connection profile to specify a different value.

  1. Click Settings > All Settings.
  2. Under Node & Group Management, click Manage Nodes.
  3. Use the Group By list to filter the nodes.
  4. Select a node in the list, and click Edit Properties.
  5. Scroll down to NCM Properties.
  6. For the Global Connection Profile, select <No Profile>.
  7. For Login Credentials, select Device.

  8. Enter the values for any fields that should not use the global variable values.

    For example, you can override any of the following:

    1. Enter the Username and Password to log in to this device.

    2. Under Enable Level, select enable if NCM must enter a command to provide a higher level of access on the network devices. On some devices, this command is required to allow NCM to back up configs, upload changed configs, and run certain scripts.

      If a command is required, but the command is not enable, do the following:

      1. Select enable in the connection profile.

      2. In the device template that defines the device-specific commands used to perform actions on that device, include the following:

        <Command Name="EnableCommand" Value="commandForMyDevice"/>

        where commandForMyDevice is the command entered on your device (for example, super).

      If the NCM account has the privileges it needs without having to enter a command such as enable, then make sure enable is not selected in the connection profile.

    3. If you selected enable, enter the password for it.
    4. For Execute Scripts Using, choose the protocol that NCM should use to execute commands and scripts.

    5. For Request Configs Using, choose the protocol that NCM should use to log in to a device and request a config transfer.

      For more information about Config Request and Transfer Config options, see Protocols NCM uses to transfer configurations.

    6. For Transfer Configs using, choose the protocol that NCM should use to upload and download configs.
    7. Set the Telnet and SSH ports to the ports allowed on your network.

  9. Click Test to test the connection.

    If the test fails, click Advanced Test to open the CLI Connection Analyzer dialog. Review the connection settings on this dialog and make changes if needed.

    To run the test again, click Test connection. The CLI Test result page shows the results as well as log file entries to help you troubleshoot any issues.

  10. When the connection test succeeds, click Submit.