Академический Документы
Профессиональный Документы
Культура Документы
Ilya Krutov Frederik Aouizerats Brandon Harrell MinChul Kim Stanimir Markov
ibm.com/redbooks
8060edno.fm
International Technical Support Organization Implementing Systems Management of IBM PureFlex System July 2012
SG24-8060-00
8060edno.fm
Note: Before using this information and the product it supports, read the information in Notices on page vii.
First Edition (July 2012) This edition applies to IBM PureFlex System. This document was created or updated on August 18, 2012.
Copyright International Business Machines Corporation 2012. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
8060TOC.fm
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The team who wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Now you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix ix xi xi xi
Part 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. Introduction to IBM PureFlex System and IBM Flex System . . . . . . . . . . . . 1.1 IBM PureFlex System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 IBM PureFlex System capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 IBM Flex System: The building blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.1 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 Compute nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.3 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.4 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.5 Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4 6 7 7 7 8 8 8
Chapter 2. IBM PureFlex System management devices and appliances . . . . . . . . . . . . 9 2.1 Management network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2 Chassis Management Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.3 Compute node management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1 Integrated Management Module II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.2 Flexible service processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.4 I/O modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.5 IBM Flex System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.5.1 Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.5.2 Software features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Part 2. Chassis Management Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Chapter 3. Planning for Chassis Management Module-based systems management 3.1 CMM-based management network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 CMM interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 CMM Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1 Security policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2 User account policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.3 External authentication of certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 FoD Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4. Chassis Management Module operations . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Initial deployment of Chassis Management Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1 Connecting to the CMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.2 Configuring the CMM through the Initial Setup Wizard . . . . . . . . . . . . . . . . . . . . . 4.1.3 Updating the Chassis Management Module firmware . . . . . . . . . . . . . . . . . . . . . 4.1.4 Preparing for Chassis Management Module redundancy . . . . . . . . . . . . . . . . . . . 4.1.5 Configuring Chassis Management Modules user authority . . . . . . . . . . . . . . . . .
Copyright IBM Corp. 2012. All rights reserved.
27 28 28 29 30 31 32 34 35 36 36 37 47 51 53 iii
8060TOC.fm
4.1.6 Restoring a Chassis Management Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Chassis Management Module management tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 Monitoring the chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2 Monitoring multiple chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3 Event notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.4 Chassis Management Module Features on Demand . . . . . . . . . . . . . . . . . . . . . . 4.2.5 Chassis management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.6 Using the Chassis Management Module CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57 58 58 59 60 63 65 75
Part 3. IBM Flex System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Chapter 5. Planning for IBM Flex System Manager-based systems management . . . 81 5.1 General planning information on systems management . . . . . . . . . . . . . . . . . . . . . . . . 82 5.1.1 FSM network integration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 5.1.2 Planning for security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 5.1.3 Planning for FoD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 5.1.4 Agents and tasks supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 5.1.5 Planning for managing the networking infrastructure . . . . . . . . . . . . . . . . . . . . . . 88 5.1.6 Planning for managing the storage infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . 89 5.1.7 Planning for IBM Fabric Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 5.2 Planning for managing the virtualization environment with Flex System Manager . . . . 92 5.2.1 Virtualization and task supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.2.2 Planning for KVM virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 5.2.3 Planning for PowerVM virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 5.2.4 Planning for VMware virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.2.5 Planning for Hyper-V virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Chapter 6. IBM Flex System Manager initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 FSM initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1 Flex System Manager startup wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 Update the FSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Select chassis to manage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4 Acquire updates for chassis components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 FSM Eth1 network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6 Updating the CMM firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Discovery and inventory collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.1 Discovery Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.2 Manual inventory collection of the chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.3 Discovery of compute nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.4 I/O Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8 Operating system discovery, access and inventory . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9 Updating compute node firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10 Updating I/O module Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11 Initial configuration of compute nodes and I/O modules . . . . . . . . . . . . . . . . . . . . . . 6.12 Manage Feature-on-Demand keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13 Discover and manage V7000 (Storage Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13.1 Discover an IBM Storwize V7000 to manage from IBM Flex System Manager Storage Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13.2 Collect inventory on the discovered V7000. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13.3 Overview of Storwize V7000 systems management. . . . . . . . . . . . . . . . . . . . . 6.13.4 External FC SAN switch discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.14 Configuring the network parameters (Network Control) . . . . . . . . . . . . . . . . . . . . . .
113 114 114 129 130 132 141 150 154 157 163 167 177 184 184 193 197 197 205 205 209 213 218 226
iv
8060TOC.fm
Chapter 7. Managing chassis hardware components with IBM Flex System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 7.1 Using the Chassis Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 7.2 Using Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 7.3 Creating an event filter from an event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 7.4 Define event actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 7.5 Automating tasks with event automation plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 7.6 Handling serviceable hardware problems with IBM Flex System Manager Service and Support Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 7.7 Integrating FSM with your enterprise monitoring system . . . . . . . . . . . . . . . . . . . . . . 264 7.8 Using Monitors and Thresholds to monitor system status and health. . . . . . . . . . . . . 265 7.9 Remote management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Chapter 8. Managing KVM environment with IBM Flex System Manager . . . . . . . . . 8.1 KVM management architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 KVM platform agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2 KVM Platform Agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.3 KVM host discovery, granting access and inventory collection. . . . . . . . . . . . . . 8.3 Image repository for KVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.2 Common Agent installation on a KVM host image repository . . . . . . . . . . . . . . . 8.3.3 Subagent installation on a KVM host image repository. . . . . . . . . . . . . . . . . . . . 8.3.4 Host mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.5 Discover and manage V7000 storage system . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.6 Discover and manage SAN switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.7 Discover and Configure an image repository server for SAN storage . . . . . . . . 8.4 Create SAN Storage system pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5 Create KVM server system pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.1 Add Host to an existing Server system pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6 Overview of Network system pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7 Operate a KVM virtual infrastructure with FSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7.1 Import virtual appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7.2 Deploy a Virtual Appliance to create a Virtual Server . . . . . . . . . . . . . . . . . . . . . 8.7.3 Capture a virtual server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7.4 Relocate virtual servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 9. Managing PowerVM environment with IBM Flex System Manager . . . . . 9.1 Initial deployment of virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.1 Solution architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.2 Setting up VIOS and NIM server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 Capture virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.1 Capture AIX using Network Installation Manager (NIM) . . . . . . . . . . . . . . . . . . . 9.2.2 Capture AIX using storage copy services (SCS) . . . . . . . . . . . . . . . . . . . . . . . . 9.3 Deploy virtual machines based on previously captured . . . . . . . . . . . . . . . . . . . . . . . 9.3.1 Deploy virtual machines using LPP_source . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.2 Deploy a virtual machine using mksysb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.3 Deploy a virtual machine using SCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4 Relocate virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.1 Relocating virtual servers manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 292 292 292 294 296 298 299 301 306 309 315 315 315 318 321 326 329 330 331 335 342 351 355 356 356 357 369 370 394 416 416 422 425 429 430
Chapter 10. Managing VMware environment with IBM Flex System Manager . . . . . 437 10.1 Environment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 10.2 Deploy a VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Contents
8060TOC.fm
Relocate a VM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relocate all VMs from a host and save a relocation plan . . . . . . . . . . . . . . . . . . . . . Modify Virtual Server resource allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable DRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Put a host in maintenance mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Topology view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automating preventive actions in response to hardware alerts. . . . . . . . . . . . . . . . .
455 459 463 468 471 475 481 495 496 496 502 502 506 507 507
Chapter 11. Managing Hyper-V environment with IBM Flex System Manager . . . . . 11.1 Operate the FSM in the Hyper-V environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1 Install agent on an Hyper-V node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Manage Hyper-V from FSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.1 Deploy virtual servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.2 Edit virtual server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.3 Delete a virtual server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.4 View virtual server network topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 513 513 513 513
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
vi
8060spec.fm
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
vii
8060spec.fm
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol ( or ), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:
AIX BladeCenter Electronic Service Agent FlashCopy Global Technology Services IBM Flex System IBM NetView Power Systems POWER7 PowerVM POWER PureApplication PureFlex PureSystems Redbooks Redbooks (logo) Storwize System Storage System x Tivoli Enterprise Console Tivoli X-Architecture
The following terms are trademarks of other companies: Intel Xeon, Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. ITIL is a registered trademark, and a registered community trademark of The Minister for the Cabinet Office, and is registered in the U.S. Patent and Trademark Office. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. NetApp, and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. and other countries. Java, and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Other company, product, or service names may be trademarks or service marks of others.
viii
8060pref.fm
Preface
To meet todays complex and ever-changing business demands, you need a solid foundation of compute, storage, networking, and software resources. This system must be simple to deploy, and be able to quickly and automatically adapt to changing conditions. You also need to be able to take advantage of broad expertise and proven guidelines in systems management, applications, industry solutions, and more. The IBM PureFlex System combines no-compromise system designs along with built-in expertise and integrates them into complete, optimized scalable solutions. With IBM Flex System Manager, multiple solution components including compute nodes, network and storage infrastructures, storage systems, and heterogeneous virtualization environments can be managed from a single panel. This IBM Redbooks publication introduces IBM PureFlex System, describes its management devices and appliances, and provides systems management implementation guidelines for Linux KVM, IBM PowerVM, VMware vSphere and Microsoft Hyper-V virtualization environments. This book is intended for the IT community of clients, Business Partners, and IBM employees who is interested in planning and implementing of and getting hands-on experience in systems management of the new offering.
ix
8060pref.fm
systems and various hypervisors. He has worked for IBM since 2000 and is based in Raleigh, NC. MinChul Kim is a Senior IT Specialist with IBM Korea and works in the Systems and Technology Group as a presales client technical architect. He has 12 years of experience in IT industry. He joined IBM GTS as Power Systems/Storage engineer in 2004, then moved to IBM Power Systems FTSS. His areas of expertise include IT simplification consulting, IBM Power Systems, AIX, and IBM System Storage. Other areas of IBM Systems interest include System x and VMware. Stanimir Markov is a Technical Leader of VMware Center of Excellence in IBM Global Technology Services and a core member of IBM virtualization development team. He leads the virtualization efforts in large scale transformation projects for enterprise customers and has a key role in defining VMware best practices across IBM GTS Delivery. Along his work on design, implementation and support of complex virtual infrastructures, Stanimir, being a VMware Certified Instructor, delivers authorized VMware classes. Stanimir has the highest VMware certification - VMware Certified Design Expert. He also holds a bachelor degree in computer science, is certified in Microsoft and Citrix technologies and ITIL. Stanimir has been with IBM since 2006.
Thanks to the following people for their contributions to this project: Kevin Barnes, Tamikia Barrow, Mary Comianos, Shari Deiana, Cheryl Gera, Linda Robinson, David Watts, Erica Wazewski International Technical Support Organization, Raleigh Center Kerry Anders, Kenneth Brown, Trina Bunting, Chris Cort, Rick McBride, Dean Price, Bob Schuster, David Tareen IBM
8060pref.fm
Comments welcome
Your comments are important to us! We want our books to be as helpful as possible. Send us your comments about this book or other IBM Redbooks publications in one of the following ways: Use the online Contact us review Redbooks form found at: ibm.com/redbooks Send your comments in an email to: redbooks@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400
Preface
xi
8060pref.fm
xii
Part 1_Introduction.fm
Part 1
Part
Introduction
This book is divided into multiple parts. In this part we introduce IBM PureFlex System and IBM Flex System and describe their management architecture, devices and appliances. This part includes the following chapters: Chapter 1, Introduction to IBM PureFlex System and IBM Flex System on page 3 Chapter 2, IBM PureFlex System management devices and appliances on page 9
Part 1_Introduction.fm
Introduction.fm
Chapter 1.
Introduction.fm
IBM PureFlex System uses workload placement based on virtual machine compatibility and resource availability. Using built-in virtualization across servers, storage, and networking, the infrastructure system enables automated scaling of resources and true workload mobility. IBM PureFlex System has undergone significant testing and experimentation so that it can mitigate IT complexity without compromising the flexibility to tune systems to the tasks businesses demand. By providing both flexibility and simplicity, IBM PureFlex System can provide extraordinary levels of IT control, efficiency, and operating agility. This combination 4
Implementing Systems Management of IBM PureFlex System
Introduction.fm
enables businesses to rapidly deploy IT services at a reduced cost. Moreover, the system is built on decades of expertise. This expertise enables deep integration and central management of the comprehensive, open-choice infrastructure system. It also dramatically cuts down on the skills and training required for managing and deploying the system. IBM PureFlex System combines advanced IBM hardware and software along with patterns of expertise. It integrates them into three optimized configurations that are simple to acquire and deploy so you get fast time to value. The PureFlex System has the following configurations: IBM PureFlex System Express, which is designed for small and medium businesses and is the most affordable entry point for PureFlex System. IBM PureFlex System Standard, which is optimized for application servers with supporting storage and networking, and is designed to support your key ISV solutions. IBM PureFlex System Enterprise, which is optimized for transactional and database systems. It has built-in redundancy for highly reliable and resilient operation to support your most critical workloads. These configurations are summarized in Table 1-1.
Table 1-1 IBM PureFlex System configurations Component IBM PureFlex System 42U Rack IBM Flex System Enterprise Chassis IBM Flex System Fabric EN4093 10 Gb Scalable Switch IBM Flex System FC3171 8 Gb SAN Switch IBM Flex System Manager Node IBM Flex System Manager software license Chassis Management Module Chassis power supplies (std/max) Chassis 80 mm fan modules (std/max) IBM Storwize V7000 Disk System IBM Storwize V7000 Software IBM PureFlex System Express 1 1 1 IBM PureFlex System Standard 1 1 1 IBM PureFlex System Enterprise 1 1 2 with both port-count upgrades 2 1 Flex System Manager Advanced with 3-year service and support 2 6/6 8/8 Yes (redundant controller) Base with 3-year software maintenance agreement
1 1 IBM Flex System Manager with 1-year service and support 2 2/6 4/8 Yes (redundant controller) Base with 1-year software maintenance agreement
2 1 IBM Flex System Manager Advanced with 3-year service and support 2 4/6 6/8 Yes (redundant controller) Base with 3-year software maintenance agreement
The fundamental building blocks of IBM PureFlex System solutions are the IBM Flex System Enterprise Chassis complete with compute nodes, networking, and storage.
Chapter 1. Introduction to IBM PureFlex System and IBM Flex System
Introduction.fm
Introduction.fm
1.3.1 Management
IBM Flex System Manager is designed to optimize the physical and virtual resources of the IBM Flex System infrastructure while simplifying and automating repetitive tasks. It provides easy system set-up procedures with wizards and built-in expertise, and consolidated monitoring for all of your resources, including compute, storage, networking, virtualization, and energy. IBM Flex System Manager provides core management functionality along with automation. It is an ideal solution that allows you to reduce administrative expense and focus your efforts on business innovation. A single user interface controls these features: Intelligent automation Resource pooling Improved resource utilization Complete management integration Simplified setup
Introduction.fm
With support for a range of hypervisors, operating systems, and virtualization environments, the compute nodes provide the foundation for these applications: Virtualization solutions Database applications Infrastructure support Line of business applications
1.3.3 Storage
The storage capabilities of IBM Flex System give you advanced functionality with storage nodes in your system, and take advantage of your existing storage infrastructure through advanced virtualization. IBM Flex System simplifies storage administration with a single user interface for all your storage. The management console is integrated with the comprehensive management system. These management and storage capabilities allow you to virtualize third-party storage with nondisruptive migration of your current storage infrastructure. You can also take advantage of intelligent tiering so you can balance performance and cost for your storage needs. The solution also supports local and remote replication, and snapshots for flexible business continuity and disaster recovery capabilities.
1.3.4 Networking
The range of available adapters and switches to support key network protocols allow you to configure IBM Flex System to fit in your infrastructure. However, you can do so without sacrificing being ready for the future. The networking resources in IBM Flex System are standards-based, flexible, and fully integrated into the system. This combination gives you no-compromise networking for your solution. Network resources are virtualized and managed by workload. And these capabilities are automated and optimized to make your network more reliable and simpler to manage. IBM Flex System gives you these key networking capabilities: Supports the networking infrastructure you have today, including Ethernet, Fibre Channel and InfiniBand Offers industry-leading performance with 1 Gb, 10 Gb, and 40 Gb Ethernet; 8 Gb and 16 Gb Fibre Channel; and FDR InfiniBand Provides pay-as-you-grow scalability so you can add ports and bandwidth when needed
1.3.5 Infrastructure
The IBM Flex System Enterprise Chassis is the foundation of the offering, supporting intelligent workload deployment and management for maximum business agility. The 14-node, 10U chassis delivers high-performance connectivity for your integrated compute, storage, networking, and management resources. The chassis is designed to support multiple generations of technology, and offers independently scalable resource pools for higher utilization and lower cost per workload.
Management_Overview.fm
Chapter 2.
Management_Overview.fm
Enterprise Chassis Flex System Manager System x compute node Power Systems compute node
CMM
Port
I/O bay 1
I/O bay 2
CMM
CMM
Management workstation
One of the key functions that the data network supports is discovery of operating systems on the various network endpoints. Discovery of operating systems by the FSM is required to support software updates on an endpoint such as a compute node. The FSM Checking and
10
Management_Overview.fm
Updating Compute Nodes wizard assists you in discovering operating systems as part of the initial setup.
a. The first feature code listed is for x-config configurations. The second feature code is for e-config configurations.
Figure 2-2 shows the location of the CMM bays on the back of the Enterprise Chassis.
11
Management_Overview.fm
The CMM has the following connectors: USB connection: Can be used for insertion of a USB media key for tasks such as firmware updates. 10/100/1000 Mbps RJ45 Ethernet connection: For connection to a management network. The CMM can be managed through this Ethernet port. Serial port (mini-USB): For local serial (command-line interface (CLI)) access to the CMM. Use the cable kit listed in Table 2-2 for connectivity.
Table 2-2 Serial cable specifications Part number 90Y9338 Feature codea A2RR / None Description IBM Flex System Management Serial Access Cable Contains two cables: Mini-USB-to-RJ45 serial cable Mini-USB-to-DB9 serial cable
a. The first feature code listed is for x-config configurations. The second feature code is for e-config configurations.
The CMM has the following LEDs that provide status information: Power-on LED Activity LED Error LED Ethernet port link and port activity LEDs The CMM also incorporates a reset button. It has two functions, dependent upon how long the button is held in: When pressed for less than 5 seconds, the CMM restarts. When pressed for more than 5 seconds (for example 10-15 seconds), the CMM configuration is reset to manufacturing defaults and then restarts.
12
Management_Overview.fm
Through an embedded firmware stack, the CMM implements functions to monitor, control, and provide external user interfaces to manage all chassis resources. The CMM allows you to perform these functions: Define login IDs and passwords Configure security settings such as data encryption and user account security Select recipients for alert notification of specific events Monitor the status of the compute nodes and other components Find chassis component information Discover other chassis in the network and enable access to them Control the chassis, compute nodes, and other components Access the I/O modules to configure them Change the startup sequence in a compute node Set the date and time Use a remote console for the compute nodes Enable multi-chassis monitoring Set power policies and view power consumption history for chassis components
The management controllers for the various Enterprise Chassis components have the following default IPv4 addresses: CMM:192.168.70.100 Compute nodes: 192.168.70.101-114 (corresponding to the slots 1-14 in the chassis) I/O Modules: 192.168.70.120-123 (sequentially corresponding to chassis bay numbering) In addition to the IPv4 address, all I/O modules also support link-local IPv6 addresses and configurable external IPv6 addresses.
13
Management_Overview.fm
IMM2 incorporates a new web user interface that provides a common look and feel across all IBM System x software products. The IMM2 provides the following major features as standard: IPMI v2.0-compliance Remote configuration of IMM2 and UEFI settings without the need to power on the server Remote access to system fan, voltage, and temperature values Remote IMM and UEFI update UEFI update when the server is powered off Remote console by way of a serial over LAN Remote access to the system event log Predictive failure analysis and integrated alerting features (for example, by using Simple Network Management Protocol (SNMP)) Remote presence, including remote control of server by using a Java or Active x client Operating system failure window (blue screen) capture and display through the web interface Virtual media that allow the attachment of a diskette drive, CD/DVD drive, USB flash drive, or disk image to a server Syslog alerting mechanism that provides an alternative to email and SNMP traps Support for Features On Demand (FoD) enablement of server functions, option card features, and System x solutions and applications For more detailed information, see Integrated Management Module II Users Guide http://ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5086346 IMM and IMM2 Support on IBM System x and BladeCenter Servers, TIPS0849: http://www.redbooks.ibm.com/abstracts/tips0849.html
14
Management_Overview.fm
attached to the FSM. SOL provides console redirection for both Software Management Services (SMS) and the server operating system. The SOL feature redirects server serial-connection data over a LAN without requiring special cabling by routing the data through the CMM network interface. The SOL connection enables POWER7-based compute nodes to be managed from any remote location with network access to the CMM. SOL offers the following functions: Remote administration without KVM Reduced cabling and no requirement for a serial concentrator Standard Telnet/SSH interface, eliminating the requirement for special client software The Chassis Management Module CLI provides access to the text-console command prompt on each server through a SOL connection. This configuration allows the POWER7-based compute nodes to be managed from a remote location.
15
Management_Overview.fm
Ability to send events, SNMP traps, and event logs to the CMM, including security audit logs. IPv4 and IPv6 on by default. The CMM management port supports IPv4 and IPv6 (IPV6 support includes the use of link local addresses. Port mirroring capabilities: Port mirroring of CMM ports to both internal and external ports. For security reasons, the ability to mirror the CMM traffic is hidden and is available only to development and service personnel Management virtual local area network (VLAN) for Ethernet switches: A configurable management 802.1q tagged VLAN in the standard VLAN range of 1 - 4094. It includes the CMMs internal management ports and the I/O modules internal ports that are connected to the nodes.
IBM Flex System Manager is designed to help you get the most out of your IBM PureFlex System while automating repetitive tasks. IBM Flex System Manager can reduce the number of manual navigational steps for typical management tasks. From simplified system setup procedures with wizards and built-in expertise to consolidated monitoring for all of your physical and virtual resources (compute, storage, and networking), IBM Flex System Manager provides core management functionality along with automation so you can focus your efforts on business innovation.
16
Management_Overview.fm
IBM Flex System Manager has the following key features: Optimizing your workload management through built-in expertise With a workload-optimized approach, you can decrease infrastructure costs and improve service levels. You can create and modify system pools using virtual workloads, make dynamic virtual workload adjustments, and move workloads within system pools, resulting in an optimized virtual environment with increased resilience to cope with planned or unplanned down time. A system pool is a group of virtualized system components that are managed as a single entity, allowing you to manage the pools with the simplicity of managing a single system, which is an essential capability for moving to cloud computing and a dynamic infrastructure. Managing all of your resources with one solution Beginning with deployment through maintenance, upgrades, and problem resolution, IBM Flex System Manager is designed to provide all of the key management functions for your integrated IT resources from a single, easy to use interface. From your office or remotely through a secure connection, you can manage your compute, storage, network and virtualized resources. Compute Auto discovery and setup wizards make deploying compute nodes quick and easy using the IBM Flex System Manager. After it is deployed, IBM Flex System Manager provides real-time updates for compute node health summaries. With the ability to define performance thresholds to trigger alerts, you can automate responses to potential problems help keep your critical business applications running at peak performance. IBM Flex System Manager can detect many problems with essential system resources and recover automatically. IBM Flex System Manager can also perform trend analysis to forecast and prevent future problems that otherwise might lead to expensive system outages. Storage IBM Flex System Manager helps you address storage management challenges from device deployment and through the data life cycle. Storage deployment capabilities in the IBM Flex System Manager include storage device discovery and simple logical and physical device configuration from a single interface. IBM Flex System Manager can provide physical and logical storage topology views and can show relationships between storage and server resources, giving you the ability to track key resources based on their business usage. Provisioning capabilities include image management for simple virtual machine creation, deployment and cloning. You can also manage storage system pools for data life cycle management and storage placement based on business policies. Networking Networking resources allow your virtualized compute and storage resources to communicate and function in the cloud. IBM Flex System Manager delivers end-to-end network management for your PureFlex System from a single tool. IBM Flex System Manager supports automated network discovery to speed deployments. It also offers a graphical view of the network from the integrated user interface. Network resources are pooled and virtualized. With logical network profiles, you can quickly and easily specify the network connectivity characteristics of a virtual machine. IBM Flex System Manager supports automatic provisioning and simple movements of virtual LANs for virtual machines. You can manage MAC addresses for virtual network interface cards. IBM Flex System Manager provides detailed network usage and performance statistics for virtual machines and physical compute nodes so you can track valuable network resources and manage them based on your business needs.
17
Management_Overview.fm
Virtualization The basic virtualization functions in the IBM Flex System Manager begin with the ability to create and manage virtual servers from pooled resources. IBM Flex System Manager takes this capability further through the application of built-in expertise to make provisioning and deployment of virtual machines fast and easy. After virtual machines are deployed, the virtualization features of IBM Flex System Manager are designed to help you manage these virtualized resources efficiently. Automation features such as dynamic virtual machine placement, automated optimization, and resource balancing simplify virtualization management. IBM Flex System Manager also helps you keep your virtual machines up and running with support for nondisruptive updates, virtual machine mobility, and a range of other resilience features. The IBM Flex System Manager appliance is based on an x86 compute node that comes with preloaded management software. The software contains a set of components that are responsible for performing certain management functions. These components must be activated using the available IBM Feature on Demand (FoD) software entitlement licenses, and they are licensed on a per-chassis basis, that is, you need one license for each chassis you plan to manage. The management node comes standard without any entitlement licenses, so you must purchase a license to enable the required FSM functionality. The part number to order the management node is shown in Table 2-4.
Table 2-4 Ordering information for IBM Flex System Manager node Part number 8731A1xa Description IBM Flex System Manager node
a. x in the Part number represents a country-specific letter (for example, the EMEA part number is 8731A1G, and the US part number is 8731A1U). Ask your local IBM representative for specifics.
The part numbers to order FoD software entitlement licenses are shown in the following tables. The part numbers for the same features are different in different countries. Ask your local IBM representative for specifics. Table 2-5 shows the information for the United States, Canada, Asia Pacific, and Japan.
Table 2-5 Ordering information for FoD licenses (United States, Canada, Asia Pacific, Japan) Part number Base feature set 90Y4217 90Y4222 IBM Flex System Manager Per Managed Chassis with 1 Year SW S&S IBM Flex System Manager Per Managed Chassis with 3 Year SW S&S Description
Advanced feature set upgradea 90Y4249 00D7554 IBM Flex System Manager, Advanced Upgrade, Per Managed Chassis with 1-Year SW S&S IBM Flex System Manager, Advanced Upgrade, Per Managed Chassis with 3-Year SW S&S
18
Management_Overview.fm
Table 2-6 shows the ordering information for Latin America and Europe/Middle East/Africa.
Table 2-6 Ordering information for FoD licenses (Latin America and Europe/Middle East/Africa) Part number Base feature set 95Y1174 95Y1179 IBM Flex System Manager Per Managed Chassis with 1 Year SW S&S IBM Flex System Manager Per Managed Chassis with 3 Year SW S&S Description
Advanced feature set upgradea 94Y9219 94Y9220 IBM Flex System Manager, Advanced Upgrade, Per Managed Chassis with 1 Year SW S&S IBM Flex System Manager, Advanced Upgrade, Per Managed Chassis with 3 Year SW S&S
IBM Flex System Manager base feature set offers the following functions: Support for up to four managed chassis Support for up to 5,000 managed elements Auto-discovery of managed elements Overall health status Monitoring and availability Hardware management Security management Administration Network management (Network Control) Storage management (Storage Control) Virtual machine life cycle management (VMControl Express) I/O address management (IBM Fabric Manager) The IBM Flex System Manager advanced feature set upgrade offers the following advanced features: Image management (VMControl Standard) Pool management (VMControl Enterprise) Important: IBM Flex System Manager base license is a prerequisite for the Advanced Upgrade license.
19
Management_Overview.fm
Two IBM 200 GB SATA 1.8" MLC SSD configured in a RAID 1 One IBM 1 TB 7.2 K 6 Gbps NL SATA 2.5" SFF HS HDD Dual-port 10 Gb Ethernet Emulex BladeEngine 3 (BE3) network controller for data network connections Dual-port Broadcom 5718-based network adapter with integrated Broadcom 5389 8-port basic L2 switch for internal chassis management network connections Integrated Management Module II (IMM2) The FSM Manager Node ships with a preinstalled software management stack based on RHEV-H. Figure 2-5 shows the internal layout of the FSM. Filler slot for Processor 2 Processor 1
Drive bays
Figure 2-5 Internal view that shows the major components of IBM Flex System Manager
20
Management_Overview.fm
Front controls
The diagram in Figure 2-6 shows the front of an FSM with the location of the control and LEDs.
Solid state drive LEDs
a aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aa aaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aaaa aa aaaaaaaaaaaaaaaaaaaaaaaaaaaa 2 aaaaaaaaaaaaaaaaaaaaaaaa a aa aa aa aa aa aaaa aa aa aa aaaa a aaaaaaaaaaaaaaaaaaaa aa a aa aaaa aaaa aaaaaaaaaaaaaaaaaa aaaa aa aa aa aa aa aa aa a aa aa aa aa aa aa aa aa aa aa aa a 1 a aaaaaa aaaa aaaa aa aa aa aa aa aa aa aa aa aa aa aaaaaaaa aaaa aaaa aa aa aa aa aa aa aa aa aa a a a a aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aaaaaaaaaaaaaa aa aa aa aa aa aa aa aa aa aa aa a a a aa a aa a aa a aa aa aa aa aa aa aa aa aaaaaaaaaaaaa a aaaaaaaaaaaaaaaaaaaaaa aa a a a a a a a a a a a aaaaaaaaaaaa 0 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Power button/LED
Identify LED
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa a a aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aaaa a aaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aa a aaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaa aaaa aaaa aa aa a aa aaaa aaaa aaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aa aaaa aa aa aa a a a a a a a a a a a aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aaaa aa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaa aa aa aa aa aa aaaaaaaaaaaaaaaaaaaaaa aaa aa aa aa aa aa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaa aaaaaaaaaaaaaaaaaaaaaa aaa a aa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa a a a a a aaaaaaaaaaaaaaaaaaaaaaaaaaaa a aaaa aaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaa aaaa aa aa aaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaa a aa aa aaaaaa aa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa a a a a aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Fault Hard disk drive LED status LED Check log LED
Storage
The FSM ships with 2 x IBM 200 GB SATA 1.8" MLC SSD and 1 x IBM 1 TB 7.2K 6 Gbps NL SATA 2.5" SFF HS HDD drives. The 200 GB SSD drives are configured in an RAID-1 pair that provides roughly 200 GB of usable space. The 1 TB SATA drive is not part of a RAID group. The partitioning of the disks is listed in Table 2-7
Table 2-7 Detailed SSD and HDD disk partitioning Physical disk SSD SSD SSD HDD HDD HDD HDD HDD Virtual disk size 50 MB 60 GB 80 GB 40 GB 40 GB 60 GB 80 GB 30 GB Description Boot disk OS/Application disk Database disk Update repository Dump space Spare disk for OS/Application Spare disk for database Service Partition
21
Management_Overview.fm
Network management Management of network switches from a variety of vendors. Discovery, inventory, and status monitoring of switches. Graphical network topology views. Support for KVM, pHyp, VMware virtual switches, and physical switches. VLAN configuration of switches. Integration with server management. Per-virtual machine network usage and performance statistics provided to VMControl. Logical views of servers and network devices grouped by subnet and VLAN. Storage management Discovery of physical and virtual storage devices. Support for virtual images on local storage across multiple chassis. Inventory of the physical storage configuration. Health status and alerts. Storage pool configuration. Disk sparing and redundancy management. Virtual volume management. Support for virtual volume discovery, inventory, creation, modification, and deletion. Virtualization management (base feature set) Support for VMware, Hyper-V, KVM, and IBM PowerVM. Creates virtual servers.
22
Management_Overview.fm
Edits virtual servers. Manages virtual servers. Relocates virtual servers. Discovers virtual server, storage, and network resources and visualize the physical-to-virtual relationships. Virtualization management (advanced feature set) Creates new image repositories for storing virtual appliances and discover existing image repositories in your environment. Imports external, standards-based virtual appliance packages into your image repositories as virtual appliances. Captures a running virtual server that is configured the way you want, complete with a guest operating system, running applications, and virtual server definition. Imports virtual appliance packages that exist in the Open Virtualization Format (OVF) from the Internet or other external sources. Deploys virtual appliances quickly to create new virtual servers that meet the demands of your ever-changing business needs. Creates, captures, and manages workloads. Creates server system pools, which enable you to consolidate your resources and workloads into distinct and manageable groups. Deploys virtual appliances into server system pools. Manages server system pools, including adding hosts or additional storage space and monitoring the health of the resources and the status of the workloads in them. Groups storage systems together using storage system pools to increase resource utilization and automation. Manages storage system pools by adding storage, editing the storage system pool policy, and monitoring the health of the storage resources. I/O address management Manages assignments of Ethernet MAC and Fibre Channel WWN addresses. Monitors the health of compute nodes, and automatically, without user intervention, replace a failed compute node from a designated pool of spare compute nodes. Preassigns MAC addresses, WWN addresses, and storage boot targets for the compute nodes. Creates addresses for compute nodes, saves the address profiles, and deploys the addresses to the slots in the same or different chassis. Additional features Resource-oriented chassis map provides an instant graphical view of chassis resources, including nodes and I/O modules. A fly-over provides an instant view of an individual server's (node) status and inventory. A chassis map provides an inventory view of chassis components, a view of active status requiring administrative attention, and a compliance view of server (node) firmware. Actions can be taken on nodes, such as working with server-related resources, showing and installing updates, submitting service requests, and launching into the remote access tools.
Chapter 2. IBM PureFlex System management devices and appliances
23
Management_Overview.fm
Remote console Open video sessions and mount media, such as DVDs with software updates, to their servers from their local workstation. Remote Keyboard, Video, and Mouse (KVM) connections. Remote Virtual Media connections (mount CD/DVD/ISO/USB media). Power operations against servers (Power On/Off/Restart).
Hardware detection and inventory creation Firmware compliance and updates Automatic detection of hardware failures Provides alerts. Takes corrective action. Notifies IBM of problems to escalate problem determination.
Health status (such as processor utilization) on all hardware devices from a single chassis view. Administrative capabilities, such as setting up users within profile groups, assigning security levels, and security governance. For more information, see the IBM Flex System Manager product publications available from the IBM Flex System Information Center at: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp
24
Part 2_CMM.fm
Part 2
Part
25
Part 2_CMM.fm
26
Planning_CMM.fm
Chapter 3.
27
Planning_CMM.fm
IMM
FSP
CMM
Port
I/O bay 1
I/O bay 2
CMM
CMM
The CMM-based management functionality is limited to the hardware management and alerting capabilities provided by the CMMs themselves and IMMs or FSPs, as described in 2.2, Chassis Management Module on page 11 and 2.3, Compute node management on page 13.
28
Planning_CMM.fm
single RJ-45 Ethernet connector on the CMM or from any other system that is connected to the same (management) network. The CMM has the following default IPv4 settings: IP address: 192.168.70.100 Subnet: 255.255.255.0 User ID: USERID (all capital letters) Password: PASSW0RD (all capital letters, with a zero instead of the letter O) The CMM does not have a fixed static IPv6 IP address by default. Initial access to the CMM in an IPv6 environment can be done by either using the IPv4 IP address or the IPv6 link-local address. The IPv6 link-local address is automatically generated based on the MAC address of the CMM. By default, the CMM is configured to respond to DHCP first before using its static IPv4 address. If you do not want this operation to take place, connect locally to the CMM and change the default IP settings. You can connect locally, for example, by using a mobile computer. Note: Network interfaces on the devices connected to the management network should be on a same IP subnet. These devices include CMMs, IMMs, FSPs, and I/O modules. The web-based GUI brings together all the functionality needed to manage the chassis elements in an easy-to-use fashion with consistency across all System x IMMv2 based platforms. Refer to 4.1.1, Connecting to the CMM on page 36 for instructions how to use the web-based interface to connect to the default CMM address. The CMM command-line interface (CLI) provides direct access to IBM Flex System management functions as an alternative to using the web-based user interface. Using the CLI, you can issue commands to control the power and configuration of the CMM and other components that are in an IBM Flex System Enterprise Chassis. The command-line interface also provides access to the text-console command prompt on each compute node through a Serial over LAN (SOL) connection. You access the CMM CLI through a direct serial or Ethernet connection to the CMM, through a Telnet connection to the IP address of the CMM, or through a Secure Shell (SSH) connection to the CMM. You can initiate connections from the client system by using standard remote communication software; no special programs are required. You do not need any special hardware to use the CMM command-line interface.
29
Planning_CMM.fm
Security enhancements and features provided in the chassis are listed below: Single sign-on (centralized user management) End to end audit logs Secure boot - TPM and CRTM Intel TXT technology (Intel Xeon-based compute nodes) Signed firmware updates to ensure authenticity Secure communications Certificate authority and management Chassis and compute node detection and provisioning Role-based access control Security policy management Same management protocols supported on BladeCenter AMM for backward compatibility Insecure protocols are disabled by default in CMM, with Locks settings to prevent user from inadvertently or maliciously enabling them Supports up to 84 local CMM user accounts Supports up to 32 simultaneous sessions Planned support for DRTM
30
Planning_CMM.fm
Certificates to establish secure, trusted connections for applications that run on the management processors. Note: You cannot access the CMM CLI through Telnet while using the Secure security policy setting.
31
Planning_CMM.fm
The Legacy user account policy establishes a lower level of control over users. It provides a less secure chassis environment than the High setting. If the Legacy user account policy is selected, you can override its default values to create a Custom policy by using the CMM web interface or the CMM CLI. Table 3-1 provides some examples of user account policy settings.
Table 3-1 Account policy settings User account policy setting User authentication method Maximum simultaneous user sessions Maximum login failures Lockout period login failure Description The method for authenticating CMM users (local, LDAP, or both) The number of concurrent login sessions allowed for each user through all CMM interfaces The maximum number of failed login attempts by a user before the account is locked out The amount of time a user account is locked out after the maximum number of unsuccessful login attempts has been reached Whether the CMM follows more secure complex password rules The requirement that users change their password the first time they log in to the CMM The amount of time a user password remains valid before requiring change The minimum amount of time between user password changes The number of password changes before a password can be reused
Complex password Password change on first access Password expiration period Minimum password change interval Password reuse cycle
Depending on the initial user account policy you selected, the user account policy settings will be configured with different values. For example, the user account policy settings Complex password and Password change on first access would be On if you selected High user account policy and Off if you selected Legacy user account policy. For more information on different user account policies, visit http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fco m.ibm.acc.cmm.doc%2Fcli_intro_beforebegin.html
Planning_CMM.fm
The CA certificate in each IBM Flex System Enterprise Chassis is unique. You download CA certificates through the primary CMM in each chassis using the CMM web interface or CLI. After you download each CA certificate, you should import it into your web browser, so that the web browser will trust websites that have a certificate signed by the CA. If there are multiple users who will access the management processors in the IBM Flex System Enterprise Chassis, you can share the CA certificates with the other users. Each user that receives a CA certificate must also import it into their web browser. If your organization has a process for pushing trusted authority certificates to users, you can also use that process. If you change a CA certificate, you must download the new certificate and import it into your web browser, into the Certificate Trust Store of your IBM Flex System Manager management software, into any IBM Systems Director servers that might be in your network, and into any external LDAP servers that might be configured for mutual authentication. This applies for all activities that can change a CA certificate: manual changes, resetting the CMM to defaults, or restoring a CMM configuration from a backup image. If your web browser advises you that a connection is untrusted or a security certificate is invalid, or has any other issue that indicates a certificate exception issue relating to a certificate exception, download and import the CA certificate, making sure to clear all old certificates from the IBM Flex System Enterprise Chassis on all tabs in the certificate pages. You can also try clearing the browser cache. Since some certificate issues impact only certain web browsers, you might be able to correct the condition by switching to a different web browser.
33
Planning_CMM.fm
34
Configuring_CMM.fm
Chapter 4.
35
Configuring_CMM.fm
Note: The Chassis Management Module has the following default settings: Subnet: 255.255.255.0 User ID: USERID (all capital letters) Password: PASSW0RD (note the number zero, not the letter O, in PASSW0RD) IP address: 192.168.70.100
36
Configuring_CMM.fm
3. Log into the CMM using the default credentials: USERID/PASSW0RD. Click Log In, as seen in Figure 4-2 on page 37
This is the Chassis Management Module main page, as shown in Figure 4-3.
37
Configuring_CMM.fm
Follow these steps to manually start the Initial Setup Wizard and perform the initial configuration: 1. From the CMM web interface home page, click Mgt Module Management as shown in Figure 4-4 on page 38
The initial setup wizard is contained in the Configuration menu, as shown in Figure 4-5.
Several options are displayed for managing the Chassis Management Module configuration. 2. For the first time connection, select the Initial Setup Wizard button, as shown in Figure 4-6
38
Configuring_CMM.fm
3. When the wizard starts, the first window displays the steps that will be performed on the left side of the window, and the basic description of the steps in the main field. Figure 4-7 shows the Welcome page of the setup wizard. This wizard is similar to other IBM wizards. Navigation buttons for the wizard are located in the lower left corner of each window. click Next.
39
Configuring_CMM.fm
4. Click Health status on the Inventory and Health page to view the detected components in the Chassis and their current health status, as seen in the Figure 4-8.
If you have saved a configuration file, the Import Existing Configuration page allows you to select the file you created and will automatically fill in the fields of the wizard with the appropriate values, as shown in the Figure 4-9.
40
Configuring_CMM.fm
The General Settings page prompts you to enter some descriptive information about the Chassis, including location and contact person, as shown in the Figure 4-10 on page 41.
41
Configuring_CMM.fm
Set the date and time for the CMM on the Date and Time page, as shown in the Figure 4-11. There are two options to sync the time: using NTP or setting manually.
Each CMM is configured with the same static IP address. You must create a unique static IP address for each CMM. If DHCP is not used, only one CMM at a time can be added onto the network for discovery. Adding more than one CMM to the network without a unique IP address assignment for each will result in IP address conflicts.
42
Configuring_CMM.fm
If you need to set up IPv6, you can use IPv6, as shown in the Figure 4-13 on page 43.
43
Configuring_CMM.fm
You can view the status and configure the options for the I/O modules that are connected to the CMM, as seen in the Figure 4-14.
Choose the security policy for your CMM, as shown in Figure 4-15.
44
Configuring_CMM.fm
Note: When the CMM is set to Secure security mode, only the secure file transfer methods HTTPS and SFTP can be used for firmware updates and other tasks involving file transfers, such as transferring a backup configuration file to restore a configuration. The insecure file transfer protocols HTTP, FTP, and TFTP are disabled when security is set to the Secure mode. For more information on security policies, refer to 3.3, CMM Security on page 29. Set the appropriate DNS options for your CMM, as seen in the Figure 4-16 on page 45.
45
Configuring_CMM.fm
Enter the email addresses where notifications are to be sent as CMM events occur, as shown in Figure 4-17.
46
Configuring_CMM.fm
Confirm all of the information that has been entered in the setup wizard, as seen in the Figure 4-18.
47
Configuring_CMM.fm
To update the CMM firmware, follow these steps: 1. In the CMM web interface, select Firmware from the Mgt Module Management menu, as shown in Figure 3-9
Check the current firmware level, as shown in Figure 4-20. We have only one Chassis Management Module installed. If standby CMM is configured, you can also check the standby CMM firmware level.
48
Configuring_CMM.fm
Click Update, new pop-up screen will show up to update the CMM firmware, as shown in Figure 4-21. Proceed through each step of the wizard by clicking the Next button and entering the information as required.
Click Browse, select CMM firmware file in your local directory, as shown in the Figure 4-22.
49
Configuring_CMM.fm
Choose the behavior after updating the CMM firmware, as shown in the Figure 4-23. Restart CMM manually Restart CMM automatically after updating
50
Configuring_CMM.fm
Verify that update is completed, as shown in the Figure 4-25, and click Finish to restart the CMM or to go back to the CMM management interface if you chose to restart the CMM manually.
51
Configuring_CMM.fm
Configure failover response for the loss of the primary CMM: In the CMM web interface, CMM failover is configured on the Advanced Failover tab on the Management Module Properties page, as shown in Figure 4-26. Select Properties from the Mgt Module Management menu to reach the Management Module Properties page.
Configure failover response for loss of the management network (uplink) connection to the primary CMM: In the CMM web interface, uplink failover is configured on the Ethernet tab on the Network Protocol Properties page. Select Network from the Mgt Module Management menu, then click Advanced Ethernet tab, as shown in Figure 4-27 on page 52.
52
Configuring_CMM.fm
53
Configuring_CMM.fm
You can set up the specific security policy level in two ways: 1. In the CMM web interface, select Security from the Mgt Module Management menu, as shown in Figure 4-29.
2. Then, on the Security Policies page use the slider bar to select Secure, and click Apply as shown in Figure 4-30 on page 54
54
Configuring_CMM.fm
Note: Although you can change individual user account policy settings from the default values for each user account policy type, the security policy of the CMM might require that specific user account policy settings have secure values. For example, if you attempt to change the CMM security policy level from Legacy to Secure, the CMM might require that you change some user account policy settings to secure values before you can change the security policy to Secure. However, if you change the CMM security policy from Secure to Legacy but you do not manually modify any of the user account policy settings, some of these setting will retain their previous secure values. In the CMM web interface, user account security policy settings are on the General tab of the Account Security Level page in the Global Login Settings window. 1. Select User Accounts from the Mgt Module Management menu, as shown in Figure 4-31.
2. Click Global Login Settings on the Accounts tab on the User Accounts page, as shown in Figure 4-32.
55
Configuring_CMM.fm
3. Click Account Security Level tab in the Global Login Settings window, as shown in Figure 4-33.
4. Select Custom Security Settings, High Security Settings or Legacy Security Settings from the menu and click OK, as shown in Figure 4-34.
For more information about the CMM security, refer to 3.3, CMM Security on page 29.
56
Configuring_CMM.fm
2. If you have physical access to the CMM, push the reset button and hold it for approximately 10 seconds.
57
Configuring_CMM.fm
The graphical view of the Chassis is active, so the changes are reflected immediately. The selections available are (matching callouts in Figure 4-37): 1. Selected Active Resource: All major components of the Chassis can be clicked for more information. Select a component of interest (in Figure 4-37, we have selected the IBM Flex System p260 Compute Node), and a pop-up displays information about that component, for example, serial number, name, bay, etc. You can power a component on or off from this pop-up by right click, or view other details about the component. 2. Selected Managed Resource: With a component selected, this box displays several tabs for additional information, for example, events, hardware, firmware, and LEDs. 3. Selected Resource Actions: I/O modules and compute nodes activate the Actions menu, from which you can power on/off, restart, and perform several other tasks. The More actions link provides additional component-specific actions.
58
Configuring_CMM.fm
Use Multi-Chassis Monitor page to view the state of all compute nodes and management nodes in multiple networked chassis from one location. Monitor the current status of installed compute nodes and management nodes in multiple chassis and discover recently connected ones on Multi-Chassis Monitor page, as shown in Figure 4-39.
59
Configuring_CMM.fm
Clicking the name of the CMM in the CMM Name column will show the managed resources in the selected chassis, as shown in Figure 4-40.
Clicking the IP address of the chassis in the Manage column (see Figure 4-39 on page 59) redirects you to another Chassis Management Modules web interface.
60
Configuring_CMM.fm
The CMM event log contains a list of all events that are received from all devices in the chassis, as shown in Figure 4-42. These events are also sent by the CMM to the IBM Flex System Manager, if one is installed.
Event actions
Event overview
You can see general information about the event, including severity, source, sequence, date, and event message, as shown in Figure 4-42. In addition, several options are available to manage logs. Export option allows you to export your event log in various formats (csv, XML, or pdf). Use the Delete Events option to delete all selected items, with the additional option of selecting audit, systems, or both. With the Settings option, you can add a log event when a log is 75% full. The Open Service Request option is enabled when you select one of the events from the table. To configure event recipient notifications in the CMM web interface, open the Events menu and click Event Recipients as shown in Figure 4-43.
61
Configuring_CMM.fm
Type recipient name and e-mail address, choose which events to receive, and click OK, as shown in Figure 4-45.
62
Configuring_CMM.fm
Choose the type and severity of the alerts to be sent, as shown in Figure 4-46.
63
Configuring_CMM.fm
Figure 4-48 shows the activated licensed features for I/O modules.
In the example above, two IOM features are activated on IBM Flex System EN4093 Fabric 10Gb Scalable Switch. Chassis License Keys Management tab shows the activated licenses on CMM itself, for example, IBM Fabric Manager, as shown in Figure 4-49.
For more information about Features on Demand, refer to the IBM Features on Demand web site at: https://www-304.ibm.com/systems/x/fod/index.wss
64
Configuring_CMM.fm
Figure 4-50 shows Features on Demand main http page. You need IBM ID to get the features that you want to activate.
65
Configuring_CMM.fm
Also you can see chassis temperature and cooling status by clicking the Temperature tab, as shown in Figure 4-53.
66
Configuring_CMM.fm
You can check fan and cooling status by selecting the Fans and Cooling menu item on Figure 4-54 on page 67.
Selecting the individual fan will show you events and power usage statistics associated with it, as shown in Figure 4-55.
67
Configuring_CMM.fm
Cooling zone status can also be checked from this page, as shown in Figure 4-56 on page 68.
You can choose power module policy that meets your specific needs by selecting Power Modules and Management menu item from the Chassis Management menu, as shown in Figure 4-57.
68
Configuring_CMM.fm
To monitor power allocation and power consumption history, select Input Power and Allocation tab, as shown in Figure 4-58 on page 69.
69
Configuring_CMM.fm
Component IP Configuration menu allows you to set the IP parameters on I/O modules and compute nodes, as shown in Figure 4-59.
70
Configuring_CMM.fm
Click the I/O module or compute node link to open its IP properties window, as shown in Figure 4-60.
71
Configuring_CMM.fm
Click Hardware Topology in the Chassis Management menu, where you can check all the components in the chassis and their hierarchy, as shown in Figure 4-61.
72
Configuring_CMM.fm
Click Reports in the Chassis Management menu, you can see hardware information in the chassis, as shown in Figure 4-62 on page 73.
73
Configuring_CMM.fm
Launch switch module remote console by clicking Launch IOM console, as shown in Figure 4-65.
Check or type the IP address of the managed I/O module, choose proper protocols and click Launch button, as shown in the Figure 4-66.
This brings selected I/O modules management user interface (UI), for example, web UI for the network switch, as shown in Figure 4-67.
74
Configuring_CMM.fm
Figure 4-68 Chassis Management Module login Chapter 4. Chassis Management Module operations
75
Configuring_CMM.fm
Figure 4-69 Command target hierarchic view Example 4-2 Command target usage
Use the -T system:mm[1] option to redirect a command to the CMM in bay 1. Use the -T system:switch[1] option to redirect a command to the I/O module in I/O bay 1.
Configuring_CMM.fm
This command displays a list of devices present within the command target. It can be used to determine the physical configuration of the IBM Flex System Enterprise Chassis, including how many CMMs are installed in the IBM Flex System Enterprise Chassis and which CMM is set as primary. To view all the components in the Chassis, run this command, as shown in Figure 4-70.
2. info command This command displays information about IBM Flex System components and their configuration. To view the information about a compute node in bay 6, issue the info command, as shown in Figure 4-71 on page 77.
77
Configuring_CMM.fm
78
Part 3_FSM.fm
Part 3
Part
79
Part 3_FSM.fm
80
Planning_FSM.fm
Chapter 5.
81
Planning_FSM.fm
82
Planning_FSM.fm
The yellow line in the Figure 5-1 on page 83 shows the production data network. The FSM also connects to the production network (Eth1) so that it can access the Internet for product updates and other related information.
One of the key functions that the data network supports is discovery of operating systems on the various network endpoints. Discovery of operating systems by the FSM is required to support software updates on an endpoint such as a compute node. Management and production data networks are usually separate subnets. In such a case, FSM management node uses both interfaces (Eth0 and Eth1). If data and management networks are combined into a single subnet, only Eth0 port must be configured with the IP address, and Eth1 must remain unconfigured.
Security policies
An IBM Flex System Manager management software security policy is a set of security-related characteristics that define a particular level of protection from security exposures. Depending on its level, the security policy might include account-related policies, communication-protocol enablement, and event-tracking levels.
83
Planning_FSM.fm
The management software enforces a chosen security policy only for the management node itself. The management software offers two types of security policy: 1. Legacy Security Policy 2. Secure Security Policy
Fulfillment Process
There are two way to activate Features on Demand. 1. FoD option ordered with server and installed in manufacturing
84
Planning_FSM.fm
IBM
Customer or Partner Key Mgmt System
Request key
Place order
Generate key
Fulfillment
Install key
1 Place order
Customer or Partner
IBM
Fulfillmen t Receive paper (and optional email) with autho rization code 2 Submit authorization Receive activation key 3 Install key
Request key
Generate key
85
Planning_FSM.fm
If you did not order management software Features on Demand when you ordered the IBM Flex System Manager Types 7955, 8731, and 8734 management node, you can purchase Features on Demand as you would any other software and hardware option. You can redeem Features on Demand for the management software at URL as below. http://www.ibm.com/systems/x/fod/
Table 5-1 FoD part numbers (United States, Canada, Asia Pacific, and Japan) Description Base feature set IBM Flex System Manager Per Managed Chassis with 1 Year SW S&S IBM Flex System Manager Per Managed Chassis with 3 Year SW S&S Advanced feature seta IBM Flex System Manager Advanced Upgrade Per Managed Chassis with 1 Year SW S&S IBM Flex System Manager Advanced Upgrade Per Managed Chassis with 3 Year SW S&S 90Y4249 00D7554 90Y4217 90Y4222 Part number
a. The Advanced Upgrade license requires the IBM Flex System Manager base license. Table 5-2 FoD part numbers (Latin America and Europe/Middle East/Africa) Description Base feature set IBM Flex System Manager Per Managed Chassis with 1 Year SW S&S IBM Flex System Manager Per Managed Chassis with 3 Year SW S&S Advanced feature seta IBM Flex System Manager Advanced Upgrade Per Managed Chassis with 1 Year SW S&S IBM Flex System Manager Advanced Upgrade Per Managed Chassis with 3 Year SW S&S 94Y9219 94Y9220 95Y1174 95Y1179 Part number
a. The Advanced Upgrade license requires the IBM Flex System Manager base license.
86
Planning_FSM.fm
Table 5-4 Part numbers for ordering Feature on Demand entitlement licenses for compute nodes Description IBM Flex System CN4054 Virtual Fabric Adapter (SW Upgrade) ServeRAID M5100 Series RAID 6 Upgrade for IBM Flex System ServeRAID M5100 Series SSD Caching Enabler for IBM Flex System IBM Virtual Fabric Advanced Software Upgrade (LOM) Part number 90Y3558 90Y4410 90Y4447 90Y9310
If you want to know how to manage Features on Demand, go to 6.12, Manage Feature-on-Demand keys on page 197.
87
Planning_FSM.fm
Agent tier Managed system type Compute nodes running Windows Compute nodes running Windows and supporting SSH or DCOM Compute nodes running VMware Other managed resources supporting SSH or SNMP
Table 5-6 summarizes the management tasks supported by the compute nodes depending on agent tier.
Table 5-6 Compute node management tasks supported by the agent tier Agent tier Managed system type Command Automation Hardware alerts Platform alerts Health and status monitoring File Transfer Inventory (hardware) Inventory (software) Problems (hardware status) Process Management Power Management Remote Control Remote Command Line Resource Monitors Update Manager Agentless in-band No No No No No No Yes No No No No Yes No No Agentless out-of-band No Yes No No No Yes No Yes No Yes Yes No No No Platform Agent No Yes Yes Yes No Yes Yes Yes No No No Yes Yes Yes Common Agent Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes
88
Planning_FSM.fm
Review your network device inventory in tables or a network topology view Monitor the health and status of network devices Manage devices by groups: Ethernet switches, Fibre Channel over Ethernet, or Subnet View network device configuration settings, and apply templates to configure devices, including Converged Enhanced Ethernet quality of service (QoS), VLANs, and Link Layer Discovery Protocol (LLDP) View systems according to VLAN and subnet Run network diagnostic tools like ping and traceroute Create Logical network profiles to quickly establish VLAN connectivity Simplified management of VM connections by configuring multiple characteristics of a network when virtual machines are part of a network system pool With management software VMControl, maintain network state (VLAN, ACLs) as a virtual machine is migrated (KVM) Management of virtual switches, including virtual Ethernet bridges Configuration of port profiles, a collection of network settings associated with a virtual system Automatic configuration of devices in network systems pools
Network Control
IBM Flex System Manager Network Control provides facilities to discover, inventory, and monitor network devices, launch vendor applications for configuration of network devices, and view groups of network devices. IBM Flex System Manager Network Control extends the network management functions of the IBM Flex System Manager product. Table 5-7 shows supported I/O switches and their management tasks.
Table 5-7 Supported I/O switches and management tasks I/O module Management task Discovery Inventory Monitoring Alerts Configuration EN2092 1 Gb Ethernet Yes Yes Yes Yes Yes EN4093 10 Gb Ethernet Yes Yes Yes Yes Yes FC3171 8 Gb FC Yes Yes Yes Yes Yes FC5022 16 Gb FC Yes Yes Yes Yes No
89
Planning_FSM.fm
IBM Flex System Enterprise Chassis and the management software offer many storage-management capabilities: Discovery of physical and virtual storage devices Support for virtual images on local storage across multiple chassis Inventory of physical storage configuration Health status and alerts Storage pool configuration Disk sparing and redundancy management Virtual volume management Support for virtual volume discovery, inventory, creation, modification, and deletion Table 5-8 shows supported storage systems and their management tasks.
Table 5-8 Supported storage systems and management tasks Storage system Management task Storage device discovery Integrated physical and logical topology views Show relationships between storage and server resources Perform logical and physical configuration View controller and volume status and to set notification alerts Yes Yes Yes Yes Yes V7000
Storage Control
With the Storage Control plug-in, you can manage an expanded set of storage subsystems and Fibre Channel switches. You can use Storage Control to discover and collect inventory, and monitor devices health. Depending on the firmware levels of these devices, Storage Control supports native interfaces to the device, which simplifies configuration setup and improves device management reliability. These interfaces use Secure Shell (ssh) credentials. For information about configuring these credentials see the Storage Control commands topic. After being discovered, these devices will be listed as being managed by Storage Manager in Flex System Manager. Storage Control uses IBM Tivoli Storage Productivity Center technology. As such, several of the device support and operating environment conditions are related to IBM Tivoli Storage Productivity Center.
90
Planning_FSM.fm
For more information see the following IBM Flex System Manager product publications, available from the IBM Flex System Information Center: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp
91
Planning_FSM.fm
IBM Fabric Manager (IFM) is pre-installed on the Flex System Manager (FSM). It is also licensed as part of the FSM chassis license. If the FSM is not purchased, the stand-alone IFM application can be licensed and installed in the environment to use against the Flex systems. IFM can be launched from the FSM Home Applications tab as shown in Figure 5-5.
Detailed information on using IFM can be found in the IBM PureFlex System InfoCenter: http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.iof m.doc/dw1li_product_page.html
5.2 Planning for managing the virtualization environment with Flex System Manager
This section describes when you are to set up some certain virtual infrastructures with IBM Flex System or IBM PureFlex System through Flex System Manager.
92
Planning_FSM.fm
policies. IBM VMControl is the single point of control for managing virtualized resources in one or more IBM Flex System Enterprise Chassis. VMControl virtualization capabilities can help you simplify the management of virtual resources (server, storage, network, virtual appliance images) and pools of virtual resources. This simplification is achieved through the integrated provisioning of server, storage, and network resources when new workloads are deployed to the systems and system pools. VMControl enables you to complete the following tasks: Discover existing image repositories in your environment and import external, standards-based images into your repositories as virtual appliances. Capture a running virtual server that is configured just the way you want, complete with guest operating system, running applications, and virtual server definition. When you capture the virtual server, a virtual appliance is created in one of your image repositories with the same definitions and can be deployed multiple times in your environment. Import virtual appliance packages that are in Open Virtualization Format (OVF) from the Internet or other external sources. After the virtual appliance packages are imported, you can deploy them in your data center. Deploy virtual appliances quickly to create new virtual servers that meet the demands of your changing business needs. Create, capture, and manage workloads. Create server system pools, which enable you to consolidate your resources and workloads into distinct and manageable groups. Deploy virtual appliances into server system pools. Manage server system pools, including adding hosts or additional storage space and monitoring the health of the resources and the status of the workloads in them. Group storage systems together, using storage system pools to increase resource utilization and automation. Manage storage system pools by adding storage, editing the storage system pool policy, and monitoring the health of the storage resources. There are three editions of VMControl: VMControl Express Edition enables you to manage virtual machines VMControl Standard Edition adds the ability to manage complete libraries of virtual images VMControl Enterprise Edition creates and enables the management of system pools dynamic collections of computing resources used to support multiple virtual images running concurrently When you activate VMControl through the IBM Flex System Manager management software, a 90-day trial of VMControl Standard and Enterprise Editions begins. After the trial period ends, VMControl Express Edition remains, but VMControl Standard and Enterprise Edition are disabled. VMControl Standard and Enterprise Editions are available as an optional Features on Demand (Advanced Upgrade) in the IBM Flex System Manager management software. VMControl discovery and inventory of virtual resources is supported for these hypervisor platforms: KVM RHEL 6.x VMware vCenter and VMware ESX
Chapter 5. Planning for IBM Flex System Manager-based systems management
93
Planning_FSM.fm
Microsoft Hyper-V Server PowerVM The following table shows supported virtualization environments and their management tasks on Table 5-9 on page 94.
Table 5-9 Supported virtualization environments and management tasks Virtualization environment Management task Deploys virtual servers Deploys virtual farms Relocates virtual servers Imports virtual appliance packages Captures virtual servers Captures workloads Deploys virtual appliances Deploys workloads Deploys server system pools Deploys storage system pools AIX and Linuxa Yes No Yes Yes Yes Yes Yes Yes Yes Yes IBM i VMware ESX Yes Yes Yes No No No No No No No Microsoft Hyper-V Yes No No No No No No No No No Linux KVM
94
Planning_FSM.fm
At least one NFS export on the NFS server is defined: For image and disk inventory to work, the export path must end with /images. example: /share/kvm/images If you are not setting up additional security in your environment, you must use the no_root_squash export option. example: cat /etc/exports as shown Figure 5-7
If you cannot change your NFS export setup, to have image files inventoried from an export path ending in something other than /images, complete the following steps: 1. In the file, /opt/ibm/director/lwi/conf/overrides/USMIKernel.properties, add a line for the following property: director.services.extendeddiscovery.nfs.suffix example: director.services.extendeddiscovery.nfs.suffix=/img-kvm This addition results in inventorying the image files within NFS export paths that end in /img-kvm instead of the default, /images.
95
Planning_FSM.fm
2. Restart the IBM Flex System Manager after adding or changing the USMIKernel.properties file. Note: For consistency, name image and disk files that are stored on NFS with a .dsk, .img, or .raw extension. Ensure that the NFS services are started. For example, by running the command: service nfs start as shown Figure 5-8
KVM Platform Agent is downloaded and installed please refer to chapter. 8.2, KVM platform agent installation on page 292 The NFS server is discovered, accessed, and inventoried by IBM Flex System Manager. The image repository is set up as explained 8.3, Image repository for KVM on page 298: IBM Flex System Manager Common Agent is installed as explained 8.3, Image repository for KVM on page 298." VMControl Common Repository subagent is installed as explained 8.3, Image repository for KVM on page 298 The shared NFS exported storage is mounted on the Image Repository server as show Figure 5-9.
96
Planning_FSM.fm
The image repository server is discovered and inventory is collected as shown Figure 5-10 For more detail please refer chapter 8.3, Image repository for KVM on page 298.
The image repository is created from VMControl. For instructions to create an image repository, as shown chapter 8.3, Image repository for KVM on page 298 One or more RHEL KVM hosts are set up and available: KVM Platform Agent is downloaded and installed on the KVM hosts. see chapter 8.2, KVM platform agent installation on page 292 KVM hosts are discovered, accessed, and inventoried from your IBM Flex System Manager. see chapter 8.4, Create SAN Storage system pools on page 318 Storage is set up. To set up storage, right-click a KVM host, select Edit Host as shown in Figure 5-11, and click Storage Pools as shown in Figure 5-12.
97
Planning_FSM.fm
Select the pool to create you virtual server disk as shown in Figure 5-12.
Note: The action above configure a shared NFS storage pool for the NFS server export that you created, then click OK to create the storage pools.
Note: When configuring KVM hosts, specify the fully qualified name as the host name, for example, hostname.company.com. Use the hostname command on the host to determine the system name. If the host is not configured with its fully qualified host name, the IBM Key Exchange providers might fail to exchange SSH keys during relocation. Also, ensure that the host name and IP address for the target system are recorded correctly in the DNS records.
98
Planning_FSM.fm
Requirements for implementing SAN storage based model are as follows: IBM Flex System Manager VMControl is activated. The Fibre Channel storage network is correctly cabled and configured with the appropriate Fibre Channel switches. KVM virtualization with VMControl only supports SAN storage over Fibre Channel. Typically, one of the fabric switches is configured with the zoning information. Additionally, VMControl requires that the Fibre Channel network has hard zoning enabled. One or more RHEL KVM hosts are set up and available: Ensure that the RHEL KVM host is connected to the Fibre Channel network with a supported adapter. The KVM Platform Agent is downloaded and installed. KVM hosts are discovered, accessed, and inventoried from your IBM Flex System Manager. The SAN storage controllers (also called storage subsystems) are configured and storage pools are set up with the desired storage space and RAID levels for virtual disk images. Neither VMControl nor Storage Control will provision these RAID storage pools for you.
99
Planning_FSM.fm
Note: Host definitions must include all World Wide Port Names (WWPNs) for the host (or hosts, as described above) they represent, even if some ports are not physically connected or active. This avoids the potential problem of mapping a single volume under different LUN IDs to the same host. For example, assume a KVM host has a Fibre Channel card with host ports WWPN1 and WWPN2. An IBM Storwize V7000 storage subsystem defines host definition KVM_Host1 for that host. Then the host definition must contain both WWPN1 and WWPN2. A Fibre Channel switch provider is configured in the environment in case where Brocade switches are used. This role can be handled by the Brocade SMI-S Agent or the Brocade Network Advisor. Storage subsystems, storage pools, and the Fibre Channel switch fabric are discovered and inventoried by Flex System Manager for shared access from endpoints in the KVM environment. These endpoints include KVM hosts and image repository servers as shown in Figure 5-13 on page 99. Encryption keys are needed for the IBM Storwize V7000. The encryption keys are used for discovery enablement and to enable IBM FlashCopy. If necessary, generate an encryption key file in OpenSSH format for your SAN device and store this file on your Flex System Manager server. For instructions to generate an encryption key file for your storage, refer to your SAN storage devices documentation. Use the manage7000 command to define your storage data source. This push your pub key and enables SAN storage discovery and inventory collection through Storage Control. Please refer chapter 6.13, Discover and manage V7000 (Storage Control) on page 205 Note: If you have many switches, zones, or zone groups defined on a fabric switch, the inventory collection task might show an error after the default Flex System Manager timeout period expires. However, zone inventory collection continues to run in the background. The image repository is set up and meets all of the following requirements. The image repository is used for storing and deploying virtual appliances. The image repository server is connected to the Fibre Channel network with a supported Fibre Channel HBA. For more information about adapters, please refer to http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.s dnm.adv.helps.doc/fnc0_r_network_ctrl_planning.html Common Agent is installed on your image repository server. For instructions, please refer 8.3, Image repository for KVM on page 298 VMControl Common Repository subagent is installed on the image repository server. For instructions, see 8.2, KVM platform agent installation on page 292. The image repository server is discovered and inventory is collected on it. The image repository is created from VMControl. For instructions to create an image repository please refer chapter 8.3, Image repository for KVM on page 298. Verify that Flex System Manager and VMControl can manage the environment. Run dumpstcfg to see the storage configuration information. Example output: Host Accessible Containers -------------------------100
Implementing Systems Management of IBM PureFlex System
Planning_FSM.fm
NAME: STORAGE SUBSYSTEM/POOL IBM Host01: Storwize V7000-2076/RAID5_Pool_KVM Storwize V7000-2076/RAID0_Pool_800GB IBM Host01 is a KVM host, Storwize V7000-2076 is the storage subsystem, and the KVM host can access both RAID5_Pool_KVM and RAID0_Pool_800GB storage pools. This indicates that inventory collection has correctly modeled connectivity from the host to the storage. Additionally, verify that the image repository server can access the SAN storage containers in the same way. Run testluncreate to verify that the SAN storage configuration is complete. The command tries to allocate a volume on a subsystem and storage pool then attach it to a host. This host could be your image repository server. If dumpstcfg or testluncreate shows problems, there might be a configuration problem. Correct the problem and collect inventory again on each endpoint, farm, storage, and switch resources.
Supported networks
VMControl supports the following network configurations for the KVM hypervisor: Virtual Ethernet Bridging (VEB) Virtual Ethernet Port Aggregator (VEPA) network (Requires IBM Flex System Manager Network Control and that the host is in a network system pool) Limited support for KVM hypervisor networks Note: Use paravirtualized (virtio) drivers for enhanced performance. Use Virtio and e1000 model configurations for virtual network server adapters.
Supported storage
Image repository and virtual disk storage options include the following: NFS version 3 server running on RHEL version 6.2. Supported SAN devices. Please refer for storage products support http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.sdnm.adv.h elps.doc/fnc0_r_network_ctrl_planning.htm
Supported tasks
In the KVM virtualization environment, you can perform these tasks: Create and delete NFS storage pools on a host Create and delete NFS or SAN virtual disks Suspend or resume virtual servers and workloads (without release of resources) Create, edit, and delete virtual servers Power operations for virtual servers Relocate virtual servers
101
Planning_FSM.fm
Turn maintenance mode on and off for hosts that are in server system pools Import a virtual appliance package containing one or more raw disk images Capture a workload or virtual server into a virtual appliance Deploy a virtual appliance package to a new virtual server with hardware and product customizations Deploy a virtual appliance package to an existing virtual server with adequate resources Start, stop, and edit a workload Create, edit, and delete server system pools Create, edit, and delete network system pools (If you are using IBM Flex System Manager Network Control with VMControl) Adjust the virtualization monitor polling interval for KVM using the KvmPlatformPollingInterval parameter
Note: To enable remote control access on you KVM, please follow the instructions in the URL: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2 Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_t_access_kvm_remotely.html
KVM requirements
In addition to the packages required by the KVM platform agent, the genisoimage.x86_64 package must also be installed for VMControl support. Please refer 8.2, KVM platform agent installation on page 292 Note: These packages might be available from your installation software. The following commands open required ports in the IPv4 firewall on the KVM host: iptables -A INPUT -p tcp --dport 427 -j ACCEPT iptables -A INPUT -p udp --dport 427 -j ACCEPT iptables -A INPUT -p tcp --dport 22 -j ACCEPT iptables -A INPUT -p tcp --dport 15988 -j ACCEPT iptables -A INPUT -p tcp --dport 15989 -j ACCEPT service iptables save Notes: The SSH service must be configured and running on the KVM host so that an SSH remote service access point for port 22 gets created for each host in addition to the CIM RSAP on ports 15988 and 15989. When a SAN storage solution is being used, there is a requirement to have at least several Megabytes of free file system space under /var/opt/ibm and /var/lib/libvirt on the KVM host. The user employed to request access to the host from ISD must have authority to write to these directories.
102
Planning_FSM.fm
Restrictions
Please refer restrictions section in the link bellow: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fco m.ibm.director.vim.helps.doc%2Ffsd0_vim_r_kvm.html
There are following requirements for implementation of PowerVM-based virtualization environment: IBM Flex System Manager is installed on a supported server. IBM Flex System Manager VMControl Standard Edition or IBM Flex System Manager VMControl Enterprise Edition is activated.
103
Planning_FSM.fm
At least one NIM master is available. IBM Flex System Manager Common Agent and the VMControl NIM subagent are installed on the NIM master. IBM Flex System Manager recognizes this NIM master as a VMControl image repository. The /export/nim filesystem in which the virtual appliances are stored must not be NFS mounted to the NIM master. The NIM master exports this filesystem itself, and NFS does not support export of a mounted filesystem. Note: The image repository is shown as a stand-alone server in the diagram. However the image repository can also be on the same Power Systems server that hosts the AIX virtual servers that you can capture from and deploy to using VMControl. At least one IBM Power 7 compute node exists to host virtual servers that you can capture from and deploy to using VMControl. The IBM Power server is typically attached to a SAN as shown in the diagram, and the SAN is used for the virtual disks of the virtual servers hosted by the IBM Power server. If you expect to use VMControl Enterprise Edition server system pools or expect to be able to do virtual server relocation on your own, then a SAN is required. If not, then disks local to the IBM Power server and virtualized by the Virtual I/O Server (VIOS) can be used as an alternative. Though not shown in the diagram, multiple VIOS virtual servers and multi-path I/O (MPIO) are supported.
Supported storage
The following storage systems are supported: IBM Storwize V7000
Supported tasks
In this environment, you can perform these tasks: Create, edit, and delete virtual servers Relocate virtual servers
104
Planning_FSM.fm
Import a virtual appliance package containing an AIX mksysb image Capture an AIX workload or virtual server, an AIX mksysb image file or NIM resource, or an IX lpp_source directory or NIM resource Deploy an AIX mksysb or lpp_source virtual appliance Group virtual servers to create a workload Start, stop, and edit a workload Create, edit, and delete system pools
Requirements for AIX, IBM i, and Linux using storage copy services
This topic describes the requirements and support for AIX, IBM i, and Linux virtual appliances, virtual servers, and workloads in a Power Systems virtualization environment that relies on storage copy services (SCS). Figure 5-15 shows an example Power Systems virtualization environment for AIX, IBM i, and Linux virtual appliances, virtual servers, and workloads that rely on SCS.
Figure 5-15 AIX, IBM i, and Linux using storage copy services system diagram
There are following requirements: IBM Flex System Manager is installed on a supported server. IBM Flex System Manager VMControl Standard Edition or IBM Flex System Manager VMControl Enterprise Edition is activated. A Virtual I/O Server (VIOS) virtual server exists on an IBM Power server to host the image repository used to store the raw disk images associated with your AIX, IBM i, and Linux virtual appliances.
105
Planning_FSM.fm
Note: You can have multiple repositories. However, for repositories that are on separate IBM Power servers, the image repository virtual servers must have access through a VIOS to the same shared SAN as the AIX, IBM i, and Linux virtual servers that they will capture and deploy. The IBM Flex System Manager Common Agent and VMControl Common Repository subagent are installed on the VIOS that you want to use as an image repository. At least one IBM Power 7 compute node exists to host virtual servers that you can capture from and deploy to using VMControl. Note: If manual or automated virtual server relocation capabilities are needed, multiple IBM Power 6 or 7 servers are required. All AIX, IBM i, and Linux virtual servers to be captured from or deployed to using VMControl have their storage allocated from the SAN and provided through one or more VIOS virtual servers. These virtual servers must use virtual Ethernet connections provided through one or more VIOS virtual servers. These virtual servers must not have any physical devices allocated from the IBM Power server. For Virtual I/O Server Version 2.2, any virtual servers that you capture and any virtual appliances you deploy use the same storage pool as the image repository in which you store the virtual appliances.
Supported tasks
In a Power Systems virtualization environment for AIX, IBM i, and Linux that relies on SCS, you can perform the following tasks: Create, edit, and delete virtual servers Import virtual appliance packages containing an AIX, IBM i, or Linux raw disk image Capture an AIX, IBM i, or Linux workload or virtual server (logical partition) Deploy an AIX, IBM i, or Linux raw disk image virtual appliance Group virtual servers to create a workload Start, stop, and edit a workload
106
Planning_FSM.fm
In a Power Systems virtualization environment for AIX and Linux that relies on SCS, you can perform the following additional tasks: Relocate virtual servers Create, edit, and delete system pools
There are following requirements for the scenario described above: IBM Flex System Manager is installed on a supported server. IBM Flex System Manager VMControl is activated. Note: To launch the VMware Infrastructure Client or the VMware vSphere Client from IBM Flex System Manager VMControl, the client must be installed on the IBM Flex System Manager system and on any system that you use to log in to the IBM Flex System Manager Web interface. VMware vCenter is installed on an x86-compatible system.
107
Planning_FSM.fm
Note: IBM Flex System Manager and VMControl require that the Operating System (OS) that VMware vCenter is running on is an x86-compatible system with a Microsoft Windows-based OS. VMware ESX exists to host virtual servers that you can manage using VMControl. Note: VMware ESX is managed by VMware vCenter. VMware ESXi exists to host virtual servers that you can manage using VMControl. Note: VMware ESXi is managed by VMware vCenter. VMware vCenter system is discovered and request access task has completed. After the request access task completes, the Configure Access task shows the vCenter protocol in OK state.
Note: If you installed VMware vCenter with a non-default port number, you must create a VMware vCenter Server Discovery profile using the Discovery Profile wizard. Specify the unique port number in the profile that you create. Then, use the profile to discover the VMware vCenter system. For more information, see "Managing discovery profiles" here: http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.dire ctor.discovery.helps.doc/fqm0_t_managing_discovery_profiles.html
Supported versions VMControl supports the following virtualization software: VMware vCenter 4.x (capable of managing the following supported hosts) VMware ESX 4.x and VMware ESXi 4.x VMware vCenter 5.x (capable of managing the following supported hosts) VMware ESX 4.x, VMware ESXi 4.x, and VMware ESXi 5 VMware ESX 4.x stand-alone Supported tasks In the VMware vCenter virtualization environment, you can perform the following tasks: Create, edit, and delete virtual servers Create a DataCenter or Cluster using the Create Virtual Farm wizard Add a host to a DataCenter or Cluster using the Add host to farm function Remove a host from a DataCenter or Cluster using the Remove host from farm function Relocate virtual servers Put a host into maintenance mode Remove a host from maintenance mode
108
Planning_FSM.fm
There are following requirements for the scenario described above: IBM Flex System Manager is installed on a supported server. IBM Flex System Manager VMControl is installed on the IBM Flex System Manager. VMware ESX exists to host virtual servers that you can manage using VMControl. IBM Flex System Manager Common Agent and the VMware ESX subagent are installed on the VMware ESX system. If you are using IBM Flex System Manager Network Control network system pools with VMware to provision new network configurations and to provide automated network relocation, SNMP must be enabled on all the VMware hosts to be included in the network system pool. To enable SNMP, log on as root and from the command line issue: service snmpd start Supported versions VMControl supports the following virtualization software: VMware ESX 4.x stand-alone Supported tasks In a VMware ESX virtualization environment, you can perform the following tasks: Create, edit, and delete virtual servers Create, edit, and delete virtual farms Relocate virtual servers
109
Planning_FSM.fm
There are following requirements for the scenario described above: IBM Flex System Manager available in your PureFlex chassis. IBM Flex System Manager VMControl is activated.
110
Planning_FSM.fm
Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled is installed on an x86-compatible system as show Figure 5-19.
IBM Flex System Manager Common Agent or Platform Agent is installed on the host. Please refer to 11.1.1, Install agent on an Hyper-V node on page 496
Supported versions
VMControl supports Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2 virtualization software. For information about the latest fixes for required software, see https://www.ibm.com/developerworks/wikis/display/WikiPtype/Minimum+Fix+Levels+for+VM Control+2.4.1+Dependencies
Supported tasks
In this environment, you can create, edit, and delete virtual servers then start, stop, restart and suspend your virtual servers.
111
Planning_FSM.fm
112
Configuring_FSM.fm
Chapter 6.
113
Configuring_FSM.fm
114
Configuring_FSM.fm
To monitor the FSM startup process, connect a console using one of these methods prior to powering up the FSM node. The steps that follow use the IMMv2 remote console method. To initiate an IMMv2 remote console session: 1. Start a browser session as shown in Figure 6-1 to the IP address of the FSM IMMv2. Note: The IP address of the IMMv2 of Intel compute nodes can be determined from the Chassis Management Module or CLI. By default, the interface is set to use DHCP, but can be changed to a static address using the CMM, a CLI, or a console connected directly to the VGA port on the front of the FSM (accessible with the use of the console breakout cable).
115
Configuring_FSM.fm
2. After logging into the IMMv2, select Server Management from the navigation options, as shown in Figure 6-2 on page 116.
116
Configuring_FSM.fm
3. In the Remote Control window, click the Start remote control in single-user mode button, as shown in Figure 6-3 on page 117. This starts a Java applet on the local desktop which will be a console session to the FSM.
Figure 6-4 shows the Java console window opened to the FSM appliance prior to power being applied.
117
Configuring_FSM.fm
4. The FSM can be powered on from several locations, including the physical power button on the FSM, or from the Chassis Management Module. For this example, using the Tools/Power/On option from the remote console menu, as shown in Figure 6-5, is the most convenient.
Figure 6-5 Powering on the FSM from the remote console session
As the FSM powers up and boots, the process can be monitored, but no input is accepted until the License Agreement window, shown in Figure 6-6, displays.
118
Configuring_FSM.fm
5. Click the I agree button to continue, and the startup wizard Welcome window displays, shown in Figure 6-7 on page 119.
6. Click Data and Time from the wizard menu to display the window shown in Figure 6-8. Set the time, date, time zone, and Network Time Protocol server, as needed.
119
Configuring_FSM.fm
8. Create a user ID and password for accessing the GUI and CLI. User ID and password maintenance, including creating additional user IDs, is available in IBM Flex System Manager after the startup wizard completes. Figure 6-9 shows the creation of user ID USERID and entering a password.
9. Click the Next button to continue. Network topology options include separate networks for management and data, or a single network for both data and management traffic from the chassis. Best practices is to have separate management and data networks. To simplify this example, a combined network is configured, using the topology on the right side of Figure 6-10 on page 120.
120
Configuring_FSM.fm
10.Click the Next button to continue to the actual network configuration. LAN adapter configuration is shown as the next step in Figure 6-11 on page 121. There are two adapters listed. The first adapter is from the FSM management network that allows FSM to communicate on the chassis management network. Traffic from this adapter flows through the Chassis Management Module and uses the CMM physical connection to the network. The second LAN adapter represents one of the integrated Ethernet ports or LAN on motherboard (LOM). Traffic from this adapter flows through the Ethernet switch in the first I/O switch bay of the chassis, and is typically be used as a separate data connection to the FSM. Notice that the radio button for the first adapter is preselected. See Figure 6-11 on page 121.
11.Click Next to continue. 12.The Configure IP Address window, shown in Figure 6-12, allows the selection of DHCP or static IP options for IPv4 and IPv6 addressing. Select the desired options, enter the information as required, then click Next.
121
Configuring_FSM.fm
After completing the previous step, the wizard cycles back to the Initial LAN Adapter window and preselects the next adapter in the list, as shown in Figure 6-13.
In our example, we are using a combined network topology and a single adapter, so additional IP addresses are not needed. 13.Select the No radio button by the question, Do you want to configure another LAN adapter? as shown in figure Figure 6-13. 14.Click the Next button to continue. After IP address assignment, the host name and gateway are configured as shown in Figure 6-14 on page 122. Enter the desired host name, domain name, and default gateway address. Note the IP address and the default gateway adapter in the pull-down areas and ensure the values are as desired. Click the Next button to continue. Note: It is expected that the host name of the FSM is available on the domain name server.
The next step has the option to enable the use of a DNS services and to add the address of one or severs and a domain suffix search order.
122
Configuring_FSM.fm
15.Enter the desired information as show in Figure 6-15 and click the Next button to continue.
The final step of the setup wizard is shown in Figure 6-16 on page 123. This is a summary window of all configured options. 16.To change a selection, use the Back button. If no changes are needed click the Finish button.
123
Configuring_FSM.fm
After the Finish button is clicked, the final configuration and setup proceeds automatically without the need of further input. See Figure 6-17 on page 124 through Figure 6-20 on page 125.
124
Configuring_FSM.fm
With startup completed, the local browser on the FSM also starts. A list of untrusted connection challenges displays. 17.Accept these challenges by clicking the I Understand the Risks twisty and the Add Exception button as shown in Figure 6-21 and Figure 6-22 on page 126.
125
Configuring_FSM.fm
126
Configuring_FSM.fm
With the security exceptions cleared, the Login window of the IBM Flex System Manager GUI displays.
127
Configuring_FSM.fm
19.Enter the user ID and credentials that were entered in the startup wizard, and click the Log in button shown in Figure 6-24.
A Getting Started pop-up reminds you that initial setup tasks must be completed. See Figure 6-25 on page 128.
128
Configuring_FSM.fm
The startup wizard and initial login are complete. The FSM is ready for further configuration and use. Our example uses a console from the remote console function of the IMMv2. At this time, a secure browser session can be started to the FSM.
Step 1 is to Check for Updates on the FSM itself. When choosing this option, the FSM will attempt to contact the IBM Fix Central site to pull down updates. If a connection to the internet is not available, a message will appear asking for a local directory on the FSM to import updates from. The updates can be downloaded manually from the IBM Fix Central website and then manually copied to the FSM as discussed in Section 6.4, Acquire updates for chassis components on page 132. FSM updates will include both software and hardware
129
Configuring_FSM.fm
stack updates. So in the event that firmware is updated through an FSM update, the FSM may need to be rebooted. After an update is complete, the message as shown in Figure 6-27 on page 130 will be seen in the Initial Setup screen.
130
Configuring_FSM.fm
4. Click the box in front of the desired chassis to set a check mark. 5. Click the Manage button. The Manage Chassis window opens. The Manage Chassis window, shown in Figure 6-30, lists the selected chassis. A drop-down box lists the available IBM Flex System Manager systems.
6. Ensure the chassis and IBM Flex System Manager selections are correct. 7. Click the Manage button. This updates the Message column from Waiting to Finalizing, then Managed. Figure 6-31 and Figure 6-32 show these steps.
131
Configuring_FSM.fm
8. After the successful completion of the manage chassis process, click the Show all chassis button as shown in Figure 6-33.
The result displays the original IBM Flex System Manager Management Domain window, with the target chassis as the managing IBM Flex System Manager. See Figure 6-34.
The Enterprise Chassis is now managed by the IBM Flex System Manager.
Configuring_FSM.fm
copied to the FSM, they must be imported into the Update Manager. First, we need to set up the Internet connection.
133
Configuring_FSM.fm
2. From the list of managers, click Update Manager to display the window shown in Figure 6-36 on page 134.
134
Configuring_FSM.fm
3. In the Common task box, click the link for Configure settings to open the window shown in Figure 6-37 on page 135. This window allows for the configuration of a direct Internet connection, or the configuration settings to use an existing proxy server.
135
Configuring_FSM.fm
4. With the settings complete, click the Test Internet Connection button to verify the connection. The test attempts to make a connection to a target IBM server. During the test, a progress indicator displays, as shown in Figure 6-38.
136
Configuring_FSM.fm
With the test successful, the Update Manager can obtain update packages directly from IBM. If a direct Internet connection is not allowed for the FSM, the following steps show how to import updates files into Update Manager.
137
Configuring_FSM.fm
The steps that follow describe how to import the update files using the GUI: 1. Beginning at the Update Manager window, click the Acquire updates link, as shown in Figure 6-40.
138
Configuring_FSM.fm
Figure 6-41 on page 139 shows the window opened by the Acquire updates link. Two options are available: check for updates using an Internet connection, or import updates from the file system. For this example, we will import the updates.
2. Click the radio button for Import updates. When the selection is made to import updates from the file system, additional options apply.
139
Configuring_FSM.fm
3. Enter the path for the updates that were manually copied to the IBM Flex System Manager, as shown in Figure 6-42.
4. Click the OK button, and the IBM Flex System Manager job scheduler displays, as shown in Figure 6-43 on page 140.
For this example, the default Run Now radio button option is checked.
140
Configuring_FSM.fm
5. Click the OK button at the bottom of the window to start the job. When the import updates job starts, the Acquire Updates window refreshes with a message indicating the new job. Status of the running job can be monitored by clicking the Display Properties button as shown in Figure 6-44 on page 141.
141
Configuring_FSM.fm
142
Configuring_FSM.fm
Select LAN adapter Eth1 which is the adapter connected to the switch in bay 1 and 2 for external access to data network as shown Figure 6-48.
Select IPv4 and static configuration, enter Eth1 IP address and the netmask (unselect IPV6 if not configured), as shown in Figure 6-49, then click Next.
143
Configuring_FSM.fm
Select the IP address desired to configure eth1, then specify the gateway. Please ensure that the Eth1 is selected as shown in Figure 6-51.
In the step above by selecting Eth1 the gateway is assigned to Eth1 interface.
144
Configuring_FSM.fm
Enter the IP address of your DNS server, then click Next, as shown in Figure 6-53.
145
Configuring_FSM.fm
You can select to schedule this job or run it now. We selected Run Now as shown in Figure 6-55.
146
Configuring_FSM.fm
During job running, you can click Display Properties to check the job status, as shown in Figure 6-56.
Note: When the job is completed, the network of the FSM appliance is restarted and you will lose your connection for a couple of seconds. Reload the FSM page and click Continue to accept the websites certificate as shown in Figure 6-57.
147
Configuring_FSM.fm
At the home page, you remark a warning symbol as shown in Figure 6-59 on the Administration tab, please select the Administration tab.
148
Configuring_FSM.fm
You get a message which explain that recent changes require a reboot as shown Figure 6-60. Select Restart IBM Flex System Manager Server. .
149
Configuring_FSM.fm
Click Run Now as shown in Figure 6-62 or schedule the FSM restart during a maintenance time frame.
An information message appears to specify that the job has been created and started as shown Figure 6-63. You can click Display Properties to check the job status.
The FSM is restarted and you temporarily loose your connection to the FSM. After FSM sever is restarted, the ethernet interface Eth1 is fully configured.
150
Configuring_FSM.fm
CMM. This compared any newer CMM firmware with the currently installed CMM firmware. If a newer firmware is found, a message will appear on the Initial Setup screen as shown in Figure 6-64.
Click uninstalled updates link and a list of newer available firmware will be shown that can be deployed to the CMM, as shown in Figure 6-65 on page 151.
Select the update, choose the Install button and an installation wizard will open.
151
Configuring_FSM.fm
After clicking Next through the initial Welcome screen, the Restarts section will show if any restart of the device is required or not, as shown in the Figure 6-66.
152
Configuring_FSM.fm
After choosing Next, the Summary screen will appear as shown in Figure 6-67 on page 153.
153
Configuring_FSM.fm
After choosing Finish, the choice of Run Now or Schedule will appear as shown in Figure 6-68.
The update will be deployed out to the CMM, the CMM will be restarted as part of the job. Once the CMM is back up and reachable, inventory will be run against it, then a compliance check to compare the newly installed firmware against the FSM update repository. This will ensure that the firmware is up to date and the CMM will show up with a compliant version.
Discovery
Discovery is the process by which IBM Flex System Manager identifies and establishes connections with network-level resources that IBM Flex System Manager can manage, such as compute nodes, switches, or external storage devices. Use system discovery to identify 154
Implementing Systems Management of IBM PureFlex System
Configuring_FSM.fm
resources within your environment, collect data about those resources, and establish connections with them.
Discovery protocols
A discovery protocol is any network communication protocol that IBM Flex System Manager uses during the discovery process to discover a resource. The default getting started discovery profile uses a predetermined list of protocols. When you specify a single IP address, a single host name, or a single range of IP addresses, system discovery uses one or more protocols based on the selected target resource type. Using a discovery profile enables you to refine the target resource type and configure specific protocols that you want to use. The communication protocols that IBM Flex System Manager uses during discovery depend on the protocols used by the target resource type. You need to decide about the different protocols only when you create or edit a discovery profile. The Discovery Profile wizard helps you select and configure the correct protocol for the type of resource that you want to discover. When discovering a large number of resources, network traffic associated with the discovery process might cause timeouts that result in some discoverable resources remaining undiscovered. To help prevent this problem, use one or more discovery profiles. Using a discovery profile enables you to target specific resources and limit the number of communication protocols used during discovery. Limiting the number of communication protocols used when discovering a large number of resources helps avoid problems caused by network traffic collisions and timeouts. By default, IBM Flex System Manager supports the following discovery protocols: Agent manager discovery Agent manager discovery specifically targets the discovery of Tivoli common agents. In the Tivoli paradigm, Service Location Protocol (SLP) is not supported and management nodes contact an agent manager that knows about the agents in their environment. You can select the agent managers that you want to use in discovery. Common Agent Services (CAS) discovery CAS discovery utilizes Service Location Protocol (SLP) discovery, with which clients can locate servers and other services on the network. Common Information Model (CIM) discovery CIM discovery utilizes the Service Location Protocol (SLP) for discovery. With CIM discovery, clients can locate servers and other services on the network. Interprocess communication (IPC) discovery IPC is the process by which programs send messages to each other. Sockets, semaphores, signals, and internal message queues are common methods of interprocess
Chapter 6. IBM Flex System Manager initial configuration
155
Configuring_FSM.fm
communication. IPC is also a mechanism of an operating system that enables processes to communicate with each other within the same computer or over a network. IPC leverages services that IBM Flex System Manager provides that components use to communicate with each other. By using these services, a server task can communicate with an agent task running on a target. Secure shell (ssh) discovery Secure shell is a Unix-based command interface and protocol for securely accessing a remote computer. With ssh discovery, you can specify either a single IP address or a range of IP addresses upon which to run discovery. Simple Network Management Protocol (SNMP) discovery SNMP is a network management standard widely used in TCP/IP networks. SNMP performs management services by using a distributed architecture of management systems and agents. SNMP provides a method of managing network hosts such as workstation or server computers, routers, bridges, and hubs from a centrally-located computer running network-management software. Storage Management Initiative Specification (SMI-S) discovery With SMI-S discovery, clients can locate servers and other services on the network. It is a design specification developed by the Storage Networking Industry Association (SNIA) that specifies a secure and reliable interface with which storage management systems (SMSs) can identify, classify, monitor, and control physical and logical resources in a storage area network (SAN). The interface integrates the various devices to be managed in a storage area network (SAN) and the tools used to manage them. Windows Distributed component object model (DCOM) discovery Use Windows DCOM (an extension of the Microsoft Component Object Model (COM) to support objects distributed across a network) configuration to specify either a single IP address or a range of IP addresses upon which to run discovery.
156
Configuring_FSM.fm
157
Configuring_FSM.fm
In our example, we will run a discovery on an IP range, therefore, select Range IPv4 address, as shown in Figure 6-70.
Note: You can also choose to schedule your discovery if required. Fill in your IP address range as shown in Figure 6-71.
.
158
Configuring_FSM.fm
A blue information square appears to say that the job is started as shown Figure 6-72. Click Display Properties to check the job status.
Wait till the progress bar has reached 100% meaning that the discovery is completed as shown in Figure 6-73.
Note: Please do not forget to grant the access for the object on which you want to collect inventory as described in the example bellow.
159
Configuring_FSM.fm
If granting access to your object is required, this will be indicated by displaying No access in the Access field, as shown in Figure 6-74.
After requesting access to the object, to ensure that you access is granted, click General tab, as shown in Figure 6-75.
160
Configuring_FSM.fm
Go back to the Resource Explorer tab and select Action Inventory View and Collect Inventory as shown in Figure 6-76, then click Run Now.
Your object is selected as Target systems. To begin inventory collection, click Collect Inventory, as shown in Figure 6-77.
161
Configuring_FSM.fm
To begin the inventory collection, select Run Now and click OK button as shown in Figure 6-78.
A blue information square appears to say that the job is started as shown in Figure 6-79. Click Display Properties to check the job status.
162
Configuring_FSM.fm
163
Configuring_FSM.fm
Check you access status to the chassis, Select Action Security Configure Access as shown in Figure 6-82.
Collect inventory on your chassis, select Action Inventory View and Collect Inventory as shown in Figure 6-83.
164
Configuring_FSM.fm
Click OK to run now or schedule the inventory collection as shown in Figure 6-85.
.
165
Configuring_FSM.fm
A blue information square appears to inform you that the job is executed as shown in Figure 6-86.
166
Configuring_FSM.fm
Click the Log tab, if you wish to get more details about the tasks performed as shown in Figure 6-88.
Figure 6-88 Collect chassis inventory job completed in the Log tab
Go back to General tab, the progress is 100% which means that the inventory collection on the chassis is completed, as shown in Figure 6-89.
167
Configuring_FSM.fm
Click Home tab as shown in Figure 6-90 on page 168, then click Compute Nodes - Check and Update Firmware.
Note: In this example we discover a compute node but you can also discover others components using this method using their IP addresses.
168
Configuring_FSM.fm
Enter the service processor IP address of your server, then click on Discover Now as shown Figure 6-91
Note: For x86 nodes its the IMMs IP address, and for the POWER7 compute nodes its the Service Processors IP address. An information window appears to say that the job has been created. Click Display Properties to see the job status as shown in Figure 6-92.
169
Configuring_FSM.fm
When the job is completed, your server has been discovered as shown in Figure 6-93.
170
Configuring_FSM.fm
You should see the discovered system with no access. You have to grant the access to the server by clicking No Access as shown in Figure 6-95.
Enter the admin user of your service processor server and the password, then click Request Access as shown Figure 6-96.
171
Configuring_FSM.fm
When a green square with OK message appears, it means that you access is granted as shown in Figure 6-97.
Last step is to collect inventory, go back to the Compute Nodes - Check and Update Firmware tab, then click Collect Inventory, as shown in Figure 6-98.
By default the CMM (the chassis) is selected and it means that by default if you click Collect Inventory you will collect the inventory on all the chassis components.
172
Configuring_FSM.fm
If you need to collect the inventory on the node, click Browse as shown in Figure 6-99.
173
Configuring_FSM.fm
When you server is in the selected list as shown in Figure 6-101, click OK.
Then you will see your server in the Target System list as shown in Figure 6-102, click Collect Inventory to launch your collection.
174
Configuring_FSM.fm
Click OK to run the job now or you can schedule it if required as shown in Figure 6-103.
An information windows message appears to inform you that the job has been executed, click Display Properties button to display the job status as shown in Figure 6-104.
175
Configuring_FSM.fm
When the job is completed, the progress bar is 100% and the status is completed as shown in Figure 6-105.
You can check the log to see the different tasks performed for your information or in case of errors as shown in Figure 6-106.
176
Configuring_FSM.fm
You get a graphical view of the chassis and you can get the information about chassis components by positioning the mouse cursor over it as shown in Figure 6-108.
177
Configuring_FSM.fm
Select your chassis component, in our case we selected the switch module in bay 1 as shown in Figure 6-109.
Scroll down to the Action menu, select Action Security Configure Access as shown Figure 6-110.
178
Configuring_FSM.fm
You can see that the general access status is Partial Access as shown in Figure 6-111.
179
Configuring_FSM.fm
You can see that there are different protocols and most of them have no access. Click Request Access as shown in Figure 6-113.
Enter credentials for your I/O module then click Request Access as shown in Figure 6-114.
180
Configuring_FSM.fm
After a couple of time, you may receive a message that the not all protocols are enabled on the managed component, because not all discovery protocol are supported by the switch as shown in Figure 6-115.
Scroll down to note that more protocols are enabled now as shown in Figure 6-116.
Note: Some protocols require to be enabled on the I/O module itself directly. For example, if SSH wasnt enabled, you have enable it on the switch before to enable access for this protocol from FSM. To enable SNMP on the switch you need to configure SNMP credentials.
181
Configuring_FSM.fm
To collect inventory for the I/O modules select Action your I/O module name inventory View and Collect Inventory as shown in Figure 6-117.
182
Configuring_FSM.fm
Click Display Properties to see the job status as shown in Figure 6-120.
183
Configuring_FSM.fm
After a couple of minutes the job is completed and you can check the status as shown Figure 6-121.
184
Configuring_FSM.fm
To determine if a system needs updates, right click on an individual system or a group of systems and choose Release Management Show and Install Updates, as shown in Figure on page 185.
From here, a list of available updates can be reviewed, as shown in Figure 6-123.
The updates can be selected individually or all at once and then deployed via the Install button. After choosing the Install button, the install wizard, that is shown in 6.6, Updating the CMM firmware on page 150, can be followed to run the updates immediately or schedule them.
185
Configuring_FSM.fm
A more noticeable way of determining needed updates for systems is by configuring a compliance policy. This can be accomplished from the Home page, Plug-ins tab and choose the Update Manager link as shown in Figure 6-124 on page 186.
Figure 6-124
186
Configuring_FSM.fm
This will take you to the main Update Manager page. This page provides a jumping point for many options such as acquiring updates, creating compliance policies and viewing currently downloaded updates. To view updates that have been obtained, click Show updates groups as shown in Figure 6-125 on page 187.
Within Show update groups, left click on a group of updates, such as the IBM System x and BladeCenter Updates group, as shown in Figure 6-126, to review the available update package information.
Figure 6-127 on page 188 shows a list of packages that information has been downloaded about. By default, only the change history and readme documents will be downloaded. The actual payload file will only be downloaded when manually run by the user or when the
187
Configuring_FSM.fm
payload needs to be deployed. This ensures that space is not wasted on unneeded updates. The packages view shows the Name, Version, Severity, Product supported, Category, if the payload is download or not and a Description of the package.
By clicking the hyperlink name of a package, a General tab shows basic information about the package, as shown in Figure 6-128.
188
Configuring_FSM.fm
The change history or readme information of that package can also be reviewed, as shown in Figure 6-129 on page 189. These details can make it very easy to help determine which updates may be needed or not throughout the environment. Additionally, they will allow the FSM to become the common update repository, helping cut down on the need to use any external support websites.
Back on the main Update Manager page, compliance policies can be configured to help determine any needed updates. Click Optional: Create and configure compliance policies as shown as a third step in Figure 6-130.
189
Configuring_FSM.fm
In the next screen, select a system or group of systems that the updates will be applied to. Keep in mind that for compute nodes, the OS is required to push updates. So as a best practice, it is suggested to create compliance policies against specific devices and not the All Systems group. So for compute nodes, create a compliance policy against the All Operating Systems group or just against a group of Chassis. In this scenario, weve browsed to the All Operating Systems group and then clicked on the Show Compliance Policies button. This will allow any previously created compliance policies to show up. In Figure 6-131 on page 190, we can see that a policy does not yet exist, so well add one by choosing the Add button.
190
Configuring_FSM.fm
In this scenario, we select All IBM System x and BladeCenter updates and Add it to the right column as shown in Figure on page 192. Next well select OK.
On the next page choose Save for the Compliance to take effect.
191
Configuring_FSM.fm
After choosing Save, the main Update Manager page will be displayed with a new compliance graph as shown in Figure 6-133 on page 192.
192
Configuring_FSM.fm
From here, we can see that six systems need minor updates. We can click the 6 systems hyperlink and review which systems need updates. From here, all systems or certain systems can be selected via Actions Select All. Then choose Actions Release Management Show and Install Updates, as shown in Figure 6-134 on page 193, to deploy the updates.
193
Configuring_FSM.fm
First, find the I/O module and ensure that access is OK as shown in Figure 6-135 on page 194.
SSH access is required to get proper inventory against the switch and to push updates. Right click the system and choose Security Configure Access, as shown in Figure 6-136, to ensure that the SSH protocol is listed as OK.
194
Configuring_FSM.fm
Once SSH shows OK access, ensure that inventory has been collected and any updates have been downloaded to the FSM. From there, see if any updates are needed by right clicking on the switch and choose Release Management Show and Install Updates as shown in Figure 6-137 on page 195.
A list of needed updates will be shown as in Figure 6-138 which can be selected and installed.
195
Configuring_FSM.fm
The Install Wizard will be started. In this scenario, the switch being used does not support updates over SFTP. For that reason, a message will appear noting that an external TFTP or FTP will need to be configured, as shown in Figure 6-139 on page 196. Click Update Settings to ensure the external TFTP information is configured.
Once an external TFTP server is configured, the update will then be deployed to the I/O Module with the same look and feel as deploying updates to compute nodes or the CMM.
196
Configuring_FSM.fm
197
Configuring_FSM.fm
On the Home page, click the Administration tab and scroll to the bottom. Under Features on Demand tasks, click Manage Features on Demand Keys as shown in Figure 6-141 on page 198.
The Manage Features on Demand Keys page opens and the installed keys are displayed and you can select the keys that you want to view. To view management software keys, select IBM FSM keys from the View list as shown in Figure 6-142.
198
Configuring_FSM.fm
To view all IBM Flex System keys, including keys for managed resources, select All keys from the View list as shown in Figure 6-143 on page 199.
To import a key, click Add IBM FSM Keys or Add Node Keys button (depending on the view). If you click Add IBM FSM Keys, an Add IBM FSM Keys window opens that enables you to import a key. If you click Add Node Keys, a window opens that enables you to import keys for compute nodes. When you click Add Node Keys, a list of configuration templates will open as shown in Figure 6-144.
199
Configuring_FSM.fm
From here, a configuration template will need to be created that includes FoD keys that need to be deployed. After clicking the Create button, Figure 6-145 on page 200 will appear. Under Template Type, choose Server (via CIM protocol) to deploy FoD keys to an IMM2 of a compute node. For template, choose Feature Activation Manager Configuration and provide a name, then click Continue.
200
Configuring_FSM.fm
In the Wizard, there are two choices as shown in Figure 6-146 on page 201.
201
Configuring_FSM.fm
If choosing the Key Management System (KMS), the options shown in Figure 6-147 are available. In order to pull in keys from the KMS, a connection to the internet is required. Additionally, an IBM ID must be configured appropriately and the appropriate authorization codes must be available as provided when the FoD keys were purchased. If a proxy is required for connection, that can be configured when choosing Next.
202
Configuring_FSM.fm
If choosing to upload keys from the local system, the Figure 6-148 on page 203 appears. Browse to the FoD keys that need to be imported and add them to the list, then choose Next.
203
Configuring_FSM.fm
In the Automatic Reboot screen, as shown in Figure 6-149 on page 204, the ability to reboot the device if needed for the FoD key to take effect can be initiated.
After choosing Next and Finish through the Template Wizard, the newly created template will appear in the list as shown in Figure 6-150. Select the key, choose the Deploy button and point it to a system that the key should be deployed to.
204
Configuring_FSM.fm
6.13.1 Discover an IBM Storwize V7000 to manage from IBM Flex System Manager Storage Control
Discovery of the IBM Storwize V7000 is performed through the command line interface. To use the command manageV7000, the user name superuser must be active on the IBM Storwize V7000 and have a password. If the user name superuser is not active, you must transfer the key manually and use the command mkdatasource, as described in: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.dir ector.storage.helps.doc%2Fconfiguring_v7000_or_svc_storage.html
205
Configuring_FSM.fm
Note: Automatic discovery of the Storwize V7000 and the CLI commands require that the V7000 software version is 6.3.0.0 or later. Please check the firmware level on the V7000 as shown in Figure 6-152.
Note: The new IBM Storwize V7000 storage subsystem comes with the pre-configured IPv4 address 192.168.70.151. After the installation of the Storwize V7000 hardware, the user ID superuser, with the password passw0rd, is created.The management software then assigns an IPv6 address to the V7000 storage subsystem. If the IPv6 address is accessible to the management software, the default IPv4 address is disabled and the management software manages the chassis through the new IPv6 address. If the IPv6 address is inaccessible, the default IPv4 address is used to manage the V7000.
Note: All new V7000 storage subsystems come with the same default IPv4 address. Therefore, you must install them one at a time until they are all managed.
206
Configuring_FSM.fm
Check that your V7000 isnt already managed by your Flex System Management Node. If a V7000 is managed by your FSM, the phrase Storage Manager (V7000) is displayed in the Common Actions area of the Chassis Map view in the Chassis Manager page as shown Figure 6-153 on page 207.
207
Configuring_FSM.fm
If require to change the IP address of the V7000 storage subsystem, log in to the V7000 web interface and change the IPv4 or IPv6 address as shown in Figure 6-154.
For more information about using the storage subsystem web interface, see: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.acc .commontasks.doc%2Fcommontasks_navigating_fsm.htm
208
Configuring_FSM.fm
Use the management software CLI on the initial management node to copy the file /home/USERID/.ssh/id_rsaV7000 from the primary management node to the /home/USERID/.ssh directory on the other FSM as shown Figure 6-155.
Then, from the CLI of the additional management node (the additional FSM), run the following command to manage the V7000: smcli mkdatasource -c svc -f /home/USERID/.ssh/id_rsaV7000 -v v7000 -i <V7000_ip_address> where <V7000_ip_address> is the IP address of the V7000.
209
Configuring_FSM.fm
Collect inventory on V7000 storage by clicking View and Collect Inventory as shown in Figure 6-157.
Click Collect Inventory button to begin the inventory collection as shown in Figure 6-158.
210
Configuring_FSM.fm
A blue box message will appears to say that the job has been started and created successfully as shown in Figure 6-160.
211
Configuring_FSM.fm
If some errors appear, click the Log tab to get more information, as shown in Figure 6-162.
212
Configuring_FSM.fm
This action opens the Storage Management window shown in Figure 6-164.
The Storage Management Summary page is divided into these areas: Capacity Summary A pie chart represents your disk capacity in each of these categories as shown Figure 6-164
213
Configuring_FSM.fm
Total configured capacity (to volumes) Number of GB of the volumes that are assigned as shown Figure 6-164 Total available capacity (for volumes) Number of GB of disk pool size that is unassigned to volumes, but are available for creating future new volumes as shown Figure 6-164 Total available capacity represents the remaining total storage array or storage pool space that could be used to create volumes. Initially, when creating a storage array or pool, the configured capacity is zero and the available capacity is the pool size. Creating additional volumes decreases the amount of available capacity. Available capacity is a measurement of the current quantity of usable storage. The capacity measurement is a snapshot created when inventory is collected on the storage arrays. Inventory collection can be configured to run on a schedule to periodically update the capacity information if storage volumes and pools are created after the initial inventory collection. For local storage, capacity information collected for storage devices attached is limited to the Total raw capacity. The Total configured capacity and Total available capacity are not included in the Capacity Summary for these storage devices. The tasks that can be performed on an external V7000 storage system are summarized below.
214
Configuring_FSM.fm
215
Configuring_FSM.fm
Storage templates, as shown in Figure 6-167, can be used: To clone the storage configuration of a system - save a storage volume template from an existing server, and then later applying a saved template to another system. This can be used for duplication (clustering, or virtual server hosts) or for saving the storage configuration for backup or disaster recovery purposes. As a starting point for creating additional volumes - start with a base template and make changes as needed.
Capacity Details
For each type of storage, this table indicates the available capacity, usable capacity, total capacity, number of systems, and number of disk drives. The entries in this list correspond to storage groups having the same name as shown Figure 6-168 on page 216. If you select an entry, a table of storage subsystems that are members of the selected group is displayed.
Local Storage that is local to only one system, and therefore dedicated to only that system.
216
Configuring_FSM.fm
For the Local Storage row, capacity information collected for storage devices attached to systems. The Total usable capacity and Total available capacity is not displayed for these storage devices as shown in Figure 6-169.
Network storage is a storage accessed with switches, adapters, and protocols such as Fibre Channel, SAS, or iSCSI, as shown in Figure 6-170. Network storage (and compute node integrated storage) is managed by IBM Flex System Manager (for supported storage devices) and by native management applications provided with the network storage device.
217
Configuring_FSM.fm
Chassis
FC3171 8Gb SAN Pass thru
These are overall steps for adding Brocade SAN switch to FSM: 1. Obtain the IP address from Brocade switch UI 2. Ensure either the FSM is in the local DNS or added to the configured workstation /etc/hosts file 3. Start SMIA application 4. Start the configuration tool 5. Add the switch as a new fabric to the SMIA 6. Use mkdatasource command from FSM 7. Collect inventory on the Farm 8. Collect inventory on the switch objects
218
Configuring_FSM.fm
Figure 6-172 shows Applications main page. Click Start to run SMIA.
Log in your external switch (Figure 6-173 on page 219 shows SAN switch main page). Click Switch Admin.
Note the IP address in the Network tab as shown Figure 6-174 on page 219.
219
Configuring_FSM.fm
Check that SMIA is running as shown in Figure 6-175. Click SMIA Configuration Tool.
220
Configuring_FSM.fm
From the Home tab left click the Fabric Discovery Option as seen in the Figure 6-177.
221
Configuring_FSM.fm
Provide a Fabric name for the TOR switch, IP address and login credentials, defaults are admin/password, as shown in Figure 6-179.
222
Configuring_FSM.fm
Left click the CIMOM tab from the tools main interface as shown in Figure 6-181.
223
Configuring_FSM.fm
Check the SMI Agent port (25989), as shown in Figure 6-182 on page 224.
From the FSM CLI enter the mkdatasource command to add the data source as shown in Figure 6-183.
224
Configuring_FSM.fm
225
Configuring_FSM.fm
226
Configuring_FSM.fm
Use IBM Flex System Manager Network Control to manage network devices in your managed systems environment by performing the following tasks: Discovering network systems Use the Discovery task to collect an extended set of resources and relationships for network systems. Collecting and viewing inventory for network systems Use the View and Collect Inventory task in IBM Flex System Manager Network Control to view and manage an extended set of resources and relationships for network systems that have already been discovered. Configuring network systems with configuration plans and templates You can use the configuration manager to create, view, edit, delete, deploy, and schedule VLAN and protocol configuration templates to be deployed on supported network resources. Managing network system pools and logical networks Use network system pools and logical networks to effectively manage your virtual and physical networks. Managing network systems health IBM Flex System Manager provides facilities to monitor and troubleshoot network systems health. Working with network device groups Use the Resource Explorer task to view and manage network systems in IBM Flex System Manager. Collecting and viewing Network Topology Inventory Use IBM Flex System Manager Network Control to work with network inventory in a topology view. We will be discussing Network Pools concept and how to configure them for the purpose of managing the virtualization environments in 8.6, Overview of Network system pools on page 329. For more information about Network Control, refer to the Network Control section in the IBM Flex System InfoCenter found at: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp
227
Configuring_FSM.fm
228
Managing_HW_FSM.fm
Chapter 7.
229
Managing_HW_FSM.fm
Figure 7-1 Initial Setup screen on IBM Flex System Manager Home page
Click the name of the chassis that you want to manage as shown in Figure 7-2.
The Chassis Manager Chassis Map appears. It has two types of views: graphical and table. After you click the name of the chassis containing the compute node that you want to manage, the graphical Chassis Map opens as shown in Figure 7-3. The graphical Chassis Map is a visual representation of the front and back of the chassis and its components. It 230
Implementing Systems Management of IBM PureFlex System
Managing_HW_FSM.fm
gives you a good picture on where your hardware components are located physically and is a central point of management from which you can get hardware configuration and status information and perform various actions.
Use the Chassis Map to quickly identify problematic components of your chassis. On Figure 7-3 you can see an error with one of the compute nodes. Hover over the compute node to see brief info of the node and its problems, as shown in Figure 7-4.
Figure 7-4 Caption with brief information on a compute node in the Chassis Map
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
231
Managing_HW_FSM.fm
Click the compute node to get full details, advanced properties and all relevant actions. The common actions area for the specific node appears on the right side of the Chassis Map, as shown in Figure 7-5.
Figure 7-5 Chassis Map with selected compute node and available Common Actions
The full list of actions and details relevant to the selected chassis component appear below the Chassis Map, as shown in Figure 7-6. Select Actions System Status and Health Active Status to display the selected compute node Active Status page.
Figure 7-6 Actions menu of selected compute node navigating to Active Status task
The Active Status page provides a centralized interface that you can use to get a quick snapshot of the resources that trigger a status set entry. Currently only entries related to the
232
Managing_HW_FSM.fm
selected compute node are listed, as seen on Figure 7-7. You also can ignore status set entries to prevent them from displaying with an elevated status in the future.
All status set entries, including problems and compliance issues, are displayed. Clicking on an entry displays further details about the entry, as shown in Figure 7-8 on page 233.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
233
Managing_HW_FSM.fm
Select the Recommendation tab to read more on the possible root cause and recommendations for fixing the problem. See Figure 7-9.
Click the provided link to see recommendations on how to fix the problem. You will see troubleshooting information as in the example on Figure 7-10.
234
Managing_HW_FSM.fm
One of the first recommendations is to check the FSM event log for any fan- or cooling-related issues. Go back to the FSM browser window and close the Active Status tab, in order to return to the Chassis Map.
Figure 7-11 Actions menu of selected compute node navigating to Event Log task
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
235
Managing_HW_FSM.fm
Click the Show advanced properties link, next to the Actions button (see Figure 7-12) and select the Event Log tab, as shown in Figure 7-13 on page 236.
Figure 7-12 Chassis Map page with highlighted Show advanced properties link
Figure 7-13 Event Log tab on compute node advanced properties page
236
Managing_HW_FSM.fm
For the purpose of our discussion, we will open Even Log for all events. Perform one of the following actions: Use Global Find to search for tasks or resources, as shown in Figure 7-14 on page 237.
In the IBM Flex System Manager Web interface navigation area, expand System Status and Health and click Event Log, as shown in Figure 7-15 on page 237.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
237
Managing_HW_FSM.fm
On the Event Log page click Event Filter and select the filter criteria that you want to use. The default filter is All Events. The event log displays the events that have been received by IBM Flex System Manager and that match the filter criteria. See Figure 7-16 on page 238 for possible choices.
Note: The number of events that are displayed is limited by the event log preferences settings. By default, the event log displays the last 500 events that occurred over the last 24 hours. Use the Event Log Preferences page to change the defaults.
238
Managing_HW_FSM.fm
View the properties for the event in the table or click the event to view additional properties and details. Use Action Show Filter Row to enable the Filter row, as shown in Figure 7-17.
Figure 7-17 Event Log Actions menu navigating to Show Filter Row
The Filter row appears, as shown in Figure 7-18. Use it to apply granular event filters on each column.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
239
Managing_HW_FSM.fm
Click on a Filter link to configure a specific filter. For the purpose of our case, we will search for events containing the string hot. Click the Filter link on the Event Text column. See Figure 7-19 on page 240.
All events containing the string hot in their Event Text are shown, as in Figure 7-20.
Click on the event text to see more details on the event. The Warning event describes improper hot air calculation in the chassis, which could be potentially related to the critical event we observed initially.
240
Managing_HW_FSM.fm
To create a simple event filter from the event we marked in the Event Log, select the event and click on the Create Filter button. The Create Simple Event Filter box appears as shown in Figure 7-21. Provide an informative filter name and description.
Click Ok and acknowledge the successful event filter creation. Click on Close Message as shown in Figure 7-22 on page 241.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
241
Managing_HW_FSM.fm
In the IBM Flex System Manager Web interface navigation area, expand Automation and click Event Filters, as shown in Figure 7-23. The newly created filter appears on the event filters list.
242
Managing_HW_FSM.fm
In the IBM Flex System Manager Web interface navigation area, expand Automation and click Event Actions, as shown in Figure 7-24.
Click Create to start the Create Action window and select Send an e-mail (Internet SMTP) as shown in Figure 7-25.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
243
Managing_HW_FSM.fm
Click OK and fill out all required information on the next page. Along with the action name and description you need to enter the Send-to e-mail address, the Reply-to e-mail address, E-mail server address and Port number. You can also specify what kind of information the e-mail subject and body should include. Customize that by adding or removing pre-defined event variables from the Event variable drop-down list. See Figure 7-26 on page 244.
Click Test to ensure that the action is properly configured. Click OK.
244
Managing_HW_FSM.fm
The newly created event action appears on the Event Actions list, as seen in Figure 7-27 on page 245.
Note: Event action History is not saved by default. Saving the history of an event action can provide useful information, such as date and time when the event action ran and event that triggered the action. Click Actions Start Saving History to enable History for a selected event action.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
245
Managing_HW_FSM.fm
In the navigation pane of the IBM Flex System Manager Web interface, expand Automation and click Event Automation Plans. On the Event Automation Plans page, click Create (see Figure 7-28).
246
Managing_HW_FSM.fm
The Welcome page of the Event Automation Plan wizard is displayed (see Figure 7-29). On the Welcome page, specify whether you want to show the Welcome page the next time you use the wizard, click Next.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
247
Managing_HW_FSM.fm
The Name and Description page is displayed (see Figure 7-30 on page 248). Type a descriptive name for the event automation plan that you are creating.
Figure 7-30 Create Event Automation Plan Wizard Name and Description page
248
Managing_HW_FSM.fm
On the Targets page, select the systems that the event automation plan will monitor for specific generated events. Select All Systems in the Available list and click Add to move them to the Selected list (see Figure 7-31 on page 249). Click Next.
Common event filters are predefined simple filters that monitor for events of common interest in systems management. For example, the Disks event filter is triggered by any hard disk events and the Fans event filter is triggered by any fan events. The Event Automation Plan wizard provides several common event filters so you can create typically required event automation plans quickly and easily.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
249
Managing_HW_FSM.fm
To monitor specific events that are not included in the common event filters, select Advanced Event Filters (see Figure 7-32 on page 250). Select the event filter we created in 7.3, Creating an event filter from an event on page 240. Click Next.
250
Managing_HW_FSM.fm
The Event Actions page is displayed (Figure 7-33 on page 251). Select the event action created in 7.4, Define event actions on page 242.
Figure 7-33 Create Event Automation Plan Wizard Event Actions page
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
251
Managing_HW_FSM.fm
On the Time Range page (Figure 7-34), choose the period of time over which you want to collect the events. You can select All the time (24x7) to enable the plan to be active all the time. Or you can select Custom to choose specific days and time for the plan to be active.
Figure 7-34 Create Event Automation Plan Wizard Time Range Custom page
Select All the time (24x7) and click Next (Figure 7-35).
Figure 7-35 Create Event Automation Plan Wizard Time Range page
252
Managing_HW_FSM.fm
On the Summary page (Figure 7-36 on page 253), verify the details of the event automation plan. If you need to make changes, click Back. Make sure to specify whether you want to apply the event automation plan as soon as you finish creating it. Click Finish.
The event automation plan is saved and is displayed on the Event Automation Plans page, as shown in Figure 7-37.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
253
Managing_HW_FSM.fm
Select the newly created automation plan and click Actions, as shown in Figure 7-38. You can Edit, Delete or Deactivate the automation plan. You can deactivate an event automation plan so that the specified events do not trigger the plan. When you want to enable event automation plan again, you can subsequently Activate the event automation plan. By default, event automation plans are activated. On the Actions menu, click Properties.
View the automation plan properties and click Edit if you need to change any settings. See Figure 7-39.
254
Managing_HW_FSM.fm
7.6 Handling serviceable hardware problems with IBM Flex System Manager Service and Support Manager
So far we discussed how to view events and introduced automation by creating event automation plans based on event filters and actions. We will continue exploring automation options in FSM in this section. In some cases you would need to contact IBM support regarding a hardware issue and submit a support data for further analysis. This activity usually includes a number of time consuming manual tasks. Such manual tasks can now be automated with Service and Support Manager. Service and Support Manager is a plug-in for FSM. Service and Support Manager automatically detects serviceable hardware problems and collects supporting data for serviceable hardware problems that occur on your monitored endpoint systems. The IBM Electronic Service Agent tool is integrated with Service and Support Manager and transmits serviceable hardware problems and associated support files to IBM support. Service and Support Manager includes the following features: Automatically detects serviceable hardware problems to IBM support for all monitored systems. The integrated Electronic Service Agent tool securely transmits serviceable hardware problems, associated support files, and Performance Management data to IBM support. Collects and securely transmits scheduled system inventory and diagnostic support files to an IBM database. This inventory information is available to IBM support representatives when they are solving your problem. Communicates with IBM support using a secure connection using encryption and authentication. Includes the option to send e-mail notifications when a serviceable problem is detected and service request is opened. Service and Support Manager begins automatically monitoring for serviceable hardware problems as soon as FSM is installed. However, activation by running the Getting Started Wizard is required to configure the Electronic Service Agent tool which is integrated with Service and Support Manager to securely transmit serviceable hardware problems and associated support files, inventory, and Performance Management data to IBM support.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
255
Managing_HW_FSM.fm
To activate Electronic Service Agent, navigate to the FSMs Home page. Click the Plug-ins tab, as shown in Figure 7-40.
Scroll down to find the Service and Support Manager section. Click Getting Started with Electronic Service Agent, as shown in Figure 7-41 on page 256.
Figure 7-41 Service and Support Manager section on FSM Plug-ins page
256
Managing_HW_FSM.fm
Figure 7-42 Getting Started with Electronic Service Agent Welcome page
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
257
Managing_HW_FSM.fm
Fill out Your company contact information (Figure 7-43 on page 258). Click Next.
Figure 7-43 Getting Started with Electronic Service Agent Your company contact page
258
Managing_HW_FSM.fm
Provide System location information which might differ from your company contact information (see Figure 7-44 on page 259).
Figure 7-44 Getting Started with Electronic Service Agent System location page
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
259
Managing_HW_FSM.fm
Electronic Service Agent tool needs Internet access in order to securely transmit serviceable hardware problems, associated support files, and Performance Management data to IBM support. Enter Internet proxy details if applicable, test Internet connection and click Next (see Figure 7-45 on page 260).
Figure 7-45 Getting Started with Electronic Service Agent Connection page
260
Managing_HW_FSM.fm
Optionally, enter any IBM IDs you might have in order to see the service information transmitted to IBM by Electronic Service Agent under your IBM account. See Figure 7-46 on page 261. Click Next.
Figure 7-46 Getting Started with Electronic Service Agent Authorize IBM IDs page
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
261
Managing_HW_FSM.fm
Review the Summary page (Figure 7-47 on page 262) and click Finish.
Figure 7-47 Getting Started with Electronic Service Agent Summary page
Return to the Plug-ins tab of the FSM Home page, scroll down and click Service and Support Manager, as shown in Figure 7-48.
Figure 7-48 Service and Support Manager section on FSM Plug-ins page
262
Managing_HW_FSM.fm
The Service and Support Manager page (Figure 7-49 on page 263) gives you an overview of the serviceable problems in the environment and provides you with a number of links to operate with it. If you need to view, collect and submit support files to IBM manually, click Manage support files. Click Manage settings to configure Service and Support Manager settings.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
263
Managing_HW_FSM.fm
Select Automatically report problems for all systems to allow Electronic Service Agent to report all problems to IBM support automatically. See Figure 7-50 on page 264
If you want to receive notifications regarding Service and Support Manager events, you can create an event automation plan as described in 7.5, Automating tasks with event automation plans on page 245. Use the Electronic Service Requests event filter in your automation plan to get notified every time Service and Support Manager detects a serviceable hardware problem and opens an electronic service request with IBM support. You can find more information on Service and Support Manager here: http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.esa.dir ector.help/esa_kickoff.html
264
Managing_HW_FSM.fm
Once configured, this event action will forward FSM events to your NetView host. In order for your NetView host to understand the SNMP data that it receives from FSM, you need to load it with the FSM Management Information Base (MIB) files. Send an SNMP trap to an IP host This event action can be used in the general case when integrating FSM with a monitoring system which can receive SNMP traps. Once configured, this action will forward FSM events to your enterprise monitoring system. In order for your monitoring system to understand the SNMP data that it receives from FSM, you need to load it with the FSM MIB files. Contact your IBM support representative to obtain the required FSM MIBs. For more information on these and other event actions, visit http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.directo r.automation.helps.doc/fqm0_c_ea_actions.html
7.8 Using Monitors and Thresholds to monitor system status and health
The term monitor refers to a specific resource counter (for example CPU Utilization) that you can watch (for real-time monitoring), record (for historical information), or set a threshold on (for alerting and automation). The Monitors task provides the tools that you need to retrieve real-time status and quantitative data for specific properties and attributes of resources in your environment. You can also set thresholds for the monitors, graph the data that monitors retrieve, and drill down to quickly view the status of resources for each system and the name of the monitor so that you can view its properties. The specific monitors available vary based on the type of resource. Note: For the purpose of this exercise, we will use a Windows 2008 R2 server with Common Agent installed. For more information on agents, refer to 5.1.4, Agents and tasks supported on page 87.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
265
Managing_HW_FSM.fm
In the IBM Flex System Manager Web interface navigation area, expand System Status and Health and click Monitors, as shown in Figure 7-51. Click Browse to select a system or group to view monitors for.
266
Managing_HW_FSM.fm
Select Target Systems from the Show drop-down list to see individual systems. Select the system to monitor (in our case PF-Windows1) and click Add to add it to the Selected list, as shown in Figure 7-52 on page 267. If needed, you can choose Groups of systems, instead of individual systems. Click OK to proceed.
FSM arranges available monitors in groups called monitor views. Each view represents a list of the most commonly available monitors in a category, for example, monitors that are supported by AIX. For our example we will use Common Monitors view. The Common Monitors view contains some of the most common monitors for operating systems that are supported by FSM. When you create your own monitor view, additional individual operating systems monitors might be available.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
267
Managing_HW_FSM.fm
Click Common Monitors or select it and click Show Monitors, as shown in Figure 7-53.
Monitor Views page shows all common monitors for the selected Windows target system. You can see the real-time values of the individual monitors and information on activated Thresholds. There are no activated thresholds as seen in Figure 6-43 on page 95.
Figure 7-54 Common Monitors Monitor View for the selected target system
A threshold for a numeric monitor is a high or low limit that you do not want the monitored system resource to exceed. For both the high threshold and the low threshold, you have the option of specifying a warning value and a critical value. For example, the high threshold for a
268
Managing_HW_FSM.fm
monitor that measures the percentage of used space on a disk drive might have a warning value of 80 and a critical value of 90. Select the CPU % Utilization monitor, click Actions Activate Threshold to configure a threshold (see Figure 7-55).
Figure 7-55 Activate Threshold Actions menu for selected CPU % Utilization monitor
When you activate a threshold on a numeric monitor you get the page shown in Figure 7-56 on page 270. Activating a threshold includes setting a number of options. Choose whether to generate an event when the threshold is exceeded and determine the amount of time the threshold waits before resending the information. Define Critical and Warning threshold values. When the monitored resource exceeds the specified value for any threshold limit, the monitor displays the appropriate icon for a warning or critical notification.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
269
Managing_HW_FSM.fm
Let us configure the threshold to trigger an event in case of high CPU Utilization on the selected Windows system. Check the Critical and Warning check boxes under Monitor values that are too high section and configure the values as shown in Figure 7-56 on page 270. Set the Minimum duration to 20 seconds. This will ensure triggering an event if the CPU Utilization value exceeds the threshold for over 20 seconds. Click OK.
270
Managing_HW_FSM.fm
The activated Threshold is now visible on the CPU % Utilization monitor, as shown in Figure 7-57.
Figure 7-57 Monitoring View page with activated threshold for CPU % Utilization monitor
For the purpose of our exercise, we utilized the systems CPU to 100%. As seen in Figure 7-58, the Threshold Status turns to Critical. This happens 20 seconds after the high CPU utilization started, because the Critical threshold value we specified earlier is 95 and the minimum duration is 20 seconds.
Figure 7-58 Monitoring View page with Critical Threshold Status for CPU % Utilization monitor
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
271
Managing_HW_FSM.fm
The Critical problem also appears in the Active Status page, as shown in Figure 7-59 on page 272.
Figure 7-59 Active Status page showing the Critical Threshold Status
We want to be notified by e-mail in the event of high CPU on our Windows system. Return to the Monitor View for the selected target system. Select the CPU % Utilization monitor, click Actions Create Event Automation Plan, as shown in Figure 7-60.
Figure 7-60 Create Event Automation Plan Actions menu for selected monitor
272
Managing_HW_FSM.fm
Click Next on the Welcome page. Enter a Name and Description for the automation plan, see Figure 7-61 on page 273.
Figure 7-61 Create Event Automation Plan Wizard Name and Description page
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
273
Managing_HW_FSM.fm
Select threshold levels to filter on. In this case, select High - Critical and High - Warning, as shown in Figure 7-62 on page 274. If you want to receive an e-mail when the Critical condition has been resolved, select Threshold resolved as well. Click Next.
274
Managing_HW_FSM.fm
Select Add to the event log and Electronic Service Notification event actions as shown in Figure 7-63 on page 275. We created Electronic Service Notification action in 7.4, Define event actions on page 242. It sends an e-mail notification with event information.
Figure 7-63 Create Event Automation Plan Wizard Event Actions page
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
275
Managing_HW_FSM.fm
Our Windows server is performing heavy CPU load operations during the weekend and high CPU utilization is expected and considered normal. We want to be notified for high CPU utilization only from Monday till Friday. On the Time Range page, select Custom and specify the time range constraints for the automation plan as shown in Figure 7-64 on page 276. Click Next.
Figure 7-64 Create Event Automation Plan Wizard Time Range Custom page
276
Managing_HW_FSM.fm
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
277
Managing_HW_FSM.fm
In the IBM Flex System Manager Web interface navigation area, expand Automation and click Event Automation Plans to see the automation plan we just created (Figure 7-66).
The automation plan is active. Any time the CPU % Utilization Threshold for our Windows system turns to Critical or Warning state, we will be notified on the e-mail address specified in the Electronic Service Notification event action settings.
278
Managing_HW_FSM.fm
Let us now stop the generated CPU load on our Windows system. Open the Event Log page by expanding System Status and Health and clicking Event Log. Enter PF-Windows1 in the Search field to filter only events related to our Windows system. Notice the Resolution event in Figure 7-67 that appeared after decreasing the CPU load.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
279
Managing_HW_FSM.fm
Open the Thresholds page by expanding System Status and Health and clicking Thresholds, as shown in Figure 7-68. Use this page as a quick way to view and manage thresholds that are set for the monitors on your resources.
280
Managing_HW_FSM.fm
Return to the Chassis Map and select a compute node. The Common Actions navigation bar on the right side of the Chassis Map gives you quick access to some of the most common tasks performed on the system, as shown in Figure 7-69.
If you need to perform hardware maintenance, you can power off and power on or restart the compute node. Click on the Remote Control task to start the Remote Control Java application. When you start the Remote Control application from FSM, you are prompted to save a shortcut to the application on your system. You can then use this shortcut to open the Remote Control session to the specified compute node without having to launch it from the FSM user interface. However, your computer must have access to FSM, because the application validates the user ID with the management software user registry.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
281
Managing_HW_FSM.fm
Select the connection type as shown in Figure 7-70 on page 282: If you need to give exclusive access to the remote control session, you can choose Single-user access. All other Remote Control sessions to the selected compute node will be blocked until you disconnect from the selected compute node. Select Multi-user to allow multiple users to connect to the remote session.
282
Managing_HW_FSM.fm
The console screen appears as shown in Figure 7-71 on page 283. You can now use the mouse and keyboard to operate with the server as if you were at the local console. Click the arrow on top of the console screen to open the Remote Control toolbar.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
283
Managing_HW_FSM.fm
The Remote Control toolbar (see Figure 7-72 on page 284) offers functions such as screen capture, compute node power controls, defining custom key sequences, sticky keys, mounting media and additional Remote Control preferences. Click the mount media icon and select Mount Remote Media.
You can mount a local CDROM drive, upload an image to the IMM (up to 50MB) or select an image. Highlight Select an image and click Add as shown in Figure 7-73.
284
Managing_HW_FSM.fm
You are prompted to select an image from your local computer. Select the image you want to mount and click Open, as shown in Figure 7-74 on page 285.
The image file path appears in the list of devices available for mounting, as shown in Figure 7-75. Click Mount All.
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
285
Managing_HW_FSM.fm
The image is now mounted as shown in Figure 7-76 on page 286. If you need to unmount it at any time, click Unmount All. Leave the image mounted and click Close.
286
Managing_HW_FSM.fm
Open My Computer in Windows, to ensure that you can access the mounted image as a CD Drive (see Figure 7-77).
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
287
Managing_HW_FSM.fm
Notice that you can also use the power control options from the Remote Control toolbar. You can choose to restart/power off the compute node immediately (Restart Immediately/Hard Power Off) or gracefully shut down the OS before (Shut Down OS and Restart/Shut Down OS and Power Off) as shown in Figure 7-78.
288
Managing_HW_FSM.fm
You can quickly open a Remote Control session to another compute node by clicking on the plus sign next to your Remote Control session thumbnail. See Figure 7-79 on page 289.
Figure 7-79 Window showing available compute nodes for Remote Control
Click Cancel and close the Remote Console. The user ID used to start the Remote Control application must be a valid user ID that has been defined in the FSM user registry. The user ID must also have sufficient user authority to access and manage a compute node. You can assign the role of SMAdministrator to the user ID, or you can define a custom role for compute node access and management and assign that role to the user ID. Note: Remote Control in FSM is available only for X-Architecture compute nodes. Instead, you can open a terminal console to any virtual server on a Power Systems compute node. For more information, see http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc. 8731.doc/using_remote_access.html
Chapter 7. Managing chassis hardware components with IBM Flex System Manager
289
Managing_HW_FSM.fm
290
Managing_KVM_FSM.fm
Chapter 8.
291
Managing_KVM_FSM.fm
Before starting the implementation of the SAN storage based solution, please read SAN storage based model on page 99.
8.2.1 Preparation
Install and configure RHEL 6.2 on the compute node using the Virtualization Host role. For the purpose of our discussion, we do not cover RHEL installation in our book.
292
Managing_KVM_FSM.fm
To allow FSM communications to the KVM platform agent, perform the following steps: 1. Disable SELinux as shown in Figure 8-2.
Note: You can also configure SELinux in permissive mode if require for security reason. 2. Configure iptables as shown in Figure 8-3.
Note: If you face some issues during the inventory collection or other action from the FSM due to iptables configuration on a KVM host, try removing the REJECT statement at the end of the INPUT chain in the filter table and reappend it to the end of the chain. You can also temporarily disable iptables for troubleshooting purposes. 3. Configure Yum on your system, please refer the URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Gu ide/sec-Configuring_Yum_and_Yum_Repositories.html Note: We recommend to configure Yum because during the KVM PA Agent installation you could face RPM dependencies requirements and you will save time if Yum is configured.
293
Managing_KVM_FSM.fm
4. Check that the date on your KVM node is the same than the other hosts and the FSM as shown in Figure 8-4.
Note: If an NTP server is configured in our network, please configure it on all your KVM hosts and on the FSM also.
3. Put the downloaded agent in /tmp of your KVM host using SCP protocol and an SCP tool then uncompress the archive as shown in Figure 8-6.
294
Managing_KVM_FSM.fm
4. Launch KVM Platform Agent installation as shown in Figure 8-7 and Figure 8-8
295
Managing_KVM_FSM.fm
Note: If you face some error message like shown Figure 8-9, please use yum to solve the dependencies issue and launch again your KVM platform agent installation.
Your KVM Platform Agent installation is completed. Note: Repeat the steps 8.2.1, Preparation on page 292 and steps 8.2.2, KVM Platform Agent installation on page 294 for each host that you want to manage with FSM.
Enter the IP address of the KVM host as shown in Figure 8-11 or the range of KVM hosts IP address that you have to discover and click Discover Now.
296
Managing_KVM_FSM.fm
When the job is completed, click on discovered system and you can see that an operating system object type has been discovered as shown in Figure 8-13, then click No access.
.
Grant access to your KVM host using root credentials as shown in Figure 8-14, then click on your host.
.
297
Managing_KVM_FSM.fm
Select Action menu and run Collect Inventory as shown in Figure 8-15.
After a couple of time, your collection is completed as shown in Figure 8-16 and your KVM host is ready to be managed by FSM.
298
Managing_KVM_FSM.fm
The picture shown in Figure 8-17 illustrate an image repository for a KVM virtual environment with SAN storage.
8.3.1 Preparation
Follow these steps to establish an image repository for KVM using the SAN-based storage. Note: The images shown in the image repository are not created automatically when a new repository is created. Images must be imported or captured to deploy virtual server and workload. 1. Install your KVM host following the step in section 8.2.1, Preparation on page 292 Note: Stop at the end of the section 8.2.1, Preparation on page 292
299
Managing_KVM_FSM.fm
2. Install prerequisite RPMs required to install Linux x86 Common Agent as shown in Figure 8-18 and Figure 8-19.
300
Managing_KVM_FSM.fm
2. Download KVM Common Agent from the following URL (see Figure 8-21): https://www14.software.ibm.com/webapp/iwm/web/reg/download.do?source=dmp&S_PKG= dir_63_x86_MDagents&lang=en_US&cp=UTF-8
3. Copy the common agent for example in /tmp of your KVM host using SCP protocol and an SCP tool then uncompress the archive with the command line bellow: tar -xvf IBM Systems Director 6.3 Common Agent for Linux on IBM x86
301
Managing_KVM_FSM.fm
Figure 8-22 Common Agent installation on the KVM future image repository server
Figure 8-23 Common Agent installation on the KVM future image repository server.
302
Managing_KVM_FSM.fm
6. Go to Discovery Manager and enter the IP address of the host, then click Discover Now as shown Figure 8-24 on page 303.
7. Click OK to run the job now and click Display Properties to check the job progress status as shown in Figure 8-25.
303
Managing_KVM_FSM.fm
8. Grant the access to the discovered system, click Discovered Systems tab as shown in Figure 8-26.
9. Click No access and use root credential to grant access to the system as shown in Figure 8-27 on page 304, then click on the system name.
304
Managing_KVM_FSM.fm
10.Select Collect Inventory on the system as shown in Figure 8-28 then click OK to run the job now.
11.Click Display Properties button as shown in Figure 8-29 to check the progress.
305
Managing_KVM_FSM.fm
You successfully completed common agent installation, discovery, and inventory collection on KVM repository host.
306
Managing_KVM_FSM.fm
Go to Actions menu, select Release Management Install Agent as shown in Figure 8-32.
You get a welcome screen for Agent Installation as shown in Figure 8-33, click Next.
307
Managing_KVM_FSM.fm
Select your future image repository system which is an object type Operating System Linux as shown in Figure 8-36, then click Next.
308
Managing_KVM_FSM.fm
Check the summary which show you the agent and the target for installation as shown in Figure 8-37, then click Finish button.
Click Display Properties as shown in Figure 8-39 to check the job status and wait until status is completed.
309
Managing_KVM_FSM.fm
Important: The KVM host WWN need to be visible from the V7000 storage system, please ensure that you can see them. If you face a problem please check you SAN zoning or your storage adapters. Log on to the V7000 storage GUI as shown in Figure 8-40.
You see that there is no host define for your KVM hosts as shown in Figure 8-42.
310
Managing_KVM_FSM.fm
Click Create Host, then click Fibre Channel Host as shown in Figure 8-43.
311
Managing_KVM_FSM.fm
Select your WWN and specify a Host Name as shown in Figure 8-44.
312
Managing_KVM_FSM.fm
313
Managing_KVM_FSM.fm
Click Create Host to launch the host map creation as shown in Figure 8-46.
Wait till the creation task is completed as shown in Figure 8-47 on page 314.
314
Managing_KVM_FSM.fm
Go back to the host view to check that your host has been created as shown in Figure 8-48.
Note: You need to repeat this process on each KVM host. To get more informations on storage, please refer to the link: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fco m.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_storage_paths.html
8.3.7 Discover and Configure an image repository server for SAN storage
Go to VMControl and click Create Image Repository as shown in Figure 8-49.
315
Managing_KVM_FSM.fm
You are redirected to the Welcome screen as shown in Figure 8-50. Click Next.
Specify the name of you KVM image repository as shown in Figure 8-51, then click Next.
316
Managing_KVM_FSM.fm
Select the Target System which has been prepared before with common agent and image repository subagent to create an image repository system as shown in Figure 8-52, then click Next.
Select the storage that you want to use for the image repository on which virtual appliances will be stored as shown in Figure 8-53 on page 317.
317
Managing_KVM_FSM.fm
Check the summary and click Finish to complete the image repository creation as shown in Figure 8-54.
A blue information windows appears, click Display Properties as shown in Figure 8-55.
Managing_KVM_FSM.fm
Click Storage system pools as shown in Figure 8-58, you can note that there are no storage system pools available at the moment. Click Create button.
The Welcome page to create storage system pool appeared as shown in Figure 8-59.
319
Managing_KVM_FSM.fm
Specify the name to assign to the Storage system pool as shown in Figure 8-60.
Select the storage system that you want to assign to the storage system pool as shown in Figure 8-61.
320
Managing_KVM_FSM.fm
A blue information window appears as shown in Figure 8-64, click Display Properties.
At the end of this process your Storage System Pool will be created.
321
Managing_KVM_FSM.fm
Go to VMControl main page as shown in Figure 8-65, click Server system pools.
You are redirected to the Server system pools window as shown in Figure 8-66, click Create to create a new Server system pool.
You are redirected to the Welcome page to create a Server system pool as shown in Figure 8-67, then click Next.
322
Managing_KVM_FSM.fm
Specify a name to assign to the server system pool as shown in Figure 8-68, then click Next.
Under Pooling Criteria, check Only add hosts capable of live virtual server relocation as shown in Figure 8-69, then click Next.
323
Managing_KVM_FSM.fm
Select a host as initial host to initiate the creation if the server system pool as shown in Figure 8-70, then click Next.
Add the host to the list as shown in Figure 8-71, then click Next.
324
Managing_KVM_FSM.fm
Select the shared storage system that you want to assign to the server system pool as shown in Figure 8-72, then click Next.
If you have several hosts, you can add additional hosts to your server system pool to increase high availability and the amount of resources shared in your system pool as shown in Figure 8-73, then click Next.
Select the optimization mode desired as shown in Figure 8-74, then click Next.
325
Managing_KVM_FSM.fm
Click Display Properties to check the creation progress as shown in Figure 8-76.
When the creation is completed, go back to View System Pools and check that the new Server system pool is available as shown in Figure 8-77.
326
Managing_KVM_FSM.fm
Select you Server system pool, click KVMpool Availability Add Hosts as shown in Figure 8-79.
The Welcome screen for adding hosts appears as shown in Figure 8-80, then click Next.
327
Managing_KVM_FSM.fm
Select the host that you want to add to your server system pool as shown in Figure 8-81, then click Next.
328
Managing_KVM_FSM.fm
Go back to Server system pools view and click your KVM pool, you can see now that you have an additional KVM host in your Server system pool as shown in Figure 8-85.
329
Managing_KVM_FSM.fm
To implement Network system pools, perform the following steps: 1. Enable SNMP on the Switches that you want to add to your Network System Pool, you have to see SNMP protocol access OK on your switch from the FSM GUI as shown in Figure 8-86.
2. Enable SNMP on your KVM hosts that you want to add to your Network System Pool as shown in Figure 8-87.
Figure 8-87
To further implement Network system pools, refer to the following documentation: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fco m.ibm.sdnm.adv.helps.doc%2Ffnc0_r_panel_network_ctrl_NSP_learn_more.html
330
Managing_KVM_FSM.fm
Select Virtual Appliances tab as shown in Figure 8-89, then click Import in the Common tasks list.
You are redirected to the import appliances Welcome page as shown in Figure 8-90. Click Next to start the import process.
331
Managing_KVM_FSM.fm
Enter the path to import your appliance, in our case we will import an appliance from an http server as shown in Figure 8-91, then click Next.
If your wish to not import the Digital Signature check the box as shown in Figure 8-92, then click Next.
By default the original appliance name is assigned, as shown in Figure 8-93, but you can specify another one, then click Next.
332
Managing_KVM_FSM.fm
Select the image repository in which you want to import the virtual appliance as shown in Figure 8-94, then click Next.
You can create a new version tree for the imported appliance as shown in Figure 8-95 or can add it under an existing tree as a child appliance of an existing one. Click Next to continue.
333
Managing_KVM_FSM.fm
Select Run Now and click OK to start the virtual appliance import process as shown in Figure 8-97.
After that, click Display Properties, you are redirected to Active and Scheduled jobs window as shown in Figure 8-98.
Note: Appliance import times may vary depending on where the appliance resides in the network.
334
Managing_KVM_FSM.fm
When import process is completed, please go back to Virtual Appliances tab as shown Figure 8-99, where you can check that the new appliance is available for deployment.
335
Managing_KVM_FSM.fm
The Welcome screen for the Deploy Virtual Appliance appears as shown in Figure 8-101, click Next.
Select the appliance that you want to deploy as shown in Figure 8-102, then click Next.
Note: You can see appliances available from different image repositories, as shown in Figure 8-102.
336
Managing_KVM_FSM.fm
Select the Target to deploy the new virtual server as shown Figure 8-103 and click Next.
Note: You can choose to deploy an appliance on an existing virtual server. A virtual server is a virtual machine with CPU, RAM and HDD on which you can install an OS or deploy a virtual appliance. Specify a Workload Name as shown in Figure 8-104 and click Next.
Note: A Workload in FSM is a group which contain one or several virtual servers.
337
Managing_KVM_FSM.fm
Specify a name for your Virtual Server as shown in Figure 8-105, then click Next.
Assign a disk from a Storage Pool or from a Storage Volume, as shown in Figure 8-106. select Assign to Storage Pool, then click Next.
Note: By default storage volume (disk1) is selected as shown Figure 8-106. Select the Storage System Pool configured previously, as shown in Figure 8-107, then click OK.
338
Managing_KVM_FSM.fm
You reached the Storage mapping GUI as shown in Figure 8-108, and you remark that the disk1 is not selected now because a disk will be created automatically in you storage pool, click Next.
Select the Virtual Network Adapter to create a virtual Ethernet adapter on your virtual server, as shown in Figure 8-109, then click Next.
339
Managing_KVM_FSM.fm
You can preconfigure several parameters like the name, the network configuration of your virtual server as shown Figure 8-110, then click Next.
340
Managing_KVM_FSM.fm
Click OK to launch creation of your virtual server workload member as shown Figure 8-112.
341
Managing_KVM_FSM.fm
Go back to the Virtual Severs and Hosts view to check that your new server has been deployed as shown in Figure 8-115.
342
Managing_KVM_FSM.fm
The Welcome capture page appears as shown Figure 8-117, click Next.
Specify a name for your virtual appliance that you want to create by the capture process as shown in Figure 8-118, then click Next.
343
Managing_KVM_FSM.fm
Select the source from which you want to capture as shown in Figure 8-119 then click Next.
Select the virtual server that you want to capture as shown in Figure 8-120.
344
Managing_KVM_FSM.fm
Select the image repository on which you want to put the appliance generated by the capture process as shown in Figure 8-121.
Select the disk that you want to capture from your existing virtual server as shown in Figure 8-122.
345
Managing_KVM_FSM.fm
Select the Network Mapping for your future appliance as shown in Figure 8-123.
If no operating system has been discovered from the original virtual server, you have to specify the type of operating system as shown in Figure 8-124.
346
Managing_KVM_FSM.fm
Select the version control type for your future virtual appliance as shown Figure 8-125.
Check the Summary and note that you cannot capture a running server as shown in Figure 8-126.
347
Managing_KVM_FSM.fm
Go back to Virtual Servers and Hosts view, then power off the virtual server that you want to capture as shown in Figure 8-127.
348
Managing_KVM_FSM.fm
Go back to Summary and close the Warning information window as shown in Figure 8-129, then click Finish.
Click OK to run the job as shown in Figure 8-130 and begin to capture your virtual server.
Click Display Properties to check the job status as shown in Figure 8-131.
Figure 8-131 Capture job status Chapter 8. Managing KVM environment with IBM Flex System Manager
349
Managing_KVM_FSM.fm
Go back to VMControl main tab and check that your appliance count has been incremented as shown in Figure 8-133, then click Virtual Appliances.
Check in Virtual Appliances that you see the new virtual appliance as shown in Figure 8-134.
350
Managing_KVM_FSM.fm
Click Virtual Servers and Hosts in Common Tasks as shown in Figure 8-136.
351
Managing_KVM_FSM.fm
Right click on your virtual server for relocation, then select Availability Relocate as shown in Figure 8-137.
A confirmation window appears to confirm that your virtual server can be relocated as shown in Figure 8-138, click OK to launch the server relocation.
352
Managing_KVM_FSM.fm
Click Display Properties to check the relocation status as shown Figure 8-139
Go back to the Virtual Servers and Hosts view and check that our virtual server is hosted by another KVM member of the system pool as shown in Figure 8-140.
353
Managing_KVM_FSM.fm
354
Managing_PowerVM_FSM.fm
Chapter 9.
355
Managing_PowerVM_FSM.fm
The diagram in Figure 9-1shows relationships between PowerVM infrastructure components and Flex System Manager. Blue boxes represent physical compute nodes. Purple box stands for Storwize V7000 and storage pools defined on it. Green boxes are I/O modules in the chassis (10 GbE switch, 8 Gb FC Pass-thru module and external 8 Gb FC SAN switch). A Flex System Manager node box describes components that are needed for PowerVM implementation. A p260 compute node box represents LPARs, FSP and SEA.
356
Managing_PowerVM_FSM.fm
First, install a VIOS on the p260 compute node. If you want more information on how to implement p260, p460 compute node, see IBM Flex System p260 and p460 Planning and Implementation Guide. http://www.redbooks.ibm.com/redpieces/abstracts/sg247989.html?Open
357
Managing_PowerVM_FSM.fm
There are two options to install VIOS in the p260 compute node for the first time. 1. First, install VIOS using DVD through supported USB optical DVD drive which connected to the p260 front panel as shown in Figure 9-3 on page 358.
Figure 9-3 Front panel of the IBM Flex System p260 compute node
2. Second, use NIM method. Note: This option is only for a NIM server already existing at the site. Since we do not have a NIM in our infrastructure yet, we will be using the first method to install VIOS.
358
Managing_PowerVM_FSM.fm
Click Manage Power Systems Resources in the menu located at the far left of chassis graphical view as shown in Figure 9-5 on page 359.
If you discover a p260 compute node and collect inventory for the p260 compute node in a proper manner, you will see physical p260 compute node. Note: If you do not see any compute node in the chassis, please go to Chapter 6.1, FSM initial setup on page 114. Right click on the discovered compute node, go to System Configuration, then select Create Virtual Server (see Figure 9-6).
Figure 9-6 Manage Power Systems Resources main page Chapter 9. Managing PowerVM environment with IBM Flex System Manager
359
Managing_PowerVM_FSM.fm
Create VIOS profile depending on your system requirements. At this time, type VIOS name, as seen in Figure 9-7.
Note: VIOS ID number should be 1 except using for full partition purpose. Define VIOS memory size, as shown in Figure 9-8.
360
Managing_PowerVM_FSM.fm
Define how many processors are used for VIOS, as shown in Figure 9-9 on page 361.
Define virtual ethernet adapter for Shared Ethernet Adapter, as shown in Figure 9-10.
361
Managing_PowerVM_FSM.fm
At this time, we create one virtual ethernet adapter for Shared Ethernet Adapter and assign priority 1 to the VIOS, as shown in Figure 9-11 on page 362.
Note: If you have a plan to set up dual VIOS or Live Partition Mobility, refer to the following documentation: IBM PowerVM Virtualization Introduction and Configuration, SG24-7940 http://www.redbooks.ibm.com/abstracts/sg247940.html?Open IBM PowerVM Live Partition Mobility, SG24-7460 http://www.redbooks.ibm.com/abstracts/sg247460.html?Open
362
Managing_PowerVM_FSM.fm
Now, we are going to create an adapter for virtual SCSI, as shown in Figure 9-13 on page 363.
363
Managing_PowerVM_FSM.fm
Define connecting VIOC ID and a adapter ID, as shown in Figure 9-14. After entering parameters for virtual storage adapters, click OK.
You can see created virtual scsi adapter in the Virtual Storage Adapters pane, as shown in Figure 9-15 on page 364. If you need to create more virtual storage adapters, click Add.
364
Managing_PowerVM_FSM.fm
Define physical I/O adapters, as seen in Figure 9-16. At this time we assigned all physical adapters to the VIOS.
Right click on the created VIOS, select Operations Activate Profile, as seen in Figure 9-18 on page 365.
365
Managing_PowerVM_FSM.fm
Set Boot mode value to SMS mode, as shown in the Figure 9-20.
Click OK, then terminal console will pop up, as seen in the Figure 9-20. Type Passw0rd, then you can see the SMS mode menu.
366
Managing_PowerVM_FSM.fm
367
Managing_PowerVM_FSM.fm
The next step is to install an AIX image. For more information to implement VIOC, refer to the following publication: IBM PowerVM Virtualization Introduction and Configuration, SG24-7940. http://www.redbooks.ibm.com/abstracts/sg247940.html?Open Note: When installing a VIOC, use a virtual CD-ROM host by VIOS. You can check media device configuration, as shown in Figure 9-26 on page 368. 1. Right click VIOS name System Configuration Manage Virtual Server. Click Media Devices then you will see the current VIOS configuration. 2. You can see which server owns media device. At this time, PF-Node1-NIM has owns the virtual CD-ROM. 3. Description tells you which media assigned to virtual server, for example, CR-ROM.
368
Managing_PowerVM_FSM.fm
There are two partitions, as shown in Figure 9-27. One is VIOS and the other one is for NIM server to deploy AIX OS. Minimum requirement is set to deploy PowerVM virtual machine by using VMControl.
369
Managing_PowerVM_FSM.fm
VIOS
NIM
mksysb
VM1
System Pool
DB2
Click Plug-ins tab on the Flex System Manager home page, as shown in Figure 9-29.
Click VMControl Enterprise Edition in the Plug-ins page, as shown in Figure 9-30.
Note: If you do not see the VMControl feature in the Plug-ins page, check whether this feature is enabled or not.
370
Managing_PowerVM_FSM.fm
Click Virtual Appliances tabs, then you can see the status of managed virtual appliances from virtual machines deployment perspective, as shown in Figure 9-31 on page 371.
3
Figure 9-31 Virtual Appliances tab
1. What to deploy: This menu shows ready-to-use virtual appliances in your data center for example, Lpp_source capture or mksysb capture, etc. When we finish this task, 0 Virtual appliances will change to 1 Virtual appliances. 2. Where to deploy: When you are deploying a virtual machine, you should choose one of these two options: virtual server itself or server system pools which are normally physical servers. 3. What to capture: This menu shows the partitions that are going to be gold images. 4. Where to store: This menu shows all image repositories that VMControl has.
371
Managing_PowerVM_FSM.fm
First step is to discover virtual machine to be captured. Check Where to deploy menu in the Virtual Appliances tab after this step. Click Discover virtual appliances, as shown in Figure 9-32.
Note: If there is no image, you will see this information. If you want to add more virtual appliances, click Discover virtual appliances in the Virtualization tasks box, as shown in Figure 9-32. Choose the Chassis that you want to discover, then click Add, as seen in the Figure 9-33 on page 372. Note: Normally choose virtual appliance that you are to discover. Discovering the Chassis is the only initial step or there is no image in the Chassis.
372
Managing_PowerVM_FSM.fm
You can see three virtual servers and two hosts after discovering virtual appliances, as shown in Figure 9-34.
Figure 9-34 Three virtual servers and two hosts are discovered
Collect inventory for the physical server and the VIO Server as shown in Figure 9-35 on page 373.
373
Managing_PowerVM_FSM.fm
Note that four virtual servers have been added, as shown in Figure 9-37 on page 374.
Figure 9-37 Four virtual Power servers in the Resource Explorer menu
374
Managing_PowerVM_FSM.fm
Six virtual servers in total have been added, as shown in Figure 9-38.
Second step is Creating a VMControl Repository using NIM. The listed steps are needed. 1. You can manage AIX mksysb or lpp_source images 2. Must be configured as a NIM master system nim_master_setup AIX 7.1 or later (recommended) Filesets: dsm.core (not installed as part of default fileset) openssh.base.client openssl.base
3. IBM Flex System Manager common agent must be installed 4. VMControl NIM subagent must be installed 5. NIM master must be discovered, accessed and inventoried by IBM Flex System Manager 6. Once /export/nim is created make sure it is large enough to hold appliances
375
Managing_PowerVM_FSM.fm
Make sure you have the SystemMgmtClient bundle installed on the NIM Server, as shown in Figure 9-39.
Ensure openssh and openssl are installed and ssh is started on the NIM server, as shown in Figure 9-40.
376
Managing_PowerVM_FSM.fm
Discover the NIM Server using its IP address, as shown in Figure 9-41. Note: This step is prerequisite to deploy VMControl agent on the NM server from FSM.
377
Managing_PowerVM_FSM.fm
Click
378
Managing_PowerVM_FSM.fm
Enter the root password for your NIM server, as shown in Figure 9-45 on page 379.
Type USERID/Password
379
Managing_PowerVM_FSM.fm
Select the NIM Server you want to discover then press Add, as shown in Figure 9-48.
Now you can deploy VMControl agent on the NIM server. Next steps will show how to install VMControl agent on the NIM server. Click Install Agents, as shown in Figure 9-49.
380
Managing_PowerVM_FSM.fm
Select the agent for NIM server then press Add, as shown in Figure 9-52.
381
Managing_PowerVM_FSM.fm
Select the NIM server for discovery, then press Add, as shown in Figure 9-53.
Verify the information then select Finish to install the agent for NIM, as shown in Figure 9-54.
382
Managing_PowerVM_FSM.fm
Click Finish button, then you see pop up menu for the installation task, as shown in Figure 9-55 on page 383. Click OK.
383
Managing_PowerVM_FSM.fm
The server object must appear for the NIM server. Now run Inventory task against both objects, as shown in Figure 9-58.
Figure 9-58 Check NIM server status in the Resource Explorer menu
384
Managing_PowerVM_FSM.fm
Next step is to create NIM repository that VMControl can manage. Click Create Image repository, as shown in Figure 9-59 on page 385.
Select the NIM Server to use as the Repository, as shown in Figure 9-60.
385
Managing_PowerVM_FSM.fm
The new NIM repository has been created. Click the Image repositories link for more information about this repository, as shown in Figure 9-61.
Prerequisite steps have finished to capture virtual server. We describe two capture methods for the NIM: Create LPP_source base Capture mksysb base
386
Managing_PowerVM_FSM.fm
VIOS
NIM
LPP_source
DB2
These are overall steps for LPP_source base capture. 1. Make LPP_souce file from AIX CD/DVD on the NIM server. 2. Check all related servers should be seen in FSM, if not, discover the specific object, then run Collect Inventory task. 3. Put LPP_source file together with OVF format using captureva command. The following commands take an existing lpp_source from the NIM server and make it into a virtual appliance, as shown in Figure 9-64. This function can not be completed from the GUI.
Use the lsrepos command to list repositories: Display all repositories: smcli lsrepos -v Display OID: smcli lsrepos -o Use the captureva command to capture a virtual appliance: Capture a virtual appliance from a virtual server: smcli captureva -v -s 123 -r 345 -n "XYZLpar" -D "Production server"
387
Managing_PowerVM_FSM.fm
Capture a virtual appliance from existing lpp_source with setting CPU and memory size: smcli captureva -r 20609 -F repos:lpp_source_6100 -n"AIX_Lppsource" -A "cpushare=1,memsize=8192" Click What to deploy page or the Virtual Appliances tab, then you see the newly created virtual appliance, as shown in Figure 9-65.
388
Managing_PowerVM_FSM.fm
Select Capture in the Virtual Appliances tab, as shown in Figure 9-66 on page 389.
389
Managing_PowerVM_FSM.fm
Type virtual appliance name, as shown in Figure 9-68 on page 390. We typed AIX-6100-mksysb.
390
Managing_PowerVM_FSM.fm
Select repository as shown in Figure 9-71. Repository is where you want to store the image that is associated with the new virtual appliance.
Figure 9-72 on page 391 shows selecting Network. We just created one SEA, so only one network is shown in this screenshot. If more than one SEA exist, you should select a network that you use.
391
Managing_PowerVM_FSM.fm
Figure 9-73 shows version control page. Normally, mksysb based capture is based on a source which is already running an AIX image. So, the wizard selects Set the version based on the virtual appliance from which the virtual server was originally deployed: Capture_AIX_SCS by default.
392
Managing_PowerVM_FSM.fm
393
Managing_PowerVM_FSM.fm
VIOS
VM
DB2
These are overall steps for SCS base capture: 1. Hardware preparation 394
Implementing Systems Management of IBM PureFlex System
Managing_PowerVM_FSM.fm
a. Storage configuration b. Fabric zoning c. Installation/configuration of VIOS on Power servers 2. SMI-S provider check step a. Configuration of SMI-S provider for the SAN switch (if needed) 3. Management check step a. VMControl b. Storage Control 4. Infrastructure discovery a. Discovery of server infrastructure: Managed Power Servers b. Discovery of storage infrastructure: V7000, SAN fabric c. Discovery of VIOS 5. Configure image repository and system pool a. Deploy Common Agent VMControl Subagent b. Image repository, system pool creation 6. Preparation for capture a. Installation of activation engine b. Enable activation engine 7. Functional test from FSM console
395
Managing_PowerVM_FSM.fm
Check related resources exist in All systems page, as shown in Figure 9-81. In our environment, there are three storage related components: Storwize V7000, FC3171 SAN pass through, and IBM B80 main SAN switch.
396
Managing_PowerVM_FSM.fm
Check ssh in the Remote Service Access Point (RASP) configuration as shown in Figure 9-82.
SSH access should be seen in the Access column, as shown in Figure 9-83.
If you want to know how to add Storwize V7000 and 3rd party SAN switch, go to 6.13, Discover and manage V7000 (Storage Control) on page 205.
SCS configuration
Check auto start setting of Common Agent fileset, as shown in Figure 9-84.
Note: VIOS OS image has Common Agent file by default. Discover VIOS and update VIOS information in the FSM: Left navigation pane Inventory System Discovery
397
Managing_PowerVM_FSM.fm
Right click discovered system in the Resource Explorer, then click Configure Access. Check CAS, CIM, SSH protocols are seen, as shown in Figure 9-85. Click Request Access, then enter proper credentials.
398
Managing_PowerVM_FSM.fm
Install agent
Click Install agents as shown in Figure 9-87.
399
Managing_PowerVM_FSM.fm
400
Managing_PowerVM_FSM.fm
401
Managing_PowerVM_FSM.fm
402
Managing_PowerVM_FSM.fm
Select VIOS as shown in Figure 9-97. In case of AIX deployment using SCS, newly created LUN is allocated to the VIOS and VIOS assigns this LUN to the new virtual server using vscsi mapping.
403
Managing_PowerVM_FSM.fm
Select a target storage pool as shown in Figure 9-98 on page 404. Whenever you request to create new virtual server, FSM will create a LUN in the storage pool and allocate it to VIOS.
404
Managing_PowerVM_FSM.fm
When Launch Job page pops up, click OK. Then check log as shown in Figure 9-100 on page 405.
405
Managing_PowerVM_FSM.fm
406
Managing_PowerVM_FSM.fm
Select a physical system that you use as a pool as shown in Figure 9-105 on page 407.
Select a storage pool which you use as shown in Figure 9-106. If you define more storage pools, you will see more storage pools in this page.
407
Managing_PowerVM_FSM.fm
When you deploy a new virtual sever in the server system pool, FSM deploys server on proper physical server automatically if you select Allow optimization to occur automatically, as shown in Figure 9-108.
408
Managing_PowerVM_FSM.fm
Note: You can run only specific commands in Flex System Manager. Extract the content of the .tar file as shown in Figure 9-112.
409
Managing_PowerVM_FSM.fm
Check the files as shown in Figure 9-113 on page 410. For AIX, ensure the JAVA_HOME environment variable is set and points at a Java Runtime Environment (JRE).
Prepare the virtual server to be captured by running the AE.sh --reset command as shown in Figure 9-115.
410
Managing_PowerVM_FSM.fm
Note: If you have previously captured the virtual server and want to capture it again, run the following commands: rm /opt/ibm/ae/AP/* cp /opt/ibm/ae/AS/vmc-network-restore/resetenv /opt/ibm/ae/AP/ovf-env.xml Virtual server shutdowns automatically as shown in Figure 9-116.
411
Managing_PowerVM_FSM.fm
Select a source virtual server as shown in Figure 9-119. Storwize V7000 runs a flashcopy command for the LUN on a virtual server that you select. Choose Virtual Server, then click Next.
412
Managing_PowerVM_FSM.fm
Select version as shown in Figure 9-123. After that, you will see another version added.
413
Managing_PowerVM_FSM.fm
Figure 9-125 shows pop up menu for launching jobs. Click OK.
414
Managing_PowerVM_FSM.fm
415
Managing_PowerVM_FSM.fm
416
Managing_PowerVM_FSM.fm
Choose a target on which LPP_source will be deployed as shown in Figure 9-130. It can be a physical server or a partition.
417
Managing_PowerVM_FSM.fm
Figure 9-132 shows storage mapping. You can choose Storage volume or Storage pool. Disk size of 9,537 MB needs to be deployed.
Assign disk to a new virtual server from VIOS rootvg storage pool as shown in Figure 9-133.
Note: There are three way to allocate disk to virtual server through VMControl: lv from vg (one of storage pool type) LUN is already assigned to VIOS by storage subsystem LUN is allocated to VIOS upon request using SMI-S (another storage pool type)
418
Managing_PowerVM_FSM.fm
419
Managing_PowerVM_FSM.fm
420
Managing_PowerVM_FSM.fm
Check virtual server in the Resource Explorer pane, as shown in Figure 9-139.
Discover newly deployed virtual server as shown in Figure 9-140. You should discover virtual server and collect inventory in the Resource Explorer pane even if you can see the virtual server in the Virtual Servers and Hosts tab in VMControl. Then click No Access link to get an access to the newly discovered server.
Enter credentials for virtual server and click Request Access as shown in Figure 9-141.
421
Managing_PowerVM_FSM.fm
Figure 9-142 shows that the request access task is completed successfully.
422
Managing_PowerVM_FSM.fm
Select a target where youll deploy this mksysb image as shown in Figure 9-144.
423
Managing_PowerVM_FSM.fm
Click Finish, then click OK on the Launch Job page. Figure 9-148 shows newly deployed virtual machine through mksysb virtual appliance.
424
Managing_PowerVM_FSM.fm
425
Managing_PowerVM_FSM.fm
Select virtual appliance as shown in Figure 9-151. Captured _AIX_SCS is an image created by V7000 flashcopy feature.
426
Managing_PowerVM_FSM.fm
427
Managing_PowerVM_FSM.fm
428
Managing_PowerVM_FSM.fm
Manual relocation
You can choose to relocate one or more virtual servers from an existing host at any time. When you relocate virtual servers within server system pools, the relocation target is automatically identified.
Automatic relocation
VMControl server system pools can predict hardware failure problems and relocate virtual servers to maintain resilience. However, you might also want to monitor and adjust resources within your server system pool. For example, you might want to monitor the hosts in your server system pool for high CPU utilization. To do this, you can activate a threshold to monitor high and low values for CPU utilization in your workloads. Then, if the threshold is reached, a message is displayed in the Server system pools dashboard, and in the Problems view.
429
Managing_PowerVM_FSM.fm
VM1
VIOS01
VIOS03
Storwize V7000
Figure 9-160 shows physical compute nodes. In our environment, we used p260 (PF-PowerVM-Node2) and p460 (Server-7895-42x) for virtual server relocation.
-
430
Managing_PowerVM_FSM.fm
This section describes some important steps that you need to follow to set up virtual server relocation (Live Partition Mobility). If you want to know more about Live Partition Mobility, refer to IBM PowerVM Live Partition Mobility, SG24-7460 at: http://www.redbooks.ibm.com/abstracts/sg247460.html?Open Click Manage Virtual Server to check VIOS profile settings as shown in Figure 9-161.
431
Managing_PowerVM_FSM.fm
Mover service check box should be checked to perform Live Partition Mobility as shown in Figure 9-162.
432
Managing_PowerVM_FSM.fm
When you create VIOS pair to perform Live Partition Mobility, priorities for Shared Ethernet Adapters should be different as shown in Figure 9-163.
Figure 9-164 shows virtual scsi configuration. Live Partition Mobility virtual server is AIX SCS. AIX SCS partition has vhost4 as vscsi in VIOS environment.
433
Managing_PowerVM_FSM.fm
Figure 9-165 on page 434 shows disk allocation information in VIOS environment.
Shared disk drives on VIO Servers must have Reserve policy set to no_reserve as shown in Figure 9-166.
434
Managing_PowerVM_FSM.fm
Figure 9-168 shows migration wizard. Click Finish after checking summary, you can observe relocation of virtual server.
435
Managing_PowerVM_FSM.fm
436
Managing_VMware_FSM.fm
10
Chapter 10.
437
Managing_VMware_FSM.fm
IP network
VM Network
VM Network
PF-ESXi-Node1
PF-ESXi-Node2
vMotion
Management
vMotion
PF-vCenter01
PF-Windows1
vm001
vm002
PF-ESXi01
PF-ESXi02
Cluster1
SAN
Management
Ethernet Fiber Channel
LUN1
LUN2
LUN3
Storwize V7000
We used two physical X-Architecture compute nodes in our PureFlex Chassis to setup a small vSphere 5 cluster with vCenter running in a virtual machine on the first node. Shared SAN storage is provided by Storwize V7000. Simple VM Network and vMotion network are configured for the hosts. FSM eth1 has network connectivity to vCenter. See Table 10-1 for more information on each component.
Table 10-1 VMware environment components Component Hosts Description 2 ESXi 5.0 hosts. Compute node PF-ESXi-Node1 runs ESXi with hostname PF-ESXi01. Compute node PF-ESXi-Node2 runs ESXi with hostname PF-ESXi02. 2 VMware virtual machines version 8 - vm001 and vm002. Both running Windows 2008 R2 as Guest OS. Both hosted by PF-ESXi-Node1. vm001 has hostname PF-vCenter01 and runs vCenter Server application. vm002 has hostname PF-Windows1. 1 VMware vCenter Server 5.0 is running in a virtual machine vm001 which is hosted by PF-ESX01. It manages both PF-ESXi01 and PF-ESXi02.
Virtual Machines
vCenter Server
438
Managing_VMware_FSM.fm
Description 1 datacenter - Datacenter1 includes 1 cluster - Cluster1. Cluster1 has 2 member hosts - PF-ESXi01 and PF-ESXi02. Cluster1 does not have VMware High Availability (HA) or Distributed Resource Scheduler (DRS) enabled. Each host has 1 vSwitch which has: 1 Virtual Machine portgroup VM Network, 1 vMotion VMkernel port and 1 Management port. vMotion network is configured using non-routable network. The 2 virtual machines, 2 management ports and FSM eth1 are within the same network. Each vSwitch has 1 10Gbit uplink. Each host is connected via 8Gbit interface through the SAN fabric to Storwize V7000. 3x 100GB LUNs are zoned and mapped to both hosts. All 3 LUNs are formatted with VMFS5 and are used to store vm001, vm002 and future virtual machine files.
Network
Storage
Note: Running vCenter Server in a virtual machine is a best practice. Some of the benefits of running vCenter in a virtual machine include: easy live migration between physical hosts, easy backup, protection by VMware HA, easy to resize its allocated resources, reduced costs by eliminating the need for a dedicated physical host. For more information on planning for VMware, refer to 5.2.4, Planning for VMware virtualization on page 107. Once we setup the environment, we discovered the vCenter operating system endpoint via FSM and requested access using Administrator local user. The Administrator user has full vCenter privileges. All ESXi hosts are discovered automatically after the vCenter compute node is accessed by FSM. Refer to 6.8, Operating system discovery, access and inventory on page 184 for more information on discovery of OS. Now that we have our initial VMware environment, let us start with creating a new virtual server, see 10.2, Deploy a VM on page 440.
Chapter 10. Managing VMware environment with IBM Flex System Manager
439
Managing_VMware_FSM.fm
10.2 Deploy a VM
In the IBM Flex System Manager Web interface navigation area, expand Inventory and click Virtual Servers and Hosts, as shown in Figure 10-2.
Select the first ESXi node and navigate to Actions System Configuration Create Virtual Server, as shown in Figure 10-3 on page 440.
Figure 10-3 Create Virtual Server Actions menu for selected ESXi host
440
Managing_VMware_FSM.fm
Click Next on the Welcome page (see Figure 10-4 on page 441).
Chapter 10. Managing VMware environment with IBM Flex System Manager
441
Managing_VMware_FSM.fm
Specify a name for the virtual server you want to create, as shown in Figure 10-5 on page 442. Type vm003 and click Next.
442
Managing_VMware_FSM.fm
Select the Guest Operation System you are planning to install on this virtual server, in this case Windows 2008 R2 (see Figure 10-6 on page 443). Click Next.
Chapter 10. Managing VMware environment with IBM Flex System Manager
443
Managing_VMware_FSM.fm
Specify a number of virtual CPUs to assign to the virtual server. Type 2 and click Next, see Figure 10-7 on page 444.
444
Managing_VMware_FSM.fm
Specify the amount of memory to assign to this virtual server in MB (see Figure 10-8 on page 445). Type 2048 and click Next.
Open the Volume label drop-down list to select a datastore where to store the virtual machine files. You will be listed with all datastores visible by the ESXi host you selected initially. Make sure you select a shared datastore in order to take advantage of cluster
Chapter 10. Managing VMware environment with IBM Flex System Manager
445
Managing_VMware_FSM.fm
features. Specify a virtual disk size in GB. The wizard will create one thick lazy zeroed dependant virtual disk with the size you specify. Enter 40 and click Next (Figure 10-9 on page 446).
446
Managing_VMware_FSM.fm
Select a Virtual Machine port group from the Network Label drop-down list. Select VM Network and click Next (Figure 10-10 on page 447). The wizard configures the virtual machine with one virtual network card connected to the port group you have selected.
Chapter 10. Managing VMware environment with IBM Flex System Manager
447
Managing_VMware_FSM.fm
Review the Summary page and click Finish (Figure 10-11 on page 448).
448
Managing_VMware_FSM.fm
Click OK in the Launch Job window to launch the virtual server creation immediately, see Figure 10-12 on page 449.
Click Display Properties in the Create Virtual Server job message box to see the job status (see Figure 10-13).
Chapter 10. Managing VMware environment with IBM Flex System Manager
449
Managing_VMware_FSM.fm
Ensure the Create Virtual Server job completed successfully (Figure 10-14 on page 450) and close the Active and Scheduled Jobs tab.
Return to the Virtual Servers and Hosts page to see the newly created virtual server vm003. It is currently in Stopped state, as seen in Figure 10-15. The virtual machine was created on the ESXi host PF-ESXi01 which is managed by the vCenter server PF-vCenter01. Click on the Information link on the PF-ESXi-Node1 row to open the list of events for that ESXi server.
450
Managing_VMware_FSM.fm
Informational event regarding the virtual server creation appears, as shown in Figure 10-16. Similar informational event will appear also under PF-vCenter01, because the virtual server was created on a host managed by PF-vCenter01.
If you need to delete the informational event, select it and click Actions Delete, as shown in Figure 10-17.
Figure 10-17 Delete menu item for selected event in Problems page
Chapter 10. Managing VMware environment with IBM Flex System Manager
451
Managing_VMware_FSM.fm
Return to the Virtual Servers and Hosts view to power on the newly created virtual server. Select vm003, click Actions Power On/Off Power On, as shown in Figure 10-18 on page 452.
Figure 10-18 Power On menu item for selected virtual server in Virtual Servers and Hosts page
452
Managing_VMware_FSM.fm
Chapter 10. Managing VMware environment with IBM Flex System Manager
453
Managing_VMware_FSM.fm
The virtual server State changes to Started in Virtual Servers and Hosts view, as shown in Figure 10-20.
Figure 10-20 Virtual Servers and Hosts page showing Started virtual server
FSM creates a virtual server without any Guest OS installed. Normally, this task would be performed by an enterprise administrator who is managing the entire chassis via FSM and has full privileges to create a virtual server. At this point a junior administrator with Virtual Machine User privileges in vCenter can connect to the Virtual Machine console via vSphere client and proceed with the Guest OS installation. In the next section, we will relocate the newly created virtual server to the second host while the virtual server is running.
454
Managing_VMware_FSM.fm
10.3 Relocate a VM
Select the virtual server you want to relocate to another host (in our case vm003), click Actions Availability Relocate as shown in Figure 10-21 on page 455.
Figure 10-21 Relocate menu item for selected virtual server in Virtual Servers and Hosts page
Verify the virtual machine name and click Next, as shown in Figure 10-22 on page 455.
Figure 10-22 Relocate wizard Welcome page Chapter 10. Managing VMware environment with IBM Flex System Manager
455
Managing_VMware_FSM.fm
Select the target host for the virtual machine or select Relocate by CPU utilization if you want the virtual server to be moved to the host with lowest CPU utilization. Select PF-ESXi-Node2, as shown in Figure 10-23.
You can save the plan for relocation in order to run it again or use it at a later time if needed. Select Relocate only and click Next as shown in Figure 10-24 on page 456.
456
Managing_VMware_FSM.fm
Verify the relocation Summary and click Finish (see Figure 10-25).
The virtual server Status in Virtual Servers and Hosts page changes to Relocating during the relocation from PF-ESXi01 to PF-ESXi02, see Figure 10-26 on page 457.
Figure 10-26 Virtual Servers and Hosts page showing a virtual server in Relocating State
Chapter 10. Managing VMware environment with IBM Flex System Manager
457
Managing_VMware_FSM.fm
Return to the Virtual Servers and Hosts page in FSM. The virtual machine vm003 is now listed under FP-ESXi02 and it is in state Started. See Figure 10-27.
Figure 10-27 Virtual Servers and Hosts page showing migrated virtual server
In some cases you might need to relocate all virtual servers away from a specific host in order to perform some service tasks. In the next section we will relocate all VMs from a host and we will save a relocation plan, which can be run later or used in an automation plan.
458
Managing_VMware_FSM.fm
10.4 Relocate all VMs from a host and save a relocation plan
For the purpose of this demonstration we moved vm003 back to PF-ESXi-Node1. Instead of going through the Actions menu, you can just right-click on the host (PF-ESXi-Node1) and then select Availability Relocate Virtual Servers, as shown in Figure 10-28.
Figure 10-28 Relocate Virtual Servers menu item for selected host in Virtual Servers and Hosts page
Verify the source host and click Next, as shown in Figure 10-29 on page 459. If you need to, you may select Put host in maintenance mode after all virtual servers are relocated.
Figure 10-29 Relocate wizard Source page Chapter 10. Managing VMware environment with IBM Flex System Manager
459
Managing_VMware_FSM.fm
You can select a specific Target host or choose Relocate by CPU utilization. Select PF-ESXi-Node2 and click Next, see Figure 10-30.
Select Relocate and save plan and provide a descriptive Relocation plan name, as shown in Figure 10-31.
460
Managing_VMware_FSM.fm
Review the Summary page and click Finish, see Figure 10-32.
Click OK to launch the relocation job immediately and observe the Virtual Servers and Hosts page to ensure all virtual machines from PF-ESXi01 relocate to PF-ESXi02, as shown in Figure 10-33.
Chapter 10. Managing VMware environment with IBM Flex System Manager
461
Managing_VMware_FSM.fm
In the IBM Flex System Manager Web interface navigation area, expand Availability and click Relocation Plans for Farms, as shown in Figure 10-34 on page 462. In this page you can View, Run and manage all relocation plans for farms.
Changing the resource allocation for a virtual server is another task which is often in responsibility of a full administrator. In the next section we will modify memory allocation of a virtual server.
462
Managing_VMware_FSM.fm
Figure 10-35 Shut down and power off menu item on Virtual Servers and Hosts page
Chapter 10. Managing VMware environment with IBM Flex System Manager
463
Managing_VMware_FSM.fm
Click OK on the launch job window to run the job immediately, see Figure 10-36 on page 464.
Figure 10-36 Shut down and power off Launch Job window
464
Managing_VMware_FSM.fm
Return to Virtual Servers and Hosts page, right-click the powered off vm002 and select System Configuration Edit Virtual Server, as shown in Figure 10-37 on page 465.
Figure 10-37 Edit Virtual Server menu item in Virtual Servers and Hosts page
Chapter 10. Managing VMware environment with IBM Flex System Manager
465
Managing_VMware_FSM.fm
Edit Virtual Server window opens. Click the Memory tab, as shown in Figure 10-38 on page 466.
Observe the current memory assigned to the virtual server, as seen in Figure 10-39 on page 466.
Change the assigned memory value from 6144 to 8192 to increase the virtual server memory to 8GB. See Figure 10-40 on page 467. Click OK to apply the new configuration.
466
Managing_VMware_FSM.fm
Right-click vm002 and power it on by selecting Power On/Off Power On. See Figure 10-41 on page 467.
Figure 10-41 Power On menu item in Virtual Servers and Hosts page
So far we discussed virtual server tasks. In the next section we will change the configuration of our VMware cluster.
Chapter 10. Managing VMware environment with IBM Flex System Manager
467
Managing_VMware_FSM.fm
Note: A platform manager manages one or more host systems and their associated virtual servers and operating systems. VMware vCenter Server is a platform manager.
468
Managing_VMware_FSM.fm
Right-click Cluster1 and select Availability Edit Virtual Farm, as shown in Figure 10-43.
Figure 10-43 Edit Virtual Farm menu item in Platform Managers and Members page
Click Next on the Welcome page, as shown in Figure 10-44 on page 469.
Chapter 10. Managing VMware environment with IBM Flex System Manager
469
Managing_VMware_FSM.fm
Verify the cluster name and click Next, as shown in Figure 10-45.
Select VMware Distributed Resource Scheduler (DRS) and leave VMotion rate as Normal, as shown in Figure 10-46 on page 470. Click Next.
Review the Summary page and click Finish, as shown in Figure 10-47.
470
Managing_VMware_FSM.fm
In some cases the FSM administrator might spot a critical problem on a compute node and will need to perform maintenance on it. In the next section we will demonstrate how to place a VMware host in maintenance mode.
Chapter 10. Managing VMware environment with IBM Flex System Manager
471
Managing_VMware_FSM.fm
Return to Virtual Servers and Hosts page and select PF-ESXi-Node2. Select Actions Availability Enter Maintenance Mode, as shown in Figure 10-48 on page 472.
Figure 10-48 Enter Maintenance Mode menu item in Virtual Servers and Hosts page
472
Managing_VMware_FSM.fm
Return to Virtual Servers and Hosts page and observe that all virtual servers are now running on PF-ESXi01 (see Figure 10-49).
Chapter 10. Managing VMware environment with IBM Flex System Manager
473
Managing_VMware_FSM.fm
Select PF-ESXi-Node2 and click Actions Availability Exit Maintenance Mode, as shown in Figure 10-50.
Figure 10-50 Exit Maintenance Mode menu item in Virtual Servers and Hosts page
474
Managing_VMware_FSM.fm
Click OK to launch the job immediately, as shown in Figure 10-51 on page 475.
Before continuing with our event automation scenario, let us quickly review another option we have in FSM to view and manage our virtual infrastructure.
Chapter 10. Managing VMware environment with IBM Flex System Manager
475
Managing_VMware_FSM.fm
In the IBM Flex System Manager Web interface navigation area, expand Inventory and Views and click Platform Managers and Members, as shown in Figure 10-52. Select the vCenter server PF-vCenter01 which is installed in virtual machine vm001.
476
Managing_VMware_FSM.fm
Select Actions Topology Perspectives Virtualization Basic, as shown in Figure 10-53 on page 477.
Figure 10-53 Virtualization Basic menu item in Platform Managers and Members page
Chapter 10. Managing VMware environment with IBM Flex System Manager
477
Managing_VMware_FSM.fm
Click the Cluster1 icon and click the maximize button of the Details window, as shown in Figure 10-54 on page 478.
478
Managing_VMware_FSM.fm
The details for the selected object appear as shown in Figure 10-55 on page 479.
Chapter 10. Managing VMware environment with IBM Flex System Manager
479
Managing_VMware_FSM.fm
Click the Hide Palette View and Zoom To Fit buttons to get a full diagram of the base components of your virtual infrastructure. Right-click on any component to get the usual Actions menu relevant to the selected component, as shown in Figure 10-56 on page 480.
Note: Click Actions Layout Tree to change the default Radial layout if it does not suit your purposes.
480
Managing_VMware_FSM.fm
Chapter 10. Managing VMware environment with IBM Flex System Manager
481
Managing_VMware_FSM.fm
Click Next on the Create Event Automation Plan Wizard Welcome page, as shown in Figure 10-58 on page 482.
482
Managing_VMware_FSM.fm
Type a Name and Description for the automation plan, as shown in Figure 10-59 on page 483.
Figure 10-59 Create Event Automation Plan Wizard Name and Description page
Chapter 10. Managing VMware environment with IBM Flex System Manager
483
Managing_VMware_FSM.fm
On the Targets page, select the systems that will be affected by the event automation plan. Select the two ESXi servers, as shown in Figure 10-60 on page 484 and click Add. Click Next to proceed.
484
Managing_VMware_FSM.fm
Select Advanced Event Filters from the Events drop-down list. Select Critical Events from the Event Filters list to process all events that have a Critical severity (see Figure 10-61 on page 485). Note: If needed, at this point you can also select Hardware Predictive Failure Alerts event filter. For the purpose of our exercise, we will filter all Critical events.
Chapter 10. Managing VMware environment with IBM Flex System Manager
485
Managing_VMware_FSM.fm
Click Create to create a new event action, as shown in Figure 10-62 on page 486.
Figure 10-62 Create Event Automation Plan Wizard Event Actions page
Move to page 2 of the actions list and select Start a task on a system that generated the event, as shown in Figure 10-63. Click OK.
486
Managing_VMware_FSM.fm
Enter an Action name and Description for the event action and select Enter Maintenance Mode from the Select a task to run drop-down list, as shown in Figure 10-64. Get familiar with the broad choice of tasks you can run as an action. Click OK.
Select the newly created Enter maintenance mode event action, as shown in Figure 10-65. Click Next.
Figure 10-65 Create Event Automation Plan Wizard Event Actions page
Chapter 10. Managing VMware environment with IBM Flex System Manager
487
Managing_VMware_FSM.fm
Figure 10-66 Create Event Automation Plan Wizard Time Range page
Review the Summary page and click Finish to create and apply the event automation plan, as shown in Figure 10-67 on page 488.
488
Managing_VMware_FSM.fm
The newly created event automation plan appears on the Event Automation Plans page, as shown in Figure 10-68.
For the purpose of testing the event automation plan, we generated a Critical System error with source PF-ESXi-Node2. The status of PF-ESXi-Node2 compute node shows Critical on the Chassis Map, as shown in Figure 10-69.
Chapter 10. Managing VMware environment with IBM Flex System Manager
489
Managing_VMware_FSM.fm
The generated error is also listed in PF-ESXi-Node2 Event Log, as shown in Figure 10-70 on page 490.
490
Managing_VMware_FSM.fm
Return to Virtual Servers and Hosts page and ensure that all virtual servers were automatically migrated away form the host with Critical error. See Figure 10-71.
Chapter 10. Managing VMware environment with IBM Flex System Manager
491
Managing_VMware_FSM.fm
Select PF-ESXi-Node2 and click Actions System Status and Health Active Status, as shown in Figure 10-72 on page 492.
492
Managing_VMware_FSM.fm
Observe the Information events describing the actions performed by the event automation plan we configured earlier. See Figure 10-73 on page 493. PF-ESXi-Node2 is now in maintenance mode.
Chapter 10. Managing VMware environment with IBM Flex System Manager
493
Managing_VMware_FSM.fm
Return to Virtual Servers and Hosts page, right-click on PF-ESXi-Node2 and select Availability Exit Maintenance Mode, as shown in Figure 10-74 on page 494.
Figure 10-74 Exit Maintenance Mode menu item in Virtual Servers and Hosts page
494
Managing_Hyper-V_FSM.fm
11
Chapter 11.
495
Managing_Hyper-V_FSM.fm
496
Managing_Hyper-V_FSM.fm
Specify the path to import the agent and click OK, as shown in Figure 11-4.
Chapter 11. Managing Hyper-V environment with IBM Flex System Manager
497
Managing_Hyper-V_FSM.fm
After a couple of time you get a blue information window as shown in Figure 11-5.
Note: You can note that six agents have been imported because six agent where present in the local FSM directory /home/USERID/RemoteAgentInstall
When the job is completed, your access is OK as shown in Figure 11-7 and you can install your common agent imported previously.
498
Managing_Hyper-V_FSM.fm
Chapter 11. Managing Hyper-V environment with IBM Flex System Manager
499
Managing_Hyper-V_FSM.fm
You can see a list of agents, click Next because the Common Agent for Windows is already in the selected list as shown in Figure 11-10, otherwise, add the Common Agent Windows from the Common Agent Packages by clicking Common Agent Packages.
500
Managing_Hyper-V_FSM.fm
Chapter 11. Managing Hyper-V environment with IBM Flex System Manager
501
Managing_Hyper-V_FSM.fm
Go to you Windows 2008 R2 Hyper-V server and check in the programs installed that the Common Agent is present.
502
Managing_Hyper-V_FSM.fm
Right click on your Hyper-V host and select System Configuration Create Virtual Server as shown in Figure 11-16.
Click Next and choose a name for your virtual server as shown in Figure 11-18
Chapter 11. Managing Hyper-V environment with IBM Flex System Manager
503
Managing_Hyper-V_FSM.fm
Click Next and choose the number of processors as shown in Figure 11-19.
Click Next and select your virtual server memory size as shown in Figure 11-20.
Click Next and select your disk size as shown in Figure 11-21.
Click Next and select the virtual switch to which you want to connect your virtual server as shown in Figure 11-22.
504
Managing_Hyper-V_FSM.fm
Click Next and check your virtual server summary configuration as shown in Figure 11-23.
Click Finish then click OK to run you virtual server creation task as shown in Figure 11-24.
You get a blue box information message as shown in Figure 11-25, then click Display Properties and wait till the job is completed as shown in Figure 11-26.
Chapter 11. Managing Hyper-V environment with IBM Flex System Manager
505
Managing_Hyper-V_FSM.fm
Go back to VMControl and select Virtual Servers/Hosts view to check that your virtual server has been created as shown in Figure 11-27.
506
Managing_Hyper-V_FSM.fm
You get information on processor and memory size as shown in Figure 11-29.
Chapter 11. Managing Hyper-V environment with IBM Flex System Manager
507
Managing_Hyper-V_FSM.fm
Right click the server and select Topology Perspective Network Basic as shown in Figure 11-32.
You get a network topology view of your virtual server within the infrastructure as shown in Figure 11-33.
508
8060glos.fm
Glossary
Your glossary term, acronym or abbreviation Term definition Sort term names: highlight rows Table Sort Column1 Sort Term1 Term2 Term3 Term1 definition Term2 definition Term3 definition
509
8060glos.fm
510
8060abrv.fm
511
8060abrv.fm
512
8060bibl.fm
Related publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book.
IBM Redbooks
The following IBM Redbooks publications provide additional information about the topic in this document. Note that some publications referenced in this list might be available in softcopy only. ????full title???????, xxxx-xxxx ????full title???????, SG24-xxxx ????full title???????, REDP-xxxx ????full title???????, TIPS-xxxx You can search for, view, download or order these documents and other Redbooks, Redpapers, Web Docs, draft and additional materials, at the following website: ibm.com/redbooks
Other publications
These publications are also relevant as further information sources: ????full title???????, xxxx-xxxx ????full title???????, xxxx-xxxx ????full title???????, xxxx-xxxx
Online resources
These websites are also relevant as further information sources: Description1 http://????????.???.???/ Description2 http://????????.???.???/ Description3 http://????????.???.???/
513
8060bibl.fm
514
8060IX.fm
Index
Numerics
00D7554 68Y7030 8731 18 90Y4217 90Y4222 90Y4249 90Y9338 94Y9219 94Y9220 95Y1174 95Y1179 18 11 18 18 18 12 19 19 19 19 discovery 130 features 19, 82 hardware 19 importing update files 137 inital setup 114 Java 117 licenses 18 management network 120 networking 21 NTP setup 119 out-of-band management 87 overview 7, 82 part numbers 18 partitions 21 planar 20 Platform Agent 87 power control 118 preload 22 remote control 117 setup 114 software 22 storage 21 system board 20 user accounts 120 wizard 114 foundations 5 FSM See Flex System Manager FSP 14
A
agents 87
B
blades See compute nodes
C
Chassis Management Module connections 12 default IP address 29 factory defaults 12 functions 13 IPv6 29 LEDs 12 ports 12 reset 12 web interface 29 cloud 3 Common Agent 87 compute nodes management 13 overview 7
I
IMMv2 See Integrated Management Module II Integrated Management Module II features 13 overview 13 integrated systems 3 internal management network 10 Internet connection 133 IP addresses 13 Chassis Management Module 29
D
default IP addresses 13
E
Ethernet internal management network 10 expert integrated systems 3 Express, PureFlex System 5
L
LEDs Chassis Management Module 12
M
management 9 See also Chassis Management Module compute nodes 13 FSP 14 I/O modules 15 Integrated Management Module II 13
F
Flex System Manager agents 87 chassis management 130 Common Agent 87 Copyright IBM Corp. 2012. All rights reserved.
515
8060IX.fm
IP addresses 13
O
out-of-band management 87
P
p260 Compute Node FSP 14 p460 Compute Node FSP 14 Platform Agent 87 PureFlex System 45
R
Redbooks website 513 Contact us xi reset the CMM 12
S
Serial-over-LAN 14 storage overview 8 systems management 9 See also Chassis Management Module compute nodes 13 FSP 14 I/O modules 15 Integrated Management Module II 13 IP addresses 13
V
VideoStopped_OutOfRange 117
W
wizards Flex System Manager 114
X
x220 Compute Node Integrated Management Module II 13 x240 Compute Node Integrated Management Module II 13 IPMI compliance 14
516
To determine the spine width of a book, you divide the paper PPI into the number of pages in the book. An example is a 250 page book using Plainfield opaque 50# smooth which has a PPI of 526. Divided 250 by 526 which equals a spine width of .4752". In this case, you would use the .5 spine. Now select the Spine width for the book and hide the others: Special>Conditional Text>Show/Hide>SpineSize(-->Hide:)>Set . Move the changed Conditional text settings to all files in your book by opening the book file with the spine.fm still open and File>Import>Formats the
8060spine.fm
517
To determine the spine width of a book, you divide the paper PPI into the number of pages in the book. An example is a 250 page book using Plainfield opaque 50# smooth which has a PPI of 526. Divided 250 by 526 which equals a spine width of .4752". In this case, you would use the .5 spine. Now select the Spine width for the book and hide the others: Special>Conditional Text>Show/Hide>SpineSize(-->Hide:)>Set . Move the changed Conditional text settings to all files in your book by opening the book file with the spine.fm still open and File>Import>Formats the
8060spine.fm
518
Back cover