AIX操作系统及HACMP群集系统安装步骤
2004-09-03 16:17
501 查看
AIX操作系统及HACMP群集系统安装步骤
在项目AIX操作系统及HACMP群集系统正式安装之前，最好能够与用户方网络管理员、系统管理员、数据库管理员一起确定各部分前期准备工作是否完成，以及确定意外情况发生时相应的责任负责人及处理顺序。
a.检测机房环境是否满足装机条件，重点检查零地电压是否小于1V；
b.拆箱并安装设备到指定位置，按标准连接各部分线缆；
c.再次检查最末端电源供应插座的电压情况，符合标准后设备加电；
d.设置光盘启动，由AIX系统盘引导进入系统安装程序；
e.基本系统BOS安装完毕后，根据应用系统如数据库的要求加装所需的系统文件包；
f.使用补丁光盘将系统所有已安装的文件包升级到当前最新的软件版本；
g.根据用户方网络管理员提供的IP地址设置设备的当前IP地址；并检查网络连接状况；
h.根据用户方系统管理员的要求设置磁盘阵列的RAID种类，创建RAID盘；
i.根据用户方数据库管理员的要求设置数据库系统、数据库数据所在的VG/LV划分；并在其基础上设立相应的文件系统或者裸设备；
j.在系统中创建数据库用户组及用户，设置相应的.profile文件，以满足数据库安装及使用时所需的系统环境；
k.mount数据库系统光盘，进入数据库系统安装步骤；
l.完成数据库系统的安装后，根据用户方数据库管理员的要求建立数据库及实例；
m.在设备上启动数据库，并使用客户端连接数据库，以确定数据库安装是否正常无误；
n.安装hacmp软件，根据项目环境的要求设置群集系统的拓扑结构；
o.根据项目环境的要求设立群集系统的资源组设定，并做同步以做hacmp的验证工作；
p.启动所有设备上的hacmp软件，并检查相应的ip/vg/rg/数据库状态，以确定群集系统启动正常，各部分状况达到预先设定的状态；
q.按照hacmp系统安装验收表的步骤进行各项hacmp的功能检测，确定hacmp系统能够在各种情况的发生下按照预先的设定发生ip/vg/数据库的接管，保证应用系统的持续运行。
r.与用户方各方面负责人一起按照设备清单核对设备到货情况、按照hacmp系统安装验收表进行hacmp系统的验收，填写相应的设备验收清单，并签字盖章；
s.在验收完成后制做系统备份带，确保在后期调试时出现人为错误后能够用此备份带恢复系统到当前验收状态。并制作项目设置各项参数的文档提供给用户方存档，以方便后期人员的维护工作。
至此，项目AIX操作系统及HACMP群集软件安装且验收完毕。
1/ Log in as root on each node 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 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.
5/ Ensure that all your nodes have 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.
# smitty dtconfig
choose Command Line
reboot the machine
9/ Check to see if I/O spacing has been enabled on each node.
# 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 there 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 they hold IP labels for the service and standby adapters and server hostnames along with IP addresses.
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 configuration of your serial networks at this 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 these 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. i.e.
# lsattr –El scsi0|grep id
22/ If you are using 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 are 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 disk is not in an available state.
27/ Identify all your external volume groups, and which nodes if any have the volume groups varied on(# lsvg –o). Check that your volume groups have the same major number on all nodes and that they are 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.
注：如果安装OPS或RAC请先行安装HA,再安装ORACLE
在项目AIX操作系统及HACMP群集系统正式安装之前，最好能够与用户方网络管理员、系统管理员、数据库管理员一起确定各部分前期准备工作是否完成，以及确定意外情况发生时相应的责任负责人及处理顺序。
a.检测机房环境是否满足装机条件，重点检查零地电压是否小于1V；
b.拆箱并安装设备到指定位置，按标准连接各部分线缆；
c.再次检查最末端电源供应插座的电压情况，符合标准后设备加电；
d.设置光盘启动，由AIX系统盘引导进入系统安装程序；
e.基本系统BOS安装完毕后，根据应用系统如数据库的要求加装所需的系统文件包；
f.使用补丁光盘将系统所有已安装的文件包升级到当前最新的软件版本；
g.根据用户方网络管理员提供的IP地址设置设备的当前IP地址；并检查网络连接状况；
h.根据用户方系统管理员的要求设置磁盘阵列的RAID种类，创建RAID盘；
i.根据用户方数据库管理员的要求设置数据库系统、数据库数据所在的VG/LV划分；并在其基础上设立相应的文件系统或者裸设备；
j.在系统中创建数据库用户组及用户，设置相应的.profile文件，以满足数据库安装及使用时所需的系统环境；
k.mount数据库系统光盘，进入数据库系统安装步骤；
l.完成数据库系统的安装后，根据用户方数据库管理员的要求建立数据库及实例；
m.在设备上启动数据库，并使用客户端连接数据库，以确定数据库安装是否正常无误；
n.安装hacmp软件，根据项目环境的要求设置群集系统的拓扑结构；
o.根据项目环境的要求设立群集系统的资源组设定，并做同步以做hacmp的验证工作；
p.启动所有设备上的hacmp软件，并检查相应的ip/vg/rg/数据库状态，以确定群集系统启动正常，各部分状况达到预先设定的状态；
q.按照hacmp系统安装验收表的步骤进行各项hacmp的功能检测，确定hacmp系统能够在各种情况的发生下按照预先的设定发生ip/vg/数据库的接管，保证应用系统的持续运行。
r.与用户方各方面负责人一起按照设备清单核对设备到货情况、按照hacmp系统安装验收表进行hacmp系统的验收，填写相应的设备验收清单，并签字盖章；
s.在验收完成后制做系统备份带，确保在后期调试时出现人为错误后能够用此备份带恢复系统到当前验收状态。并制作项目设置各项参数的文档提供给用户方存档，以方便后期人员的维护工作。
至此，项目AIX操作系统及HACMP群集软件安装且验收完毕。
1/ Log in as root on each node 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 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.
5/ Ensure that all your nodes have 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.
# smitty dtconfig
choose Command Line
reboot the machine
9/ Check to see if I/O spacing has been enabled on each node.
# 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 there 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 they hold IP labels for the service and standby adapters and server hostnames along with IP addresses.
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 configuration of your serial networks at this 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 these 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. i.e.
# lsattr –El scsi0|grep id
22/ If you are using 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 are 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 disk is not in an available state.
27/ Identify all your external volume groups, and which nodes if any have the volume groups varied on(# lsvg –o). Check that your volume groups have the same major number on all nodes and that they are 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.
注：如果安装OPS或RAC请先行安装HA,再安装ORACLE
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- AIX Useful Commands
- AIX安装
- AIX 系统参数配置
- AIX安装后的基本系统设置
- AIX 5L上安装RAC的遭遇
- AIX 5L新特性
- 详解RAID——几种常见的RAID形式
- aix启动过程
- 今天的收获---实现excel工资单的自动发送
- waiting for the next customer services
- Qmail
- Japanese business glossary -- Kangei-kai and Sobetsu-kai
- Allaire JRun 3.0 可被目录浏览
- Allaire JRun 3.0 可被目录浏览
- allaire jurn 漏洞总汇
- allaire jurn 漏洞总汇
- Allaire JRun 目录遍历漏洞
- Allaire JRun 目录遍历漏洞
- 为什么我用不了PGtGM收GMAIL啊? 晕~
- EAI在网通业务支撑系统建设中的运用