HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 52

Configuring partner firmware update, Configuring system utilities

Page 52 highlights

3. In the Auto-Write Through Cache Behaviors section, either select (enable) or clear (disable) the options: • Revert when Trigger Condition Clears. Changes back to write-back caching after the trigger condition is cleared. Enabled by default. • Notify Other Controller. Notifies the partner controller that a trigger condition occurred. Enable this option to have the partner also change to write-through mode for better data protection. Disable this option to allow the partner continue using its current caching mode for better performance. In a dual-controller system this option is disabled by default. In Single Controller mode this option is grayed out. 4. Click Apply. Configuring partner firmware update In a dual-controller system in which partner firmware update is enabled, when you update firmware on one controller, the system automatically updates the partner controller. Disable partner firmware update only if requested by a service technician. To change the partner firmware update setting 1. In the Configuration View panel, right-click the system and select Configuration > Advanced Settings > Firmware. 2. Either select (enable) or clear (disable) the Partner Firmware Update option. 3. Click Apply. Configuring system utilities Configuring background scrub for vdisks You can enable or disable whether the system continuously analyzes disks in vdisks to find and fix disk errors. This command will fix parity mismatches for RAID 3, 5, 6, and 50; mirror mismatches for RAID 1 and 10; and media errors for all RAID levels. You can use a vdisk while it is being scrubbed. Background vdisk scrub runs at background utility priority, which reduces to no activity if processor usage is above a certain percentage or if I/O is occurring on the vdisk being scrubbed. A vdisk scrub may be in process on multiple vdisks at once. A new vdisk will first be scrubbed 20 minutes after creation. After a vdisk is scrubbed, scrub will start again after the interval specified by the Vdisk Scrub Interval (hours) option. When a scrub is complete, event 207 is logged and specifies whether errors were found and whether user action is required. Enabling background vdisk scrub is recommended. TIP: If you choose to disable background vdisk scrub, you can still scrub a selected vdisk by using Tools > Media Scrub Vdisk (page 88). To configure background scrub for vdisks 1. In the Configuration View panel, right-click the system and select Configuration > Advanced Settings > System Utilities. 2. Set the options: • Either select (enable) or clear (disable) the Vdisk Scrub option. This option is enabled by default. • Set the Vdisk Scrub Interval (hours) option, which is the interval between background vdisk scrub finishing and starting again, from 0-360 hours. The default is 24 hours. 3. Click Apply. Configuring background scrub for disks not in vdisks You can enable or disable whether the system continuously analyzes disks that are not in vdisks to find and fix disk errors. The interval between background disk scrub finishing and starting again is 72 hours. The first time you enable this option, background disk scrub will start with minimal delay. If you disable and then re-enable this option, background disk scrub will start 72 hours after the last background disk scrub completed. Enabling background disk scrub is recommended. 52 Configuring the system

  • 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
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

52
Configuring the system
3.
In the Auto-Write Through Cache Behaviors section, either select (enable) or clear (disable) the options:
Revert when Trigger Condition Clears
. Changes back to write-back caching after the trigger condition is
cleared. Enabled by default.
Notify Other Controller
. Notifies the partner controller that a trigger condition occurred. Enable this option to
have the partner also change to write-through mode for better data protection. Disable this option to allow the
partner continue using its current caching mode for better performance. In a dual-controller system this option
is disabled by default. In Single Controller mode this option is grayed out.
4.
Click
Apply
.
Configuring partner firmware update
In a dual-controller system in which partner firmware update is enabled, when you update firmware on one controller,
the system automatically updates the partner controller. Disable partner firmware update only if requested by a
service technician.
To change the partner firmware update setting
1.
In the Configuration View panel, right-click the system and select
Configuration > Advanced Settings > Firmware
.
2.
Either select (enable) or clear (disable) the
Partner Firmware Update
option.
3.
Click
Apply
.
Configuring system utilities
Configuring background scrub for vdisks
You can enable or disable whether the system continuously analyzes disks in vdisks to find and fix disk errors. This
command will fix parity mismatches for RAID 3, 5, 6, and 50; mirror mismatches for RAID 1 and 10; and media
errors for all RAID levels.
You can use a vdisk while it is being scrubbed. Background vdisk scrub runs at background utility priority, which
reduces to no activity if processor usage is above a certain percentage or if I/O is occurring on the vdisk being
scrubbed. A vdisk scrub may be in process on multiple vdisks at once. A new vdisk will first be scrubbed 20 minutes
after creation. After a vdisk is scrubbed, scrub will start again after the interval specified by the Vdisk Scrub Interval
(hours) option.
When a scrub is complete, event 207 is logged and specifies whether errors were found and whether user action is
required.
Enabling background vdisk scrub is recommended.
TIP:
If you choose to disable background vdisk scrub, you can still scrub a selected vdisk by using
Tools > Media
Scrub Vdisk
(
page 88
).
To configure background scrub for vdisks
1.
In the Configuration View panel, right-click the system and select
Configuration > Advanced Settings > System
Utilities
.
2.
Set the options:
Either select (enable) or clear (disable) the
Vdisk Scrub
option. This option is enabled by default.
Set the Vdisk Scrub Interval (hours) option, which is the interval between background vdisk scrub finishing and
starting again, from 0–360 hours. The default is 24 hours.
3.
Click
Apply
.
Configuring background scrub for disks not in vdisks
You can enable or disable whether the system continuously analyzes disks that are not in vdisks to find and fix disk
errors. The interval between background disk scrub finishing and starting again is 72 hours. The first time you enable
this option, background disk scrub will start with minimal delay. If you disable and then re-enable this option,
background disk scrub will start 72 hours after the last background disk scrub completed.
Enabling background disk scrub is recommended.