A P P E N D I X  B

 


Using a Standalone JBOD Array (Sun StorEdge 3510 FC Array Only)

A single Sun StorEdge 3510 FC JBOD array can be connected directly to certain Solaris operating system hosts. This appendix describes the use of Sun StorEdge 3510 FC JBOD arrays.



Note - Sun StorEdge 3511 SATA configurations do not support the use of JBOD arrays.



The topics covered in this appendix are:


B.1 Supported Configurations (JBOD Arrays)

A Sun StorEdge 3510 FC JBOD array can be attached directly to a single Sun host computer using either single-port or dual-port configurations. See Section B.7.1, Single-Port Connection to a Sun StorEdge 3510 FC JBOD Array and Section B.7.2, Dual-Port Connections to a Sun StorEdge 3510 FC JBOD Array for more information.


B.2 Supported Operating Systems (JBOD Arrays)

The Sun StorEdge 3510 FC JBOD array can be used with currently released versions of the Solaris 8 operating system, the Solaris 9 operating system, and the Solaris 10 operating system.


B.3 Supported Host Platforms and Connection Methods (JBOD Arrays)

TABLE B-1 lists the Sun systems that are supported by the Sun StorEdge 3510 FC JBOD array. The table also shows the connection methods supported for each of the supported Sun systems.

Supported HBAs include (X)6767A 2-Gbit PCI Single FC HBA and (X)6768A 2-Gbit PCI Dual FC HBA.

TABLE B-1 Supported Sun Servers and Connection Methods (JBOD Arrays)

Server

HBA

Sun Enterprisetrademark 220R server

Yes

Sun Enterprise 250 server

Yes

Sun Enterprise 420R server

Yes

Sun Enterprise 450 server

Yes

Sun Firetrademark V120 server

Yes

Sun Fire V280 server

Yes

Sun Fire V880 server

Yes



B.4 Known Limitations Affecting Sun StorEdge 3510 FC JBOD Arrays

Limitations affecting the Sun StorEdge 3510 FC JBOD array are listed below.


B.5 Using Sun StorEdge 3000 Family Software Monitoring and Management Tools with JBOD Arrays

The following software management tools are included on the Sun Download Center and on the Sun StorEdge 3000 Family Software and Documentation CD available for your array.

For details on how to install Sun StorEdge Configuration Service, Sun StorEdge Diagnostic Reporter, or Sun StorEdge CLI software, refer to the Sun StorEdge 3000 Family Software Installation Guide.

B.5.1 Sun StorEdge Configuration Service

Sun StorEdge Configuration Service supports the Sun StorEdge 3310 SCSI array, the Sun StorEdge 3510 FC array and the Sun StorEdge 3511 SATA array. It also supports, to a limited degree, standalone Sun StorEdge 3510 FC JBOD arrays. Since standalone JBOD arrays do not have a RAID controller to manage the disks, this software support for JBODs is limited to the following functions:

Refer to the "Monitoring JBODs" appendix in the Sun StorEdge 3000 Family Configuration Service User's Guide for information about using these functions with JBOD arrays.

B.5.1.1 Enabling JBOD Support

To monitor peripheral device conditions and events on a Sun StorEdge 3510 FC JBOD array from the Sun StorEdge Configuration Service Console, you first need to enable JBOD support. See Section B.8, Enabling Sun StorEdge 3510 FC JBOD Array Support for the procedure for enabling JBOD support.

B.5.2 Sun StorEdge Diagnostic Reporter

Sun StorEdge Diagnostic Reporter supports standalone JBOD arrays. However, triggered event notification is limited to environmental failures and hard drive failures.

B.5.3 Sun StorEdge CLI

The Sun StorEdge CLI supports JBOD arrays. However, because JBOD arrays do not have a RAID controller to manage the disks, this support is limited to the following commands:

Refer to the Sun StorEdge 3000 Family CLI User's Guide for information about using these commands.


B.6 Setting the Loop ID on a Sun StorEdge 3510 FC JBOD Array

When a Sun StorEdge 3510 FC JBOD array is directly attached to a host, unique, hard-assigned loop IDs are assigned to each drive in the JBOD array. A loop ID is the decimal version of an AL_PA. The lowest number loop ID is the lowest priority address on the loop.

