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

About firmware update, Average I/O Size - iops

Page 33 highlights

Disk-performance graphs include: • Data Transferred • Data Throughput • I/O • IOPS • Average Response Time • Average I/O Size • Disk Error Counters • Average Queue Depth Vdisk-performance graphs include: • Data Transferred • Data Throughput • Average Response Time You can save historical statistics in CSV format to a file for import into a spreadsheet or other third-party application. You can also reset historical statistics, which clears the retained data and continues to gather new samples. NOTE: The SMU does not show live statistics. For information about viewing live statistics, see the CLI Reference Guide. Related topics • "Vdisk performance" (page 101) (to view historical performance statistics for a vdisk) • "Disk performance" (page 113) (to view historical performance statistics for a disk) • "Resetting historical disk-performance statistics" (page 91) • "Saving historical disk-performance statistics" (page 91) About firmware update Controller modules, expansion modules, and disk drives contain firmware that operate them. As newer firmware versions become available, they may be installed at the factory or at a customer maintenance depot or they may be installed by storage-system administrators at customer sites. The controller-module firmware-update algorithm supports the following scenarios for a dual-controller system: • The administrator installs a new firmware version in one controller and wants that version to be transferred to the partner controller. • In a system that has been qualified with a specific firmware version, the administrator replaces one controller module and wants the firmware version in the remaining controller to be transferred to the new controller (which might contain older or newer firmware). When a controller module is installed into an enclosure at the factory, the enclosure midplane serial number and firmware-update timestamp are recorded for each firmware component in controller flash memory, and will not be erased when the configuration is changed or is reset to defaults. These two pieces of data are not present in controller modules that are not factory-installed and are used as replacements. When you update controller firmware, you can use the Partner Firmware Update option to ensure that the same firmware version is installed in both controller modules. This option uses the following algorithm to determine which controller module will update its partner: • If both controllers are running the same firmware version, no change is made. • If the firmware in only one controller has the proper midplane serial number then the firmware in that controller is transferred to the partner controller. • If the firmware in both controllers has the proper midplane serial number then the firmware having the latest firmware-update timestamp is transferred to the partner controller. System concepts 33

  • 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

System concepts
33
Disk-performance graphs include:
Data Transferred
Data Throughput
I/O
IOPS
Average Response Time
Average I/O Size
Disk Error Counters
Average Queue Depth
Vdisk-performance graphs include:
Data Transferred
Data Throughput
Average Response Time
You can save historical statistics in CSV format to a file for import into a spreadsheet or other third-party application.
You can also reset historical statistics, which clears the retained data and continues to gather new samples.
NOTE:
The SMU does not show live statistics. For information about viewing live statistics, see the CLI Reference
Guide.
Related topics
"Vdisk performance" (page 101)
(to view historical performance statistics for a vdisk)
"Disk performance" (page113)
(to view historical performance statistics for a disk)
"Resetting historical disk-performance statistics" (page 91)
"Saving historical disk-performance statistics" (page 91)
About firmware update
Controller modules, expansion modules, and disk drives contain firmware that operate them. As newer firmware
versions become available, they may be installed at the factory or at a customer maintenance depot or they may be
installed by storage-system administrators at customer sites. The controller-module firmware-update algorithm supports
the following scenarios for a dual-controller system:
The administrator installs a new firmware version in one controller and wants that version to be transferred to the
partner controller.
In a system that has been qualified with a specific firmware version, the administrator replaces one controller
module and wants the firmware version in the remaining controller to be transferred to the new controller (which
might contain older or newer firmware).
When a controller module is installed into an enclosure at the factory, the enclosure midplane serial number and
firmware-update timestamp are recorded for each firmware component in controller flash memory, and will not be
erased when the configuration is changed or is reset to defaults. These two pieces of data are not present in
controller modules that are not factory-installed and are used as replacements.
When you update controller firmware, you can use the Partner Firmware Update option to ensure that the same
firmware version is installed in both controller modules. This option uses the following algorithm to determine which
controller module will update its partner:
If both controllers are running the same firmware version, no change is made.
If the firmware in only one controller has the proper midplane serial number then the firmware in that controller is
transferred to the partner controller.
If the firmware in both controllers has the proper midplane serial number then the firmware having the latest
firmware-update timestamp is transferred to the partner controller.