Test environment:
< p> Configure heartbeat haresources as resources in the previous blog post Configure crm on the basis of the manager (using the configuration interface of hb_gui);
1. Turn off the heartbeat service on web1
#service heartbeat stop
#ssh web2.luochen.com’service heartbeat stop’
2. Edit the ha.cf file on web1, Enable crm
#vim /e tc/ha.d/ha.cf
node web1.luochen.com
node web2.luochen.com
crm on ####Add this line
3. Synchronize the configuration file on web1 to the web2 node
#/usr/lib64/heartbeat/ ha_propagate (only sync authkeys, ha.cf files)
4. Install the graphical configuration tool heartbeat-gui on web1 and web2
#rpm -ivh heartbeat-gui-2. 1.4.el5.i386.rpm
5. Delete the haresources file on web1 and web2
#rm -rf /etc/ha.d/haresources
#service heartbeat start
PS: There is no VIP and httpd service startup on web1 and web2 to prove that the configuration is successful , You can continue to configure when you see that port 5560 is listening; crm monitors on port tcp/5560 through mgmtd process;
6. Provide a user password for the graphical configuration interface (you need to start the host of hb_gui to add a password for the hacluster user, and use it to log in hb_gui)
#tail /etc/passwd
#passw d hacluster
#hb_gui & ### (Xmanager needs to be installed)
There are two methods to bind all resources to a node; the first method uses arrangement constraints, position constraints and order constraints, and the other method is to define resource groups
The first method defines arrangement constraints, position constraints and order constraints:
Test environment:
192.168.1.111 web1
192.168.1.112 web2
192.168.1.114 nfs
VIP: 192.168.1.140
hb_gui login interface:
Node and resource list:
Add VIP
650) this.width=650;” src=”/wp-content/uploadshttp:/img.voidcn.com/vcimg/static/loading.png” title=” 4.png” alt=”wKiom1YjVXiDl7GgAALWU5uDeiU189.jpg” data-src=”http://s3.51cto.com/wyfs02/M00/74/9A/wKiom1YjVXiDl7GgAALWU5uDeiU189.jpg”>
Add httpd
Add arrangement constraints, bind two resources to the same node (the default is not on the same node)
Test on the host machine
< /span>
< img onload="if(this.width>650) this.width=650;” src=”/wp-content/uploadshttp: /img.voidcn.com/vcimg/static/loading.png” title=”7.png” alt=”wKioL1YjVjrxSsw9AADMGntTurA505.jpg” data-src=”http://s3.51cto.com/wyfs02/M00/74/ 96/wKioL1YjVjrxSsw9AADMGntTurA505.jpg”>
Add location constraints to make resources run on a node as much as possible
650) this.width=650;” src=”/wp-content/uploadshttp:/img.voidcn.com/vcimg/static/loading.png” title=”10.png” alt=”wKioL1YjVsPQVpwmAAKcfElZHQU320.jpg” data-src=”http://s3.51cto.com/wyfs02/M02/74/96/wKioL1YjVsPQVpwmAAKcfElZHQU320.jpg”>
test again to see if the configuration is successful
Finally, check whether the VIP configuration is successful on the node running the resource
The second method defines resource group:
< p style="white-space:normal;"> Test environment:
192.168.1.111 web1
192.168.1.112 web2
192.168.1.114 nfs
VIP: 192.168.1.140
Define resource group
650) this. width=650;” src=”/wp-content/uploadshttp:/img.voidcn.com/vcimg/static/loading.png” title=”2.png” alt=”wKioL1YjWYOyQBDZAAH2SbSMthE725.jpg” data-src=”http ://s3.51cto.com/wyfs02/M00/74/96/wKioL1YjWYOyQBDZAAH2SbSMthE725.jpg”>
Add VIP
Add shared storage
Add httpd
View resource group list
Test on the host
Finally, check whether the VIP configuration is successful on the node running the resource
PS: This is the end of the hb_gui configuration of crm NS. . . The configuration interface of the command line will be introduced later