Netra™ High Availability Suite 3.0 1/08 Foundation Services Cluster Administration Guide

Netra™ High Availability Suite 3.0 1/08 Foundation Services Cluster Administration Guide

819-5235-13

Contents

Tables

Preface

Using Cluster Administration Tools and Configuration Files

Using the Tools

Using Netra HA Suite Tools for Cluster Administration

Using Solaris Tools for Cluster Administration

Using Linux Tools for Cluster Administration

Using the Foundation Services Configuration Files in the Cluster Environment

Using Solaris Configuration Files in the Cluster Environment

Using Linux Configuration Files in the Cluster Environment

Accessing and Maintaining Log Files

Accessing System Log Files

To Redirect Netra HA Suite Messages to a File on the Master Node

To Define loghost in /etc/hosts

Maintaining System Log Files

To Redirect System Log Messages to a Nonpeer Node

To Remove Links to Crashed Daemons

Logging NFS Operations

To Log NFS Operations

Determining Cluster Validity

Defining Minimum Criteria for a Cluster Running Highly Available Services

Verifying Services on Peer Nodes

To Verify That the Cluster Has a Master Node and a Vice-Master Node

To Verify That an nhcmmd Daemon Is Running on Each Peer Node

To Verify That the Cluster Has a Redundant Ethernet Network

To Verify That the Master Node and Vice-Master Node Are Synchronized

To Verify That the Reliable Boot Service Is Running

Verifying That a Cluster Is Configured Correctly

To Verify That a Cluster Is Configured Correctly

Reacting to a Failover

To React to a Failover

Examining the Cluster Networking Configuration

Using Tools to Examine the Cluster Network

Verifying the Network Configuration

To Verify the Network Interfaces of a Node

Creating a Network Topology Map

Mapping the Network Configuration of a Peer Node

To Identify the Name of a Node

To Identify the Host Name of the Network Interfaces of a Node

To Obtain Configuration Information About the Network Interfaces of a Node

Mapping the External Network Configuration of a Node

To Examine Interfaces Configured for External Communication

Mapping the Floating Address Triplet of the Master Node

To Map the Floating Address Triplet of the Master Node

Mapping the Floating External Address of the Master Node

To Map the Floating External Address of the Master Node

Examining the Network Configuration Files

Examining the Routes on a Node

To Examine the Routing Table for a Node

Output of the netstat r Command

Debugging Diskless Nodes With the snoop or tcpdump Tools

To Examine a Diskless Node From the Master Node

Using and Managing System Files

Using Data Caches in Shared File Systems

To Enable or Disable Data and Attribute Caching on Solaris

To Enable or Disable Data and Attribute Caching on Linux

Changing the Location of the Scoreboard Bitmap

Storing Bitmap Scorecards on Disk or in Memory

To Change the Location of the Scoreboard Bitmap

Managing Differences Between Files That Are Not Shared

To Manage Differences Between Files That Are Not Shared

Using the Naming Services

Starting and Stopping Services, Nodes, and Clusters

Stopping and Restarting the Foundation Services

To Start a Node Without the Foundation Services

To Stop and Restart the Foundation Services Without Stopping the Solaris OS

To Stop and Restart the Foundation Services Without Stopping Linux

To Restart the Foundation Services

Stopping and Restarting Daemon Monitoring

To Stop Daemon Monitoring

To Restart Daemon Monitoring

Shutting Down and Restarting a Node

General Rules for Shutting Down a Node

To Perform a Clean Reboot of a Solaris OS Node

To Perform a Clean Reboot of a Linux Node

To Perform a Clean Power off of a Solaris Node

To Perform a Clean Power off of a Linux Node

To Perform a Clean Halt of a Solaris Node

To Perform a Clean Halt of a Linux Node

To Abruptly Reboot a Solaris Node

To Abruptly Reboot a Linux Node

To Abruptly Power Off a Solaris Node

To Abruptly Power Off a Linux Node

To Abruptly Halt a Solaris Node

To Abruptly Halt a Linux Node

Shutting Down a Node

To Shut Down the Master Node

To Shut Down the Vice-Master Node

To Shut Down a Diskless Node or Dataless Node

Restarting a Node

To Restart a Node

