AIX operating system and HACMP cluster system installation steps are best to be able to determine if all partial pre-preparatory work is completed together with the user-based network administrator, system administrator, and database administrators before the project AIX operating system and HACMP cluster system. Determine the heads of responsibility and processing order when an accident occurred. a. Detect whether the equipment room environment satisfies the installation conditions, the focus checks if the zero voltage is less than 1V; b. Unpack and install the device to the specified location, connect each part of the cable according to the standard. C. Check the voltage of the last power supply socket again. Compliance with standard post-appliance power and power; d. Set the CD start, boot into the system installer by the AIX system disk; E. After the basic system BOS is installed, install the required system file package according to the application system, such as the database. . Use the patch disc to upgrade all installed files installed to the current latest software version; g. Set the current IP address of the device according to the IP address provided by the user network administrator; and check the network connection status; h. According to the user The system administrator's request sets the RAID type of the disk array, creates a RAID disk; i. Set the database system, the database data is set by the VG / LV division according to the requirements of the user database administrator; and set up the corresponding file system based on it. Naked equipment; J. Create a database user group and user in the system, set the corresponding .profile file to meet the system environment required to install and use; K.Mount database system disc, enter the database system installation step; l. After completing the installation of the database system, establish a database and instance according to the requirements of the user database administrator; m. Start the database on the device and use the client to connect to the database to determine if the database installation is normal; n. Install the HACMP software, according to The requirements of the project environment set the topology of the cluster system; O. According to the requirements of the project environment, set up the resource group settings of the cluster system, and synchronize to do HACMP verification; p. Start all devices, HACMP software, and check the corresponding The IP / VG / RG / Database State To determine the normal set of the cluster system, each of the status is preset; Q. Follow the steps of the HACMP system installation acceptance form to determine the HACMP system can be In the event of a pre-set setting, the application system is taken to ensure the continuous operation of the application system. r. With the person in charge of the user, in accordance with the equipment checklist, according to the HACMP system installation acceptance list, fill in the corresponding device acceptance list, and sign the seal; s. After acceptance completion Make the system backup belt to ensure that people can use this backup with recovery system to the current acceptance status after people have errors during later debugging. And make the project to set the documentation of each parameter to provide the user party archive to facilitate the maintenance of the later staff. At this point, the project AIX operating system and HACMP cluster software are installed and the acceptance is completed.
1 / log in your cluster. 2 / EnSure That Hacmp Is Not Running On Any Node .. if IT IS, Run Smit Clstop. 3 / Ensure That You Have The Same Release of Hacmp Installed On Each Node in the cluster and 5 / Ensure that all your nodes have that the same fileset components are installed. # lslpp -L cluster. * 4 / If you find that any filesets are missing for nodes in your cluster, complete the HACMP installation before progressing further. at least 64MB of physical RAM # lsattr -El sys0 |.. grep realmem 6 / Ensure that all of your nodes have at least double the amount of paging space in proportion to physical RAM # lsps -a 7 / Check to see if each node has the same adapters installed in the same slots. # lsdev -Cc adapter 8 / If your cluster nodes boot using the Common Desktop Environment, change the system startup mode such that the node boots in ASCII (command line) mode. Otherwise, CDE will HANG WHEN IP is enabled. # itty dtconfig choose Command Line reboot the machine 9 / chec K to see if I / o spacing has been enabled on each name. # smit chgsys you are suggested to change the 'high water mark' to 33 and 'low water mark' to 22. 10 / check the value of 'the wall' . # no -a |. grep thewall 11 / Check the physical connection of your IP and non-IP networks Ensure that each node has at least two network adapters connected to a TCP / IP network and a non-IP connection to the other node In The Cluster. 12 / Check The TCP / IP Configuration for Each Node In The Cluster. 13 / if The are Any Errors In The Configuration of Your Network Adapters,
correct these. Do NOT use the ifconfig command as this only retains the configuration until the next reboot or cfgmgr operation. You can use # smitty chinet 14 / Check the routing table on each node to ensure that the service and standby adapters have routes to different logical subnets. # netstat -rn 15 / If there are errors in the configuration of your routes, especially duplicate entries, correct these now. Do NOT use the netstat command as this only retains the configuration until the next reboot or cfgmgr operation. You can use # smitty mkroute or # smitty rmroute as required. 16 / Check the / etc / hosts and /.rhosts files on each node to ensure that hold IP labels for the service and standby adapters and server hostnames along with IP addresses they. 17 / Check The Tty Configuration of Your Serial Network. On Node 1, # stty> / dev / tty1 - Command Should HANG On Node 2, # stty dev / tty1 - Command Should Display On Both Nodes. 18 / Correct Any Problems That May EXISTS with THE Configu市 stage. 19 / check That You Do Not Have An /etc/netsvc.conf or /etc/resolv.conf file in place on any Cluster Node At Present. If The Files Are IN Place, Simply Rename them to filename.OLD as they may be required later 20 / Check the network options parameters and ensure that IP forwarding is disabled # no -a |.. grep ipforwarding if the value is 1, # no -o ipforwarding = 0 21 / If you are using any form of SCSI technology as your shared disk bus, ensure that no adapter has its external bus ID set to 7. Ideally the adapters should be on SCSI ids 6,5,4 and 3 where possible. ie # lsattr -El SCSI0 | GREP ID 22 / IF you are uses ssa,
ensure that you have complete loops between all your cluster nodes and that each node is capable of addressing every disk in all the loops. 23 / Check that the hdisk to PVID numbering of external disks follows the same sequence on each node in the cluster. You may have cross connected SCSI buses or SSA loops. # lspv 24 / If you find a problem with the cabling of SCSI or SSA shared disks, resolve this before progressing futher. 25 / Check that the number of internal disks matches on each node. # lsdev -Cc disk 26 / If there is a mismatch between the number of internal disks, perform the following sequence of actions to achieves symmetry: On the node with the lower number of internal disks: a / Unmount any filesystems on non-rootvg volume groups . B / VARYOFF ANY NON-ROOTVG VOLUME GROUPS. C / Export Any Non-root Volume Groups. D / List The Physical Volumes Attached To The Node (# LSPV). E / Import Your Non-root Volume Groups and Change THEM To NOT Auto-Varyon. f / Remove All Physical Volumes That Ar e not part of rootvg (# rmdev -l hdiskn -d). g / create a dummy Physical Volume Using the mkdev Command (# mkdev -c disk -t 857MB -S SCSI -P SCSI0 -W0, 5 -D). h / Run cfgmgr to force discovery of the removed physical volumes. i / List the physical volumes attached to the node (# lspv). You should now see that external disks have been renumbered as the dummy disk occupies an hdisk location. This extra disk is NOT SHOWN BY LSPV BECAUSE THE DIS NOT IN AN Available State. 27 / Identify All your External Volume Groups,
And which nodes if any have the Volume Groups varied on all nodes and what isy all set nodes and what ity is not set to auto-varyon (# chvg -an vgname). 28 / Identify any filesystems that may be present on external volume groups, and their associated LV names 29 / Download the redbook:. IBM Certification Study Guide: pSeries HACMP for AIX from http://www.redbooks.ibm.com for further reference. Note: If you install an OPS or RAC, please install HA first, then install Oracle