Impact of Upgrade from a Release Prior to Release 1.3(1i)
An upgrade from an earlier Cisco UCS firmware release to release 1.3(1i) or higher has the following impact
on the Protect Configuration property of the local disk configuration policy the first time servers are associated
with service profiles after the upgrade:
Unassociated Servers
After you upgrade the Cisco UCS domain, the initial server association proceeds without configuration
errors whether or not the local disk configuration policy matches the server hardware. Even if you
enable the Protect Configuration property, Cisco UCS does not protect the user data on the server if
there are configuration mismatches between the local disk configuration policy on the previous service
profile and the policy in the new service profile.
If you enable the Protect Configuration property and the local disk configuration
policy encounters mismatches between the previous service profile and the
new service profile, all subsequent service profile associations with the server
are blocked.
Note
Associated Servers
Any servers that are already associated with service profiles do not reboot after the upgrade. Cisco UCS
Manager does not report any configuration errors if there is a mismatch between the local disk
configuration policy and the server hardware.
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.
Guidelines for Local Disk Configuration Policies Configured for RAID
No Mixed HDDs and SSDs
Do not include HDDs and SSDs in a single RAID configuration.
Do Not Use the Any Configuration Mode on Servers with MegaRAID Storage Controllers
If a blade server or rack-mount server in a Cisco UCS domain includes a MegaRAID storage controller, do
not configure the local disk configuration policy in the service profile for that server with the Any
Configuration mode. If you use this mode for servers with a MegaRAID storage controller, the installer for
the operating system cannot detect any local storage on the server.
If you want to install an operating system on local storage on a server with a MegaRAID storage controller,
you must configure the local disk configuration policy with a mode that creates a RAID LUN (RAID volume)
on the server.
Server May Not Boot After RAID1 Cluster Migration if Any Configuration Mode Specified in Service Profile
After RAID1 clusters are migrated, you need to associate a service profile with the server. If the local disk
configuration policy in the service profile is configured with Any Configuration mode rather than RAID1,
the RAID LUN remains in "inactive" state during and after association. As a result, the server cannot boot.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
408 OL-25712-04
Configuring Local Disk Configuration Policies