Managing Disk Units

7/25/2019 Managing Disk Units

1/36

iSeries

Managing disk units


2/36


3/36

iSeries

Managing disk units


4/36

Copyright International Business Machines Corporation 2001. All rights reserved.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/36

Contents

Managing disk units in disk pools . . . . . . . . . . . . . . . . . . . . . . . . . . 1Planning for disk management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Accessing Disk Units in Operations Navigator . . . . . . . . . . . . . . . . . . . . . 2

Accessing your iSeries server from your PC . . . . . . . . . . . . . . . . . . . . . . 2

Choosing the right procedure for configuring disks . . . . . . . . . . . . . . . . . . . . 3Calculating disk pool space requirements. . . . . . . . . . . . . . . . . . . . . . . 14Task 1: Calculating the current storage used . . . . . . . . . . . . . . . . . . . . . 15

Task 2: Calculating storage needed . . . . . . . . . . . . . . . . . . . . . . . . . 15Using the graphical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Managing disk unit configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Adding a disk unit or disk pool. . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Maintaining disk unit configuration . . . . . . . . . . . . . . . . . . . . . . . . . 18Protecting data on disk units . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Working with device parity protection . . . . . . . . . . . . . . . . . . . . . . . . 20Working with mirrored protection . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Optimizing disk unit performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Managing data in independent disk pools. . . . . . . . . . . . . . . . . . . . . . . . 24

Making a tower switchable or private . . . . . . . . . . . . . . . . . . . . . . . . 25Making a disk pool available or unavailable . . . . . . . . . . . . . . . . . . . . . . 26

Recovering an independent disk pool . . . . . . . . . . . . . . . . . . . . . . . . 27

Copyright IBM Corp. 2001 iii


6/36

iv iSeries: Managing disk units


7/36

Managing disk units in disk pools

Managing your disk units is a straightforward process with the help of Operations Navigator. OperationsNavigator implements a graphical view so you can see exactly where your disk units are located and

obtain configuration information about each one. Operations Navigator offers several wizards that simplifythe processes of installing a disk unit, adding a disk unit to a disk pool, replacing a disk unit, and creatinga new disk pool.

Adisk pool is an auxiliary storage pool (ASP) that contains only disk units. A disk pool allows you toconsolidate related information on groups of disk units for recovery, availability, and performance reasons.A disk pool is a software definition of how the disk units are arranged. It does not necessarily correspondto the physical placement of disk units in the server.

Once you have your disk pools and disk units configured, you can use Operations Navigator to customizeand maintain disk unit performance. Operations Navigator also gives you the ability to manageindependent disk pools to ensure your information is continuously available. To learn more about the disk

management possibilities available to you, see the following topics:

Note:In this topic the word tower is used to refer to an expansion unit, a feature that can be connectedto a system unit to provide additional storage and processing capacity.

Planning for disk managementBefore you start, make sure you can access Disk Units in Operations Navigator as well as theiSeries server through the service tools server. Also, find the right procedural checklist and a table tohelp calculate space needed to perform actions in disk pools. Finally, learn how the graphical view

helps you plan and configure disk units.

Managing disk unit configurationFind out how easy it is to combine several disk configuration procedures into one with the Add Disk

Unit and New Disk Pool wizards. Learn how to move, remove, and replace disk units to suit yourneeds. Also, find out how to delete or clear disk pool data.

Protecting data on disk units

Learn to protect your data with device parity protection and mirrored protection through OperationsNavigator.

Optimizing disk unit performanceFind out how preventing disk pool overflow, enabling automatic overflow recovery, balancing disk

pools, and starting disk compression can contribute to more efficient data management.

Managing data in independent disk poolsLearn how to create a switchable or dedicated independent disk pool. Find out how to make towers

switchable and disk pools available. Also, learn how to recover an independent disk pool.

The topics listed above give you an overview of disk management using Operations Navigator. If you need

more information, consult Backup and Recovery or Operations Navigator online help for disk units.

Planning for disk management

Changing the disk configuration of your server is a time-consuming process, so you want to plan carefullyto be as efficient as possible. Before you begin disk management using Operations Navigator, go throughthis short list to ensure you are ready.

Copyright IBM Corp. 2001 1


8/36

1. Install the Configuration and Service component of Operations Navigator so that you can access DiskUnits.

2. Make sure you can access your server from your PC in order to do disk management functions.

3. Find the right disk unit configuration checklist to use during your procedures.

4. Check your disk pool space requirements.

5. Evaluate the current configuration of the server and plan your strategy using the graphical view window

in Operations Navigator.

Return to Managing disk units in disk pools.

Accessing Disk Units in Operations NavigatorBefore you can perform any disk management tasks with Operations Navigator, you need to install theConfiguration and Service component and enable the Disk Units container. Follow these steps in order to

access the Disk Units container:

Install the Configuration and Service component

1. From the File menu of Operations Navigator select Selective Setup.

2. Follow the wizard instructions to install the Configuration and Service component.

Enable the Disk Units container

1. In Operations Navigator right-click the server connection and selectApplication Administration.

2. On the resulting window, clickOK.

3. Click the Host Applications tab.

4. ExpandOperating System/400.

5. ExpandService.

6. SelectDisk Units to have Default Access or All Object Access.

7. Click OK.

8. Restart Operations Navigator.

Access the Disk Unit container to perform all disk management functions

1. In Operations Navigator, expand My Connections (or your active environment).

2. Expand any iSeries server.

3. ExpandConfiguration and Service.

4. ExpandHardware.

5. ExpandDisk Units.

When you reach this point, you are ready to perform disk management tasks.

Return to Planning for disk management for more planning steps.

Accessing your iSeries server from your PCOperations Navigator allows you to access the iSeries server from your PC through the service tools

server (STS) to perform disk management functions at two different levels. You can access the iSeriesserver when it is fully restarted, or you can access the server when it is in dedicated service tools (DST)mode. DST provides some additional functions for disk management that are not available when theserver is fully restarted. Before you attempt to use any disk management functions, you must configure theservice tools server. If you want to access DST functions, you must also set a service IP address.

Configuring the service tools server

2 iSeries: Managing disk units


9/36

In order to access disk management functions in Operations Navigator, you must first configure the servicetools server (STS) with DST access and user profiles. For instructions to configure the service tools server,

refer to the Managing Service Tools section of the Tips for Managing and Monitoring Authority chapter in

Tips and Tools.

Setting the service IP address

In order to access DST functions on your server from Operations Navigator, you will need to specify aservice IP address for the server. The service IP address specifies the TCP/IP address of the service

system that the current physical system uses. This address takes the form xxx.xxx.xxx.xxxwhere xxx is aninteger from 0 to 255. The address can also be a Domain Name System (DNS) that resolves to anaddress as described above. Contact your network administrator for this information.

