Users Guide

Table Of Contents
NOTE: If there are no physical disks in Ready state, the Auto Configure RAID0 operation fails and displays an error
message. For more information about alerts and their corrective actions, see the Server Administrator Messages Reference
Guide. at dell.com/openmanagemanuals.
Set the Auto Configure Behavior of a RAID controller
By using the Auto-Configure Behavior feature in OpenManage 10.0.1 and later versions, you can enable a RAID controller
(PERC) to automatically convert "ready" state (unconfigured good) physical drives into non-RAID physical drives. The current
available options for setting the auto-configure behavior are:
Non-RAID DiskConverts the following types of hard drives into non-RAID physical drives after enabling and restarting a
system:
All "ready state" (unconfigured good) physical drives that are available in the system (online drives).
An "ready state" (unconfigured good) physical drive that is hot-inserted.
OffThe hot-inserted unconfigured good physical drives are not automatically converted to non-RAID physical drives.
However, any available non-RAID physical drives will continue to stay in its mode online, and any physical drives in Ready
state will continue to remain in the same state even after restarting the system.
To set the auto-configure mode of a RAID controller (PERC), do the following on the OpenManage Server Administrator page:
1. In the Server Administrator window, in the left pane, expand System > Storage.
2. Select the controller.
3. In the working pane, click Information/Confirmation.
4. On the Controller Information <
controller name
> page, from the Controller Tasks drop-down menu, select Set Auto
Configure Behavior.
5. Click Execute.
On the Set Auto Configure Behavior for <
controller name
> page, the current state of auto-configure mode is displayed.
6. In the New Auto Configure Behavior section, select the required mode
7. Click Apply Changes.
The updated auto-configure mode of the controller is displayed in the Auto Configure Behavior row.
System Configuration Lock Down Mode
System Configuration Lock Down Mode provide a configurable option to the customer so that after it is enabled, any
configuration on that particular system is not permitted with some exceptions. Typical usage of this setting is after the system
is provisioned to a certain level along with the rest of the systems in the domain then enabling this mode reduces the drift the
systems usually see during the operation over a period of time.
When the server is in System configuration lock down mode you will not be allowed to initiate any of the configuration
operation from either OMSS GUI or CLI. If this mode is set, you are not allowed to perform most of the operations in OMSS
except some of the enumeration or reporting operations.
You can enable the lock down mode from the iDRAC GUI. For enabling the lock down mode, you have to select the Turn on the
System Lockdown mode option from the More Actions drop-down menu on the iDRAC page. It may take some time for the
changes to be available on the OMSS GUI.
NOTE:
OMSS does not support configuring or setting the lock down mode from either GUI or CLI. For enabling the system
configuration lock down mode, you have to access iDRAC GUI or similar applications.
NOTE: If you restart the data manager/Engine service after setting the system lock down mode on, then the immediate
reflection on the OMSS page happens. You might have to refresh the OMSS GUI after the restart, if required.
OMSS CLI: Only the tasks available or supported in the GUI will be available or supported in the OMSS CLI, when the system
is in System configuration lock down mode. If you try to run any of the unsupported operation, the following error message is
displayed.
Error! System Configuration Lockdown mode is turned ON. Configuration actions cannot be
performed in this mode. Operation failed!!!
Controllers
79