HP ProLiant DL380p Configuring Arrays on HP Smart Array Controllers Reference - Page 59

Identifying devices, Deleting target devices, Generating a diagnostic report

Page 59 highlights

Identifying devices You can enter a command that causes the LEDs on target devices to flash, enabling you to identify the devices. After an hour, the LEDs stop flashing. You can also stop LED flashing by entering the off command. Syntax: modify led=on|off Example commands: => ctrl ch="Lab 4" modify led=on => ctrl ch="Lab 4" array A modify led=off Deleting target devices Syntax: delete [forced] where can be a controller, array, or logical drive. Except in the case of controllers, you can delete several devices simultaneously if they are of similar type by using the all keyword. Because deleting a target device can result in data loss, the screen displays a warning prompt unless you include the forced parameter. Example commands: => ctrl ch="Lab 4" delete forced => ctrl slot=3 ld all delete Generating a diagnostic report HP provides several ways for administrators to generate diagnostic information, including all three ACU formats and the standalone HP Array Diagnostics and SmartSSD Wear Gauge Utility. In ACU CLI, the diag command outputs diagnostic information about a specified controller or all controllers on the system. The ssdrpt option generates the SmartSSD Wear Gauge report. Syntax: diag [ris=on|off] [ssdrpt=on|off] [xml=on|off] [zip=on|off] where the following is designated: • is a controller or all controllers. • designates the target file in which the diagnostic information is saved. • [ris=on|off] determines whether RIS information is or is not included. The off value is provided for backward compatibility and is ignored. • [ssdrpt=on|off] specifies to generate or not generate the Smart SSD Wear Gauge report. The default is off. • [xml=on|off] outputs diagnostic information in formatted XML. The off value is provided for backward compatibility and is ignored. • [zip=on|off] compresses the output to a zipped file. Default behavior is uncompressed. The off value is provided for backward compatibility and is ignored. Example commands: ctrl all diag file=c:\allcontrollers.zip ctrl slot=4 diag file=c:\ctrl_slot4.zip ctrl ch="mybox" diag file=mybox.zip ssdrpt=on HP Array Configuration Utility 59

  • 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

HP Array Configuration Utility
59
Identifying devices
You can enter a command that causes the LEDs on target devices to flash, enabling you to identify the
devices. After an hour, the LEDs stop flashing. You can also stop LED flashing by entering the
off
command.
Syntax:
<target> modify led=on|off
Example commands:
=> ctrl ch="Lab 4" modify led=on
=> ctrl ch="Lab 4" array A modify led=off
Deleting target devices
Syntax:
<target> delete [forced]
where
<target>
can be a controller, array, or logical drive. Except in the case of controllers, you can
delete several devices simultaneously if they are of similar type by using the
all
keyword.
Because deleting a target device can result in data loss, the screen displays a warning prompt unless you
include the
forced
parameter.
Example commands:
=> ctrl ch="Lab 4" delete forced
=> ctrl slot=3 ld all delete
Generating a diagnostic report
HP provides several ways for administrators to generate diagnostic information, including all three ACU
formats and the standalone HP Array Diagnostics and SmartSSD Wear Gauge Utility.
In ACU CLI, the
diag
command outputs diagnostic information about a specified controller or all controllers
on the system. The
ssdrpt
option generates the SmartSSD Wear Gauge report.
Syntax:
<target> diag <file=filename> [ris=on|off] [ssdrpt=on|off] [xml=on|off]
[zip=on|off]
where the following is designated:
<target>
is a controller or all controllers.
<file=filename>
designates the target file in which the diagnostic information is saved.
[ris=on|off]
determines whether RIS information is or is not included. The
off
value is provided for
backward compatibility and is ignored.
[ssdrpt=on|off]
specifies to generate or not generate the Smart SSD Wear Gauge report. The
default is
off
.
[xml=on|off]
outputs diagnostic information in formatted XML. The
off
value is provided for
backward compatibility and is ignored.
[zip=on|off]
compresses the output to a zipped file. Default behavior is uncompressed. The
off
value is provided for backward compatibility and is ignored.
Example commands:
ctrl all diag file=c:\allcontrollers.zip
ctrl slot=4 diag file=c:\ctrl_slot4.zip
ctrl ch="mybox" diag file=mybox.zip ssdrpt=on