To set the service IP address for your system, follow these steps:

1. In Operations Navigator, expand My Connections (or your active environment).

2. Right-click the server for which you want to specify a service IP address, and selectProperties.

3. Click the Service tab.

4. Enter the service IP address and clickOK to enact the changes.

Once the service IP address is set, you can connect to the system when it is in DST mode by using

Operations Navigator. Simply start Operations Navigator as you normally would to connect to the system.Operations Navigator will open with a subset of functions that you can perform in DST.

Return to Planning for disk management for more planning steps.

Choosing the right procedure for configuring disksThis article contains several checklists for performing configuration procedures. Use this table to determinewhich checklist to use for your situation.

Task description Procedure to follow Requires

DST?Configure your system for the first time. Checklist 1 Yes

Add one or more disk units that will not have device parity protection. This

checklist applies to disk units that are capable of device parity protection if you

do not plan to start device parity protection for the disks.

Checklist 2 No

Add one or more disks to an existing 9337 Disk Array Subsystem if you plan to

protect the disks with device parity protection. Use this checklist if device parity

protection is already started for the 9337 Disk Array Subsystem.

Checklist 3 No

Add one or more disks to an existing Input/Output Processor (IOP) that has

built-in device parity capability. Use this checklist if you plan to protect some or

all of the new disks with device parity protection.

Checklist 4 No

Add a new IOP that has built-in device parity capability. Use this checklist if you

plan to protect some or all of the new disks with device parity protection.

Checklist 5 Yes

Move disk units between existing disk pools without mirrored protection. Checklist 6 Yes

Move disk units between existing ASPs with mirrored protection. Checklist 7 Yes

Delete a basic disk pool. Checklist 8 Yes

Remove one or more disk units without device parity protection. Checklist 9 Yes 1

Remove one or more disk units from a 9337 Disk Array Subsystem. Use this

checklist if device parity protection is started for some or all of the disks in the

9337 Disk Array Subsystem and they are in disk pools without mirrored

protection.

Checklist 10 Yes

Managing disk units in disk pools 3


10/36

Remove one or more disk units from a 9337 Disk Array Subsystem. Use this

checklist if device parity protection is started for some or all of the disks in the

9337 Disk Array Subsystem and they are in disk pools with mirrored protection.

Checklist 11 Yes

Remove one or more disk units from an IOP. Use this checklist if device parity

protection is started for some or all of the disk units that are attached to the IOP

and they are in disk pools without mirrored protection.

Checklist 12 Yes

Remove one or more disk units from an IOP. Use this checklist if device parityprotection is started for some or all of the disks units that are attached to the

IOP and they are in disk pools with mirrored protection.

Checklist 13 Yes

1 Unassigned disk units can be removed from offline independent disk pools without requiring the system to be in

DST mode.

Checklist 1: Configuring disks on a new systemThis checklist shows the sequence of tasks that you use to configure disks on a new iSeries server.Whether you need to perform all the tasks depends on the disk protection that you want on your system.Setting up disk protection for your data provides more information about the disk protection that is

available.

Attention:When you perform the tasks in this checklist, the system moves large amounts of data. Makesure that you have completely saved your system in the event that you need to recover from an errorsituation.

Before you begin, make a copy of this checklist. Check off the configuration tasks as you perform them.This checklist provides an important record of your actions. It may help you diagnose any problems thatoccur.

Most tasks in the checklist include references to other topics. Refer to these topics if you need moreinformation about how to perform a particular task.

Task What to do Where to learn more

1.___ Display your disk configuration. Currently, all of

your disk units except the load source unit appearas nonconfigured.

Using the graphical view

2.___ Use the Add Disk Unit wizard to add nonconfigured

disks to the correct disk pools. You will have the

option to start device parity protection or to start

compression, if disks are available for these

actions.

Using the Add Disk Unit and New Disk Pool

wizards

3.___ The default storage threshold for each disk pool is

90%. Change to a different storage threshold for

any disk pool, if desired.

Setting the disk pool threshold

4.___ If you chose to create protected disk pools and

included pairs of disk units to be mirrored, you may

want to restart to dedicated service tools (DST)

level and start mirroring for those disk pools now.

Working with mirroring

5.___ If you started mirrored protection for the system

disk pool or a basic disk pool, wait until your

system completely restarts.

6.___ Verify that your disk configuration is correct. Using the graphical view

7.___ Print a hard copy of your disk configuration to have

in case of a recovery situation. Backup and Recovery



11/36

Checklist 2: Adding disk units without device parity protectionThis checklist shows the sequence of tasks that you use to configure disks on a new iSeries server.

Whether you need to perform all the tasks depends on the disk protection that you want on your system.Setting up disk protection for your data provides more information about the disk protection that isavailable.

Adding to a disk pool with mirrored protection

You can add disk units to a disk pool that has mirrored protection without stopping and starting mirroredprotection. You must add disk units in pairs with equal capacities. The added units will always be paired

with each other. You may want to choose a later time, when your system can be unavailable for severalhours, to stop and start mirrored protection. When you start mirrored protection again, the systemevaluates the pairing for all disk units on your system. This may provide a higher level of availability forfailures that affect a controller, an IOP, or a bus.


Before you begin, make a copy of this checklist. Check off the configuration tasks as you perform them.

This checklist provides an important record of your actions. It may help you diagnose any problems thatoccur.

Most tasks in the checklist include references to other topics. Refer to these topics if you need moreinformation about how to perform a particular task.


1.___ Use the graphical view to find empty slots for the

disk units you want to install.


2.___ Right-click an empty slot and start the Install Disk

Unit wizard to guide you through the process.


disks to existing or new disk pools. You will havethe option to start compression or to add disk units

of equal capacity to mirror protected disk pools if

disks are available for these actions.


wizards


90%. Change to a different storage threshold for

any disk pool if desired.


5.___ If you chose to create protected disk pools and you

included pairs of disk units to be mirrored, you may

want to restart to the dedicated service tools (DST)

level and start mirroring for those disk pools now.


6.___ If you started mirrored protection for the system

disk pool or a basic disk pool, wait until your

system completely restarts.




Checklist 3: Adding disk units to a 9337 disk array subsystemThis checklist shows the sequence of tasks that you use to add one or more disks to an existing 9337

Disk Array Subsystem. Use this checklist if you plan to protect the new disk units with device parityprotection.



12/36

Attention:When you perform the tasks in this checklist, the system moves large amounts of data. Makesure that you have completely saved your system in the event that you need to recover from an error

situation.

Before you begin, make a copy of this checklist. Fill in the appropriate areas as you or the servicerepresentative perform the configuration tasks. This checklist provides an important record of your actions.

