Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
CentOS High Availability

You're reading from   CentOS High Availability Leverage the power of high availability clusters on CentOS Linux, the enterprise-class, open source operating system

Arrow left icon
Product type Paperback
Published in Apr 2015
Publisher
ISBN-13 9781785282485
Length 174 pages
Edition 1st Edition
Tools
Arrow right icon
Toc

Table of Contents (16) Chapters Close

Preface 1. Getting Started with High Availability FREE CHAPTER 2. Meet the Cluster Stack on CentOS 3. Cluster Stack Software on CentOS 6 4. Resource Manager on CentOS 6 5. Playing with Cluster Nodes on CentOS 6 6. Fencing on CentOS 6 7. Testing Failover on CentOS 6 8. Two-node Cluster Considerations on CentOS 6 9. Cluster Stack Software on CentOS 7 10. Resource Manager on CentOS 7 11. Playing with Cluster Nodes on CentOS 7 12. STONITH on CentOS 7 13. Testing Failover on CentOS 7 14. Two-node Cluster Considerations on CentOS 7 Index

Cluster operating system preparation

I assume your cluster nodes are all set up; power, network and other cables are connected; the operating system is installed; and disks are partitioned the way you want them. Before you can start with the installation and configuration of the cluster stack software, you must carefully follow these steps:

  1. Network configuration: You must configure a static IP address for all available network interfaces on all cluster nodes. You can do this by editing the /etc/sysconfig/network-scripts/ifcfg-ethX files. You must also disable the Network Manager network interface control. In the following screenshot, you can see the network interface configuration for the node-1 cluster node:
    Cluster operating system preparation

    Note

    Change the NM_CONTROLLED line to no. This specifies that the Network Manager service cannot control the network interface.

    Change the BOOTPROTO line to none. This specifies that no boot protocol is used for this interface, since this interface has a static IP address assigned to it...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image