storage disk set-led
Suggest changes
PDFs
Identify disks by turning on their LEDs
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The storage disk set-led command controls the LED of a specified disk.
You can turn an LED on or off, cause it to blink or stop blinking, or test it.
This command is useful for locating a disk in its shelf.
Parameters
-action {on|off|blink|blinkoff|testall|resetall}- Action-
This parameter specifies the state to which the LED is to be set. Possible values include the following:
-
on - The LED is lit steadily
-
off - The LED is not lit
-
blink - The LED blinks
-
blinkoff - The LED stops blinking and is not lit
-
testall - This tests the operation of every disk enclosure's hardware and drivers per node. Do not use this value in normal operation.
-
resetall - This resets the LED of every disk on the node and lights up the LED of disks with faults.
-
- {
[-disk <disk path name>]- Disk Name -
This specifies the disk whose LED is to be set. Disk names take one of the following forms:
-
Disks are named in the form
<stack-id>.<shelf>.<bay> -
Disks on multi-disk carriers are named in the form
<stack-id>.<shelf>.<bay>.<lun> -
Virtual disks are named in the form <prefix>.<number>, where prefix is the storage array's prefix and number is a unique ascending number.
Disk names take one of the following forms on clusters that are not yet fully upgraded to Data ONTAP 8.3:
-
Disks that are not attached to a switch are named in the form
<node>:<host_adapter>.<loop_ID>. For disks with a LUN, the form is<node>:<host_adapter>.<loop_ID>L<LUN>. For instance, disk number 16 on host adapter 1a on a node named node0a is named node0a:1a.16. The same disk on LUN lun0 is named node0a:1a.16Llun0. -
Disks that are attached to a switch are named in the form
<node>:<switch_name>:<switch_port>.<loop_ID>. For disks with a LUN, the form is<node>:<switch_name>:<switch_port>.<loop_ID>L<LUN>. For instance, disk number 08 on port 11 of switch fc1 on a node named node0a is named node0a:fc1:11.08. The same disk on LUN lun1 is named node0a:fc1:11.08Llun1.
Before the cluster is upgraded to Data ONTAP 8.3, the same disk can have multiple disk names, depending on how the disk is connected. For example, a disk known to a node named alpha as alpha:1a.19 can be known to a node named beta as beta:0b.37. All names are listed in the output of queries and are equally valid. To determine a disk's unique identity, run a detailed query and look for the disk's universal unique identifier (UUID) or serial number.
-
- |
[-adapter <text>]- Adapter Name -
The name of the adapter to which the shelves of disks of interest are attached to.
[-node {<nodename>|local}]- Node Name }-
The node for which action is to be taken.
[-duration <integer>]- Duration (minutes)-
This specifies the duration, in minutes, that the LED is to remain in the specified state. Only actions "on" and "blink" are supported.
[-iteration <integer>]- Test iterations-
This specifies the number of iterations to run the action for. Only action "test-all" is supported.
Examples
The following example causes the LEDs on all disks whose names match the pattern 1.0.* to turn on for 5 minutes:
Cluster1::> storage disk set-led -disk 1.0.* -action on -duration 5
The following example causes the LEDs on disks 1.0.0 and 1.0.1 to turn on for 2 minutes:
Cluster1::> storage disk set-led -disk 1.0.0,1.0.1 -action on -duration 2
The following example causes the LEDs on all disks attached to adapter 0b on Node2 to turn on for 1 minute:
Cluster1::> storage disk set-led -node Node2 -adapter 0b -action on -duration 1
The following example resets the LEDs on all disks on the local node and causes the LEDs of disks with faults to turn on:
Cluster1::> storage disk set-led -action resetall
The following example tests the LEDs on all disks owned by the local node for 3 iterations:
Cluster1::> storage disk set-led -action testall -iteration 3