It may help you diagnose any problems that occur.

Most tasks in the checklist include links to other topics. Refer to these topics if you need more informationabout how to perform a particular task.


1.___ Physically attach disk units using the Install Disk

Unit wizard available in the graphical view.



disks to the correct disk pools. Take the option to

include disk units in a parity set.


wizards


90%. If you want a different storage threshold for

any disk pool, change it.





Checklist 4: Adding disk units to an existing input/output processorThis checklist shows the sequence of tasks that you use to add one or more disks to an existingInput/Output Processor that has built-in device parity protection. Use this checklist if you plan to protectsome or all of the new disk units with device parity protection. If you do not plan to protect any of the new

disk units, use checklist 2.

You can use this procedure whether or not you have mirrored protection on your system because you start

device parity protection before you add the disk units to a disk pool.


Before you begin, make a copy of this checklist. Fill in the appropriate areas as you or the servicerepresentative perform the configuration tasks. This checklist provides an important record of your actions.It may help you diagnose any problems that occur.

Most tasks in the checklist include link to other topics. Refer to these topics if you need more informationabout how to perform a particular task.


1.___ Physically attach disk units using the Install Disk

Unit wizard available in the graphical view.



disks to the correct disk pools. The wizard will

allow you to include the disk units that you want to

protect in device parity protection


wizards



13/36








Checklist 5: Adding a new input/output processorThis checklist shows the sequence of tasks that you use to add a new Input/Output Processor (IOP) anddisk units to your system. Use this checklist if you plan to protect some or all of the new disks with deviceparity protection.You can use this procedure whether or not you have mirrored protection on your system

because you start device parity protection before you add the disk units to a disk pool. If you do havemirrored protection and you are adding disks that do not have device parity protection, you must add themin pairs that have equal capacities.

Note:If you do not plan to start device parity protection for any of the new disks, use the procedure inchecklist 2 to add them.


Before you begin, make a copy of this checklist. Fill in the appropriate areas as you or the service

representative perform the configuration tasks. This checklist provides an important record of your actions.It may help you diagnose any problems that occur.


The following are the basic rules for starting protection for IOPs that support device parity protection:

v Maximum number of parity sets allowed: 2

v Maximum number of devices per parity set: 10

v Minimum number of devices per parity set: 4

v All devices in a parity set must be the same capacity

v The protection supports 66xx devices, not 61xx devices in parity sets or devices that use the write

cache support.

v You must remove 66xx Model 30 devices from the disk pool configuration before you start device parityprotection. This allows the system to reformat the disk for the advanced functions of the IOP. After youstart device parity protection, add the disk to the ASP configuration.


1.___ Install the new input/output processor in the server.

This is normally done by a service representative.


2.___ Physically attach disk units to the new IOP using

the Install Disk Unit wizard which you can access

from the Graphical View.



disks to the correct disk pools. Take the option to

start device parity protection.


wizards







14/36

5.___ You may want to restart to the dedicated service

tools (DST) level in order for the device parity

protection to take effect.

Working with device parity protection

6.___ Wait until your system completely restarts.

7.___ Verify that your disk configuration is correct. Using the Graphical View



Checklist 6: Moving disk units between non-mirrored disk poolsThis checklist shows the sequence of tasks that you use to move one or more disk units from one basicdisk pool to another basic disk pool. Use these tasks when you do not have mirrored protection active forthe disk pools. You must restart your server to DST mode to perform the tasks in this checklist.


Before you begin, make a copy of this checklist. Fill in the appropriate areas as you perform the

configuration tasks. This checklist provides an important record of your actions. It may help you diagnoseany problems that occur.

Most tasks in the checklist include links to other topics. Refer to these topics if you need more information

about how to perform a particular task.


1.___ Display your current disk configuration. Using the graphical view

2.___ Calculate the space requirements for both the

source and target disk pools for the disk units.

Calculating disk pool space requirements

3.___ Use option 21 from the Save menu to save your

entire system.

Saving your server with the GO SAVE command

4.___ Restart your server to dedicated service tools

(DST) mode.

5.___ From the graphical view window, right-click the disk

unit you want to move and select Move.

Maintaining disk unit configuration

6.___ Verify that your disk configuration in correct. Using the graphical view



8.___ Restart your server.

Checklist 7: Moving disk units between mirrored disk pools

This checklist shows the sequence of tasks that you use to move one or more disk units from one basicdisk pool to another basic disk pool. Use these tasks when one or more of the disk pools involved in themove has mirrored protection. You cannot use the move disk unit procedure when mirrored protection isactive. Instead, you remove mirrored pairs from the source disk pool and add them to the target disk pool.You must restart your server to Dedicated Service Tools (DST) mode to perform the tasks in this checklist.




15/36

Before you begin, make a copy of this checklist. Fill in the appropriate areas as you perform theconfiguration tasks. This checklist provides an important record of your actions. It may help you diagnose

any problems that occur.


Task What to do Where to learn more1.___ Display your current disk configuration. Using the Graphical View

2.___ Calculate the space requirements for both the

source and target disk pools for the disk units.



entire system.



(DST) mode.

5.___ In the graphical view, filter by Mirrored Pair, then

hold the Ctrl key until you have selected each disk

unit of the mirrored pair. Right-click one of the

selected disk units and select Remove.


6.___ Add nonconfigured disk units to the correct disk

pools. If you are adding disk units to a protected

disk pool and the new disk units do not have

device parity protection, you must add pairs of disk

units that have identical capacities.

Adding disk units

7.___ If you created a new disk pool when you added

disk units, the system set the storage threshold of

the disk pool to 90%. If you want a different

storage threshold for any disk pool, change it.


8.___ If you created any new disk pools and you want

those disk pools to have mirrored protection, start

mirrored protection now.


9.___ Verify that your disk unit configuration is correct. Using the graphical view



Checklist 8: Deleting a disk poolThis checklist shows the sequence of tasks that you use to delete a basic or independent disk pool. If youwant to delete or clear an independent disk pool that is unavailable, you can do so when your system isfully restarted. For all other disk pools, you will need to restart your system to DST before clearing or

deleting them.

Attention:Make sure that you have completely saved your system in the event that you need to recoverfrom an error situation. Also note that when a disk pool is deleted, all data remaining in that disk pool is

lost.







16/36


2.___ Calculate the space requirements for the remaining

disk pools.



entire system.


4.___ Remove objects from the disk pool that you are

deleting or move the objects to a different diskpool.

Backup and Recovery manual


(DST) mode.

6.___ Delete the disk pool. This procedure places all of

the disks that were assigned to the deleted disk

pool in nonconfigured status.


7.___ If you want to add the now nonconfigured disk

units to a different disk pool, refer to Checklist 2 or

3.

Checklist 2 or Checklist 3





