Hi Jiri, In the recon rules are you allowing the CIs to be auto-identified?
Relationships in your discovery dataset will identify with relationships in the production dataset only if the source CIs have the same identities and the destination CIs have the same identities. Make sure that when CIs are created in your discovery dataset they have their recon ID left as '0'. CIs created in the BMC.ASSET dataset automatically have their recon IDs set but, out-of-the-box, other datasets should not be affected. In testing I have often run reconciliation and then reset the discovered CIs' recon IDs back to '0' to try another test. I have always reset normal CIs in the base element form but have often forgotten to reset the base relationship CIs. Maybe you did this? If your discovery only uses the BMC_Dependency relationship class then none of your relationships are weak and all CIs will be reconciled in the same way. If your discovery creates other relationship types then look in the class manager to see whether they are weak. If weak relationships are used then parent CIs plus weak chldren have different, more powerful, behaviours during reconciliation. Cheers Peter > ++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Please Read The Disclaimer At The Bottom Of This Email > ++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Peter, > > I have found issues with our relationship data. > It appears that reconciliation IDs of CIs recorded in the relationship > entry do not match the Reconciliation Identity of the CIs (instance IDs > are correct, so relationship works fine, the problem only appears when > trying to reconcile/merge the relationship data). > I hope I can fix this by clearing the reconciliation identities on CIs and > on relationship records and identifying them again. > > In terms of performing a comparison, our discovery tool submits the > relationships as the dependency type. This, I believe, does not create the > weak relationship between CIs. > Is there a way to compare relationships that do not create the weak > relationship? > > Thanks > Jiri > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] Behalf Of Peter Romain > Sent: 29 February 2008 18:11 > To: [email protected] > Subject: Re: CMDB - how to reconcile and compare relationships > > > Hi Jiri, > > What exactly is it about the relationships that you are trying to > reconcile? > > In my experience the relationships take care of themselves. > > Is your discovery tool creating weak relationships between computer > systems and software? > > Cheers > > Peter > > > > > > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Please Read The Disclaimer At The Bottom Of This Email >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> Hi, >> >> I am trying to use the Atrium CMDB reconciliation engine, but cannot see >> a >> way to reconcile, compare and then update relationships. >> Our discovery tool can create CIs in various classes and then record >> their >> relationship, i.e. what applications run on each server. >> I am trying then to reconcile this data with the 'production' data set, >> which is fine for CIs, but cannot see how I can do the same for >> relationships. >> Similarly, I can then compare CIs in CI classes, but there does not seem >> to be any way to compare relationships. >> This is rather important as relationships store the information on what >> SW >> or applications run on each server and if this changes it is recorded by >> the relationship. >> >> I hope I am missing something obvious here. >> Would appreciate any advice or suggestion. >> >> Thanks >> Jiri Pospisil >> >> LCH.Clearnet >> >> >> ************************************************************************************************* >> >> This email is intended for the named recipient(s) only. Its contents are >> confidential and may only be retained by the named recipient(s) and may >> only be copied or disclosed with the consent of LCH.Clearnet Limited. >> If >> you are not an intended recipient please delete this e-mail and notify >> [EMAIL PROTECTED] >> >> The contents of this email are subject to contract in all cases, and >> LCH.Clearnet Limited makes no contractual commitment save where >> confirmed >> by hard copy. LCH.Clearnet Limited accepts no liability, including >> liability for negligence, in respect of any statement in this email. >> >> LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High >> Street, London EC3N 1EA. Recognised as a Clearing House under the >> Financial Services & Markets Act 2000. Reg in England No.25932 >> Telephone: +44 20 7426 7000 Internet: >> http://www.lchclearnet.com >> >> ************************************************************************************************* >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
