Associate/Disassociate Service Profile

[Stephan Perschke]

Hi,

I run into a problem when associating a service profile that was associate with another server before.

We have two equally equipped C240 M4S servers. I associated a Service Profile - including a Storage Profile - to the first server. Requested by the Storage Profile two LUNs were created. Later I disassociated the Service Profile again and tried to associate it with the second C240 M4S but failed with the following error message

Failed to modify Service Profile MyProfile1s association. Cause: {1} object ot found: object of class storageVirtualDrive with RN vd-1001

Checking the first server I recognized that the two LUNs still existed but their Config State was now Orphaned. After manually deleting the two orphaned LUNs I was successfully able to assiciate the Service Profile with the second server.

I'm running UCS Manager 2.2(6c) but assigned Host Firmware Package 2.2(6e) to the two servers.

This issue has quite some impact as it makes automation more complex.

Kind regards,

Stephan

[Kirk J]

Greetings.

If you know you will want to re-provision local storage, make sure your local disk policy is not set to 'protect config' prior to disassociating the original service profile.

If the 'protect' configuration flag is not set on a given server's local raid controller/meta data, the new service profile should be able to remove, and recreate the new configuration, provided all the other requirements are met.

On the server that required you to manually remove the two orphaned LUNs, do you recall if the previous service profile had the 'protect' config enabled on the local disk policy?

Thanks,

Kirk...

[Stephan Perschke]

Hi Kirk,

thank you again for your response.

To be honest, I wasn't aware of the "Protect Config" setting and checked it immediately. Unfortunately it is not set so this cannot be the cause for this issue.

Kind regards,
Stephan