Configuring DS8000 HyperSwap with independent auxiliary storage pools (IASPs)

Edit online

In an IASP-based HyperSwap® configuration, both HyperSwap and logical unit (LUN) switching must be configured.

As with most other operations, any secondary IASPs are defined in the same HyperSwap relationship as the associated primary IASP. It is not possible to split primary and secondaries into separate relationships. You can define separate relationships for different primary or UDFS IASPs.

For IBM® i high availability solutions that use DS8000® HyperSwap, detection of the HyperSwap configuration is automatic after the DS8000 is appropriately configured.

The steps assume knowledge of configuring and managing an IBM System Storage DS8000. For information about using an IBM System Storage DS8000 unit, see Copy Services in the IBM System Storage DS8000 Information Center.

To configure HyperSwap, follow these steps:
  1. Create LUNs on the source DS8000.
  2. Verify the HyperSwap configuration with the Display HyperSwap Status (DSPHYSSTS) command.
  3. Assign LUNs on the source DS8000 to the System i partition.
    Note: The IASP LUNs must be in separate volume groups than any SYSBAS LUNs on both the source and target DS8000.
  4. Create LUNs on the target DS8000. Do not assign them to the IBM i until after Metro Mirror is configured.
    Note: The IBM i device driver ensures data consistency for HyperSwap switchover and failover operations. Recommend that Metro Mirror consistency groups should not be used.
  5. Configure Metro Mirror between the source and target DS8000 with the mkpprcpath command within the PASE environment.
  6. Start Peer-to-Peer Remote Copy (PPRC) with the mkpprc command within the PASE environment.
  7. Assign the LUNs on the target DS8000 to the same IBM i partition.
Do the following to set up the LUN level switching in an IASP-based HyperSwap environment on the IBM i partition:
  1. Pause PPRC with the pausepprc command within the PASE environment.
  2. Create the IASP with the Configure Device ASP (CFGDEVASP) command.
  3. To see the units for the IASP, use the Display HyperSwap Status (DSPHYSSTS) command.
  4. Resume replication with the Change HyperSwap Status command, CHGHYSSTS OPTION(*START) ASPDEV(iasp-name).
  5. Create the cluster, device domain, and device CRG to control the switching. All nodes in the recovery domain of the device CRG must be in the same device domain.
  6. Create the ASP device description on the backup node.
  7. Use the Add ASP Copy Description (ADDASPCPYD) command to configure both LUN level switching and HyperSwap. The nodes, host connections, and volume groups, which can access the IASP are entered in the recovery domain parameter. The storage host information, LUN ranges, and recovery domain information for the second DS8000 in the HyperSwap relationship are entered by using the STGHOST2, LUN2, and RCYDMN2 parameters.
  8. Create an ASP copy description for every ASP device that is to use LUN level switching with HyperSwap. All ASP devices in the cluster resource group must be defined by a separate ASP copy description.
  9. Verify the HyperSwap configuration with the Display HyperSwap Status (DSPHYSSTS) command and the correct ASP copy description configuration with the Display ASP Copy Description (DSPASPCPYD) command.
Do the following to add units to an existing IASP in a HyperSwap environment:
  1. For the new disk units to be added to the IASP, pause PPRC with the pausepprc command within the PASE environment.
  2. Stop replication with the Change HyperSwap Status command, CHGHYSSTS OPTION(*STOP) ASPDEV(iasp-name).
  3. Add the new units to the IASP with the System Service Tools (STRSST) command.
  4. To see the units for the IASP, use the Display HyperSwap Status (DSPHYSSTS) command.
  5. Resume replication with the Change HyperSwap Status command, CHGHYSSTS OPTION(*START) ASPDEV(iasp-name).