Implementing IBM VM Recovery Manager for IBM Power Systems
Total Page:16
File Type:pdf, Size:1020Kb
Front cover Implementing IBM VM Recovery Manager for IBM Power Systems Dino Quintero Jose Martin Abeleira Adriano Almeida Bernhard Buehler Primitivo Cervantes Stuart Cunliffe Jes Kiran Byron Martinez Martinez Antony Steel Oscar Humberto Torres Stefan Velica Redbooks IBM Redbooks Implementing IBM VM Recovery Manager for IBM Power Systems October 2019 SG24-8426-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (October 2019) This edition applies to: Virtual I/O Server (VIOS) V3.1.0.11 AIX 7.2.2.1 Hardware Management Console (HMC) V9 R1 920 KSYS V1.3.0.1 © Copyright International Business Machines Corporation 2019. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too! . xi Comments welcome. xii Stay connected to IBM Redbooks . xii Chapter 1. Introduction to high availability and disaster recovery . 1 1.1 General high availability and disaster recovery overview . 2 1.1.1 General concepts . 3 1.1.2 Outage-related differences . 4 1.1.3 High availability and continuous availability . 6 1.1.4 Disaster recovery . 9 1.2 Restart technologies and clustering methods . 10 1.2.1 Live Partition Mobility . 10 1.2.2 Simplified Remote Restart . 13 1.2.3 IBM PowerHA SystemMirror . 15 1.2.4 Comparison of solutions . 16 1.3 VM Recovery Manager HA . 17 1.4 IBM VM Recovery Manager DR . 18 1.4.1 Implementing IP change scripts on AIX . 19 1.4.2 Implementing IP change scripts on Linux . 29 Chapter 2. IBM VM Recovery Manager High Availability components . 39 2.1 Overview and capabilities . 40 2.1.1 Overview . 40 2.1.2 Capabilities . 41 2.2 Solution components and detailed architecture . 42 2.2.1 Simplified component model. 42 2.2.2 Refined component model . 44 2.2.3 KSYS test cluster example . 48 2.2.4 KSYS as a Resource Monitoring and Control subsystem. 52 2.2.5 KSYS daemon restart exercise. 62 2.2.6 KSYS subsystem functional modules . 91 2.2.7 Host monitor, Health Status Database, and related VIOS internals . 114 2.2.8 VM Agent architecture . 164 2.2.9 HVNCP protocol . 199 2.3 Communication flows . 202 2.3.1 Discovery of a VM that is enabled for monitoring . 203 2.3.2 Failure Detection Engine: QuickQuery and NeedsAttention flows . 234 2.3.3 Application Reporting flow . 262 Chapter 3. Planning and deploying IBM VM Recovery Manager High Availability for IBM Power Systems . 265 3.1 VM Recovery Manager HA requirements . 266 3.1.1 Software requirements . 266 3.1.2 Firmware requirements . 267 © Copyright IBM Corp. 2019. All rights reserved. iii 3.1.3 Installation and configuration requirements . 267 3.1.4 Host group requirements . 268 3.1.5 HMC requirements . 268 3.1.6 Network requirements. 269 3.1.7 GUI requirements . 270 3.2 VM Recovery Manager HA coexistence with other products . 271 3.2.1 IBM Power Virtualization Center . 271 3.2.2 IBM PowerHA SystemMirror Software . 271 3.2.3 PowerVM NovaLink . 271 3.3 VM Recovery Manager HA restrictions . 272 3.3.1 Migration restriction. 272 3.3.2 VM Agent restrictions . 272 3.3.3 GUI restrictions . 273 3.3.4 VM Recovery Manager HA filesets and structure . 273 3.4 Installing the VM Recovery Manager HA solution. 274 3.4.1 Installing the VIOS interim fix . 275 3.4.2 Installing the KSYS software. 277 3.4.3 Installing VM Agents . 279 3.5 Configuring VM Recovery Manager HA . 281 3.5.1 Initializing the KSYS cluster . 283 3.5.2 Adding HMCs . 284 3.5.3 Adding hosts . 285 3.5.4 Creating host groups. 286 3.5.5 Discovering and verifying the KSYS configuration . 289 3.6 Setting up HA policies . 297 3.6.1 HA monitoring policies . 297 3.6.2 Environment-level policies . 298 3.6.3 VM-level policies . 305 3.7 Setting up the VM Agent . 309 3.7.1 The ksysvmmgr command and utility . 310 3.7.2 Application Management Engine . 312 3.8 Setting contacts for event notification . ..