HACMP - Disk HeartBeat
~cd to /usr/sbin/rsct/bin (not needed if path is already added)
~First execute # ./dhb_read -p hdisk2 -r on one node where hdisk2 is your heartbeat disk.
~Then execute # ./dhb_read -p hdisk2 -t on the other node.
~If they are working normally we should get a message Link operating normally.
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.
HACMP Installation--Pre-Installation Tasks
~irst do smitty tcpip and install the communicatoin devices en0 and en1 so that we can establish communication between the two nodes.
~Then update the /etc/hosts file with the non-service IPs,persistent IPs and service IPs.
~Install bos.adt,bos.compat and any cluster.* filesets in AIX CD1. Also install rsct and bos.clvm filesets from CD3.
~Then update the /etc/hosts file with the non-service IPs,persistent IPs and service IPs.
~Install bos.adt,bos.compat and any cluster.* filesets in AIX CD1. Also install rsct and bos.clvm filesets from CD3.
High Availability and Hardware Availability for HACMP
High availability is sometimes confused with simple hardware availability. Fault tolerant,redundant systems (such as RAID) and dynamic switching technologies (such as DLPAR)provide recovery of certain hardware failures, but do not provide the full scope of error detection and recovery required to keep a complex application highly available.
A modern, complex application requires access to all of these components:
• Nodes (CPU, memory)
• Network interfaces (including external devices in the network topology)
• Disk or storage devices.
Recent surveys of the causes of downtime show that actual hardware failures account for only
a small percentage of unplanned outages. Other contributing factors include:
• Operator errors
• Environmental problems
• Application and operating system errors.
Reliable and recoverable hardware simply cannot protect against failures of all these different
aspects of the configuration. Keeping these varied elements—and therefore the application—highly available requires:
• Thorough and complete planning of the physical and logical procedures for access and operation of the resources on which the application depends. These procedures help to avoid failures in the first place.
• A monitoring and recovery package that automates the detection and recovery from errors.
• A well-controlled process for maintaining the hardware and software aspects of the cluster configuration while keeping the application available.
A modern, complex application requires access to all of these components:
• Nodes (CPU, memory)
• Network interfaces (including external devices in the network topology)
• Disk or storage devices.
Recent surveys of the causes of downtime show that actual hardware failures account for only
a small percentage of unplanned outages. Other contributing factors include:
• Operator errors
• Environmental problems
• Application and operating system errors.
Reliable and recoverable hardware simply cannot protect against failures of all these different
aspects of the configuration. Keeping these varied elements—and therefore the application—highly available requires:
• Thorough and complete planning of the physical and logical procedures for access and operation of the resources on which the application depends. These procedures help to avoid failures in the first place.
• A monitoring and recovery package that automates the detection and recovery from errors.
• A well-controlled process for maintaining the hardware and software aspects of the cluster configuration while keeping the application available.
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)