Installation guide
Controller Object Commands
www.lsi.com/channel/products  33
( if direct attached), the enclosure and slot (if expander attached), and model 
number of the drive.
The BBU summary lists details about the BBU, if one is installed. It lists the 
online state, readiness, and status of the BBU unit, along with the voltage, 
temperature, charge capacity expressed as time remaining in hours, and the 
BBU's last test date..
You can obtain additional attributes about controllers, units, ports and disks 
by querying for them explicitly. For details, see the other show subcommands.
Example output:
Note that the port information is represented by VPort (virtual port) and 
Cache is represented by both Read Cache and Write cache.
 Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy
 ---------------------------------------------------------------------------
 u0 SPARE OK - - - 149.042 - OFF
 u1 Single OK - - - 149.051 RiW OFF
 VPort Status Unit Size Type Phy Encl-Slot  Model
 ---------------------------------------------------------------------------
 p0 OK - 149.05 GB SATA 3 - WDC WD1600JS-22NCB1
 p1 OK u0 149.05 GB SATA 0 - WDC WD1600JS-22NCB1
 p2 OK u1 149.05 GB SATA 2 - WDC WD1600JS-22NCB1
 p3 OK - 34.18 GB SAS 6 - SEAGATE ST936701SS
/cx show attribute [attribute ...]
The /cx show attribute command shows the current setting of the specified 
attributes on the specified controller. You can specify one or many attributes. 
If you specify an invalid attribute, the loop terminates. Possible attributes are: 
achip, allunitstatus, autocarve , autorebuild , bios, carvesize , driver, 
drivestatus, firmware, memory, model, monitor, numdrives, numports, 
numunits, ctlbus , pcb, pchip, qpolicy, serial, spinup, stagger, and unitstatus. 
Example: To view the driver and firmware version installed on controller 0, 
type the following: 
//localhost> /c0 show driver firmware
/c0 Driver Version = 2.x
/c0 Firmware Version = FE9X 3.x
(In the sample output above, x represents the actual version number.)
Note: If a drive is not present, that port entry is not listed. 
Consequently, the port numbers in the list might not be sequential. Moreover, if 
there are no drives present for the specified controller, the output of its Port 
summary shows an empty summary consisting of only the header