Checklist 9: Removing disk units without device parity protectionThis checklist shows the sequence of tasks that you use to remove one or more disk units from yoursystem when the disk units do not have device parity protection. Use these tasks when you arepermanently removing disk units from your system. Do not use these tasks when you are repairing orreplacing a failed disk unit. You must restart your server to dedicated service tools (DST) mode to perform

the tasks in this checklist.

Attention:When you perform the tasks in this checklist, the system moves large amounts of data. Make

sure that you have completely saved your system in the event that you need to recover from an errorsituation.

Before you begin, make a copy of this checklist. Fill in the appropriate areas as you perform theconfiguration tasks. This checklist provides an important record of your actions. It may help you diagnoseany problems that occur.




2.___ Calculate the space requirements for the disk pools

that are involved in disk removal.



entire system.



(DST) mode.

5.___ Remove disk units that you plan to remove from

the system.





17/36



8.___ Continue restarting your server.

Checklist 10: Removing disk units with device parity protection (9337) from a disk

pool without mirrored protectionThis checklist shows the sequence of tasks that you use to remove one or more disk units from a 9337Disk Array Subsystem. Use these steps when device parity protection is active for the 9337 Disk ArraySubsystem and when the disk pools containing the disk units do not have mirrored protection. Use these

tasks when you are permanently removing disk units from your system. Do not use these tasks when youare repairing or replacing a failed disk unit. You must restart your server to dedicated service tools (DST)mode to perform the tasks in this checklist.


Before you begin, make a copy of this checklist. Fill in the appropriate areas as you or the service

representative perform the configuration tasks. This checklist provides an important record of your actions.It may help you diagnose any problems that occur.

Most tasks in the checklist include links to other topics. Refer to these topics if you need more information

about how to perform a particular task.







entire system.


4.___ Restart your server to dedicated service tools(DST) mode.


the system.


6.___ Exclude the disk units from device parity protection

in the 9337.






Checklist 11: Removing disk units that have device parity protection (9337) from adisk pool with mirrored protectionThis checklist shows the sequence of tasks that you use to remove one or more disk units from a 9337Disk Array Subsystem. These tasks apply when the disk pools containing the disk units have mirrored

protection and when device parity protection is active for the 9337 Disk Array Subsystem. Use these taskswhen you are permanently removing disk units from your system. Do not use these tasks when you arerepairing or replacing a failed disk unit. You must restart your server to dedicated service tools (DST)mode to perform the tasks in this checklist.



18/36

Attention:When you perform the tasks in this checklist, the system moves large amounts of data. Makesure that you have completely saved your system in the event that you need to recover from an error

situation.










entire system.



(DST) mode.


the system.


6.___ Stop mirrored protection for the disk pools that will

have disk units removed. When you stop mirrored

protection, one disk unit from each mirrored pair

becomes nonconfigured. You need to stop mirrored

protection only if the disk pool contains other disk

units that are attached to the 9337 Disk Array

Subsystem and have device parity protection.


7.___ Exclude the disk units from the 9337. The service

representative can perform the exclude function on

the 9337.

8.___ Add nonconfigured disk units to the correct diskpools. These disk units became nonconfigured

when you stopped mirrored protection in task 6.

Adding disk units to a disk pool

9.___ Start mirrored protection for the disk pools that had

mirrored protection stopped in task 6.





Checklist 12: Removing disk units that have device parity protection from a diskpool without mirrored protection

This checklist shows the sequence of tasks that you use to remove one or more disk units from anInput/Output Processor with built-in device parity protection. These tasks apply when the disk poolscontaining the disk units do not have mirrored protection and when device parity protection is started forthe IOP. Use these tasks when you are permanently removing disk units from your system. Do not use

these tasks when your are repairing or replacing a failed hard disk. You must restart your server toDedicated Service Tools (DST) mode to perform the tasks in this checklist.

Attention:When you perform the tasks in this checklist, the system moves large amounts of data. Make

sure that you have completely saved your system in the event that you need to recover from an errorsituation.



19/36

Before you begin, make a copy of this checklist. Fill in the appropriate areas as you or the servicerepresentative perform the configuration tasks. This checklist provides an important record of your actions.

It may help you diagnose any problems that occur.


Task What to do Where to learn more1.___ Display your current disk configuration. Using the graphical view





entire system.



(DST) mode.


the system.


6.___ Exclude the disk units from device parity

protection. If you were successful in excluding thedisk units, skip to task 8. Otherwise, continue to

task 7.


7.___ Stop device parity protection for all the disk units in

the IOP.


8.___ Physically remove disk units. If you stopped device

parity protection in task 7, then continue with task

9. If you did not stop device parity protection, then

skip to task 10.


9.___ Start device parity protection again. Working with device parity protection





Checklist 13: Removing disk units that have device parity protection from a diskpool with mirrored protectionThis checklist shows the sequence of tasks that you use to remove one or more disk units from anInput/Output Processor that is capable of device parity protection. These tasks apply when the disk poolsthat contain the disk units have mirrored protection and when the disk units have device parity protection.

Use these tasks when your are permanently removing disk units from your system. Do not use these taskswhen you are repairing or replacing a failed disk unit. You must restart your server to the dedicated servicetools (DST) mode to perform the tasks in this checklist.


Before you begin, make a copy of this checklist. Fill in the appropriate areas as you perform theconfiguration tasks. This checklist provides an important record of your actions. It may help you diagnoseany problems that occur.

Most tasks in the checklist include links to other topics in this article. Refer to these topics if you needmore information about how to perform a particular task.



20/36







entire system.



(DST) mode.


the system.


6.___ Exclude the disk units from device parity

protection. If you were successful in excluding the

disk units, skip to task 9. Otherwise, continue to

task 7.


7.___ Stop mirrored protection for the disk pools that will

have disk units removed. When you stop mirrored

protection, one disk unit from each mirrored pair

becomes nonconfigured. You need to stop mirrored

protection only if the disk pool contains other diskunits that are attached to the IOP and have device

parity protection.


8.___ Stop device parity protection for all the disk units in

the IOP.


9.___ Physically remove disk units. This is normally done

by a service representative. If you stopped device

parity protection in task 8, then continue with task

10. If you did not stop device parity protection, then

skip to task 14.

10.___ Start device parity protection again. Working with device parity protection

11.___ Add nonconfigured disk units to the correct disk

pools. These disk units became nonconfiguredwhen you stopped mirrored protection in task 7.

Adding disk units to a disk pool

12.___ If you created a new disk pool on your system

when you added disk units, the system set the

storage threshold of the disk pool to 90%. If you

want a different storage threshold for any disk pool,

change it.


13.___ Start mirrored protection for the disk pools that had

mirrored protection stopped in task 7.