An ID switch on the left front side of a Sun StorEdge 3510 FC JBOD array, underneath the left chassis ear, is used to set loop IDs for the disk drives to different ranges of values.

  FIGURE B-1 ID Switch

Figure shows ID Switch Located on the Left Front Side of the JBOD.

By default, the ID switch on all Sun StorEdge 3510 FC JBOD arrays is set to 1 so the range of IDs is automatically 16 to 31. You can leave the ID switch set to 1, or set it for whichever range of IDs you prefer.

The ID switch offers eight ID ranges. Each set contains 16 IDs. The last 4 IDs in each range are ignored. These ranges are shown in TABLE B-2.

TABLE B-2 ID Switch Settings for Sun StorEdge 3510 FC JBOD Arrays

ID Switch Setting

Range of IDs

0

0-15

1

16-31

2

32-47

3

48-63

4

64-79

5

80-95

6

96-111

7

112-125


B.6.1 Changing Your ID Switch Setting

Perform the following steps to change your ID switch setting:

1. Remove the bezel (the front faceplate).

See Section 7.5, Replacing the Front Bezel and Ear Caps for step-by-step instructions for removing and replacing the front bezel and ear caps.



caution icon

Caution - The plastic ear covers are snap-on parts that require care when you remove them. If you remove the right plastic ear cap, take care to avoid breaking the Reset push button directly below the ear cap.



2. Remove the left plastic ear cap from the front of the chassis.

3. Use the buttons to change the ID number.



caution icon

Caution - The loop ID should only be changed while the JBOD array is powered off or not in use. After changing the loop ID, a power cycle is required to make the ID switch change take effect. Failure to cycle the power following an ID switch change can lead to unexpected results.



4. Reattach the plastic ear cap and the bezel on the front of the chassis.


B.7 Connecting Sun StorEdge 3510 FC JBOD Arrays

You can connect a Sun StorEdge 3510 FC JBOD array directly to a host server. Use your standard host system disk management utilities for management of disks in a Sun StorEdge 3510 FC JBOD array, such as partitioning and formatting. Refer to your host system documentation for more information about disk management.

There are two ways to verify that you have a Sun StorEdge 3510 FC JBOD array (or expansion unit) rather than a Sun StorEdge 3510 FC RAID array:

B.7.1 Single-Port Connection to a Sun StorEdge 3510 FC JBOD Array

You can connect a Sun StorEdge 3510 FC JBOD array to an FC port, a port on a single-port HBA, or a single port on a dual-port HBA. FIGURE B-2 shows an example of a Sun StorEdge 3510 FC JBOD array with 12 drives, connected to a host computer over a single loop to a single FC port. In this example, the port is one of a pair of ports on a dual-port HBA.

  FIGURE B-2 Sun StorEdge 3510 FC JBOD Array Attached to a Single HBA Port

Figure shows one connection from a host bus adapter (HBA) to a Sun StorEdge 3510 FC JBOD.

In this example, if the loop ID switch is set to 0, the format command shows 12 drives on this loop, ranging from c1t0d0 to c1t11d0.

TABLE B-3 Example of 12 Drives Shown on a 12-Disk Sun StorEdge 3510 FC JBOD Array Connected to a Host Over a Single FC Loop

Drive Identifier

c1t0d0

c1t3d0

c1t6d0

c1t9d0

c1t1d0

c1t4d0

c1t7d0

c1t10d0

c1t2d0

c1t5d0

c1t8d0

c1t11d0


The drive identifiers are arranged in four columns of three drives each to reflect the physical location of these drives in the JBOD. They correspond to the locations of Disk 0 through Disk 11.

B.7.2 Dual-Port Connections to a Sun StorEdge 3510 FC JBOD Array

You can also connect a Sun StorEdge 3510 FC JBOD array to both ports on a dual-port HBA, ports on two single-port HBAs, or a port on a single-port HBA and a single port on a dual-port HBA.

Use host-based multipathing software such as VERITAS DMP 3.2 or 3.5 software to manage Sun StorEdge 3510 FC JBOD arrays connected to a host over more than one loop. Multipathing software provides full services on multiple paths between the server and the storage system.

