I have created a Service Profile with the Local Disk Configuration Policy set to the default value. All went ok until I wanted to associate a different profile, now with RAID1 as the policy for the local disks. Here I got a misconfiguration error. Apparently, the default disk policy has the Protect Configuration activated by default and only Any Configuration mode is now accepted.
On the Cisco documentation it says the following about the Protect Configuration setting:
If checked, the server retains the configuration in the local disk configuration policy even if the server is disassociated from the service profile.
This property is checked by default.
When a service profile is disassociated from a server and a new service profile associated, the setting for the Protect Configuration property in the new service profile takes precedence and overwrites the setting in the previous service profile.
If you disassociate the server from a service profile with this option enabled and then associate it with a new service profile that includes a local disk configuration policy with different properties, the server returns a configuration mismatch error and the association fails.
So, from what I understand just create a new service profile with a Local Disk Policy that has the same Mode (Any Configuration in this case) but with the Protect Configuration not activated, and on associating it the new setting for Protect Configuration will be overwritten.
I've tried this, but it doesn't work. The new profile gets associated with the new created LocalDisk Configuration Policy but the setting for Protect Configuration does not get overwritten.
Do you have any suggestions?
P.S. The firmware version is 1.3(1n)