Working with Mirroring




Calculating disk pool space requirementsWhen you are planning to make changes to the disk configuration or the disk protection on your system,

you need to calculate the space requirements for the change before you begin. You want to ensure thatyour system has sufficient disk storage for the changes.

Below is an example of a worksheet that you can use to calculate your requirements. The following topics

describe the steps for completing the worksheet.



21/36

Worksheet for calculating disk pool capacity

Type of storage Current storage Interim storage Final storage

Disk pool: 1

Total used

Total capacity

Percent used

Disk pool: 2

Total

Total capacity

Percent used

Task 1: Calculating the current storage usedFollow these steps to determine how your current system configuration uses the disk capacity.

1. In Operations Navigator, expand Disk Units.

2. ExpandDisk Pools.3. Right-click the source disk pool for which you want to determine space requirements.

4. Select the Capacity tab.

The Capacity tab shows you the used space, free space, total capacity, and percentage used.

You can also use Management Central to monitor disk usage and disk storage on your servers.

On the disk pool capacity worksheet record the following values.

1. Record the total used space. This example uses 1.82 GB (where GB equals 1 000 000 000 bytes).

2. Record the total capacity of the disk pool. This example uses 3.8 GB.

3. Record the percent used. This example uses 47%.

Example 1: Calculating disk pool capacity


Disk pool: 1

Total used 1.82 GB

Total capacity 3.8 GB

Percent used 47%

Task 2: Calculating storage needed

Some changes that you make to your disk configuration require work space on the system. For example, ifyou move a disk unit from one disk pool to another, the system must copy the information from the disk

unit to the other disk units in the source disk pool.

Refer to Example 2 and do the following steps to determine the amount of interim space required by thesystem for this procedure. Fill in the worksheet as you go:

1. From the disk pool display for your source disk pool, determine the disk unit capacities for those youplan to move. The disk units in the example have capacities of .7 GB and 1.1 GB..7 GB + 1.1 GB = 1.8 GB



22/36

2. Subtract the total from step 1 from the total capacity of the disk pool:3.8 GB - 1.8 GB = 2.0 GB

3. Determine what the interim-percent-used amount will be. Divide the total used storage by the amountfrom step 2.1.82 GB / 2.0 GB = 91% used

4. Estimate the amount of data that you will move from the source disk pool to the target disk pool. Forexample, if you plan to move a library you would use one of the following:

v The DSPLIB LIB (library-name) OUTPUT(*PRINT) command

v The QLIRLIBD API

5. Subtract the amount in step 4 from the total storage used for the source disk pool. Add it to the targetdisk pool. For purposes of this example, assume you are moving several large libraries whose sizetotals 200 MB.1.82 GB - .2 GB = 1.62 GB Final storage capacity used

Example 2: Calculating disk pool capacity


Disk pool: 1

Total used 1.82 GB 1.82 GB 1.62 GB

Total capacity 3.8 GB 2.0 GB 2.0 GB

Percent used 47% 91% 81%

Disk pool: 2

Total used 200 MB

Total capacity 1.8 GB

Percent used 10.88%


Before you change the disk configuration of your server, it is important to know exactly where the existingdisk units are located in relation to disk pools, I/O processors, and towers. The graphical view of

Operations Navigator eliminates the painstaking process of compiling all this information. The graphicalview shows you a graphic of how your server is configured. You can choose to view the information bydisk units, by disk pools, by tower, or by I/O processor. You can right-click a particular disk unit or diskpool to obtain a list of its properties. Properties include such things as serial numbers, the storage capacity

used, type of protection, and the disk pool threshold.

You can also perform actions from within the graphical view. If you right-click a disk unit, you can selectfrom a list of actions to perform. For example, you can start or stop compression on the disk unit, include

the disk unit in a parity set, and suspend or resume mirroring if the disk unit has mirrored protection. If youright-click an empty disk unit slot, you can start the Install Disk Unit wizard.

To activate the graphical view, follow these steps:1. In Operations Navigator, expand Disk Units.

2. Right-click All Disk Units, and select Graphical View.



23/36

Figure 1: Example of the Graphical View in Operations Navigator. The View by drop-down menulists several options for viewing disk units.

To find more information about the graphical view, consult the online help for disk units.


Managing disk unit configuration

The Add Disk Unit and New Disk Pool wizards simplify the process of initially configuring your disk units.As your storage needs change you can use Operations Navigator to move, remove, and replace diskunits. The interface also allows you to clear or delete disk pools when you no longer need the informationcategorized in that way. As a part of maintenance you can also rename, format, or scan disk units.



24/36

Note:Before changing the disk configuration of your server, you should have already read Planning fordisk management. Planning is necessary to determine which procedural checklist to use and to calculate

disk pool space requirements.

To learn about adding disk units and disk pools as well as maintaining disk unit configuration see thefollowing:

v Adding disk units or disk pools

v Maintaining disk unit configuration


Adding a disk unit or disk poolThe Add Disk Unit and New Disk Pool wizards save you time by bundling several time-consuming

configuration functions into one efficient process. They also take the guesswork out of disk unitconfiguration because they understand the capabilities of your system and only offer valid choices. Forinstance, the wizard will not list the option to start compression unless your server has that capability.

Both the Add Disk Unit and New Disk Pool wizards allow you to create a basic or independent disk pool or

to use an existing disk pool to add new or nonconfigured disk units. When you choose to add disk units to

a protecteddisk pool, the wizard forces you to include the disk units in device parity protection or to addenough disk units of the same capacity to start mirrored pair protection. The wizard also gives you theoption of balancing data across the disk pool or starting disk compression if these are permissible actions

for your system configuration. You decide which options to choose so that the operation is tailored to yoursystem.

Note:Before changing the disk configuration of your server, you should have already read Planning for

disk management. Planning is necessary to determine which procedural checklist to use and to calculatedisk pool space requirements.

To use the Add Disk Unit and New Disk Pool wizards, follow these simple steps:


2. To add disk units, right-clickAll Disk Units and select Add Disk Unit.3. To create a new disk pool, right-clickDisk Pools and select New Disk Pool.

4. Follow the instructions in the wizard to complete the task.

Return to Managing disk unit configuration.

Maintaining disk unit configurationOperations Navigator gives you the flexibility to move disk units to other disk pools or replace a failed diskunit in an existing disk pool. You can delete a disk pool or clear data from a disk pool. You can alsorename, format, and scan disk units.

Note:Before changing the disk configuration of your server, you should have already read Planning for

disk management. Planning is necessary to determine which procedural checklist to use and to calculatedisk pool space requirements.

Moving and removing disk units

As your storage needs change, you can select to move a disk unit from one disk pool to another disk pool.When you move a disk unit, the server first moves all of the data on that disk unit to other disk units in the

