HACMP - Configuration
~smitty hacmp --> extended configuration --> extended topology-->config a HACMP cluster --> Add/change/show a HA cluster
~Here give the cluster name (here test_cl).
~Press F3 to go back
~Again Extended topology --> config a HA node --> Add a node to a HA cluster
~Here give a node name (here aix1) and a communication path (here aix1_nsvc1).
~Similarly add another node.
Again Extended topology config HA n/w Add a n/w
add ether,rs232 and then SCSI one by one.
~Now go back to extended config Discover devices....hacmp attempts to discover other devices based on the info provided by us.
~Again Extended topology --> config HA commn., Interfaces --> Add a commn., Interface --> Add discovered --> commn Int., -->select All --> select en0,en1
Showing posts with label High Availability Cluster Multi-Processing for AIX. Show all posts
Showing posts with label High Availability Cluster Multi-Processing for AIX. Show all posts
Tuesday, April 28, 2009
Monday, April 27, 2009
HACMP -Installation - Contd
~Now lets create VGs for diskheartbeat,production and development(here dhbvg,prodvg and devvg respectively).
~While creating a VG make lets make sure that make vg active on system restart is turned off because this will be taken care of by HACMP.
~Also after the creation of the VG we should not forget to turn off the quorum as this will interfere with the functioning of HACMP.
~Finally we should specify a major number while creating a VG.
Now we should varyoff the VGs,export them and import them in node2(here AIX2).
~After importing varyoff the VGs.
---NON-IP(RS-232) N/W---
~smitty tty --> add tty -->rs232 --> select enable login and press enter.
~To test which tty device is being used for heartbeat enter...
~stty < /dev/tty1 (run this on each node) ~If you get an echo status saying OK then its working fine.
~While creating a VG make lets make sure that make vg active on system restart is turned off because this will be taken care of by HACMP.
~Also after the creation of the VG we should not forget to turn off the quorum as this will interfere with the functioning of HACMP.
~Finally we should specify a major number while creating a VG.
Now we should varyoff the VGs,export them and import them in node2(here AIX2).
~After importing varyoff the VGs.
---NON-IP(RS-232) N/W---
~smitty tty --> add tty -->rs232 --> select enable login and press enter.
~To test which tty device is being used for heartbeat enter...
~stty < /dev/tty1 (run this on each node) ~If you get an echo status saying OK then its working fine.
HACMP - Installation
To install HACMP....through smitty
-smitty installp and select cd as the source.
-Press F4 to se the list of filesets and select..
-cluster.adt.es
-cluster.doc.en_us.es
-cluster.es.cfs
-cluster.es.clvm
-cluster.es.cspoc
-cluster.es.plugins
-cluster.haview
-cluster.license
-rsct.exp
-Do Not Forget To RESTART the NODE after Installation.
-smitty installp and select cd as the source.
-Press F4 to se the list of filesets and select..
-cluster.adt.es
-cluster.doc.en_us.es
-cluster.es.cfs
-cluster.es.clvm
-cluster.es.cspoc
-cluster.es.plugins
-cluster.haview
-cluster.license
-rsct.exp
-Do Not Forget To RESTART the NODE after Installation.
High Availability Cluster Multi-Processing for AIX
The IBM HACMP software provides a low-cost commercial computing environment that ensures quick recovery of mission-critical applications from hardware and software failures.
HACMP has two major components: high availability (HA) and cluster multi-processing
(CMP).
With HACMP software, critical resources remain available. For example, an HACMP cluster could run a database server program that services client applications. The clients send queries to the server program that responds to their requests by accessing a database, stored on a shared
external disk.
This high availability system combines custom software with industry-standard hardware to minimize downtime by quickly restoring services when a system, component, or application fails. Although not instantaneous, the restoration of service is rapid, usually within 30 to 300 seconds.
In an HACMP cluster, to ensure the availability of these applications, the applications are put under HACMP control. HACMP takes measures to ensure that the applications remain available to client processes even if a component in a cluster fails. To ensure availability, in case of a component failure, HACMP moves the application (along with resources that ensure access to the application) to another node in the cluster.
HACMP has two major components: high availability (HA) and cluster multi-processing
(CMP).
With HACMP software, critical resources remain available. For example, an HACMP cluster could run a database server program that services client applications. The clients send queries to the server program that responds to their requests by accessing a database, stored on a shared
external disk.
This high availability system combines custom software with industry-standard hardware to minimize downtime by quickly restoring services when a system, component, or application fails. Although not instantaneous, the restoration of service is rapid, usually within 30 to 300 seconds.
In an HACMP cluster, to ensure the availability of these applications, the applications are put under HACMP control. HACMP takes measures to ensure that the applications remain available to client processes even if a component in a cluster fails. To ensure availability, in case of a component failure, HACMP moves the application (along with resources that ensure access to the application) to another node in the cluster.
Subscribe to:
Posts (Atom)