Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos Space] Device discovery failure: "Failed to configure device, Check Device state"

0

0

Article ID: KB29250 KB Last Updated: 28 Apr 2015Version: 2.0
Summary:

Device discovery fails with error code:

"Failed to configure device, Check Device state"

This article explains the cause and provides a resolution procedure.

Symptoms:

 Device discovery fails with error code:

"Failed to configure device, Check Device state"
Cause:

 This could be caused by:

  • A pending commit on device
  • Any error or warning message during commit

  • An existing lock on device
  • A commit synchronize fail during device discovery on high-end device(s)

Solution:

Follow these steps:

  1. Log in to the device using the username that is being used to discover the device on Space:

    # ssh <user-name>@<device-ip>

    For example:  # ssh admin@172.27.201.215

  2. Run the following command in configuration mode:

    # show | compare

    If the result shows any pending configuration, then you need to review and commit or roll back.

  3. To verify that the commit is successful without any error or warning, run the following command in configuration mode:

    # commit confirmed 1  

    Note: The commit will automatically roll back after one minute.

    If the commit has the following error:

    Commit error: "cannot connect to other RE , ignoring it"

    Then follow this KB article: Commit error: "cannot connect to other RE , ignoring it"

    Note: If you still encounter any errors during the commit, open a case with the concerned device team.

Verify if other users are making changes on the device. Every user should exit from configuration mode. To view logged in users (run in operational mode):

# show system users

To force a user logout, follow the procedure outlined here: request system logout. This should release the lock from the device.


For commit synchronize, which usually fails on SRX clusters that are configured with dual Routing Engines.

  1. Go to Platform > Administration > Manage Applications > Network Application Platform >. Right-click and select Modify settings.

  2. Clear the "Configure commit synchronization during device discovery" check box when discovering SRX device(s) with dual Routing Engines.

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search