original disk pool. You cannot move disk units to or from an independent disk pool. For disk units insystem and basic disk pools, you need to restart your system to dedicated service tools (DST) modebefore moving them.



25/36

When you remove a disk unit, the server redistributes the data on that disk unit to other disk units in thedisk pool. If you want to remove a disk unit from an independent disk pool that is unavailable, you can do

so when your system is fully restarted. For all other disk pools, you need to restart your system to DSTbefore removing them.

Depending on disk unit capacity and performance, the Move or Remove process can take from several

minutes to over an hour to complete, potentially affecting system performance.

To move or remove a disk unit from a disk pool, follow these steps:


2. Right-click the disk unit you want to move and selectMove or Remove.

3. Follow the instructions on the resulting dialog.

Replacing a disk unit

If you need to replace a failed disk unit or exchange a disk unit to prevent failure, the Replace Disk Unitwizard makes the process a simple task. The disk unit to be replaced or exchanged must be running witheither mirrored protection (must be suspended) or device parity protection. A disk unit that is running with

device parity protection can be exchanged only if it has failed. A disk unit running with device parity

protection cannot be replaced with a nonconfigured disk even if it has failed.

To replace a failed disk unit or exchange a suspended mirrored unit, follow these steps:


2. Select All Disk Units.

3. Right-click the disk unit that you want to replace and selectReplace Disk Unit.

4. Follow the wizards instructions to replace the failed disk unit.

Deleting or clearing data from a disk pool

If you never need to access the data in a disk pool again, you can choose to clear the disk pool or deletethe disk pool. Both actions destroy all data on the disk units in the pool. If you choose to clear the disk

pool, the disk units are still available for new data storage. If you delete the disk pool all disk units areremoved and you can no longer access the disk pool. If you want to delete or clear an independent diskpool that is unavailable, you can do so when your system is fully restarted. For all other disk pools, you

need to restart your system to DST mode before clearing or deleting them.

To delete or clear a disk pool, follow these steps:


2. ExpandDisk Pools and select the disk pools you want to clear.

3. Right-click a selected disk pool and select Clear or Delete.

4. Follow the instructions on the dialog that displays.

Renaming a disk unit

Operations Navigator gives you the option of changing the default disk unit name to something more

helpful to you. For instance you could change Dd001 to LoadSource. You cannot specify names withspaces in them.

To rename the disk unit, follow these steps:


2. Select the disk unit you want to rename.

3. Right-click the disk unit and selectRename.



26/36


Formatting a disk unit

You can select to clear all data from a nonconfigured disk unit and write the sectors, which prepares thedisk unit for use in an iSeries server. Depending on disk unit capacity and performance, formatting a disk

unit can take from several minutes to over an hour to complete, potentially affecting system performance.

To format a disk unit, follow these steps:


2. Right-click the disk unit you want to format and selectFormat.


Scanning a disk unit

You can select to simply scan a disk unit to check the surface of the disk units and correct any sectorswith errors. Depending on disk unit capacity and performance, scanning a disk unit can take anywherefrom several minutes to over an hour to complete, potentially affecting system performance.

To scan a disk unit, follow these steps:1. In Operations Navigator, expand Disk Units.

2. Right-click the disk unit you want to scan and selectScan.


Return to Managing disk unit configuration.

Protecting data on disk units

To obtain optimal data protection, use Operations Navigator to protect all the disk units on your systemwith either device parity protection or mirrored protection. This prevents the loss of information when a diskfailure occurs. In many cases, you can keep your system running while a disk unit is being repaired or

replaced.v Working with device parity protection

v Working with mirrored protection

Visit Setting up Disk Protection for more conceptual information about device parity protection and

mirrored protection.

Working with device parity protectionDevice parity protection uses a data redundancy technique that protects data by spreading the parity data

across multiple disk units in the parity set. When a failure occurs on a disk unit that has device parityprotection, the data is reconstructed.

Starting device parity protection

The best time to start device parity protection is when you add new or nonconfigured disk units. The AddDisk Unit wizard has steps for including disk units in a parity set and starting device parity protection. It isalso possible to start device parity protection at a later time.

To start device parity protection (if you did not do this step with the Add Disk Unit wizard), follow thesesteps:


2. Select the disk units for which you want to start device parity protection.



27/36

3. Right-click a selected disk unit and selectStart Parity.

4. From the resulting dialog, clickStart Parity to start device parity protection on the displayed disk units.

Stopping device parity protection

You can select to stop device parity protection on the displayed disk units. The list displays all of the disk

units in the parity set. When preparing to stop device parity protection, the system performs validity

checking to make sure that stopping device parity protection does not leave the system in a configurationthat is not supported. Depending on disk unit capacity and performance, stopping device parity protectioncan take from several minutes to over an hour to complete, potentially affecting system performance.

You cannot stop device parity protection on a disk unit that is in a mirrored disk pool. To stop device parityprotection, you must first stop mirrored protection.

To stop device parity protection on the disk units in a parity set, follow these steps:


2. Select the disk units for which you want to stop device parity protection.

3. Right-click a selected disk unit and selectStop Parity.

4. From the resulting dialog, clickStop Parity to stop device parity protection.

Including or excluding disk units from a parity set

You can select which disk units you want to include in a parity set. When you attach a new disk unit to anexisting I/O processor that has device parity protection, you can include the disk unit in a device parity setwith other disk units of the same capacity. The I/O processor determines the fewest number of parity setsneeded to protect all the disk units of the same capacity.

You can also select which disk units you want to exclude from the parity set. When you exclude a disk unitfrom the parity set, the data on this disk unit remains there but is no longer protected by device parityprotection. If the disk pool is protected, you are not allowed to exclude a disk unit that belongs to that disk

pool from a parity set. The system does not allow unprotected disk units to reside in a protected disk pool.

If you want to include or exclude a disk unit from an independent disk pool that is unavailable, you can doso when your system is fully restarted. For all other disk pools, you need to restart your system to

dedicated service tools (DST) mode before including or excluding them from a parity set.

To include a disk unit in a parity set, follow these steps:


2. Select the disk units that you want to include.

3. Right-click a selected disk unit and select Include in Parity Set.

4. From the resulting dialog, clickInclude to include the selected disk units in a parity set.

To exclude a disk unit from a parity set, follow these steps:


2. Select the disk units that you want to exclude.

3. Right-click a selected disk unit and select Exclude from Parity Set.

4. From the resulting dialog, clickExclude to exclude the disk units from a parity set.

For more conceptual information about device parity protection, visit Device parity protection.



28/36

