Instruction/ maintenance manual of the product SA33-3285-02 Compex Systems
Go to page of 531
A d v an ce d Se ria lRAI D A d ap te rs Us e r ’ s G u ide a nd M a in t e n an c e Inf o rm ati o n SA33-3285-02.
.
A d v an ce d Se ria lRAI D A d ap te rs Us e r ’ s G u ide a nd M a in t e n an c e Inf o rm ati o n SA33-3285-02.
Third Edition (September 2000) This softcopy of 14 January 2002 is a minor revision to SA33-3285-02. It contains new technical changes that are not shown in the printed book. Such changes are shown by a colon (:) to the left of each change. Changes that are also in the printed book are shown by a vertical line to the left of each change.
Contents Safety Notices ........................ x v Definitions of Safety Notices ................... x v Safety Notice for Installing, Relocating, or Servicing ............ x v About This Book ...................... xvii Who Should Use This Book ...
Reserving Disk Drives ..................... 2 7 Fast-Write Cache ....................... 2 7 Chapter 3. RAID Functions and Array States ............. 2 9 RAID Functions ....................... 2 9 Availability ........................ 2 9 Disk Drives That Are Not in Arrays .
Dealing with RAID Array Problems ................. 8 9 Getting Access to the SSA RAID Array SMIT Menu ........... 9 0 Identifying and Correcting or Removing Failed Disk Drives ........ 9 1 Installing a Replacement Disk Drive ................ 9 5 Using Other Configuration Functions .
Remove a Disk From an SSA RAID Array ............. 1 9 0 Swap Members of an SSA RAID Array .............. 1 9 1 Chapter 8. Split-Site Management ................ 1 9 3 Configuration of RAID-1 and RAID-10 Arrays ............. 1 9 3 Operation after a Loss of Member Disks .
Example 7: T o Change an Attribute of an Object ........... 2 4 2 Example 8: T o Exchange a Member Disk Drive of an Existing Array ..... 2 4 2 Example 9: T o Make a New System Disk .............. 2 4 3 Example 10: T o Delete an Array .................
Device Attributes ...................... 2 7 0 Device-Dependent Subroutines ................. 2 7 2 Error Conditions ...................... 2 7 4 Special Files ....................... 2 7 6 IOCINFO (Device Information) SSA Disk Device Driver ioctl Operation .
Related Information ..................... 3 0 4 IOCINFO (Device Information) tmssa Device Driver ioctl Operation ...... 3 0 5 Purpose ........................ 3 0 5 Description ........................ 3 0 5 TMIOST A T (Status) tmssa Device Driver ioctl Operation .
ssacand Command ...................... 3 4 4 Purpose ........................ 3 4 4 Syntax ......................... 3 4 4 Description ........................ 3 4 4 Flags ......................... 3 4 4 ssa_certify Command ..................... 3 4 5 Purpose .
ssa_fw_status Command .................... 3 6 0 Purpose ........................ 3 6 0 Syntax ......................... 3 6 0 Description ........................ 3 6 0 Flags ......................... 3 6 0 Output ......................... 3 6 0 Examples .
Flags ......................... 3 7 1 Output ......................... 3 7 1 ssaxlate Command ...................... 3 7 2 Purpose ........................ 3 7 2 Syntax ......................... 3 7 2 Description ........................ 3 7 2 Flags .
Federal Communications Commission (FCC) Statement .......... 4 8 5 Japanese V oluntary Control Council for Interference (VCCI) Statement ..... 4 8 5 Korean Government Ministry of Communication (MOC) Statement ...... 4 8 5 New Zealand Compliance Statement .
xiv User ’ s Guide and Maintenance Information.
Safety Notices For a translation of the danger and caution notices contained in this book, see the Safety Information manual, SA23-2652. Definitions of Safety Notices A danger notice indicates the presence of a hazard that has the potential of causing death or serious personal injury .
xvi User ’ s Guide and Maintenance Information.
About This Book Who Should Use This Book This book is for people who operate or service a RISC system that contains one or more Advanced SerialRAID Adapters. T o follow the instructions in this book, you should be familiar with the basic operational procedures for a RISC system.
Web Support Pages When you are installing an SSA device or subsystem, upgrading your SSA subsystem, or doing preventive maintenance on your SSA subsystem, refer to the web page shown here. This web page provides access to the latest SSA publications, micorocde, and support information for the using system, SSA adapters, and SSA subsystem.
Part 1. User Information 1.
2 User ’ s Guide and Maintenance Information.
Chapter 1. Introducing SSA and the Advanced SerialRAID Adapters This chapter describes: v Serial storage architecture (SSA). v The Advanced SerialRAID Adapter and the Advanced SerialRAID Plus Adapter . Physically , the two types of adapter are the same.
The Advanced SerialRAID Adapters (type 4 – P) The Advanced SerialRAID Adapters (see Figure 1) are 40-MB-per-second Serial Storage Architecture (SSA), Peripheral Component Interconnect (PCI) adapters that serve as the interface between systems that use PCI architecture and devices that use SSA.
Note: In the SSA service aids, this adapter is called “ IBM SSA 160 SerialRAID Adapter (14109100) ” . The adapter card has four SSA connectors that are arranged in two pairs. Connectors A1 and A2 are one pair; connectors B1 and B2 are the other pair .
Lights of the Advanced SerialRAID Adapters Each pair of connectors has a green light that indicates the operational status of its related loop: Status of Light Meaning Off Both SSA connectors are inactive.
Chapter 2. Introducing SSA Loops This chapter describes the principles of SSA loops, how SSA devices are known to the system programs, and the rules that you must observe when you configure your SSA loops.
Simple Loop Figure 2 shows a simple SSA loop. The devices that are attached to the SSA adapter card 1 are connected through SSA links 2 . These SSA links are configured as a loop. Data and commands to a particular device pass through all other devices on the link between the adapter and the target device.
Simple Loop — One Disk Drive Missing If a disk drive fails, or is switched off, the loop is broken, and one of the data paths to a particular disk drive is no longer available. The disk drives on the remainder of the loop continue to work, but an error is reported to the system.
Simple Loop — T wo Disk Drives Missing If two or more disk drives are switched off, fail, or are removed from the loop, some disk drives might become isolated from the SSA adapter . In Figure 4, disk drives 3 and 7 have been removed. Disk drives 1 and 2 can communicate with the using system only through connector A1 of the SSA adapter .
One Loop with T wo Adapters in One Using System In Figure 5, the loop contains two SSA adapters 1 and 2 that are both in the same using system. In this configuration, all the disk drives can still communicate with the using system if one SSA adapter fails.
One Loop with T wo Adapters in Each of T wo Using Systems If the loop contains four SSA adapters, with two adapters in each of two using systems, disk drives become isolated if they are connected between the two adapters of one using system, and both those adapters fail, or are held reset, but remain powered on.
If, however , disk drives are connected into the link between two SSA adapters that are in the same using system, those disk drives become isolated if both SSA adapters fail, or are held reset, but remain powered on (see also “ Bypass Note ” on page 12).
T wo Loops with One Adapter If only one SSA adapter is contained in the SSA loops, the adapter can provide support for up to 96 disk drives (a maximum of 48 per loop). Figure 8 shows an example configuration that has two loops and one adapter: Adapter SSA Disk Drives Figure 8.
T wo Loops with T wo Adapters The two adapters can provide support for up to 96 SSA disk drives (a maximum of 48 per loop). Figure 9 shows an example configuration that has two loops and two adapters: Adapter Adapter SSA Disk Drives Figure 9. T wo Loops with T wo Adapters Chapter 2.
Large Configurations Up to eight SSA adapters can be connected in a particular SSA loop, and up to 48 disk drives can be included in that loop. Figure 10 shows an example of a large configuration that has eight adapters in eight using systems. Figure 1 1 shows an example of a large configuration that has eight adapters in four using systems.
Switching Off Using Systems Be careful if you want to switch off one or more using systems in a large configuration. If any disk subsystem in the configuration does not use bypass cards, some using sy.
Configuring Devices on an SSA Loop If an SSA loop contains three or more SSA adapters that are installed in two or more using systems, you must ensure that all those using systems are switched on, and.
Identifying and Addressing SSA Devices This section describes how SSA adapters and devices are known to the using system programs. Location Code Format Location codes identify the locations of adapters and devices in the using system and its attached subsystems and devices.
The configuration software first recognizes the disk drive by its machine-readable serial number . The serial number of the disk drive is also displayed by the service aids. The service aids show the number as the last eight digits of the IEEE SSA Unique ID.
SSA Unique IDs Each SSA device has a specific identifier that is not used by any other SSA device in the whole world. This identifier is called the IEEE SSA Unique ID (UID) of the device. It is written into the device during manufacture. The full UID consists of 16 characters.
Rules for SSA Loops For SSA loops that include an Advanced SerialRAID Adapter (type 4 – P), the following rules apply: v Each SSA loop must be connected to a valid pair of connectors on the SSA adapter (that is, either connectors A1 and A2, or connectors B1 and B2).
Checking the Level of the Adapter Microcode If you need to check the level of the adapter microcode: 1. T ype, on the command line: lscfg -vl ssan where ssan is the name of the adapter whose microcode you are checking; for example, ssa0. A list of vital product data (VPD) is displayed.
Rules for the Physical Relationship between Disk Drives and Adapters The physical relationship between the disk drives and the adapters in an SSA loop can affect the performance of the subsystem. The following rules help you to get best performance from your subsystem.
Pairs of Adapter Connectors in the Loop – Some Shared Data The following sequence enables you to determine the best relationship between the disk drives and the adapter on an SSA loop that contains two or more pairs of adapter connectors. Some of the disk drives share data access with other disk drives.
Pairs Of Adapter Connectors in the Loop – Mainly Shared Data The following sequence enables you to determine the best relationship between the disk drives and the adapter , or adapters, on an SSA loop that contains two or more pairs of adapter connectors.
Reserving Disk Drives The Advanced SerialRAID Adapter , the Micro Channel SSA Multi-Initiator/RAID EL Adapter , and the PCI SSA Multi-Initiator/RAID EL Adapter implement reservation by using commands that are sent directly from adapter to adapter . They do not use the SCSI reservation command.
28 User ’ s Guide and Maintenance Information.
Chapter 3. RAID Functions and Array States This chapter describes the RAID functions and the states of RAID arrays. RAID Functions Redundant Array of Independent Disks (RAID) technology provides: v Larger disk size v Immediate availability and recovery of data v Redundancy of data at a level that you can choose.
transfer operations, performance is better than that provided by RAID-1 because data is striped across member disk drives. For short data transfer operations, performance is better because operations are distributed across the member disk drives, and the effect of skew is reduced.
RAID-0 Array States A RAID-0 array can be in either of two states. A knowledge of those states is useful when you are configuring your arrays. The states are described here. Good State A RAID-0 array is in the Good state when all the member disk drives of that array are present.
RAID-1 Array States RAID-1 array states are the same as RAID-10 array states. For details, see “ RAID-10 Array States ” on page 36. In RAID-1 arrays, the first member disk drive of the array is defined as the primary disk drive and the second member disk drive is defined as the secondary disk drive.
RAID-5 Array States A RAID-5 array can be in one of several states. A knowledge of those states is useful when you are configuring your arrays. The states are described here.
While in Degraded state, an array is not protected. If another disk drive in the array fails, or the power fails during a write operation, data might be lost. Y ou can return the disk drive to the array , or install another disk drive by using the procedure in step 37 on page 473 of MAP 2324: SSA RAID to logically add the device to the array .
RAID-5 Array State Flowchart Second disk fails or is removed Write operation Array Offline New disk Original disk replaced Y Y Array enabled for Hot Spare Hot Spare swapped in Hot Spare available Arra.
RAID-10 Array States Configuration information of the array is held in a reserved area sector on each of the first three member disk drives of the array . If fewer than two of these sectors can be read or written, the array normally goes into the Offline state.
operations put the array into the Degraded state. When the missing member disk drives are reintroduced, the array returns to the Good state. Degraded State A RAID-10 array is in the Degraded state when one or more member disk drives are missing or deconfigured, and a write operation has occurred.
v Both member disk drives of a mirrored pair are missing, deconfigured, or rebuilding. Unknown State A RAID-10 array is in the Unknown state when not enough array members are present for the array configuration to be determined; that is, fewer than two of the first three members are present.
Chapter 4. Using the SSA SMIT Menus This chapter describes how to use the system management interface tool (SMIT) to display and change characteristics of the SSA devices, and to access various service functions. Three SSA menus are available through the SMIT Devices menu.
Getting Access to the SSA Adapters SMIT Menu 1. For fast-path access to the SSA RAID Array SMIT menus, type smitty ssaa and press Enter . Otherwise: a. T ype smitty and press Enter . The System Management menu is displayed. b. Select Devices . The Devices menu is displayed.
Getting Access to the SSA Disks SMIT Menu 1. For fast-path access to the SSA RAID Array SMIT menus, type smitty ssad and press Enter . Otherwise: a. T ype smitty and press Enter . The System Management menu is displayed. b. Select Devices . The Devices menu is displayed.
4. The SSA Logical Disks menu is displayed: SSA Logical Disks Move cursor to desired item and press Enter. List All Defined SSA Logical Disks List All Supported SSA Logical Disks Add an SSA Logical Di.
Getting Access to the SSA RAID Arrays SMIT Menu 1. For fast-path access to the SSA RAID Array SMIT menus, type smitty ssaraid and press Enter . Otherwise: a. T ype smitty and press Enter . The System Management menu is displayed. b. Select Devices . The Devices menu is displayed.
44 User ’ s Guide and Maintenance Information.
Chapter 5. Hot Spare Management With all levels of adapter code, disk drives can be configured to be hot spare disk drives. These hot spare disk drives can be used in any array that is on the same SSA loop. If the adapter microcode level is at, or higher than, level 50, each hot spare disk drive can be configured to a particular hot spare pool.
Figure 16 shows an array that has its primary disk drives (pdisk2, pdisk3, pdisk10 and pdisk1 1) in building 1, and its secondary disk drives (pdisk5, pdisk6, pdisk7 and pdisk8) in building 2. Pdisk1 and pdisk4 have been assigned as hot spare disk drives, but no hot spare pool has been defined.
If pdisk2 fails, the hot spare disk drive pdisk4 might replace pdisk 2 as one of the primary disk drives in the array , as shown in Figure 17. Now , assume that for some reason, the disk drives in building 2 are no longer available. The example array is now in the Offline state because one of its four primary disk drives is in building 2.
This problem can be solved if, in each building, a hot spare pool is created for the disk drives. In Figure 18, all the disk drives in building 1 have been made members of pool A1, and all the disk drives in building 2 have been made members of Pool A2.
Figure 19 shows how RAID-5 arrays can be protected against the complete failure of an SSA enclosure. Each pdisk of each array (hdisk) is in a different SSA enclosure. The hot spare disk drives are also in a different enclosure. Pools A1 and A2 each contain an hdisk and a hot spare disk drive.
Figure 20 shows an alternative method of protecting RAID-5 arrays against the complete failure of an SSA Enclosure. This method uses a different hot spare disk drive to protect each member of the array . P ool A2 P ool A3 hdisk hdisk P ool A1 Enclosure-1 Enclosure-2 Enclosure-3 pdisk pdisk pdisk pdisk pdisk pdisk Spare Spare Spare Figure 20.
Figure 21 shows how a RAID-10 array can be protected against the complete failure of an SSA enclosure. The primary disk drives of the array are in enclosure 1; the secondary disk drives are in enclosure 2. The secondary disk drives contain the same data as do the primary disk drives.
that is needed to protect the array in the selected pool. No error log entry is made until the number of hot spare disk drives that remains in the pool is less than the Hot Spare Minimum parameter . Rules for Hot Spare Disk Drive Pools v By default, all hot spare disk drives are in pool zero.
Solving Hot Spare Pool Problems Hot spare pool problems are indicated by the state of the pool and by error codes in the system error log. When configuring or reconfiguring hot spare pools, it is recommended that you use the state of the hot spare pool to help guide your actions.
v Have a size equal to, or greater than, the largest disk drive that they will be protecting v Are in pool 0 on the SSA loop on which the hot spare pool exists 2.
Inconsistent The member disk drives in the pool do not agree about the size of the hot spare disk drives, or about the minimum number of hot spare disk drives that is required. This state is probably caused by changes to the SSA loop; for example, the addition of disk drives or changes to the SSA cabling.
56 User ’ s Guide and Maintenance Information.
Chapter 6. Using the RAID Array Configurator This chapter describes how to use the system management interface tool (SMIT) to manage your SSA RAID arrays. The SMIT provides a set of menus from which you can select the various functions of the ssaraid command.
Installing and Configuring SSA RAID Arrays Y ou can get to the required SMIT menu by using fast path commands, or by working through other menus. In this chapter , the fast path command for a particular option is given at the start of the description of that option.
Getting Access to the SSA RAID Arrays SMIT Menu 1. For fast-path access to the SSA RAID Array SMIT menus, type smitty ssaraid and press Enter . Otherwise: a. T ype smitty and press Enter . The System Management menu is displayed. b. Select Devices . The Devices menu is displayed.
Adding an SSA RAID Array This option lets you add an array to the configuration. 1. For fast path, type smitty mkssaraid and press Enter . Otherwise, select Add an SSA RAID Array from the SSA RAID Arrays menu. A list of adapters is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
2. Select the adapter to which you want to add the array . A list of array types is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
3. Select the type of array that you want to create. If you select RAID-0, the following menu is displayed: Add an SSA RAID Array Type or select values in entry fields.
If you select RAID-1, the following menu is displayed: Add an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
If you select RAID-5, the following menu is displayed: Add an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
If you select RAID-10, the following menu is displayed: Add an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
Meanings of the Fields SSA RAID Manager The name of an SSA RAID Manager . SSA RAID Managers are devices that control SSA RAID arrays. RAID Array T ype The type of the SSA RAID array . Member Disks For a RAID-0 or a RAID-5 array , member disks are the disk drives that are to be added to the SSA RAID array .
If you select Exact , the replacement disk drive is chosen only from hot spare disk drives whose size exactly matches the size of the failing disk drive. Choose Hot Spare only from Preferred Pool If you select yes for this option, a hot spare disk drive is selected only from the hot spare pool that contains the failed member disk drive.
If you select yes for this option, the array enters the Rebuilding state. The data that is on the primary disk drives is copied to the secondary disk drives. This operation might take several hours to complete, during which time, performance is affected.
6. Select the disk drives that you want in the array . You must select a minimum of: v T wo disk drives if you are creating a RAID-0 array v One primary and one secondary disk drive if you are creatin.
Deleting an SSA RAID Array This option allows you to delete arrays that you have created through the Add an SSA RAID Array option. The deleted array is broken into its member disk drives. Y ou cannot delete arrays that do not have a corresponding hdisk.
3. A prompt is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter. List All Defined SSA RAID Arrays List All Supported SSA RAID Arrays List All SSA RAID Arrays Connecte.
Creating a Hot Spare Disk Drive 1. For fast path, type smitty chgssadisk and press Enter . Otherwise, select Change/Show Use of an SSA Physical Disk from the SSA RAID Arrays menu. A list of disk drives and their usage is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
3. Select the disk drive that you want to designate as a hot spare. The following screen is displayed for the disk drive that you have chosen: Change/Show Attributes of an SSA Physical Disk Type or select values in entry fields. Press Enter AFTER making all desired changes.
Changing or Showing the Status of a Hot Spare Pool This option shows you the existing configuration of the arrays and the status of each hot spare pool. 1. For fast path, type smitty ls_hsm_status and press Enter . Otherwise, select List Status of Hot Spare Pools from the SSA RAID Arrays menu.
3. A list of hot spare pools and their status is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
empty The pool contains no hot spare disk drives, or the hot spare disk drives that are in the pool are not suitable as member disk drives of the pool. reduced The number of hot spare disk drives that are in the pool is less than the number of hot spare disk drives that were originally configured, but greater than the configured minimum number .
Showing the Disks That Are Protected by Hot Spares This option shows you which member disk drives of an array are protected by hot spare disk drives. 1. For fast path, type smitty ls_hsm_array_status and press Enter . Otherwise, select List Status of Hot Spare Protection for an SSA RAID Array from the SSA RAID Arrays menu.
3. A list of protected member disk drives is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. ssa1 Component Location Size Pool Protected Status hdisk4 raid_10 pdisk13 04-02-REGY-06-P 18.
Status The status of the array member disk drive. V alid values for status are: good The disk drive is working. not_present The disk drive cannot be detected. It has been removed or it has failed. too_large The member disk drive is too large to be protected by one of the hot spare disk drives that is in the pool.
Listing the Disks That Are in a Hot Spare Pool This option shows you all the disk drives that are in a hot spare pool and shows the status of each disk drive. 1. For fast path, type smitty ls_hsm_array_components and press Enter . Otherwise, select List Components in a Hot Spare Pool from the SSA RAID Arrays menu.
3. A list of hot spare pools is displayed: SSA RAID Arrays Move cursor to desired item and press Enter. List All Defined SSA RAID Arrays List All Supported SSA RAID Arrays List All SSA RAID Arrays Con.
Component The array member disk drive of the hdisk that is listed on the screen, or hot spare disk drives that are assigned to the pool. Location The physical location of the array member disk drive.
Adding a New Hot Spare Pool This option allows you to add a new hot spare pool. If you are not sure how to configure hot spare pools, read Chapter 5, “ Hot Spare Management ” on page 45 before you proceed. 1. For fast path, type smitty add_hsm_pool_adap and press Enter .
3. A list that shows Loop A or Loop B is displayed: SSA RAID Arrays Move cursor to desired item and press Enter. List All Defined SSA RAID Arrays List All Supported SSA RAID Arrays List All SSA RAID A.
The Hot Spares Minimum field contains a default value of 1. This value defines the minimum number of spares that can exist in the pool before an error condition is logged. Y ou should normally set this field to the number of hot spare disk drives that you intend to assign to this pool.
Adding Disks to, or Removing Disks from, a Hot Spare Pool This option allows you to exchange the disk drives that are in the hot spare pool, or to resynchronize the state of the pool. If you are not sure how to configure hot spare pools, read Chapter 5, “ Hot Spare Management ” on page 45 before you proceed.
3. A list of hot spare pools is displayed: SSA RAID Arrays Move cursor to desired item and press Enter. List All Defined SSA RAID Arrays List All Supported SSA RAID Arrays List All SSA RAID Arrays Con.
4. The hot spare pool is displayed: SSA Hot Spare Pools Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] SSA RAID Manager ssa1 Spares Pool pool_B2 St.
Dealing with RAID Array Problems This part of the chapter describes how to solve problems that might occur on your SSA RAID arrays. Y ou can get to the required SMIT menu by using fast path commands or by working through other menus.
Getting Access to the SSA RAID Array SMIT Menu 1. For fast-path access to the SSA RAID Array SMIT menus, type smitty ssaraid and press Enter . Otherwise: a. T ype smitty and press Enter . The System Management menu is displayed. b. Select Devices . The Devices menu is displayed.
Identifying and Correcting or Removing Failed Disk Drives When a disk drive fails, the array rejects it. If access to the array is still possible, the Current Use attribute of the disk drive is changed from Member of an SSA RAID Array to Rejected . The disk drive is listed in the SMIT menus as a rejected disk drive.
3. A list of rejected disk drives is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. pdisk4 08005AEA030D00D member rejected 2.3G Physical disk F1=Help F2=Refresh F3=Cancel F6=Command F8=Image F9=Shell F10=Exit /=Find n=Find Next 4.
8. Select the adapter that contains the rejected disk drive. The following menu is displayed: Identify Rejected Array Disks Type or select values in entry fields.
13. Physically remove the failing disk drive for a new one (see the Operator Guide or Service Guide for the unit). 14. If you are going to install a replacement disk drive, go to “ Installing a Replacement Disk Drive ” on page 95.
Installing a Replacement Disk Drive 1. Physically install the replacement disk drive (see the Operator Guide or Service Guide for the unit). 2. If the failed disk drive has been exchanged for a hot spare disk drive, change the use of the new disk drive to Hot Spare Disk (see “ Changing or Showing the Use of an SSA Disk Drive ” on page 144).
5. The following information is displayed: Swap Members of an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
Using Other Configuration Functions This part of the chapter describes the maintenance procedures that are available for your Advanced SerialRAID Adapter . Y ou can use these procedures at any time. Y ou can get to the required SMIT menu by using fast path commands or by working through other menus.
Getting Access to the SSA RAID Array SMIT Menu 1. For fast-path access to the SSA RAID Array SMIT menus, type smitty ssaraid and press Enter . Otherwise: a. T ype smitty and press Enter . The System Management menu is displayed. b. Select Devices . The Devices menu is displayed.
–“ Identifying the Disk Drives in an SSA RAID Array ” on page 1 19 –“ Identifying Hot Spare Disk Drives ” on page 121 –“ Identifying Rejected Array Disk Drives ” on page 123 –“ I.
Listing All Defined SSA RAID Arrays This option lists all the arrays that are connected to the SSA adapter . 1. For fast path, type smitty lsdssaraid and press Enter . Otherwise, select List All Defined SSA RAID Arrays from the SSA RAID Arrays menu. 2.
Listing All Supported SSA RAID Arrays This option lists all the types of array that are supported by the installed SSA RAID managers. 1. For fast path, type smitty lsssaraid and press Enter . Otherwise, select List All Supported SSA RAID Arrays from the SSA RAID Arrays menu.
Listing All SSA RAID Arrays That Are Connected to a RAID Manager This option lists all the SSA RAID disk drives that are connected to a particular RAID manager . 1. For fast path, type smitty lsmssaraid and press Enter . Otherwise, select List All SSA RAID Arrays Connected to a RAID Manager from the SSA RAID Arrays menu.
3. A list of arrays is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. hdisk4 09523173A02137K good 3.4G RAID-5 array hdisk3 095231779F0737K good 3.4G RAID-5 array F1=Help F2=Refresh F3=Cancel F6=Command F8=Image F9=Shell F10=Exit /=Find n=Find Next Chapter 6.
Listing the Status of All Defined SSA RAID Arrays This option lists the status of each defined array . 1. For fast path, type smitty lstssaraid and press Enter . Otherwise, select List Status of All Defined SSA RAID Arrays from the SSA RAID Arrays menu.
3. The following information is displayed for RAID-5 arrays: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. Unsynced Parity Strips Unbuilt Data Strips hdisk3 0 0 hdisk4 0 0 F1=Help F2=Refresh F3=Cancel F6=Command F8=Image F9=Shell F10=Exit /=Find n=Find Next Chapter 6.
The following information is displayed for RAID-1 and RAID-10 arrays: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
exposed One member disk drive of a mirrored pair is missing or has failed, but no write operation has been issued to the pair . degraded One member disk drive of a mirrored pair is missing or has failed, and a write operation has been issued to the working member disk drive.
Listing or Identifying SSA Physical Disk Drives This option allows you to list the disk drives that are being used by a particular array , and to identify particular disk drives. 1. For fast path, type smitty lsidssaraid and press Enter . Otherwise, select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
Listing the Disk Drives in an SSA RAID Array This option allows you to list the disk drives that are contained in a particular array . 1. For fast path, type smitty lssaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. A list of disk drives is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. pdisk1 0004AC5119E000D member present 1.1G Physical disk pdisk4 08005AEA030D00D member present 2.
Listing Hot Spare Disk Drives This option allows you to list the hot spare disk drives that are available to a particular array . 1. For fast path, type smitty lhssaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. A list of hot spare disk drives is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. pdisk3 0004AC5119E000D spare n/a 1.1G Physical disk pdisk5 08005AEA030D00D spare n/a 2.
Listing Rejected Array Disk Drives This option allows you to list disk drives that have been rejected (probably because of failure) from arrays. 1. For fast path, type smitty lfssaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. A list of rejected disk drives is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. pdisk3 0004AC5119E000D rejected n/a 1.1G Physical disk pdisk5 08005AEA030D00D rejected n/a 2.
Listing Array Candidate Disk Drives This option allows you to list disk drives that are available for adding to an array . 1. For fast path, type smitty lcssaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. A list of candidate disk drives is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
Listing System Disk Drives This option allows you to list disk drives that are used by the using system. These disk drives are not member disk drives of any array . 1. For fast path, type smitty lassaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. A list of system disk drives is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
Identifying the Disk Drives in an SSA RAID Array This option allows you to identify the disk drives that are contained in a particular array . 1. For fast path, type smitty issaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. The following information is displayed: Identify Disks in an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
Identifying Hot Spare Disk Drives This option allows you to identify the hot spare disk drives that are available to a particular SSA RAID manager . 1. For fast path, type smitty ihssaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. The following information is displayed: Identify Hot Spares Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] SSA RAID Manager ssa0 * Hot Spare Disks + Flash Disk Identification Lights yes + F1=Help F2=Refresh F3=Cancel F4=List F5=Reset F6=Command F7=Edit F8=Image F9=Shell F10=Exit Enter=Do 4.
Identifying Rejected Array Disk Drives This option allows you to identify disk drives that have been rejected (probably because of failure) from arrays. 1. For fast path, type smitty ifssaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. The following information is displayed: Identify Rejected Array Disks Type or select values in entry fields. Press Enter AFTER making all desired changes.
Identifying Array Candidate Disk Drives This option allows you to identify disk drives that are available for adding to an array . 1. For fast path, type smitty icssaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. The following information is displayed: Identify Array Candidate Disks Type or select values in entry fields. Press Enter AFTER making all desired changes.
Identifying System Disk Drives This option allows you to identify disk drives that are used by the using system. These disk drives are not member disk drives of any array . 1. For fast path, type smitty iassaraid and press Enter . Otherwise: a. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
3. The following information is displayed: Identify System Disks Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] SSA RAID Manager ssa0 * System Disks + Flash Disk Identification Lights yes + F1=Help F2=Refresh F3=Cancel F4=List F5=Reset F6=Command F7=Edit F8=Image F9=Shell F10=Exit Enter=Do 4.
Canceling all SSA Disk Drive Identifications This option allows you to cancel all disk drive identifications. For fast path, type smitty ssa_identify_cancel and press Enter . Otherwise: 1. Select List/Identify SSA Physical Disks from the SSA RAID Arrays menu.
Listing or Deleting Old RAID Arrays Recorded in an SSA RAID Manager If an array becomes disconnected from a RAID manager by some method other than the method described in “ Deleting an SSA RAID Array ” on page 70, a record of that array remains in the RAID manager .
Listing Old RAID Arrays Recorded in an SSA RAID Manager This option allows you to list the serial numbers of disconnected arrays whose records remain in the RAID manager . 1. Select List/Delete Old RAID Arrays in an SSA RAID Manager from the SSA RAID Arrays menu.
5. If any old arrays are in the RAID manager , a list of those arrays appears: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
Deleting an Old RAID Array Recorded in an SSA RAID Manager This option allows you to delete the records of RAID managers that have been disconnected, but whose records remain in the RAID manager . 1. Select List/Delete Old RAID Arrays in an SSA RAID Manager from the SSA RAID Arrays menu.
4. The following information is displayed: Delete an Old RAID Array Recorded in an SSA RAID Manager Type or select values in entry fields. Press Enter AFTER making all desired changes.
Changing or Showing the Attributes of an SSA RAID Array Each array type has several attributes associated with it. This option allows you to see, and possibly change, those attributes. 1. For fast path, type smitty chssaraid and press Enter . Otherwise, select Change/Show Attributes of an SSA RAID Array from the SSA RAID Arrays menu.
4. A list of attributes is displayed: Change/Show Attributes of an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
Changing Member Disks in an SSA RAID Array This option allows you to remove a disk drive from an array and install a replacement disk drive. All the data that is on the original disk drive is automatically written to the replacement disk drive. 1. For fast path, type smitty swpssaraid and press Enter .
Removing a Disk Drive from an SSA RAID Array This option allows you to remove a disk drive from an array so that you can install a replacement disk drive. Use this option when you do not have either an available online disk drive, or a spare slot for a replacement disk drive.
3. The following information is displayed: Remove a Disk from an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
Adding a Disk Drive to an SSA RAID Array This option allows you to install a replacement disk drive into a RAID-5 array that is running in the Exposed or Degraded state because a disk drive has been rejected or removed from the array . You cannot use this procedure to add a disk drive to a RAID-1 or RAID-10 array .
3. The following information is displayed: Add a Disk to an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
Swapping Members of an SSA RAID Array This option allows you to swap a disk drive for a replacement disk drive. 1. For fast path, type smitty exssaraid and press Enter . Otherwise: a. Select Change Member Disks in an SSA RAID Array from the SSA RAID Arrays menu.
3. The following information is displayed: Swap Members of an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
Changing or Showing the Use of an SSA Disk Drive This option allows you to change, or see, how particular disk drives are used. 1. For fast path, type smitty chgssadisk and press Enter . Otherwise, select Change/Show Use of an SSA Physical Disk from the SSA RAID Arrays menu.
3. A list of disk drives and their usage is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter. List All Defined SSA RAID Arrays -------------------------------------------------------------------------- | SSA Physical Disk | | | | Move cursor to desired item and press Enter.
4. Select the disk drive that you want to change or show . The following screen is displayed for the disk drive that you have chosen: Change/Show Use of an SSA Physical Disk Type or select values in entry fields. Press Enter AFTER making all desired changes.
Changing the Use of Multiple SSA Physical Disks 1. For fast path, type smitty chgssadisks and press Enter . Otherwise, select Change Use of Multiple SSA Physical Disks from the SSA RAID Arrays menu. 2. A list of adapters is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
4. Use the Select key to select the disk drives whose use you want to change. Select only those disk drives that are to have the same use. (For example, select only disk drives that are to become hot spare disk drives, or select only disk drives that are to become system disks.
Chapter 7. Copying Data from Arrays and from V olume Groups When disk drives are configured through the Logical V olume Manager for mirroring, you can use the Split Copy function to create a copy of a logical volume. Y ou can then save that copy on a tape or other medium for backup purposes.
synchronized to the array before you run the copy operation. The recommended procedure for copying logical volumes is to use the ssa_make_copy command, rather than SMIT or ssaraid commands. The ssa_delete_copy command is provided to enable you to delete the copy after it has been backed up.
Copying Data from an Array Three methods are available by which you can create a RAID-Copy array from a RAID-1 or RAID-10 array . Those methods are: v Using the ssaraid command from the command line v.
All the free disk drives that are listed are large enough and have the correct format to become part of the RAID-Copy array for hdisk5. 2. With a disk drive from the list (for example, 000629CD8A3900D), create your RAID-Copy array .
4. The time needed for the copy operation is related to the amount of data that you are copying. A large amount of data might take more that one hour to copy .
8. The newly created RAID-Copy array is created as a free disk drive. Y ou must now make it a system disk drive, and configured it on the using system: a. Using the RAID-Copy array serial number that was created in step 6 on page 153, type: ssaraid -H -l ssa2 -n 185439188B4F4CT -a use=system The RAID-Copy array is now a system disk drive.
Using SMIT to Create a RAID-Copy Array from a RAID-1 or RAID-10 Array This section describes how to use the SMIT menus to create RAID-copy arrays. This method and the ssaraid command method (see “ U.
3. Select the RAID-1 or RAID-10 array hdiskx that you want to copy , and press Enter . The Prepare a Copy menu is displayed: Prepare a Copy Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] Array to be copied hdisk3 Number of disk drives required 1 Minimum disk drive size required 9.
c. Press Enter . The new RAID-Copy array is created and coupled to the parent array . The copy operation starts. 5. The time needed for the copy operation is related to the amount of data that you are copying. A large amount of data can take more than one hour to copy .
6. T o uncouple the RAID-Copy Array: a. Select Array Copy Services from the SSA RAID Arrays menu. b. Select Uncouple a RAID Array Copy . A list is displayed of all the RAID-1 and RAID-10 arrays that have been copied. c. Select the array that you want to uncouple, for example, hdisk3, and press Enter .
Using the ssa_make_copy Command to Create a RAID Copy from a RAID-1 or RAID-10 Array Figure 22 shows a volume group that contains one physical volume: hdisk1. This hdisk is a RAID-1 array . The ssa_make_copy command checks whether the hdisk is either a RAID-1 or a RAID-10 array .
The recreatevg command is run on the RAID-Copy array . It creates the new volume group, renames the file systems, and mounts them to new mount points (see Figure 24).
ssa_make_copy Command Purpose T o create a RAID-Copy array from a RAID-1 or RAID-10 array . Syntax ssa_make_copy -v vgname -l lvname -f fsname [-V newvgname] [-L newlvprename] [-F newfsprempoint] [-s].
c. If the dump logical volume and the boot logical volume are copied, a warning is displayed. Y ou must delete the copies of these logical volumes after the copy volume group has been created. d. If the logical volume that you want to copy has a file system loglv that is located in a different volume group, you cannot copy the logical volume.
-F Determines the name of the copy file system. If this flag is not provided, the default naming convention applies. For example, the copy of the original file system /data is named /fs/data . -L Determines the name of the copy logical volume. If this flag is not provided, the default naming convention applies.
Example 1: Copying a Complete V olume Group In this example, you are copying a complete volume group from the parent array to the RAID-Copy array . T o copy a complete volume group, give the commands: ssa_make_copy -P -v vgname ssa_make_copy -v vgname Figure 25 shows, from left to right: v The parent array that contains the source volume group.
Example 2: Copying One Logical V olume In this example, you are copying only one logical volume (-lv B) from the parent array to the RAID-Copy array . T o copy one logical volume, give the commands: ssa_make_copy -P -l lv_B ssa_make_copy -l lv_B Figure 26 shows, from left to right: v The parent array that contains the source volume group.
Example 3: Copying One Logical V olume by Logical V olume Name or by FS Name In this example, you are copying one logical volume (lv_A) from the parent array to the RAID-Copy array . Y ou can use either the logical volume name (lv_A), or the FS name (data fs_1).
Figure 27 shows, from left to right: v The parent array that contains the source volume group. v The empty RAID-Copy array coupled to the parent array . v The uncoupled RAID-Copy array that now contains a copy of the logical volume. Note that in the copy , all names start with fs.
Example 4: Copying One Logical V olume by Logical V olume Name or by FS Name (2) In this example, you are copying one logical volume (lv_C) from the parent array to the RAID-Copy array . Y ou can use either the logical volume name (lv_C), or the FS name (data_fs2).
Example 4: Copying a Complete V olume Group and Recreating the Copy on Another Using System In this example, you are copying a complete volume group, then recreating the copy on another using system.
Example 5: Running an Automatic Copy of a V olume Group 1. Prepare a volume group for copying: a. Give the command: ssa_make_copy -P -v vgname b. W ait for the copy to complete. c. W ait for the external trigger to be created. 2. Uncouple the volume group: Give the command: ssa_make_copy -U -v vgname 3.
ssa_delete_copy Command Purpose T o delete a RAID-Copy array after it has been backed up. Syntax ssa_delete_copy -v vgname | -p pvname -A/-C [-f] Flags -A Deletes a copy and its RAID-Copy arrays. -C Deletes a copy and couples the RAID-Copy to its original parents.
SMIT Menus for 3-W ay Copy Operations This section describes the SMIT menus that are related to the 3-W ay Copy function. These SMIT menus help you to develop your own shell scripts to manage the copy operations. Getting Access to the Array Copy Services Menu 1.
Array Copy Services For fast path access to the Array Copy Services menu, type smitty ssa_copy and press Enter . Otherwise, select Array Copy Services from the SSA RAID Arrays menu.
Uncouple a RAID Array Copy Select this option if you want to uncouple a copy from an array . The copy must be in the Good state before it can be uncoupled. When the copy is uncoupled, a new hdisk is created. This hdisk contains the copied data. When this option is selected, a RAID array selection menu is displayed.
Prepare a Copy For fast path, type smitty copy_pre_array and press Enter . Otherwise, select Prepare a Copy from the Array Copy Services menu. The Prepare a Copy menu is displayed: Prepare a Copy Type or select values in entry fields. Press Enter AFTER making all desired changes.
Hot spare selection Default Assigns the coupled disk drives to the pool to which those disk drives were previously assigned: Primary Each coupled disk drive is assigned to the hot spare pool to which the Primary disk drive that it is copying is assigned.
Uncouple a V olume Group, Logical V olumes, or Filesystems Copy For fast path, type smitty copy_unvglvfs and press Enter . Otherwise, select Uncouple a V olume Group, Logical V olumes, or Filesystems Copy from the Array Copy Services menu.
If you select yes , the file systems are mounted when the copy is uncoupled. If you select read only , the file systems are mounted for “ read only ” when the copy is uncoupled. Synchronize the file systems Select this option to schedule a synchronization operation before the copy is uncoupled.
List All Copy Candidates For fast path, type smitty copy_lstcopycand and press Enter . Otherwise, select List All Copy Candidates from the Array Copy Services menu. The following information is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
Copying Data is being copied to the coupled disk drives, but these coupled disk drives do not yet contain an exact copy of the data that is on the array . Degraded A copy has been created, but one or more coupled disk drives are missing or have failed.
List All Uncoupled Copies For fast path, type smitty copy_lstcopies and press Enter . Otherwise, select List All Uncoupled Copies from the Array Copy Services menu. The following information is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
List All Uncoupled V olume Groups For fast path, type smitty copy_lstunvg and press Enter . Otherwise, select List All Uncoupled V olume Groups from the Array Copy Services menu. The following information is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
Delete a RAID Array Copy For fast path, type smitty copy_delcopy and press Enter . Otherwise, select Delete a RAID Array Copy from the Array Copy Services menu. The following information is displayed: Array Copy Services Move cursor to desired item and press Enter.
Delete a V olume Group, Logical V olumes, or Filesystems Copy For fast path, type smitty copy_delvglvfs and press Enter . Otherwise, select Delete a V olume Group, Logical V olumes, or Filesystems Copy from the Array Copy Services menu. The following information is displayed: Array Copy Services Move cursor to desired item and press Enter.
The meanings of the fields are: V olume Group The volume group that you selected previously . Action The possible actions are: Delete and Detach The volume group name is removed. Data on the volume group is no longer accessible. The RAID-Copy arrays change to free, and can be recoupled to parent arrays.
Effects of Array Copy on Other SMIT Menus This section shows SMIT menus that are described elsewhere in this book. When Array Copy is used, however , additional fields or display panels are present.
Percentage Copied The percentage of the array data that has been copied onto the coupled disk drives. When this reaches 100%, the coupled disk drives contain an exact copy of the data that is on the array , and can be uncoupled at any time from the array .
List Status Of All Defined SSA RAID Arrays For fast path, type smitty lstssaraid and press Enter . Otherwise, select List Status Of All Defined SSA RAID Arrays from the SSA RAID Arrays menu.
Identify Disks in an SSA RAID Array For fast path, type smitty issaraid and press Enter . Otherwise, select Identify Disks in an SSA RAID Array from the List/Identify SSA Physical Disks menu.
Remove a Disk From an SSA RAID Array For fast path, type smitty redssaraid and press Enter . Otherwise, select Remove a Disk From an SSA RAID Array from the Change Member Disks in an SSA RAID Array menu.
Swap Members of an SSA RAID Array For fast path, type smitty exssaraid and press Enter . Otherwise, select Swap Members of an SSA RAID Array from the Change Member Disks in an SSA RAID Array menu.
192 User ’ s Guide and Maintenance Information.
Chapter 8. Split-Site Management This chapter describes how to configure and manage a system in which the computing and disk drive resources are split between two or more sites, so that the system can continue to operate if one site is lost.
loss of any power domain in this configuration, a using system continues to detect either all the primary configuration disk drives, or one primary and one secondary configuration disk drive, and continues to access the array without the need to set the Split Array Resolution flag.
spare disk drives are not introduced if the Split Array Resolution flag is set to Secondary (secondary disk drives only are being used), the HotSpareSplits flag is set to off , and all the primary disk drives and the other adapter are not visible.
Single-Host System with Primary Disk Drive Missing Figure 29 shows a single-host system that has just been switched on. The system contains a RAID-1 array whose primary disk drive is missing.
Dual-Host System with Primary Disk Drive Missing Figure 30 shows a dual-host system that has just been switched on. The system contains a RAID-1 array whose primary disk drive is missing.
Dual-Host System with Only One System Switched On Figure 31 shows a dual-host system that has just been switched on. The system contains a RAID-1 array , but the primary disk drive is missing because system 1 in not switched on.
Split Systems The system can become split because communications have failed between the two systems. System 1 Split from System 2: Figure 32 shows system 1 split from system 2. On system 1, the array is in the Exposed or the Degraded state. On system 2, the array is in the Offline state, and SRN 48750 is generated.
Normal Reconnection: When the systems are reconnected, the secondary disk drives are resynchronized with the primary disk drives, as shown in Figure 33.
Failure of a Primary Disk Drive in a Dual-Host System: Figure 34 shows a dual-host system in which the primary disk drive of a RAID-1 array has failed. Because both adapters can still detect the secondary disk drive of the array , the Split Array Resolution flag is automatically set to Secondary , and I/O operations continue.
RAID-1 Failure of a Host System and a Primary Disk Drive: Figure 35 shows system 2 disconnected from system 1. The array is in the Of fline state. If you set Split Array Resolution to Secondary , the array goes into the Good state. RAID-10 Failure of a Host System and a Primary Disk Drive: Figure 36 shows system 2 disconnected from system 1.
Array is Offline because Adapter Is Not Known to the Remaining Half of the Array When this condition exists, the host system generates SRN 48755. T o maintain data consistency , SSA RAID-1 and RAID-10 arrays keep a record of the adapters to which they are connected.
Moving an Array between Systems In Figure 38, exactly half of a RAID-10 array is being moved from its original connections (adapter A and adapter B) to a new configuration where it is connected to adapter C and adapter D. Under these conditions: v The half of the array that is still connected to adapter A and adapter B is in the Exposed state.
v Change the state of the Split Array Resolution flag on the new adapters. Attention: This method helps you to recover the system from severe errors. Use this method only if the other half of the array has failed completely , and will never be used again.
RAID-10 Array Split Figure 39 shows a RAID-10 array that has been split into halves. The Split Array Resolution flag has been set to Secondary to permit I/O operations to be performed on the secondary half of the array . Only user actions can set this condition.
RAID-10 Array with Unsynchronized Data Figure 40 shows a RAID – 10 array whose halves have been reconnected. Each half of the array contains different data, but no indication is given to which data is valid. Under these conditions, the array is in the Offline state, and both systems generate SRN 48760.
208 User ’ s Guide and Maintenance Information.
Chapter 9. Using the SSA Spare T ool The SSA Spare T ool helps you to manage your SSA networks when Logical V olume Manager (L VM) mirrored volume groups are used. It works with the L VM to identify stale partitions or missing physical volumes in L VM mirrored volume groups.
210 User ’ s Guide and Maintenance Information.
Chapter 10. Using the Fast-Write Cache Feature This chapter describes how to configure the Fast-Write Cache feature, and how to deal with any fast-write problems that might occur during fast-write operations. Fast-Write Cache Card Battery The Fast-Write Cache Option Card receives its power from a rechargeable battery .
those shown in this book. If you are not familiar with the selection of items from the graphics versions of the menus, use the smitty command. The menus will then appear as shown in this book. 2. If you use fast-path commands, you might need to go through intermediate steps that are not shown in this book.
Getting Access to the Fast-Write Menus 1. For fast-path access to the Fast-Write SMIT menus, type smitty ssadlog and press Enter . Otherwise: a. T ype smitty and press Enter . The System Management menu is displayed. b. Select Devices . The Devices menu is displayed.
Enabling or Disabling Fast-Write for One Disk Drive This option lets you enable or disable the fast-write function for one disk drive. 1. For fast-path access to the Change/Show Characteristics of an SSA Logical Disk menu: a. T ype smitty chgssardsk and press Enter .
device is present in the fast-write cache, and you want to disable the fast-write function, go to “ Enabling or Disabling Fast-Write for Multiple Devices ” . Enabling or Disabling Fast-Write for Multiple Devices This option allows you to enable or disable the fast-write function on multiple devices.
Notes: a. If you are running a two-way fast-write operation, and you enable or disable the fast-write function, the hdisk on the second using system becomes unavailable. From the second using system, delete that hdisk, and reconfigure as follows: 1) T ype: rmdev -l hdiskname -d 2) Run cfgmgr to reconfigure the new hdisk.
Bypassing the Cache in a One-W ay Fast-Write Network If you are using the two-way fast-write function (that is, two adapters have access to a fast-write disk drive), you can choose whether you want fast-write operations to continue if the partner adapter fails or becomes not accessible.
Dealing with Fast-Write Problems This section describes how to recover from problems that might occur during fast-write operations. The type of problems are those in which data loss might have occurred or customer data recovery procedures need to be performed.
v T o disable the fast-write cache, type: ssaraid -l ssaX -H -n Y -a fastwrite=off -a force=yes -u where X is the number of the adapter that has reported the failure, and Y is the name of the device. (The name of the device can be either the logical disk name, or the SSA serial number .
SRN 42524 If a Fast-Write Cache Option Card fails, or is removed from the adapter , the affected devices are all those that contain unsynchronized data when the cache card fails, or is removed. T o list these devices, type: ssaraid -l ssaX -Iz -a state=no_cache where X is the adapter number .
Chapter 1 1. SSA Error Logs This chapter describes: v Error logging v Error logging management v Error log analysis v Good housekeeping Each topic is discussed as a summary , then as a detailed description . The summaries provide all the information that you need for routine service operations on SSA subsystems.
Detailed Description SSA error logs are grouped into types of errors. Each type of error is assigned to an Error Label and an Error ID. The Error Label specifies the text that appears when the error log is displayed. It also specifies the priority that is applied to each error type when the cause of a problem is determined.
T able 2. Error Labels (continued) Error Label Error ID Error Description SSA_DEVICE_ERROR FE9E9357 This error can be logged against the adapter or disk drive resource. When the error is logged against a disk drive, it indicates that the adapter has detected a failure on the disk drive.
T able 2. Error Labels (continued) Error Label Error ID Error Description SSA_LINK_ERROR ABECECFD Link errors might be detected by any node in the SSA loop. The adapter is notified of these errors. It performs any necessary error recovery , and logs the error.
Disk drive errors on SSA subsystems are logged against the physical disk drive (pdisk) rather than the logical disk drive (hdisk). If you are looking for the cause of a problem where the failing hdisk.
SCSI Sense Data Format: Errors that are logged with the following labels have SCSI sense data in the detail data field in the error log: DISK_ERR1 SSA_DISK_ERR2 DISK_ERR4 SSA_DISK_ERR3 SSA_DISK_ERR1 SSA_DISK_ERR4 SCSI sense data consists of 32 bytes of data.
v Redundant power failures in SSA enclosures The test runs hourly at a specific time in the hour . run_ssa_link_speed cron SSA links can run at 20 MB per second or at 40 MB per second. Normally , two SSA nodes that can communicate at 40 MB per second operate the link between them at 40 MB per second.
Error Logging Management Summary If an error is permanent, it is reported each time that the health check is run. If an error is intermittent, it is logged each time that it occurs.
The example also shows that, during any six hour period, no more than three errors of this type are sent to the error log. If other types of error occur for this device, or errors occur for another device, they are sent immediately to the error log.
If SD/6000 is installed on the system, it runs error log analysis whenever a hardware error is logged, and raises an incident if problems are found that need service activity . Detailed Description Error log analysis determines whether the data that is in the error log indicates that service activity is needed on the subsystem.
error log analysis that is related to a period longer than 24 hours, use the ssa_ela command (see “ Command Line Error Log Analysis ” on page 232). If the detail data field for the error record contains SCSI sense data: v SSA_DISK_ERR2 or SSA_DISK_ERR3 type errors do not generate an SRN.
Command Line Error Log Analysis A command line utility has been provided that allows you to run SSA error log analysis from a manually-entered command or from shell scripts.
Good Housekeeping The items described here can help you ensure that your SSA subsystem works correctly . v When you are installing your SSA subsystem, ensure that ssa_adm is set to an address that is suitable for your installation.
234 User ’ s Guide and Maintenance Information.
Chapter 12. Using the SSA Command Line Interface for RAID Configurations Y ou can use the ssaraid command from the command line instead of the from the SMIT panels (see Chapter 6, “ Using the RAID Array Configurator ” on page 57) to configure and manage your arrays.
v List the objects that have support from a particular RAID manager: – List all the types of array objects. – List all the types of objects that can be created.
Command Syntax ssaraid -? ssaraid -M [-o] [-l RaidManager] ssaraid -l RaidManager [-n Name [-m|-p|-x|-e] | -t ObjectType [-r Name] [-c]] ssaraid -I -l RaidManager [-n Name [-m|-p|-x|-e] | -t ObjectType [-r Name] [-c]] [-a Attribute=Value]...[-o|-z[-h] | -S[-o]] ssaraid -C -l RaidManager -t CreateType -s Member [Member].
Options Y ou can use the following options with the ssaraid command: Option Description -? Print a short usage message. -A Perform an action on an object. -C Create an object. -D Delete an object. -H Change an object. -I Report information on an object.
Examples For the examples given here, assume that the following items of hardware are available in the system: v A RAID Manager named ssa0 v Four SSA physical disks named pdisk0, pdisk1, pdisk2, and pdisk3 Example 1: T o Create a RAID-0 Array This example shows how to use three SSA physical disks to create a RAID-0 array .
Example 3: T o Create a RAID-5 Array This example shows how to use three SSA physical disks to create a RAID-5 array . The attributes of the disks are all set to their default values. T ype the command: > ssaraid -C -l ssa0 -t raid_5 -s pdisk0 pdisk1 pdisk2 -d where: -C specifies that this operation is a create operation.
Example 5: T o Create a Hot Spare Pool This example shows how to create a hot spare pool that contains an array member disk drive and a hot spare disk drive.
Example 7: T o Change an Attribute of an Object This example shows how to change an attribute of an object; for example, to change the new array so that it does not automatically call a hot spare disk drive if one of its member disk drives goes into the Offline state.
Example 9: T o Make a New System Disk This example shows how use a single SSA disk to make a new system disk. T ype the command: > ssaraid -H -l ssa0 -n pdisk0 -a use=system -d where: -H specifies that this operation is a change operation. -l ssa0 specifies the RAID manager that is to be used.
SSARAID Command Attributes When using the ssaraid command, you can specify the following types of attribute: v RAID array Creation and Change attributes v RAID array Change attributes v Physical Disk .
bypass_cache_if_oneway=true/false (default=false) With the attribute set to true : If the partner fast-write cache becomes not available, the fast-write cache operations to this disk drive are disabled, and an entry is made in the error log.
read_only_when_exposed=true/false (default=false) With the attribute set to false : If the array enters the Exposed state, and write operations are made to the array: v The first write operation causes the array to enter the Degraded state. The written data is not protected.
Creation and Change Attributes for RAID-1 and RAID-10 Arrays Only Y ou can specify the following attributes with the -a option when you are using the ssaraid command with the -C or -H option to create.
Creation and Change Attribute for RAID-5 Arrays Only Y ou can specify the following attribute with the -a option when you are using the ssaraid command with the -C option to create a RAID-5 array: fw_.
force=yes/no If an array is using a fast-write cache that is failing, you must specify this attribute as yes to allow the fast-write cache to be disabled.
Other Change Attributes for Physical Disk Drives Y ou can specify the following attributes with the -a option when you are using the ssaraid command with the -H option to change a physical disk drive. use=system/spare/free With the attribute set to system : The physical disk drive can be used directly by the operating system.
fw_max_length (default=128) This attribute sets the maximum size, in blocks, of write operations to the fast-write cache. Write operations that are larger than the specified value write data directly to the disk, and do not use the fast-write cache.
Couple Action Attributes (RAID-1 and RAID-10 Only) Y ou can specify the following attributes with the -a option when you are using the ssaraid command with the -A and -i couple options to do actions on a RAID-1 or RAID-10 array .
Return Codes Code Description 0 Successful. 1 Some changes made, but finally not successful. 2 General problem accessing the object data manager (ODM). 3 Specified object (file, record, ODM object) not found. 4 Heap allocation failed. 5 Open/ioctl failure for RAID manager .
254 User ’ s Guide and Maintenance Information.
Chapter 13. Using the Programming Interface SSA Subsystem Overview Device Drivers T wo types of device driver provide support for all SSA subsystems: v The SSA adapter device driver , which deals with the SSA adapter . v The SSA head device drivers, which deal with devices that are attached to the SSA adapter .
Interface between the SSA Adapter Device Driver and Head Device Driver T o communicate with the SSA adapter device driver , the SSA head device driver: 1. Uses the fp_open kernel service to open the required instance of the SSA adapter device driver .
SSA Adapter Device Driver Purpose T o provide support for the SSA adapter . Syntax #include /usr/include/sys/ssa.h #include /usr/include/sys/devinfo.h Description The /dev/ssa n special files provide an interface that allows client application programs to access SSA adapters and the SSA devices that are connected to those adapters.
intr_priority Holds the value of the interrupt priority that the SSA adapter device driver for this adapter will use. daemon Specifies whether to start the SSA adapter daemon. If the attribute is set to TRUE, the daemon is started when the adapter is configured.
Y ou can use the open or the openx subroutine call to open the SSA adapter device driver . If you use the openx subroutine call, set the ext parameter to 0, because the call does not use it.
Files /dev/ssa0, /dev/ssa1,..., /dev/ssa n Provide an interface to allow SSA head device drivers to access SSA devices or adapters. 260 User ’ s Guide and Maintenance Information.
IOCINFO (Device Information) SSA Adapter Device Driver ioctl Operation Purpose T o return a structure that is defined in the /usr/include/sys/devinfo.h file. Description The IOCINFO ioctl operation returns a structure that is defined in the /usr/include/sys/devinfo.
SSA_TRANSACTION SSA Adapter Device Driver ioctl Operation Purpose T o send an SSA transaction to an SSA adapter . Description The SSA_TRANSACTION operation allows the caller to issue an IPN (Independent Packet Network) transaction to a selected SSA adapter .
TimeOutPeriod Number of seconds after which the transaction is considered to have failed. A value of 0 indicates no time limit. Note: If an operation takes longer to complete than the specified time-out, the adapter is reset to purge the command. Attention: This is a very low-level interface.
SSA_GET_ENTR Y_POINT SSA Adapter Device Driver ioctl Operation Purpose T o allow another kernel extension, typically a SSA head device driver , to determine the direct call entry point for the SSA adapter device driver . This operation is the entry point through which the head device driver communicates with the adapter device driver .
SSA Adapter Device Driver Direct Call Entry Point Purpose T o allow another kernel extension to send transactions to the SSA adapter device driver . This function is not valid for a user process. When the function completes its run, an off-level interrupt notifies the caller .
ssadisk SSA Disk Device Driver Purpose T o provide support for Serial Storage Architecture (SSA) disk drives. Syntax #include <sys/devinfo.h> #include <sys/ssa.
Multiple Adapters Some SSA subsystems (see “ Rules for SSA Loops ” on page 22) allow a disk drive to be controlled by up to two adapters in a particular using system. The disk drive has, therefore, two paths to each using system, and the SSA subsystem can continue to function if an adapter fails.
Fencing is provided as an alternative method for controlling access to disks that are connected to multiple using systems. The PCI SSA Multi-Initiator/RAID EL Adapter , the Micro Channel SSA Multi-Ini.
Using mkdev to Configure a Physical Disk T o use mkdev to configure an SSA physical disk, specify the following information: Parent ssar Class pdisk Subclass ssar T ype Y ou can list the types by typing: lsdev -P -c pdisk -s ssar ConnectionLocation 15-character unique identifier of the disk drive.
v Construct the 15-character unique identifier from the 12-character SSA UID that is shown on the label that is on the side of the disk drive. Y ou can recognize the UID by its three-character suffix “ 00D ” . v Run the ssacand command, and specify the adapter to which the logical disk is connected.
Attributes Common to SSA Logical and SSA Physical Disks adapter_a Specifies either the name of one adapter that is connected to the device, or none if no adapter is connected as adapter_a now . adapter_b Specifies either the name of one adapter that is connected to the device, or none if no adapter is connected as adapter_b now .
max_coalesce The maximum number of bytes that the SSA disk device driver attempts to transfer to or from an SSA logical disk in one operation. The default value is appropriate for most environments.
secondary path, if one exists. Y ou can prevent this switch by additionally specifying the SSADISK_NOSWITCH flag. This flag has support both for SSA logical disk drives and for SSA physical disk drives. Y ou cannot specify this flag and the SSADISK_SECONDARY flag together .
each side of the indicated physical so that the disk can be removed from the loop for service, and no errors are caused on the loops. This flag has support only for SSA physical disk drives. Y ou cannot specify this flag and the SSADISK_SCSIMODE flag together .
v An attempt was made to open an SSA physical device that has already been opened by another process. v The target device is reserved by another initiator .
ENOMEM The system does not have enough real memory or enough paging space to complete the operation. ENOLCK An attempt was made to open a device in Service mode, and the device is in an SSA network that is not a loop. Special Files The ssadisk device driver uses raw and block special files to perform its functions.
IOCINFO (Device Information) SSA Disk Device Driver ioctl Operation Purpose T o return a structure that is defined in the /usr/include/sys/devinfo.h file. Description The IOCINFO operation returns a structure that is defined in the /usr/include/sys/devinfo.
SSADISK_ISAL_CMD (ISAL Command) SSA Disk Device Driver ioctl Operation Purpose T o provide a method of sending Independent Network Storage Access Language (ISAL) commands to an SSA physical or logical disk drive. ISAL consists of a set of commands that allow a program to control and access a storage device.
The SSADISK_ISAL_CMD ioctl uses the following fields of the ssadisk_ioctl_parms structure: dsb Contains the directive status byte that is returned for the command. The byte contains a value from the /usr/include/ipn/ipndef.h file. A non-zero value indicates an error .
Files /dev/pdisk0, /dev/pdisk1, ..., /dev/pdisk n Provide an interface to allow SSA device drivers to access SSA physical disk drives. /dev/hdisk0, /dev/hdisk1,..., /dev/hdisk n Provide an interface to allow SSA device drivers to access SSA logical disk drives.
SSADISK_ISALMgr_CMD (ISAL Manager Command) SSA Disk Device Driver ioctl Operation Purpose T o provide a method of sending Independent Network Storage Access Language (ISAL) Manager commands to an SSA physical or logical disk drive. ISAL consists of a set of commands that allow a program to control and access a storage device.
u0.isal.status_descriptor Set by the caller to indicate the buffer for status data. u0.isal.minor_function Set by the caller to one of the ISAL Manager Commands that is defined in the /usr/include/ipn/ipnsal.h file and listed at the start of the description of this operation.
SSADISK_SCSI_CMD (SCSI Command) SSA Disk Device Driver ioctl Operation Purpose T o provide a method of sending Serial Storage Architecture - Small Computer Systems Interface (SSA-SCSI) commands to an SSA physical disk drive that has been opened with the SSADISK_SCSIMODE extension flag.
u0.scsi.cdb_length Set by the caller to indicate the length of the CDB. u0.scsi.scsi_status Contains the SCSI status that is returned for the command. The device driver does not know the contents of the CDB. The driver only passes on the CDB to the hardware.
SSADISK_LIST_PDISKS SSA Disk Device Driver ioctl Operation Purpose T o provide a method of determining which SSA physical disk drives make up a SSA logical disk drive. Description The SSADISK_LIST_PDISKS operation can be issued by any user to an SSA logical disk (hdisk).
Return V alues If the command was successfully sent to the adapter card, this operation returns a value of 0. Otherwise, a value of -1 is returned, and the errno global variable is set to one of the following values: EIO An unrecoverable I/O error has occurred.
SSA Disk Concurrent Mode of Operation Interface The SSA subsystem provides support for the broadcast of one-byte message codes from one using system to all other using systems that are connected to the same disk drive. This ability to pass messages can be used to synchronize access to the disk drive.
DD_CONC_TEST Issues a test disk command to verify that the SSA disk drive is still accessible to this using system. The concurrent mode entry point returns a value of EINV AL if any of the following is true: v The top kernel extension did not perform a DD_CONC_REGISTER operation.
error field of the conc_cmd structure contains the return code that is necessary for the completion of this command. The possible values are defined in the /usr/include/sys/errno.h file. The conc_cmd pointer argument to the special interrupt handler entry point of the top kernel extension is non-null.
SSA Disk Fencing SSA disk fencing is a facility that is provided in the SSA subsystem. It allows multiple using systems to control access to a common set of disks. Using the fencing commands that are provided by the hardware, you can prevent particular using systems from accessing a particular disk drive.
SSADISK_FORCED_OPEN to the openx subroutine, the reservation is broken, but the open fails with errno set to ENOCONNECT . T o break through the fence, the SSA logical disk must be opened in SSADISK_FENCEMODE and the SSADISK_ISALCMD ioctl operation used to issue the appropriate hardware command to break the fence condition.
between the adapters fails. The tmssa device driver automatically switches to adapters ssa1 and ssa3 or adapters ssa1 and ssa4. The connections between nodes can be modified while they are in use, and the target-mode interface tries to recover .
When configuration is complete, special files exist in the /dev directory . These files allow you to use the target mode interface with each node that is defined in the configuration database. Configuration does not need communication to be actually possible between the relevant using systems.
amount of data that is being sent. For example, to write 64 KB of data with no retry operations, you need 64 KB read and write buffers. If you allow one retry operation, you need only 32 KB buffers. Using SSA T arget Mode SSA T arget Mode does not attempt to manage the data transfer between devices.
SSA tmssa Device Driver Purpose T o provide support for using-system to using-system communications through the SSA target-mode device driver . Syntax #include /usr/include/sys/devinfo.h #include /usr/include/sys/tmscsi.h #include /usr/include/sys/scsi.
The calling program must observe any other rules that are needed to maintain, or otherwise manage, the communication of data. Delays that occur when data is received or sent through the target mode device driver are that are characteristics of the hardware and software driver environment.
EINV AL Attempted to run an open subroutine for a device instance, but either a wrong open flag was used, or the device is not yet configured. EIO An I/O error occurred.
any time, the device driver does not maintain an internal timer to interrupt the read. Therefore, if a time-out function is required, it must be started by the calling program. If the calling program wants to break a blocked read subroutine, the program can generate a signal.
write subroutine Support for the write entry point is provided only for the initiator-mode device driver . The write entry point generates one write operation in response to a calling program write request.
timeout_value = ((transfer_length / 65536) + 1) * 20 In the calculation, 20 is the default scaling factor that generates the time-out value. The caller can customize the time-out value through the TMCHGIMP ARM operation.
ioctl Subroutine The following ioctl operations are provided by the target-mode device driver . Some are specific to either the target-mode device or the initiator-mode device. All require the respective device instance be open for the operation run. IOCINFO Returns a structure defined in the /usr/include/sys/devinfo.
The POLLIN event is indicated by the device driver when any data is received for this target instance. A nonblocking read subroutine, if subsequently issued by the caller , returns data. For a blocking read subroutine, the read does not return until either the requested length is received, or the write operation ends, whichever comes first.
v A hardware error that has not been recovered v A software error that has been detected by the device driver The target-mode device driver passes error-recovery responsibility for all detected errors to the caller . For these errors, the target-mode device driver does not know if this type of error is permanent or temporary .
tmssa Special File Purpose T o provide access to the SSA tmssa device driver . Description The Serial Storage Architecture (SSA) target-mode device driver provides an interface that allows the SSA interface to be used for data transfer from using system to using system.
IOCINFO (Device Information) tmssa Device Driver ioctl Operation Purpose T o return information about the device in a structure that is defined in the /usr/include/sys/devinfo.h file. Description This operation allows you to supply a pointer to the address of an area of type struct devinfo in the arg parameter to the IOCINFO operation.
Use TM_GetDevinfoNodeNum( ) to read the node number from which the data is received. The remainder of the structure is filled as follows: devtype DD_TMSCSI.
TMIOST A T (Status) tmssa Device Driver ioctl Operation Purpose T o allow the caller to put the status information for the current or previous write operation into a structure that is defined in the /usr/include/sys/tmscsi.h file. Description This operation returns information about the last write operation.
TMCHGIMP ARM (Change Parameters) tmssa Device Driver ioctl Operation Purpose T o allow the caller to change the retry parameter and the time out parameter that are used by the target-mode device driver . Description This operation allows the caller to change the default set up of the device.
Regardless of the value of the timeout_type field, if the new_timeout field is set to a value of 0, the caller specifies “ no time out ” for the send command, allowing the command to take an indefinite amount of time. If the calling program wants to end a write operation, it generates a signal.
310 User ’ s Guide and Maintenance Information.
Part 2. Maintenance Information 31 1.
312 User ’ s Guide and Maintenance Information.
Chapter 14. SSA Adapter Information For a description of the SSA adapter , port addresses, and the rules for SSA loops, see Chapter 1, “ Introducing SSA and the Advanced SerialRAID Adapters ” . Installing the SSA Adapter 1. Install the adapter and disk drive microcode from the media that are supplied with the adapter .
The second entry instructs the run_ssa_healthcheck shell script to run once each hour . This shell script causes the SSA adapter to log any errors that might exist in the SSA subsystem, but that are not causing application programs to fail. The third entry instructs the run_ssa_encl_healthcheck shell script to run at 30 minutes past each hour .
Diagnostic Information for Multiple Bus Systems manual). The microcode level is shown in the ROS level field. Alternatively , give the following command: lscfg -v1 adapter where adapter is the ID of the adapter that you want to check.
Vital Product Data (VPD) for the SSA Adapter The vital product data (VPD) for the SSA adapter can be displayed by using the using-system service aids. This section shows the types of information that are contained in the VPD. Part number The part number of the adapter card.
Adapter Power-On Self-T ests (POST s) Power-on self-tests (POST s) are resident in the SSA adapter . These tests ensure that the adapter does not run the functional code until the hardware that uses the code has been tested. The hardware consists of only the adapter card, memory module, and, if installed, Fast-Write Cache Option Card and battery .
318 User ’ s Guide and Maintenance Information.
Chapter 15. Removal and Replacement Procedures Exchanging Disk Drives 1. If you are removing a disk drive under concurrent maintenance (see the service information for the device that contains the disk drive), you must first determine which hdisk is using the pdisk that you want to remove.
SSA RAID Arrays Move cursor to desired item and press Enter. List All Defined SSA RAID Arrays List All Supported SSA RAID Arrays List All SSA RAID Arrays Connected to a RAID Manager List Status Of All.
4. A prompt is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter. List All Defined SSA RAID Arrays List All Supported SSA RAID Arrays List All SSA RAID Arrays Connecte.
7. Attention: Y ou should be here only if you are working with a RAID-1, RAID-5, or RAID-10 array . For fast path, type smitty redssaraid and press Enter . Otherwise: a. Select Change Member Disks in an SSA RAID Array from the SSA RAID Array menu. b. Select Remove a Disk from an SSA RAID Array .
9. The following information is displayed: Remove a Disk from an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
17. On each using system to which this replacement disk drive is connected, you must now remove from the system configuration the reference to the pdisk that you have just removed. Attention: If the disk drive is connected to more than one using system, the pdisk and hdisk numbers might be different on each system.
23. If the disk drive that you are installing is a replacement for a disk drive that was a member of an SSA RAID array , go to step 24. Otherwise, go no further with these instructions. 24. T ype smitty ssaraid and press Enter . 25. Select Change/Show Use of an SSA Physical Disk .
Changing Pdisk and Hdisk Numbers Pdisk and hdisk numbers are assigned automatically when the using system is configured. T o help in system administration, it is sometimes useful to change these numbers. If you want to change the numbers, use the following procedure: 1.
Removing and Replacing an Advanced SerialRAID Adapter Attention: The adapter assembly contains parts that are electrostatic-discharge (ESD) sensitive. Use the tools and procedures defined by your organization to protect such parts. 1. Remove the adapter from the using system (see the Installation and Service Guide for the using system).
If you cannot do this procedure because, for example, the boot disks are on the SSA network, do the following: a. Run diagnostics to the SSA adapter that is on the partner system, to ensure that no array problems exist. b. W ait until all coupled disk drives can be uncoupled, before you connect the new adapter to the network.
Removing an SDRAM Module of an Advanced SerialRAID Adapter Attention: The adapter assembly contains parts that are electrostatic-discharge (ESD) sensitive. Use the tools and procedures defined by your organization to protect such parts. 1. Remove the adapter from the using system (see the Installation and Service Guide for the using system).
Installing an SDRAM Module of an Advanced SerialRAID Adapter Attention: v The adapter assembly contains parts that are electrostatic-discharge (ESD) sensitive.
4. Refer to Figure 45. 5. Carefully insert the SDRAM module into the connector . 6. Press strongly on the module until it is fully home. 7. Close the clips 1 by pivoting them in the directions shown by the arrows in the diagram. Y ou hear a click when the clips are fully closed.
Removing the Fast-Write Cache Option Card of an Advanced SerialRAID Adapter Attention: v The adapter assembly contains parts that are electrostatic-discharge (ESD) sensitive. Use the tools and procedures defined by your organization to protect such parts.
5. Refer to Figure 47. 6. Invert the adapter card, so that its components are upward. 7. Carefully unplug the Fast-Write Cache Option card 2 from the connector 1 .
Installing the Fast-Write Cache Option Card of an Advanced SerialRAID Adapter Attention: The adapter card contains parts that are electrostatic-discharge (ESD) sensitive. Use the tools and procedures defined by your organization to protect such parts.
6. Refer to Figure 49. 7. Install the mounting screw 1 , and tighten it fully . (The screw is supplied with the Fast-Write Cache Option Card.) 8. Reinstall the adapter into the using system (see the Installation and Service Guide for the using system).
Removing the Battery Assembly from the Fast-Write Cache Option Card of an Advanced SerialRAID Adapter Attention: v The adapter assembly contains parts that are electrostatic-discharge (ESD) sensitive. Use the tools and procedures defined by your organization to protect such parts.
6. Refer to Figure 51. 7. Invert the Fast-Write Cache Option card. 8. Carefully unplug the battery assembly from the connector 1 . 1 Figure 51. Disconnecting the Battery Assembly Chapter 15.
Installing a Battery Assembly into the Fast-Write Cache Option Card of an Advanced SerialRAID Adapter Attention: v The adapter assembly contains parts that are electrostatic-discharge (ESD) sensitive. Use the tools and procedures defined by your organization to protect such parts.
4. Refer to Figure 53. 5. Locate the battery assembly so that the two lugs 1 are under the edges of the small slots 2 , and the clip 3 is over the larger slot 4 . 6. Carefully press the battery assembly downward until the clip latches under the edge of the slot.
Part Numbers v Advanced SerialRAID Adapter card without SDRAM module and without Fast-Write Cache Option card: 09L2090 v 64 MB module: 09L2104 v 128 MB module: 08J0663 v Fast-Write Cache Option Card: .
Chapter 16. Using the SSA Command Line Utilities The commands that are described here allow you to get access from the command line to some of the functions that are available in the SSA service aids. The commands are very simple and are intended for use mainly from within shell scripts.
-t This optional flag allows new levels of microcode to be tested. The enclosure returns to the original level of microcode if the enclosure power is switched off, then switched on. Examples T o install the latest level of microcode on all available SES enclosures, give the command: ssa_sesdld -u T o install microcode file coral1014.
ssaadap Command Purpose T o list the adapters to which a logical disk or physical disk is connected. Syntax ssaadap -l LogicalDiskName ssaadap -l PhysicalDiskName Description The output is the list of SSA adapters to which the logical or physical disk is connected.
ssacand Command Purpose T o display the unused connection locations for an SSA adapter . Syntax ssacand -a AdapterName -P|-L Description The ssacand command lists the available connection locations of an SSA adapter .
ssa_certify Command Purpose v T o certify the physical disk drive so that data can be read from, or written to, the disk drive without problems. v T o certify a RAID-5 array to determine whether any array logical block addresses (LBAs) have been as unreadable.
reassign operations. Y ou must not use this flag when the ssa_certify command is running concurrently on an active using system. -n MaxReadSize Specifies the maximum size, in kilobytes, of each read command that is sent to the disk drive.
ssaconn Command Purpose T o display the SSA connection details for the physical disk. Syntax ssaconn -l PhysicalDiskName -a AdapterName Description The ssaconn command performs a function that is similar to the Link V erification service aid.
ssa_diag Command Purpose T o run diagnostic tests to a specified device. Syntax ssa_diag -l pdiskX ssa_diag -l ssaX Description The ssa_diag command is in /usr/lpp/diagnostics/bin. Flags -a Causes the adapter to be reset if the device that is being tested is an adapter .
ssadisk Command Purpose T o display the names of disk drives that are connected to an SSA adapter . Syntax ssadisk -a AdapterName -P|-L Description The ssadisk command lists the names of disk drives that are connected to an SSA adapter .
ssadload Command Purpose T o download microcode to SSA physical disk drives. Syntax ssadload -d PhysicalDiskName -f CodeFileName [-p] ssadload -u [-d PhysicalDiskName | -a adapter ] [-p] ssadload -s [-d PhysicalDiskName | -a adapter ] Description The ssadload command performs microcode downloads to SSA physical disk drives.
Flags -d PhysicalDiskName Specifies the physical disk drive that is to receive the microcode. -f CodeFileName Specifies the microcode file to be downloaded. -u Ensures that all SSA physical disk drives are loaded with the latest level of microcode that is available on the system.
v Using the -s and -a adapter flags: ssadload -s -a ssa0 With these flags, the command lists the existing levels of microcode of all the available disk drives that are connected to adapter ssa0.
ssa_ela Command Purpose T o look for the most significant error in the error log. Syntax ssa_ela ssa_ela -l Device [-h timeperiod] ssa_ela -l pdisk ssa_ela -l hdisk ssa_ela -l adapter Description The ssa_ela command (with no flags) scans the error log, and looks for all SSA errors.
Output If an error occurs, the ssa_ela command sends an error message to stdout, such as: ssa0 SRN 42500 If no error occurs, the command sends no message to stdout. A non-zero return code indicates an error . The command sends an error message to stderr .
ssaencl Command Purpose T o allow the monitoring and changing of the status for SSA SES disk enclosures (subsystems). Syntax T o display enclosure component settings: ssaencl -l name [-s] [-v] [-i] [-r] [-b [card ...]] [-t [threshold ...]] [-a] [-f [fan .
-t [threshold] Displays all the temperature thresholds, or only the specified temperature thresholds. The valid values for the [threshold] parameter are: lowarn The low-temperature warning threshold. locrit The low-temperature critical threshold. hiwarn The high-temperature warning threshold.
-S b[card ...] Resets the flag for the bypass card. V alid values for card are 1, 4, 5, 8, 9, 12, 13, 16. -S p[PSU ...] Resets the flag for the selected PSU (power supply assembly). V alid values for PSU are 1, 2. -S r Resets the flag for remote power on (RPO).
ssa_format Command Purpose T o format the specified device. Syntax ssa_format -l pdisk or ssa_format -l SSA_Adapter [-b] Description The ssa_format -l pdisk command opens the pdisk special file, and uses the ISAL Format command to format the device. Y ou can close the device while the format operation is running.
-b Specifies that the battery-age counter be reset. When this flag is used, the data on the Fast-Write Cache Option Card is not set to zero. Important: Do not select the -b flag unless you have exchanged the battery . Otherwise, no error message will occur when the battery reaches the end of its life.
ssa_fw_status Command Purpose T o show the status of the fast-write cache. Syntax ssa_fw_status -a Adapter [-p|-l|-c] Description The ssa_fw_status command displays the status of the fast-write cache of an SSA adapter . Flags -a Adapter Shows all fast-write status for the specific adapter .
ssa_getdump Command Purpose T o display SSA adapter dump locations, and to save the dump to a specified location. Syntax For the List version of the command: ssa_getdump -l [-h] [-d pdiskxx] [-a Adapt.
Flags The ssa_getdump command uses several types of flag: v Required flags for both modes v Required flags for Copy mode v Optional flags for List mode v Optional flags for Copy mode Required Flags for Both Modes Yo u must use one of these flags: -l Specifies that the program is to operate in List mode.
-a AdapterName Specifies the adapter name for which the program must search (for example, ssa1). The adapter must be known to the searching machine. -n AdapterUID Specifies the adapter UID for which the program must search. The adapter need not be known to the searching machine.
ssaidentify Command Purpose T o set or clear Identify mode for a physical disk. Syntax ssaidentify -l PhysicalDiskName -y ssaidentify -l PhysicalDiskName -n Description If the -y parameter is specified, the disk is set into Identify mode. While the disk is in Identify mode, its amber Ready light flashes at approximately one-second intervals.
ssa_progress Command Purpose T o show how much (by percentage) of a format operation has been completed, and to show the status of the format operation.
ssa_rescheck Command Purpose T o report the reservation status of an hdisk. Syntax ssa_rescheck -l hdisk [-h] Description The ssa_rescheck command tests the access paths to the specified hdisk. It checks whether the disk is reserved. If the disk is reserved, the command attempts to determine why the disk is reserved.
Examples The following examples show typical output from the rescheck command. The Adapter In Use field shows which adapter path the using system is using.
ssa_servicemode Command Purpose T o put the disk drive into Service Mode (set Service Mode), or to remove the disk drive from Service Mode (reset Service Mode).
ssa_speed Command Purpose T o determine the operating speed of SSA links. Syntax ssa_speed -l pdisk [-s] ssa_speed -a AdapterName {-p Loop | -n Network} [-s] ssa_speed -x [-e] Description The ssa_spee.
Output The ssa_speed command sends all error messages to stderr , and output to stdout. Link speeds can be: v 20 (20 MB) v 40 (40 MB) v 00 (not operational) v ?? (not determined) Examples v T o displa.
ssavfynn Command Purpose T o check for duplicated node numbers. Note: It is recommended that this command be used only when all the adapters on the network are SSA RAID adapters. Syntax ssavfynn [-w] Description The ssavfynn command is in the /usr/lpp/diagnostics/bin file.
ssaxlate Command Purpose T o translate between logical disks (hdisks) and physical disks (pdisks). Syntax ssaxlate -l LogicalDiskName ssaxlate -l PhysicalDiskName Description If the parameter is a logical disk, the output is a list of names of the physical disks that provide support for that logical disk.
Chapter 17. SSA Service Aids Note: For some problems, you can use the SSA command line utilities instead of the SSA service aids. For information about the command line utilities, see Chapter 16, “ Using the SSA Command Line Utilities ” on page 341.
Note: The service aids refer to the Advanced SerialRAID Adapter as IBM SSA 160 SerialRAID Adapter (14109100). On some service screens, this name is shortened.
The Identify Function The Identify function can be accessed from many of the service aid menus . This function enables you to determine the location of a particular disk drive that you want to identify , but do not want to remove.
Starting the SSA Service Aids T o start the SSA service aids: 1. Start the using-system diagnostics (see the Diagnostic Information for Multiple Bus Systems manual), and go to the Diagnostic Operating Instructions . 2. Follow the instructions to select Function Selection .
5. Select the service aid that you require, then go to the relevant instructions in this chapter: “ Set Service Mode Service Aid ” on page 378 “ Link V erification Service Aid ” on page 383 .
Set Service Mode Service Aid The Set Service Mode service aid enables you to determine the location of a particular disk drive, and to remove that disk drive from the unit in which it is installed. It causes the Check light of that disk drive to come on for identification, and stops all SSA loop activity through the disk drive.
T o use the Set Service Mode service aid: 1. Select Set Service Mode from the SSA Service Aids menu (see “ Starting the SSA Service Aids ” on page 376). A list of physical disk drives (pdisks) is displayed: SET SERVICE MODE 802381 Move cursor onto selection, then press <Enter>.
2. Select the pdisk that you want to identify or put into Service Mode (for example, pdisk3). The following display appears with details of the disk drive that you have just selected: SET SERVICE MODE 802382 systemname:pdisk0 AC50AE43 4GB SSA C Physical Disk Drive Move cursor onto selection, then press <Enter>.
3. Select Service Mode or the Identify function. (For this example, assume that you have selected Service Mode.) The list of pdisks is displayed again, and the disk drive that you selected is marked by a >, which shows that the disk drive is in Service Mode.
4. Select a second disk drive if required (for example, pdisk5). The following display appears again: SET SERVICE MODE 802382 systemname:pdisk5 AC7C6E51 4GB SSA C Physical Disk Drive Move cursor onto selection, then press <Enter>. + Set or Reset Identify.
Link V erification Service Aid The Link V erification service aid helps you determine: v Which devices are connected to the SSA loop v Where an SSA loop has been broken v The status of the disk drives.
3. When you have selected an adapter , a list is displayed that shows all the devices that are connected to the adapter: LINK VERIFICATION 802386 SSA Link Verification for: nunu:ssa0 04-02 IBM SSA 160 SerialRAID Adapter ( To Set or Reset Identify, move cursor onto selection, then press <Enter>.
v The Adapter Port column shows the address of each adapter port to which a particular device is connected. The device is connected to two ports except when the SSA loop is broken, under which condition the device is connected to only one port. v The Status column shows the existing status of the physical disk drive, as known by the adapter .
Notes: a. In the lists of physical disk drives (pdisks) that are displayed by the service aids, you might see: ????? These question marks show where an SSA loop is broken. The service aid cannot display which, if any , devices are missing from this configuration.
Configuration V erification Service Aid The Configuration V erification service aid enables you to determine the relationship between SSA logical units (hdisks) and SSA physical disk drives (pdisks). It also displays the connection information and operational status of the disk drive.
2. Select the hdisk or pdisk that you want to verify . 3. If you select an hdisk, a list of pdisks is displayed: CONFIGURATION VERIFICATION 802391 systemname:hdisk2 AC51DB47 SSA Logical Disk Drive Good To set or reset Identify, move cursor onto selection, then press <Enter>.
Format Disk Service Aid The Format Disk service aid formats SSA disk drives. Attention: Formatting a disk drive destroys all the data on that disk drive. Use this procedure only when instructed to do so by the service procedures. T o use the Format Disk service aid: 1.
2. Select the pdisk that you want to format. The following instructions are displayed: FORMAT DISK 802396 systemname:pdisk2 AC1DBE11 4GB SSA C Physical Disk Drive Move cursor onto selection, then press <Enter>. + Set or Reset Identify. Select this option to set or reset the Identify indicator on the disk drive.
Certify Disk Service Aid The Certify service aid verifies that all the data on a disk drive can be read correctly . Other maintenance procedures tell you when you need to run this service aid. T o use the Certify Disk service aid: 1. Select Certify Disk from the SSA Service Aids menu (see “ Starting the SSA Service Aids ” on page 376).
2. Select the pdisk that you want to certify . The following instructions are displayed: CERTIFY DISK 802405 systemname:pdisk0 AC706E9A 4GB SSA C Physical Disk Drive Move cursor onto selection, then press <Enter>. + Set or Reset Identify. Select this option to set or reset the Identify indicator on the disk drive.
Display/Download Disk Drive Microcode Service Aid The Display/Download Disk Drive Microcode service aid allows you to: v Display the level of microcode that is installed on all available disk drives.
T o use the Display/Download Disk Drive Microcode service aid: 1. Select Display/Download Disk Drive Microcode from the SSA Service Aids menu (see “ Starting the SSA Service Aids ” on page 376). The following menu is displayed: MICROCODE DOWNLOAD 802420 Move cursor onto selection, then press Enter.
3. Attention: For several seconds during microcode download, new data is written to the disk drive EEPROM. If the power fails while that data is being written, the disk drive microcode might become corrupted. The microcode cannot be corrected . Normally , exchange the disk drive for a new one.
Link Speed Service Aid The Link Speed service aid allows you to display the operating speed of each link on an SSA adapter . T o use the Link Speed service aid: 1. Select Link Speed from the SSA Service Aids menu (see “ Starting the SSA Service Aids ” on page 376).
2. Select the adapter that you want to inspect. A list of link speeds is displayed, as shown in this example screen: LINK SPEED 802438 SSA Link Speed for: systemname:ssa0 00-03 IBM SSA 160 SerialRAID Adapter ( To set or reset Identify, move cursor onto selection, then press <Enter>.
The Source field represents the link end that is closest to the A1 or B1 port. The Destination field represents the link end that is closest to the A2 or B2 port. Note: The Source and Destination fields have no other meaning. They do not indicate data flow .
This screen shows the same configuration, but here the link is broken between pdisk1 and pdisk2. LINK SPEED 802438 SSA Link Speed for: systemname:ssa0 00-03 IBM SSA 160 SerialRAID Adapter ( To set or reset Identify, move cursor onto selection, then press <Enter>.
Service Aid Service Request Numbers (SRNs) If the SSA service aids detect an unrecoverable error , and are unable to continue, one of the following service request numbers (SRNs) might occur: v SSA01 v SSA02 v SSA03 These SRNs are explained in the main SRN table (see “ Service Request Numbers (SRNs) ” on page 41 1).
Example 1. Normal Loops In Figure 56, disk drives 1 through 8 are connected to connectors A1 and A2 of the SSA adapter 1 . Disk drives 9 through 12 are connected to connectors B1 and B2 of the same SSA adapter . Disk drives 13 through 16 are connected to connectors A1 and A2 of a different SSA adapter 2 .
For this example, the Link V erification service aid displays the following information: LINK VERIFICATION 802386 SSA Link Verification for: systemname:ssa0 00-04 IBM SSA 160 SerialRAID Adapter ( To Set or Reset Identify, move cursor onto selection, then press <Enter>.
Example 2. Broken Loop (Cable Removed) Each disk drive normally communicates with the adapter through one data path. Because data can pass round the loop in either direction, the adapter automatically reconfigures the loop to enable communication to continue to each disk drive if the loop becomes broken.
Using system Disk 1 Disk 2 Disk 3 Disk 4 Disk 5 Disk 6 Disk 7 Disk 8 Disk 16 Disk 15 Disk 14 Disk 13 Disk 12 Disk 11 Disk 10 Disk 9 Using system A1 A2 B1 B2 A1 A2 B1 B2 Figure 57.
For this example, the Link V erification service aid displays the following information: LINK VERIFICATION 802386 SSA Link Verification for: systemname:ssa0 00-04 IBM SSA 160 SerialRAID Adapter ( To Set or Reset Identify, move cursor onto selection, then press <Enter>.
Example 3. Broken Loop (Disk Drive Removed) In Figure 58 on page 407, disk drives 1 through 8 are connected to connectors A1 and A2 of the SSA adapter 1 , but the loop is broken because disk drive number 3 has been removed. Disk drives 9 through 12 are connected to connectors B1 and B2 of the same SSA adapter .
Using system Disk 1 Disk 2 Disk 3 Disk 4 Disk 5 Disk 6 Disk 7 Disk 8 Disk 16 Disk 15 Disk 14 Disk 13 Disk 12 Disk 11 Disk 10 Disk 9 Using system A1 A2 B1 B2 A1 A2 B1 B2 Figure 58.
For this example, the Link V erification service aid displays the following information: LINK VERIFICATION 802386 SSA Link Verification for: systemname:ssa0 00-04 IBM SSA 160 SerialRAID Adapter ( To Set or Reset Identify, move cursor onto selection, then press <Enter>.
Finding the Physical Location of a Device The physical location of a device (for example, a disk drive or an SSA adapter) cannot be reported directly by the using system because of the way in which the SSA interface works. The address of an SSA device is related to the position of that device on the SSA loop.
410 User ’ s Guide and Maintenance Information.
Chapter 18. SSA Problem Determination Procedures SSA problem determination procedures are provided by power-on self-tests (POST s), service request numbers, and maintenance analysis procedures (MAPs). Some of these procedures use the service aids that are described in Chapter 17, “ SSA Service Aids ” on page 373.
2. Read carefully the “ Action ” you must do for the problem. Do not exchange FRUs unless you are instructed to do so . 3. Normally exchange only one FRU at a time. After each FRU is exchanged, go to “ MAP 2410: SSA Repair V erification ” on page 475 to verify the repair .
SRN Problem Possible Causes 1xxxx Description: SRNs in this range are not adapter SRNs. Action: For SRNs in this range, see the documentation for your SSA enclosure or SSA subsystem. Not applicable. 20P AA Description: An open SSA link has been detected.
SRN Problem Possible Causes 2A004 Description: Async code 04 has been received. Probably , a software error has occurred. Action: Go to “ Software and Microcode Errors ” on page 441 before exchanging any FRUs. Software error . Possible FRUs: Device (50%) ( “ Exchanging Disk Drives ” on page 319).
SRN Problem Possible Causes 34000 Description: The adapter cannot initialize a device. This problem might be badly affecting the SSA loop. If the device was a member of a RAID array , you might not be able to list this disk drive by using the RAID facilities.
SRN Problem Possible Causes 40128 Description: A 128 MB SDRAM in the adapter card module has failed. Action: Exchange the FRUs for new FRUs. Possible FRUs: 128 MB SDRAM module (99%) ( “ Removing an SDRAM Module of an Advanced SerialRAID Adapter ” on page 329).
SRN Problem Possible Causes 42510 Description: Not enough SDRAM available to run the fast-write cache operation. Action: 1. Start the using-system service aids. 2. Select Display or Change Configuration or Vital Product Data (VPD) . 3. Select Display Vital Product Data .
SRN Problem Possible Causes 42521 Description: A Fast-W rite Cache Option Card has failed. Data has been written to the cache card, and cannot now be recovered. The disk drives that have lost the data cannot be identified. All unsynchronized fast-write disk drives that are attached to this adapter are offline.
SRN Problem Possible Causes 42524 Description: A fast-write disk drive (or drives) contains unsynchronized data, but the Fast-Write Cache Option Card cannot be detected. The disk drive (or drives) is offline. Action: v If the Fast-Write Cache Option Card has been removed, reinstall it, and test the disk drive subsystem.
SRN Problem Possible Causes 42525 Description: A fast-write logical disk contains unsynchronized data, but the Fast-Write Option Card does not contain that data.
SRN Problem Possible Causes 42528 Description: A fast-write disk drive has been detected that was previously unsynchronized, but has since been configured on a different adapter . Action: If this disk drive contains data that should be kept, return the disk drive to the adapter to which it was previously connected.
SRN Problem Possible Causes 4252C Description: The Fast-Write Cache Option Card battery needs to be exchanged for a new one. Action: Exchange the FRU for a new FRU. Possible FRUs: Fast-Write Cache Option Card battery (100%) ( “ Removing the Fast-Write Cache Option Card of an Advanced SerialRAID Adapter ” on page 332).
SRN Problem Possible Causes 43P AA Description: An SSA device on the link is preventing the completion of the loop configuration. Action: If the SSA service aids are available, run the Link V erification service aid (see “ Link V erification Service Aid ” on page 383) to determine which device is preventing configuration.
SRN Problem Possible Causes 46500 Description: A member disk drive is missing from an array , or the original SSA adapter is not available. The array is in the Offline state. Action: v If the missing disk drive is still operational, reconnect it to the SSA loop.
SRN Problem Possible Causes 48600 Description: All the member disk drives of an array are not on the same SSA loop. The array is in the Exposed state, and write operations to the array are inhibited. Action: All the member disk drives of an array must be on the same SSA loop.
SRN Problem Possible Causes 48750 Description: An array is in the Offline state because the primary or the secondary half of the array is not present. Action: Switch on the power to the other half of the array , or repair the broken loop that is preventing access to the other disk drives.
SRN Problem Possible Causes 48760 Description: An array is in the Offline state because the split/join procedure was not performed correctly . The data on the array is not constant. Action: See Chapter 8, “ Split-Site Management ” on page 193 before you attempt to recover the array .
SRN Problem Possible Causes 48950 Description: A disk drive has caused an array building operation to fail. Action: 1. T ype smitty ssaraid and press Enter . 2. Select List all Defined SSA RAID Arrays . The hdisk that is causing this problem is listed as exposed or degraded.
SRN Problem Possible Causes 49000 Description: An array is in the Degraded state. A disk drive might not be available for one of the following reasons: v The disk drive has failed. v The disk drive has been removed from the subsystem. v An SSA link has failed.
SRN Problem Possible Causes 49500 Description: No hot spare disk drives are available for an array that is configured for hot spare disk drives. Action: Determine whether any disk drives have failed or have been rejected.
SRN Problem Possible Causes 49510 Description: Hot-spare configuration is not synchronized. This problem has occurred because the cabling has changed or because new hot-spare disks have been added to the SSA loop. Action: 1. If the changes were not planned, restore the system to its original configuration.
SRN Problem Possible Causes 49520 Description: Hot-spare tuning has been lost. Action: 1. T ype smitty ssaraid and press Enter . 2. Select List Status of Hot-Spare Pools . 3. Select the adapter that logged the error . If the adapter is not known, select all adapters.
SRN Problem Possible Causes 49530 Description: The number of disk drives that remain in a hot-spare pool is less than the specified number . Action: 1. T ype smitty ssaraid and press Enter . 2. Select Change/Show Use of an SSA Physical Disk . 3. Note all the disk drives that are listed as rejected.
SRN Problem Possible Causes 49950 Description: An array copy disk drive is missing. The array copy is degraded. If the missing disk drive is restored to the network or exchanged for a new disk drive, the copy rebuilds. A disk drive might not be available for one of the following reasons: v The disk drive has failed.
SRN Problem Possible Causes 50002 Description: An SSA adapter DMA error has occurred. Action: Exchange the FRU for a new FRU. Possible FRUs: SSA adapter card (100%) ( “ Removing and Replacing an Advanced SerialRAID Adapter ” on page 327). 50007 Description: The IOCC detected an internal error.
SRN Problem Possible Causes 50200 Description: A duplicate node number has been detected. This problem is a user error . Action: See “ SSA Disk Concurrent Mode of Operation Interface ” on page 287. Y ou can use the ssavfynn command line utility (see “ ssavfynn Command ” on page 371) to determine which node has the duplicate node number .
SRN Problem Possible Causes 504XX Description: The SSA adapter microcode has hung. Action: Run diagnostics in System V erification mode to the SSA adapter . If the diagnostics fail, exchange the FRU for a new FRU. If the diagnostics do not fail, go to “ Software and Microcode Errors ” on page 441.
SRN Problem Possible Causes D4000 Description: The diagnostics cannot configure the SSA adapter . Action: Exchange the FRU for a new FRU. Possible FRUs: SSA adapter card (100%) ( “ Removing and Replacing an Advanced SerialRAID Adapter ” on page 327).
SRN Problem Possible Causes DFFFF Note: The description and action for this SRN are valid only if you have run diagnostics to the SSA attachment. If this SRN has occurred because you have run diagnostics to some other device, see the service information for that device.
SRN Problem Possible Causes SSA03 Description: The service aid was unable to open an hdisk. This problem might have occurred because a disk drive has failed or has been removed from the system.
Software and Microcode Errors Some SRNs indicate that a problem might have been caused by a software error or by a microcode error . If you have one of these SRNs, do the following actions: 1. Make a note of the contents of the error log for the device that has the problem.
2. Review the configuration that you are trying to make, and determine why that configuration is not valid. 3. Correct your configuration by reconfiguring the SSA cables or by removing the excess devices or adapters from the loop.
SSA Maintenance Analysis Procedures (MAPs) The maintenance analysis procedures (MAPs) describe how to analyze a failure that has occurred in an SSA loop. How to Use the MAPs Attention: Unless the using system needs to be switched off for some other reason, do not switch off the using system when servicing an SSA loop .
MAP 2010: ST ART This MAP is the entry point to the MAPs for the adapter . If you are not familiar with these MAPs, read “ How to Use the MAPs ” on page 443 first. Y ou might have been sent here because: v The system problem determination procedures sent you here.
MAP 2320: SSA Link This MAP helps you to isolate FRUs that are causing an SSA loop problem between a device and the SSA adapter , or between two devices. If you are not familiar with SSA loops, read the section Chapter 2, “ Introducing SSA Loops ” on page 7 before using this MAP .
If the service aid cannot detect any pdisks, a message is displayed: LINK VERIFICATION 802385 Move cursor onto selection, then press <Enter>. nunu:ssa1 00-04 IBM SSA 160 SerialRAID Adapter ( nun.
LINK VERIFICATION 802386 SSA Link Verification for: nunu:ssa0 00-04 IBM SSA 160 SerialRAID Adapter ( To Set or Reset Identify, move cursor onto selection, then press <Enter>.
5. (from step 4) Observe the Status column on the screen. If the status of any pdisk is ‘ Failed ’ , that pdisk is failing. In the example shown here, pdisk2 is failing.
6. (from step 5) Observe the list of pdisks the screen. A row of question marks (?????) shows that a link in one of the loops is broken. If two rows of question marks are displayed, two links are broken, one in each loop. In the example shown here, pdisk2 is missing.
MAP 2323: SSA Intermittent Link Error This MAP helps you to isolate FRUs that are causing an intermittent SSA link problem. Y ou are here because you have an SRN from the series 21xxx through 29xxx, or you have SRN 33xxx.
a. Observe the SRN that sent you to this MAP . The last three characters are in the format P AA, where P is the number of the SSA adapter port, and AA is the SSA address of the device). Note the value of P AA in the SRN. For example: If the SRN is 24002, P AA = 002.
Example 1 If the SRN is 24002, the device is connected to adapter port 0 (shown as A1 on the screen), and has an SSA address of 02 (shown as 2 on the screen). In the example screen, that device is pdisk3, which is the first device of the two. The second device is pdisk2 (P AA − 1).
Example 2 If the SRN is 24104, the device (in theory) is connected to adapter port 1 (shown as A2 on the screen). The device, however , has an SSA address of 04. That address is higher than the highest address that is displayed for adapter port 1. The devices are, therefore, the SSA adapter and pdisk1.
MAP 2324: SSA RAID This MAP helps you to solve problems that have occurred in SSA RAID arrays. Attention: Unless the using system needs to be switched off for some other reason, do not switch off the using system when servicing an SSA link or an enclosure in which SSA devices are installed .
3. (from step 2) Do you have any other SRN? NO Go to step 22 on page 467. YES a. Solve the problems that caused the SRN. b. Return to step 1 on page 454. 4. (from step 2) Find your SRN in the following table, then do the appropriate actions. Note: If you still do not have any of these SRNs, you are in the wrong MAP .
6. (from step 5) Either one or more disk drives have failed, or an array that is not complete has been connected to the SSA adapter . v If one or more disk drives have been added to this system, and those disk drives were previously members of an array on this system or on another system, do the following: a.
7. (from step 6) The array data cannot be recovered. The following steps clear the error condition and change the disk drives to a usable state. a. T ype smitty ssaraid and press Enter .
9. (from step 4) Attention: Part of the data that is on the array has been damaged and cannot be recovered. Before any other action is taken, the user must recover all the data that is not damaged, and create a backup of that data. a. T ype smitty ssaraid and press Enter .
10. (from step 9) a. T ype smitty ssaraid and press Enter . b. Select List/Identify SSA Physical Disks . c. Select List Disks in an SSA RAID Array . d. Select the failing disk drive, and note the pdisk numbers of the disk drives that are members of the array .
12. (from step 1 1) Did the Certify service aid fail again? NO a. Ask the user to recreate the array . b. Go to step 22 on page 467. YES a. Exchange the failing disk drive for a new one (see “ Exchanging Disk Drives ” on page 319).
14. (from step 13) Are any disk drives listed as “ SSA physical disks that are rejected ” ? NO A disk drive has not been detected by the adapter . Go to step 15 on page 462. YES a. Run diagnostics in System V erification mode to all the disk drives that are listed as rejected.
When the rebuilding operation is complete, ask the user to run diagnostics in System V erification mode to the SSA adapters, to ensure that the rebuilding operation has not found any more problems. k. Go to “ MAP 2410: SSA Repair V erification ” on page 475 to verify the repair .
17. (from step 4) A RAID-5 array is in the Exposed state when one member disk drive of the array is not available to the array . A RAID-1 or RAID-10 array is in the Exposed state when one or more mirrors are exposed. A mirror is exposed when one disk drive in the mirror pair is not available to the array .
18. (from step 17) Are any disk drives listed as “ SSA physical disks that are rejected ” ? NO A disk drive has not been detected by the adapter . Go to step 19 on page 465. YES a. Run diagnostics in System V erification mode to all the disk drives that are listed as rejected.
When the rebuilding operation is complete, ask the user to run diagnostics in System V erification mode to the SSA adapters, to ensure that the rebuilding operation has not found any more problems. k. Go to “ MAP 2410: SSA Repair V erification ” on page 475 to verify the repair .
21. (from step 1) No spare disk drives are available for an array that is configured for hot spare disk drives. a. If the subsystem contains disk drives that have failed, repair those disk drives, or exchange them for new disk drives (see “ Exchanging Disk Drives ” on page 319).
22. (from step 7 in MAP 2410: SSA Repair V erification, and from steps 3, 1 1, and 12 in this MAP) RAID Checkout Y ou are now starting the RAID checkout procedure a. T ype smitty ssaraid and press Enter . b. Select Change/Show Use of an SSA Physical Disk from the SSA RAID Arrays menu.
c. If problems occur on any disk drive, exchange that disk drive for a new disk drive (see “ Exchanging Disk Drives ” on page 319), then continue from step 24e in this procedure. d. A disk drive that is listed as rejected is not necessarily failing.
d. Select the pdisk from the list, and change the Current Use parameter to Array Candidate Disk . e. Select Change Member Disks in an SSA RAID Array . f. Select Swap Members of an SSA RAID Array . g. Select the hdisk that is in the Degraded copy state (that is, the hdisk that you noted in step 23d on page 467).
27. (from step 22) Is any disk drive failing? NO A disk drive that is listed as rejected is not necessarily failing. For example, the array might have rejected the disk drive because a power problem, or an SSA link problem, caused that drive to become temporarily unavailable.
30. (from step 29) Do any RAID-5 arrays have Unsynced Parity Strips or Unbuilt Data Strips? NO Go to step 31. YES The rebuilding operation is running or has stopped before completion. a. Note the number of unsynced parity strips and unbuilt data strips.
33. (from step 32) W as SRN 49100 logged, but no error found, when diagnostics were run in System V erification mode? NO Go to step 34. YES An array was in the Exposed state, but is now in the Good state. This problem might have occurred because a disk drive was temporarily removed from the system.
36. (from step 35) Y ou have solved all the problems. a. Run the repair verification or repair completion procedures that are defined by your using system.
v Array Candidate Disk if the use of hot spares is disabled for the arrays on the subsystem e. Go to step 38. 38. (from step 37) Y ou have changed the use of a disk drive. Y ou must now ensure that the hot spare pools are correctly configured. T o do this action: a.
MAP 2410: SSA Repair V erification This MAP helps you to verify that FRUs that you have exchanged for new FRUs, or repair actions that you have done, have solved all the problems on the subsystem.
Notes: 1) Do not run Advanced Diagnostics; otherwise, errors might be logged on other using systems that share the same loop. 2) If you have just exchanged a disk drive or an SSA adapter , you might need to run cfgmgr to restore the device to the system configuration.
7. (from steps 3 in MAP 2010: ST ART and from steps 5 and 4 in this MAP) Does your subsystem contain RAID arrays? If you are not sure whether your subsystem contains RAID arrays: a. T ype smitty ssaraid and press Enter . b. Select List All Defined SSA RAID Arrays .
SSA Link Errors SSA link errors can be caused if: v Power is removed from an SSA device. v An SSA device is failing. v An SSA device is removed. v A cable is disconnected.
Example 1 In Figure 59, the link is between two disk drives that are in the same subsystem. It has three parts. Example 2 In Figure 60, the link is between two disk drives that are in the same subsystem. It has five parts. Internal Connection Disk Drive 1 Disk Drive 2 SSA Subsystem Figure 59.
Example 3 In Figure 61, the link is between two disk drives that are not in the same subsystem. It has seven parts. Example 4 Figure 62, the link is between a disk drive and an SSA adapter . It has five parts. Example 5 In Figure 63, the link is between two SSA adapters.
Link Status (Ready) Lights If a fault occurs that prevents the operation of a particular link, the link status lights of the various parts of the complete link show that the error has occurred. Y ou can find the failing link by looking for the flashing green status light at each end of the affected link.
Service Aid If service aids are available, you can use the Link V erification service aid to show that the SSA loop is broken. LINK VERIFICATION 802386 SSA Link Verification for: systemname:ssa0 00-04 SSA Enhanced RAID Adapter To Set or Reset Identify, move cursor onto selection, then press <Enter>.
Part 3. Appendixes 483.
484 User ’ s Guide and Maintenance Information.
Appendix. Communications Statements The following statements apply to this product. The statements for other products intended for use with this product appear in their accompanying manuals.
International Electrotechnical Commission (IEC) Statement This product has been designed and built to comply with (IEC) Standard 950. A vis de conformit éà la r é glementation d ’ Industrie Canada Cet appareil num é rique de la classe A est conforme à la norme NMB-003 du Canada.
festgelegt), dann kann es dabei eventuell gest ö rt werden. In solch einem Fall ist der Abstand bzw . die Abschirmung zu der industriellen St ö rquelle zu vergr ö ssern. ″ Anmerkung: Um die Einhaltung des EMVG sicherzustellen sind die Ger ä te, wie in den Handb ü chern angegeben, zu installieren und zu betreiben.
488 User ’ s Guide and Maintenance Information.
Glossary This glossary explains terms and abbreviations that are used in the manual. The glossary contains terms and definitions from the IBM Dictionary of Computing . If you do not find the term or abbreviation for which you are looking, try the index or refer to the IBM Dictionary of Computing at URL: http://www .
Exposed state. The state that a RAID array enters if a member disk drive becomes missing (logically or physically) from that array . F Failed status. The disk drive is not working. fencing. SSA disk fencing is a facility that is provided in the SSA subsystem.
microcode. One or more microinstructions used in a product as an alternative to hard-wired circuitry to implement functions of a processor or other system component. mirrored pair . T wo disk drives that contain the same data, and are referred to as one entity by the using system.
service request number . A number that helps you to identify the cause of a problem, the failing field-replaceable units (FRUs), and the service actions that might be needed to solve the problem. Service request numbers are generated by the system error-log analysis, system configuration code, and customer problem determination procedures.
Index Numerics 128 MB Memory Module feature 5 3-way copy array copy services 173 Delete a RAID Array Copy option 183 Delete a V olume Group, Logical V olumes, or Filesystems Copy option 184 List All C.
array copy services (continued) Prepare a Copy option 175 Uncouple a V olume Group, Logical V olumes, or File Systems Copy option 177 array states, RAID-0 31 Good 31 Offline 31 array states, RAID-1 32.
attributes (continued) ODM, PCI (continued) bus_mem_start2 257 bus_mem_start3 257 bus_mem_start4 257 daemon 258 dma_mem 258 host_address 258 intr_priority 257 poll_threshold 258 scat_gat_pages 258 uco.
choosing the error threshold (alarm) level for a hot spare pool 51 chssaraid command 135 close subroutine tmssa device driver 297 command line error log analysis 232 Command Line Interface for RAID 23.
configuring and installing SSA RAID arrays (continued) adding a new hot spare pool 83 adding an SSA RAID array 60 adding disks to a hot spare pool 86 canceling all SSA disk drive identifications 129 c.
Degraded state, RAID-10 37 Degraded state, RAID-5 33 Delete a RAID Array Copy option 183 Delete a V olume Group, Logical V olumes, or Filesystems Copy option 184 Delete an SSA RAID Array option 70 det.
disk device driver (continued) files 282 purpose 281 return values 282 SSADISK_LIST_PDISKS ioctl operation 285 description 285 files 286 purpose 285 return values 286 SSADISK_SCSI_CMD ioctl operation .
FRU part numbers 340 full-stride writes, definition 272 G getting access to the Fast-Write menus 213 getting access to the SSA Adapters SMIT menu 40 getting access to the SSA Disks SMIT menu 41 gettin.
installing the SSA adapter 313 instruct types, Command Line Interface 238 interface, adapter device driver/head device driver 256 IOCINFO ioctl operation 261, 305 description 261, 305 disk device driv.
Offline state, RAID-5 34 one loop with two adapters in each of two using systems 12 one loop with two adapters in one using system 1 1 open and close subroutines adapter device driver 258 open subrout.
RAID arrays (continued) adding to the configuration 60 canceling all SSA disk drive identifications 129 changing member disks in an SSA RAID array 137 changing or showing the attributes of an SSA RAID.
removal and replacement procedures (continued) installing a battery assembly into the fast-write cache card 338 installing an SDRAM module 330 installing the fast-write cache card 334 removing an SDRA.
SMIT (or SMITTY) options (continued) Change/Show Characteristics of an SSA Logical Disk 214 Change/Show Use of an SSA Disk 144 Change/Show/Delete a Hot Spare Pool 86 Delete an SSA RAID Array 70 Enable.
SSA loops (continued) large configurations 16 links and data paths 7 loops and data paths, examples broken loop (cable removed) 403 broken loop (disk drive removed) 406 normal loops 401 one loop with .
ssadisk SSA disk device driver (continued) attributes common to logical and physical disks 271 attributes for logical disks only 271 attributes of the SSA router , ssar 270 error conditions 274 specia.
three-way copy (continued) SMIT menus for 172 ssa_delete_copy command 171 ssa_make_copy command 161 using SMIT menus to create a copy array 155 using ssa_make_copy command to create a copy array 159 u.
.
Part Number: 27H0678 Printed in the U.S.A. SA33-3285-02 (1P) P/N: 27H0678.
Spine information: A d va n ced S eri alRAID A d a p ters U se r’s Gui d e an d M ain te na n ce Inf o rma ti o n.
An important point after buying a device Compex Systems SA33-3285-02 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Compex Systems SA33-3285-02 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Compex Systems SA33-3285-02 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Compex Systems SA33-3285-02 you will learn all the available features of the product, as well as information on its operation. The information that you get Compex Systems SA33-3285-02 will certainly help you make a decision on the purchase.
If you already are a holder of Compex Systems SA33-3285-02, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Compex Systems SA33-3285-02.
However, one of the most important roles played by the user manual is to help in solving problems with Compex Systems SA33-3285-02. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Compex Systems SA33-3285-02 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
