Question about Discovery and Bulk Import

Unanswered Question
Apr 24th, 2009
User Badges:

I have added all of our devices so far via Bulk Import using a csv file. I have a question about using discovery now that I have devices in RME. How do I avoid duplicating all of my devices if I use discovery from here on out? We are getting ready to deploy 1500 VoIP handsets and I want to be able to discover them without importing them. My main concern is using discovery now that I have a working DB and duplicating the current devices. I have names for all of my devices as opposed to IP Addresses and would rather keep it that way. Any ideas or input appreciated.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Fri, 04/24/2009 - 12:24
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

What versions of Campus Manager and Common Services do you have?

Joe Clarke Mon, 04/27/2009 - 09:42
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Then you have nothing to worry about in terms of duplicates. Discovery will automatically resolve duplicates. If you do not want to display name attribute changing in DCR, then do NOT check the "Update DCR Display Name" box in the Discovery Global Settings.

stephenscott Tue, 04/28/2009 - 04:52
User Badges:

Thanks Joe. I tried the suggestions and all went well until I got this error message:

Error in communicating with DCR Server. DCR Server may be down. Please start the DCR Server and then start discovery.

I have made sure this folder is excluded from AntiVirus scanning. I even issued the command net stop crmdmgdt and net start crmdmgdt. I actually get that error quite a bit.

I feel your pain. I can see no rhyme or reason that this occurs (and it occurs to me TOO frequently). I have yet to see any explanation for it either.

Try going in through CW and stopping and re-starting just the DCR SERVER ...

From the Functional Tab go to..

Common Services... Server...Admin...Processes

Scroll down to DCR Server and Select it. Then you can stop it, and re-start it. At that point it SHOULD be running.



This Discussion