Working with mirrored protectionMirrored protection is beneficial if you have a multibus server or a server with a large single bus. A greaternumber of disk units provides more opportunity for failure and increased recovery time. Mirrored protectionworks to prevent outage on the server by keeping a second copy of the data on a mirrored disk unit. If onedisk unit fails, the server relies on the mirrored disk unit.

Starting mirrored protection

The Add Disk Unit and New Disk Pool wizards guide you through the process of adding pairs of identicalcapacity disk units to a protected disk pool. When you have your disks configured correctly, you are ready

to start mirroring. If you want to start mirroring on an independent disk pool that is unavailable, you can doso when your system is fully restarted. For all other disk pools, you need to restart your system to thededicated service tools (DST) mode before starting mirrored protection.

To start mirroring, follow these steps:


2. ExpandDisk Pools.

3. Right-click the disk pools you want to mirror, and selectStart Mirroring.

Stopping mirrored protection

When you stop mirrored protection, one unit from each mirrored pair becomes nonconfigured. Before youcan stop mirrored protection for a disk pool, at least one unit in each mirrored pair in that disk pool mustbe present and active. To control which mirrored unit of each pair becomes nonconfigured, you maysuspend the storage units that you want to become nonconfigured. For units that are not suspended, theselection is automatic.

If you want to stop mirroring on an independent disk pool that is unavailable, you can do so when yoursystem is fully restarted. For all other disk pools, you need to restart your system to the dedicated servicetools (DST) mode before stopping mirrored protection.

To stop mirrored protection, follow these steps:1. In Operations Navigator, expand Disk Units.


3. Select the disk pools you want to mirror.

4. Right-click any selected disk pool, and selectStop Mirroring.

5. Click Stop Mirroring from the resulting confirmation dialog.

Enabling remote load source mirroring

You may also want to consider using Operations Navigator to enable remote load source mirroring. This

action makes it possible for the two disk units of the load source mirrored pair to be on different I/Oprocessors or system buses. Remote load source mirroring allows you to protect against a site disaster by

dividing the disk storage between the two sites, mirroring one site to another.

To enable remote load source mirroring, follow these steps:



3. ExpandDisk Pool 1.

4. Right-click the load source disk unit and selectEnable Remote Load Source Mirroring.



29/36

Note:Enabling remote load source mirroring does not start mirrored protection on the disk units. Remoteload source mirroring affects only the load source disk units.

Suspending mirrored protection

If a disk unit in a mirrored pair fails, you will need to suspend mirroring to repair or replace it. If you want

to suspend mirroring on an independent disk pool that is unavailable, you can do so when your system is

fully restarted. For all other disk pools, you need to restart your system to the dedicated service tools(DST) mode before suspending mirroring.

To suspend mirrored protection, follow these steps:


2. Double-clickAll Disk Units.

3. Select the disk unit for which you want to suspend mirrored protection.

4. Right-click the selected disk unit and selectSuspend Mirroring.

For more conceptual information about mirroring, visit Mirrored protection.

Optimizing disk unit performanceHere you will find an overviews and procedures for using several tools available through Operations

Navigator that can help you manage your data more efficiently. The Backup and Recovery manualand the online help for disk units contain more detailed information.

Setting the threshold of a disk pool

You can eliminate recovery problems that occur when a disk pool overflows by setting a disk pool

threshold. When the data stored in the disk pool exceeds the specified threshold, the server sends awarning message, allowing you time to add more storage space or delete unnecessary objects. Thedefault threshold of a disk pool is set to 90%. You can change this value by dragging a pointer up or down

the threshold scale.

To change the threshold of a disk pool, follow these steps:


2. Right-click the disk pool for which you want to change the threshold and selectProperties.

3. From the Threshold tab, increase or decrease the threshold for the disk pool.

Enabling automatic overflow recovery

If a basic disk pool fills up and the data in the basic disk pool overflows into the system disk pool, thebasic disk pool is said to be in an overflowed state. If you enable automatic overflow recovery, you canrecover the data that overflowed to the system disk pool by performing a normal restart of your system. If

you have created sufficient space in the basic disk pool, the system will copy the overflowed data to thedisk pool from the system disk pool. If automatic overflow recovery is disabled, you will need to manually

restart your server to the dedicated service tools (DST) mode and recover the overflowed data using DSTfrom the command prompt.

To enable automatic overflow recovery, follow these simple steps:

1. ExpandDisk Pools and select the disk pools on which you want to enable automatic overflowrecovery.

2. Right-click a selected disk pool and select Enable Overflow Recovery.




30/36

Balancing a disk pool

You can improve the server performance by ensuring that the disk units in the disk pool have equalpercentages of data residing on them. The capacity balancing function ensures that the disk units in thedisk pool are balanced. You can balance a disk pool when you use the Add Disk Unit or New Disk Poolwizards. To customize your system with usage balancing or hierarchical storage management (HSM)

balancing, consult Backup and Recovery.

You have two ways to balance the capacity of disk pools using Operations Navigator:

v Use the Add Disk Unit wizard.

v Use the New Disk Pool wizard.

Starting disk compression

Compression increases the apparent capacity of disk units by encoding the data to take up less physicalstorage space. Compression does affect performance because of the overhead required to compress anddecompress the data. You may choose to compress data that you access infrequently or that does not

require high I/O performance rates. If you want to compress a nonconfigured disk unit or a disk unit in an

independent disk pool that is unavailable, you can do so when your system is fully restarted. For all otherdisk pools, you need to restart your server to the DST mode before compressing them.

To start disk compression, follow these steps:

1. ExpandAll Disk Units.

2. Select the disk units that you want to compress.

3. Right-click a selected disk unit and selectStart Compression.

4. Follow the the instructions on the resulting dialog to start compression on the selected disk units.


Managing data in independent disk poolsAn independent disk pool gives you the flexibility to perform some disk management functions while theserver is fully restarted, as long as the tasks are performed within the independent disk pool that is variedoff. An independent disk pool can also save processing time during a system restart or reclaim storage ifyou choose to keep large amounts of data that are not used for day-to-day business processing offline.

You can increase your flexibility by creating a switchable independent disk pool in a clustered environment,or you can make use of these benefits with an independent disk pool dedicated to one server.

Creating a switchable independent disk pool

Before you can create a switchable independent disk pool with the New Disk Pool wizard, you need to dosome careful planning for your cluster. You need to consider not only your current needs, but also futureneeds and the potential to include more nodes in a cluster. If you plan to use a system in the future toaccess the switchable independent disk pool, you need to include that system in the device domain.

Once you have thought through the process, follow these steps to create a switchable independent diskpool. You can create a simple two-node cluster using the clustering functions of Operations Navigator oryou can use application program interfaces (APIs) that are linked to below:

1. Create the cluster with desired nodes.

2. Create the device domain for all nodes nodes involved in switching an independent ASP or set ofindependent ASPs.



31/36

