Anda di halaman 1dari 64

HACMP Installation smitty installp Install the below requisites (can also install all filesets in the CD)

cluster.doc.en_US.es cluster.es cluster.es.cfs cluster.es.clvm cluster.es.cspoc cluster.license cluster.man.en_US.es cluster.msg.En_US.cspoc rsct.basic bos.adt.libm 5.2.0.13 bos.adt.syscalls 5.2.0.11 bos.clvm.enh 5.2.0.31 bos.data 5.1.0.0 rsct.basic.hacmp 2.4.2.0 rsct.basic.rte 2.4.2.0 rsct.basic.sp 2.4.2.0 # Fileset Update # Fileset Update # Fileset Update # Base Level Fileset # Base Level Fileset # Base Level Fileset # Base Level Fileset

Other Dependency Fileset s for above : rsct.compat.basic.hacmp rsct.compat.basic.rte rsct.compat.basic.sp rsct.compat.clients.hacmp rsct.compat.clients.rte rsct.compat.clients.sp

Host name Entries of Both Servers in /etc/hosts vi /etc/hosts 192.168.5.25 192.168.5.1 10.2.2.1 192.168.5.200 192.168.5.2 10.2.2.2 service bootip (en0 node1) pri-stdby (en1 node1) service2 bootip2 (en0 node2) sec-stdby (en1 node2)

On Secondary ifconfig looks like below : Remote Hosts file - /.rhosts pri sec pri-boot pri-stdby sec-stdby root root root root root service n2e0 n1e0 n1e1 n2e1

HACMP Configuration : smitty hacmp

View Settings which is configured :

RG Configurations :

On Secondary : Configure Add Cluster Configure Add Nodes

From Primary :

WARNING: There are IP labels known to HACMP and not listed in file /usr/es/sbin/cluster/etc/clhosts.client on node: sec. Verification can automatically populate this file to be used on a client node, if executed in auto-corrective mode. WARNING: There are IP labels known to HACMP and not listed in file /usr/es/sbin/cluster/etc/clhosts.client on node: pri. Verification can automatically populate this file to be used on a client node, if executed in auto-corrective mode. On Secondary : Verify its Syncd : # /usr/es/sbin/cluster/utilities/cllsif Adapter Type Network Net Type Attribute Node IP Address Hardware Address Interface Name Global Name Netmask pri-boot en0 boot ha_ether_01 ether 255.255.255.0 public pri 192.168.5.2

pri service ha_ether_01 ether public pri 192.168.5.25 255.255.255.0 pri-stdby standby ha_ether_01 ether public pri 10.2.2.2 en1 255.255.255.0 sec boot ha_ether_01 ether public sec 192.168.5.200 en0 255.255.255.0 sec-stdby standby ha_ether_01 ether public sec 10.2.2.1 en1 255.255.255.0 On Primary or Secondary : Create Vg s and to add in RG :

If its vpath s instead of hdisks :

Adding VG in RG : We are doing in Primary Server :

Sync the Cluster Starting the cluster smitty clstart

Boot-IP is now replaced with service-IP Monitor the activities using another telnet session tail f /tmp/hacmp.out End of file will be like below HACMP Event Summary Event: /usr/es/sbin/cluster/events/check_for_site_up_complete pri Start time: Wed Feb 13 22:36:53 2008 End time: Wed Feb 13 22:36:53 2008 Action: Resource: Script Name: ---------------------------------------------------------------------------No resources changed as a result of this event

Start the cluster in the secondary node Failover smitty clstop

Monitor using tail f /tmp/hacmp.out /usr/es/sbin/cluster/clstat Service IP address can be seen in the secondary server. # hostname sec # ifconfig -a en0: flags=4e080863,80<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTIC AST,GROUPRT,64BIT,PSEG,CHAIN> inet 192.168.5.200 netmask 0xffffff00 broadcast 192.168.5.255 en1: flags=4e080863,80<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTIC AST,GROUPRT,64BIT,PSEG,CHAIN> inet 192.168.5.25 netmask 0xffffff00 broadcast 192.168.5.255 lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST, GROUPRT,64BIT> inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255 inet6 ::1/0

tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1 # Start the cluster again on the primary server.

# /usr/es/sbin/cluster/utilities/clRGinfo ----------------------------------------------------------------------------Group Name State Node ----------------------------------------------------------------------------HA_rg ONLINE pri OFFLINE sec #

Simulation Node failure by abrupt reboot of the primary node (monitor tail f /tmp/hacmp.out and clstat in the secondary node)

Anda mungkin juga menyukai