HACMP 6.1 ADMINISTRATION GUIDE PDF
Enhanced Scalability Installation and Administration Guide – SC 6. Press Enter. The system adds these values to the HACMP for AIX ODM and. Product Guide, P/N HACMP for AIX Administration Guide, HACMP for AIX Geographic LVM: Planning and Administration Guide. Selection from Guide to IBM PowerHA SystemMirror for AIX Version [Book] PowerHA SystemMirror · Rolling migration from PowerHA SystemMirror to PowerHA SystemMirror (AIX TL3 or Administration.
|Published (Last):||12 March 2015|
|PDF File Size:||1.87 Mb|
|ePub File Size:||15.84 Mb|
|Price:||Free* [*Free Regsitration Required]|
It will also show you where any resource groups are active. We’ve written a script for this purpose.
Guide to IBM PowerHA SystemMirror for AIX Version 7.1.3
View properties for a cluster such as the PowerHA SystemMirror version, name of sites and nodes, and repository disk information. At this time, the storage is properly configured on both nodes, and it is time to add the volume group s to the PowerHA resource group.
You’re probably familiar with the clstat or the xclstat commands.
Once done, ensure that the volume group is varied off, for example for volume group fs01vg: The first thing that we’ll need to know is a common majar number that is available on both nodes of a cluster. Next, log in to the other node, and run the cfgmgr command on that node as well, so the disks will be discovered on the other node as well. Next, sync the cluster, which should bring the volume group s online: For PowerHA, a new volume group should be configured as concurrent-capable configured by the -C option of the mkvg command.
On both nodes, make sure that the disk attributes are set correctly. This administratoon but effective tool accepts the following flags: Now run “lspv” on both nodes of the cluster, and look at the PVIDs listed.
For that purpose, run the following command on all cluster nodes, which lists the available major numbers: In the case of SAN storage, please ensure that your storage administrator adds the storage to both nodes of the cluster. Mount Guard is not enabled by default, but is configurable by the system administrator. Information on how to install and start using it can be found on the IBM website. Now, this may differ for the type guids storage used so please make sure to check your storage vendor’s recommendations on this topicbut a good starting point is for example, for disk hdisk4: Also, the format of the log file is 6.11 to read and identify important information.
You may schedule this command through cron to get a regular up to date version.
For the latest version, check www. This may be caused by the volume group being varied on, on the other node. Then hhacmp the newly added storage by running the cfgmgr command on one of the nodes: This article describes how to add a new volume group to an existing resource group of an active PowerHA cluster. This can be done while the cluster is up and running: At this point, the volume group, logical volume and file system have been created.
The filesystem is potentially mounted on another node.
UNIX Health Check – PowerHA / HACMP
Clstat is rather slow with its hacmpp, and sometimes the required clinfo deamon needs restarting in order to get it operational, so this is, well, not perfect. Do make sure to select the correct PVID of one axministration the disks in the volume group on the first node when importing this volume group on the second node, as you’ll want to make sure both nodes of a PowerHA cluster use the same volume group names. IBM included a clstat. Monitor the status for all clusters, sites, nodes, and resource groups in your environment.
To check the current running configuration of xntpd for the -x flag: If clstat is not working, you may get the following error, when running guids Also, The quorum should be disabled by using -Qnand the auto-varyon should be disabled as well by using the hafmp option as PowerHA will varyon the volume group for us.
Pick one of the disks on which you configured the volume group on the first node, and take that disk’s PVID, for example 00facb28b Then create a file system on the previously defined logical volume: This is version 1.
This still doesn’t provide an overview in administratioj single look, as the clstat. First, verify that the cluster is in a good state by running: Cluster services are not active on any nodes.
The behavior is configured with the -x flag for the xntpd daemon.
Guide to IBM PowerHA SystemMirror for AIX Version [Book]
There are a number of possible causes: You can create additional volume groups, logical volumes and file systems as it pertains to your situation. Subsystem PID is Per cluster you can see: Failed retrieving cluster information. Admniistration version 7 starting with version 7. The command needed to generate the report is clmgr.
You can download the script here. And when you run “lspv” on the second node after running cfgmgr, you’ll notice that the PVID is already set for all the discovered disks it was set on the first node. Operation is not allowed because vg is a RAID concurrent volume group. Finally, the major number should be set in the example below: For the purpose of this article, let’s assume major number 57 is available.
If you run into the following error: If the time on the yacmp clock is behind adminisgration time of the system clock, the hcamp clock will be set backwards causing the same time period to be passed twice. If the event occurred because of an error or issue in your environment, you can read suggested solutions to fix the problem.