Device discovery

[DCIM_Support]

This question was originally posted on DCIM Support by jan voorsluys on 2018-12-27

---

Device discovery has been running 2 hrs with no discovery. Is there a way to stop it?

(CID:137728424)

[DCIM_Support]

This answer was originally posted on DCIM Support by Ed Tarento on 2018-12-27

---

Hi Jan

DCE Discovery runs as per the schedule you set when you created the discovery entry or if you manually run.  Why do you want to stop the discovery?  As you're expecting DCE to discover something, you may have a mis config in the IP address of your DCE, or the public and private NIC configs are swapped or the device community string on your discovery entry doesn't match whats on your device/s  

If none of the above work, post some more info, DCE part number, version, config or your NICs and config of a device you expect to discover.   Also ping the device you expect to discover from DCE using 

• Tools available from http://<DCE_IP>/nbc/status/Troubleshoot
  • Ping

Cheers

Ed

(CID:137728436)

[DCIM_Support]

This comment was originally posted on DCIM Support by jan voorsluys on 2018-12-27

---

Hi Ed,

We recently upgraded DCE to 7.6.0.114 which I'm assuming is the latest version.  What I'm trying to discover are the Netbotz devices out there. The issue was we only had 200 licenses at the time and most of the netbotz were deleted to make room to add UPS's.  Now we have purchased more licenses I wanted to search for the netbotz which were deleted previously. I think the problem is that I'm searching the whole network vs. just the subnets.  Unfortunately nobody took note of the netbotz IP's before deleting. I did stop the discovery by rebooting the server. So the question is, is there a way to stop discovery without rebooting computer?    

(CID:137728442)

[DCIM_Support · Accepted solution]

This answer was originally posted on DCIM Support by Ed Tarento on 2018-12-27

---

Thanks for extra info.  NetBotz discovery depends on model number.  http://sxwhelpcenter.ecostruxureit.com/display/public/UADCE725/Device+discovery+processes has more info.  What is the problem with letting the discovery run to completion? say overnight?  What address range are you trying to discover across?   Is there any old documentation for IP address assignment that might give you a clue?  Do you use static or dynamically assigned IPs?

No way I know to stop discovery without reboot.

Perhaps consider breaking up a large discovery entry into multiples?

Cheers

Ed

(CID:137728445)

[DCIM_Support]

This comment was originally posted on DCIM Support by jan voorsluys on 2018-12-27

---

Hi Ed,

DCE was set up years ago by the IT department and no one looked at until I did recently. No history that they can find.  Unk how the IP's were obtained by the devices.  From what I gather there are only 355's and 450 appliances out there.  I'm currently running discovery through the subnet's and that seems to be working. Thanks for your help.  Jan    

(CID:137728450)

[DCIM_Support]

This comment was originally posted on DCIM Support by Ed Tarento on 2018-12-27

---

You're welcome

(CID:137728453)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.