FIGURE B-3 shows an example of a Sun StorEdge 3510 FC JBOD array with 12 drives, connected to a host computer over two loops to two FC ports. In this example, both ports are on dual-port HBAs.

  FIGURE B-3 Sun StorEdge 3510 FC JBOD Array Attached to Two HBA Ports

Figure shows two connections from separate host bus adapters (HBAs) to a Sun StorEdge 3510 FC JBOD.

When you connect your Sun StorEdge 3510 FC JBOD array to a host over two loops, the format command shows 24 drives, 12 on each loop, because the host sees a device entry for each path. If the loop switch ID is set to 0, these drives are identified as ranging from c1t0d0 to c1t11d0 and from c2t0d0 to c2t11d0, as shown in TABLE B-4. However there are, of course, still only 12 physical drives in the JBOD array. These drives are arranged in four columns of three drives each, as shown in TABLE B-3.

TABLE B-4 Example of 24 Drives Shown on a 12-Disk Sun StorEdge 3510 FC JBOD Array Connected to a Host Over Two FC Loops

Drive Identifier (First Loop)

Drive Identifier (Second Loop)

c1t0d0

c2t0d0

c1t1d0

c2t1d0

c1t2d0

c2t2d0

c1t3d0

c2t3d0

c1t4d0

c2t40d0

c1t5d0

c2t5d0

c1t6d0

c2t6d0

c1t7d0

c2t7d0

c1t8d0

c2t8d0

c1t9d0

c2t9d0

c1t10d0

c2t10d0

c1t11d0

c2t11d0




caution icon

Caution - Be careful not to mount the same drive twice if you are not using multipathing software.



B.7.3 Changing Your SFP Configuration on JBOD Arrays

Sun StorEdge 3510 FC JBOD arrays use SFP connectors to attach to Fibre Channel ports on your host computer. You might need to move or add one or more SFP connectors to your Sun StorEdge 3510 FC JBOD array to connect it to your host computer.

For more information about SFPs, refer to the Sun StorEdge 3000 Family Installation, Operation, and Service Manual for your array.

B.7.4 Connecting the Sun StorEdge 3510 FC JBOD Array to a Host Computer

Use fiber-optic cables to connect one or two HBA ports on the host computer to the Sun StorEdge 3510 FC JBOD array, as shown in FIGURE B-2 and FIGURE B-3.

1. Connect a fiber-optic cable to an HBA.

2. Set your loop IDs using the ID switch on the JBOD array.



caution icon

Caution - The loop ID should only be changed while the JBOD array is powered off or not in use. After changing the loop ID, a power cycle is required to make the ID switch change take effect. Failure to cycle the power following an ID switch change can lead to unexpected results.



3. Connect the SFP connector at the other end of each of these fiber-optic cables to host channel SFP connectors on the back of the JBOD array.

4. Power up the equipment in the following order, so that the host computer discovers all connected arrays:

a. Sun StorEdge 3510 FC JBOD array

b. Host computer

5. Use your host system disk management utilities to prepare the disks in the Sun StorEdge 3510 FC JBOD array for use.

Refer to your host system documentation for more information about disk management utilities available to you.


B.8 Enabling Sun StorEdge 3510 FC JBOD Array Support

For Sun StorEdge 3510 FC JBOD arrays, configure JBOD support only when you have a JBOD array connected directly to a host. This enables you to monitor peripheral device conditions and events. If you have an expansion unit connected to a RAID array, the RAID controllers monitor the expansion unit's conditions and events for you.



Note - Enabling JBOD support can impact I/O performance.



To monitor peripheral device conditions and events on a Sun StorEdge 3510 FC JBOD array from the Sun StorEdge Configuration Service console, you first must enable JBOD support.

1. Choose "View right arrow Agent Options Management."

The Agent Options Management window is displayed.

2. Select the Enable JBOD Support checkbox.

3. To immediately display the JBOD array in the main window, choose "View right arrow View Server" and click Probe to probe for new inventory.

4. Click OK.

The JBOD array is displayed in the main window.

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

 Screen capture showing a single-bus JBOD configuration.

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

 Screen capture showing a split-bus JBOD configuration.


B.9 Downloading Firmware to Disk Drives in a JBOD

For instructions on how to download firmware to disk drives in a JBOD directly attached to a host, refer to the README file in the patch that contains the firmware.


