Device discovery fails with error code:

This article explains the cause and provides a resolution procedure.

 Device discovery fails with error code:

 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)

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 [email protected]

• 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.

• 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.

If the above workaround doesn't fix, please check the server.log. 

2024-08-31 10:49:21,969 ERROR [net.juniper.jmp.cmp.deviceIOMgr.DeviceInboundConnection] (Thread-982 (ActiveMQ-client-global-threads)) response from device ---- <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/21.2R0/juno

s" message-id="1">

<commit-results>

<routing-engine junos:style="show-name">

<name>re0</name>

<rpc-error>

<error-type>protocol</error-type>

<error-tag>operation-failed</error-tag>

<error-severity>error</error-severity>

<error-message>

Unique id allocation failed for '//var/etc/stp_all_port.id' - no more free ids

</error-message>

</rpc-error>

<rpc-error>

<error-type>protocol</error-type>

<error-tag>operation-failed</error-tag>

<error-severity>error</error-severity>

<error-message>

Unique id allocation failed for '//var/etc/stp_port.id' - no more free ids

</error-message>

</rpc-error>

<rpc-error>

<error-type>protocol</error-type>

<error-tag>operation-failed</error-tag>

<error-severity>error</error-severity>

<error-message>

Unique id allocation failed for '//var/etc/stp_port.id' - no more free ids

If you are seeing the above error, please follow the article Commit failing - error: Unique ID allocation failed for '//var/etc/stp_all_port.id'

Or Raise a case with the Device Team

17-10-2024: Modified the KB: Need to check the server.log

• [SRX] Commit error: "cannot connect to other RE , ignoring it"