IBM Lpar Instance changes frames and discovery creates a new CI every time

Stacey Shapiro
Tera Expert

Hi community, 

I have an issue where every time an IBM Lpar instance changes frames, then discovery runs on the HMC server, a new CI is created for the IBM Lpar instance. The IRE for virtual machine instance looks at Object id. Object id is derived from the serial number of the frame. So if it changes frames, the seral number and the object id will change. So discovery is working as expected and creates a new CI since object ID is no longer unique. The Class owner is complaining that they have so many CIs for the same lpar instance. They asked me to change the IRE to use NAME since that is unique for there use case. Even after I changed it to use NAME and the LPAR moved frames, a new CI was still created. I opened a HI ticket and they said it is because of the dependency rule that the IBM Lpar has on the IBM Frame. They said this is how it works OOB and recommend not changing it. That is fine but I am not sure how to handle all the CIs that are created every time an LPAR instance changes frames. Wondering if others have the same issue and how they addressed it. Thanks in advance. 

5 REPLIES 5

Rahul Priyadars
Giga Sage
Giga Sage

Name is Same here even when frame is changed ...

In my view lets write a maintenance  Job for CI whose name is same but Frame is changed . Just keep the latest entry for same Sorted on Date.

If i remember in past we have faced i think similar isssue for Solaris LDOMs .

Regards

RP

Hi RP, 

Can you explain more about the maintenance job? Is this a business rule? When you say keep the latest entry, what would you do with the other CI. Is this method favorable over changing the IRE to look at Name and then updating the relationship rules in a manner that would not create a new CI when the lpar changes frames? Thanks again for your help. 

Hi

Approach 1- Change IRE and make NAME as key for Update . 

Approach 2- No Change in IRE and keep the product configuration as OOTB. Write a Schedule Job which

will deactivate / Delete the Older LPAR which are DUPS now.

Regards

RP

Srikanth30
Tera Contributor

Hello @Stacey Shapiro ,

 

Were you able to resolve this issue?

We are in the same boat on having duplicates being created when the frame changes. Did you try updating the IBM HMC Server pattern or applying any other rules/logic? Appreciate your help!