Controller Object Commandswww.3ware.com 55/cx set exportjbod=on|offThis command allows you to set the JBOD Export Policy to on or off. Bydefault, exportjbod is off.If the JBOD export policy is off, CLI will not be able to create JBODs. Duringreboot, firmware will not export JBOD units to the operating system.The JBOD Export Policy is only supported on 9000-series controllers.Previous models did not have such a policy enforcement feature.A JBOD is an unconfigured disk attached to your 3ware RAID controller.AMCC recommends that you use Single Disk as a replacement for JBOD, totake advantage of features such as RAID level migration./cx set ondegrade=cacheoff|followThis command is only for 9500S controllers.This command allows you to set a controller-based write cache policy. If thepolicy is set to cacheoff and a unit degrades, the firmware will disable thewrite-cache on the degraded unit, regardless of what the unit-based writecache policy is. If the policy is set to follow and a unit degrades, firmware willfollow whatever cache policy has been set for that unit. (For details about theunit-based policy, see “/cx/ux set cache=on|off [quiet]” on page 68.)/cx set spinup=nnThis command is only for 9000 series controllers.This command allows you to set a controller-based Disk Spinup Policy thatspecifies how many drives can spin up at one time. The value must be apositive integer between 1 and the number of disks/ports supported on thecontroller (4, 8, or 12). The default is 1.This policy is used to stagger spinups of disks at boot time in order to spreadthe power consumption on the power supply. For example, given a spinuppolicy of 2, the controller will spin up two disks at a time, pause, and then spinup another 2 disks. The amount of time to pause can be specified with theSpinup Stagger Time Policy (/cx set stagger).Not all drives support staggered spinup. If you enable staggered spinup andhave drives that do not support it, the setting will be ignored.