Advanced SerialRAID Adapters User’s Guide and Maintenance Information SA33-3285-02
Advanced SerialRAID Adapters User’s Guide and Maintenance Information 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. . . . . . . . . . . . . . . . . . . . . . . . xv Definitions of Safety Notices . . . . . . . . . . . . . . . . . . . xv Safety Notice for Installing, Relocating, or Servicing. . . . . . . . . . . . xv | About This Book . . . . . . . . . . . . . . . . . . . . . . xvii Who Should Use This Book . . . . . . . . . . . . . . . . . . . xvii What This Book Contains . . . . . . . . . . . . . . . . . . . . xvii If You Need More Information. . . . . . . . . . . . . . . . . . .
Reserving Disk Drives Fast-Write Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 . 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
| Dealing with RAID Array Problems . . . . . . . . . . . . . . Getting Access to the SSA RAID Array SMIT Menu . . . . . . . . Identifying and Correcting or Removing Failed Disk Drives . . . . . Installing a Replacement Disk Drive . . . . . . . . . . . . . Using Other Configuration Functions . . . . . . . . . . . . . Getting Access to the SSA RAID Array SMIT Menu . . . . . . . . Listing All Defined SSA RAID Arrays . . . . . . . . . . . . Listing All Supported SSA RAID Arrays . . . . . . . . . . .
| | Remove a Disk From an SSA RAID Array Swap Members of an SSA RAID Array . . . . . . . . . . . . . . . . . . . . . . . Chapter 8. Split-Site Management . . . . . . . . . . . . . . Configuration of RAID-1 and RAID-10 Arrays . . . . . . . . . . . Operation after a Loss of Member Disks . . . . . . . . . . . . . One Half of the Array Is Not Present . . . . . . . . . . . . . Array is Offline because Adapter Is Not Known to the Remaining Half of the Array . . . . . . . . . . . . . . . . . . . . . .
| | Example 7: To Change an Attribute of an Object . . . . . . . Example 8: To Exchange a Member Disk Drive of an Existing Array . Example 9: To Make a New System Disk. . . . . . . . . . Example 10: To Delete an Array. . . . . . . . . . . . . SSARAID Command Attributes . . . . . . . . . . . . . . RAID Arrays Creation and Change Attributes . . . . . . . . RAID Arrays Change Attributes . . . . . . . . . . . . . Hot Spare Pool Creation and Change Attribute . . . . . . . .
Device Attributes . . . . . . . . . . . . . . . . . . . . . . Device-Dependent Subroutines . . . . . . . . . . . . . . . . . Error Conditions . . . . . . . . . . . . . . . . . . . . . . Special Files . . . . . . . . . . . . . . . . . . . . . . . IOCINFO (Device Information) SSA Disk Device Driver ioctl Operation . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . Description. . . . . . . . . . . . . . . . . . . . . . . . Files . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Information . . . . . . . . . . . . . . . . . . IOCINFO (Device Information) tmssa Device Driver ioctl Operation . . . Purpose . . . . . . . . . . . . . . . . . . . . . Description. . . . . . . . . . . . . . . . . . . . . TMIOSTAT (Status) tmssa Device Driver ioctl Operation . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . Description. . . . . . . . . . . . . . . . . . . . . TMCHGIMPARM (Change Parameters) tmssa Device Driver ioctl Operation Purpose . . . . . . . . . . . . . . . . . .
ssacand Command . Purpose . . . Syntax . . . . Description. . . Flags . . . . ssa_certify Command Purpose . . . Syntax . . . . Description. . . Flags . . . . ssaconn Command . Purpose . . . Syntax . . . . Description. . . Flags . . . . ssa_diag Command . Purpose . . . Syntax . . . . Description. . . Flags . . . . Output . . . . ssadisk Command . Purpose . . . Syntax . . . . Description. . . Flags . . . . ssadload Command . Purpose . . . Syntax . . . . Description. . . Flags . . . . Examples . . .
| | | | | | | ssa_fw_status Command . Purpose . . . . . Syntax . . . . . . Description. . . . . Flags . . . . . . Output . . . . . . Examples . . . . . ssa_getdump Command . Purpose . . . . . Syntax . . . . . . Description. . . . . Flags . . . . . . Output . . . . . . ssaidentify Command . . Purpose . . . . . Syntax . . . . . . Description. . . . . Flags . . . . . . ssa_progress Command . Purpose . . . . . Syntax . . . . . . Description. . . . . Flags . . . . . . Output . . . . . . Examples . . . . .
Flags . . . Output . . . ssaxlate Command Purpose . . Syntax . . . Description. . Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 371 372 372 372 372 372 Chapter 17. SSA Service Aids . . . . . . . . . .
Federal Communications Commission (FCC) Statement . . . . . . Japanese Voluntary Control Council for Interference (VCCI) Statement . Korean Government Ministry of Communication (MOC) Statement . . New Zealand Compliance Statement . . . . . . . . . . . . International Electrotechnical Commission (IEC) Statement . . . . . Avis de conformité à la réglementation d’Industrie Canada . . . . . Industry Canada Compliance Statement . . . . . . . . . . . United Kingdom Telecommunications Requirements . . . . . . .
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. This book contains no danger notices. A caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury. This book contains two caution notices.
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. To follow the instructions in this book, you should be familiar with the basic operational procedures for a RISC system. What This Book Contains Part 1 of this book is mainly for the user.
| 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. | http://www.storage.ibm.com/hardsoft/products/ssa | Numbering Convention In this book: KB means 1 000 bytes. MB means 1 000 000 bytes.
Part 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 Plus Adapter, however, provides additional functions. In this book, the name “Advanced SerialRAID Adapter” is used both for the Advanced SerialRAID Adapter and for the Advanced SerialRAID Plus Adapter, unless otherwise stated.
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. These adapters provide support for two SSA loops. Each loop can contain a maximum of eight pairs of adapter connectors and a maximum of 48 disk drives. See also “Rules for SSA Loops” on page 22.
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. The SSA links must be configured as loops. Each loop is connected to a pair of connectors at the SSA adapter card.
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. If disk drives or other SSA adapters are connected to these connectors, either those disk drives or adapters are failing, or their SSA links are not active. Permanently on Both SSA links are active (normal operating condition). Slow Flash Only one SSA link is active.
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. Loops, Links, and Data Paths In the simplest SSA configuration, SSA devices are connected through two or more SSA links to an SSA adapter that is located in a using system. The devices, SSA links, and SSA adapter are configured in 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. Data can travel in either direction round the loop. The adapter can, therefore, get access to the devices 3 (disk drives in this example) through two data paths.
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. The adapter now uses the alternative path to some of the devices. In Figure 3, disk drive number 3 has failed. Disk drives 1 and 2 can communicate with the using system only through connector A1 of the SSA adapter.
Simple Loop — Two 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. Disk drive number 8 can communicate with the using system only through connector A2 of the SSA adapter. Disk drives 4, 5, and 6 are isolated from the SSA adapter.
One Loop with Two 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. Using System A1 A2 1 B1 B2 A1 A2 2 B1 B2 Disk Disk Disk Disk Disk Disk Disk Disk 16 15 14 13 12 11 10 9 Disk Disk Disk Disk Disk Disk Disk Disk 1 2 3 4 5 6 7 8 Figure 5.
One Loop with Two Adapters in Each of Two 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. Bypass Note: Your SSA Disk Subsystem, or SSA Disk Enclosure, might contain bypass cards.
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). In Figure 7, disk drives 13 through 16 have been connected between the SSA adapters in using system 1. If both adapters fail, or are held reset, but remain powered on, disk drives 1 through 12 can still communicate with using system 2.
Two 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.
Two Loops with Two 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 SSA Disk Drives Adapter Figure 9. Two Loops with Two 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. Adapter Adapter Adapter Adapter Adapter SSA Disk Drives Adapter Adapter Adapter Figure 10.
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 systems might lose access to disk drives if you: v Switch off more than one using system at a time v Switch off a using system when a disk drive has failed. Note: For more information about bypass cards, see the publications for your disk subsystems or enclosures.
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 that all the disk drives in all those using systems are configured, as follows: v If all the using systems are switched off (Micro Channel or PCI): 1. For each Micro Channel system: a. Set Secure mode on each using system. b. Switch on all the using systems. c.
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. These codes are displayed when the diagnostic programs isolate a problem. For information about the location codes that are used by the using system, see the Operator Guide for the using system.
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. Service actions are always related to physical disk drives. For this reason, errors that occur on SSA disk drives are always logged against the physical disk drive (pdisk).
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. The label on the side of a disk drive shows the full UID. The label on the front of a disk drive shows the serial number of the disk drive. The serial number is actually part of the UID.
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). v A maximum of one pair of adapter connectors can be connected in a particular SSA loop. v All member disk drives of an array must be on the same SSA loop. v A maximum of 48 SSA disk drives can be connected in a particular SSA loop.
Checking the Level of the Adapter Microcode If you need to check the level of the adapter microcode: 1. Type, 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. | 2. Find ROS Level and ID, for example, 5000. Chapter 2.
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. One Pair of Adapter Connectors in the Loop The following sequence enables you to determine the best relationship between the disk drives and the adapter on an SSA loop that contains only one pair of adapter connectors. 1.
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. 1. For each pair of connectors, identify all the data that the loop is to access. 2. For each pair of connectors, identify the data that the loop is to access most frequently. 3.
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. Most of the disk drives share data access with each other. 1. Determine which data is shared between the pairs of adapter connectors. 2. Assign this data to the disk drives that are equally spaced between the sharing 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. The advantages of this method are: | v System software can read the Physical Volume ID (PVID) from a reserved disk drive.
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. RAID technology stores data across groups of disk drives that are known as arrays. These arrays are contained in array subsystems, which can be configured with one or more arrays.
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. Member disk drives of a RAID-10 array can be configured to be in separate domains. Separate domains ensure that data remains available if, for example, a complete domain fails through loss of power.
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. Offline State A RAID-0 array enters Offline state when one or more member disk drives become missing. Read and write operations are not allowed. Chapter 3.
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. These definitions prevent operation on separate member disk drives of the array when the array becomes split, but separate systems can still access one of the member disk drives.
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. A flowchart for the RAID-5 array states is shown in Figure 15 on page 35. Good State A RAID-5 array is in the Good state when all the member disk drives of that array are present. Exposed State A RAID-5 array enters the Exposed state when a member disk drive becomes missing (logically or physically) from that array.
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. You 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. The array management software starts a rebuilding operation to synchronize the new disk drive with the data that is contained in the other disk drives of the array.
RAID-5 Array State Flowchart Array Good Disk is removed Disk fails Array Exposed Disk rejected Second disk fails or is removed Original disk replaced Y N N Write operation Array Offline Y New disk Array Degraded Array enabled for Hot Spare N Y Hot Spare available N Y Hot Spare swapped in Allow Write while Exposed Y N Array Rebuilding Write Op rejected Array Degraded (no protection) Figure 15. RAID-5 Array State Flowchart Chapter 3.
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. An important characteristic of RAID-10 is that the mirrored pairs can be located in different sites in different power domains. The availability of a RAID-10 array is, therefore, better than that of RAID-5 array.
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. Read and write operations can be performed on the array. The missing member disk drives are deconfigured so that they are permanently excluded from the array.
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. v SSA Adapter v SSA Disks v SSA RAID Arrays | | | | | | | | | | | | | Notes: 1. Although this book always refers to the smitty commands, you can use either the smitty command, or the smit command.
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. Type smitty and press Enter. The System Management menu is displayed. b. Select Devices. The Devices menu is displayed. c. Select SSA Adapters. 2. The SSA Adapters menu is displayed: SSA Adapters Move cursor to desired item and press Enter.
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. Type smitty and press Enter. The System Management menu is displayed. b. Select Devices. The Devices menu is displayed. c. Select SSA Disks. 2. The SSA Disks menu is displayed: SSA Disks Move cursor to desired item and press Enter.
4. The SSA Logical Disks menu is displayed: SSA Logical Disks Move cursor to desired item and press Enter.
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. Type smitty and press Enter. The System Management menu is displayed. b. Select Devices. The Devices menu is displayed. c. Select SSA RAID Arrays. 2. The SSA RAID Arrays menu is displayed: SSA RAID Arrays Move cursor to desired item and press Enter.
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. The pdisks of arrays can also be configured to hot spare pools.
Figure 16 shows an array that has its primary disk drives (pdisk2, pdisk3, pdisk10 and pdisk11) 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. Building 1 A D A P T E R pdisk1 (Spare) pdisk2 pdisk12 pdisk11 Building 2 pdisk3 pdisk10 pdisk4 (Spare) pdisk5 pdisk9 pdisk8 Primary Disks Figure 16.
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. Building 1 A D A P T E R Building 2 pdisk1 (Spare) pdisk2 (Failed) pdisk3 pdisk12 pdisk11 pdisk10 pdisk4 pdisk5 pdisk6 A D A P T E R Primary Disks pdisk9 pdisk8 pdisk7 Secondary Disks Figure 17.
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. A failure of a member disk drive in Pool A1 now causes pdisk1 to be selected as the hot spare disk drive.
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. The pools ensure that, if any one SSA enclosure fails completely, three disk drives are always available for each hdisk.
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. Enclosure-1 hdisk Pool A1 pdisk Enclosure-2 pdisk Spare pdisk Spare pdisk Spare Pool A2 pdisk Enclosure-3 Pool A3 pdisk Figure 20.
Figure 21 shows how a RAID-10 array can be protected against the complete failure of an SSA enclosure. Enclosure-1 Pool A1 hdisk1 Primary Disks hdisk2 Primary Disks spare Enclosure-2 Pool A2 hdisk1 Secondary Disks hdisk2 Secondary Disks spare Figure 21. Pools and Hdisks along Enclosures 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. v Pool zero is called A0 for hot spare disk drives that are on SSA loop A, and B0 for hot spare disk drives that are on SSA loop B. v Hot spare pool numbers are in the range A0 through A31 and B0 through B31.
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. If hot spare pool problems occur during normal operations, use the Service Request Number (SRN) that is generated by the diagnostics to guide your actions. To display the operating state of a hot spare pool: 1.
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. If you are not sure whether your disk drives are assigned correctly: a. Ensure that the required number of disk drives of the correct size are assigned as hot spare disk drives, or as array candidate disk drives (see “Changing the Use of Multiple SSA Physical Disks” on page 147). b.
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. If you did not intend to make such changes, and you correct them, the pool returns to its original state. If you did intend to make the changes: 1.
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. The ssaraid command allows you to create, delete, and manage your RAID arrays.
Installing and Configuring SSA RAID Arrays You 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. Notes: 1. Although this book always refers to the smitty commands, you can use either the smitty command, or the smit command. The procedures that you follow remain the same, whichever of the two commands you use.
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. Type smitty and press Enter. The System Management menu is displayed. b. Select Devices. The Devices menu is displayed. c. Select SSA RAID Arrays. 2. The SSA RAID Arrays menu is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SSA RAID Arrays Move cursor to desired item and press Enter.
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. Press Enter AFTER making all desired changes. [Entry Fields] ssa0 raid_0 SSA RAID Manager RAID Array Type * Member Disks Allow Page Splits Enable Fast-Write F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit F3=Cancel F7=Edit Enter=Do For the meanings of the fields, see page 66.
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. SSA RAID Manager RAID Array Type * Member Disks Strip Size (KB) Enable Use of Hot Spares Choose Hot Spare only from Preferred Pool Allow Page Splits Enable-Fast Write F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit F3=Cancel F7=Edit Enter=Do For the meanings of the fields, see page 66.
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 Type 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. The array must consist of disk drives that are in the same loop. Primary Disk The primary disk drive of a RAID-1 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 no for this option, a hot spare disk drive is selected, if available, 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. Enable Fast-Write Switches the fast-write cache on or off. This facility is not available on adapter cards that do not, or cannot, have a fast-write cache installed. 4.
6. Select the disk drives that you want in the array. You must select a minimum of: v Two disk drives if you are creating a RAID-0 array v One primary and one secondary disk drive if you are creating a RAID-1 array v Three disk drives if you are creating a RAID-5 array v Two primary and two secondary disk drives if you are creating a RAID-10 array Try to select disk drives of equal sizes.
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. You cannot delete arrays that do not have a corresponding hdisk. 1. For fast path, type smitty rmssaraid and press Enter. Otherwise, select Delete an SSA RAID Array from the SSA RAID Arrays menu. A list of arrays is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
3. A prompt is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
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. List All Defined SSA RAID Arrays -------------------------------------------------------------------------| SSA Physical Disk | | | | Move cursor to desired item and press Enter. Use arrow keys to scroll.
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. 2. A list of adapters is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
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. ssa1 Pool Components Spares 0 7 6 1 0 2 pool_A0 pool_A1 pool_B1 F1=Help F8=Image n=Find Next Configured F2=Refresh F9=Shell 1 1 2 Minimum Status 1 1 1 unused empty full F3=Cancel F10=Exit F6=Command /=Find The columns of information displayed on the screen have the following meanings: Pool The pool identifier.
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. critical The number of hot spare disk drives that are in the pool is less than the specified number of hot spare disk drives for that pool.
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. 2. A list of adapters is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
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 hdisk4 pdisk13 pdisk11 pdisk3 pdisk6 pdisk7 pdisk15 raid_10 04-02-REGY-06-P 04-02-REGY-08-P 04-02-REGY-05-P 04-02-REGY-03-P 04-02-REGY-01-P 04-02-REGY-07-P 18.2GB 9.2GB 9.2GB 9.2GB 9.2GB 18.
Status The status of the array member disk drive. Valid 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. | | | | | | | Note: The size of the member disk drive is not the physical size of the disk drive, but the size that the array manager assigns to it.
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. 2. A list of adapters is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | || | 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 Connected to a RAID Manager ------------------------------------------------------------------------| SSA Hot Spare Pools | | | | Move cursor to desired item and press F7. | | ONE OR MORE items can be selected.
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. Size The size of the array member disk drive. This value is useful to know, if you have assigned a hot spare disk drive to a pool, but the array member disk drive is too large to be protected by the hot spare disk drive. Status The status 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. Otherwise, select Add a Hot Spare Pool 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.
3. A list that shows Loop A or Loop B is displayed: SSA RAID Arrays Move cursor to desired item and press Enter.
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. You should normally set this field to the number of hot spare disk drives that you intend to assign to this pool. You can, however, set it to a lower number if you do not want to be alerted when a single hot spare disk drive has been used (see “Choosing the Error Threshold (Alarm) Level for a Hot Spare Pool” on page 51). 5.
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. 1. For fast path, type smitty chg_hsm_pool_adap and press Enter. Otherwise, select Change/Show/Delete a Hot Spare Pool from the SSA RAID Arrays menu. 2.
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 Connected to a RAID Manager ------------------------------------------------------------------------| SSA Hot Spare Pools | | | | Move cursor to desired item and press Enter.
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] ssa1 pool_B2 full 3 1 1 [] [] [1] SSA RAID Manager Spares Pool Status Components in Pool Hot Spares Previously Configured Hot Spares in Pool Components to Add Components to Remove Hot Spares Minimum F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit F3=Cancel F7=Edit Enter=Do + + # F4=List F8=Image v To add disk drives to the pool: 1.
Dealing with RAID Array Problems This part of the chapter describes how to solve problems that might occur on your SSA RAID arrays. You can get to the required SMIT menu by using fast path commands or by working through other menus. During problem determination, you can use any of the maintenance procedures described in Using Other Configuration Functions. A hot spare disk drive automatically replaces a failed or missing disk drive in a RAID array if: v The Enable Use of Hot Spares attribute is set to yes.
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. Type smitty and press Enter. The System Management menu is displayed. b. Select Devices. The Devices menu is displayed. c. Select SSA RAID Arrays. 2. The SSA RAID Arrays menu is displayed: SSA RAID Arrays Move cursor to desired item and press Enter.
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. If the disk drive cannot be accessed, however, it cannot be listed as a rejected disk. (A disk drive cannot be accessed if its Check light is on, or its Power light is off.
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 F1=Help F8=Image n=Find Next 08005AEA030D00D member F2=Refresh F9=Shell rejected F3=Cancel F10=Exit 2.3G Physical disk F6=Command /=Find 4. Check the list of rejected disk drives against other error reports to find out why the disk drive was rejected from the array. 5.
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. Press Enter AFTER making all desired changes. [Entry Fields] ssa0 SSA RAID Manager * Rejected Array Disks Flash Disk Identification Lights F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + + yes F3=Cancel F7=Edit Enter=Do F4=List F8=Image 9. Select yes in the Flash Disk Identification Lights field. 10.
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). Run system diagnostics to verify that the disk drive is working correctly.
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. [Entry Fields] ssa1 hdisk4 raid_10 00703784C540C0O SSA RAID Manager SSA RAID Array RAID Array Type Connection Address / Array Name * Disk To Remove * Disk To Add F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + + F3=Cancel F7=Edit Enter=Do F4=List F8=Image 6. Select Disk to Remove. 7.
Using Other Configuration Functions This part of the chapter describes the maintenance procedures that are available for your Advanced SerialRAID Adapter. You can use these procedures at any time. You can get to the required SMIT menu by using fast path commands or by working through other menus. Notes: 1. Although this book always refers to the smitty commands, you can use either the smitty command, or the smit command. The procedures that you follow remain the same, whichever of the two commands you use.
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. Type smitty and press Enter. The System Management menu is displayed. b. Select Devices. The Devices menu is displayed. c. Select SSA RAID Arrays. 2. The SSA RAID Arrays menu is displayed: SSA RAID Arrays Move cursor to desired item and press Enter.
– “Identifying the Disk Drives in an SSA RAID Array” on page 119 – “Identifying Hot Spare Disk Drives” on page 121 – “Identifying Rejected Array Disk Drives” on page 123 – “Identifying Array Candidate Disk Drives” on page 125 – “Identifying System Disk Drives” on page 127 – “Canceling all SSA Disk Drive Identifications” on page 129 v “Listing or Deleting Old RAID Arrays Recorded in an SSA RAID Manager” on page 130 – “Listing Old RAID Arrays Recorded in an SSA RAID Manager” on page 131 – “Deleting an Old RAI
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. A list of defined arrays is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
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. 2. A list of supported arrays is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
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. 2. A list of RAID managers is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
3. A list of arrays is displayed: COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. hdisk4 hdisk3 F1=Help F8=Image n=Find Next 09523173A02137K good 095231779F0737K good F2=Refresh F9=Shell 3.4G 3.4G F3=Cancel F10=Exit RAID-5 array RAID-5 array F6=Command /=Find 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. 2. The following information is displayed: SSA RAID Arrays Move cursor to desired item and press Enter.
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. hdisk3 hdisk4 F1=Help F8=Image n=Find Next Unsynced Parity Strips 0 0 F2=Refresh F9=Shell Unbuilt Data Strips 0 0 F3=Cancel F10=Exit F6=Command /=Find 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. Components Primary hdisk4 pdisk13 pdisk3 pdisk7 F1=Help F8=Image n=Find Next Secondary Status degraded good good degraded pdisk15 pdisk6 BlankReserved5Z F2=Refresh F9=Shell F3=Cancel F10=Exit F6=Command /=Find Status data is given for the array and for each mirrored pair of disk drives in the array.
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. rebuilding A failed member disk drive in a mirrored pair has been exchanged and data is rebuilding. offline Both member disk drives of a mirrored pair are missing or have failed. Chapter 6.
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. 2. The following information is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
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. b. Select List Disks in an SSA RAID Array. 2. A list of arrays is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
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 pdisk4 pdisk7 pdisk8 F1=Help F8=Image n=Find Next 110 0004AC5119E000D 08005AEA030D00D 08005AEA087A00D 08005AEA098100D F2=Refresh F9=Shell User’s Guide and Maintenance Information member member member member present present present not_present F3=Cancel F10=Exit 1.1G 2.3G 4.
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. b. Select List Hot Spares. 2. A list of adapters is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
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 pdisk5 F1=Help F8=Image n=Find Next 112 0004AC5119E000D spare 08005AEA030D00D spare F2=Refresh F9=Shell User’s Guide and Maintenance Information n/a n/a F3=Cancel F10=Exit 1.1G 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. b. Select List Rejected Array Disks. 2. A list of adapters is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
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 pdisk5 F1=Help F8=Image n=Find Next 114 0004AC5119E000D rejected n/a 08005AEA030D00D rejected n/a F2=Refresh F9=Shell User’s Guide and Maintenance Information F3=Cancel F10=Exit 1.1G 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. b. Select List Array Candidate Disks. 2. A list of adapters is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
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. pdisk3 pdisk5 F1=Help F8=Image n=Find Next 116 0004AC5119E000D free 08005AEA030D00D free F2=Refresh F9=Shell User’s Guide and Maintenance Information 1.1G 2.
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. | b. Select List System Disks. 2.
| 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. pdisk3 pdisk5 F1=Help F8=Image n=Find Next 118 0004AC5119E000D system 08005AEA030D00D system F2=Refresh F9=Shell User’s Guide and Maintenance Information 1.1G 2.
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. b. Select Identify Disks in an SSA RAID Array. 2. A list of arrays is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
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. Entry Fields ssa0 hdisk2 SSA RAID Manager SSA RAID Array * Member Disks Flash Disk Identification Lights F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + + yes F3=Cancel F7=Edit Enter=Do F4=List F8=Image 4. Select yes in the Flash Disk Identification Lights field. 5. Press the List key to list the disk drives. 6.
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. b. Select Identify Hot Spares. 2. A list of arrays is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
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] ssa0 SSA RAID Manager * Hot Spare Disks Flash Disk Identification Lights F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + + yes F3=Cancel F7=Edit Enter=Do F4=List F8=Image 4. Select yes in the Flash Disk Identification Lights field. 5. Press the List key to list the disk drives. 6.
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. b. Select Identify Rejected Array Disks. 2. A list of arrays is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
3. The following information is displayed: Identify Rejected Array Disks Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] ssa0 SSA RAID Manager * Rejected Array Disks Flash Disk Identification Lights F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + + yes F3=Cancel F7=Edit Enter=Do F4=List F8=Image 4. Select yes in the Flash Disk Identification Lights field. 5. Press the List key to list the disk drives. 6.
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. b. Select Identify Array Candidate Disks. 2. A list of adapters is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
3. The following information is displayed: Identify Array Candidate Disks Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] ssa0 SSA RAID Manager * Array Candidate Disks Flash Disk Identification Lights F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + + yes F3=Cancel F7=Edit Enter=Do F4=List F8=Image 4. Select yes in the Flash Disk Identification Lights field. 5. Press the List key to list the disk drives. 6.
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. | b. Select Identify System Disks. 2.
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] ssa0 SSA RAID Manager * System Disks Flash Disk Identification Lights F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + + yes F3=Cancel F7=Edit Enter=Do F4=List F8=Image 4. Select yes in the Flash Disk Identification Lights field. 5. Press the List key to list the disk drives.
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. 2. Select Cancel all SSA Disk Identifications. The Check lights of all identified disk drives stop flashing. Chapter 6.
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. The record must be deleted manually. This option allows you to list the serial numbers of such arrays, and to delete the records of those arrays from the SSA RAID manager. 1. For fast path, type smitty nvrssaraid and press Enter.
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. 2. Select List Old RAID Arrays Recorded in an SSA RAID Manager. 3. A list of RAID managers is displayed in a window: List/Delete Old RAID Arrays in an SSA RAID Manager Move cursor to desired item and press Enter.
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. [TOP] 0952314698B637K 09523146994837K 0952314699A437K 0952314699CE37K 095231469A9337K 095231469B6D37K 095231469C4537K 095231469CEE37K 095231469D7A37K 095231469E2C37K 095231469F7C37K 09523146A42637K 09523146A4B737K [MORE...
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. 2. Select Delete an Old RAID Array Recorded in an SSA RAID Manager. 3. A list of RAID managers is displayed in a window: List/Delete Old RAID Arrays in an SSA RAID Manager Move cursor to desired item and press Enter.
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. [Entry Fields] ssa0 SSA RAID Manager * Old SSA RAID Array Record to Delete F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit F3=Cancel F7=Edit Enter=Do F4=List F8=Image Press the List key to list the records. 5.
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. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | || | 2. A list of RAID managers is displayed in a window. 3.
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. [Entry Fields] ssa0 hdisk3 00243199986267K raid_5 good pdisk1 pdisk3 pdisk4 p> 3.
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. Otherwise, select Change Member Disks in an SSA RAID Array from the SSA RAID Arrays menu. 2.
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. 1. For fast path, type smitty redssaraid and press Enter. Otherwise: a. Select Change Member Disks in an SSA RAID Array from the SSA RAID Arrays menu. b. Select Remove a Disk from an SSA RAID Array. 2.
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. [Entry Fields] ssa0 hdisk3 095231779F0737K SSA RAID Manager SSA RAID Array Connection Address / Array Name * Disk to Remove F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + F3=Cancel F7=Edit Enter=Do F4=List F8=Image Press the List key to list the disk drives. 4.
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. When you install the replacement disk drive, all the data that was contained on the original disk drive is automatically written to the replacement disk drive. 1.
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. [Entry Fields] ssa0 hdisk3 09523177F0737K SSA RAID Manager SSA RAID Array Connection Address / Array Name * Disk to Add F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + F3=Cancel F7=Edit Enter=Do F4=List F8=Image Press the List key to list the disk drives. 4.
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. b. Select Swap Members of an SSA RAID Array. 2. A list of arrays is displayed in a window: Change Member Disks of an SSA RAID Array Move cursor to desired item and press Enter.
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. [Entry Fields] ssa0 hdisk3 09523173A02137K SSA RAID Manager SSA RAID Array Connection Address / Array Name * Disk To Remove * Disk To Add F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F10=Exit + + F3=Cancel F7=Edit Enter=Do F4=List F8=Image Select Disk to Remove, and press the List key. 4.
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. 2. A list of adapters is displayed in a window: | | | | | | | | | | | | | | | | | | | | | | | | | List/Identify SSA Physical Disks Move cursor to desired item and press Enter.
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. Use arrow keys to scroll. | | | | # SSA physical disks which are members of arrays. | | pdisk0 00022123DFHC00D member n/a 4.5G Physical d | | pdisk1 0004AC5119E000D member n/a 1.
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.) | The following screen is displayed for the disk drives that you have chosen: | | | | | | | | | | | | | | | | | | | | | | | | | Change Use of Multiple SSA Physical Disks Type or select values in entry fields.
| | Chapter 7. Copying Data from Arrays and from Volume Groups | | | | | | When disk drives are configured through the Logical Volume Manager for mirroring, you can use the Split Copy function to create a copy of a logical volume. You can then save that copy on a tape or other medium for backup purposes. When disk drives are configured as members of a RAID-1 or RAID-10 array, a similar function, called 3-Way Copy, is available. This chapter describes the 3-Way Copy function, and how it can be used.
| | | | 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: | | | | | | Using the ssaraid Command to Create a RAID-Copy Array from a RAID-1 or RAID-10 Array v Using the ssaraid command from the command line v Using SMIT v Using the ssa_make_copy command (the recommended method) This section describes how to use the ssaraid command to create RAID-copy arrays.
| | | | | 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. Type: ssaraid -C -l ssa2 -t raid_copy -s | | | 000629CD8A3900D -r hdisk5 A message is displayed; for example: 185439188B4F4CT created 000629CD8A3900D changed | | | | Your RAID-copy array is 185439188B4F4CT. 3. Couple the RAID-Copy array to the parent RAID 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. To check whether the copy operation has completed, type: ssaraid -I -l ssa2 -n hdisk5 | | | | | | | | While the copy operation is running, the following information is included in the displayed data: | | When copy_status changes from copying to good, the copy operation has completed.
| | | | | 8. The newly created RAID-Copy array is created as a free disk drive. You 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. b. If you now give the cfgmgr command, the RAID-Copy array is configured, and is given the next available hdisk name; for example, hdisk6.
| | | | | | 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 “Using the ssaraid Command to Create a RAID-Copy Array from a RAID-1 or RAID-10 Array” on page 151) are particularly suitable if you are not using Logical Volume Manager LVM). For more details about the SMIT menus, see “SMIT Menus for 3-Way Copy Operations” on page 172.
| | 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.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | || | | | 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. To check whether the copy operation has completed: a. Select Array Copy Services. b. Select List all copy candidates.
| | | | | | | | | | | | | | | | | | 6. To 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. When the array is uncoupled, a new hdisk is created. This hdisk contains a copy of the data that was on the parent array when the RAID-Copy array was uncoupled.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. Figure 22. A Volume Group the Contains One Physical Volume The ssa_make_copy command checks whether the hdisk is either a RAID-1 or a RAID-10 array. If the array is neither of these types, the command displays a warning, then stops.
| | | | | 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). | | | | Figure 24.
| | ssa_make_copy Command | | Purpose | | | | | | | | | | | | | | | | | | | | | | | Syntax | | | | | | | | | | | Description | | | | | | | To create a RAID-Copy array from a RAID-1 or RAID-10 array.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | c. If the dump logical volume and the boot logical volume are copied, a warning is displayed. You 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. 2.
| | | -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. For example, the copy of the original logical volume /lv001 is named /fslv001. | -I Provides information. | | | | | | | | | | | -e | -E filename Calls the external trigger.
| | | Example 1: Copying a Complete Volume Group In this example, you are copying a complete volume group from the parent array to the RAID-Copy array. | | | To copy a complete volume group, give the commands: ssa_make_copy -P -v vgname ssa_make_copy -v vgname | | | | | | | | | | Figure 25. Copying a Complete Volume Group Figure 25 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.
| | | | | | Example 2: Copying One Logical Volume In this example, you are copying only one logical volume (-lv B) from the parent array to the RAID-Copy array. To copy one logical volume, give the commands: ssa_make_copy -P -l lv_B ssa_make_copy -l lv_B | | | | | | | | | | | | | | | | Figure 26. Copying One Logical Volume Figure 26 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.
| | | | | Example 3: Copying One Logical Volume by Logical Volume 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. You can use either the logical volume name (lv_A), or the FS name (data fs_1).
| | | | | | | | | Figure 27. Copying One Logical Volume or Copying by FS Name (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. | Chapter 7.
| | | | | Example 4: Copying One Logical Volume by Logical Volume 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. You can use either the logical volume name (lv_C), or the FS name (data_fs2).
| | | | | | | | | | | | | | | | | Example 4: Copying a Complete Volume 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. 1. On the original using system, give the commands: ssa_make_copy -P -v vgname ssa_make_copy -U -v vgname A message is displayed; for example: Copy Array hdiskx 014639AB30DC0T Uncouple completed successfully 2. On the using system where you want to recreate the copy: a.
| | | | | | | | | | | | | | | | Example 5: Running an Automatic Copy of a Volume Group 1. Prepare a volume group for copying: a. Give the command: ssa_make_copy -P -v vgname b. Wait for the copy to complete. c. Wait for the external trigger to be created. 2. Uncouple the volume group: Give the command: ssa_make_copy -U -v vgname 3. Recreate the volume group: Give the command: ssa_make_copy -v vgname 4. Either delete the copy volume group and destroy the RAID-Copy array: a.
| | ssa_delete_copy Command | | Purpose | | Syntax | Flags To delete a RAID-Copy array after it has been backed up. ssa_delete_copy -v vgname | -p pvname -A/-C [-f] | -A Deletes a copy and its RAID-Copy arrays. | -C Deletes a copy and couples the RAID-Copy to its original parents. | | -f If the specified volume group is varied off, this flag forces the volume group to be exported.
| | SMIT Menus for 3-Way Copy Operations | | | This section describes the SMIT menus that are related to the 3-Way 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 | | | | | | | | | | | | | | | | | | | | | | | | | || SSA RAID Arrays 1. For fast path access to the SSA RAID Array SMIT menu, type smitty ssaraid and press Enter. Otherwise: a. Type smitty and press Enter. b.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | || 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. Note: Array Copy Services are designed to be run from shell scripts. These SMIT menus are intended as an aid to shell script development and as a problem determination tool. Array Copy Services Move cursor to desired item and press Enter.
| | | | 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. If you select a RAID array that has a copy status of good, the copy is uncoupled from its parent, and a new array is created. The new array uses the next available hdisk name.
| | Prepare a Copy | Otherwise, select Prepare a Copy from the Array Copy Services menu. | The Prepare a Copy menu is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | || For fast path, type smitty copy_pre_array and press Enter. 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 | | | Secondary Each coupled disk drive is assigned to the hot spare pool to which the Secondary disk drive that it is copying is assigned.
| | Uncouple a Volume Group, Logical Volumes, or Filesystems Copy | | Otherwise, select Uncouple a Volume Group, Logical Volumes, or Filesystems Copy from the Array Copy Services menu. | | The Uncouple a Volume Group, Logical Volumes or Filesystems Copy menu is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | || For fast path, type smitty copy_unvglvfs and press Enter. Uncouple a Volume Group, Logical Volumes or Filesystems Copy Type or select values in entry fields.
| | | 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 | Otherwise, select List All Copy Candidates from the Array Copy Services menu. | The following information is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For fast path, type smitty copy_lstcopycand and press Enter. 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. If missing disk drives are replaced or exchanged for new disk drives, the copy operation continues.
| | List All Uncoupled Copies | Otherwise, select List All Uncoupled Copies from the Array Copy Services menu. | The following information is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | || For fast path, type smitty copy_lstcopies and press Enter. COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
| | List All Uncoupled Volume Groups | | Otherwise, select List All Uncoupled Volume Groups from the Array Copy Services menu. | The following information is displayed: For fast path, type smitty copy_lstunvg and press Enter. | | | | | | | | | | | | | | | | | | | | | | | || COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
| | Delete a RAID Array Copy | Otherwise, select Delete a RAID Array Copy from the Array Copy Services menu. | The following information is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | || For fast path, type smitty copy_delcopy and press Enter. Array Copy Services Move cursor to desired item and press Enter.
| | Delete a Volume Group, Logical Volumes, or Filesystems Copy | | Otherwise, select Delete a Volume Group, Logical Volumes, or Filesystems Copy from the Array Copy Services menu. | The following information is displayed: For fast path, type smitty copy_delvglvfs and press Enter. | | | | | | | | | | | | | | | | | | | | | | | | | | | Array Copy Services Move cursor to desired item and press Enter.
| The meanings of the fields are: | | Volume 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. | | | Delete The volume group name is removed, and pdisks that are in each array in the volume group change to free disk drives. Data on the volume group is no longer accessible.
| | 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. Change/Show Attributes of an SSA RAID Array The following information is displayed for RAID-1 or RAID-10 arrays: | | | | | | | | | | | | | | | | | | | | | | | | | | | Change/Show Attributes of an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
| | | | | 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. | | For fields that are not defined here, see “Changing or Showing the Attributes of an SSA RAID Array” on page 135.
| | 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. | The following information is displayed for RAID-Copy arrays: | | | | | | | | | | | | | | | | | | | | | | | | | || COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
| | 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. | The following information is displayed for RAID arrays that have coupled disk drives: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Identify Disks in an SSA RAID Array Type or select values in entry fields. Press Enter AFTER making all desired changes.
| | 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. | | When the List key is pressed for the Disk to Remove option, the following pop-up menu is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove a Disk From an SSA RAID Array Type or select values in entry fields.
| | 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. | | When the List key is pressed for the Disk to Remove option, the following pop-up menu is displayed: | | | | | | | | | | | | | | | | | | | | | | | | | | | Swap Members of an SSA RAID Array Type or select values in entry fields.
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. Configuration of RAID-1 and RAID-10 Arrays RAID-1 and RAID-10 arrays hold data on mirrored pairs of disk drives; that is, the two disk drives of a particular pair contain the same data. If either disk drive fails, the data is still available.
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. Three types of array management problems can cause an array to be in the Offline state to the using system: v One half of the array is not present. v The adapter is not known to the remaining half of the array.
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. The array remains online, but in the Exposed state until one of the following occurs: v The missing primary disk drive becomes available again before a write operation to the array occurs.
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. The array remains online, but in the Exposed state until one of the following occurs: v The missing primary disk drive becomes available again before a write operation to the array occurs.
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. The array remains in the Offline state on both systems until either of the following occurs: v The primary disk drive becomes available. v The Split Array Resolution flag is set to Secondary. Split Array Resolution = Primary System 2 SSA Adapter Secondary 1 Figure 31.
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. Split Array Resolution Split Array Resolution = Primary = Primary System 1 System 2 SSA Adapter SSA Adapter Primary 1 Secondary 1 Primary 2 Secondary 2 Figure 32. System 1 Split from System 2 On system 1, the array is in the Exposed or the Degraded state.
Normal Reconnection: When the systems are reconnected, the secondary disk drives are resynchronized with the primary disk drives, as shown in Figure 33. Split Array Resolution Split Array Resolution = Primary = Primary System 1 SSA Adapter System 2 0011 0011 1111 0000 0011 0011 1111 1111 Primary 1 Secondary 1 0000 1111 1010 1010 0000 1111 1010 1010 Primary 2 Secondary 2 Figure 33. Reconnection of a Split Array The array enters the Good state for both systems.
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. Split Array Resolution = Primary System 1 System 2 SSA Adapter SSA Adapter Primary 1 Secondary 1 Figure 34. RAID-1 Disk Drive Failure 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. The array is in the Exposed or Degraded state.
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 Offline state. If you set Split Array Resolution to Secondary, the array goes into the Good state. Split Array Resolution = Primary System 2 SSA Adapter Secondary 1 Figure 35. RAID-1 Failure of a Host System and a Primary Disk Drive 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. To maintain data consistency, SSA RAID-1 and RAID-10 arrays keep a record of the adapters to which they are connected. If exactly one half of the array is connected to a different adapter, the array remains in the Offline state unless you take specific action to make the array available.
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. System 1 System 2 SSA Adapter A SSA Adapter B Primary 1 Secondary 1 Primary 2 Secondary 2 System 3 System 4 SSA Adapter C SSA Adapter D Primary 1 Primary 2 Figure 38.
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. Array is Offline because the Split and Join Procedure Was Not Performed Correctly When this condition occurs, the host system generates SRN 48760.
RAID-10 Array Split Figure 39 shows a RAID-10 array that has been split into halves. Split Array Resolution Split Array Resolution = Primary = Primary System 1 System 2 SSA Adapter SSA Adapter Primary 1 Secondary 1 Primary 2 Secondary 2 Figure 39. Forcing Access on a RAID-10 Array 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. Split Array Resolution Split Array Resolution = Primary = Primary System 2 System 1 SSA Adapter 0011 1110 1010 0000 ? Primary 1 1110 0001 1111 0100 Primary 2 1111 0000 0000 0001 SSA Adapter Secondary 1 ? 0001 0101 0101 1110 Secondary 2 Figure 40. Reconnecting an Unsynchronized Array Each half of the array contains different data, but no indication is given to which data is valid.
208 User’s Guide and Maintenance Information
Chapter 9. Using the SSA Spare Tool The SSA Spare Tool helps you to manage your SSA networks when Logical Volume Manager (LVM) mirrored volume groups are used. It works with the LVM to identify stale partitions or missing physical volumes in LVM mirrored volume groups. If the SSA Spare Tool finds any stale partitions or missing physical volumes: v It automatically resynchronizes the stale partition if no replacement hardware is needed.
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. This battery can maintain data in the write cache for seven days after power has been removed from the adapter card.
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. Also, some menus might be displayed slightly differently from those 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. Type smitty and press Enter. The System Management menu is displayed. b. Select Devices. The Devices menu is displayed. c. Select SSA Disks. The SSA Disks menu is displayed. d. Select SSA Logical Disks. 2. The SSA Logical Disks menu is displayed: SSA Logical Disks Move cursor to desired item and press Enter.
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. Type smitty chgssardsk and press Enter. b. From the menu displayed, select the logical disk that you want to change. Otherwise: a. Select Change/Show Characteristics of an SSA Logical Disk from the SSA Logical Disks menu. b.
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. You can select multiple devices from the list that this option displays. The displayed list contains also offline and broken cache items, so that you can delete them. 1.
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) Type: rmdev -l hdiskname -d 2) Run cfgmgr to reconfigure the new hdisk. b. The fast-write function is disabled only if no data for your selected devices is present in the fast-write cache.
Bypassing the Cache in a One-Way 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. By default , fast-write operations continue. 1. For fast-path access to the Change/Show Characteristics of an SSA Logical Disk menu: a. Type smitty chgssardsk and press Enter. b.
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. These problems are indicated by any of the following Service Request Numbers (SRNs): v 42521 v 42524 v 42525 If any of these SRNs occurs, do the following actions: 1. Go to “Service Request Numbers (SRNs)” on page 411, and find the SRN. 2.
v To 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. To list these devices, type: ssaraid -l ssaX -Iz -a state=no_cache where X is the adapter number. Use the recovery procedure that is described for SRN 42521. You must recover all the devices that are listed.
Chapter 11. 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. For these operations, you have no need to inspect the system error log, or to attempt to analyze the contents of the log.
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. The Error ID is a numeric identifier for the Error Label. Table 2 shows the error labels that SSA subsystems use. | Table 2.
Table 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. It is possible, however, that the failure was detected because the disk drive was unavailable for a short period. Run the error log analysis to determine whether the disk drive should be exchanged for a new one.
Table 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. Link errors are normally associated with some other failure on the SSA loop. Link errors might be logged when other devices on the loop are switched on or off, or when cables or devices are disconnected during service activity.
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 is known, you can use either of the following methods to find that cause: v Use the Configuration Verification service aid, or give the ssaxlate -l hdisk command, to determine which pdisks are associated with the hdisk. v Give the ssa_ela -l hdisk command to run error log analysis.
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 DISK_ERR4 SSA_DISK_ERR1 SSA_DISK_ERR2 SSA_DISK_ERR3 SSA_DISK_ERR4 SCSI sense data consists of 32 bytes of data. See “Error Log Analysis” on page 229 to find out how this data is used.
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. Some faults, however, can cause a 40-MB-per-second link to run at only 20 MB per second. The run_ssa_link_speed program detects when a pair of high-speed nodes are running at low speed.
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. Because a particular error need be logged only a defined number of times for the automatic error log analysis to determine that service activity is needed, the device driver stops the repeated logging of the same error.
Figure 41. Example of an Open Link Error 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. The actual threshold values that are used for any given error type are regularly reviewed, and might change with any new version of the device driver.
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. The analysis uses the detailed data that is logged with each error. If service activity is needed, an SRN is produced.
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. v DISK_ERR1 or DISK_ERR4 type errors (media errors) generate an SRN if more than a predetermined number of these errors exist in the log. The SRN is 1XXXX, where XXXX is the contents of bytes 20 and 21 of the detail data.
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. The utility is ssa_ela. It can perform SSA error log analysis on: v All SSA devices v A selected hdisk v A selected pdisk v A selected adapter v Any of the above items for a history period of up to seven days See “ssa_ela Command” on page 353 for details of how to use the utility.
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. v Regularly view the mail messages or OPMSGs that are in the error log, to determine whether the automatic error log analysis has detected any errors.
234 User’s Guide and Maintenance Information
Chapter 12. Using the SSA Command Line Interface for RAID Configurations You 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. The Command Line Interface includes a README file that explains the syntax for the ssaraid command. The README file is located at: /usr/lpp/devices.ssa.IBM_raid/ssaraid.
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. – List all types of object. Notes about the ssaraid Command: 1. You can specify RAID object names (arrays or member disk drives) as either the 15-character connection location, or as the device name. | The preferred name is the 15-character connection location. This name is the same as the SSA serial number for the device. 2.
Command Syntax | | | | | | | | | | | ssaraid ssaraid ssaraid ssaraid ssaraid ssaraid ssaraid ssaraid ssaraid -? -M [-o] [-l RaidManager] -l RaidManager [-n Name [-m|-p|-x|-e] | -t ObjectType [-r Name] [-c]] -I -l RaidManager [-n Name [-m|-p|-x|-e] | -t ObjectType [-r Name] [-c]] [-a Attribute=Value]...[-o|-z[-h] | -S[-o]] -C -l RaidManager -t CreateType -s Member [Member]... [-a Attribute=Value]...
Options You can use the following options with the ssaraid command: Option -? -A -C -D -H -I -M -S -Ya -Yc -Yo -a -c -d -e -h -i -k -l -m -n -o -p -r -s -t -u -x -z | | | | | Description Print a short usage message. Perform an action on an object. Create an object. Delete an object. Change an object. Report information on an object. List all the available SSA RAID managers that are on the system. Show the hot spare pool information for an SSA RAID array. List all array types. List all create types.
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: To Create a RAID-0 Array This example shows how to use three SSA physical disks to create a RAID-0 array. The attributes of the disks are all set to their default values.
Example 3: To 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. Type the command: > ssaraid -C -l ssa0 -t raid_5 -s pdisk0 pdisk1 pdisk2 -d where: -C specifies that this operation is a create operation. -l ssa0 specifies that RAID Manager ssa0 is to be used. -t raid_5 specifies that a RAID-5 array object is to be created. -s pdisk...
Example 5: To 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. The attributes of the disks are all set to their default values. Type the command: > ssaraid -C -l ssa0 -t spare_pool -n pool_B1 -s pdisk0 pdisk3 where: -C specifies that this operation is a create operation. -l ssa0 specifies that RAID Manager ssa0 is to be used. -t spare_pool specifies that a spare pool is to be created.
Example 7: To 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. Type the command: > ssaraid -H -l ssa0 -n hdisk5 -a spare=false where: -H specifies that this operation is a change operation. -n hdisk5 specifies that the object hdisk5 is about to be changed.
Example 9: To Make a New System Disk | This example shows how use a single SSA disk to make a new system disk. Type 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. | -n pdiskspecifies the pdisk that is to be changed to a system disk. -a use specifies the new use of the pdisk. | -d specifies that a system disk is to be attached to the new array.
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 Drive Change attributes v Action attributes RAID Arrays Creation and Change Attributes This section describes the creation and change attributes that you can use for: v All RAID arrays v RAID-1, RAID-5, and RAID-10 arrays only v RAID-1 and RAID-10 arrays only v RAID-5 arrays only v RAID-10 arrays only Creatio
| | 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. With the attribute set to false: If the partner fast-write cache becomes not available, fast-write operations to this disk drive continue.
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. If another disk drive in the array fails, or the power fails during a write operation, data might be lost. While the array is in the Degraded state, however, operations to the array continue.
Creation and Change Attributes for RAID-1 and RAID-10 Arrays Only You can specify the following attributes with the -a option when you are using the ssaraid command with the -C or -H option to create or change a RAID-1 or RAID-10 array: | split_resolution=primary/secondary (default=primary) This attribute selects the copy of the data that is to remain available if the primary disk drive is completely separated from the secondary disk drive.
Creation and Change Attribute for RAID-5 Arrays Only | You 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_max_length (default=128 x (n-1), where n is the number of member disk drives in the array) This attribute sets the maximum size, in blocks, of write operations to the cache.
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 You 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. If you specify also the -d option, a corresponding hdisk device is created for the physical disk drive.
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. force=yes/no If a disk 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.
| | | | Couple Action Attributes (RAID-1 and RAID-10 Only) You 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. | | | | raid_copy=copy This attribute specifies the name that you have given to the existing RAID copy that you are going to use. The RAID copy must not be attached to any logical disk.
Return Codes | Code 0 1 2 3 4 5 6 7 8 9 10 11 12 100 101 102 103 104 Description Successful. Some changes made, but finally not successful. General problem accessing the object data manager (ODM). Specified object (file, record, ODM object) not found. Heap allocation failed. Open/ioctl failure for RAID manager. Bad Transaction result. Array already known to cfgmgr. System call failed. Internal logic error. Method not found, not executable, or not correct. Problem communicating with back-end method.
254 User’s Guide and Maintenance Information
Chapter 13. Using the Programming Interface SSA Subsystem Overview Device Drivers Two 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. The SSA disk device driver is an example of an SSA head device driver.
Interface between the SSA Adapter Device Driver and Head Device Driver To 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. 2. Calls the fp_ioctl kernel service to issue the SSA_GET_ENTRY_POINT operation to the opened adapter. 3. Calls the function SSA_Ipn_Directive whose address was returned by the ioctl operation.
SSA Adapter Device Driver Purpose To provide support for the SSA adapter. Syntax #include /usr/include/sys/ssa.h #include /usr/include/sys/devinfo.h Description The /dev/ssan special files provide an interface that allows client application programs to access SSA adapters and the SSA devices that are connected to those adapters. Multiple-head device drivers and application programs can all access a particular SSA adapter and its connected devices at the same time.
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. The daemon holds the adapter device driver open although the operating system might not be using that adapter device driver at the time.
You 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. Summary of SSA Error Conditions If an open or ioctl subroutine that has been issued to an SSA adapter fails, the subroutine returns -1, and the global variable errno is set to a value from the file /usr/include/sys/errno.h.
Files /dev/ssa0, /dev/ssa1,..., /dev/ssan Provide an interface to allow SSA head device drivers to access SSA devices or adapters.
IOCINFO (Device Information) SSA Adapter Device Driver ioctl Operation Purpose To 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.h header file. The caller supplies the address to an area that is of the type struct devinfo. This area is in the arg parameter to the IOCINFO operation. The device-type field for this component is DD_BUS; the subtype is DS_SDA.
SSA_TRANSACTION SSA Adapter Device Driver ioctl Operation Purpose To 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. IPN is the language that is used to communicate with the SSA adapter. The caller must be root, or have an effective user ID of root, to issue this operation. IPN is described in theTechnical Reference for the 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. It is for use only by configuration methods and diagnostics software. Use of this interface might result in system hangs, system crashes, system corruption, or undetected data loss.
SSA_GET_ENTRY_POINT SSA Adapter Device Driver ioctl Operation Purpose To 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. The address that is supplied is valid only while the calling kernel extension holds an open file descriptor for the SSA adapter device driver.
SSA Adapter Device Driver Direct Call Entry Point Purpose To 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. See SSA_GET_ENTRY_POINT SSA adapter ioctl operation. Description The entry point address is the address that is returned in EntryPoint by the SSA_GET_ENTRY_POINT ioctl operation.
ssadisk SSA Disk Device Driver Purpose To provide support for Serial Storage Architecture (SSA) disk drives. Syntax #include #include #include Configuration Issues SSA Logical Disks, SSA Physical Disks, and SSA RAID Arrays | | | | | | Serial Storage Architecture (SSA) disk drives are represented in the operating system as SSA logical disks (hdisk0, hdisk1.....hdiskN) and SSA physical disks (pdisk0,pdisk1.....pdiskN).
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. If an adapter fails or the disk drive cannot be accessed from the original adapter, the SSA disk device driver switches to the alternative adapter without returning an error to any working application.
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-Initiator/RAID EL Adapter, and the Advanced SerialRAID Adapter can reserve to a node number rather than to an adapter (see “Reserving Disk Drives” on page 27).
Using mkdev to Configure a Physical Disk To use mkdev to configure an SSA physical disk, specify the following information: Parent ssar Class pdisk Subclass ssar Type You can list the types by typing: lsdev -P -c pdisk -s ssar ConnectionLocation 15-character unique identifier of the disk drive. You can determine the unique identifier in three ways: v If the disk drive is already defined, you can use the lsdev command to determine the unique identity, as follows: 1.
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. You 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. primary_adapter Specifies whether adapter_a or adapter_b is to be the primary adapter for this device.
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. For applications that perform very long sequential write operations, performance improves when data is written in blocks of 64 KB multiplied by (n-1), where n is the number of disks in the array. For example, if the array contains six member disks, the data would be written in blocks of 64 KB x 5.
secondary path, if one exists. You 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. You cannot specify this flag and the SSADISK_SECONDARY flag together. SSADISK_SECONDARY Opens the device using the secondary adapter as the path to the device. As a result of hardware errors, the device driver might automatically switch to the primary path, if one exists.
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. You cannot specify this flag and the SSADISK_SCSIMODE flag together. SSADISK_SCSIMODE Opens an SSA physical disk in SCSI passthrough mode. This action allows SSADISK_IOCTL_SCSI ioctls to be issued to the physical disk. This flag has support only for SSA physical disk drives.
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. EFAULT Illegal user address. EINVAL One of the following circumstances has occurred: v The read or write subroutine supplied an nbyte parameter that is not an even multiple of the block size. v The data buffer length exceeded the maximum length that is defined in the devinfo structure for an ioctl subroutine operation.
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 To 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.h header file. The caller supplies the address to an area of type struct devinfo in the arg parameter to the IOCINFO operation. The device-type field for this component is DD_SCDISK; the subtype is DS_PV.
SSADISK_ISAL_CMD (ISAL Command) SSA Disk Device Driver ioctl Operation Purpose To 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 ISAL command set is described in the Technical Reference for the adapter.
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. result Contains the Independent Packet Network (IPN) result word that is returned by IPN for the command. The word contains values from the /usr/include/ipn/ipntra.h file. A non-zero value indicates an error. u0.isal.
Files /dev/pdisk0, /dev/pdisk1, ..., /dev/pdiskn Provide an interface to allow SSA device drivers to access SSA physical disk drives. /dev/hdisk0, /dev/hdisk1,..., /dev/hdiskn 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 To 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. The ISAL command set is described in the Technical Reference for the adapter.
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. Note: Structures are provided in the /usr/include/ipn/ipnsal.h file. This file can be used to format the contents of the parameter buffer for the various commands.
SSADISK_SCSI_CMD (SCSI Command) SSA Disk Device Driver ioctl Operation Purpose To 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. Description The SSADISK_SCSI_CMD operation allows the caller to issue an SSA-SCSI command to a selected physical disk. The caller must be root, or have an effective user ID of root, to issue this ioctl.
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. See the relevant hardware documentation to determine what CDBs are valid for a particular SSA physical disk. Return Values If the command was successfully sent to the adapter card, this operation returns a value of 0.
SSADISK_LIST_PDISKS SSA Disk Device Driver ioctl Operation Purpose To 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). The operation returns a list of the SSA physical disks (pdisks) that make up the specified logical disk drive. The arg parameter for the SSADISK_LIST_PDISKS operation is the address of an ssadisk_ioctl_parms structure.
Return Values 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. ENOMEN The device driver was unable to allocate or pin enough memory to complete the operation. Files /dev/pdisk0, /dev/pdisk1, ..., /dev/pdiskn Provide an interface to allow SSA device drivers to access SSA physical disks.
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. The operating system has a concurrent mode interface to handle the sending and receiving of messages.
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 EINVAL if any of the following is true: v The top kernel extension did not perform a DD_CONC_REGISTER operation. v The conc_cmd pointer is null. v The devno field in the conc_cmd structure is not valid. v The cmd_op field of the conc_cmd structure is not one of the four valid values that were previously listed.
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. The cmd_op, message_code, and devno fields are zero. DD_CONC_UNLOCK The DD_CONC_UNLOCK device driver entry point has completed.
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. Each disk drive has an access list that is independent of the access lists for the other disk drives. Fencing is a function that is provided by the hardware and manipulated by hardware commands.
SSADISK_FORCED_OPEN to the openx subroutine, the reservation is broken, but the open fails with errno set to ENOCONNECT. To 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. SSA Target Mode The SSA Target-Mode interface (TMSSA) provides node-to-node communication through the SSA interface.
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. The TMSSA uses either of two methods to read and write data: v The blocking method, which waits until the I/O is complete or an error occurs before it returns control to you. v The nonblocking method, which returns control to you immediately.
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. Communication is needed only for the write operation.
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 Target Mode SSA Target Mode does not attempt to manage the data transfer between devices. It does, however, take action if buffers become full, and it ensures that read operations can read data from only one write operation.
SSA tmssa Device Driver Purpose To 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.h #include /usr/include/sys/tmssa.h Description The Serial Storage Architecture (SSA) target-mode device driver provides an interface to allow using-system to using-system data transfer by using an SSA interface.
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. Configuration Information When tmssan is configured (where n is the remote node number), the tmssan.im and tmssan.tm special files are both created.
EINVAL 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. ENOMEM The SSA device does not have enough memory resources. close Subroutine The close subroutine deallocates resources that are local to the target device driver for the target or initiator device. No commands are sent to the device as a result of running the close subroutine.
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. The target-mode device driver receives the signal and ends the current read subroutine.
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. If the device is opened with the O_NDELAY flag set, and the write request is for a length that is greater than the total buffer size of the device, the write request fails. The errno global variable is set to EINVAL.
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 TMCHGIMPARM operation. The actual period that elapses before a time-out occurs can be up to 10 seconds longer than the calculated value, because it is related to the operation of the hardware at the time of the write operation. A time-out value of zero means that no time-out occurs.
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.h file. TMCHGIMPARM Allows the caller to change some parameters that are used by the target mode device driver for a particular device instance.
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. Asynchronous notification of the POLLIN event occurs when received data is available. This notification occurs only if the select event POLLSYNC was not set.
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. These types of errors are handled as temporary errors.
tmssa Special File Purpose To 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. You can access the data transfer functions through character special files that are named dev/tmssann.xx, where nn is the node number of the node with which you are communicating.
IOCINFO (Device Information) tmssa Device Driver ioctl Operation Purpose To 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. This structure is defined in the /usr/include/sys/devinfo.h file. The SCSI target-mode union is used for this as follows: Initiator-Device buf_size Size of transmit buffer.
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. flags Set to zero. devsubtype DS_TM.
TMIOSTAT (Status) tmssa Device Driver ioctl Operation Purpose To 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. Because a nonblocking write operation might still be running, you must ensure that the status information applies to a particular write operation. The tm_get_stat structure in the /usr/include/sys/tmscsi.
TMCHGIMPARM (Change Parameters) tmssa Device Driver ioctl Operation Purpose To 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. It is allowed only for the initiator-mode device. The arg parameter to the TMCHGIMPARM operation contains the address of the tm_chg_im_parm structure that is defined in the /usr/include/sys/tmscsi.h file.
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. This option is allowed only for blocking-type write operations. Chapter 13.
310 User’s Guide and Maintenance Information
Part 2.
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. A README sheet of installation instructions is also supplied. 2. Install the adapter into a slot in the using system (see the Installation and Service Guide for the using system). 3.
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. This shell script searches for SSA enclosures that provide support for SCSI Enclosure Services (SES).
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. You can determine the disk drive microcode level by using the Display/Download Disk Drive Microcode SSA service aid (see “Display/Download Disk Drive Microcode Service Aid” on page 393).
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. FRU number The part number of the adapter card field-replaceable unit (FRU). Serial number The serial number of the adapter card. Engineering change level The engineering change level of the adapter card.
Adapter Power-On Self-Tests (POSTs) Power-on self-tests (POSTs) 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. Some POST failures cause the adapter to become unavailable to the using system.
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.
4. A prompt is displayed in a window: SSA RAID Arrays Move cursor to desired item and press Enter.
7. Attention: You 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. 8. A list of arrays is displayed in a window: Change Member Disks in an SSA RAID Array Move cursor to desired item and press Enter.
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. Entry Fields ssa0 hdisk3 095231779F0737K SSA RAID Manager SSA RAID Array Connection Address / Array Name * Disk to Remove F1=Help F5=Reset F9=Shell + F2=Refresh F6=Command F10=Exit F3=Cancel F7=Edit Enter=Do F4=List F8=Image Press F4 to list the disk drives. 10. A list of disk drives is displayed.
| | | | | | | 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. Type smitty ssaraid and press Enter. 25. Select Change/Show Use of an SSA Physical Disk. The pdisk that has been exchanged is listed under SSA Physical Disks that are system disks. 26. Select the pdisk from the list. 27. Change the Current Use parameter to Hot Spare Disk or to Array Candidate Disk.
Changing Pdisk and Hdisk Numbers Pdisk and hdisk numbers are assigned automatically when the using system is configured. To help in system administration, it is sometimes useful to change these numbers. If you want to change the numbers, use the following procedure: 1. Find the pdisk or hdisk number that you want to change, and select a new (unused) name. 2. Give the command: lsdev -Cl [disknumber] -Fconnwhere where [disknumber] is the pdisk or hdisk number (for example, pdisk0) that you want to change.
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). 2. If you are exchanging this adapter for another, remove from it the SDRAM module and, if present, the Fast-Write Cache Option Card.
| | | | | | 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. Wait until all coupled disk drives can be uncoupled, before you connect the new adapter to the network. 6. Install the adapter into the using system (see the Installation and Service Guide for the using system).
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). 2. Refer to Figure 43. 3. Holding your thumbs against the connector 3 , open the clips 1 by pressing them in the directions shown by the arrows in the diagram.
Installing an SDRAM Module 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. v If you are exchanging a new SDRAM for a failed SDRAM, ensure that new SDRAM is the same size as the old SDRAM. Refer to the label on each SDRAM. 1. Refer to Figure 44. 2 1 2 3 3 1 Figure 44. Checking the Clips, Slots and Guides 2.
4. Refer to Figure 45. 1 1 Figure 45. Installing the SDRAM Module 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. You hear a click when the clips are fully closed. If you cannot close the clips, the module is not fully home. Press the module fully home, then close the clips. 8.
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. v The Fast-Write Cache Option card might contain customer data. 1. Remove the adapter from the using system (see the Installation and Service Guide for the using system). 2.
5. Refer to Figure 47. 1 2 Figure 47. Removing the Fast-Write Cache Option Card 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 . Chapter 15.
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. 1. Remove the adapter from the using system, if not already removed (see the Installation and Service Guide for the using system). 2. Place the adapter card, with its components upward, onto a nonconducting surface. 3. Refer to Figure 48. 1 2 Figure 48.
6. Refer to Figure 49. 1 Figure 49. Installing the Mounting Screw of the Fast-Write Cache Option Card 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). | | | | | | Note: The battery on the Fast-Write Option Card is not fully charged.
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. v The Fast-Write Cache Option card might contain customer data. 1. Remove the adapter from the using system (see the Installation and Service Guide for the using system). 2.
6. Refer to Figure 51. 1 Figure 51. Disconnecting the Battery Assembly 7. Invert the Fast-Write Cache Option card. 8. Carefully unplug the battery assembly from the connector 1 . 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. v The Fast-Write Cache Option card might contain customer data. 1. Refer to Figure 52. 1 Figure 52. Connecting the Battery Assembly 2. Hold the Fast-Write Cache Option card so that the battery-assembly connector 1 is upward.
4. Refer to Figure 53. 1 3 2 4 2 1 Figure 53. Installing the Battery Assembly 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. 7. Reinstall the Fast-Write Cache Option card (see “Installing the Fast-Write Cache Option Card of an Advanced SerialRAID Adapter” on page 334). 8.
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: 09L2105 v Fast-write cache battery: 09L5609 340 User’s Guide and Maintenance Information
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. They do not provide many error checking routines or error messages. If you need such facilities, use the SSA service aids (see Chapter 17, “SSA Service Aids” on page 373).
| | | | | | | -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 To install the latest level of microcode on all available SES enclosures, give the command: ssa_sesdld -u | | To install microcode file coral1014.hex on enclosure0, give the command: | | | To install microcode file coral1014.
ssaadap Command Purpose To 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. If the list contains more than one adapter, the first adapter in the list is the primary adapter. Flags -l DiskName Specifies the logical or physical disk. Chapter 16.
ssacand Command Purpose To 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. These connection locations are related to disk drives that, although connected to the adapter, are not yet configured as system disk drives. Flags -a AdapterName Specifies the adapter whose connection locations are to be listed.
ssa_certify Command Purpose v To certify the physical disk drive so that data can be read from, or written to, the disk drive without problems. v To certify a RAID-5 array to determine whether any array logical block addresses (LBAs) have been as unreadable. Syntax ssa_certify -l pdisk [-n MaxReadSize] [-a] ssa_certify -l hdisk [-b StartLBA] [-c] Description If the ssa_certify command is issued to a pdisk, it uses the ISAL_Read, ISAL_Write, or ISAL_Characteristics command to certify the disk drive.
reassign operations. You 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. Default size for this flag = 3072 kilobytes Minimum value that can be specified for this flag = 64 kilobytes Maximum value that can be specified for this flag = 10240 kilobytes.
ssaconn Command Purpose To 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 Verification service aid. The output from this command is: PhysicalDiskName AdapterName hopcount1 hopcount2 hopcount3 hopcount4 The four hop counts represent the number of SSA devices that are between the physical disk and the A1, A2, B1, and B2 ports of the adapter, respectively.
ssa_diag Command Purpose To 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. This flag has no effect if the device is a disk drive. -u Forces a disk reservation to be broken if the device the device that is being tested is a disk drive.
ssadisk Command Purpose To 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. These names are related to devices that are in the customized device data base, and have the SSA adapter as their adapter_a or adapter_b attribute. Flags -a AdapterName Specifies the adapter to which the disk drives are connected. -P Produce a list of physical disks.
ssadload Command Purpose To 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. The command has three modes of operation: v Load a specific level of microcode into a specific SSA physical disk drive.
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. By default, this flag ensures that all SSA physical disk drives are loaded with the latest microcode. To update a specific disk drive, use this flag and the -d flag.
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. v Using the -u, -a adapter, and -p flags: ssadload -u -a ssa0 -p & ; ssadload -u -a ssa1 -p | | | With these flags, the command causes the update mechanism to run in parallel and update concurrently the microcode on all the available disk drives that are connected to adapters ssa0 and ssa1.
ssa_ela Command Purpose To look for the most significant error in the error log. Syntax ssa_ela ssa_ela ssa_ela ssa_ela ssa_ela | | | | | -l -l -l -l Device [-h timeperiod] pdisk hdisk adapter Description | | | The ssa_ela command (with no flags) scans the error log, and looks for all SSA errors. The command returns a list that contains one SRN for each SSA device that is on the system. Each SRN is for the most significant error of its related SSA device.
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 To allow the monitoring and changing of the status for SSA SES disk enclosures (subsystems). Syntax | | | | To display enclosure component settings: ssaencl -l name [-s] [-v] [-i] [-r] [-b [card ...]] [-t [threshold ...]] [-a] [-f [fan ...]] [-d [drive_bay ...]] [-p [PSU ...]] [-o] [-c] [-e] To modify enclosure component settings: ssaencl -l name [-I ID [-U]] [-B mode | card=mode ...] [-S{d[drive_bay ...] | b[card...] | p[PSU ...] | r | c | o }] [-T threshold=value ...
-t [threshold] Displays all the temperature thresholds, or only the specified temperature thresholds. The valid values for the [threshold] parameter are: -a lowarn The low-temperature warning threshold. locrit The low-temperature critical threshold. hiwarn The high-temperature warning threshold. hicrit The high-temperature critical threshold. Displays the ambient temperature of the enclosure. -f [fan] Displays the status of all the fans, or of only the specified fans.
| | | -S b[card ...] Resets the flag for the bypass card. Valid 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). Valid values for PSU are 1, 2. | -S r Resets the flag for remote power on (RPO). | -S c Resets the flag for the controller card. | -S o Resets the flag for the operator panel. -T threshold=value Modifies the specified temperature thresholds to the given values.
ssa_format Command Purpose To 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. You can close the device while the format operation is running. If the command cannot format the device, it prints an error message. The ssa_format -l SSA_Adapter command attempts to format the Fast-Write Cache Option Card (if present).
-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. Output The ssa_format command sends all error messages to stderr. Chapter 16.
| ssa_fw_status Command | | Purpose | | Syntax | | | Description | Flags To show the status of the fast-write cache. ssa_fw_status -a Adapter [-p|-l|-c] The ssa_fw_status command displays the status of the fast-write cache of an SSA adapter. | | -a Adapter Shows all fast-write status for the specific adapter. | -l Displays the expected life of the battery. | -p Displays the number of hours for which the battery has been powered-on. | -c Shows the state of the fast-write cache.
ssa_getdump Command Purpose To 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 AdapterName | -n AdapterUID | -s SlotNumber ] For the Copy version of the command: ssa_getdump -c [-h] -d pdiskxx {-a AdapterName | -n AdapterUID | -s SlotNumber } [-x] -o OutputFile Description The ssa_getdump command has two modes of operation: List mode and Copy mode.
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 You must use one of these flags: -l Specifies that the program is to operate in List mode. The program searches for dumps. -c Specifies that the program is to operate in Copy mode. The program copies the dump (if one is found) from the specified location to the specified output point.
-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. -s SlotNumber Specifies the slot that contains the disk drive, as shown in the List Output. Optional Flags for Copy Mode You can choose either or both of these flags: -h Prevents the output of progress messages from the program.
ssaidentify Command Purpose To 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. The -n flag switches off Identify mode. Flags -l PhysicalDiskName Specifies the device to place into Identify mode. 364 -y Switches on Identify mode.
ssa_progress Command Purpose To show how much (by percentage) of a format operation has been completed, and to show the status of the format operation. The status can be “Complete”, “Formatting”, or “Failed”. Syntax ssa_progress -l pdisk Description The ssa_progress command opens the pdisk special file, and uses the ISAL Progress command to determine the percentage of the formatting operation that is complete.
ssa_rescheck Command Purpose To 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. Flags -l hdisk Specifies the hdisk that you want to test. -h Switches off the header output. Output The ssa_rescheck command sends error messages to stderr.
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 To put the disk drive into Service Mode (set Service Mode), or to remove the disk drive from Service Mode (reset Service Mode). Syntax ssa_servicemode -l [-a AdapterName] -y|-n Description The ssa_servicemode command opens the adapter special file, and sends the appropriate IACL command to put the disk drive into, or remove it from, Service Mode. When the Service Mode has been successfully set or reset, the IACL command closes the adapter special file.
ssa_speed Command Purpose To 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_speed command either tests the existing link speeds of the selected pdisk or adapter, or searches for link speed exceptions on all SSA adapters in the using system. Flags -l pdisk Specifies the pdisk that you want to test. -a AdapterName Specifies the adapter that you want to test.
Output The ssa_speed command sends all error messages to stderr, and output to stdout.
ssavfynn Command Purpose To 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. It has no flags. If the ssavfynn command runs and finds no duplicate node numbers on the SSA network, it returns no message.
ssaxlate Command Purpose To 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. If the parameter is a physical disk, the output is a list of names of the logical disks that use that physical disk. Flags -l DiskName Specifies the logical or physical 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. SSA service aids are resident in the using system. They help you to service SSA subsystems. This section describes those service aids, and tells how to use them.
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. When set, the Identify function causes the Check light of the disk drive to flash for identification (two seconds on, two seconds off), but has no effect on the normal operation of the disk drive.
Starting the SSA Service Aids To 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. 3. Select Task Selection from the Function Selection menu. 4. Select SSA Service Aids from the Tasks Selection list. The SSA Service Aids menu is displayed: SSA SERVICE AIDS 802380 Move cursor onto selection, then press Enter.
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 Verification Service Aid” on page 383 “Configuration Verification Service Aid” on page 387 “Format Disk Service Aid” on page 389 “Certify Disk Service Aid” on page 391 “Display/Download Disk Drive Microcode Service Aid” on page 393 “Link Speed Service Aid” on page 396 Chapter 17.
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. It also causes the Subsystem Check light (if present) of the unit containing the selected disk drive to come on. Only one disk drive at a time can be in Service Mode.
To 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 .
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 systemname:pdisk0 AC50AE43 802382 4GB SSA C Physical Disk Drive Move cursor onto selection, then press . + Set or Reset Identify. Select this option to set or reset the Identify indicator on the disk drive. > Set or Reset Service Mode.
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. SET SERVICE MODE 802381 Move cursor onto selection, then press .
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 . + Set or Reset Identify. Select this option to set or reset the Identify indicator on the disk drive. > Set or Reset Service Mode. Select this option to set or reset Service Mode on the disk drive.
Link Verification Service Aid The Link Verification 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 on that SSA loop v The location of enclosure faults that have been detected by the disk drives on that SSA loop To use the Link Verification service aid: 1. Select Link Verification from the SSA Service Aids menu (see “Starting the SSA Service Aids” on page 376).
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 . Physical Serial# [TOP] nunu:pdisk2 nunu:pdisk9 nunu:pdisk8 nunu:pdisk3 ssd32:ssa0:A nunu:pdisk6 nunu:pdisk1 nunu:pdisk7 nunu:pdisk5 [MORE...
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. Status conditions are: Good The disk drive is working correctly. Failed The disk drive has failed. Power The disk drive has detected an enclosure fault.
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. ***** | | These asterisks indicate an unconfigured device; that is, an SSA device that is in the SSA network, but whose type is not known.
Configuration Verification Service Aid The Configuration Verification 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. Notes: 1. User applications communicate with the hdisks; error data is logged against the pdisks. 2.
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 systemname:hdisk2 802391 AC51DB47 SSA Logical Disk Drive Good To set or reset Identify, move cursor onto selection, then press .
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. To use the Format Disk service aid: 1. Select Format Disk from the SSA Service Aids menu (see “Starting the SSA Service Aids” on page 376). A list of pdisks is displayed: FORMAT DISK 802395 Move cursor onto selection, then press .
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 . + Set or Reset Identify. Select this option to set or reset the Identify indicator on the disk drive. Format. Select this option only if you are sure that you have selected the correct disk drive. FORMATTING DESTROYS ALL DATA ON THE DISK DRIVE. F3=Cancel F10=Exit 3.
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. To 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). A list of pdisks is displayed: CERTIFY DISK 802404 Move cursor onto selection, then press .
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 . + Set or Reset Identify. Select this option to set or reset the Identify indicator on the disk drive. Certify. Select this option to start the Certify operation. F3=Cancel F10=Exit 3.
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. v Change the level of microcode, for a specific available disk drive, to any level that is available in the using-system microcode directory or on diskette.
To 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. Display the Microcode levels of all SSA Physical Disk Drives Select this option to display the microcode levels installed on all ’Available’ SSA disk drives.
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. If you need to try to save data, you might be able to exchange the electronics card assembly of the disk drive. For more details, see the Installation and Service Guide for the unit that contains the disk drive.
Link Speed Service Aid The Link Speed service aid allows you to display the operating speed of each link on an SSA adapter. To 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). A list of adapters is displayed: LINK SPEED 802437 Move cursor onto selection, then press .
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 .
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. The Speed field indicates the operating speed of the link as follows: 00 The link is not operational 20 20 MB per second 40 40 MB per second Figure 54 gives a physical representation of the configuration that is shown on the screen.
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 .
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 411). Using the Service Aids for SSA-Link Problem Determination If you have a problem with an SSA loop, use the Link Verification service aid (see “Link Verification Service Aid” on page 383).
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 Verification service aid displays the following information: LINK VERIFICATION SSA Link Verification for: systemname:ssa0 802386 00-04 IBM SSA 160 SerialRAID Adapter ( To Set or Reset Identify, move cursor onto selection, then press . Physical Serial# [TOP] systemname:pdisk11 systemname:pdisk8 systemname:pdisk2 systemname:pdisk3 systemname:pdisk7 systemname:pdisk12 systemname:pdisk0 systemname:pdisk1 systemname:pdisk10 [MORE...
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. In Figure 57 on page 404, disk drives 1 through 8 should be connected to connectors A1 and A2 of the SSA adapter 1 , but the loop is broken because the SSA cable has been disconnected from connector A2.
Using system A1 A2 Using system B1 B2 A1 A2 Disk Disk Disk Disk Disk Disk Disk Disk 16 15 14 13 12 11 10 9 Disk Disk Disk Disk Disk Disk Disk Disk 1 2 3 4 5 6 7 8 Figure 57.
For this example, the Link Verification service aid displays the following information: LINK VERIFICATION SSA Link Verification for: systemname:ssa0 802386 00-04 IBM SSA 160 SerialRAID Adapter ( To Set or Reset Identify, move cursor onto selection, then press . Physical Serial# [TOP] systemname:pdisk11 systemname:pdisk8 systemname:pdisk2 systemname:pdisk3 systemname:pdisk7 systemname:pdisk12 systemname:pdisk0 systemname:pdisk1 ????? [MORE...
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. Disk drives 13 through 16 are connected to connectors A1 and A2 of a different SSA adapter 2 .
Using system A1 A2 Using system B1 B2 A1 A2 B1 B2 Disk Disk Disk Disk Disk Disk Disk Disk 16 15 14 13 12 11 10 9 Disk Disk Disk Disk Disk Disk Disk Disk 1 2 3 4 5 6 7 8 Figure 58. Broken Loop (Disk Drive Removed) Chapter 17.
For this example, the Link Verification 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 . Physical Serial# [TOP] systemname:pdisk11 systemname:pdisk8 ????? systemname:pdisk3 systemname:pdisk7 systemname:pdisk12 systemname:pdisk0 systemname:pdisk1 systemname:pdisk10 [MORE...
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. The address can, therefore, change if the configuration is changed.
410 User’s Guide and Maintenance Information
Chapter 18. SSA Problem Determination Procedures SSA problem determination procedures are provided by power-on self-tests (POSTs), 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. Service Request Numbers (SRNs) Service request numbers (SRNs) are generated by the system error-log analysis, system configuration code, diagnostics, and customer problem-determination procedures.
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 Verification” on page 475 to verify the repair. 4. When exchanging an adapter, always use the instructions that are supplied with the system unit.
SRN Problem Possible Causes 1xxxx Description: SRNs in this range are not adapter SRNs. Not applicable. Action: For SRNs in this range, see the documentation for your SSA enclosure or SSA subsystem. 20PAA Description: An open SSA link has been detected. Action: Run the Link Verification service aid to isolate the failure (see “Link Verification Service Aid” on page 383).
SRN 2A004 Problem Possible Causes Description: Async code 04 has been received. Probably, a software error has occurred. Software error. Possible FRUs: Action: Go to “Software and Microcode Errors” on page 441 before exchanging any FRUs. | | | | Device (50%) (“Exchanging Disk Drives” on page 319). SSA adapter card (50%) (“Removing and Replacing an Advanced SerialRAID Adapter” on page 327). 2A005 to 2A206 Description: SRNs in this range are not adapter SRNs.
SRN 34000 Problem Possible Causes 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. Possible FRUs: Action: Exchange the FRUs for new FRUs.
SRN 40128 Problem Possible Causes Description: A 128 MB SDRAM in the adapter card module has failed. Possible FRUs: Action: Exchange the FRUs for new FRUs. | | | | 128 MB SDRAM module (99%) (“Removing an SDRAM Module of an Advanced SerialRAID Adapter” on page 329). SSA adapter card (1%) (“Removing and Replacing an Advanced SerialRAID Adapter” on page 327). 42000 Description: Either no SDRAM module is present on the adapter card, or the POST cannot determine the size of the existing SDRAM module.
SRN 42510 Problem Possible Causes Description: Not enough SDRAM available to run the fast-write cache operation. User or service action. 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. 4. Find the VPD for the SSA adapter that is logging the error. 5. Note the SDRAM and cache sizes (Device Specifics Z0 and Z1). 6.
SRN 42521 Problem Possible Causes Description: A Fast-Write 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. Possible FRUs: Action: 1.
SRN 42524 Problem Possible Causes 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. System configuration problem. Action: v If the Fast-Write Cache Option Card has been removed, reinstall it, and test the disk drive subsystem. v If the Fast-Write Cache Option card has failed: 1.
SRN 42525 | | | Problem Possible Causes Description: A fast-write logical disk contains unsynchronized data, but the v The data was not Fast-Write Option Card does not contain that data. The failing disk drive is synchronized on the old offline. adapter before the disk drive was moved to this adapter. Action: v The wrong Fast-Write Option v If the disk drive has just been moved from another adapter, do either of Card was installed onto this the following actions: adapter.
SRN 42528 Problem Possible Causes Description: A fast-write disk drive has been detected that was previously unsynchronized, but has since been configured on a different adapter. User or service action. Action: If this disk drive contains data that should be kept, return the disk drive to the adapter to which it was previously connected. If the disk drive does not contain data that should be kept: 1. Physically remove the disk drive from the system configuration. 2.
SRN 4252C Problem Possible Causes Description: The Fast-Write Cache Option Card battery needs to be exchanged for a new one. Possible FRUs: Action: Exchange the FRU for a new FRU. || || | | | || | | | | | | | | 4252D Description: Fast-write caching is suspended (stopped temporarily) for one or more devices. Action: 1. Type smitty devices and press Enter. Fast-Write Cache Option Card battery (100%) (“Removing the Fast-Write Cache Option Card of an Advanced SerialRAID Adapter” on page 332).
SRN 43PAA Problem Possible Causes Description: An SSA device on the link is preventing the completion of the loop configuration. Possible FRUs: Action: If the SSA service aids are available, run the Link Verification service aid (see “Link Verification Service Aid” on page 383) to determine which device is preventing configuration. (That device is the one beyond the last-configured device on an open SSA loop.) | | | | Device (90%) (“Exchanging Disk Drives” on page 319).
SRN Problem Possible Causes | 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: At least one disk drive missing from an array, and that array is not now connected to the SSA adapter that opened it. The array remains in the Offline state, because its data integrity cannot be verified.
SRN | | 48600 Problem Possible Causes 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. SSA loop configuration problem. Action: All the member disk drives of an array must be on the same SSA loop. Find all the members of the array: 1. Type smitty devices and press Enter. 2. Select SSA RAID Arrays. 3. Select List/Identify SSA Physical Disks. 4. Select List Disks in an SSA RAID Array. 5.
SRN 48750 Problem Possible Causes Description: An array is in the Offline state because the primary or the secondary half of the array is not present. The adapter cannot get access the other adapter in the loop because one of the following conditions exists: 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 | | 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. This problem can occur if a RAID-1 array or a RAID-10 array has been split exactly in half, and a write operation has been performed independently to both halves of the array.
SRN 48950 Problem Possible Causes Description: A disk drive has caused an array building operation to fail. A disk drive has failed during an array building operation. Because the failure occurred before an initial array building operation had completed, a hot spare disk drive has not replaced the failed disk drive. Action: 1. Type 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. 3.
SRN | | 49000 | Problem Possible Causes 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. v A power failure has occurred. v A RAID-5 array causes this SRN if a disk drive is not available to the array, and a write command is sent to the array.
SRN 49500 Problem Possible Causes Description: No hot spare disk drives are available for an array that is configured for hot spare disk drives. A RAID array is configured to use hot spare disk drives, but no disk drive can be found that is configured as a hot spare. This error code is used only when no hot spare pools have been assigned. All arrays and hot spare disk drives are in the default pool0. Action: Determine whether any disk drives have failed or have been rejected. To do this action: 1.
SRN | | | | 49510 Problem Possible Causes SSA loop configuration Description: Hot-spare configuration is not synchronized. This problem has occurred because the cabling has changed or because new hot-spare problem. disks have been added to the SSA loop. Action: 1. If the changes were not planned, restore the system to its original configuration. If the changes were planned, go to step 2. 2. Type smitty ssaraid and press Enter. 3. Select List Status of Hot-Spare Pools. 4.
SRN 49520 Problem Possible Causes Description: Hot-spare tuning has been lost. An array member has used a hot spare disk drive from a pool other than its specified pool. If the hot-spare pools have been correctly configured, this error indicates that more than one disk drive might have failed. Action: 1. Type 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. 4.
SRN 49530 Problem Possible Causes Description: The number of disk drives that remain in a hot-spare pool is less than the specified number. The number of hot-spare disk drives that are now in the assigned pool is less than the specified minimum number. Action: 1. Type 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. 4. Exchange all the rejected disk drives for new disk drives.
SRN | || || || | | | | | | | 49950 Problem Possible Causes 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: Possible FRUs: Device (100%) (“Exchanging Disk Drives” on page 319). v The disk drive has failed. v The disk drive has been removed from the subsystem. v An SSA link has failed.
SRN 50002 | | | | Problem Possible Causes Description: An SSA adapter DMA error has occurred. Possible FRUs: SSA adapter card (100%) (“Removing and Replacing an Advanced SerialRAID Adapter” on page 327). Action: Exchange the FRU for a new FRU. 50007 | | | | Description: The IOCC detected an internal error. SSA adapter card (100%) (“Removing and Replacing an Advanced SerialRAID Adapter” on page 327). Action: Exchange the FRU for a new FRU.
SRN | | 50200 | Problem Possible Causes Description: A duplicate node number has been detected. This problem is a user error. SSA loop configuration problem. Action: See “SSA Disk Concurrent Mode of Operation Interface” on page 287. You can use the ssavfynn command line utility (see “ssavfynn Command” on page 371) to determine which node has the duplicate node number. | | 50411 Description: The SSA adapter has detected an SS_SIC_CLASS1 error.
SRN 504XX | | | | : | :| | | : : : 54050 Problem Possible Causes Description: The SSA adapter microcode has hung. Software error. Action: Run diagnostics in System Verification 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. Possible FRUs: Description: The adapter bus has been reset.
SRN D4000 | | | | | | || | | | | | Possible Causes Possible FRUs: Action: Exchange the FRU for a new FRU. D4050 Description: The Enhanced Error Handling test has failed. Action: Exchange the FRUs for new FRUs. D4100 Description: The diagnostics cannot open the SSA adapter. Action: Exchange the FRU for a new FRU. D4300 | | | | Possible FRUs: SSA adapter card (60%) (“Removing and Replacing an Advanced SerialRAID Adapter” on page 327). Action: Exchange the FRU for a new FRU.
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. Description: A command or parameter that has been sent or received is not valid. This problem is caused either by the SSA adapter, or by an error in the microcode. Software error.
SRN Problem 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. Action: Do the actions described here: 1. Use the Configuration Verification service aid (see “Configuration Verification Service Aid” on page 387) to determine the location code of the SSA adapter to which the hdisk is attached.
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. For AIX Versions 4.2 and above, run the snap -b command to collect system configuration data, and to dump data. For AIX versions below 4.
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. Enclosure power cables and external SSA cables that connect the devices to the using system can be disconnected while that system is running.
MAP 2010: START 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. You might have been sent here because: v The system problem determination procedures sent you here. v A problem occurred during the installation of a disk subsystem or a disk drive. v Another MAP sent you here. v A customer observed a problem that was not detected by the system problem determination procedures.
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. Chapter 2, “Introducing SSA Loops” explains SSA links, strings, and loops. Attention: Unless the using system needs to be switched off for some other reason, do not switch off the using system when servicing the SSA loop.
If the service aid cannot detect any pdisks, a message is displayed: LINK VERIFICATION 802385 Move cursor onto selection, then press . nunu:ssa1 nunu:ssa1 nunu:ssa1 00-04 00-05 00-07 IBM SSA 160 SerialRAID Adapter ( IBM SSA 160 SerialRAID Adapter ( IBM SSA 160 SerialRAID Adapter ( -----------------------------------------------------| | No pdisks are in the ’Available’ state.
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 . Physical Serial# [TOP] nunu:pdisk11 nunu:pdisk8 nunu:pdisk2 nunu:pdisk3 nunu:pdisk7 nunu:pdisk12 nunu:pdisk0 nunu:pdisk1 nunu:pdisk10 [MORE...
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. 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 . Physical Serial# [TOP] nunu:pdisk11 nunu:pdisk8 nunu:pdisk2 nunu:pdisk3 nunu:pdisk7 nunu:pdisk12 nunu:pdisk0 nunu:pdisk1 nunu:pdisk10 [MORE...
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. 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 .
MAP 2323: SSA Intermittent Link Error This MAP helps you to isolate FRUs that are causing an intermittent SSA link problem. You are here because you have an SRN from the series 21xxx through 29xxx, or you have SRN 33xxx. If you are not familiar with the SSA link, read the section Chapter 2, “Introducing SSA Loops” on page 7 before using this MAP. Chapter 2, “Introducing SSA Loops” explains SSA links, strings, and loops.
a. Observe the SRN that sent you to this MAP. The last three characters are in the format PAA, where P is the number of the SSA adapter port, and AA is the SSA address of the device). Note the value of PAA in the SRN. For example: If the SRN is 24002, PAA = 002. If the SRN is 24104, PAA = 104. b. Observe the Link Verification screen, and identify the physical device that is represented by PAA in the SRN. This device is the first of the two devices that are connected by the failing link.
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 (PAA−1). If the SRN is 33002, the first device of the two is again pdisk3. The second device is pdisk4 (PAA+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. 3. (from step 2) The problem is in the SSA link between the two devices that you identified in step 2 on page 450. Exchange, in the sequence shown, the following FRUs for new FRUs.
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. Enclosure power cables and external SSA cables that connect devices to the using system can be disconnected while that system is running.
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. | SRN Cause Action 46000 An array is in the Offline state. Go to step 5. 47000 You have more than the maximum number of arrays allowed. Go to step 8 on page 457.
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. Type smitty ssaraid and press Enter. b. Select Delete an SSA RAID Array. c. Select the array that is in the Offline state, and delete it. All data that is on that RAID array is now lost. d.
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. Type smitty ssaraid and press Enter. b. Select Change/Show Use of an SSA Physical Disk. Are any disk drives listed as “SSA physical disks that are rejected”? NO Ask the user to delete and recreate the array that is in the Offline state. YES a. Run diagnostics in System Verification mode to all the disk drives that are listed as rejected. b.
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. Type smitty ssaraid and press Enter. b. Select List Status Of All Defined SSA RAID Arrays. c. Select, in turn, each array type that is used in your subsystem, and press Enter.
10. (from step 9) a. Type 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. e. Ask the user to create a backup of all the data from this array. Some data might not be accessible. f. When the backup has been created, ask the user to delete the array. g.
12. (from step 11) 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). b. Go to step 37 on page 473 to add the disk drive to the group of disk drives that are available for use by the RAID manager. 13.
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 Verification mode to all the disk drives that are listed as rejected. b. Run the Certify service aid (see “Certify Disk Service Aid” on page 391) to all the disk drives that are listed as rejected. c.
When the rebuilding operation is complete, ask the user to run diagnostics in System Verification mode to the SSA adapters, to ensure that the rebuilding operation has not found any more problems. k. Go to “MAP 2410: SSA Repair Verification” on page 475 to verify the repair. 15. (from step 14) Does the Link Verification service aid indicate an open loop? NO Go to step 16. YES Go to “MAP 2320: SSA Link” on page 445. 16.
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. If the missing disk drives are returned to the array, the array enters the Good state. No data rebuilding is necessary.
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 Verification mode to all the disk drives that are listed as rejected. b. Run the Certify service aid (see “Certify Disk Service Aid” on page 391) to all the disk drives that are listed as rejected. c.
When the rebuilding operation is complete, ask the user to run diagnostics in System Verification mode to the SSA adapters, to ensure that the rebuilding operation has not found any more problems. k. Go to “MAP 2410: SSA Repair Verification” on page 475 to verify the repair. 19. (from step 18) Does the Link Verification service aid indicate an open loop? NO Go to step 20. YES Go to “MAP 2320: SSA Link” on page 445. 20.
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). b. Type smitty ssaraid and press Enter. c. Select Change/Show Use of an SSA Physical Disk. Are any disks listed as “SSA Physical disks that are hot spares”? NO Review with the user the requirement for hot spare disk drives.
22. (from step 7 in MAP 2410: SSA Repair Verification, and from steps 3, 11, and 12 in this MAP) RAID Checkout You are now starting the RAID checkout procedure a. Type smitty ssaraid and press Enter. b. Select Change/Show Use of an SSA Physical Disk from the SSA RAID Arrays menu. Are any disks listed as “SSA physical disks that are rejected”? NO Go to step 28 on page 470. YES a. Run diagnostics in System Verification mode to all the disk drives that are listed as rejected. b.
| | | | | | | | | | | | 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. 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. Under such conditions, the disk drive can be reused.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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). h. Referring to the displayed instructions, select a disk drive to remove from the array, and the disk drive to add to the array.
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. Under such conditions, the disk drive can be reused. If you think that a disk drive has been rejected because it is failing, check the error log history for that disk drive.
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. b. Press the Cancel key to leave the status display. c. Wait for a few moments, then reselect the status display. d. Again note the number of unsynced parity strips and unbuilt data strips.
33. (from step 32) Was SRN 49100 logged, but no error found, when diagnostics were run in System Verification 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. Verify that using-system procedures ensure that the power system switches on power to all the disk drives before, or when, it switches on the power to the using system. 34. (from step 33) a.
| 36. (from step 35) You have solved all the problems. a. Run the repair verification or repair completion procedures that are defined by your using system. b. If you have previously created a backup, reload that data now. | 37. (from steps 7, 10, 12, and 27) Has a failed disk drive been exchanged for a new disk drive? NO If you have repaired a power or cabling fault that caused the disk drive to be missing from the system, the drive might now be in a rejected state.
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) You have changed the use of a disk drive. You must now ensure that the hot spare pools are correctly configured. To do this action: a. Type smitty ssaraid and press Enter. b. Select List Status of Hot Spare Pools. c. Select, in turn, each SSA adapter. d.
MAP 2410: SSA Repair Verification 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. 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.
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. If the original problem was not reported by a device, run diagnostics to each SSA adapter in the using system. b. Go to step 4. 4. (from step 3) Do you still have the same SRN? NO Go to step 5. YES Go to step 6. 5.
7. (from steps 3 in MAP 2010: START 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. Type smitty ssaraid and press Enter. b. Select List All Defined SSA RAID Arrays. NO Run the repair verification, or repair completion, procedures that are defined by your using system. YES Go to the RAID Checkout at step 22 on page 467 of MAP 2324: SSA RAID. Chapter 18.
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. SSA Subsystem Disk Drive 1 Internal Connection Disk Drive 2 Figure 59. Three-Part Link in One Subsystem Example 2 In Figure 60, the link is between two disk drives that are in the same subsystem. It has five parts. SSA Subsystem Disk Drive 1 Internal Connection Dummy Disk Drive Internal Connection Disk Drive 2 Figure 60. Five-Part Link in One Subsystem Chapter 18.
Example 3 In Figure 61, the link is between two disk drives that are not in the same subsystem. It has seven parts. SSA Subsystem Disk Drive Internal Connection SSA Subsystem SSA Connector Card SSA Connector Card Cable Internal Disk Connection Drive Figure 61. Seven-Part Link in Two Subsystems Example 4 Figure 62, the link is between a disk drive and an SSA adapter. It has five parts. SSA Subsystem Internal Disk Drive Connection SSA Connector Card Cable Adapter Figure 62.
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. You can find the failing link by looking for the flashing green status light at each end of the affected link. Some configurations might have other indicators along the link (for example, SSA connector cards) to help with FRU isolation.
Service Aid If service aids are available, you can use the Link Verification 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 . Physical Serial# [TOP] systemname:pdisk11 systemname:pdisk8 systemname:pdisk2 systemname:pdisk3 systemname:pdisk7 systemname:pdisk12 systemname:pdisk0 ????? systemname:pdisk10 [MORE...
Part 3.
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. Federal Communications Commission (FCC) Statement This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules.
International Electrotechnical Commission (IEC) Statement This product has been designed and built to comply with (IEC) Standard 950. Avis de conformité à la réglementation d’Industrie Canada Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada. Industry Canada Compliance Statement This Class A digital apparatus complies with IECS-003.
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. Taiwan Class A Compliance Statement Appendix.
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: couple. To attach a copy array to a RAID-1 or RAID-10 array, and copy data from the RAID-1 or RAID-10 array to that copy array.
I Exposed state. The state that a RAID array enters if a member disk drive becomes missing (logically or physically) from that array. interface. Hardware, software, or both, that links systems, programs, or devices. F IOCC. Input/output channel controller. Failed status. The disk drive is not working. IPN. Independent Packet Network. 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 disk drives. ISAL.
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. Two disk drives that contain the same data, and are referred to as one entity by the using system. mirroring. The process of writing the same data to two disk drives at the same time. The two disk drives become a mirrored pair. The system can, therefore, continue to operate correctly when one of the mirrored disk drives fails.
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. unrecoverable error. An error for which recovery is impossible without the use of recovery methods that are outside the normal computer programs. | | | SMIT.
Index Numerics 128 MB Memory Module feature 5 3-way copy array copy services 173 Delete a RAID Array Copy option 183 Delete a Volume Group, Logical Volumes, or Filesystems Copy option 184 List All Copy Candidates option 179 List All Uncoupled Copies option 181 List All Uncoupled Volume Groups option 182 Prepare a Copy option 175 Uncouple a Volume Group, Logical Volumes, or File Systems Copy option 177 copying data from an array 151 description 149 effects of array copy on other SMIT menus 186 Change/Show A
array copy services (continued) Prepare a Copy option 175 Uncouple a Volume Group, Logical Volumes, or File Systems Copy option 177 array states, RAID-0 31 Good 31 Offline 31 array states, RAID-1 32 array states, RAID-10 36 Degraded 37 Exposed 36 Good 36 multiple 38 Offline 37 Rebuilding 37 Unknown 38 array states, RAID-5 33 Degraded 33 Exposed 33 read operations while in 33 write operations while in 33 flowchart 35 Good 33 initial rebuilding operation 34 Offline 34 Rebuilding 34 adapter replacement 34 disk
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 ucode 257 physical disk change attributes 249 physical disk drive change fastwrite=on/off 250 force=yes/no 251 fw_end_block 250 fw_max_length 250 fw_start_block 250 use=system/spare/free 250 RAID arrays change 248 force=yes/no 248 use=system/free 248 RAID arrays creation and change 244 allow_page_splits=true/false
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 235 action attributes 251 command syntax 237 couple action attributes 252 hot spare pool creation and change attributes 249 instruct types 238 object types 238 options 238 physical disk change attributes 249 RAID arrays change attributes 248 RAID arrays creation and change attributes 244 return codes 253 SSARAID
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 changing member disks in an SSA RAID array 137 changing or showing the attributes of an SSA RAID array 135 changing or showing the status of a hot spare pool 74 changing or showing the use of an SSA disk drive 144 changing the use of multiple SSA physical disks 147 creating a hot spare disk drive 72 deleting an
Degraded state, RAID-10 37 Degraded state, RAID-5 33 Delete a RAID Array Copy option 183 Delete a Volume Group, Logical Volumes, or Filesystems Copy option 184 Delete an SSA RAID Array option 70 detail data formats, error logging 225 device attributes 270 device driver entry point 287 device drivers 255 adapter configuring devices 257 description 257 device-dependent subroutines 258 direct call entry point 265 IOCINFO ioctl operation 261 managing dumps 259 open and close subroutines 258 purpose 257 SSA_GET_
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 283 description 283 files 284 purpose 283 return values 284 syntax 266 disk drive microcode maintenance 315 disk drives failed, identifying, correcting, and removing 91 finding the physical location 409 formatted on different types of machine 387 identification 19 not in arrays 30 reservation of 27 unique IDs (
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 getting access to the SSA RAID Array SMIT menu 59 good housekeeping 233 Good state, RAID-0 31 Good state, RAID-10 36 Good state, RAID-5 33 H hdisks and pdisks changing numbers 326 explanation of 19 reformatting a pdisk as an hdisk 387 head device driver/adapter device driver interface 256 hot spare management 45 c
installing the SSA adapter 313 instruct types, Command Line Interface 238 interface, adapter device driver/head device driver IOCINFO ioctl operation 261, 305 description 261, 305 disk device driver 277 description 277 files 277 purpose 277 files 261 purpose 261, 305 ioctl subroutine tmssa device driver 301 issaraid command 119 256 L large configurations 16 switching off using systems 17 switching on using systems 17 lassaraid command 117 lcssaraid command 115 lfssaraid command 91, 113 lhssaraid command 1
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 11 open and close subroutines adapter device driver 258 open subroutine tmssa device driver 296 open, read, write, and close subroutines disk device driver 272 operation after a loss of member disks, split-site management 194 adapter not known to remaining half of the array 203 one half of the array is not present 195 split and join procedure not performed correctly 205 options
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 array 135 changing or showing the status of a hot spare pool 74 changing or showing the use of an SSA disk drive 144 changing the use of multiple SSA physical disks 147 creating a hot spare disk drive 72 deleting an old RAID array recorded in an SSA RAID manager 133 deleting from the configuration 70 identifyi
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 SDRAM module 329 removing the battery assembly from the fast-write cache card 336 removing the fast-write cache card 332 SSA adapter 327 Remove a Disk from an SSA RAID Array option 138 Remove a Disk From an SSA RAID Array option, effects of array copy 190 removing an SDRAM module 329 removing and replacing an SSA a
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/Disable Fast-Write for Multiple Devices 215 Identify Array Candidate Disks 125 Identify Disks in an SSA RAID Array 119 Identify Hot Spares 121 Identify Rejected Array Disks 123 Identify System Disks 127 List All Defined SSA RAID Arrays 100 List All SSA RAID Arrays Connected to a RAID Manager 102 List All Suppo
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 two adapters in each of two using systems 12 one loop with two adapters in one using system 11 problem determination 400 rules 22 simple 8 simple, one disk drive missing 9 simple, two disk drives missing 10 two loops with one adapter 14 two loops with two adapters 15 SSA RAID Array SMIT menu, getting access 59
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 special files 276 SSADISK_ISAL_CMD ioctl operation disk device driver 278 description 278 files 280 purpose 278 return values 279 SSADISK_ISALMgr_CMD ioctl operation disk device driver 281 description 281 files 282 purpose 281 return values 282 SSADISK_LIST_PDISKS ioctl operation disk device driver 285 description 285
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 using ssaraid commands to create a copy array 151 TMCHGIMPARM (change parameters) tmssa device driver ioctl operation 308 description 308 purpose 308 TMIOSTAT (status) tmssa device driver ioctl operation 307 description 307 purpose 307 tmssa device driver 295 description 295 IOCINFO ioctl operation 305 descripti
Part Number: 27H0678 SA33-3285-02 (1P) P/N: 27H0678 Printed in the U.S.A.
Spine information: Advanced SerialRAID Adapters User’s Guide and Maintenance Information
