3Ware 9650SE-2LPB-10 CLI Guide - Page 61

/cx set exportjbod=on|off, /cx set ondegrade=cacheoff|follow, /cx set spinup=nn, cacheoff, follow

Get 3Ware 9650SE-2LPB-10 - Sataii Raid Hardware 10Pk PDF manuals and user guides
UPC - 693494601022
View all 3Ware 9650SE-2LPB-10 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 61 highlights

Controller Object Commands /cx set exportjbod=on|off This command allows you to set the JBOD Export Policy to on or off. By default, exportjbod is off. If the JBOD export policy is off, CLI will not be able to create JBODs. During reboot, 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, to take advantage of features such as RAID level migration. /cx set ondegrade=cacheoff|follow This command is only for 9500S controllers. This command allows you to set a controller-based write cache policy. If the policy is set to cacheoff and a unit degrades, the firmware will disable the write-cache on the degraded unit, regardless of what the unit-based write cache policy is. If the policy is set to follow and a unit degrades, firmware will follow whatever cache policy has been set for that unit. (For details about the unit-based policy, see "/cx/ux set cache=on|off [quiet]" on page 68.) /cx set spinup=nn This command is only for 9000 series controllers. This command allows you to set a controller-based Disk Spinup Policy that specifies how many drives can spin up at one time. The value must be a positive integer between 1 and the number of disks/ports supported on the controller (4, 8, or 12). The default is 1. This policy is used to stagger spinups of disks at boot time in order to spread the power consumption on the power supply. For example, given a spinup policy of 2, the controller will spin up two disks at a time, pause, and then spin up another 2 disks. The amount of time to pause can be specified with the Spinup Stagger Time Policy (/cx set stagger). Not all drives support staggered spinup. If you enable staggered spinup and have drives that do not support it, the setting will be ignored. www.3ware.com 55

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
Controller Object Commands
www.3ware.com
55
/c
x
set exportjbod=on|off
This command allows you to set the JBOD Export Policy to
on
or
off
. By
default, exportjbod is
off
.
If the JBOD export policy is
off,
CLI will not be able to create JBODs. During
reboot, 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, to
take advantage of features such as RAID level migration.
/c
x
set ondegrade=cacheoff|follow
This command is only for 9500S controllers.
This command allows you to set a controller-based write cache policy. If the
policy is set to
cacheoff
and a unit degrades, the firmware will disable the
write-cache on the degraded unit, regardless of what the unit-based write
cache policy is. If the policy is set to
follow
and a unit degrades, firmware will
follow whatever cache policy has been set for that unit. (For details about the
unit-based policy, see “/cx/ux set cache=on|off [quiet]” on page 68.)
/c
x
set spinup=
nn
This command is only for 9000 series controllers.
This command allows you to set a controller-based Disk Spinup Policy that
specifies how many drives can spin up at one time. The value must be a
positive integer between 1 and the number of disks/ports supported on the
controller (4, 8, or 12). The default is 1.
This policy is used to stagger spinups of disks at boot time in order to spread
the power consumption on the power supply. For example, given a spinup
policy of 2, the controller will spin up two disks at a time, pause, and then spin
up another 2 disks. The amount of time to pause can be specified with the
Spinup Stagger Time Policy (
/c
x
set stagger
).
Not all drives support staggered spinup. If you enable staggered spinup and
have drives that do not support it, the setting will be ignored.