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

[Stacey Shapiro]

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. 

[Stacey Shapiro]

We changed the IRE to use name instead of serial on the IBM Lpar Instance. Did not want to customize the pattern. Thanks!