| Sun StorEdge 3000 Family CLI 1.5 User's Guide |    
|
| Sun StorEdge 3000 Family CLI 1.5 User's Guide |
|
| C H A P T E R 3 |
|
Controller, Disks, and Battery Commands |
This chapter provides the available controller, disks, and battery commands with sample code. Topics covered in this chapter include:
The following commands are explained in this section:
The fail command simulates a controller failure and causes all the LUNs assigned to the specified controller to fail over to the redundant controller.
|
Note - Before running this command, perform a show redundancy command to make sure a secondary controller exists. |
|
Fails the logical drive to the primary controller (default). |
|
The following example fails the secondary controller if Y is specified at the prompt. Specify N to cancel the failure.
The mute controller command silences the controller's audible alarm. After the fault condition that caused the alarm to sound is cleared, the next fault condition causes the alarm to sound again.
For details on alarms, refer to the Sun StorEdge 3000 Family Installation, Operation, and Service Guide for your array.
|
Note - This command works on RAID subsystems. It does not work on JBODs. To manually silence a JBOD alarm, push the Reset button on the right ear of the array. |
Use the password command to supply the password assigned to the array controller. The user must specify the correct password when issuing potentially dangerous commands to the array over a network connection. For interactive sessions, the CLI prompts the user for this password only when necessary; the password command is provided for non-interactive applications where the password must be embedded in a script. No password is required when accessing the array using in-band SCSI. For details on setting the password, see set password.
|
Note - Use quotation marks around password strings that contain spaces or apostrophes. |
The following example supplies the controller password, test.
The reset controller command shuts down the controller, flushes its cache to disk, and then restarts the controller. This temporarily causes the array to go offline, which might affect applications running on any hosts connected to the array. Also see shutdown controller.
|
Caution - All reset commands are potentially dangerous. Use only as instructed. |
This command sets cache mode (write-back or write-through) and optimization (sequential or random-access).
The following example sets the cache mode to write-back.
The following example sets the cache mode to write-back and the optimization to sequential.
The set controller-name command specifies a name for the array. The name can be between 1 and 15 characters, but the number of characters plus the length of the current controller password must not be more than 16 characters.
The following example sets the controller name as testname:
This command sets the controller password. The password must be fewer then 8 characters.
The following example sets the controller password as sun123:
This command is a shortcut for the set inter-controller-link command.
The following example sets the port bypass circuit for channel 5 on the upper controller slot to enabled.
This command specifies a password that protects the RS-232 character interface, Telnet, and FTP services from unauthorized use. The string can be any alphanumeric string up to 15 characters in length, provided that the sum of the lengths of the password and the controller-name parameter is not more than 16.
To remove an existing password, specify a zero-length string with a pair of double-quote characters. For example:
This command specifies the speed, in bits per second, for the specified RAID controller port. Single controller configurations have a single RS232 port (port 1). Redundant controllers have a second port (port 2). Usually, both ports are connected to support controller failover, so both should be set to the same speed. The default speed is 38400. The controller must be reset for this change to take effect.
set rs232-configuration port-number speed |
In the following example, the RAID controller RS232 port 1 band rate is set to 38400:
This command specifies the unique identifier for the array subsystem as a 6-digit hexadecimal number from 0 to 0xfffff. This identifier is initialized from the chassis serial number automatically, and should not be changed unless the chassis is replaced.
This value is used to construct unique values for Ethernet address, FC WWNs, and other identifiers, and changing it unnecessarily might cause the logical units to become inaccessible to hosts. The controller must be reset for this change to take effect.
The following example sets the controller unique identifier as 0x1234:
The following example sets the controller unique identifier to the default value based on the chassis serial number. This command must be followed by the reset controller command before the change takes effect.
This command displays the cache write policy for the controller. Values returned include: write through or write back.
The following example shows the cache policy is set to write back.
This command displays the RAID controller name. If the RAID controller name is not set, the command returns "not set."
The following example shows the controller name is test.
This command displays the SCSI INQUIRY data returned by the array controller. The output of this command varies from one product to another, and from one channel to another.
The following example shows an in-band Sun StorEdge 3510 inquiry:
The show-redundancy mode command shows whether the two controllers are operating correctly as a redundant pair. Returned values include: Active-Active, disabled, enabled, primary, or secondary.
The following example shows the controller mode is Active-Active.
sccli> show redundancy-mode Primary controller serial number: 3341097 Redundancy mode: Active-Active Redundancy status: Enabled Secondary controller serial number: 3341045 |
This command displays the controller unique identifier, which defaults to the enclosure serial number. A valid controller unique identifier is a hexidecimal number from 0 to 0xfffff. It is displayed as a 6-digit value, where the first digit is always 0 for consistency with the presentation of FRU serial numbers. The default value for the unique ID is the FRU serial number of the midplane/chassis in which the controller resides.
The following example shows the unique identifier is 00476F.
This command shuts down the RAID controller and stops I/O processing. This temporarily causes the array to go offline, which might affect applications running on any hosts connected to the array. Data in the controller cache is flashed to logical drives. After issuing this command, issue the reset controller command.
|
Note - Use this command whenever the RAID controller is powered off. It ensures that all data is written to disk, and that the backup battery (if present) will not be drained by the cache memory. |
The unfail command reverses the fail secondary command, permitting the secondary controller to resume operation and restore the controller pair to normal (redundant) operation.
|
Note - When a primary controller fails, the secondary controller becomes the primary controller. The unfail command makes the initial primary controller the secondary controller. |
The following example reverses the fail secondary command.
The following commands are explained in this section:
This command specifies a global spare disk. The disk drive status is set to standby.
|
Specify the disk to create. For example, specify the disk with target ID 1 on channel 2 as 2.1. |
The following example configures disk drive ID 5 on SCSI channel 2 as a global spare:
SCSI arrays only. This command illuminates the drive LED for the specified disk (or slot). For JBODs, specify a disk device using a Solaris device name such as sd31 or c1t0d0s2, or specify a slot number. Use the show led-status command to show the status of the identified disk drive.
To illuminate a specific drive LED in a RAID array, use the following parameters:
To illuminate a specific drive LED in a JBOD, use the following parameters:
In the following example, assume the user wants to identify the drive with SCSI address 8 in the enclosure associated with the enclosure device /dev/es/ses0:
This command displays information about the disk drives in the array enclosure and any expansion chassis.
The following example returns information for disks ID 0, ID 3, and ID 7 on SCSI channel 2:
The following example returns information for disks on SCSI channel 2 for disks 3 through 7, and for SCSI channel 1 disk 4:
Returned values include: channel number, disk SCSI ID, size, speed (megabytes per second), LD assignment, status, vendor and product ID. If the -b option is specified, the drive buffer size and drive serial number are displayed.
The following example shows all disk information.
This command displays the status of the LED adjacent to the specified disk drive slot in the array enclosure or expansion chassis.
To display the status of LEDs in LVD RAID enclosures, use the following syntax:
To show the status of LVD JBOD enclosures, use the following parameters:
The following example shows the status of the LED adjacent to the disk assigned to drive slot 3 for an expansion chassis:
This command unconfigures a global spare disk.
|
Specify the disk to create. For example, specify the disk with target ID 1 on channel 2 as 2.1. |
The following example unconfigures disk drive ID 5 on SCSI channel 2 as a global spare:
The show battery-status command is explained in this section.
Fibre Channel arrays only. This command displays the status of the battery modules, which preserve the nonvolatile cache memory in each RAID controller. For redundant controllers, status for both batteries is shown. Status values include: Expired, Warning, or Good. A status of Warning indicates that the battery will expire within 21 days.
If the battery type is an early board module, then battery expiration monitoring is not supported. In this case, a message displays that says, "battery board type is not supported."
The following example shows one good battery and one expired battery:
The following example shows one good battery one and one battery that is set to expire within the next week:
| Sun StorEdge 3000 Family CLI 1.5 User's Guide | 817-4951-10 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.
