-A P P E N D I X

A P P E N D I X B

Monitoring JBODs

This appendix explains how to enable and monitor a standalone JBOD. Note that not all of the array functionality is supported for JBODs. Procedures covered in this appendix include the following:

To Enable JBOD Support

To View Component and Alarm Characteristics

To Download Firmware for Devices

To Discover a Drive

Note - Most Sun StorEdge 3000 family products offer a standalone JBOD. The Sun StorEdge 3120 SCSI array is a standalone JBOD. Only the procedures contained in this appendix apply to the Sun StorEdge 3120 SCSI array.

To Enable JBOD Support

To monitor peripheral device condition and events of a JBOD, you first need to enable JBOD support.

1. Choose View right arrow Agent Options Management.

The Agent Options Management window is displayed.

2. Select the Enable JBOD Support check box.

3. To immediately display the JBOD in the main window, you need to probe for new inventory. Choose View right arrow View Server and click Probe.

4. Click OK.

The JBOD is displayed in the main window.

In a single-bus configuration, both ports of the JBOD are connected to one HBA on the server as shown in the following example.

Screen capture showing a single-bus JBOD configuration.

In a dual-bus configuration, each port is connected to its own HBA as shown in the following example.

Screen capture showing a dual-bus JBOD configuration.

Note - In a dual-bus configuration, if each port is connected to different servers, the program can only monitor the JBOD from the server connected to port B.

To View Component and Alarm Characteristics

The View Enclosure window displays the component and alarm characteristics of a JBOD. When a JBOD is in a state that requires attention, a device status state symbol is displayed on the JBOD device in the main window. See Device Status State for a description of the symbols.

1. Select the EMU (SCSI) or SES (Fibre Channel) icon EMU icon .

2. Choose View right arrow View Enclosure.

To display FRU ID information, click View FRU.

Screen capture showing the View Enclosure window.

To Download Firmware for Devices

For instructions on how to download firmware to disk drives for the Solaris host, refer to the README file in the patch that contains the firmware. For patch information, refer to the release notes for your array.

To Discover a Drive

Drive failure places the JBOD in a critical state. A red device status symbol Critical symbol is displayed on the JBOD device in the main window. After replacing a failed drive, perform the following steps to discover the drive.

Solaris OS

The following steps describe how to discover the replaced drive on systems running the Solaris OS.

1. If the drive comes back online automatically (that is, the red device status symbol is dismissed), run the command:

# devfsadm

2. Run the command:

# format

3. If the drive does not come back online automatically (that is, the red device status symbol is not dismissed), perform a reconfiguration reboot by running the command:

# reboot -- -r

Linux OS

The following steps describe how to discover the replaced drive on systems running the Linux OS.

1. Reboot the system.

2. Run the command:

# dmesg

3. In the dmesg output, look for a line similar to "Detected scsi disk sdX at scsi<controller>, id <channel>, lun <target>" where the X in sdX is the disk number.

4. To create the device entries in /dev, run the command:

# cd /dev; ./MAKEDEV sdX

Where the X in sdX is the disk number.

5. Proceed to fdisk, format, and create a file system.

Microsoft Windows OS

The following steps describe how to discover the replaced drive on a Microsoft Windows OS.

1. Install the new drive according to the instructions in the Sun StorEdge 3000 Family Installation, Operation, and Service Manual for your array.

2. Select View right arrow View Server, and click Rescan.

3. To verify that the program recognizes the new drive, select it on the main window.

4. Select View right arrow View Physical Drive, and verify the information.

HP-UX OS

The following steps describe how to discover the replaced drive on systems running the HP-UX OS.

1. Run the command:

# ioscan -fnC disk

2. Select View right arrow View Server, and click Rescan.

3. To verify that the program recognizes the new drive, select it on the main window.

4. Select View right arrow View Physical Drive, and verify the information.

5. If the drive is still not seen, the host might need to be rebooted. Run the commands:

# sync;sync;sync

# reboot

IBM AIX OS

The following steps describe how to discover the replaced drive on systems running the IBM AIX OS.

Note - You must have superuser privileges to run the commands necessary to replace a failed drive.

1. Create the logical drive and map its LUN to the correct host channel.

2. Run the command:

# cfgmgr

3. Run the command:

# lspv

Output similar to the following is displayed.

hdisk0 000df50dd520b2e rootvghdisk1 000df50d928c3c98 Nonehdisk1 000df50d928c3c98 None

4. If any of the drives show "none," you need to assign a Physical Volume IDENTIFIER.

5. Run the command:

# smitty

a. Select Devices.

b. Select Fixed Disk.

c. Select Change/Show Characteristics of a Disk.

d. Select the disk without a pvid.

e. Select ASSIGN physical volume identifier, press Tab once to display Yes for the value, and press Return.

f. Press Return again to confirm and repeat steps a-g as necessary.

6. From the smitty main menu, select System Storage Management (Physical & Logical Storage) right arrow Logical Volume Manager Volume Groups Add a Volume Group.

7. Specify a name for the volume group, make sure the partitions for the journaled file system are large enough, and select the Physical Volume Name(s).

8. From the smitty main menu, select System Storage Management (Physical & Logical Storage) right arrow File Systems Add / Change / Show / Delete File Systems (Enhanced) Journaled File System.

9. Select the volume group and set the field.

Run the command:

# umount mount point