B.10 Resizing LUNs Greater Than 1 Tbyte

When a LUN is created larger than 1 Tbyte, the Solaris operating system identifies the LUN as an EFI drive. If the LUN is later rebuilt to less than 1 Tbyte, it retains the EFI label. If you want the LUN to revert back to SMI labeling, the format -e | label command is required.

To relabel a LUN to less than 1 Tbyte, perform these steps:



Note - In this example, the LUN being relabeled is c1t2d3.



1. Type the format command in a terminal window:.

# format -e devicename

2. At the format> prompt, type label.

# format -e c1t2d3
format> label

Two menu items are displayed and you are prompted to choose between them:

# format -e c1t2d3
   format> label
   [0] SMI Label
   [1] EFI Label
   Specify Label type[0]:

3. Select option 0 (SMI).

Specify Label type[0]: 0

4. Respond to the on-screen prompts to relabel the device.


B.11 Troubleshooting Sun StorEdge 3510 FC JBOD Arrays

This section describes troubleshooting procedures and error messages you can use to isolate configuration and hardware problems. For additional troubleshooting information refer to the "Troubleshooting Your Array" chapter in the Sun StorEdge 3000 Family Installation, Operation, and Service Manual.

B.11.1 Troubleshooting Configuration Issues

Follow this sequence of general steps to isolate software and configuration issues.

1. Look for storage-related messages in /var/adm/messages and identify any suspect Sun StorEdge 3510 FC JBOD arrays and fibre loops.

2. Check your Sun StorEdge Configuration Service console for alerts or messages.

3. Check revisions of software package, patches, and hardware.

4. Verify correct device file paths.

5. Check any related software, configuration, or startup files for recent changes.

Search SunSolve Online for any known related bugs and problems at: http://sunsolve.Sun.com

B.11.2 Troubleshooting Hardware Issues

When a problem is not otherwise reproducible, suspect hardware might need to be replaced. Always make only one change at a time and carefully monitor results. When possible, it is best to restore the original hardware before replacing another part to eliminate the introduction of additional unknown problem sources.

After hardware replacement, a problem can usually be considered solved if it does not resurface during a period equal to twice its original frequency of occurrence. For example, if a problem was occurring once a week on average before a potential fix was made, running two weeks without seeing the problem again suggests a successful fix took place.

Troubleshooting hardware problems is usually accomplished by an FRU isolation sequence that uses the process of elimination. Set up a minimal configuration that shows the problem and then replace elements in this order, testing after each replacement until the problem is solved:

1. Replace the cables.

2. Replace the SFPs.

3. Replace the drives.

4. Replace the HBAs.

Often you can also find out what does cause a hardware problem by determining the elements that do not cause it. Start out by testing the smallest configuration that does work, and then keep adding components until a failure is detected.

To view error messages reported by JBODs or expansion units, use any of the following:

For more information about replacing the chassis, I/O module, or controller, refer to the Sun StorEdge 3000 Family FRU Installation Guide.



caution icon

Caution - Whenever you are troubleshooting your array or replacing components, there is an increased possibility of data loss. To prevent any possible data loss, back up user data to another storage device prior to replacing a disk drive or any other component.





caution icon

Caution - When you replace drives, make sure that all I/O is stopped.



Before you begin troubleshooting a JBOD or expansion unit, check the cables that connect the host to the JBOD or expansion unit. Look for bent pins, loose wires, loose cable shields, loose cable casing, and any FC cables with 90 degree or more bends in them. If you find any of these conditions, replace the cable.

The FIGURE B-4 flowchart provides troubleshooting procedures specifically for JBODs and expansion units. For additional troubleshooting flowcharts, see and .

  FIGURE B-4 JBOD or Expansion Unit Troubleshooting Flowchart, 1 of 2

Flow chart diagram for diagnosing Fibre Channel JBOD or expansion unit problems.

  FIGURE B-5 JBOD or Expansion Unit Troubleshooting Flowchart, 2 of 2

Flow chart diagram for diagnosing Fibre Channel JBOD or expansion unit problems.


B.12 Converting a JBOD to a RAID array

You can convert an FC JBOD (or expansion unit) into a single-controller or dual-controller FC RAID array. For instructions on how to do this, refer to the Sun StorEdge 3000 Family FRU Installation Guide.