Network Management

NCM is unable to connect to Cisco ASA

Generally, NCM should have no problems connecting, logging in, and working with a Cisco ASA, provided that NCM is configured with the correct login credentials, correct protocols chosen, and Device Template selected. There are times when an ASA may not append the Hostname to the Prompt, leaving only the # at the enable mode. This may cause NCM not to fully engage.

First published date

10/8/2018 7:56 PM

Last published date

10/9/2018 1:41 PM

Overview

In most cases, NCM should have no issues connecting, logging in, and working with a Cisco ASA, as long as NCM is configured with the correct login credentials, correct protocols chosen, and Device Template selected. However, at times, an ASA may not append the Hostname to the Prompt, leaving only the # at the enable mode, which may cause NCM not to fully engage.

Product section

Network Configuration Manager

Cause

The Enable Prompt is a single #.

Resolution

  1. On Cisco ASA, use the prompt hostname command so the device will send the hostname with the prompt, or make a copy of the Cisco Adaptive Security Appliance Template and add the following commands:
<Command Name="MenuBased" Value="False"/>
<Command Name="VirtualPrompt" Value=">"/>
<Command Name="VirtualEnablePrompt" Value="#"/>
  1. Set the New Template to have a unique name.
  2. Set the New Template not to be used for Auto determine.
  3. After saving the template, edit the ASAs displaying this behavior and manually set the new device template to be used in the communication section.