When TD creates a CI in the import dataset it reads back the instanceid and uses that value for any future updates of the CI.
If you have multiple CIs with the same serial number then that's almost definitely what TD found. You can't guarantee that Serial Numbers are unique even though we'd like them to be. The TokenID field is used by the otb recon job to see if the same CI already exists in the production dataset. This is only useful for CIs that were discovered, then lost and their CIs deleted from the import dataset, and then re-discovered or for CIs discovered by other tools using the same rules to create the TokenID. Depending on the identification activity of the TD recon job the recon engine should be able to merge your computers with the same serial numbers to the production dataset without a problem. HTH Peter From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Chowdhury, Tauf Sent: 28 June 2010 18:43 To: [email protected] Subject: Re: Topology and CMDB Synchronization ** I'm pretty sure Topo Disco 1.6 uses a "TokenID" field as the unique identifier during CMDB sync. You may want to start looking there. Most likely, you will then have to clear and re-scan those "duplicate" CI's. Then the Recon should take care of the merge if you haven't modified any of the OOB rules. The OOB rules in the Topo Disco jobs look at hostname being not null, serial number being unique, and Token ID also. I hope this leads you in the right direction. Tauf Chowdhury | Forest Laboratories, Inc. Analyst, Service Management Mobile:646.483.2779 _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Kathy Morris Sent: Monday, June 28, 2010 12:25 PM To: [email protected] Subject: Topology and CMDB Synchronization Hi, We are using Discovery 1.6, CMDB 2.1. We are finding multiple assets in Topology with the same serial number, however each record has different attributes. I thought when an asset is scanned, if the serial number matches, the Discovery updates the unique serial number? So the serial number should only display one time (1X) in the TOPO dataset. For example Serial #453, OS Windows, Dell, Scan date: 4/2/2010 Serial #453, Windows Enterprise, Dell, Scan date: 5/24/2010 When I run to do a merge, if there are 3 serial numbers, how is the engine going to know which record to purge? _____ This e-mail and its attachments may contain Forest Laboratories, Inc. proprietary information that is privileged, confidential or subject to copyright belonging to Forest Laboratories, Inc. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this e-mail to the intended recipient, you are hereby notified that any dissemination, distribution, copying or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
