Troubleshooting
Problem
This document provides an example of how to configure a basic 2-node geographic mirroring environment.
Resolving The Problem
Document Guidelines
This document uses the following formats in order to provide working examples of a configuration:
Pre-Configuration Steps
Before configuring and testing a new geographic mirroring environment, it is advised to perform the following:
The following steps assume that the referenced PowerHA PTFs are applied in the environment:
This document uses the following formats in order to provide working examples of a configuration:
- Text in <brackets> indicates a user-defined field. These parameters can be defined, depending on system values and, or customer naming conventions.
- Subsequent values in BOLD show example values placed in those fields.
Pre-Configuration Steps
Before configuring and testing a new geographic mirroring environment, it is advised to perform the following:
- Check the system destined to become the mirror node and be certain that no IASP resources exist.
- Check to be sure all current PTFs related to PowerHA, clustering, and geographic mirroring are installed on both systems.
- Use the Planning Checklist for Clusters as found on the IBM i documentation site.
- Consider reducing the amount of time it takes to perform the CFGGEOMIR command by preparing the non-configured target disk units. Prepare the target disk units by going into service tools and deleting the disk unit data (STRSST, option 3, option 3, option 5). It should be noted that this can only be performed on non-configured disk units. Deleting the disk unit data will take some amount of time.
- If the target mirror node is using internal NVMe drives, then its namespaces need to be created before the CFGGEOMIR is issued on the source. See step 1 of document 6472897: "Creating NVMe namespaces and adding them to an ASP"
Configuration
*Important Note: With the December 2020 PowerHA PTFs SI74865 (R740) and SI74921 (R720 & R730), PowerHA simplified the configuration Geographic Mirror. You can watch a video here: Deploying PowerHA Geographic Mirror
*Important Note: With the June 2021 PowerHA PTFs SI76617 (R740) and SI76565 (R720 & R730), PowerHA added and changed some default parameters to simplify the deployment and start of Geographic Mirror.
The following steps assume that the referenced PowerHA PTFs are applied in the environment:
Step 1 - Create Cluster and Start Cluster Nodes
From the primary node: CRTCLU CLUSTER(<ClusterName>) NODE((<PrimaryNodeName> (<PrimaryNode_IP_Interface>)) (<BackupNodeName> (<BackupNode_IP_Interface>)))
Note: It is good practice use dedicated lines for cluster communications
Example:
CRTCLU CLUSTER(TWINCLU) NODE((MPLS (111.22.3.4)) (STPAUL (111.22.33.4)))
Note: The creation of the cluster automatically starts the cluster nodes and adds them into an auto created device domain.
Ensure both nodes are active by using the DSPCLUINF command, or WRKCLU, Opt.6.
Step 2 - Create the cluster administrative domain (This step is optional and depending on the use of administrative domain)
From the primary node: CRTCLU CLUSTER(<ClusterName>) NODE((<PrimaryNodeName> (<PrimaryNode_IP_Interface>)) (<BackupNodeName> (<BackupNode_IP_Interface>)))
Note: It is good practice use dedicated lines for cluster communications
Example:
CRTCLU CLUSTER(TWINCLU) NODE((MPLS (111.22.3.4)) (STPAUL (111.22.33.4)))
Note: The creation of the cluster automatically starts the cluster nodes and adds them into an auto created device domain.
Ensure both nodes are active by using the DSPCLUINF command, or WRKCLU, Opt.6.
Step 2 - Create the cluster administrative domain (This step is optional and depending on the use of administrative domain)
From the primary node: CRTCAD ADMDMN(<Admin Domain Name>)
Example:
CRTCAD ADMDMN(ADMDMN)
Step 3 - Populate the cluster administrative domain
Using the ADDCADMRE command, Monitored Resource Entries can be added into admin domain. The most commonly used MRE Resource Types will be used in the example. Starting in R740, performing this task on a brand new installation automatically creates PowerHA policies for creating, deleting and restoring MRE objects. To read more about PowerHA policies, click HERE.
From the primary node: ADDCADMRE RESOURCE(*ALL) RSTTYPE(<Type to be Added>)
Example:
ADDCADMRE RESOURCE(*ALL) RSTTYPE(*USRPRF)
ADDCADMRE RESOURCE(*ALL) RSTTYPE(*AUTL)
Step 4 - Create Independent ASP (IASP), also referred to as an Independent Disk Pool
Note: This step can be skipped, if the IASP exists. This might be true in environments using geographic mirroring for the first time, but the IASP had already been in use.
To create the IASP from a command-line interface from the primary node:
CFGDEVASP ASPDEV(<IASP_Name>) ACTION(*CREATE)
Example:
CFGDEVASP ASPDEV(TWINIASP) ACTION(*CREATE)
Notes:
1. Specify the name of the IASP here. A device description by the same name will be created on the primary node.
2. If specifying UNITS(*SELECT), it will be prompt with a list of non-configured disks to add to the IASP.
Step 5 - Create the Device CRG (Cluster Resource Group), but do NOT start the CRG yet
Perform the following on the primary node (not required, but to keep things consistent):
CRTCRG CRG(<DevCRGName>) CRGTYPE(*DEV) RCYDMN((MPLS *PRIMARY *LAST <PrimarySiteName> (<DataPort_IP_Address>)) (STPAUL *BACKUP 1 <BackupSiteName> (<DataPort_IP_Address>))) CFGOBJ((<Name of IASP> *DEVD *ONLINE))
Example:
CRTCRG CRG(TWINCRG) CRGTYPE(*DEV) RCYDMN((MPLS *PRIMARY *LAST MPLS (111.22.3.5)) (STPAUL *BACKUP 1 STPAUL (111.22.13.5)) CFGOBJ((TWINIASP *DEVD *ONLINE))
Notes:
1. The above example assumes the IASP production copy will initially and preferably be owned by node MPLS, with node STPAUL owning the mirror copy of the IASP.
2. The Data Port IP addresses listed above are examples. It is advised to use different IP addresses than what is being used for clustering, or this can create problems with cluster communications.
Step 6 - Configure Geographic Mirroring
***Before performing the steps below, do a quick spot check to ensure the following is true:
Note: This step can be skipped, if the IASP exists. This might be true in environments using geographic mirroring for the first time, but the IASP had already been in use.
To create the IASP from a command-line interface from the primary node:
CFGDEVASP ASPDEV(<IASP_Name>) ACTION(*CREATE)
Example:
CFGDEVASP ASPDEV(TWINIASP) ACTION(*CREATE)
Notes:
1. Specify the name of the IASP here. A device description by the same name will be created on the primary node.
2. If specifying UNITS(*SELECT), it will be prompt with a list of non-configured disks to add to the IASP.
Step 5 - Create the Device CRG (Cluster Resource Group), but do NOT start the CRG yet
Perform the following on the primary node (not required, but to keep things consistent):
CRTCRG CRG(<DevCRGName>) CRGTYPE(*DEV) RCYDMN((MPLS *PRIMARY *LAST <PrimarySiteName> (<DataPort_IP_Address>)) (STPAUL *BACKUP 1 <BackupSiteName> (<DataPort_IP_Address>))) CFGOBJ((<Name of IASP> *DEVD *ONLINE))
Example:
CRTCRG CRG(TWINCRG) CRGTYPE(*DEV) RCYDMN((MPLS *PRIMARY *LAST MPLS (111.22.3.5)) (STPAUL *BACKUP 1 STPAUL (111.22.13.5)) CFGOBJ((TWINIASP *DEVD *ONLINE))
Notes:
1. The above example assumes the IASP production copy will initially and preferably be owned by node MPLS, with node STPAUL owning the mirror copy of the IASP.
2. The Data Port IP addresses listed above are examples. It is advised to use different IP addresses than what is being used for clustering, or this can create problems with cluster communications.
Step 6 - Configure Geographic Mirroring
***Before performing the steps below, do a quick spot check to ensure the following is true:
- Both nodes in the cluster are Active.
- Job QHASVR is Active on both nodes. Error HAE2029 is a sign of an inactive job.
- The Device CRG is Inactive.
- The IASP *DEVD exists on both nodes (Remember the STRCRG will create the target *DEVD if it is missing).
- Review the pre-configuration steps above and consider preparing the target disks ahead of time.
- The IASP is varied off on the source node (and has not been configured with geographic mirror on the target yet).
*Important Note: The IASP must be varied off before Geographic Mirroring can be configured.
To configure geographic mirroring through the command-line interface from the primary node:
CFGGEOMIR ASPDEV(<IASP_Name>) ACTION(*CREATE) DELIVERY(*ASYNC)
Example:
CFGGEOMIR ASPDEV(TWINIASP) ACTION(*CREATE) DELIVERY(*ASYNC)
Notes:
1. It is no longer needed to specify the ASP session name, along with the two ASP copy description names. These are now defaulted to *GEN during the CFGGEOMIR and will automatically be created. Only specify these parameters if a specific naming convention is desired.
2. When leaving the default of *SELECT for the UNITS parameter, it will prompt to select from a list of non-configured disk units on the target site (backup node). The original restriction was that the total capacity for the mirror copy must be 95% or greater of the production copy. This restriction has been lifted, but it's always best to make the two copies nearly equal capacity, since IASPs cannot overfill and geographic mirroring will suspend once the capacity of one copy has reached its limit.
3. The example above uses DELIVERY(*ASYNC). The normal default is DELIVERY(*SYNC). This can be modified as needed, via the CHGASPSSN command.
To configure geographic mirroring through the command-line interface from the primary node:
CFGGEOMIR ASPDEV(<IASP_Name>) ACTION(*CREATE) DELIVERY(*ASYNC)
Example:
CFGGEOMIR ASPDEV(TWINIASP) ACTION(*CREATE) DELIVERY(*ASYNC)
Notes:
1. It is no longer needed to specify the ASP session name, along with the two ASP copy description names. These are now defaulted to *GEN during the CFGGEOMIR and will automatically be created. Only specify these parameters if a specific naming convention is desired.
2. When leaving the default of *SELECT for the UNITS parameter, it will prompt to select from a list of non-configured disk units on the target site (backup node). The original restriction was that the total capacity for the mirror copy must be 95% or greater of the production copy. This restriction has been lifted, but it's always best to make the two copies nearly equal capacity, since IASPs cannot overfill and geographic mirroring will suspend once the capacity of one copy has reached its limit.
3. The example above uses DELIVERY(*ASYNC). The normal default is DELIVERY(*SYNC). This can be modified as needed, via the CHGASPSSN command.
4. When the CFGGEOMIR completes successfully, the CRG is Active, the IASP is Available and replication is occurring.
The DSPASPSSN command can now be used to check the current status of geographic mirroring using the command-line interface.
Example:
DSPASPSSN SSN(TWINSSN)
The DSPASPSSN command can now be used to check the current status of geographic mirroring using the command-line interface.
Example:
DSPASPSSN SSN(TWINSSN)
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CMQAA2","label":"High Availability-\u003EGeographic Mirror"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0;and future releases"}]
Historical Number
605199794
Was this topic helpful?
Document Information
Modified date:
04 October 2024
UID
nas8N1011443