Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Account Credential is still connecting to Telnet or SSH even after being deleted in NCM settings

Account Credential is still connecting to Telnet or SSH even after being deleted in NCM settings

Created by John Salvani, last modified by Melanie Boyd on Jun 15, 2018

Views: 899 Votes: 1 Revisions: 5

Overview

Upon checking Event logs (event 6273), Account Credential is still connecting to TELNET or SSH even after being deleted in NCM settings.

Environment

  • NCM, all versions

Cause 

Some credentials are still connected on other modules settings via the web console.

Resolution

To resolve this issue, check the following settings:

  • On the Orion Web console, go to Settings > IPAM settings > Managed credentials, and then determine which credential is still connecting to a device via Telnet or SSH.
  • On the Orion Web console, go to Settings > VNQM Settings > Remove VNQM node (or operation), and then check the devices that send CLI queries via Telnet or SSH.

 

 

Last modified

Tags

Classifications

Public