Lacie 131018 User Manual - Page 91

Status, Hardware/Firmware, Configuration, Operations

Page 91 highlights

Controller Environmentals 8.2.1 Status This group of items are applicable to the functional status of the RAID Controller. They include general controller status, battery status, temperature of the controller, and voltage status. Placing the mouse pointer over the item will display a pop-up window with more detailed information. In the illustrated example, the mouse pointer is over "Voltage" so the voltage data is displayed. Status icons appear adjacent to the item in the group along with a text message. Status icon and text message conditions are defined as green - normal, yellow - warning, and red - failed. When the mouse pointer is rolled over the Battery status icon, the pop-up display provides the remaining charge on the battery expressed as a percentage and the length of time the battery will hold the cache data. A warning icon indicates a below 80% charge (battery is low but most likely charging). An error indicates below 80% charge and the controller has been powered up for over 24 hours. 8.2.2 Hardware/Firmware This group of items are applicable to the controller's physical memory and firmware. From this group you can determine the type of processor, onboard memory size, the firmware version, and the CPLD (Complex Programmable Logic Device) firmware version. The controller's WWN (world wide name) is presented in this group. 8.2.3 Configuration This group identifies the WWN (world wide name) assigned to the configuration, the speed of each port and the LUN assigned to the port. The configuration can be assigned the WWN of any controller preferably one of the controllers installed in the enclosure. For more information on the configuration WWN and port LUN assignment, see 9.2.1 "Identity" beginning on page 92. 8.2.4 Note Operations These items include a group of buttons that allow the user to reset and shutdown each controller individually, update the controller firmware (see 8.2.4.1 on page 83), update the expansion module (Disk I/O or EBOD I/O module) firmware (see 8.2.4.2 on page 85), export the controller logs (see 8.2.4.4 on page 88) and clear the log files (see 8.2.4.3 on page 87). When choosing to shutdown the RAID Controller(s) for an extended period of time, be sure to verify that the Cache Active LED on each RAID Controller is NOT illuminated. If it is, wait until the controlling application has completed writing the data to the disk before continuing with the shutdown. This will ensure that the backup battery is not holding cache data and will prevent the battery from being drained. The user can dump the controller's diagnostic information into a file for use with technical support when troubleshooting a problem by clicking the DIAGNOSTIC DUMP button. 8.2.4.1 Updating the Controller Firmware This option provides the means to update the RAID Controller firmware. The controllers have the ability to automatically update their partners firmware in dual controller configurations, however the update process behaves differently under certain conditions. If one controller has a later version of firmware than its partner controller, during the startup process the later version firmware controller will automatically update the firmware on the lower version controller. If a partner controller fails in a dual controller configuration, when the failed controller is replaced regardless of its firmware version it will always be updated to match the surviving controllers firmware. 83

  • 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
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214

Controller Environmentals
83
8.2.1
Status
This group of items are applicable to the functional status of the RAID Controller. They include general
controller status, battery status, temperature of the controller, and voltage status. Placing the mouse
pointer over the item will display a pop-up window with more detailed information. In the illustrated
example, the mouse pointer is over “Voltage” so the voltage data is displayed. Status icons appear
adjacent to the item in the group along with a text message. Status icon and text message conditions are
defined as green - normal, yellow - warning, and red - failed.
When the mouse pointer is rolled over the Battery status icon, the pop-up display provides the remaining
charge on the battery expressed as a percentage and the length of time the battery will hold the cache
data. A warning icon indicates a below 80% charge (battery is low but most likely charging). An error
indicates below 80% charge and the controller has been powered up for over 24 hours.
8.2.2
Hardware/Firmware
This group of items are applicable to the controller’s physical memory and firmware. From this group you
can determine the type of processor, onboard memory size, the firmware version, and the CPLD
(Complex Programmable Logic Device) firmware version. The controller’s WWN (world wide name) is
presented in this group.
8.2.3
Configuration
This group identifies the WWN (world wide name) assigned to the configuration, the speed of each port
and the LUN assigned to the port. The configuration can be assigned the WWN of any controller
preferably one of the controllers installed in the enclosure. For more information on the configuration
WWN and port LUN assignment,
see 9.2.1 ”Identity” beginning on page 92.
8.2.4
Operations
These items include a group of buttons that allow the user to reset and shutdown each controller
individually, update the controller firmware (see
8.2.4.1 on page 83
), update the expansion module
(Disk I/O or EBOD I/O module) firmware (see
8.2.4.2 on page 85
), export the controller logs (see
8.2.4.4
on page 88
) and clear the log files (see
8.2.4.3 on page 87
).
Note
When choosing to shutdown the RAID Controller(s) for an extended period of time, be sure to verify that
the Cache Active LED on each RAID Controller is NOT illuminated. If it is, wait until the controlling
application has completed writing the data to the disk before continuing with the shutdown. This will
ensure that the backup battery is not holding cache data and will prevent the battery from being drained.
The user can dump the controller’s diagnostic information into a file for use with technical support when
troubleshooting a problem by clicking the
DIAGNOSTIC DUMP
button.
8.2.4.1
Updating the Controller Firmware
This option provides the means to update the RAID Controller firmware.
The controllers have the ability to automatically update their partners firmware in dual controller
configurations, however the update process behaves differently under certain conditions. If one controller
has a later version of firmware than its partner controller, during the startup process the later version
firmware controller will automatically update the firmware on the lower version controller. If a partner
controller fails in a dual controller configuration, when the failed controller is replaced regardless of its
firmware version it will always be updated to match the surviving controllers firmware.