RHEL High Availability Documentation: Testing and Troubleshooting Procedures

Updated

NOTE: For a general overview of the documentation available for the Red Hat High Availability Add-On, see the Red Hat High Availability Add-On Documentation Guide.

Troubleshooting your system should begin when you first configure your system, when you create your fencing devices and system resources. It is important that you test your system at each configuration step before proceeding to the next step. For example, if you configure a fence agent and then add many resources without testing along the way, your system may start to see problems that you could have prevented if you'd stopped right after fence configuration and tested your fence devices.

It is particularly important to test your fencing devices during initial configuration, even if you do not see any issues immediately. A situation that may require your system to be fenced might arrive many months down the line, but if you have not fully tested your fence configuration originally you will not see a problem in the configuration until that time.

Red Hat provides the following documentation to help you test your system and its components.

General testing and troubleshooting documentation

Using the kdump feature to troubleshoot your cluster

Troubleshooting specific errors

Contacting technical support

Article Type