Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Guide de dépannage télécharger pdf (Page 13)

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

4 SDC Cluster

To achieve maximum availability for cluster resources by detecting and recovering from node

and resource-level failures, SDC uses Pacemaker, as its cluster resource manager, and

Corosync, as its group communication layer for Pacemaker. For more information about

Pacemaker and Corosync, refer to the following link:

http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Clusters_from_Scratch/

Prerequisites

For Cluster Resource Manager troubleshooting, verify that there are a minimum of two nodes

(Pizza Boxes, Blades, VMs).

General Cluster Commands for Troubleshooting

The following table summarizes the most used cluster commands that you will use when

troubleshooting:

Cluster Command –What is Does?

CRM Command Example

Show Status – top view

crm_mon

Show Status – One-shot display

crm_mon -1

Show Status – Per-node view

crm_mon –n

Show Last Failures

crm_mon -1nf

Show cluster operations history

crm_mon -1o

Show cluster operations history with

timing details

crm_mon -1t

List top-level resources

crm_mon -1 |grep -P '^\s+Resource|Clone'

Take node offline (on standby)

crm node standby sdclab001-01

Take mode online

crm node online sdclab001-01

Stop single resource

crm resource stop traffix_webui-grp

Start single resource

crm resource start traffix_webui-grp

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 41 42

Pas de commentaire

Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Guide de dépannage Page 13