Shutting Down and Restarting a Cluster

To Shut Down a Cluster

To Restart a Cluster

Triggering a Switchover

To Trigger a Switchover With nhcmmstat

Recovering an IP-Replicated Cluster

To Recover a Solaris Cluster After Failure

To Recover a Linux Cluster After Failure

Patching Software on a Solaris Cluster

About Patching Software on a Solaris Cluster

Choosing a Procedure to Patch Software on a Cluster

Overwriting Modified Netra HA Suite Files

Patching a Nonshared Package on Both Master-Eligible Nodes

To Patch a Nonshared Package on Both Master-Eligible Nodes

Patching a Dataless Node

To Patch a Dataless Node

Patching a Diskless Node

Patching the /usr Directory for a Diskless Node

To Patch the /usr Directory for Diskless Nodes

Patching the root Directory for Diskless Nodes

To Patch the root File System for Diskless Nodes

Patching a Shared Package

To Patch a Shared Package on a Cluster

Patching Software on a Linux Cluster

About Patching Software on a Linux Cluster

To Patch a Package on Both Master-Eligible Nodes

To Patch a Dataless Node

Modifying and Adding Disk Partitions for Replicated Data on the Solaris OS

Using the format Utility to Display and Modify the Configuration of a Disk Partition on a Solaris Node

To Display the Configuration of a Disk Partition on a Solaris Node

To Change the Size of a Disk Partition on a Master-Eligible Node on the Solaris OS

Increasing the Size of a Replicated Data Partition on a Physical Disk on a Solaris Node

To Increase the Size of a Replicated Data Partition on a Physical Disk on a Solaris Node

Increasing the Size of a Replicated Data Partition on a Virtual Disk on a Solaris Node

To Increase the Size of a Replicated Data Partition on a Virtual Disk on a Solaris Node

Adding a Mirrored Data Partition to a Virtual Disk on a Solaris Node

To Add a Mirrored Data Partition to a Virtual Disk on a Solaris Node

Modifying and Adding Disk Partitions for Replicated Data on Linux

Using the parted Utility to Display and Modify the Configuration of a Disk Partition on a Linux Node

To Display the Configuration of a Disk Partition on a Linux Node

To Change the Size of a Disk Partition on a Master-Eligible Node on Linux

Increasing the Size of a Replicated Data Partition on a Physical Disk on a Linux Node

To Increase the Size of a Replicated Data Partition on a Physical Disk on a Linux Node

Increasing the Size of a Replicated Data Partition on a Virtual Disk on a Linux Node

To Increase the Size of a Replicated Data Partition on a Virtual Disk on a Linux Node

Adding a Mirrored Data Partition to a Virtual Disk on a Linux Node

To Add a Mirrored Data Partition to a Virtual Disk on a Linux Node

Adding a Node to a Cluster

Deciding How to Add a Node to a Cluster

Determining Whether a Cluster Has Predefined Nodes

To Determine Whether the Cluster Has Predefined Nodes

Replacing Hardware in a Cluster

Preparing to Replace Hardware in a Cluster

Replacing a CPU Board on a Node

To Replace a Board on a Node

Replacing a CPU Board on a Diskless Node

To Replace a Board on Diskless Nodes With the DHCP Client ID Boot Policy

To Replace a Diskless Node With the DHCP Static Boot Policy

Replacing Ethernet Cards on a Vice-Master or Dataless Node

To Replace Ethernet Cards on the Vice-Master Node or a Dataless Node

Replacing Ethernet Cards on a Diskless Node

To Replace Ethernet Cards on a Diskless Node With the DHCP Static Boot Policy

Replacing the Disk on the Vice-Master Node

To Replace the Disk on the Vice-Master Node Using IP Replication

To Replace the Disk on the Vice-Master Node Using Shared Disk

Replacing Disks on Both Master-Eligible Nodes Without Cluster Shutdown

To Replace Disks on Both Master-Eligible Nodes Using IP Replication Without Full Cluster Shutdown

Replacing a Dataless Node Disk

To Replace a Dataless Node Disk

Netra™ High Availability Suite 3.0 1/08 Foundation Services Cluster Administration Guide

819-5235-13

Copyright © 2008, Sun Microsystems, Inc. All rights reserved.