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 > 3COM configuration backup failing through SSH

3COM configuration backup failing through SSH

Created by Ivan Zlatkov, last modified by Bill Corgey on Jun 13, 2017

Views: 1,215 Votes: 1 Revisions: 15

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. Modify the Command from the copy of template to an Appropriate Value: If there are multiple nodes, try to find a common prompt characteristic.
<Command Name="VirtualPrompt" Value="XYZ"/>

 

Assign the new Device template to the devices 

Last modified

Tags

Classifications

Public