Network Management

Fortinet login validation tests fail with a $ as a prompt

Test Failed timeout in Fortigate devices.

First published date

10/11/2018 1:25 PM

Last published date

12/9/2022 6:10 AM

Overview

This article describes the issue when adding a Fortinet device to NCM, and the prompt is a $ and not a # or a >, NCM fails to connect even with standard customer commands added to the template for EnableIdentifier or Virtual Prompt.

Product section

Network Configuration Manager

Cause

This is a known issue and as of the moment, developers are investigating on how to fix the current problem.

Resolution

Use device credentials in NCM that have full Admin/Root access. These credentials return a # as the prompt.

Another way to fix the problem is to add to the device template using the following command:

<Command Name="VirtualPrompt" Value="$"/>

For more information, click on this link on how to modify a device template for NCM version 7.4: Modify a default device template in NCM 7.4

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.