Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Transfer Status: Connectivity issues, discarding configuration (or configuration is too short)

Transfer Status: Connectivity issues, discarding configuration (or configuration is too short)

Created by Mariusz Handke, last modified by James Fahey on Oct 07, 2016

Views: 4,845 Votes: 2 Revisions: 7

Overview

This article discusses how to address the following error while attempting to download config manually.

 

The following error is displayed in the CONFIGS tab in Node Details view:

 

Transfer Status: Connectivity issues, discarding configuration (or configuration is too short)

 

 

 

The following error is displayed in the Transfer Status grid in Configuration Management view:

 

Connectivity issues, discarding configuration (or configuration is too short)

 

Environment

All NCM versions

Cause

The most common cause of such behaviour is an incorrect download config command which results in the short error message displayed by the device which then NCM interprets as config too short and discards it.

Resolution

To resolve the issue, make sure that the correct command is used in the template assigned to the node in NCM:

  1. Log in to the Orion Web Console.
  2. Go to the node in question and then select Edit Node.
  3. In the NCM section, check Device Template and make note of it. If it set to Auto Determine, follow these steps:
    1. Click Test.
    2. Once the test completes, click Show credential login details and make a note of the template name. It will be shown similar to the below example and displaying the name of device template (Cisco IOS) and also the node's SysObjectID (1.3.6.1.4.1.9.12.3.1.3.847):
      Device Template: Cisco IOS-1.3.6.1.4.1.9.12.3.1.3.847 
      
  4. Review the DownloadConfig command in the above device template and adjust accordingly making sure that the command being used works directly on the device.

Another issue is whether the commands being issued are being issued to a Privileged Account or Privileged / Enable Mode.

With Cisco, if the prompt shows ">" and not "#", commands such as disabling pager or to show a config type will fail.

 

Last modified

Tags

Classifications

Public