Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Applying a configuration backup causes some devices to fail

Applying a configuration backup causes some devices to fail

Updated: October 4, 2017

Overview

When you download a configuration backup, some devices fail. However, you can telnet to the NCM server and testing through NCM is successful.

When this issue occurs, the following entries display in session traces:

TimerTick: Login Timeout

Connected! The current connection has timed out.

Environment

  • NCM 7.6 and older

Cause 

NCM exceeds the 45 second Telnet/SSH Connection Timeout limit before establishing a valid connection with the server.

Resolution

Gather session traces to confirm the errors. 

  1. Open the Orion Web Console.
  2. Click Settings > All Settings > NCM settings.
  3. Under Advanced, click Advanced settings.
  4. Select the Enable Session Tracing checkbox, and then click Submit. 
  5. If you are running this NCM download/command through the Orion Web Console, go to the next step.
    If you are using the 32-bit Windows application on the server to download a configuration, close and re-open the NCM application for this setting to take effect.  
  6. After you reproduce the error, uncheck the Enable Session Tracing checkbox in Advanced Settings, and then click Submit.
  7. Review the trace and debug file.
    The session traces are stored at:
    C:\ProgramData\Solarwinds\Logs\Orion\NCM\Session-Trace
  8. Verify that the IP addresses of each failed device and confirm the issue.
  9. In the Orion Web Console, click Settings > All Settings > NCM Settings. 
  10. Under Network, click Protocol Settings.

  11. Increase the Telnet/SSH Connection Timeout value from 45 seconds to 120 seconds. 

  12. Click Submit. 

 

 

 

Last modified

Tags

Classifications

Public