Avago Technologies MegaRAID Fast Path Software - Manual (Page 243)

LSI Corporation Confidential | July 2011 Page 243
MegaRAID SAS Software User Guide Chapter 5: MegaRAID Command Tool | Configuration-Related Options
NOTE: -AdpEventLogInfo does not support the file option in PCLI.
5.12.2 Set BBU Terminal Logging Use the command in the following table to set the BBU terminal logging for the
selected controllers.
5.13 Configuration-Related
Options
You can specify the drives by using the Enclosure ID:Slot ID for SAS controllers. This
option assumes that all drives are connected to the controller through an enclosure. If
the drives are not connected to an enclosure, they are assumed to be connected to
Enclosure 0. In this case no slot exists, so you can use the pdlist command to get the
slot equivalent number. (This option applies to all commands that use the Enclosure
ID:Slot ID format.) MegaCLi expects the input in [:S] format for directly attached devices.
In the following options, [E0:S0, E1:S1] specifies the enclosure ID and slot ID for the
drive.
5.13.1 Create a RAID Drive Group
from All Unconfigured-Good Drives
Use the command in the following table to create one RAID drive group out of all of the
Unconfigured Good drives, and a hot spare, if desired. This command is for RAID levels
0, 5, 6, 10, 50, or 60. All free drives are used to create a new drive group and, if desired,
one hot spare drive. If it is not possible to use all of the free drives, the command will
abort with a related error level. If drives of different capacities exist, the largest drive is
used to make the hot spare.
NOTE: The firmware supports only 32 drives per drive group. If more than 32
Unconfigured Good drives exist, MegaCLi cannot configure any of the drives, and the
command aborts.
Table 72: Set BBU Terminal Logging
Convention MegaCli –FwTermLog -Bbuoff |–BbuoffTemp|-Bbuon|-BbuGet| -aN| -a0,1,2|-aALL
Description Sets BBU terminal logging options. The following are the settings you can select on a single controller, multiple
controllers, or all controllers:
-Bbuoff : While storing the TTY log in DRAM, BBU is not used for buffering. In the case of power loss, this log is
lost..
–BbuoffTemp : TTY BBU buffering will be set to off only for this boot.
-Bbuon : While storing the TTY log in DRAM, BBU is used for buffering. The Log is preserved even in the case of
power loss.
-BbuGet : This parameter gives the current BBU state, i.e., if BBU is on or off for TTY history.