3. Create the device descriptions on each node or partition that will be in the cluster resource group(CRG). On the command line in the character-based interface, enter CRTDEVASP (Create Device

Description ASP). In the Resource Name field, enter the name of the independent disk pool you planto create.

4. Create the CRG with the nodes, their roles in the recovery domain, and independent disk poolresources.

5. Make the towers switchable or the buses shareable as your configuration requires.

6. Create the switchable independent disk pool on the node that owns the disk units using the New DiskPool wizard when the server is fully restarted. Make sure clustering is active before you start. Name

the independent disk pool to match the device description resource name that you gave in step 3. Asyou add disk units, it is best to localize disk units in the same tower or IOP. Also, do not spread thedisk pool across device parity sets.

7. Now you can make the independent disk pool available or unavailable as you choose.

Note:Add independent disk pools when your server is fully restarted. If you must use the New Disk Poolwizard at the dedicated service tools (DST) level, you need to make sure the independent disk pool namecorresponds to the device description resource name. The server cannot ensure that you choose the

correct disk units for the independent ASP.

Creating a dedicated independent disk pool

Creating a dedicated independent disk pool does not require as much planning as a switchable

independent disk pool. However, you should still take the time to make sure that your future needs will notrequire you to be able to switch the independent disk pool.

To create a dedicated independent disk pool, access the New Disk Pool wizard. As you add disk units, do

not spread the disk pool across device parity sets.

Note:Add independent disk pools when your server is fully restarted. If you must use the New Disk Poolwizard at the dedicated service tools (DST) level, you need to make sure the independent disk pool name

corresponds to the device description resource name.

If you begin to experience problems accessing an independent disk pool, the configuration source may becorrupted or its mirrored disk unit may be damaged. Learn how to attempt to recover it.

For more information about clusters, visit the Clusters topic.


Making a tower switchable or privateAn independent disk pool can contain disk units within several towers. If you have a standalone tower thatcontains disk units included in an independent disk pool, you must authorize the tower to grant access to

other servers. This is called making a tower switchable. If you do not want other servers to be able toaccess the standalone tower, you must make the tower private.

To make a tower switchable or private, follow these instructions:


2. ExpandBy Location and select the tower you want to make switchable.

3. Right-click a selected tower and select Make Private or Make Switchable.


Note:If you receive an error when you attempt to make the tower switchable or private, refer to Errorcodes when making towers switchable.



32/36

Error codes when making towers switchable

Error code Error that occurred

ffffffffffffff82 A hardware failure occurred during the processing of your request. Check the problem log

for errors.

ffffffffffffffCE A failure occurred during the processing of your request. Check the problem log for errors.

Contact your next level of support.

fffffffffffffE9E You can only change the switch mode of a tower from the system that owns the tower. Also,

the system power control network (SPCN) must own the tower.

fffffffffffffE9F The tower does not have a specified owner.

fffffffffffffEA0 You can only change the switch mode of a tower from the system that owns the tower. Also,

the system power control network (SPCN) must own the tower.

fffffffffffffEA1 You can only change the switch mode of a tower when the tower is owned by the system

power control network (SPCN) system.

fffffffffffffEBA The bus adapter hardware in the tower does not support switching.

fffffffffffffEB5 The tower does not contain the most current the system power control network (SPCN)

code.

fffffffffffffEB6 The current high-speed link (HSL) configuration is not complete. Check the problem log for

errors.

fffffffffffffEB7 The current high-speed link (HSL) configuration is not valid. Check the Problem Activity Log

for errors.

fffffffffffffEB8 The storage area network (SAN) manager must exist (the tower is in a high-speed link

(HSL) cluster) and it must be enabled and operational in order to change private mode to

switchable mode.

fffffffffffffEB9 A system power control network (SPCN) failure occurred during the processing of your

request. Check the problem log for errors.

fffffffffffffED2 The tower must not have any buses with a primary-partition or a secondary-partition load

source disk unit.

fffffffffffffEFD The tower is owned by a system that has logical partitions (LPAR) enabled. In an LPAR

environment with high-speed link (HSL) configuration, all of the buses in the tower must beowned by a single partition.

fffffffffffffF00 The tower is owned by a system that has logical partitions (LPAR) enabled. In an LPAR

environment with high-speed link (HSL) configuration, all of the buses in the tower must be

owned by a single partition.

fffffffffffffF9A Your request cannot be performed because a Cluster Resource Group (CRG) in the tower is

active. End the active CRG and try your request again.

Making a disk pool available or unavailableTo access the disk units in an independent disk pool you must vary on the disk pool. You can vary on the

independent disk pool to the current node or to another node in the cluster. The independent disk pool can

only be varied on to one node at a time. When you want to access the independent disk pool from adifferent node, you must first vary off the disk pool from the current node. Then you must switch theindependent disk pool to to the new cluster node. Refer to the online help topic, Switch cluster resources

from the primary node to the backup node, for more information on switching.

To make an independent disk pool available or unavailable with Operations Navigator, follow these steps:


2. To make a disk pool available, right-click the unavailable disk pool and selectMake Available.

3. To make a disk pool unavailable, right-click the available disk pool and selectMake Unavailable.

4. Follow the directions in the resulting dialogue to complete the action.



33/36

Note:If the independent disk pool currently has jobs running on it, you cannot vary it off from OperationsNavigator.

If you cannot vary off the independent disk pool from Operations Navigator because you have jobsrunning, use the character-based interface and follow these instructions:

1. At the command line, enter VRYCFG (Vary Configuration).

2. In the Configuration object field, type the name of the independent disk pool.

3. In the Type field, type *DEV.

4. In the Status field, type *OFF.

5. Press Enter.

6. In the Forced vary off field that appears on the next screen, type *YES.

Recovering an independent disk poolIf you begin to experience problems accessing an independent disk pool or making it available, theconfiguration source may be corrupted or its mirrored disk unit may be damaged. The configurationsource is a disk unit that contains information about all the disk units in the disk pool. When it is corrupted,the disk pool appears to have no disk units in it.

If the configuration source is corrupted, you can attempt to recover the configuration information. Therecovery operation tries to determine the original configuration and recover it.

Attention:During this process, the independent disk pool may need to be cleared, destroying all data onthe disk units in the pool. If the disk pool needs to be cleared, a message displays warning you of this andallowing you to cancel the recovery.

To attempt to recover an independent disk pool, follow these steps:


2. Right-click the independent disk pool that has the configuration problem. If Operations Navigatordetects one of the problems listed above, then Recover Configuration or Recover Unknown

Configuration Source appears in the list. If you see either of these options, select it to continue.


Return to Managing data in independent disk pools.



34/36



35/36


36/36

Printed in U.S.A.

Documents

Managing Disk Units