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:
checked, the server retains the configuration in the local disk
configuration policy even if the server is disassociated from the
This property is checked by default.
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.
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.
I received the config error when I created a new service profile that had a different local disk config policy than the one that was currently assigned to the blade. To resolve I unchecked the protected option on the disk config policy that was assigned to the original service profile.
Disassociated the profile, waited for the whole process to finish, and then re-associated it.
Having at the LocalDiskConfiguration Policy the same Mode as the one stored in the storage contoller, but with the Protect Configuration option not checked, this should have overwritten the settings stored.
But it doesn't happen and I still see the same captures as on the above post.
Problem solved and it had nothing to do with the Service Profile or with the Protect Configuration setting.
Apparently, the UCS Management Interface GUI has a bug on the Inventory tab and it doesn't update the status of the Protect Configuration setting once it gets changed.
I've found this when I needed to connect to the manager from a different workstation than the one that I was using. And surprise... surprise... The Protect Configuration setting was off. Once I restarted the GUI on the original workstation, I got the same results: everything was ok. I was fighting with windmills.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...