Description

This article explains how to fix if the device discovery is failing with the error "Device is already managed" on a device-initiated connection. However, there is no duplicate entry

Symptoms

The below error will be displayed in server.log: 
2024-03-13 00:55:58,718 ERROR [SystemDiscoveryManagerBean] () publishing discovery job information. Job id:96437590 ## discovery action parameters :{import-policy=false, context-information=net.juniper.jmp.cmp.jobManager.InternalScheduleContext@53e02311}

If the customer is using device initiated connection and Since the configuration already exists in the device, Junos space thinks that the device is already managed.

Solution

To fix the issue,

  • Check if the "outbound-ssh" configuration exists on the device.
  • Please delete all "outbound-ssh" configurations.

 

For example:
 

set system services outbound-ssh client 00000000EFBC device-id 5B88FE

set system services outbound-ssh client 00187D0CEFBC secret "$ABC123"

set system services outbound-ssh client 00000000EFBC services netconf

set system services outbound-ssh client 00000000EFBC xxx.xxx.xxx.xxx port 7804

Now try to discover the device again to Junos Space.

 

Please contact JTAC if the same issue is seen again.

Modification History

2024-03-13 : Article Created