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 > 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: 976 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