Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Network Configuration Manager (NCM) > 3COM configuration backup failing through SSH

3COM configuration backup failing through SSH

Created by Ivan Zlatkov, last modified by MindTouch on Jun 23, 2016

Views: 4 Votes: 1 Revisions: 14

Overview

3COM configuration backup fails with "connection refused" error after changing the preferred protocol from Telnet to SSH.

Environment

NCM v7.4

Cause 

The following line within the template is causing the issue:

<Command Name="VirtualPrompt" Value="Bas-3com4500"/>

This line was previously added to the set of predefined (system) templates. As a result, it instructs NCM to expect specific prompt (Bas-3com4500) on any devices. This should not be the case since devices may have a different prompt based on their hostnames.

Resolution

  1. Create a duplicate template.
    Note: Depending on the NCM version, use the relevant steps to manage templates. For more information, refer to the NCM Documentation.
  2. Remove offending line from the copy of template:
    <Command Name="VirtualPrompt" Value="Bas-3com4500"/>
Last modified
21:02, 22 Jun 2016

Tags

Classifications

Public