sg 248060

Draft Document for Review August 18, 2012 12:15 am SG24-8060-00

ibm.com/redbooks

Front cover

Implementing Systems Management of IBM PureFlex System

Ilya KrutovFrederik Aouizerats

Brandon HarrellMinChul Kim

Stanimir Markov

Explores IBM PureFlex Systemand its management capabilities

Provides planning and deployment considerations

Explains step-by-step implementation instructions

http://www.redbooks.ibm.com/


International Technical Support Organization


July 2012

Draft Document for Review August 18, 2012 12:15 am 8060edno.fm

SG24-8060-00

© 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 ScheduleContract with IBM Corp.

8060edno.fm Draft Document for Review August 18, 2012 12:15 am

First Edition (July 2012)

This edition applies to IBM PureFlex System.

This document was created or updated on August 18, 2012.

Note: Before using this information and the product it supports, read the information in “Notices” on page vii.

Draft Document for Review August 18, 2012 12:15 am 8060TOC.fm

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixThe team who wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixNow you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiStay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Part 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction to IBM PureFlex System and IBM Flex System . . . . . . . . . . . . 31.1 IBM PureFlex System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 IBM PureFlex System capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 IBM Flex System: The building blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.3.1 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3.2 Compute nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3.3 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.4 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.5 Infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2. IBM PureFlex System management devices and appliances . . . . . . . . . . . . 92.1 Management network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Chassis Management Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Compute node management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.3.1 Integrated Management Module II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.2 Flexible service processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.4 I/O modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.5 IBM Flex System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.5.1 Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.5.2 Software features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Part 2. Chassis Management Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 3. Planning for Chassis Management Module-based systems management 273.1 CMM-based management network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2 CMM interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.3 CMM Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.3.1 Security policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.2 User account policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.3 External authentication of certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.4 FoD Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 4. Chassis Management Module operations . . . . . . . . . . . . . . . . . . . . . . . . . . 354.1 Initial deployment of Chassis Management Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.1.1 Connecting to the CMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.1.2 Configuring the CMM through the Initial Setup Wizard . . . . . . . . . . . . . . . . . . . . . 374.1.3 Updating the Chassis Management Module firmware . . . . . . . . . . . . . . . . . . . . . 474.1.4 Preparing for Chassis Management Module redundancy. . . . . . . . . . . . . . . . . . . 514.1.5 Configuring Chassis Management Module’s user authority . . . . . . . . . . . . . . . . . 53

© Copyright IBM Corp. 2012. All rights reserved. iii

8060TOC.fm Draft Document for Review August 18, 2012 12:15 am

4.1.6 Restoring a Chassis Management Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.2 Chassis Management Module management tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.2.1 Monitoring the chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2.2 Monitoring multiple chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.3 Event notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.2.4 Chassis Management Module Features on Demand . . . . . . . . . . . . . . . . . . . . . . 634.2.5 Chassis management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.2.6 Using the Chassis Management Module CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Part 3. IBM Flex System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 5. Planning for IBM Flex System Manager-based systems management . . . 815.1 General planning information on systems management . . . . . . . . . . . . . . . . . . . . . . . . 82

5.1.1 FSM network integration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.1.2 Planning for security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835.1.3 Planning for FoD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.1.4 Agents and tasks supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875.1.5 Planning for managing the networking infrastructure . . . . . . . . . . . . . . . . . . . . . . 885.1.6 Planning for managing the storage infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . 895.1.7 Planning for IBM Fabric Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

5.2 Planning for managing the virtualization environment with Flex System Manager . . . . 925.2.1 Virtualization and task supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925.2.2 Planning for KVM virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945.2.3 Planning for PowerVM virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.2.4 Planning for VMware virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075.2.5 Planning for Hyper-V virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 6. IBM Flex System Managerinitial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

6.1 FSM initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146.1.1 Flex System Manager startup wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

6.2 Update the FSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1296.3 Select chassis to manage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306.4 Acquire updates for chassis components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326.5 FSM Eth1 network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416.6 Updating the CMM firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506.7 Discovery and inventory collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

6.7.1 Discovery Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1576.7.2 Manual inventory collection of the chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636.7.3 Discovery of compute nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676.7.4 I/O Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

6.8 Operating system discovery, access and inventory . . . . . . . . . . . . . . . . . . . . . . . . . . 1846.9 Updating compute node firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846.10 Updating I/O module Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1936.11 Initial configuration of compute nodes and I/O modules . . . . . . . . . . . . . . . . . . . . . . 1976.12 Manage Feature-on-Demand keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1976.13 Discover and manage V7000 (Storage Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

6.13.1 Discover an IBM Storwize V7000 to manage from IBM Flex System Manager Storage Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

6.13.2 Collect inventory on the discovered V7000. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2096.13.3 Overview of Storwize V7000 systems management. . . . . . . . . . . . . . . . . . . . . 2136.13.4 External FC SAN switch discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

6.14 Configuring the network parameters (Network Control) . . . . . . . . . . . . . . . . . . . . . . 226

iv Implementing Systems Management of IBM PureFlex System

Draft Document for Review August 18, 2012 12:15 am 8060TOC.fm

Chapter 7. Managing chassis hardware components withIBM Flex System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

7.1 Using the Chassis Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2307.2 Using Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2357.3 Creating an event filter from an event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2407.4 Define event actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2427.5 Automating tasks with event automation plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2457.6 Handling serviceable hardware problems with IBM Flex System Manager Service and

Support Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2557.7 Integrating FSM with your enterprise monitoring system . . . . . . . . . . . . . . . . . . . . . . 2647.8 Using Monitors and Thresholds to monitor system status and health. . . . . . . . . . . . . 2657.9 Remote management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Chapter 8. Managing KVM environment with IBM Flex System Manager . . . . . . . . . 2918.1 KVM management architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2928.2 KVM platform agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

8.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2928.2.2 KVM Platform Agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2948.2.3 KVM host discovery, granting access and inventory collection. . . . . . . . . . . . . . 296

8.3 Image repository for KVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2988.3.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2998.3.2 Common Agent installation on a KVM host image repository . . . . . . . . . . . . . . . 3018.3.3 Subagent installation on a KVM host image repository. . . . . . . . . . . . . . . . . . . . 3068.3.4 Host mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3098.3.5 Discover and manage V7000 storage system . . . . . . . . . . . . . . . . . . . . . . . . . . 3158.3.6 Discover and manage SAN switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3158.3.7 Discover and Configure an image repository server for SAN storage . . . . . . . . 315

8.4 Create SAN Storage system pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3188.5 Create KVM server system pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

8.5.1 Add Host to an existing Server system pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3268.6 Overview of Network system pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3298.7 Operate a KVM virtual infrastructure with FSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

8.7.1 Import virtual appliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3318.7.2 Deploy a Virtual Appliance to create a Virtual Server . . . . . . . . . . . . . . . . . . . . . 3358.7.3 Capture a virtual server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3428.7.4 Relocate virtual servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Chapter 9. Managing PowerVM environment with IBM Flex System Manager . . . . . 3559.1 Initial deployment of virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

9.1.1 Solution architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3569.1.2 Setting up VIOS and NIM server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

9.2 Capture virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3699.2.1 Capture AIX using Network Installation Manager (NIM) . . . . . . . . . . . . . . . . . . . 3709.2.2 Capture AIX using storage copy services (SCS) . . . . . . . . . . . . . . . . . . . . . . . . 394

9.3 Deploy virtual machines based on previously captured . . . . . . . . . . . . . . . . . . . . . . . 4169.3.1 Deploy virtual machines using LPP_source . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4169.3.2 Deploy a virtual machine using mksysb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4229.3.3 Deploy a virtual machine using SCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

9.4 Relocate virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4299.4.1 Relocating virtual servers manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Chapter 10. Managing VMware environment with IBM Flex System Manager . . . . . 43710.1 Environment overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43810.2 Deploy a VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

Contents v

8060TOC.fm Draft Document for Review August 18, 2012 12:15 am

10.3 Relocate a VM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45510.4 Relocate all VMs from a host and save a relocation plan . . . . . . . . . . . . . . . . . . . . . 45910.5 Modify Virtual Server resource allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46310.6 Enable DRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46810.7 Put a host in maintenance mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47110.8 Topology view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47510.9 Automating preventive actions in response to hardware alerts. . . . . . . . . . . . . . . . . 481

Chapter 11. Managing Hyper-V environment with IBM Flex System Manager . . . . . 49511.1 Operate the FSM in the Hyper-V environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

11.1.1 Install agent on an Hyper-V node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49611.2 Manage Hyper-V from FSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

11.2.1 Deploy virtual servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50211.2.2 Edit virtual server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50611.2.3 Delete a virtual server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50711.2.4 View virtual server network topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

vi Implementing Systems Management of IBM PureFlex System

Draft Document for Review August 18, 2012 12:15 am 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.

© Copyright IBM Corp. 2012. All rights reserved. vii

8060spec.fm Draft Document for Review August 18, 2012 12:15 am

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 Implementing Systems Management of IBM PureFlex System

http://www.ibm.com/legal/copytrade.shtml

Draft Document for Review August 18, 2012 12:15 am 8060pref.fm

Preface

To meet today’s 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.

The team who wrote this book

This book was produced by a team of specialists from around the world working at the International Technical Support Organization, Raleigh Center.

Ilya Krutov is a Project Leader at the ITSO Center in Raleigh and has been with IBM since 1998. Before joining the ITSO, Ilya served in IBM as a Run Rate Team Leader, Portfolio Manager, Brand Manager, Technical Sales Specialist, and Certified Instructor. Ilya has expertise in IBM System x®, BladeCenter® and PureFlex System products, server operating systems, and networking solutions. He has authored over 100 books, papers, and Product Guides. He has a bachelor degree in computer engineering from the Moscow Engineering and Physics Institute.

Frederik Aouizerats is an IT Infrastructure Consultant in Systems Lab Services Business Solution Center in La Gaude, France. Frederik has worked for IBM since 2001. He applied his skills to support customer projects across diverse business areas, most notably in Virtualization and Cloud. He was designated as one of Europe’s Top Gun experts in IBM PureFlex Systems for the Early Shipment Program (ESP). Frederik’s strong infrastructure, networking and virtualization background helped him to drive acceptance of IBM emerging technologies for EMEA clients.

Brandon Harrell is a member of the IBM Advanced Technical Skills (ATS) team with more than 12 years specializing in IBM X-Architecture® systems management products. He supports IBM Flex System Manager, IBM Systems Director, and service processors such as the CMM, IMM and AMM. Prior to his current role, he was the Technical Team Leader for the IBM Systems Director world-wide support team. Brandon also has expertise across IBM System x, BladeCenter and Flex System hardware products as well as server operating

© Copyright IBM Corp. 2012. All rights reserved. ix

8060pref.fm Draft Document for Review August 18, 2012 12:15 am

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.

The team (l-r): Ilya, MinChul, Brandon, Frederik, and Stanimir

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 WazewskiInternational Technical Support Organization, Raleigh Center

Kerry Anders, Kenneth Brown, Trina Bunting, Chris Cort, Rick McBride, Dean Price, Bob Schuster, David TareenIBM

x Implementing Systems Management of IBM PureFlex System

Draft Document for Review August 18, 2012 12:15 am 8060pref.fm

Now you can become a published author, too!

Here’s an opportunity to spotlight your skills, grow your career, and become a published author—all at the same time! Join an ITSO residency project and help write a book in your area of expertise, while honing your experience using leading-edge technologies. Your efforts will help to increase product acceptance and customer satisfaction, as you expand your network of technical contacts and relationships. Residencies run from two to six weeks in length, and you can participate either in person or as a remote resident working from your home base.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

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:

[email protected]

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South RoadPoughkeepsie, NY 12601-5400

Stay connected to IBM Redbooks

� Find us on Facebook:

http://www.facebook.com/IBMRedbooks

� Follow us on Twitter:

http://twitter.com/ibmredbooks

� Look for us on LinkedIn:

http://www.linkedin.com/groups?home=&gid=2130806

� Explore new Redbooks publications, residencies, and workshops with the IBM Redbooks weekly newsletter:

https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm

� Stay current on recent Redbooks publications with RSS Feeds:

http://www.redbooks.ibm.com/rss.html

Preface xi

http://www.redbooks.ibm.com/residencies.html

http://www.redbooks.ibm.com/residencies.html



http://www.redbooks.ibm.com/contacts.html

http://www.facebook.com/IBMRedbooks

http://twitter.com/ibmredbooks

http://www.linkedin.com/groups?home=&gid=2130806

https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm

http://www.redbooks.ibm.com/rss.html

8060pref.fm Draft Document for Review August 18, 2012 12:15 am

xii Implementing Systems Management of IBM PureFlex System

Draft Document for Review August 18, 2012 12:15 am Part 1_Introduction.fm

Part 1 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

© Copyright IBM Corp. 2012. All rights reserved. 1

Part 1_Introduction.fm Draft Document for Review August 18, 2012 12:15 am

2 Implementing Systems Management of IBM PureFlex System

Draft Document for Review August 18, 2012 12:15 am Introduction.fm

Chapter 1. Introduction to IBM PureFlex System and IBM Flex System

During the last 100 years, information technology has moved from a specialized tool to a pervasive influence on nearly every aspect of life. From tabulating machines that counted with mechanical switches or vacuum tubes to the first programmable computers, IBM has been a part of this growth. The goal has always been to help customers to solve problems. IT is a constant part of business and of general life. The expertise of IBM in delivering IT solutions has helped the planet become more efficient. As organizational leaders seek to extract more real value from their data, business processes, and other key investments, IT is moving to the strategic center of business.

To meet these business demands, IBM is introducing a new category of systems - IBM PureSystems™. These systems combine the flexibility of general-purpose systems, the elasticity of cloud computing, and the simplicity of an appliance that is tuned to the workload. Expert integrated systems are essentially the building blocks of capability. This new category of systems represents the collective knowledge of thousands of deployments, established guidelines, innovative thinking, IT leadership, and distilled expertise.

The IBM PureSystems offerings are optimized for performance and virtualized for efficiency. These systems offer a no-compromise design with system-level upgradeability. IBM PureSystems is built for cloud, containing “built-in” flexibility and simplicity.

At IBM, expert integrated systems come in two types:

� IBM PureFlex System. Infrastructure systems deeply integrate the IT elements and expertise of your system infrastructure.

� IBM PureApplication™ System. Platform systems include middleware and expertise for deploying and managing your application platforms.

1


Introduction.fm Draft Document for Review August 18, 2012 12:15 am

1.1 IBM PureFlex System

To meet today’s complex and ever-changing business demands, you need a solid foundation of server, storage, networking, and software resources. Furthermore, it needs to be simple to deploy, and able to quickly and automatically adapt to changing conditions. You also need access to, and the ability to take advantage of, broad expertise and proven guidelines in systems management, applications, hardware maintenance and more.

IBM PureFlex System is a comprehensive infrastructure system that provides an expert integrated computing system. It combines servers, enterprise storage, networking, virtualization, and management into a single structure. Its built-in expertise enables organizations to manage and flexibly deploy integrated patterns of virtual and hardware resources through unified management. These systems are ideally suited for customers who want a system that delivers the simplicity of an integrated solution while still able to tune middleware and the runtime environment. Figure 1-1 shows IBM PureFlex System.

Figure 1-1 IBM PureFlex System

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



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

The fundamental building blocks of IBM PureFlex System solutions are the IBM Flex System Enterprise Chassis complete with compute nodes, networking, and storage.

Component IBM PureFlex System Express

IBM PureFlex System Standard

IBM PureFlex System Enterprise

IBM PureFlex System 42U Rack

1 1 1

IBM Flex System Enterprise Chassis

1 1 1

IBM Flex System Fabric EN4093 10 Gb Scalable Switch

1 1 2 with both port-count upgrades

IBM Flex System FC3171 8 Gb SAN Switch

1 2 2

IBM Flex System Manager Node

1 1 1

IBM Flex System Manager software license

IBM Flex System Manager with 1-year service and support

IBM Flex System Manager Advanced with 3-year service and support

Flex System Manager Advanced with 3-year service and support

Chassis Management Module 2 2 2

Chassis power supplies (std/max)

2 / 6 4 / 6 6 / 6

Chassis 80 mm fan modules (std/max)

4 / 8 6 / 8 8 / 8

IBM Storwize® V7000 Disk System

Yes (redundant controller) Yes (redundant controller) Yes (redundant controller)

IBM Storwize V7000 Software Base with 1-year software maintenance agreement

Base with 3-year software maintenance agreement

Base with 3-year software maintenance agreement

Chapter 1. Introduction to IBM PureFlex System and IBM Flex System 5


1.2 IBM PureFlex System capabilities

The PureFlex System offers these advantages:

� Configurations that ease acquisition experience and match your needs

� Optimized to align with targeted workloads and environments

� Designed for cloud with SmartCloud Entry included on Standard and Enterprise

� Choice of architecture, operating system, and virtualization engine

� Designed for simplicity with integrated, single-system management across physical and virtual resources

� Simplified ordering that accelerates deployment into your environments

� Ships as a single integrated entity directly to you

� Includes factory integration and lab services optimization

IBM PureFlex System has three preintegrated offerings that support compute, storage, and networking requirements. You can select from these offerings, which are designed for key client initiatives and help simplify ordering and configuration. As a result, PureFlex System reduces the cost, time, and complexity of system deployments.

The IBM PureFlex System is offered in these configurations:

� Express: The infrastructure system for small-sized and midsized businesses, and the most cost-effective entry point.

� Standard: The infrastructure system for application servers with supporting storage and networking.

� Enterprise: The infrastructure system optimized for scalable cloud deployments. It has built-in redundancy for highly reliable and resilient operation to support critical applications and cloud services.

A PureFlex System configuration has these main components:

� Preinstalled and configured IBM Flex System Enterprise Chassis

� Compute nodes with either IBM POWER® or Intel Xeon processors

� IBM Flex System Manager, preinstalled with management software and licenses for software activation

� IBM Storwize V7000 external storage unit

� All hardware components preinstalled in an IBM PureFlex System 42U rack

� Choice of:

– Operating system: IBM AIX, IBM i, Microsoft Windows, Red Hat Enterprise Linux, or SUSE Linux Enterprise Server

– Virtualization software: IBM PowerVM, KVM, VMware vSphere, or Microsoft Hyper V

– SmartCloud Entry

� Complete pre-integrated software and hardware

� On-site services included to get you up and running quickly

Restriction: Orders for Power Systems compute node must be one of the three IBM PureFlex System configurations. Build-to-order configurations are not available.



1.3 IBM Flex System: The building blocks

IBM PureFlex System and IBM PureApplication System are built from reliable IBM technology that supports open standards and offer confident road maps, IBM Flex System. IBM Flex System is designed for multiple generations of technology, supporting your workload today while being ready for the future demands of your business. IBM Flex System is shown in Figure 1-2

Figure 1-2 IBM Flex System

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

1.3.2 Compute nodes

The compute nodes are designed to advantage of the full capabilities of IBM POWER7® and Intel Xeon processors. This configuration offers the performance you need for your critical applications.

Chapter 1. Introduction to IBM PureFlex System and IBM Flex System 7


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.


Draft Document for Review August 18, 2012 12:15 am Management_Overview.fm

Chapter 2. IBM PureFlex System management devices and appliances

The IBM Flex System hardware and software features can help you optimize your resource and power utilization, track and deploy your assets, maintain a secure environment, and simplify the overall management of your data center. The Chassis Management Module (CMM), integrated compute node management controllers, and the IBM Flex System Manager management node are specifically designed to help simplify the overall management of your IBM Flex System resources.

This chapter contains the following sections:

� 2.1, “Management network” on page 10� 2.2, “Chassis Management Module” on page 11� 2.3, “Compute node management” on page 13� 2.5, “IBM Flex System Manager” on page 16

2


Management_Overview.fm Draft Document for Review August 18, 2012 12:15 am

2.1 Management network

The management network is a private and secure Gigabit Ethernet network. It is used to complete management-related functions throughout the chassis, including management tasks related to the compute nodes, switches, and the chassis itself.

The management network is shown in Figure 2-1 as the blue line. It connects the Chassis Management Module (CMM) to the compute nodes, the switches in the I/O bays, and the Flex System Manager (FSM). The FSM connection to the management network is through a special Broadcom 5718-based management network adapter (Eth0). The management networks in multiple chassis can be connected together through the external ports of the CMMs in each chassis through a GbE top-of-rack switch.

The yellow line in the Figure 2-1 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.

Figure 2-1 Separate management and production data networks

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

Enterprise Chassis

Flex System Manager

Eth0 Eth1

CMM

CMM

Management Network

Top-of-Rack Switch

CMM CMM

System x compute node

Data Network

I/O bay 1 I/O bay 2

PowerSystems

compute node

Por

t

FSPIMMIMM

Eth1 = embedded 2-port 10 GbE controller with Virtual Fabric Connector

Eth0 = GbE management network adapter with integrated L2 switch

CMMs in other Enterprise Chassis

Management workstation



Updating Compute Nodes wizard assists you in discovering operating systems as part of the initial setup.

2.2 Chassis Management Module

The CMM provides single-chassis management, and is used to communicate with the management controller in each compute node. It provides system monitoring, event recording, and alerts, and manages the chassis, its devices, and the compute nodes.

The chassis supports up to two chassis management modules. If one CMM fails, the second CMM can detect its inactivity, activate itself, and take control of the system without any disruption. The CMM is central of the management of the chassis, and is required in the Enterprise Chassis.

An Enterprise chassis comes with at least one CMM installed. Table 2-1 lists the ordering information for the second CMM if required.

Table 2-1 Chassis Management Module ordering information

Figure 2-2 shows the location of the CMM bays on the back of the Enterprise Chassis.

Figure 2-2 CMM Bay 1 and Bay 2

Part number Feature codea

a. The first feature code listed is for x-config configurations. The second feature code is for e-config configurations.

Description

68Y7030 A0UE / 3592 IBM Flex System Chassis Management Module

Chapter 2. IBM PureFlex System management devices and appliances 11


Figure 2-3 shows the CMM connectors and LEDs.

Figure 2-3 Chassis Management Module

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

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.

Part number Feature codea

a. The first feature code listed is for x-config configurations. The second feature code is for e-config configurations.

Description

90Y9338 A2RR / None IBM Flex System Management Serial Access CableContains two cables:� Mini-USB-to-RJ45 serial cable � Mini-USB-to-DB9 serial cable



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

2.3 Compute node management

Each node in the Enterprise Chassis has a management controller that communicates upstream through the CMM-enabled 1 GbE private management network that enables management capability. Different chassis components supported in the Enterprise Chassis can implement different management controllers. Table 2-3 details the different management controllers implemented in the chassis components.

Table 2-3 Chassis components and their respective management controllers

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.

2.3.1 Integrated Management Module II

The Integrated Management Module II (IMM2) is the next generation of the integrated service processors for the IBM x86-based server family. The IMM2 enhancements include a more responsive user interface, faster power on, and increased remote presence performance. The

Chassis components Management controller

Intel Xeon processor-based compute nodes Integrated Management Module II (IMM2)

Power Systems compute nodes Flexible service processor (FSP)



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 User’s 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

2.3.2 Flexible service processor

Several advanced system management capabilities are built into POWER7-based compute nodes. The Flexible Service Processor (FSP) handles most of the server-level system management. The FSP used in Enterprise Chassis compatible POWER-based nodes is the same service processor used on POWER rack servers. It has system alerts and Serial over LAN (SOL) capability

The FSP provides out-of-band system management capabilities, such as system control, runtime error detection, configuration, and diagnostic procedures. Generally, you do not interact with the FSP directly. Rather, you interact by using tools such as IBM Flex System Manager and Chassis Management Module.

The Flexible Service Processor provides an SOL interface, which is available by using the CMM and the console command. The POWER7-based compute nodes do not have an on-board video chip, and do not support keyboard, video, and mouse (KVM) connections. Server console access is obtained by a SOL connection only.

SOL provides a means to manage servers remotely by using a CLI over a Telnet or SSH connection. SOL is required to manage servers that do not have KVM support or that are


http://ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5086346

http://www.redbooks.ibm.com/abstracts/tips0849.html


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.

2.4 I/O modules

The I/O modules have the following base functions:

� Initialization� Configuration� Diagnostics (both power-on and concurrent)� Status reporting

In addition, the following set of protocols and software features are supported on the I/O modules:

� Supports configuration method over the Ethernet management port.

� A scriptable SSH CLI, a web server with SSL support, Simple Network Management Protocol v3 (SNMPv3) Agent with alerts, and a sFTP client.

� Server ports used for Telnet, HTTP, SNMPv1 agents, TFTP, FTP, and other insecure protocols are DISABLED by default.

� LDAP authentication protocol support for user authentication.

� For Ethernet I/O modules, 802.1x enabled with policy enforcement point (PEP) capability to allow support of TNC (Trusted Network Connect).

� The ability to capture and apply a switch configuration file and the ability to capture a first failure data capture (FFDC) data file.

� Ability to transfer files by using URL update methods (HTTP, HTTPS, FTP, TFTP, sFTP).

� Various methods for firmware updates are supported including FTP, sFTP, and TFTP. In addition, firmware updates by using a URL that includes protocol support for HTTP, HTTPs, FTP, sFTP, and TFTP are supported.

� Supports SLP discovery in addition to SNMPv3.

� Ability to detect firmware/hardware hangs, and ability to pull a ‘crash-failure memory dump’ file to an FTP (sFTP) server.

� Supports selectable primary and backup firmware banks as the current operational firmware.



� 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 CMM’s internal management ports and the I/O modules internal ports that are connected to the nodes.

2.5 IBM Flex System Manager

IBM Flex System Manager (FSM) is a systems management appliance that drives efficiency and cost savings in the data center. IBM Flex System Manager provides a pre-integrated and virtualized management environment across servers, storage, and networking that is easily managed from a single interface. A single focus point for seamless multichassis management provides an instant and resource-oriented view of chassis and chassis resources for both IBM System x and IBM Power Systems compute nodes. You can reduce the number of interfaces, steps, and clicks it takes to manage IT resources, intelligently manage and deploy workloads based on resource availability and predefined policies, and manage events and alerts to increase system availability and reduce downtime while reducing operational costs.

The IBM Flex System Manager management appliance is shown in Figure 2-4.

Figure 2-4 IBM Flex System Manager management appliance

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.



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.



– 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

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 Description

8731A1xa

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.

IBM Flex System Manager node


Base feature set

90Y4217 IBM Flex System Manager Per Managed Chassis with 1 Year SW S&S


Advanced feature set upgradea

a. Base feature set is a prerequisite for the Advanced Upgrade.

90Y4249 IBM Flex System Manager, Advanced Upgrade, Per Managed Chassis with 1-Year SW S&S

00D7554 IBM Flex System Manager, Advanced Upgrade, Per Managed Chassis with 3-Year SW S&S



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)

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)

2.5.1 Hardware overview

The IBM FSM Manager Node has the following fixed hardware specifications:

� One Intel Xeon processor E5-2650 8C 2.0 GHz 20 MB Cache 1600 MHz 95 W

� 32 GB of memory with eight 4 GB (1x4 GB, 1Rx4, 1.35 V) PC3L-10600 CL9 ECC DDR3 1333 MHz LP RDIMMs

� Integrated LSI SAS2004 RAID controller


Base feature set



Advanced feature set upgradea

a. Base feature set is a prerequisite for the Advanced Upgrade.

94Y9219 IBM Flex System Manager, Advanced Upgrade, Per Managed Chassis with 1 Year SW S&S

94Y9220 IBM Flex System Manager, Advanced Upgrade, Per Managed Chassis with 3 Year SW S&S

Important: IBM Flex System Manager base license is a prerequisite for the Advanced Upgrade license.



� 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.

Figure 2-5 Internal view that shows the major components of IBM Flex System Manager

Processor 1Filler slot for Processor 2

Management network adapter

Drive bays



Front controlsThe diagram in Figure 2-6 shows the front of an FSM with the location of the control and LEDs.

Figure 2-6 FSM front panel showing controls and LEDs

StorageThe 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

Management network adapterThe management network adapter is a standard feature of the FSM, and provides a physical connection into the private management network of the chassis. The adapter contains a Broadcom 5718 Dual 1GbE adapter and a Broadcom 5389 8-port L2 switch. This card is one of the features that makes the FSM unique compared to all other nodes supported by the Enterprise Chassis. The management network adapter provides a physical connection into the private management network of the chassis. The connection allows the software stack to have visibility into both the data and management networks. The L2 switch on this card is automatically set up by the IMM2, and connects the FSM and the onboard IMM2 into the same internal private network.

Physical disk Virtual disk size Description

SSD 50 MB Boot disk

SSD 60 GB OS/Application disk

SSD 80 GB Database disk

HDD 40 GB Update repository

HDD 40 GB Dump space

HDD 60 GB Spare disk for OS/Application

HDD 80 GB Spare disk for database

HDD 30 GB Service Partition

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa a a a a a a a a a a a a a a a a a

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

USB connector

KVM connector

Powerbutton/LED

IdentifyLED

Check logLED

FaultLED

Hard disk driveactivity LED

Hard disk drivestatus LED

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa a a a a a a a a a a a a a a a a a a

0

2

1

Solid statedrive LEDs



2.5.2 Software features

The IBM Flex System Manager management software has these main features:

� Monitoring and problem determination

– A real-time, multichassis view of hardware components with overlays for additional information.

– Automatic detection of issues in your environment through an event setup that triggers alerts and actions.

– Identification of changes that might impact availability.

– Server resource utilization by virtual machine or across a rack of systems.

� Hardware management

– Automated discovery of physical and virtual servers and interconnections, applications, and supported third-party networking.

– Inventory of hardware components.

– Chassis and hardware component views.

• Hardware properties.

• Component names/hardware identification numbers.

• Firmware levels.

• Utilization rates.

� 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.



– 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.



– 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



Draft Document for Review August 18, 2012 12:15 am Part 2_CMM.fm

Part 2 Chassis Management Module

In this part we describe how to implement systems management of IBM PureFlex System using the Chassis Management Module.


� Chapter 3, “Planning for Chassis Management Module-based systems management” on page 27

� Chapter 4, “Chassis Management Module operations” on page 35

Part 2


Part 2_CMM.fm Draft Document for Review August 18, 2012 12:15 am


Draft Document for Review August 18, 2012 12:15 am Planning_CMM.fm

Chapter 3. Planning for Chassis Management Module-based systems management

This chapter describes systems management capabilities of the Chassis Management Module and considerations you need to take into account when planning for CMM-based management in your infrastructure.

In this chapter we discuss CMM tasks, management network, CMM configuration interfaces and options for securing your chassis management components.

3


Planning_CMM.fm Draft Document for Review August 18, 2012 12:15 am

3.1 CMM-based management network

The internal chassis management network topology for CMM-based deployments is shown in Figure 3-1 as the blue line. It connects the CMM to the compute nodes and the switches in the I/O bays. The CMM interfaces with the integrated management module (IMM) or flexible service processor (FSP) integrated in each compute node in the chassis through the management network. The management networks in multiple chassis can be connected together via the external ports of the CMMs in each chassis via a GbE top-of-rack switch. The yellow line in Figure 3-1 shows the production data network.

Figure 3-1 CMM-based management network topology

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.

3.2 CMM interfaces

The Chassis Management Module supports a web-based graphical user interface and command-line interface (CLI). Both the web-based and CLI interfaces are accessible via the

Enterprise Chassis

CMM

CMM

Management Network

Top-of-Rack Switch

CMM CMM

System x compute node

Data Network

I/O bay 1 I/O bay 2

PowerSystems

compute node

Por

t

FSPIMM



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.

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.

3.3 CMM Security

Unsecured systems management tools can potentially represent a threat to the hardware and software and place your data at risk. You must understand all security risks in your system environment and what you can do to minimize these risks.

The CMM offers advanced security capabilities and user management settings to help you secure your environment.

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.

Important: All security and user-management settings are replicated to the IMMs that CMM manages.

Chapter 3. Planning for Chassis Management Module-based systems management 29


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

3.3.1 Security policies

A CMM security policy is a set of security-related characteristics that define a particular level of protection from security exposures. The CMM security policies include hardware-related communication-protocol controls and account-related access controls.

The CMM offers two levels of security policy: Legacy and Secure. Security policies are not customizable, but you can modify the user account policies that the security policies access (see 3.3.2, “User account policies” on page 31 for more information).

An administrator or a user with administrative privileges can use the CMM CLI or web interface to change the security policy settings. See “Security policies” on page 53 on how to configure Security Policies.

Secure security policyThe CMM Secure security policy is the most secure and least flexible setting that is available for your configuration. The Secure security policy establishes a more restrictive chassis infrastructure with a higher level of control over users and chassis configuration. It helps secure the chassis environment and enforces the following conditions:

� Complex password policies for CMM user accounts

� Mandatory change of password for all user accounts at first login

� Disabling of communication protocols that are not secure: FTP, SNMPv1, Telnet, TFTP, FTP, and non-secure TCP command mode (only secure communication protocols such as SSH, SSL, and HTTPS are allowed)

Important: If the security policy settings are changed after the compute nodes are up and running, the security policy status will remain in Pending state until the compute nodes in the chassis have been restarted.



� Certificates to establish secure, trusted connections for applications that run on the management processors.

Legacy security policyThe CMM Legacy security policy is the least secure and most flexible setting that is available for your configuration.

The Legacy level of management software security policy provides flexibility in managing the chassis infrastructure, but this policy is the least secure. It permits the use of the following conditions:

� Weaker password policies for CMM user accounts

� No requirement that passwords for user accounts be changed at first login

� Availability of all communication protocols, both secure and unencrypted (Telnet, SNMP v1, TCP command mode, CIM-XML, FTP, and TFTP).

3.3.2 User account policies

A CMM user account policy is a set of criteria that determine how CMM user account security, including passwords, is implemented.

User account policy conditions affect all users of the CMM. They help enforce the security policy that is chosen for the IBM Flex System Enterprise Chassis environment (see 3.3.1, “Security policies” on page 30 for more information).

The CMM offers two initial user account policy choices: Legacy and High. You can customize the default values of each of these choices to create a Custom user account policy for your IBM Flex System Enterprise Chassis chassis environment.

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.

High user account policyThe CMM user account policy must have a High setting to be used with a CMM that has a Secure security policy.

The High user account policy establishes a higher level of control over users. It provides a more secure chassis environment than the Legacy setting. If the High 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.

Legacy user account policyWhen the CMM password policy is configured for use with the Legacy security policy, it allows more flexible, and less secure, accounts.

Note: You cannot access the CMM CLI through Telnet while using the Secure security policy setting.



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

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=%2Fcom.ibm.acc.cmm.doc%2Fcli_intro_beforebegin.html

3.3.3 External authentication of certificates

Certificates are used to establish secure, trusted connections to the CMM and from the CMM to other servers.

For an application initiating a connection to trust the server that it is connecting to, it must have in its trust store a copy of either the server certificate or the certificate of the Certificate Authority (CA) that signed the server certificate. The CMM has a CA that signs certificates for the LDAP, HTTPS, and CIM servers of all systems management processors in the IBM Flex System Enterprise Chassis. You can create trust between your web browser and the HTTPS servers on the management processors in the chassis by importing the CA certificate into your web browser. Additionally, when you work with an external LDAP server, you can use the CMM web interface or CLI to configure either non-mutual (server only) or mutual certificate authentication.

User account policy setting Description

User authentication method The method for authenticating CMM users (local, LDAP, or both)

Maximum simultaneous user sessions

The number of concurrent login sessions allowed for each user through all CMM interfaces

Maximum login failures The maximum number of failed login attempts by a user before the account is locked out

Lockout period login failure The amount of time a user account is locked out after the maximum number of unsuccessful login attempts has been reached

Complex password Whether the CMM follows more secure complex password rules

Password change on first access

The requirement that users change their password the first time they log in to the CMM

Password expiration period The amount of time a user password remains valid before requiring change

Minimum password change interval

The minimum amount of time between user password changes

Password reuse cycle The number of password changes before a password can be reused


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.acc.cmm.doc%2Fcli_intro_beforebegin.html


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.

Importing an LDAP certificate with non-mutual authenticationImport a certificate by using non-mutual external authentication when you only have to authenticate the LDAP server with the CMM. You can authenticate the LDAP server with the CMM using the CMM command-line interface (CLI) or web interface.

Importing an LDAP certificate with mutual authenticationImport certificates for mutual authentication when you need the external LDAP server to authenticate the CMM and the CMM to authenticate the external LDAP server.

There are two ways to establish mutual authentication between the CMM and an external LDAP server. When you use either method, you must also perform the steps for non-mutual authentication.

� Export the chassis Certificate Authority (CA) certificate and import it into the trust store for your external LDAP server. This allows mutual authentication between the LDAP server and all elements in the chassis that have their security configuration automatically provisioned.

� Export a certificate-signing request (CSR) from the CMM and have it signed by a Certificate Authority that the LDAP server already trusts. This method provides mutual authentication between only the CMM and the LDAP server.

For more information on external authentication of certificates, visit http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.cmm.doc/cli_ext_cert_authentication.html

Note: Certificates must be signed using SHA-1 hashes, SHA-2 hashes are not supported.


http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.cmm.doc/cli_ext_cert_authentication.html

http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.cmm.doc/cli_ext_cert_authentication.html


3.4 FoD Planning

Features on Demand (FoD) is the capability to activate or “unlock” features that are integrated in IBM products. The feature is in the firmware or software but is “locked” until the activation key is installed.

You can purchase activation keys to activate the Features on Demand (FoD) for your CMMs, I/O modules, and compute nodes, if your components support these features.

You can use CMM to view activated license keys. Refer to 4.2.4, “Chassis Management Module Features on Demand” on page 63.

In order to activate the keys in you can:

� Do it directly on your I/O modules

� Do it directly on the compute nodes via the IMM or Advanced Settings Utility (ASU).

� Use Flex System Manager to manage all your FoD keys. See 5.1.3, “Planning for FoD” on page 84.

Refer to 5.1.3, “Planning for FoD” on page 84 for a list of available FoD keys for IBM Flex System.


Draft Document for Review August 18, 2012 12:15 am Configuring_CMM.fm

Chapter 4. Chassis Management Module operations

This chapter describes the steps required to perform initial configuration of the Chassis Management Module and show how to manage the Enterprise chassis with the CMM. The Chassis management Module initial setup and operation include the following tasks, each of them is described in detail in the chapter:

� Initial deployment of the Chassis Management Module

– Connecting to the CMM – Configuring the Chassis Management Module through the Initial Setup Wizard– Updating Chassis Management Module firmware– Preparing for Chassis Management Module redundancy– Configuring Chassis Management Module user authority– Restoring a Chassis Management Module configuration

� Management tasks performed through the Chassis Management Module

– Monitoring the chassis– Monitoring multiple chassis– Event notification– Chassis Management Module and Features on Demand– Chassis management– Using the Chassis Management Module CLI

4


Configuring_CMM.fm Draft Document for Review August 18, 2012 12:15 am

4.1 Initial deployment of Chassis Management Module

This section describes how to initially configure the Chassis Management Module to enable chassis management tasks. Refer to 2.2, “Chassis Management Module” on page 11 for more information about CMM capabilities.

4.1.1 Connecting to the CMM

You can cable the CMM to support a management connection that best matches your site configuration. You must connect a client system to the CMM to configure and manage operation of the IBM Flex System Enterprise Chassis.

By default, the CMM does not have a fixed static IPv6 IP address. For initial access to the CMM in an IPv6 environment, you can either use the IPv4 IP address or the IPv6 link-local address.

By default, the CMM is configured to respond to DHCP first before it uses its static IP address.

The HTTP connection is not available when the CMM security policy is set to Secure (the manufacturing default setting). When the security policy is set to Secure, Ethernet connections must be made using HTTPS.

To connect to the CMM, perform the following steps:

1. Make sure that the subnet of the client computer is set to the same value as in the CMM (the default CMM subnet is 255.255.255.0). The IP address of the CMM must also be in the same local domain as the client computer. To connect to the CMM for the first time, you might have to change the Internet Protocol properties on the client computer.

2. Open a web browser on the client computer, and direct it to the CMM IP address. For the first connection to the CMM, use the default IP address of the CMM, as seen in Figure 4-1.

Figure 4-1 Log in Chassis Management Module with default IP address

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



3. Log into the CMM using the default credentials: USERID/PASSW0RD. Click Log In, as seen in Figure 4-2 on page 37

Figure 4-2 CMM login

This is the Chassis Management Module main page, as shown in Figure 4-3.

Figure 4-3 CMM main page

4.1.2 Configuring the CMM through the Initial Setup Wizard

The next step is the initial configuration of the Chassis Management Module. The initial setup wizard can help you configure the CMM through a web interface. The wizard starts automatically when you first access the web interface of a new CMM or a CMM that has been reset to its default settings.

Chapter 4. Chassis Management Module operations 37


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

Figure 4-4 CMM main page - Mgt Module Management

The initial setup wizard is contained in the Configuration menu, as shown in Figure 4-5.

Figure 4-5 Mgt Module management page

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

Figure 4-6 Manage Configuration page



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.

Figure 4-7 Welcome page



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.

Figure 4-8 Inventory and Health page

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.

Figure 4-9 Import Existing Configuration page



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.

Figure 4-10 General Settings page



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.

Figure 4-11 Date and Time page

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.



Figure 4-12 shows the IP configuration page.

Figure 4-12 IPv4 configuration page

If you need to set up IPv6, you can use IPv6, as shown in the Figure 4-13 on page 43.

Figure 4-13 IPv6 configuration page



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.

Figure 4-14 I/O Module page

Choose the security policy for your CMM, as shown in Figure 4-15.

Figure 4-15 Security Policy page



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.

Figure 4-16 DNS setup page

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.



Enter the email addresses where notifications are to be sent as CMM events occur, as shown in Figure 4-17.

Figure 4-17 Event Recipients page



Confirm all of the information that has been entered in the setup wizard, as seen in the Figure 4-18.

Figure 4-18 Confirm page

4.1.3 Updating the Chassis Management Module firmware

This section explains how to manage the Chassis Management Module firmware.

Some IBM Flex System solutions require specific code levels or coordinated code updates. If the CMM is part of one of these solutions, verify that the level of code is supported for the solution before you update the code.

If your IBM Flex System Enterprise Chassis is configured for redundant operations and the second CMM is installed, both will have the same level of firmware after the primary CMM push the updates to the standby CMM after it is installed. The latest level of CMM firmware is available at the IBM support web site:

http://www-947.ibm.com/support/entry/portal/Downloads?lnk=mhsd


http://www-947.ibm.com/support/entry/portal/Downloads?lnk=mhsd


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

Figure 4-19 Mgt Module Management menu

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.

Figure 4-20 Checking the current firmware level



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.

Figure 4-21 Select File Source page

Click Browse, select CMM firmware file in your local directory, as shown in the Figure 4-22.

Figure 4-22 Select Firmware File page



Choose the behavior after updating the CMM firmware, as shown in the Figure 4-23.

� Restart CMM manually� Restart CMM automatically after updating

Figure 4-23 Choose Post Update Behavior page

Monitor the firmware update progress, as shown in Figure 4-24.

Figure 4-24 Performing Firmware Flash update progress page



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.

Figure 4-25 Performing Firmware Flash update status page

4.1.4 Preparing for Chassis Management Module redundancy

This section will cover how to set up fail over between two Chassis Management Modules.

To prepare your CMM for redundancy, complete the following steps:

1. Install the standby CMM in the available CMM bay.

2. Wait approximately 2 minutes while the primary CMM transfers the firmware and configuration information to the standby CMM.

3. Configure Chassis Management Module failover response.

There are two options to configure CMM failover. The first case is that the hardware failure or some malfunction resulted in failure of the primary CMM. The second case is the primary CMM operates properly, but there is a network problem, for example, network switch went down resulting in loss of connectivity to the primary CMM.

Note: Whenever power is restored to an IBM Flex System Enterprise Chassis that has two functional CMMs, the CMM in CMM bay 1 is designated as the primary CMM, even if the CMM in CMM bay 2 was the primary CMM before power was removed.



� 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.

Figure 4-26 Failover Menu

� 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.

Figure 4-27 Network Protocol Properties



Define failover condition depending on your requirements, as shown in Figure 4-28.

Figure 4-28 Network Failover set up menu

4.1.5 Configuring Chassis Management Module’s user authority

Security policiesThe IBM Flex System Enterprise Chassis takes a new approach to security with a ground-up Chassis management design to meet new Trusted Computing Group (TCG) security standards.

The Enterprise Chassis ships with secure settings by default, with two security policy settings supported: Secure and Legacy. Refer to 3.3.1, “Security policies” on page 30 for details on each security policy.

The centralized security policy makes the Enterprise Chassis easy to configure. In essence, all components run the same security policy that is provided by the Chassis Management Module.



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.

Figure 4-29 Mgt Module Management: Security

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

Figure 4-30 Security page

User account policiesA CMM user account policy is a set of criteria that determine how CMM user account security, including passwords, is implemented.

User account policy conditions affect all users of the CMM. They help enforce the security policy that is chosen for the IBM Flex System Enterprise Chassis environment

The CMM offers two initial user account policy choices: Legacy and High. You can customize the default values of each of these choices to create a Custom user account policy for your IBM Flex System Enterprise Chassis environment.



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.

Figure 4-31 Mgt Module Management: User Accounts

2. Click Global Login Settings on the Accounts tab on the User Accounts page, as shown in Figure 4-32.

Figure 4-32 User account page

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.



3. Click Account Security Level tab in the Global Login Settings window, as shown in Figure 4-33.

Figure 4-33 Global Login Settings

4. Select Custom Security Settings, High Security Settings or Legacy Security Settings from the menu and click OK, as shown in Figure 4-34.

Figure 4-34 Global Login Settings: Security Settings

For more information about the CMM security, refer to 3.3, “CMM Security” on page 29.



4.1.6 Restoring a Chassis Management Module

Restoring the CMM manufacturing default configurationYou can restore the CMM to its manufacturing default configuration in two ways:

1. In the CMM web interface, select Reset to Defaults from the Mgt Module Management menu, as shown in Figure 4-35.

Figure 4-35 Mgt Module Management: Reset to Defaults

2. If you have physical access to the CMM, push the reset button and hold it for approximately 10 seconds.

Restoring a saved CMM configurationIn the CMM web interface, a saved configuration is applied from the Manage Configuration page, as shown in Figure 4-36. Select Configuration from the Mgt Module Management menu to open the Manage Configuration page.

Figure 4-36 Manage Configuration page



4.2 Chassis Management Module management tasks

In this section, we discuss how to operate the CMM to perform specific systems management tasks.

4.2.1 Monitoring the chassis

The System Status page is the default page when you enter the CMM web interface, as shown in Figure 4-37. You can also access it by clicking System Status on the menu bar.

Figure 4-37 Chassis status

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.

Selected Active Resource

Selected Resource Actions

Selected Managed Resource



4.2.2 Monitoring multiple chassis

You can view multiple networked Chassis from the CMM web interface, as seen in the Figure 4-38.

Figure 4-38 Select Multi-Chassis Monitor

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.

Figure 4-39 Monitoring multiple chassis



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.

Figure 4-40 Extended Information

Clicking the IP address of the chassis in the Manage column (see Figure 4-39 on page 59) redirects you to another Chassis Management Module’s web interface.

4.2.3 Event notifications

Click Event Log to check events, as shown in the Figure 4-41.

Figure 4-41 Events: Event Log



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.

Figure 4-42 Event Log page

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.

Figure 4-43 Event Recipients page

Event overview

Event actions



Select the E-mail Recipient as shown in Figure 4-44.

Figure 4-44 Event Recipients page continued

Type recipient name and e-mail address, choose which events to receive, and click OK, as shown in Figure 4-45.

Figure 4-45 Create E-mail Recipient page



Choose the type and severity of the alerts to be sent, as shown in Figure 4-46.

Figure 4-46 Event Recipient Global Settings page

4.2.4 Chassis Management Module Features on Demand

You can check Feature on Demand (FoD) features activated on your CMM and I/O modules.

Follow these steps to check Features on Demand:

1. Check current Feature on Demand in Chassis Management Module. Select License Key Management from the Mgt Module Management menu, as shown in Figure 4-47.

Figure 4-47 License Key Management



Figure 4-48 shows the activated licensed features for I/O modules.

Figure 4-48 License Key Management: I/O Module

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.

Figure 4-49 License Key Management: Chassis

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


https://www-304.ibm.com/systems/x/fod/index.wss


Figure 4-50 shows Features on Demand main http page. You need IBM ID to get the features that you want to activate.

Figure 4-50 Features on Demand main page

4.2.5 Chassis management

This section describes the management of the configured resources in the chassis.

Chassis Management menu is used for reviewing or changing the properties of the components in the chassis. The menu is shown in Figure 4-51. Click Chassis.

Figure 4-51 Chassis Management menu



Operating the chassisYou can check the hardware addition or removal history through Hardware Activity tab, as shown in Figure 4-52.

Figure 4-52 Hardware Activity tab

Also you can see chassis temperature and cooling status by clicking the Temperature tab, as shown in Figure 4-53.

Figure 4-53 Temperature tab



You can check fan and cooling status by selecting the Fans and Cooling menu item on Figure 4-54 on page 67.

Figure 4-54 Fans and Cooling page

Selecting the individual fan will show you events and power usage statistics associated with it, as shown in Figure 4-55.

Figure 4-55 Power consumption page



Cooling zone status can also be checked from this page, as shown in Figure 4-56 on page 68.

Figure 4-56 Cooling Zones status

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.

Figure 4-57 Power Modules and Management page



To monitor power allocation and power consumption history, select Input Power and Allocation tab, as shown in Figure 4-58 on page 69.

Figure 4-58 Power consumption



Component IP Configuration menu allows you to set the IP parameters on I/O modules and compute nodes, as shown in Figure 4-59.

Figure 4-59 Component IP Configuration page



Click the I/O module or compute node link to open its IP properties window, as shown in Figure 4-60.

Figure 4-60 IP Address Configuration node01 page



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.

Figure 4-61 Chassis Hardware Topology page



Click Reports in the Chassis Management menu, you can see hardware information in the chassis, as shown in Figure 4-62 on page 73.

Figure 4-62 Reports page

Operating the compute nodeSelecting Compute Nodes from the menu shows a page listing the servers installed in the chassis, as shown in Figure 4-63. You can power on/off compute nodes, access them through a remote console, set properties, for example, Wake on LAN, and perform other actions.

Figure 4-63 Compute Nodes page

Operating the I/O moduleThe I/O Modules page is similar to the Compute Nodes page. A table is displayed, showing the I/O modules. Clicking the module name yields a pop-up windows with the properties of that module. See Figure 4-64.



Figure 4-64 I/O Modules page

Launch switch module remote console by clicking Launch IOM console, as shown in Figure 4-65.

Figure 4-65 Launch I/O Modules menu

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.

Figure 4-66 Launch IOM Console window

This brings selected I/O module’s management user interface (UI), for example, web UI for the network switch, as shown in Figure 4-67.



Figure 4-67 Network I/O module main page

4.2.6 Using the Chassis Management Module CLI

This section contains information about configuring the CMM and managing components that are installed in an IBM Flex System Enterprise Chassis using the command-line interface.

The IBM Flex System Chassis Management Module (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 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 must authenticate with the CMM before you issue commands.

Use telnet or ssh program and type IP address and choose protocol, then you can login in Chassis Management Module CLI interface, as seen in the Figure 4-68 on page 75.

Figure 4-68 Chassis Management Module login



Command-line interface guidelinesAll commands have the following basic structure:

Example 4-1 command usage

command -option parameter

Selecting the command targetYou can use the command-line interface to target commands to the CMM or to other devices in the IBM Flex System Enterprise Chassis. The command-line prompt indicates the persistent command environment: where commands are directed unless another target is specified. You can specify a command target by using the full target name or by using a target name that is relative to the persistent command environment.

Command targets are specified hierarchically, as shown in Figure 4-69.

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.

Using Command-line Interface.This topic describe how CLI works with Chassis Management Module. We ran two CLI commands as below.

1. list command



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.

Figure 4-70 list command output

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.

Figure 4-71 info command output

For more information on CLI, go to IBM Flex System information.




Draft Document for Review August 18, 2012 12:15 am Part 3_FSM.fm

Part 3 IBM Flex System Manager

In this part we describe how to implement systems management of IBM PureFlex System using the IBM Flex System Manager.


� Chapter 5, “Planning for IBM Flex System Manager-based systems management” on page 81

� Chapter 6, “IBM Flex System Manager initial configuration” on page 113

� Chapter 7, “Managing chassis hardware components with IBM Flex System Manager” on page 229

� Chapter 8, “Managing KVM environment with IBM Flex System Manager” on page 291

� Chapter 9, “Managing PowerVM environment with IBM Flex System Manager” on page 355

� Chapter 10, “Managing VMware environment with IBM Flex System Manager” on page 437

� Chapter 11, “Managing Hyper-V environment with IBM Flex System Manager” on page 495

Part 3


Part 3_FSM.fm Draft Document for Review August 18, 2012 12:15 am


Draft Document for Review August 18, 2012 12:15 am Planning_FSM.fm

Chapter 5. Planning for IBM Flex System Manager-based systems management

This chapter describes general planning information on IBM Flex System Manager (FSM). Also when you want to build certain managed virtual infrastructure through Flex System Manager, this chapter explains specific virtualization solution management considerations with the FSM.

Planning for Flex System Manager based management include the followings, each of which is described in detail in the chapter:

1. General planning information on systems management

� FSM network integration architecture� Planning for security� Planning for FoD� Agents and tasks supported� Planning for storage management (StorageControl)� Planning for network management (NetworkControl)� Planning for IBM Fabric Manager

2. Planning for virtualized infrastructure systems management

� Virtualization and task supported� Planning for KVM virtualization� Planning for PowerVM virtualization� Planning for VMware virtualization� Planning for Hyper-V virtualization

5


Planning_FSM.fm Draft Document for Review August 18, 2012 12:15 am

5.1 General planning information on systems management

IBM Flex System Manager (FSM) is a systems management appliance that drives efficiency and cost savings in the data center. IBM Flex System Manager provides a pre-integrated and virtualized management environment across servers, storage, and networking that is easily managed from a single interface. A single focus point for seamless multichassis management provides an instant and resource-oriented view of chassis and chassis resources for both IBM System x and IBM Power Systems compute nodes. You can reduce the number of interfaces, steps, and clicks it takes to manage IT resources, intelligently manage and deploy workloads based on resource availability and predefined policies, and manage events and alerts to increase system availability and reduce downtime while reducing operational costs.

The following list describes the high-level features and functions of the IBM Flex System Manager.

� Supports a comprehensive, pre-integrated system that is configured to optimize performance and efficiency

� Automated processes triggered by events simplify management and reduce manual administrative tasks

� Centralized management reduces the skills and the number of steps it takes to manage and deploy a system

� Enables comprehensive management and control of energy utilization and costs

� Automates responses for a reduced need for manual tasks: Custom actions / filters, configure, edit, relocate, automation plans

� Full integration with server views, including virtual server views enables efficient management of resources

For more information about FSM hardware and software, refer to 2.5, “IBM Flex System Manager” on page 16.

5.1.1 FSM network integration architecture

In an IBM Flex System Enterprise Chassis, you have the option to configure separate management and data networks.

The management network is a private and secure Gigabit Ethernet network used to complete management-related functions throughout the chassis, including management tasks related to the compute nodes, switches, and the chassis itself.

The management network is shown in Figure 5-1 on page 83 as the blue line. It connects the CMM to the compute nodes, the switches in the I/O bays and the FSM. The FSM connection to the management network is via a special Broadcom 5718-based management network adapter (Eth0). The management networks in multiple chassis can be connected together via the external ports of the CMMs in each chassis via a GbE top-of-rack switch.



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.

Figure 5-1 Management and production data network

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.

5.1.2 Planning for security

The IBM Flex System products include features that can help you secure your environment. The following sections provide basic information about how some of these features work. You can use this information along with the documentation that comes with your IBM Flex System products to help you evaluate and implement the security plan for your environment.

As you evaluate the security requirements of your environment, be sure to consider that unsecured systems-management tools can damage hardware and software. It is extremely important that you understand all security risks in your system environment and what you can do to minimize these risks.

Security policiesAn 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.

Chapter 5. Planning for IBM Flex System Manager-based systems management 83


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

Legacy Security PolicyThe IBM Flex System Manager management software Legacy security policy is the least secure and most flexible setting that is available for your configuration.

The Legacy level of management software security policy provides flexibility in managing platform security, but this policy is the least secure. It permits the use of the following conditions:

� Weak password policies with minimal controls are permitted

� Manufacturing default passwords that do not have to be changed

� Unencrypted communication protocols such as Telnet, SNMPv1, TCP Command Mode, CIM-XML, FTP Server, and TFTP Server

Secure Security PolicyThe IBM Flex System Manager management software Secure security policy is the most secure and least flexible setting that is available for your configuration.

The Secure security controls setting, or Secure policy, is the default security setting. It helps to ensure a secure chassis infrastructure and enforces the use of the following conditions:

� Strong password policies with automatic validation and verification checks

� Updated passwords that replace the manufacturing default passwords after the initial setup

� Only secure communication protocols such as SSH and SSL

� Certificates to establish secure, trusted connections for applications that run on the management processors

5.1.3 Planning for FoD

IBM Feature on Demand is the capability to activate or “unlock” features integrated in IBM products. The feature is in the firmware or software but “locked” until the activation key is installed. There are several benefits using FoD:

• Feature keys for the FoD can be purchased just like other options

• You buy the features you need now with the ability to grow your system later without costly rip and replace.(Pay as You Grow)

• Allows for upgrades in the field

• Feature activation can be done on server or chassis at the time of the server/chassis sale or at a later time

• FoD enables ease of installation, reduced inventory, and faster fulfillment of options

Fulfillment Process There are two way to activate Features on Demand.

1. FoD option ordered with server and installed in manufacturing



Figure 5-2 Features on Demand field order option

2. FoD option purchased separately or post system sale

Figure 5-3 Features on Demand Post or respective order option

Features on Demand for IBM Flex System ManagerIBM Features on Demand provides optional software that is available for IBM Flex System Manager Types 7955, 8731, and 8734 and IBM Flex System Manager management software. You can also use the management software to enable optional features for managed compute nodes.

Features on Demand provides a convenient way for you to order and activate optional features from IBM through the management software web interface. You can also upload compute node Features on Demand keys to the management node and administer the keys to managed compute nodes through the management software.

Any Features on Demand software that you ordered with your IBM Flex System Manager Types 7955, 8731, and 8734 management node are preactivated and do not require manual activation through the management software interface.

Place order Request key

Send product with activated key

Generate key

Installkey

Fulfillment

Key

Mgm

tSy

stem

IBM

Cust

omer

or P

artn

er

Place order1

Receive paper (and optional email) with authorization

code

FulfillmentKe

yM

gmt

Syst

em

IBM

Cust

omer

or P

artn

er

Request key

Generatekey

Receive activation key

Install key3

From request to email authorization takes only 24 hours

Submit authorization2



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)

Table 5-2 FoD part numbers (Latin America and Europe/Middle East/Africa)

Features on Demand for Components in the ChassisThere are a lot of Features on Demand on the Components. For example, There are a few option to activate to the I/O modules. Table 5-3 and Table 5-4 on page 87 shows Features on Demand for I/O modules and Compute node.

Table 5-3 Part numbers for ordering Feature on Demand entitlement licenses for I/O modules

Description Part number

Base feature set

IBM Flex System Manager Per Managed Chassis with 1 Year SW S&S 90Y4217


Advanced feature seta

a. The Advanced Upgrade license requires the IBM Flex System Manager base license.

IBM Flex System Manager Advanced Upgrade Per Managed Chassis with 1 Year SW S&S

90Y4249


00D7554


Base feature set



Advanced feature seta

a. The Advanced Upgrade license requires the IBM Flex System Manager base license.


94Y9219


94Y9220


IBM Flex System EN2092 1Gb Ethernet Scalable Switch-10Gb Uplinks 49Y4298

IBM Flex System EN4093 10Gb Virtual Fabric Scalable Switch-Upgrade 1 49Y4798

IBM Flex System EN4093 10Gb Virtual Fabric Scalable Switch-Upgrade 2 88Y6037

IBM Flex System IB6131 Infiniband Switch-FDR Upgrade 90Y3462


http://www.ibm.com/systems/x/fod/


Table 5-4 Part numbers for ordering Feature on Demand entitlement licenses for compute nodes

If you want to know how to manage Features on Demand, go to 6.12, “Manage Feature-on-Demand keys” on page 197.

5.1.4 Agents and tasks supported

IBM Flex System Manager provides four tiers of agents for managed systems. For each managed system, you need to choose the tier that provides the amount and level of capabilities that you need for that managed system. Depending on the type of managed system and the management tasks you need to perform, you can choose the level of agent capabilities that best fits your needs.

IBM Flex System Manager has four agent tiers:

� Agentless in-band

Managed systems without any FSM client software installed. FSM communicates with the managed system through the operating system.

� Agentless out-of-band

Managed systems without any FSM client software installed. FSM communicates with the managed system through something other than the operating system, such as a service processor or a hardware management console.

� Platform Agent

Managed systems with Platform Agent installed. FSM communicates with the managed system through the Platform Agent.

� Common Agent

Managed systems with Common Agent installed. FSM communicates with the managed system through the Common Agent.

Table 5-5 lists the agent tier support for the IBM Flex System managed compute nodes. Managed nodes include x220 and x240 compute node supporting Windows, Linux and VMware, and p260 and p460 compute nodes supporting IBM AIX, IBM i and Linux.

Table 5-5 Agent tier support by management system type


IBM Flex System CN4054 Virtual Fabric Adapter (SW Upgrade) 90Y3558

ServeRAID M5100 Series RAID 6 Upgrade for IBM Flex System 90Y4410

ServeRAID M5100 Series SSD Caching Enabler for IBM Flex System 90Y4447

IBM Virtual Fabric Advanced Software Upgrade (LOM) 90Y9310

Agent tierManaged system type

Agentlessin-band

Agentlessout-of-band

PlatformAgent

CommonAgent

Compute nodes running AIX Yes Yes No Yes

Compute nodes running IBM i Yes Yes Yes Yes

Compute nodes running Linux No Yes Yes Yes

Compute nodes running Linux and supporting SSH

Yes Yes Yes Yes



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

5.1.5 Planning for managing the networking infrastructure

IBM Flex System Manager management software Network Control provides advanced network management functions for IBM Flex System Enterprise Chassis network devices. Functions include discovery, inventory, network topology, health and status monitoring, and configuration of network devices. Network Control is a preinstalled plug-in that builds on base management software capabilities by integrating the launch of vendor-based device management tools, topology views of network connectivity, and subnet-based views of servers and network devices.

Network Control offers the following network-management capabilities:

� Discover network devices in your environment

Compute nodes running Windows No Yes Yes Yes

Compute nodes running Windows and supporting SSH or DCOM

Yes Yes Yes Yes

Compute nodes running VMware Yes Yes Yes Yes

Other managed resources supporting SSH or SNMP

Yes Yes No No


Agentlessin-band


PlatformAgent

CommonAgent

Command Automation No No No Yes

Hardware alerts No Yes Yes Yes

Platform alerts No No Yes Yes

Health and status monitoring No No Yes Yes

File Transfer No No No Yes

Inventory (hardware) No Yes Yes Yes

Inventory (software) Yes No Yes Yes

Problems (hardware status) No Yes Yes Yes

Process Management No No No Yes

Power Management No Yes No Yes

Remote Control No Yes No No

Remote Command Line Yes No Yes Yes

Resource Monitors No No Yes Yes

Update Manager No No Yes Yes


Agentlessin-band


PlatformAgent

CommonAgent



� 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 ControlIBM 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

5.1.6 Planning for managing the storage infrastructure

Storage management with IBM Flex System Manager management software involves two software components: Storage Manager and Storage Control. Both components are included with the management software. Storage Manager is a standard management software capability that provides basic storage lifecycle management (Discovery, Inventory, Health and Alerts). Storage Control is a preinstalled plug-in for the management software that expands storage support to mid-range and high-end storage devices. It is based on technology from IBM Tivoli® Storage Productivity Center.

I/O moduleManagement task

EN20921 Gb Ethernet

EN409310 Gb Ethernet

FC31718 Gb FC

FC502216 Gb FC

Discovery Yes Yes Yes Yes

Inventory Yes Yes Yes Yes

Monitoring Yes Yes Yes Yes

Alerts Yes Yes Yes Yes

Configuration Yes Yes Yes No



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 ControlWith 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.

Storage systemManagement task

V7000

Storage device discovery Yes

Integrated physical and logical topology views Yes

Show relationships between storage and server resources Yes

Perform logical and physical configuration Yes

View controller and volume status and to set notification alerts Yes



Figure 5-4 on page 91 shows Storage Control overview.

Figure 5-4 Storage Control main page

For more information see the following IBM Flex System Manager product publications, available from the IBM Flex System Information Center:


5.1.7 Planning for IBM Fabric Manager

IBM Fabric Manager (IFM) is a solution that enables you to quickly replace and recover compute nodes in your environment. It provides the following capabilities:

� I/O address assignment for initial compute node deployment and re-deployment

� Slot-based I/O address assignment – Ethernet and FCoE MAC, FC WWNs, SAS WWNs, FC and SAS boot targets

� Pre-assignment allows LAN/SAN configuration prior to compute node installation

� Automatic re-assignment on compute node swap (a.k.a. rip/replace)

� Failover Monitors or Event Automation Plans for automatic compute node failover

� Create standby compute node pools

� Configure boot target settings

� Provides I/O parameter and VLAN migration to standby compute nodes in case of hardware failure




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.

Figure 5-5 IFM Launch in Context

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.iofm.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.

5.2.1 Virtualization and task supported

System virtualization-management products and components in the IBM Flex System Enterprise Chassis integrate and interact to support the management of virtualized server, storage, and network resources.

Virtualization management refers to the software that enables the use and management of virtual server, storage, network, and image resources. Virtualization management enables you to utilize your compute resources fully, deploy new workloads rapidly, monitor resource consumption, and maintain the availability of workloads. IBM Flex System Manager management software automates this complex set of tasks through administrator-defined


http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.iofm.doc/dw1li_product_page.html


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



� 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

5.2.2 Planning for KVM virtualization

The IBM FSM appliance can provide a set of capabilities to easily manage a KVM virtual infrastructure with features such high availability, virtual server relocation, capture, deployment, import appliance and network multitenancy using VLANs provisioning.

This topic describes the requirements and support for the Linux Kernel-based Virtual Machine (KVM) virtualization environment in IBM Flex System Manager VMControl.

There are two implementation models to manage a KVM virtual infrastructure:

� SAN storage based model:

A supported storage system acting as the shared storage device

� NFS storage based model:

The NFS server acting as the shared storage device

Virtualization environment Management task

AIX and Linuxa

a. Linux on IBM Power Systems compute nodes

IBM i VMware ESX

Microsoft Hyper-V

Linux KVM

Deploys virtual servers

Yes Yes Yes Yes Yes

Deploys virtual farms No No Yes No Yes

Relocates virtual servers

Yes No Yes No Yes

Imports virtual appliance packages

Yes Yes No No Yes

Captures virtual servers

Yes Yes No No Yes

Captures workloads Yes Yes No No Yes

Deploys virtual appliances

Yes Yes No No Yes

Deploys workloads Yes Yes No No Yes

Deploys server system pools

Yes No No No Yes

Deploys storage system pools

Yes No No No No



NFS storage based modelThere are following requirements for NFS storage-based model:

� IBM Flex System Manager VMControl is activated

� An NFS x86_64 Red Hat Enterprise Linux (RHEL) server is set up and configured. The picture shown Figure 5-6 the KVM virtualization environment with NFS storage.

Figure 5-6 KVM virtual environment with NFS storage

� 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

Figure 5-7 no_root_squash export option

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.



2. Restart the IBM Flex System Manager after adding or changing the USMIKernel.properties file.

� Ensure that the NFS services are started. For example, by running the command:

service nfs start as shown Figure 5-8

Figure 5-8 NFS service restart

� 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.

Figure 5-9 NFS export mounted on image repository server

Note: For consistency, name image and disk files that are stored on NFS with a .dsk, .img, or .raw extension.



� 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.

Figure 5-10 images repository

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.

Figure 5-11 select edit KVM host



Select the pool to create you virtual server disk as shown in Figure 5-12.

Figure 5-12 create a new KVM disk in a storage pool

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.



SAN storage based modelSAN Storage configuration looks more complex than the NFS solution but the block storage based model offer better performances and more flexibility.

The picture in Figure 5-13 shown a KVM virtualization environment with SAN storage.

Figure 5-13 KVM virtualization environment with SAN storage

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.



� 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 device’s 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

� 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.sdnm.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--------------------------

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.

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.


http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.sdnm.adv.helps.doc/fnc0_r_network_ctrl_planning.html





NAME: STORAGE SUBSYSTEM/POOLIBM Host01: Storwize V7000-2076/RAID5_Pool_KVMStorwize 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 hosts, Linux versions, and firmware versionsKVM virtualized environments must run on X-Architecture compute nodes.

You must use the following Linux versions for the KVM virtualization environment.

– Hosts require Red Hat Enterprise Linux version 6.2 with KVM installed.

Supported networksVMControl 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

Supported storageImage 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.helps.doc/fnc0_r_network_ctrl_planning.htm

Supported tasksIn 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

Note: Use paravirtualized (virtio) drivers for enhanced performance. Use Virtio and e1000 model configurations for virtual network server adapters.




– 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

KVM requirementsIn 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

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




� service iptables save

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=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_t_access_kvm_remotely.html

Note: These packages might be available from your installation software.

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.


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_t_access_kvm_remotely.html


RestrictionsPlease refer restrictions section in the link bellow: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_r_kvm.html

5.2.3 Planning for PowerVM virtualization

This topic describes the requirements and support for AIX and Linux virtual appliances, virtual servers, and workloads in the Power Systems virtualization environment.

The two types of architectures to implementing PowerVM base virtualization through Flex System Manager:

1. Requirements and support for AIX using Network Installation Manager (NIM)

2. Requirements and support for AIX, IBM i, and Linux using storage copy services (SCS)

Requirements and support for AIX using Network Installation ManagerThis topic describes the requirements and support for AIX virtual appliances, virtual servers, and workloads in a Power Systems virtualization environment that relies on AIX Network Installation Manager (NIM).

Requirements for AIX using NIMThe following diagram shows an example Power Systems virtualization environment for AIX virtual appliances, virtual servers, and workloads that rely on NIM.

Figure 5-14 shows an example Power Systems virtualization environment for AIX virtual appliances, virtual servers, and workloads that rely on NIM.

Figure 5-14 AIX using NIM System diagram

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.


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_r_kvm.html


� 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.

� 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 AIX and firmware versionsYou must use the following AIX and firmware versions in this environment:

� NIM master

– The NIM master must be AIX 6.1 TL03 or newer.

� Virtual I/O Server (VIOS)

– For POWER7, use a minimum of VIOS 2.2.1.0 and all available updates.

� Virtual appliances

– You can capture any AIX Version 5.3, AIX Version 6.1, or AIX Version 7.1 virtual server or workload as a virtual appliance, and you can import or deploy any AIX Version 5.3, AIX Version 6.1, or AIX Version 7.1 virtual appliance.

Supported storageThe following storage systems are supported:

� IBM Storwize V7000

Supported tasksIn this environment, you can perform these tasks:

� Create, edit, and delete virtual servers

� Relocate virtual servers

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.

Note: The level of AIX on the NIM master must be the same or higher than the level of AIX on the virtual servers that you capture or the virtual appliances that you deploy.



� 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 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.



� 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.

� 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 operating systems and firmware versionsYou must use the following operating systems and firmware versions in this SCS-based Power Systems virtualization environment.

� IBM Flex System Manager

– You can use any IBM Flex System Manager with VMControl Standard Edition or VMControl Enterprise Edition activated.

� Virtual I/O Server (VIOS)

– For POWER7, use a minimum of VIOS 2.2.1.0 and all available updates.

� IBM Power firmware

– For POWER7 processor-based servers, use a minimum of FW7.2 and all available updates.

Supported tasksIn a Power Systems virtualization environment for AIX, IBM i, and Linux that relies on SCS, you can perform the following tasks:


� 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

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.

Note: If manual or automated virtual server relocation capabilities are needed, multiple IBM Power 6 or 7 servers are required.



In a Power Systems virtualization environment for AIX and Linux that relies on SCS, you can perform the following additional tasks:


� Create, edit, and delete system pools

5.2.4 Planning for VMware virtualization

This topic describes the requirements and support for the VMware virtualization environment in IBM Flex System Manager VMControl.

VMware ESX and VMware ESXi hosts managed by VMware vCenterFigure 5-16 on page 107 shows a virtualization environment with VMware vCenter managing VMware ESX and VMware ESXi hosts.

Figure 5-16 Diagram of VMware vCenter virtualization environment

There are following requirements for the scenario described above:



� VMware vCenter is installed on an x86-compatible system.

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 ESX exists to host virtual servers that you can manage using VMControl.

� VMware ESXi exists to host virtual servers that you can manage using VMControl.

� 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.

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 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


� Put a host into maintenance mode

� Remove a host from maintenance mode

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.

Note: VMware ESX is managed by VMware vCenter.

Note: VMware ESXi is managed by VMware vCenter.

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.director.discovery.helps.doc/fqm0_t_managing_discovery_profiles.html


http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.director.discovery.helps.doc/fqm0_t_managing_discovery_profiles.html


VMware ESX stand-aloneFigure 5-17 on page 109 shows the VMware ESX virtualization environment.

Figure 5-17 Diagram of VMware ESX virtualization environment



� 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 farms




5.2.5 Planning for Hyper-V virtualization

Flex System Manager is able to manage basics tasks for the Microsoft Hyper-V hypervisor. The advantage is that you can start, stop, restart, suspend, create and delete your virtual servers running on Microsoft hypervisors with same tool which manage also the other hypervisors of the market.

This section describe the requirements and support for the Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled virtualization environment in IBM Flex System Manager VMControl.

The picture bellow shows the Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled virtualization environment managed by IBM Flex System Manager Figure 5-18.

Figure 5-18 Hyper-V architecture managed by FSM


� IBM Flex System Manager available in your PureFlex chassis.




� 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.

Figure 5-19 Enable Hyper-V role on Windows 2008 R2

� 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 versionsVMControl 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+VMControl+2.4.1+Dependencies

Supported tasksIn this environment, you can create, edit, and delete virtual servers then start, stop, restart and suspend your virtual servers.


https://www.ibm.com/developerworks/wikis/display/WikiPtype/Minimum+Fix+Levels+for+VMControl+2.4.1+Dependencies

Draft Document for Review August 18, 2012 12:15 am Configuring_FSM.fm

Chapter 6. IBM Flex System Managerinitial configuration

This chapter describes initial setup steps required for the IBM Flex System Manager-based systems management. These include initial configuration of the FSM, discovery and inventory collection of the chassis components, operating systems and external storage devices, and firmware updates for the FSM, CMM, compute nodes and I/O modules.

6


Configuring_FSM.fm Draft Document for Review August 18, 2012 12:15 am

6.1 FSM initial setup

FSM is an appliance that delivers with all required software preinstalled. When this software stack is launched for the first time, a startup wizard is initiated that steps through the required configuration process, such as licensing agreements and Transmission Control Protocol/Internet Protocol (TCP/IP) configuration for the appliance.

When configuration is complete, the FSM is ready to manage the chassis it is installed in, and other chassis, up to four. Now that the chassis is managed, individual components, such as compute nodes and switches, can also be managed.

This section describes how to use the startup wizards and use the chassis management selection and basic POWER-based compute node management functions.

6.1.1 Flex System Manager startup wizard

FSM is based on an Intel compute node and has the same options for obtaining an initial console. These options are the IMMv2 remote console or using the supplied dongle and front port on the FSM node to connect directly to keyboard, display and mouse connected or a KVM console unit.

Note: At the time of this writing, IBM Flex System Manager is required for any configuration containing a Power Systems compute node. It is also anticipated that IBM Flex System Manager is preconfigured to manage the initial chassis. In that event, the steps in this section are not required unless IBM Flex System Manager is being reinstalled.



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.

Figure 6-1 IMMv2 login

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).

Chapter 6. IBM Flex System Manager initial configuration 115


2. After logging into the IMMv2, select Server Management from the navigation options, as shown in Figure 6-2 on page 116.

Figure 6-2 Remote control option in IMMv2



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-3 Starting remote console from IMMv2

Figure 6-4 shows the Java console window opened to the FSM appliance prior to power being applied.

Figure 6-4 FSM console in power off state



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.

Figure 6-6 FSM license agreement



5. Click the I agree button to continue, and the startup wizard Welcome window displays, shown in Figure 6-7 on page 119.

Figure 6-7 FSM Welcome window

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.

Figure 6-8 Setting the FSM date and time

7. Click the Next button.



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.

Figure 6-9 FSM system level user ID and password step

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.

Figure 6-10 FSM network topology options



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.

Figure 6-11 FSM LAN adapter configuration

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.

Figure 6-12 FSM IP address assignment



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.

Figure 6-13 FSM LAN adapter configuration continue option

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.

Figure 6-14 FSM host name and gateway configuration

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.

Note: It is expected that the host name of the FSM is available on the domain name server.



15.Enter the desired information as show in Figure 6-15 and click the Next button to continue.

Figure 6-15 FSM DNS services configuration

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.

Figure 6-16 FSM startup wizard summary window



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.

Figure 6-17 FSM system setup processing status

Figure 6-18 FSM system setup processing completion

Figure 6-19 FSM startup



Figure 6-20 FSM startup status

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.

Figure 6-21 FSM browser setup



Figure 6-22 FSM browser exception add



18.Click the Confirm Security Exception button, as shown in Figure 6-23.

Figure 6-23 FSM security exception confirmation

With the security exceptions cleared, the Login window of the IBM Flex System Manager GUI displays.



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.

Figure 6-24 FSM Login window

A Getting Started pop-up reminds you that initial setup tasks must be completed. See Figure 6-25 on page 128.

Figure 6-25 FSM Getting Started reminder



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.

6.2 Update the FSM

When first logging into the FSM web console, the Initial Setup screen will appear as shown in Figure 6-26. The goal of this screen is to provide a logical step through for updating Flex components.

Figure 6-26 FSM Initial Setup

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



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.

Figure 6-27 FSM Update Restart Message

6.3 Select chassis to manage

Most tasks in the IBM Flex System Manager can be reached by more than one method using the GUI. We’ll show a common method.

After the initial setup of the FSM, it discovers any available chassis. Selections can then be made as to which chassis will be managed by the current FSM. The steps are:

1. From the tabs shown across the top of the window, select the Home tab.

2. Select the Initial Setup tab to display the Initial Setup window.

3. Click the IBM Flex System Manager Domain - Select Chassis to be Managed link, as shown in Figure 6-28.

Figure 6-28 FSM initial setup window



A list of available chassis displays, as shown in Figure 6-29 on page 131.

Figure 6-29 FSM chassis selection for management

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.

Figure 6-30 FSM, manage chassis options

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.

Figure 6-31 FSM manage chassis Step 1



Figure 6-32 FSM manage chassis Step 2

8. After the successful completion of the manage chassis process, click the Show all chassis button as shown in Figure 6-33.

Figure 6-33 FSM manage chassis steps completed

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.

Figure 6-34 FSM with management domain updated

The Enterprise Chassis is now managed by the IBM Flex System Manager.

6.4 Acquire updates for chassis components

The IBM Flex System Manager Update Manager is responsible for obtaining and applying chassis, switch, system firmware, and certain operating system updates from IBM. In addition, the Update Manager is used to update the FSM itself. The updates can be obtained by Internet connection from the FSM, or they can be downloaded manually from IBM to another workstation, then copied to the FSM by FTP or SCP connection. After the files are



copied to the FSM, they must be imported into the Update Manager. First, we need to set up the Internet connection.

Direct Internet connection To set up and test the Internet connection, follow these steps:

1. Starting from the Home page, click the Plug-ins tab. The Plug-ins window lists all of the managers that are available on the FSM, as shown in Figure 6-35 on page 133.

Figure 6-35 FSM list of managers



2. From the list of managers, click Update Manager to display the window shown in Figure 6-36 on page 134.

Figure 6-36 FSM Update Manager



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.

Figure 6-37 FSM Update Manager Internet connection settings



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.

Figure 6-38 FSM testing Internet connection for Update Manager



A successful completion message displays, as shown in Figure 6-39 on page 137.

Figure 6-39 Successful Internet connect test for Update Manager

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.

Import update filesThe following describes how to import files into Update Manager. Given that the FSM is an appliance, methods of moving files directly to the FSM are not allowed. The file movement process must be initiated by the FSM from a user login either from the GUI or from a CLI.

The scp command is used to copy the update files from a local workstation to the FSM. The update files on the local workstation are obtained from IBM Fix Central. From an ssh login, you only have access to the /home/userid directory. Additional subdirectories can be created and files copied and removed from these sub directories, but a cd to the subdirectory is a restricted operation.



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.

Figure 6-40 FSM Update Manager



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.

Figure 6-41 Update Manager acquire updates selection

2. Click the radio button for Import updates.

When the selection is made to import updates from the file system, additional options apply.



3. Enter the path for the updates that were manually copied to the IBM Flex System Manager, as shown in Figure 6-42.

Figure 6-42 Import path to update files

4. Click the OK button, and the IBM Flex System Manager job scheduler displays, as shown in Figure 6-43 on page 140.

Figure 6-43 Starting the import updates job on FSM

For this example, the default Run Now radio button option is checked.



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.

Figure 6-44 Acquire updates: job status

6.5 FSM Eth1 network configuration

Best practices is to have separate management and data networks. In this section we will configure the data network on the FSM ethernet1 adapter.

First log on the FSM as shown Figure 6-45

Figure 6-45 FSM home tab



Select administration tab as shown Figure 6-46

Figure 6-46 FSM Administration tab

Select in Configuration tasks, select Configure Network as shown Figure 6-47

Figure 6-47 FSM COnfiguration tasks



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.

Figure 6-48 Select FSM Eth1 adapter

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.

Figure 6-49 IP address configuration



Select Continue Wizard then click Next, as shown in Figure 6-50.

Figure 6-50 Continue Wizard selection to configure only eth1

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.

Figure 6-51 Host and Gateway configuration

In the step above by selecting Eth1 the gateway is assigned to Eth1 interface.



If required you can define static routes as shown Figure 6-52.

Figure 6-52 FSM static routes

Enter the IP address of your DNS server, then click Next, as shown in Figure 6-53.

Figure 6-53 FSM DNS configuration



Check Summary, if everything is OK, as shown in Figure 6-54, click Next.

Figure 6-54 FSM network configuration summary

You can select to schedule this job or run it now. We selected Run Now as shown in Figure 6-55.

Figure 6-55 Run FSM network configuration job



During job running, you can click Display Properties to check the job status, as shown in Figure 6-56.

Figure 6-56 Network configuration job running

Reload the FSM page and click Continue to accept the website’s certificate as shown in Figure 6-57.

Figure 6-57 Reload the FSM webpage

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.



Log in to the FSM as USERID as shown in Figure 6-58.

Figure 6-58 FSM login

At the home page, you remark a warning symbol as shown in Figure 6-59 on the Administration tab, please select the Administration tab.

Figure 6-59 FSM home page



You get a message which explain that recent changes require a reboot as shown Figure 6-60. Select Restart IBM Flex System Manager Server.

.

Figure 6-60 Restart FSM message request

Click OK as shown in Figure 6-61.

Figure 6-61 Restart FSM confirmation



Click Run Now as shown in Figure 6-62 or schedule the FSM restart during a maintenance time frame.

Figure 6-62 Restart FSM run confirmation

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.

Figure 6-63 FSM restart information message

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.

6.6 Updating the CMM firmware

The FSM has the ability to push firmware updates to the Chassis Management Module (CMM). When a Flex Chassis is set to managed, as discussed in 6.3, “Select chassis to manage” on page 130, inventory is collected automatically. From this point on, when updates are imported (either manually or from the IBM site) a compliance check is run against the



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.

Figure 6-64 CMM Uninstalled Updates

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.

Figure 6-65 CMM Show and Install Updates page

Select the update, choose the Install button and an installation wizard will open.



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.

Figure 6-66 Install Wizards Restart screen



After choosing Next, the Summary screen will appear as shown in Figure 6-67 on page 153.

Figure 6-67 Install Wizard Summary



After choosing Finish, the choice of Run Now or Schedule will appear as shown in Figure 6-68.

Figure 6-68 Install Wizard Schedule Job

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.

6.7 Discovery and inventory collection

To manage a resource within an environment or view inventory data about it, that resource must first be discovered and, after access is granted, an inventory must be collected. The resource is recognized and added to the comprehensive list of native resources and native attributes for the system. Discovery and inventory collection are the two primary tasks that are used to connect to supported network resources and collect information about them.

DiscoveryDiscovery 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



resources within your environment, collect data about those resources, and establish connections with them.

Choosing which discovery method to useDiscovering your resources in the most efficient manner means deciding which method best suits your needs. Each method has advantages and disadvantages to consider.

To collect the inventory of a chassis component we need three actions: Discovery, then Grant Access, then Collect Inventory.

There are several paths to discover and collect the inventory on the IBM Flex System components. In this section we present the generic method with Discovery Manager, the subsequent sections of this chapter present different paths to discover the three main components in an Enterprise Chassis (CMM, compute nodes, and I/O modules).

Discovery protocolsA 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



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.



6.7.1 Discovery Manager

Discovery manager allows you to discover and connect to the systems at your site. This window displays an overview of all discovered systems, which ones you have access to, and which ones you have collected inventory from, and has options to explore all discovered resources, in order by category, as shown in Figure 6-69.

Select System discovery under Common tasks.

Figure 6-69 Discovery Manager

Note: You can run a discovery on a single IP address or on an IP address range

Discovered Systems Overview

Overview of systems with access granted

Commonly user functions



In our example, we will run a discovery on an IP range, therefore, select Range IPv4 address, as shown in Figure 6-70.

Figure 6-70 IP address range selection

Fill in your IP address range as shown in Figure 6-71.

.

Figure 6-71 Fill in IP address range for discovery

Note: You can also choose to schedule your discovery if required.



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.

Figure 6-72 Discovery job information

Wait till the progress bar has reached 100% meaning that the discovery is completed as shown in Figure 6-73.

Figure 6-73 Discovery completed

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.



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.

Figure 6-74 Granting access to the object

After requesting access to the object, to ensure that you access is granted, click General tab, as shown in Figure 6-75.

Figure 6-75 Access is granted



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.

Figure 6-76 Inventory collection

Your object is selected as Target systems. To begin inventory collection, click Collect Inventory, as shown in Figure 6-77.

Figure 6-77 Collect Inventory button



To begin the inventory collection, select Run Now and click OK button as shown in Figure 6-78.

Figure 6-78 Run collect inventory

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.

Figure 6-79 Collect inventory information



Wait till the job is completed as shown Figure 6-80.

Figure 6-80 Collect inventory completed

6.7.2 Manual inventory collection of the chassis

Considering that your chassis has already been discovered. Please refer to 6.3, “Select chassis to manage” on page 130.

Select CMM as shown in Figure 6-81.

Figure 6-81 Select CMM to manage

Note: When you select a CMM that means you select the chassis managed by this CMM.



Check you access status to the chassis, Select Action → Security → Configure Access as shown in Figure 6-82.

Figure 6-82 Check CMM access

Collect inventory on your chassis, select Action → Inventory → View and Collect Inventory as shown in Figure 6-83.

Figure 6-83 Chassis inventory collection



Click Collect Inventory button as shown in Figure 6-84.

Figure 6-84 collect chassis inventory continued

Click OK to run now or schedule the inventory collection as shown in Figure 6-85.

.

Figure 6-85 Run Now chassis inventory collection



A blue information square appears to inform you that the job is executed as shown in Figure 6-86.

Figure 6-86 Collect chassis inventory job information

You can track the progress as shown in Figure 6-87.

.

Figure 6-87 Collect inventory job running



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.

Figure 6-89 Collect chassis inventory job completed in General tab

6.7.3 Discovery of compute nodes

With IBM Flex System Enterprise Chassis, by discovering the CMM you discover all chassis hardware components managed by the CMM, but if you wish to discover an operating system on the node, or rediscover the node itself, you can follow the process described bellow.



Click Home tab as shown in Figure 6-90 on page 168, then click Compute Nodes - Check and Update Firmware.

To discover your server, click Discover as shown in Figure 6-90.

Figure 6-90 Discover component

Note: In this example we discover a compute node but you can also discover others components using this method using their IP addresses.



Enter the service processor IP address of your server, then click on “Discover Now” as shown Figure 6-91

Figure 6-91 Enter the IMM 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.

Figure 6-92 Job information

Note: For x86 nodes it’s the IMM’s IP address, and for the POWER7 compute nodes it’s the Service Processor’s IP address.



When the job is completed, your server has been discovered as shown in Figure 6-93.

Figure 6-93 Discovery completed

Click the Discovered Systems tab as shown in Figure 6-94.

Figure 6-94 Discovered systems



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.

Figure 6-95 Compute node with no access

Enter the admin user of your service processor server and the password, then click Request Access as shown Figure 6-96.

Figure 6-96 Server access request



When a green square with OK message appears, it means that you access is granted as shown in Figure 6-97.

Figure 6-97 Server access granted

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.

Figure 6-98 Collect Inventory

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.



If you need to collect the inventory on the node, click Browse as shown in Figure 6-99.

Figure 6-99 Browse selection for the target server

Select you server and click Add as shown in Figure 6-100.

Figure 6-100 Select object to collect inventory



When you server is in the selected list as shown in Figure 6-101, click OK.

Figure 6-101 Server select for inventory collect

Then you will see your server in the Target System list as shown in Figure 6-102, click Collect Inventory to launch your collection.

Figure 6-102 Collect inventory



Click OK to run the job now or you can schedule it if required as shown in Figure 6-103.

Figure 6-103 Collect Inventory job

An information window’s 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.

Figure 6-104 Collect Inventory job information



When the job is completed, the progress bar is 100% and the status is completed as shown in Figure 6-105.

Figure 6-105 Collect Inventory completed

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.

Figure 6-106 Collect inventory completed without any error in log



6.7.4 I/O Modules

In this subsection we discuss how to discover I/O modules. Select your chassis from the Chassis Manager view and click on it, as shown Figure 6-107.

Figure 6-107 Chassis selection

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.

Figure 6-108 Chassis physical view from the FSM



Select your chassis component, in our case we selected the switch module in bay 1 as shown in Figure 6-109.

Figure 6-109 Select IO module component from the physical view

Scroll down to the Action menu, select Action → Security → Configure Access as shown Figure 6-110.

Figure 6-110 Configure access



You can see that the general access status is Partial Access as shown in Figure 6-111.

Figure 6-111 I/O switch module partial access

Go to Action → Inventory → View and Collect Inventory as shown in Figure 6-112.

Figure 6-112 I/O module view and collect inventory



You can see that there are different protocols and most of them have no access. Click Request Access as shown in Figure 6-113.

Figure 6-113 IBM switch protocols

Enter credentials for your I/O module then click Request Access as shown in Figure 6-114.

Figure 6-114 Partial access on an Ethernet I/O module



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.

Figure 6-115 Partial access message

Scroll down to note that more protocols are enabled now as shown in Figure 6-116.

Figure 6-116 Partial access with more protocols

Note: Some protocols require to be enabled on the I/O module itself directly. For example, if SSH wasn’t 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.



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.

Figure 6-117 I/O module inventory collection

Click Collect Inventory as shown in Figure 6-118.

Figure 6-118 Collect Inventory



Click OK to run your collection task now, as shown in Figure 6-119.

Figure 6-119 Run job

Click Display Properties to see the job status as shown in Figure 6-120.

Figure 6-120 Job information



After a couple of minutes the job is completed and you can check the status as shown Figure 6-121.

Figure 6-121 Job completed

6.8 Operating system discovery, access and inventory

Updating firmware on compute nodes will be discussed in 6.9, “Updating compute node firmware”. Updates are applied in an online manner meaning in-band through the Operating System (OS) network data path from the FSM. For this reason, it is a prerequisite to discover and inventory the OS or hypervisor running on the compute node. Discovery of the OS is performed in the same way as discovering the compute nodes as discussed in 6.7.3, “Discovery of compute nodes” on page 167. The main difference is pointing to the IP address or hostname of the OS running on the compute nodes, requesting access with valid OS credentials and then perform inventory.

Once Inventory is collected from the OS, firmware information will be available so that updates can be properly downloaded and deployed as we will be discussed in 6.9, “Updating compute node firmware”.

6.9 Updating compute node firmware

Once OS is discovered, accessed and inventoried, as discussed in 6.8, “Operating system discovery, access and inventory”, firmware updates can be pushed. Once updates are imported as discussed in 6.4, “Acquire updates for chassis components” on page 132, a compliance check will occur automatically against all discovered systems. In the case of discovered Operating Systems, the FSM will compare its repository of updates against the firmware inventory available. Once compliance is complete, determining which systems need updates can be handled by reviewing the Show Needed Updates option or by creating a compliance policy.



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.

Figure 6-122 Show and Install Updates...

From here, a list of available updates can be reviewed, as shown in Figure 6-123.

Figure 6-123 Show and Install Updates List

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.



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



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.

Figure 6-125 Show Update Groups

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-126 Updates Groups

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



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.

Figure 6-127 Update Packages

By clicking the hyperlink name of a package, a General tab shows basic information about the package, as shown in Figure 6-128.

Figure 6-128 Update Package General Tab



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.

Figure 6-129 Update Package Documentation tab

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.

Figure 6-130 Step 3: Optional: Create and configure compliance policies



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, we’ve 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 we’ll add one by choosing the Add button.

Figure 6-131 Page with No Compliance Policy



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 we’ll select OK.

Figure 6-132 Policy Group

On the next page choose Save for the Compliance to take effect.



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.

Figure 6-133 Update Compliance



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.

Figure 6-134 Show and Install Updates

6.10 Updating I/O module Firmware

Downloading updates for I/O modules (e.g. Ethernet switches, Fibre Channel switches, etc) is similar to downloading updates for compute nodes as has been discussed in previous sections. In this scenario, we’ll show updates for an IBM Flex System EN4093 10Gb Virtual Fabric Scalable Switch.

While compute node firmware updates are pushed through the Operating System (OS) via specific OS protocols (DCOM for Windows, SSH for Linux), updates for I/O modules are pushed out over SFTP. For this reason, the I/O module must support SFTP, otherwise and external FTP or TFTP server may need to be provided.

A compliance policy can be configured for I/O Modules using the same method as discussed in the previous section. Additionally, the context sensitive menu can be used to show needed updates after that have been downloaded.



First, find the I/O module and ensure that access is OK as shown in Figure 6-135 on page 194.

Figure 6-135 I/O Module Access OK

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.

Figure 6-136 SSH OK



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.

Figure 6-137 Show and Install Updates for I/O Module

A list of needed updates will be shown as in Figure 6-138 which can be selected and installed.

Figure 6-138 Update List



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.

Figure 6-139 Update Message concerning TFTP

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.



6.11 Initial configuration of compute nodes and I/O modules

The first step to configure the compute nodes and I/O modules is by assigning an IP address to them. The best way to do this today is via the CMM. Log into the CMM web interface and go to Chassis Management → Component IP Configuration and click the device name of the components to apply IPv4 and/or IPv6 settings, as shown in Figure 6-140 on page 197.

Figure 6-140 Component IP Configuration

6.12 Manage Feature-on-Demand keys

Features on Demand keys enable you to view and install optional features for IBM Flex System Manager management software and managed IBM Flex System resources.

You can only enable Features on Demand keys on compute nodes through the management software if the compute node is configured to boot a UEFI-compatible operating system. If the compute node was configured in the Setup Utility to boot in legacy mode, you cannot activate Features on Demand keys.

Install Features on Demand keys through the management software web interface. If you use the IMM2 interface or any other method to import and install Features on Demand keys, the activated software will not work until you restart the management software.

The Manage Features on Demand Keys page has a view list, from which you can select either IBM FSM keys or All keys. The "FSM keys" view enables you to add and remove only the keys that apply to the management software. The "All keys" view enables you to add and remove keys from the management software and managed compute nodes.

To manage the Features on Demand keys that are installed, or to import a new key, complete the steps described below.



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.

Figure 6-141 Features on Demand tasks

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.

Figure 6-142 FSM Keys



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.

Figure 6-143 All Keys

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.

Figure 6-144 Configuration Templates



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.

Figure 6-145 Configuration Template creation



In the Wizard, there are two choices as shown in Figure 6-146 on page 201.

Figure 6-146 Key Redemption Method



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.

Figure 6-147 KMS Login



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.

Figure 6-148 Upload Key Files



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.

Figure 6-149 Automatic Reboot

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.

Figure 6-150 FoD key deployment



6.13 Discover and manage V7000 (Storage Control)

As part of the comprehensive consolidated management approach, storage management is integrated into the FSM. After your storage appliance is discovered and access requested by the FSM, you can start managing it as shown in Figure 6-151.

Figure 6-151 Flex System Manager Storage Management

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.director.storage.helps.doc%2Fconfiguring_v7000_or_svc_storage.html


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.storage.helps.doc%2Fconfiguring_v7000_or_svc_storage.html


Please check the firmware level on the V7000 as shown in Figure 6-152.

Figure 6-152 Firmware level on V7000

Note: Automatic discovery of the Storwize V7000 and the CLI commands require that the V7000 software version is 6.3.0.0 or later.

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.



Check that your V7000 isn’t 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.

Figure 6-153 Storage Manager (V7000) is visible



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.

Figure 6-154 V7000 management IP address

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

Add a new V7000If your V7000 isn’t managed by any Flex System Management Node or others IBM System Management Software, from the management software command-line interface (CLI), enter the command:

smcli manageV7000 -i V7000_IP_address -u admin_user_ID -p admin_password

In this command, V7000_IP_address is the IP address of the V7000, and admin_user_ID and admin_password are the administrator’s user ID and password.

Manage an existing V7000 from several FSM

If you need to manage a V7000 from others Flex System Manager, complete the following steps for each additional management node, as described below.

Important: If you have more than one management node (FSM) on your network, you can use the manageV7000 command only on the initial management node (FSM) that manages the V7000. If you run the manageV7000 command on an additional management node, the V7000 key that was generated by the initial management node is replaced on the V7000 by a key that is generated by the subsequent management node.


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.acc.commontasks.doc%2Fcommontasks_navigating_fsm.html



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.

Figure 6-155 copy USERID key to an other FSM node

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.

Remove an existing V7000 To remove an existing V7000 from the list of managed devices, enter the command:

smcli unmanageV7000 -i V7000_IP_address

where V7000_IP_address is the IP address of the V7000.

6.13.2 Collect inventory on the discovered V7000

Discovery and inventory collection must be run before you can display storage systems in Storage Control. After you have run manageV7000 command line, you V7000 has been discovered by your Flex System management node and you should see a new farm object type with OK access in Resource Explorer as shown in Figure 6-156.

Figure 6-156 Storage Farm object discovered



Collect inventory on V7000 storage by clicking View and Collect Inventory as shown in Figure 6-157.

Figure 6-157 View and Collect Inventory on Storage Farm object

Click Collect Inventory button to begin the inventory collection as shown in Figure 6-158.

Figure 6-158 Collect Inventory on V7000 Farm Object discovered



Click OK to run the collection task as shown in Figure 6-159.

Figure 6-159 Collection task on Storage Farm Object

A blue box message will appears to say that the job has been started and created successfully as shown in Figure 6-160.

Figure 6-160 Storage farm inventory collection launched successfully



Wait until it is completed as shown in Figure 6-161.

Figure 6-161 Collect Inventory on a farm object completed

If some errors appear, click the Log tab to get more information, as shown in Figure 6-162.

Figure 6-162 Storage farm Inventory Collect log



6.13.3 Overview of Storwize V7000 systems management

Your storage devices can be viewed and managed in one central location. The Storage Management Summary page provides an introduction to your storage systems. The Storage Management Summary is invoked from the Plug-ins tab of the Home page as shown Figure 6-163 on page 213.

Figure 6-163 Go to Storage Control from Home page

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



� 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.

Server to Storage Mapping View Server to Storage Mapping View displays a table that shows what storage resources are associated with your virtual servers. After selecting this task, you will choose the servers to view, as shown in Figure 6-165.

Figure 6-165 Server to Storage view



Storage to Server Mapping view This task displays a table that shows the virtual server disks and which storage pools contain them. After selecting this task, you will choose the storage resources to view as shown in Figure 6-166.

Figure 6-166 Storage to Server view

View and Manage Storage Volumes This task work with your currently-defined storage volumes to make changes, add or delete them. Details about status and capacity are also available.

This task is managing the assignment of network storage to individual systems, from the context of a specific host system. You can create a new volume from network storage to be assigned to a selected host system, or delete a volume that is currently assigned to a selected host system. The create volumes function simplifies the allocation process by determining the best fit storage system, and creating any necessary RAID arrays automatically.

View and Apply Storage Templates This task works with storage templates, which are predefined images for certain storage devices. Storage templates are used to ensure uniformity among common storage elements, as well as save time and effort on repetitive tasks.



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.

Figure 6-167 Storage configuration templates

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.

Figure 6-168 Capacity details

Local Storage that is local to only one system, and therefore dedicated to only that system.



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.

Figure 6-169 Dedicated Local Storage

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.

Figure 6-170 Network storage



6.13.4 External FC SAN switch discovery

Figure 6-171 on page 218 shows our test environment. One SAN switch installed in the chassis has a pass through capability and is connected to the IBM SAN B80 switch.

Figure 6-171 Test SAN environment

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

FC31718Gb SAN Pass thru

Brocade 80BSAN Switch

Storwize V7000 Data N/W

Fiber Channel

N/W Fiber Channel

SAN switch configuration

Chassis

VMControl

StorageManagement

Power Systems

Management

Plug-ins

IBM Fabric Manager

SMIAConfiguration

Tool

Applications



Figure 6-172 shows Applications main page. Click Start to run SMIA.

Figure 6-172 Application main page in the FSM

Log in your external switch (Figure 6-173 on page 219 shows SAN switch main page). Click Switch Admin.

Figure 6-173 SAN switch main page

Note the IP address in the Network tab as shown Figure 6-174 on page 219.

Figure 6-174 Ethernet IP address of the IBM SAN B80 switch



Check that SMIA is running as shown in Figure 6-175. Click SMIA Configuration Tool.

Figure 6-175 Check SMIA status

Type SAN switch credentials as shown in Figure 6-176.

Figure 6-176 SAN switch login page



From the Home tab left click the Fabric Discovery Option as seen in the Figure 6-177.

Figure 6-177 SMIA main page

Click the Add button as shown in Figure 6-178 on page 221.

Figure 6-178 Discover Fabrics Main page



Provide a Fabric name for the TOR switch, IP address and login credentials, defaults are admin/password, as shown in Figure 6-179.

Figure 6-179 Add Fabric Discovery page

Figure 6-180 shows added SAN switch.

Figure 6-180 Discover Fabrics Main page



Left click the CIMOM tab from the tool’s main interface as shown in Figure 6-181.

Figure 6-181 SMIA main page



Check the SMI Agent port (25989), as shown in Figure 6-182 on page 224.

Figure 6-182 CIMON page

From the FSM CLI enter the mkdatasource command to add the data source as shown in Figure 6-183.

Figure 6-183 FSM CLI page



Run collect inventory on a farm as shown in Figure 6-184 on page 225.

Figure 6-184 Run a collect inventory

Check logs as shown Figure 6-185.

Figure 6-185 Check logs



Figure 6-186 shows the new switch object added.

Figure 6-186 Check SAN switch added

6.14 Configuring the network parameters (Network Control)

IBM Flex System Manager allows you to have full management of your network and network devices as long as the network devices are discovered and have full access. The Network Control window is shown in Figure 6-187.

Figure 6-187 Manage Network Devices



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:




Draft Document for Review August 18, 2012 12:15 am Managing_HW_FSM.fm

Chapter 7. Managing chassis hardware components withIBM Flex System Manager

This chapter discusses FSM capabilities for chassis hardware components management. FSM offers a wide range of hardware management options. In this chapter we will operate with the FSM graphical interface and will describe common hardware management interfaces and tasks such as:

� Chassis maps

� Monitor system status and health (events, monitors, thresholds)

� Automation plans

� Service and Support Manager

� Remote presence (power control and remote console)

7

Note: For the purpose of our discussion in this chapter, we simulated a high temperature problem within the chassis in our lab.


Managing_HW_FSM.fm Draft Document for Review August 18, 2012 12:15 am

7.1 Using the Chassis Manager

View chassis properties and manage a chassis with the Chassis Manager and Chassis Map in the IBM Flex System Manager management software web interface. Click Chassis Manager in the management software web interface Home page to open a list of chassis that are under management. See Figure 7-1.

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.

Figure 7-2 Managed Chassis list

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



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.

Figure 7-3 Chassis Map - graphical view

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


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



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.

Figure 7-7 Active Status page for selected compute node

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.

Figure 7-8 Active Status entry details page



Select the Recommendation tab to read more on the possible root cause and recommendations for fixing the problem. See Figure 7-9.

Figure 7-9 Active Status entry Recommendation details page

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.

Figure 7-10 Infocenter page on selected active status event message



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.

7.2 Using Event Log

An event is an occurrence of significance to a task or resource. Examples of events include the completion of an operation, the failure of a hardware component, or the exceedance of a processor threshold. The Event Log task displays all events that the FSM receives from any resource to which you have authority to view events.

Use the following method to open Event Log for events reported by a specific source:1. Select a component from the Chassis Map.2. Perform one of the following actions:

– Select Actions → System Status and Health → Event Log as shown in Figure 7-11 on page 235.

Figure 7-11 Actions menu of selected compute node navigating to Event Log task



– 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



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.

Figure 7-14 Global Find box on Chassis Map page

� 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.

Figure 7-15 Event Log option in navigation area



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.

Figure 7-16 Event filter drop-down list

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.



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.

Figure 7-18 Filter row in the Event Log table



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.

Figure 7-19 Event Log Filter message box

All events containing the string hot in their Event Text are shown, as in Figure 7-20.

Figure 7-20 Filtered Event Log table

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.

7.3 Creating an event filter from an event

A filter specifies one or more events that you want your event automation plan to process. The event automation plan ignores any event instances that do not meet the specifications of the filter. Typically, you will use the common event filters that are provided in the Event Automation Plan wizard. Occasionally there are situations where you will want to create a sophisticated event filter. Using advanced filters, you can specify details for an event that covers very specific problems and occurrences.



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.

Figure 7-21 Create Simple Event Filter window

Click Ok and acknowledge the successful event filter creation. Click on Close Message as shown in Figure 7-22 on page 241.

Figure 7-22 Simple event filter successful creation message box



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.

Figure 7-23 Event filters page

7.4 Define event actions

Event actions specify the action that FSM takes in response to a specific event or events. Using the Event Automation Plan wizard, you can easily create an event automation plan that will send you an e-mail or pager notification in response to an event. Additionally, the Event Automation Plan wizard provides other advanced event actions that you can use.

In our example we will use the Create Action wizard to create an event action that will later be used in an automation plan. The event action will be sending an e-mail.



In the IBM Flex System Manager Web interface navigation area, expand Automation and click Event Actions, as shown in Figure 7-24.

Figure 7-24 Event Actions page

Click Create to start the Create Action window and select Send an e-mail (Internet SMTP) as shown in Figure 7-25.

Figure 7-25 Actions list in Create Action window



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.

Figure 7-26 Send an e-mail action details in Create Action window

Click Test to ensure that the action is properly configured. Click OK.



The newly created event action appears on the Event Actions list, as seen in Figure 7-27 on page 245.

Figure 7-27 Event Actions page

7.5 Automating tasks with event automation plans

Use event automation plans to automate tasks in your systems management environment. By creating event automation plans and applying them to specific systems, you can be notified by e-mail, for example, when a specified threshold is reached or a specified event occurs. Or, you can configure an event automation plan to start a program on a system in response to the event. These plans are composed of event filters and event actions. The plans are triggered by events. Event automation plans are a powerful feature to automate a huge variety of manual tasks in your environment and subsequently reduce labour costs.

We already identified an event, created an event filter for it and defined an event action. Now we will automate triggering the action based on the filtered event. In our specific example, we will setup an automated e-mail notification in case a warning event occurs indicating improper chassis hot air circulation.

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.



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).

Figure 7-28 Event Automation Plans page



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.

Figure 7-29 Create Event Automation Plan Wizard Welcome page



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



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.

Figure 7-31 Create Event Automation Plan Wizard Targets page

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.



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.

Figure 7-32 Create Event Automation Plan Wizard Events page



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



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



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.

Figure 7-36 Create Event Automation Plan Wizard Summary page

The event automation plan is saved and is displayed on the Event Automation Plans page, as shown in Figure 7-37.




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.

Figure 7-38 Event Automation Plans Actions menu

View the automation plan properties and click Edit if you need to change any settings. See Figure 7-39.

Figure 7-39 Event Automation Plan properties page



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.



To activate Electronic Service Agent, navigate to the FSM’s Home page. Click the Plug-ins tab, as shown in Figure 7-40.

Figure 7-40 Plug-ins tab of FSM Home page

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



Click Next on the Welcome page (Figure 7-42 on page 257).

Figure 7-42 Getting Started with Electronic Service Agent Welcome page



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



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



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



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



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



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.

Figure 7-49 Service and Support Manager page



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

Figure 7-50 Service and Support Manager Settings

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.director.help/esa_kickoff.html

7.7 Integrating FSM with your enterprise monitoring system

If you have an enterprise monitoring system already implemented in your environment, you can create event automation plans to forward FSM events to it. FSM offers several predefined actions to help you do that. Refer to 7.4, “Define event actions” on page 242 and instead of selecting Send an e-mail (Internet SMTP), you can choose one of the following advanced event actions:

� Send an IBM Tivoli Enterprise Console® event

Once configured, this event action will forward FSM events to your Tivoli Enterprise Console (TEC) server in the appropriate format that TEC can accept.

� Send an SNMP trap reliably to a IBM NetView® host


http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.esa.director.help/esa_kickoff.html


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.director.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.


http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.director.automation.helps.doc/fqm0_c_ea_actions.html


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.

Figure 7-51 Monitors page



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.

Figure 7-52 Monitors Context Chooser

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.



Click Common Monitors or select it and click Show Monitors, as shown in Figure 7-53.

Figure 7-53 Monitor Views page with Common Monitors selected

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



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.



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.

Figure 7-56 Threshold page



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 system’s 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



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



Click Next on the Welcome page. Enter a Name and Description for the automation plan, see Figure 7-61 on page 273.




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.




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.




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



Review the Summary page (Figure 7-65) and click Finish.




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.



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.

Figure 7-67 Event Log page



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.

Figure 7-68 Thresholds page

7.9 Remote management

With the Remote Control application in IBM Flex System Manager management software, you can manage X-Architecture compute nodes as if you were at a local console. This will come useful in many cases, especially when you do not have any other way of accessing your system remotely (lack of OS, network issue, etc).

Note: Remote Control is a Java Web Start application that requires the IBM or Oracle/Sun Java Runtime Environment (JRE) plug-in, version 6.0, update 18 or later. You must obtain and install the JRE plug-in before you can use the Remote Control application.



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.

Figure 7-69 Common Actions on the Chassis Map page

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.



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.

Figure 7-70 FSM Remote Control connection type dialog box



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.

Figure 7-71 Remote Control console window



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.

Figure 7-72 Remote Control toolbar

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.

Figure 7-73 Mount Remote Media window



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.

Figure 7-74 Open dialog box

The image file path appears in the list of devices available for mounting, as shown in Figure 7-75. Click Mount All.

Figure 7-75 Mount Remote Media window showing Selected Resources



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.

Figure 7-76 Mount Remote Media window showing mounted resources



Open My Computer in Windows, to ensure that you can access the mounted image as a CD Drive (see Figure 7-77).

Figure 7-77 Windows Server console showing mounted image



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.

Figure 7-78 Power Controls menu on the Remote Controls toolbar



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


http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.8731.doc/using_remote_access.html

http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.8731.doc/using_remote_access.html

Draft Document for Review August 18, 2012 12:15 am Managing_KVM_FSM.fm

Chapter 8. Managing KVM environment with IBM Flex System Manager

This chapter is focused on managing the Red Hat Enterprise Linux’s KVM-based virtualization environment with IBM Flex System Manager. We discuss how to enable KVM to be managed by FSM, and how to perform typical virtualization management tasks including virtual machine’s lifecycle management, automation capabilities, and maintenance.

The following topics are covered:

� 8.1, “KVM management architecture” on page 292� 8.2, “KVM platform agent installation” on page 292� 8.3, “Image repository for KVM” on page 298� 8.4, “Create SAN Storage system pools” on page 318� 8.5, “Create KVM server system pools” on page 321� 8.6, “Overview of Network system pools” on page 329� 8.7, “Operate a KVM virtual infrastructure with FSM” on page 330

8


Managing_KVM_FSM.fm Draft Document for Review August 18, 2012 12:15 am

8.1 KVM management architecture

If you wish to install an environment using the NFS storage based solution, please refer the URL: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_r_kvm.html

SAN Storage configuration looks more complex than the NFS solution but the block storage based model offer better performance, more functionality and flexibility.

The picture shown Figure 8-1 illustrate a KVM virtualization environment with SAN storage.

Figure 8-1 Select option to install KVM host

Before starting the implementation of the SAN storage based solution, please read “SAN storage based model” on page 99.

8.2 KVM platform agent installation

To manage the KVM host from IBM Flex System Manager VMControl, you need to manually install an agent called the KVM Platform Agent. You cannot use Deploy Agent wizard on the the IBM Flex System Manager to deploy this agent.

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.





To allow FSM communications to the KVM platform agent, perform the following steps:

1. Disable SELinux as shown in Figure 8-2.

Figure 8-2 Disable SELinux

2. Configure iptables as shown in Figure 8-3.

Figure 8-3 Configure iptables

3. Configure Yum on your system, please refer the URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html

Note: You can also configure SELinux in “permissive” mode if require for security reason.

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.

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.

Chapter 8. Managing KVM environment with IBM Flex System Manager 293

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html





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.

Figure 8-4 Check date on KVM host

8.2.2 KVM Platform Agent installation

To install KVM Platform Agent, perform the following steps:

1. Remove some packages using the following command:

yum -y erase tog-pegasus libcmpiutil libvirt-cim sblim-cmpi-nfsv3 sblim-cmpi-fsvol sblim-gather-provider sblim-gather sblim-cmpi-base openslp

2. Download KVM Platform Agent from the following URL (see Figure 8-5):

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

Figure 8-5 KVM Platform Agent download

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.

Figure 8-6 Uncompressed agent previously copied in /tmp

Note: If an NTP server is configured in our network, please configure it on all your KVM hosts and on the FSM also.




4. Launch KVM Platform Agent installation as shown in Figure 8-7 and Figure 8-8

Figure 8-7 KVM PA agent installation screen 1

Figure 8-8 KVM PA Agent installation screen 2



Figure 8-9 dependencies error example

Your KVM Platform Agent installation is completed.

8.2.3 KVM host discovery, granting access and inventory collection

KVM host discoveryGo to Discovery Manager as shown Figure 8-10 and click System Discovery.

Figure 8-10 Discovery Manager

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.

Figure 8-11 KVM host enter IP address for discovery

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.

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.



Wait till the job is completed as shown in Figure 8-12.

Figure 8-12 KVM discovery progress

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.

.

Figure 8-13 Discovered KVM host system

Grant access to your KVM host using root credentials as shown in Figure 8-14, then click on your host.

.

Figure 8-14 KVM host operating system access granted



Select Action menu and run Collect Inventory as shown in Figure 8-15.

Figure 8-15 Collect Inventory on KVM host

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.

Figure 8-16 Collect inventory on KVM host completed

8.3 Image repository for KVM

To set up the image repository for IBM FSM/VMControl with SAN storage, several pieces must be in place. The section bellow describe you the steps to perform.

In this chapter we will cover the implementation of the KVM SAN storage based solution. If you wish to install an environment using the NFS storage based solution, please refer the URL: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_repositories_kvm.html


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_repositories_kvm.html





The picture shown in Figure 8-17 illustrate an image repository for a KVM virtual environment with SAN storage.

Figure 8-17 KVM image repository with SAN storage

8.3.1 Preparation

Follow these steps to establish an image repository for KVM using the SAN-based storage.

1. Install your KVM host following the step in section 8.2.1, “Preparation” on page 292

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.

Note: Stop at the end of the section 8.2.1, “Preparation” on page 292



2. Install prerequisite RPMs required to install Linux x86 Common Agent as shown in Figure 8-18 and Figure 8-19.

Figure 8-18 Linux x86 common agents RPMs prerequsites

Figure 8-19 Linux x86 common agents RPMs prerequisites



8.3.2 Common Agent installation on a KVM host image repository

To install Common Agent, perform these steps:

1. Allow ports required by the Common Agent as shown in Figure 8-20.

Figure 8-20 Open ports for CAS

2. Download KVM Common Agent from the following URL (see Figure 8-21):


Figure 8-21 Linux Common Agent x86

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







4. Launch Common Agent installation as shown in Figure 8-22.

Figure 8-22 Common Agent installation on the KVM future image repository server

5. Wait till the Common Agent is completed as shown in Figure 8-23.

Figure 8-23 Common Agent installation on the KVM future image repository server.



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.

Figure 8-24 KVM hosts with common agent discovery

7. Click OK to run the job now and click Display Properties to check the job progress status as shown in Figure 8-25.

Figure 8-25 KVM hosts with common agent discovery completed



8. Grant the access to the discovered system, click Discovered Systems tab as shown in Figure 8-26.

Figure 8-26 Discovered systems

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.

Figure 8-27 Access granted on KVM image repository



10.Select Collect Inventory on the system as shown in Figure 8-28 then click OK to run the job now.

Figure 8-28 Collect inventory

11.Click Display Properties button as shown in Figure 8-29 to check the progress.

Figure 8-29 Information blue box



12.Wait till the collect is completed as shown Figure 8-30.

Figure 8-30 Collect inventory completed

You successfully completed common agent installation, discovery, and inventory collection on KVM repository host.

8.3.3 Subagent installation on a KVM host image repository

You can access and install IBM Flex System Manager VMControl subagents using the IBM Flex System Manager Agent Installation Wizard. You can start this wizard from the VMControl Summary page or from the IBM Flex System Manager Release Management task or from Resource Explorer by selecting your system as shown Figure 8-31 on page 306.

Figure 8-31 KVM image repository: Operating system



Go to Actions menu, select Release Management → Install Agent as shown in Figure 8-32.

Figure 8-32 Install VMControl image repository sub agent

You get a welcome screen for Agent Installation as shown in Figure 8-33, click Next.

Figure 8-33 Install VMControl image repository sub agent

Click Common Agent Subagent Packages as shown in Figure 8-34.

Figure 8-34 Select Common Agent Subagent Packages group



Select CommonAgentSubagent_VMConrol_CommonRepository-2.4.1 as shown in Figure 8-35, then click Next.

Figure 8-35 CommonAgentSubagent_VMConrol_CommonRepository-2.4.1

Select your future image repository system which is an object type Operating System Linux as shown in Figure 8-36, then click Next.

Figure 8-36 Select Image repository host operating system target



Check the summary which show you the agent and the target for installation as shown in Figure 8-37, then click Finish button.

Figure 8-37 Agent installation summary

Click OK button to run the job now as shown in Figure 8-38.

Figure 8-38 Run agent installation job

Click Display Properties as shown in Figure 8-39 to check the job status and wait until status is completed.

Figure 8-39 Display Properties

8.3.4 Host mapping

When you deploy to a new virtual server on Linux Kernel-based Virtual Machine (KVM), the disks in the virtual appliance are assigned to the disks in the virtual server based on disk order.



Log on to the V7000 storage GUI as shown in Figure 8-40.

Figure 8-40 V7000 GUI

Click Hosts icon as shown Figure 8-41.

Figure 8-41 V7000 host view

You see that there is no host define for your KVM hosts as shown in Figure 8-42.

Figure 8-42 hosts view before define KVM host mapping

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.



Click Create Host, then click Fibre Channel Host as shown in Figure 8-43.

Figure 8-43 create Fiber Channel host



Select your WWN and specify a Host Name as shown in Figure 8-44.

Figure 8-44 select KVM host WWN



Click Add Port to List as shown in Figure 8-45.

Figure 8-45 Add KVM WWN to Port Definitions list



Click Create Host to launch the host map creation as shown in Figure 8-46.

Figure 8-46 Host map creation

Wait till the creation task is completed as shown in Figure 8-47 on page 314.

Figure 8-47 Host map creation



Go back to the host view to check that your host has been created as shown in Figure 8-48.

Figure 8-48 Host map creation checking

To get more informations on storage, please refer to the link: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_storage_paths.html

8.3.5 Discover and manage V7000 storage system

Refer to 6.13, “Discover and manage V7000 (Storage Control)” on page 205 for the information on how to discover and manage V7000 storage system.

8.3.6 Discover and manage SAN switches

Refer to 6.13.4, “External FC SAN switch discovery” on page 218 for the information on how to discover and manage SAN switches.

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.

Figure 8-49 Create image repository

Note: You need to repeat this process on each KVM host.


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_storage_paths.html


You are redirected to the Welcome screen as shown in Figure 8-50. Click Next.

Figure 8-50 create image repository Welcome screen

Specify the name of you KVM image repository as shown in Figure 8-51, then click Next.

Figure 8-51 Give a name to the KVM image repository



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.

Figure 8-52 select image repository system

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.

Figure 8-53 Select virtual appliance storage



Check the summary and click Finish to complete the image repository creation as shown in Figure 8-54.

Figure 8-54 Image repository creation summary

A blue information windows appears, click Display Properties as shown in Figure 8-55.



Figure 8-56 image repository creation completed

8.4 Create SAN Storage system pools

Before to start on Storage System pools please refer to the URL: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_getting_started_system_pools.html


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_getting_started_system_pools.html





Go to VMControl plug-in as shown Figure 8-57.

Figure 8-57 VMControl main page

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.

Figure 8-58 No storage system pools available

The Welcome page to create storage system pool appeared as shown in Figure 8-59.

Figure 8-59 Welcome page to create Storage System pools



Specify the name to assign to the Storage system pool as shown in Figure 8-60.

Figure 8-60 Storage system pool name

Select the storage system that you want to assign to the storage system pool as shown in Figure 8-61.

Figure 8-61 Select Storage Subsystem

Check the summary as shown in Figure 8-62 and click Finish.

Figure 8-62 Storage system pool creation summary



Wait till the storage pool is created as shown in Figure 8-63.

Figure 8-63 Storage system pool creation

A blue information window appears as shown in Figure 8-64, click Display Properties.

Figure 8-64 Display job properties window

At the end of this process your Storage System Pool will be created.

8.5 Create KVM server system pools

Before to start on Server system pools please read the information found at the URL: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_getting_started_system_pools.html

For prerequisites, refer to the following URL: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.acc.commontasks.doc%2Fcommontasks_navigating_fsm.html









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.

Figure 8-66 Server system pool member list

You are redirected to the Welcome page to create a Server system pool as shown in Figure 8-67, then click Next.

Figure 8-67 Server system pool Welcome page



Specify a name to assign to the server system pool as shown in Figure 8-68, then click Next.

Figure 8-68 Server system pool name

Under Pooling Criteria, check Only add hosts capable of live virtual server relocation as shown in Figure 8-69, then click Next.

Figure 8-69 Pooling criteria



Select a host as initial host to initiate the creation if the server system pool as shown in Figure 8-70, then click Next.

Figure 8-70 Initial server system pool host

Add the host to the list as shown in Figure 8-71, then click Next.

Figure 8-71 Add initial host



Select the shared storage system that you want to assign to the server system pool as shown in Figure 8-72, then click Next.

Figure 8-72 Assign a storage system to server system pool

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.

Figure 8-73 Additional server system pool

Select the optimization mode desired as shown in Figure 8-74, then click Next.

Figure 8-74 Server system pool optimization choice



Check the summary as shown in Figure 8-75.

Figure 8-75 Check summary

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.

Figure 8-77 Server system pools views

8.5.1 Add Host to an existing Server system pool

To increase your Server system pool availability or to increase the amount of resources in your pool, you need to add CPU and memory. To add memory and CPUs you need to add additional KVM hosts in your Server system pool as described in the section bellow.



Go to Server system pools view as shown in Figure 8-78.

Figure 8-78 Add Hosts to a server system pool

Select you Server system pool, click KVMpool → Availability → Add Hosts as shown in Figure 8-79.

Figure 8-79 Add Hosts

The Welcome screen for adding hosts appears as shown in Figure 8-80, then click Next.

Figure 8-80 Welcome add hosts screen



Select the host that you want to add to your server system pool as shown in Figure 8-81, then click Next.

Figure 8-81 Select hosts to add to an existing server system pool

Check the Summary and click Finish as shown in Figure 8-82.

Figure 8-82 Summary

Click Display Properties as shown in Figure 8-83.

Figure 8-83 Display job properties




Figure 8-84 Job completed

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.

Figure 8-85 KVM server system pool

8.6 Overview of Network system pools

Before starting with Network system pools please refer to the URL: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_c_learnmore_getting_started_system_pools.html

A network system pool logically groups virtual and physical networks to so you can manage them as a single network.

Network system pools simplify and automate network configuration tasks for virtual servers. You can manage the network connections of the pooled network systems to ensure network connectivity across a set of network switches. Use network system pools to ensure day-to-day virtual server connectivity for the following tasks:

� Automatic network port configuration (for example, VLANs and ACLs)

� Automatic MAC address migration

� Automatic Layer 2 profile migration (VLANs, ACLs)





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.

Figure 8-86 SNMP access

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=%2Fcom.ibm.sdnm.adv.helps.doc%2Ffnc0_r_panel_network_ctrl_NSP_learn_more.html

8.7 Operate a KVM virtual infrastructure with FSM

The following tasks can be performed when operating the KVM infrastructure:

� 8.7.1, “Import virtual appliance”� 8.7.2, “Deploy a Virtual Appliance to create a Virtual Server” on page 335� 8.7.3, “Capture a virtual server” on page 342� 8.7.4, “Relocate virtual servers” on page 351


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.sdnm.adv.helps.doc%2Ffnc0_r_panel_network_ctrl_NSP_learn_more.html

http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.sdnm.adv.helps.doc%2Ffnc0_r_panel_network_ctrl_NSP_learn_more.html


8.7.1 Import virtual appliance

Go to the VMControl plug-in tab as shown in Figure 8-88.

Figure 8-88 VMControl plug-in main screen

Select Virtual Appliances tab as shown in Figure 8-89, then click Import in the Common tasks list.

Figure 8-89 Virtual Appliances tab

You are redirected to the import appliances Welcome page as shown in Figure 8-90. Click Next to start the import process.

Figure 8-90 Import appliances Welcome page



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.

Figure 8-91 Import appliance source path file

If your wish to not import the Digital Signature check the box as shown in Figure 8-92, then click Next.

Figure 8-92 Digital Signature

By default the original appliance name is assigned, as shown in Figure 8-93, but you can specify another one, then click Next.

Figure 8-93 Assign the name to a virtual appliance



Select the image repository in which you want to import the virtual appliance as shown in Figure 8-94, then click Next.

Figure 8-94 Appliance repository

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.

Figure 8-95 Version Control

Check the Summary as shown in Figure 8-96, then click Next.

Figure 8-96 Import appliance summary



Select Run Now and click OK to start the virtual appliance import process as shown in Figure 8-97.

Figure 8-97 Run appliance import now

After that, click Display Properties, you are redirected to Active and Scheduled jobs window as shown in Figure 8-98.

Figure 8-98 Import Appliance Job progress

Note: Appliance import times may vary depending on where the appliance resides in the network.



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.

Figure 8-99 Virtual Appliances view

8.7.2 Deploy a Virtual Appliance to create a Virtual Server

You can deploy virtual appliances in the Linux Kernel-based Virtual Machine (KVM) virtualization environment in IBM Flex System Manager VMControl to new or existing virtual servers or to server system pools.

Prerequisites: http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_r_kvm_deploy_reqs.html

To deploy a virtual appliance, go to the main page of the VMControl Plug-in as shown in Figure 8-100, then click Deploy Virtual Appliances under Common Tasks list.

Figure 8-100 VMControl plug-in main page


http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.director.vim.helps.doc%2Ffsd0_vim_r_kvm_deploy_reqs.html


The Welcome screen for the Deploy Virtual Appliance appears as shown in Figure 8-101, click Next.

Figure 8-101 Deploy Appliances Welcome page

Select the appliance that you want to deploy as shown in Figure 8-102, then click Next.

Figure 8-102 Virtual appliances catalogue

Note: You can see appliances available from different image repositories, as shown in Figure 8-102.



Select the Target to deploy the new virtual server as shown Figure 8-103 and click Next.

Figure 8-103 Target to deploy a virtual server

Specify a Workload Name as shown in Figure 8-104 and click Next.

Figure 8-104 Workload name

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.

Note: A Workload in FSM is a group which contain one or several virtual servers.



Specify a name for your Virtual Server as shown in Figure 8-105, then click Next.

Figure 8-105 Virtual Server name

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.

Figure 8-106 Assign disk

Select the Storage System Pool configured previously, as shown in Figure 8-107, then click OK.

Figure 8-107 select storage pool

Note: By default storage volume (disk1) is selected as shown Figure 8-106.



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.

Figure 8-108 Storage mapping

Select the Virtual Network Adapter to create a virtual Ethernet adapter on your virtual server, as shown in Figure 8-109, then click Next.

Figure 8-109 Network Mapping



You can preconfigure several parameters like the name, the network configuration of your virtual server as shown Figure 8-110, then click Next.

Figure 8-110 Virtual server preconfiguration

Check the Summary and click Finish as shown in Figure 8-111.

Figure 8-111 Virtual Server creation Summary



Click OK to launch creation of your virtual server workload member as shown Figure 8-112.

Figure 8-112 Run job

Click Display Properties as shown in Figure 8-113.


Virtual server creation is completed as shown in Figure 8-114.

Figure 8-114 Virtual server creation completed



Go back to the Virtual Severs and Hosts view to check that your new server has been deployed as shown in Figure 8-115.

Figure 8-115 Virtual Servers and Hosts view

8.7.3 Capture a virtual server

Go to VMControl plug-in main screen, then click Capture in Common Tasks as shown Figure 8-116.




The Welcome capture page appears as shown Figure 8-117, click Next.

Figure 8-117 Capture Welcome page

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.

Figure 8-118 Appliance capture name



Select the source from which you want to capture as shown in Figure 8-119 then click Next.

Figure 8-119 Source type to capture

Select the virtual server that you want to capture as shown in Figure 8-120.

Figure 8-120 Select server to capture



Select the image repository on which you want to put the appliance generated by the capture process as shown in Figure 8-121.

Figure 8-121 Repository to capture

Select the disk that you want to capture from your existing virtual server as shown in Figure 8-122.

Figure 8-122 Select Disk for capture



Select the Network Mapping for your future appliance as shown in Figure 8-123.

Figure 8-123 Network mapping

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.

Figure 8-124 Virtual Server captured Operating System



Select the version control type for your future virtual appliance as shown Figure 8-125.

Figure 8-125 Version Control

Check the Summary and note that you cannot capture a running server as shown in Figure 8-126.

Figure 8-126 Virtual Server capture Summary



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.

Figure 8-127 Power off server for capture

Check that the virtual server is stopped as shown in Figure 8-128.

Figure 8-128 Virtual server stopped for capture



Go back to Summary and close the Warning information window as shown in Figure 8-129, then click Finish.

Figure 8-129 Capture Summary

Click OK to run the job as shown in Figure 8-130 and begin to capture your virtual server.

Figure 8-130 Run Job Now

Click Display Properties to check the job status as shown in Figure 8-131.

Figure 8-131 Capture job status




Figure 8-132 Capture completed

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.

Figure 8-133 VMControl main window

Check in Virtual Appliances that you see the new virtual appliance as shown in Figure 8-134.

Figure 8-134 Virtual Appliances window



8.7.4 Relocate virtual servers

Relocation allow you to migrate you virtual server from a physical KVM host to an other physical KVM host.

Go to VMControl plug-in main page, then click the Virtual Servers/Hosts tab as shown in Figure 8-135.

Figure 8-135 VMControl plug-in main page - Virtual Servers/Hosts tab

Click Virtual Servers and Hosts in Common Tasks as shown in Figure 8-136.

Figure 8-136 Virtual Servers and Hosts



Right click on your virtual server for relocation, then select Availability → Relocate as shown in Figure 8-137.

Figure 8-137 select server for relocation

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.

Figure 8-138 relocate virtual server info window



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.

Figure 8-140 Check relocation OK


Draft Document for Review August 18, 2012 12:15 am Managing_PowerVM_FSM.fm

Chapter 9. Managing PowerVM environment with IBM Flex System Manager

This chapter describes how to manage the PowerVM infrastructure through Flex System Manager. IBM Flex System p260 and p460 compute nodes have the same capabilities as rack POWER7 system family for example, Power770, Power750 etc. You can create logical partition profiles, modify, delete and activate them. You can use p260 and p460 compute nodes for full partition purpose, also you can set up VIOS environment in the p260, p460 compute nodes. You can manage VIOC client image through VMcontrol which is one of features in the Flex System Manager. The VMControl feature can capture, deploy, relocate virtual servers. This scenario describes the steps to set up PowerVM virtualization environment.


� 9.1, “Initial deployment of virtual machine” on page 356� 9.2, “Capture virtual machines” on page 369� 9.3, “Deploy virtual machines based on previously captured” on page 416� 9.4, “Relocate virtual machines” on page 429

9


Managing_PowerVM_FSM.fm Draft Document for Review August 18, 2012 12:15 am

9.1 Initial deployment of virtual machine

This section describes how to deploy virtual machine through Flex System Manager.

9.1.1 Solution architecture

Overall architecture of the PowerVM-based infrastructure with Flex System Manager is shown in Figure 9-1.

Figure 9-1 Overall architecture overview with Flex System Manager

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.



9.1.2 Setting up VIOS and NIM server

This section shows initial deployment of PowerVM on the p260 compute node.

You can see physical compute nodes and I/O modules in the Chassis Manager view of Flex System Manager, as shown in Figure 9-2. For more information about managing the chassis., see Chapter 4, “Chassis Management Module operations” on page 35

Figure 9-2 Chassis components view

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

p260 compute node

10Gb N/W switch 8Gb SAN switch

Chapter 9. Managing PowerVM environment with IBM Flex System Manager 357

http://www.redbooks.ibm.com/redpieces/abstracts/sg247989.html?Open


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.

Since we do not have a NIM in our infrastructure yet, we will be using the first method to install VIOS.

Creating VIOS profile through Flex System ManagerThe one of strong points in the FSM is providing single point of management.

Click Chassis Manager in Initial Setup tab, then click chassis name as shown in Figure 9-4.

Figure 9-4 Installed chassis name

Note: This option is only for a NIM server already existing at the site.



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.

Figure 9-5 Manage Power Systems Resources

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.

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

Note: If you do not see any compute node in the chassis, please go to Chapter 6.1, “FSM initial setup” on page 114.



Create VIOS profile depending on your system requirements.

At this time, type VIOS name, as seen in Figure 9-7.

Figure 9-7 Creating VIOS profile step 1

Define VIOS memory size, as shown in Figure 9-8.


Note: VIOS ID number should be 1 except using for full partition purpose.



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.




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


Check box if you have a plan to use SEA







Click Create Adapter..., as shown in Figure 9-12.


Now, we are going to create an adapter for virtual SCSI, as shown in Figure 9-13 on page 363.




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.

Figure 9-15 Creating VIOS profile step9

Shown created virtual scsi adapter



Define physical I/O adapters, as seen in Figure 9-16. At this time we assigned all physical adapters to the VIOS.


Check Summary page, as seen in Figure 9-17.


Right click on the created VIOS, select Operations → Activate → Profile, as seen in Figure 9-18 on page 365.

Figure 9-18 Activate the created VIOS profile step 1



Click Advanced.., as seen in the Figure 9-19.


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.




Select 5. Select Boot Options, as seen in Figure 9-22.

Figure 9-22 SMS menu: Main menu

Select 2. Configure Install/Boot Device, as seen in Figure 9-23

Figure 9-23 SMS menu: Multiboot

Select 3. Select CD/DVD, as seen in Figure 9-24 on page 367

Figure 9-24 SMS menu: Select device type



Select "6. Select USB", as seen in the Figure 9-25

Figure 9-25 SMS menu: Select media type

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.


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.

Figure 9-26 Media Devices page in the Manage Virtual Server

Note: When installing a VIOC, use a virtual CD-ROM host by VIOS.

1

2 3





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.

Figure 9-27 Created two partitions

9.2 Capture virtual machines

This section will describe how to capture virtual machines in PowerVM environment.

There are two method to capture virtual machine in the PowerVM virtual infrastructures:

� 9.2.1, “Capture AIX using Network Installation Manager (NIM)”� 9.2.2, “Capture AIX using storage copy services (SCS)” on page 394

If you want to know concepts of NIM and SCS based capture methods, go to 5.2.3, “Planning for PowerVM virtualization” on page 103.



9.2.1 Capture AIX using Network Installation Manager (NIM)

This topic describes how to capture AIX using NIM through Flex System Manager.

This diagram describe minimum configuration for NIM-based virtual machine deployment, as shown in Figure 9-28.

Figure 9-28 System diagram for NIM based deployment

Click Plug-ins tab on the Flex System Manager home page, as shown in Figure 9-29.

Figure 9-29 Flex System Manager main page

Click VMControl Enterprise Edition in the Plug-ins page, as shown in Figure 9-30.

Figure 9-30 VMControl Enterprise Edition menu

Note: If you do not see the VMControl feature in the Plug-ins page, check whether this feature is enabled or not.

System Pool

Flex System Manager Node


DB2

Storage Pool

IBM Fabric Manager

SMIAConfiguration

Tool

VMControl

StorageManagement

Power Systems

Management

Plug-ins

Applications

FC31718Gb SANPass thru

Management N/W

EN4093 10Gb NW IO module VM1

VIOSFSP

p260 compute node

Data N/W Fiber Channel

N/W

Fiber Channel

Storwize V7000

NIM

mksysb

System diagram for NIM based deployment



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.

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.

1

3 4

2



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.

Figure 9-32 Basics tab in the VMControl

Choose the Chassis that you want to discover, then click Add, as seen in the Figure 9-33 on page 372.

Figure 9-33 Choose the virtual appliance in the Target tab

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.

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.

Choose the Chassis



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.

Figure 9-35 Run a Collect Inventory job



Check the log for a job, as shown in Figure 9-36.

Figure 9-36 Check Log in the Logs tab

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



Six virtual servers in total have been added, as shown in Figure 9-38.

Figure 9-38 Discovered virtual server in the Virtual Server/Hosts

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



Make sure you have the SystemMgmtClient bundle installed on the NIM Server, as shown in Figure 9-39.

Figure 9-39 SystemMgmtClient fileset

Ensure openssh and openssl are installed and ssh is started on the NIM server, as shown in Figure 9-40.

Figure 9-40 Check ssh status



Discover the NIM Server using its IP address, as shown in Figure 9-41.

Figure 9-41 Discover NIM server

Check progress, as shown in Figure 9-42.

Figure 9-42 Check the discovery job

Note: This step is prerequisite to deploy VMControl agent on the NM server from FSM.



Check logs, as shown in Figure 9-43 on page 378.

Figure 9-43 Check the Log

Click No Access to gain access to the server, as shown in Figure 9-44.

Figure 9-44 Discovered Systems tab

Click



Enter the root password for your NIM server, as shown in Figure 9-45 on page 379.

Figure 9-45 Request Access page

You can see access is granted, as shown in Figure 9-46.

Figure 9-46 Check accessibility in the Resource Explorer menu

Discover the NIM Server in VMControl, as shown in Figure 9-47.

Figure 9-47 Discover virtual appliances

Type USERID/Password



Select the NIM Server you want to discover then press Add, as shown in Figure 9-48.

Figure 9-48 Discover virtual appliances menu

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.

Figure 9-49 Install Agents in the Basic tab



You will see welcome page, as shown in Figure 9-50.

Figure 9-50 Agent Installation welcome page

Select Common Agent Subagent Packages, as shown in Figure 9-51.

Figure 9-51 Agent Installation page

Select the agent for NIM server then press Add, as shown in Figure 9-52.

Figure 9-52 Agent Installation page continued



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.




Click Finish button, then you see pop up menu for the installation task, as shown in Figure 9-55 on page 383. Click OK.


Check progress, as shown in Figure 9-56.

Figure 9-56 Check progress



Check logs, as shown in Figure 9-57.

Figure 9-57 Check Logs

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



Next step is to create NIM repository that VMControl can manage.

Click Create Image repository, as shown in Figure 9-59 on page 385.

Figure 9-59 Create Image repository in the Basics tab

Select the NIM Server to use as the Repository, as shown in Figure 9-60.

Figure 9-60 Create Image repository continued



The new NIM repository has been created. Click the Image repositories link for more information about this repository, as shown in Figure 9-61.

Figure 9-61 Check newly created image repository

Check created image repository, as shown in Figure 9-62.

Figure 9-62 Check image repository

Prerequisite steps have finished to capture virtual server.

We describe two capture methods for the NIM:

� Create LPP_source base

� Capture mksysb base



Create LPP_source baseThis section describes to how to create LPP_source.

Figure 9-63 on page 387 shows LPP_source base capture system diagram.

Figure 9-63 System diagram for LPP_source based deployment

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.

Figure 9-64 create LPP_source base capture

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"



DB2

Storage Pool

IBM Fabric Manager

SMIAConfiguration

Tool

VMControl

StorageManagement

Power Systems

Management

Plug-ins

Applications


Management N/W

EN4093 10Gb NW IO module

VIOSFSP

p260 compute node

Data N/W

Fiber Channel

N/W

Fiber Channel

Storwize V7000

NIM

LPP_source

System diagram for LPP_source based deployment



� 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.

Figure 9-65 Check created virtual appliance

Capture mksysb baseThis section describe to how to create virtual appliance using the mksysb method.

These are overall steps for mksysb base capture.

1. Create two partitions without VIOS: one for NIM server (if exist, no need) and one AIX partition where mksysb is to be run.

2. Check all related servers are seen in FSM, if not, discover the specific object, then run Collect Inventory task.

3. Check filesystem size where mksysb file is to be stored in the NIM.



Select Capture in the Virtual Appliances tab, as shown in Figure 9-66 on page 389.

Figure 9-66 Virtual Appliances page

Figure 9-67 shows capture welcome page.

Figure 9-67 Capture welcome page



Type virtual appliance name, as shown in Figure 9-68 on page 390. We typed AIX-6100-mksysb.

Figure 9-68 Capture continued

Choose the source type, as shown in Figure 9-69.


Select source virtual server, as shown in Figure 9-70 on page 390.




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.




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.


Figure 9-74 on page 392 shows a summary.




Figure 9-75 shows Launch Job pop up menu.


Check the log as shown in Figure 9-76.




Check newly captured virtual appliance, as shown in Figure 9-77.

Figure 9-77 Capture finished

9.2.2 Capture AIX using storage copy services (SCS)

This section describe to how to work with SCS method.

Figure 9-78 shows SCS based capture system diagram.

Figure 9-78 system diagram SCS based deployment

These are overall steps for SCS base capture:

1. Hardware preparation



DB2

Storage Pool

IBM Fabric Manager

SMIAConfiguration

Tool

VMControl

StorageManagement

Power Systems

Management

Plug-ins

Applications


Management N/W


VIOSFSP

p260 compute node

Data N/W

Fiber Channel

N/W

Fiber Channel

Storwize V7000

System diagram for SCS based deployment

VM



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

Check Storage Copy Service configurationThis topic describes checklist to perform SCS configuration.

Check if Storage Control is running or not, as shown in Figure 9-79.




Check related resources exist in the farm, as shown in Figure 9-80.

Figure 9-80 Check farm resources

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.

Figure 9-81 All Systems page in the Resource Explorer



Check ssh in the Remote Service Access Point (RASP) configuration as shown in Figure 9-82.

Figure 9-82 Check RASP configuration

SSH access should be seen in the Access column, as shown in Figure 9-83.

Figure 9-83 Check RASP configuration continued

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 configurationCheck auto start setting of Common Agent fileset, as shown in Figure 9-84.

Figure 9-84 Agent startup setting check step

Discover VIOS and update VIOS information in the FSM: Left navigation pane → Inventory → System Discovery

Note: VIOS OS image has Common Agent file by default.



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.

Figure 9-85 Configure Access page

Check Access status, as shown in Figure 9-86.

Figure 9-86 Check access status



Install agentClick Install agents as shown in Figure 9-87.

Figure 9-87 Install agent

Figure 9-88 shows Agent Installation welcome page.



Figure 9-88 Agent installation welcome page

Select CommonAgentSubagent_VMControl_CommonRepository-2.41 as shown in Figure 9-89. Click Add.

Figure 9-89 selecting a proper agent

Select a VIOS to deploy an agent, as shown in Figure 9-90.

Figure 9-90 Selecting a target VIOS



Figure 9-91 shows summary.

Figure 9-91 Summary page

Figure 9-92 shows Launch Job pop up menu. Click OK.

Figure 9-92 Launch Job



Check log as shown in Figure 9-93 on page 402.

Figure 9-93 Check log

Image repository creation stepClick Create image repository as shown in Figure 9-94 on page 402.

Figure 9-94 Image repository creation step



Figure 9-95 shows welcome page.

Figure 9-95 Image repository creation welcome page

Type the repository name as shown in Figure 9-96 on page 403.

Figure 9-96 Type repository name

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.

Figure 9-97 Select target system



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.

Figure 9-98 Select a target storage

Figure 9-99 shows summary page.




When Launch Job page pops up, click OK. Then check log as shown in Figure 9-100 on page 405.


Create server system poolThis topic describes how to create server system pool.

Click Server system pools and members as shown in Figure 9-101.

Figure 9-101 Server system pools creation



Click Create as shown in Figure 9-102.

Figure 9-102 Click Create

Figure 9-103 shows Create Server System Pool welcome page.

Figure 9-103 Create Server System Pool welcome page

Figure 9-104 on page 406 shows Pooling Criteria.

Figure 9-104 Pooling Criteria



Select a physical system that you use as a pool as shown in Figure 9-105 on page 407.

Figure 9-105 Selecting a physical server

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.

Figure 9-106 Selecting storage pool

Figure 9-107 shows set up page for Additional Hosts to add.

Figure 9-107 Additional Hosts add page



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.

Figure 9-108 Optimization page





Check log as shown in Figure 9-110 on page 409.


Preparation for captureThis topic describes how to capture virtual server in SCS environment.

You have to copy vmc.vsar.tar file from Flex System Manager using scp command as shown in Figure 9-111.

Figure 9-111 Copy vmc.vsae.tar file from FSM

Extract the content of the .tar file as shown in Figure 9-112.

Figure 9-112 Unpack tar file

Note: You can run only specific commands in Flex System Manager.



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).

Figure 9-113 Set up environment

Run aix-install.sh as shown in Figure 9-114.

Figure 9-114 Installing VSAE file

Prepare the virtual server to be captured by running the AE.sh --reset command as shown in Figure 9-115.

Figure 9-115 Preparing the virtual server to be captured



Virtual server shutdowns automatically as shown in Figure 9-116.

Figure 9-116 Check AE.sh progress

Capture AIX using Storage Copy ServiceThis topic describes steps to capture AIX using SCS.

Click Capture as shown in Figure 9-117.

Figure 9-117 Capture AIX using SCS

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



Enter name as shown in Figure 9-118.

Figure 9-118 Enter name

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.

Figure 9-119 Selecting a source virtual server

Choose a repository as shown Figure 9-120.

Figure 9-120 Select a repository



Figure 9-121 shows information about LUN being captured.

Figure 9-121 Disk information to be captured

Figure 9-122 shows network mapping.

Figure 9-122 Network mapping page

Select version as shown in Figure 9-123. After that, you will see another version added.

Figure 9-123 Version control





Figure 9-125 shows pop up menu for launching jobs. Click OK.

Figure 9-125 Launch Job menu



Check log for the task completion, as shown in Figure 9-126.


Check a captured image as shown in Figure 9-127.

Figure 9-127 Check a captured image



9.3 Deploy virtual machines based on previously captured

This section describe different types of deployment methods of previously captured virtual machines.

9.3.1 Deploy virtual machines using LPP_source

This section covers how to deploy VMs using LPP_source.

Select an LPP_source on a Virtual Appliances tab, then click Deploy virtual appliance task, as shown in Figure 9-128.

Figure 9-128 VM deployment using LPP_source

Figure 9-129 shows Deploy virtual appliance welcome page.




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.

Figure 9-130 Choose an available target

Type workload name as shown in Figure 9-131.

Figure 9-131 Enter workload name



Figure 9-132 shows storage mapping. You can choose Storage volume or Storage pool. Disk size of 9,537 MB needs to be deployed.

Figure 9-132 Storage Mapping page

Assign disk to a new virtual server from VIOS rootvg storage pool as shown in Figure 9-133.

Figure 9-133 Assign disk to new virtual server.

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)



Figure 9-134 shows mapping view.

Figure 9-134 Storage mapping view

Put IP address information as shown in Figure 9-135.

Figure 9-135 IP address configuration





Figure 9-137 shows Launch Job menu. Click OK.

Figure 9-137 Launch Job menu

Figure 9-138 shows newly deployed virtual server.

Figure 9-138 Check newly deployed virtual server



Check virtual server in the Resource Explorer pane, as shown in Figure 9-139.

Figure 9-139 Virtual server in the Resource Explorer

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.

Figure 9-140 Check the virtual server status

Enter credentials for virtual server and click Request Access as shown in Figure 9-141.

Figure 9-141 Enter credentials for virtual server



Figure 9-142 shows that the request access task is completed successfully.

Figure 9-142 Request Access page

9.3.2 Deploy a virtual machine using mksysb

This section covers how to deploy VMs using mksysb.

Select virtual appliance of mksysb type as shown in Figure 9-143.

Figure 9-143 Select virtual appliance of mksysb type



Select a target where you’ll deploy this mksysb image as shown in Figure 9-144.

Figure 9-144 Select a target

Type workload name as shown in Figure 9-145.




Figure 9-146 shows networking mapping.

Figure 9-146 Network Mapping page

Type IP address and DNS information as shown in Figure 9-147.

Figure 9-147 IP address configuration page

Click Finish, then click OK on the Launch Job page.

Figure 9-148 shows newly deployed virtual machine through mksysb virtual appliance.

Figure 9-148 Newly deployed virtual server



9.3.3 Deploy a virtual machine using SCS

This section shows deployment steps using the SCS method.

Click Deploy virtual appliance as shown in Figure 9-149.

Figure 9-149 Deploy virtual appliance task

Figure 9-150 shows welcome page.




Select virtual appliance as shown in Figure 9-151. Captured _AIX_SCS is an image created by V7000 flashcopy feature.

Figure 9-151 Select a virtual appliance

Select a target as shown in Figure 9-152.

Figure 9-152 Select a target

Type name as shown in Figure 9-153.




Figure 9-154 shows networking mapping.

Figure 9-154 Network Mapping page

Type IP address information as shown in Figure 9-155.

Figure 9-155 IP address configuration page



Figure 9-156 shows summary.


Figure 9-157 shows Launch Job page.

Figure 9-157 Launch Job page



Figure 9-158 shows job log with the task completed.

Figure 9-158 Job log: task completed

9.4 Relocate virtual machines

IBM Flex System Manager VMControl can relocate virtual servers in response to predicted hardware failures related to processors, memory subsystems, power source, or storage. You might also choose to relocate virtual servers for planned maintenance or downtime or to adjust resources to improve performance.

The following relocation methods are supported in a PowerVM environment:

� Static relocation in virtual farms

� Live relocation in virtual farms

� Live relocation in server system pools

Manual relocationYou 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 relocationVMControl 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.



9.4.1 Relocating virtual servers manually

Figure 9-159 shows overall architecture for virtual server relocation.

Figure 9-159 System diagram for virtual server relocation

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.

-

Figure 9-160 Chassis front view

VM1

FC31718Gb SAN Pass thru

VIOS03VIOS01



Storwize V7000 Data N/W Fiber Channel

N/W Fiber Channel


p260 compute

node

p460 compute

node

System diagram for virtual server relocation



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:


Click Manage Virtual Server to check VIOS profile settings as shown in Figure 9-161.

Figure 9-161 Launch Virtual Server settings




Mover service check box should be checked to perform Live Partition Mobility as shown in Figure 9-162.

Figure 9-162 Check VIOS server setting



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-163 Virtual Ethernet Adapter setting

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.

Figure 9-164 virtual scsi configuration page



Figure 9-165 on page 434 shows disk allocation information in VIOS environment.

Figure 9-165 Disk allocation information

Shared disk drives on VIO Servers must have Reserve policy set to no_reserve as shown in Figure 9-166.

Figure 9-166 Set to no_reserve



Click Migrate as shown in Figure 9-167.

Figure 9-167 Launch a relocation virtual server

Figure 9-168 shows migration wizard. Click Finish after checking summary, you can observe relocation of virtual server.

Figure 9-168 Virtual server relocation wizard

Figure 9-169 shows AIX-SCS running on the p460 (Server-7895-42X).

Figure 9-169 Check AIX running status on p460


Draft Document for Review August 18, 2012 12:15 am Managing_VMware_FSM.fm

Chapter 10. Managing VMware environment with IBM Flex System Manager

This chapter discusses the FSM integration with VMware environment. It describes common tasks that can be performed on your VMware infrastructure using FSM. Examples of common tasks include creating, editing and relocating virtual servers, as well as reconfiguring clusters and working with maintenance mode.

In this chapter we also describe how to use FSM to configure simple but powerful automation plans that can be used to protect your virtual servers proactively from hardware problems. We test a common use case scenario of a hardware problem and observe the results from the automaton plan.

VMware vCenter Server is the central management component for VMware ESX/ESXi hosts. Nowadays, vCenter is used in almost all VMware environments and is required in order to use VMware cluster features.

FSM uses its VMControl plug-in to interact with vCenter. FSM does not aim at replacing vCenter. In fact, VMControl leverages the robust and virtualization specialized vCenter to execute tasks targeted at the VMware vSphere infrastructure components. FSM provides an essential collection of most commonly used tasks by a privileged administrator. This way your enterprise administrator with full privileges can manage all platforms in your chassis from the single FSM interface and have junior administrators with lower privileges perform additional activities directly on vCenter, if needed.

Additionally, the integration of FSM with VMware lets you correlate events and automate tasks that span over the physical hardware through your hypervisor, clusters and virtual servers. It gives you a full picture of your infrastructure end to end and lets you operate it from a single pane of glass from hardware and software perspective.

10


Managing_VMware_FSM.fm Draft Document for Review August 18, 2012 12:15 am

10.1 Environment overview

For the purpose of our discussion, we have configured the initial vSphere 5.0 environment shown in Figure 10-1.

Figure 10-1 VMware environment diagram

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 Description

Hosts 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.

Virtual Machines 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.

vCenter Server 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.

LUN1 Storwize V7000


PF-ESXi01

VM Network

vMot

ion

Man

agem

ent

IP network

Cluster1

PF-Windows1

PF-E

SXi-N

ode1

SAN

PF-ESXi02

VM Network

vMot

ion

Man

agem

ent

PF-E

SXi-N

ode2

LUN2 LUN3 Fiber Channel

Ethernet

PF-vCenter01vm001 vm002



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.

Datacenters and Clusters 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.

Network 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.

Storage 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.

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.

Component Description

Chapter 10. Managing VMware environment with IBM Flex System Manager 439


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.

Figure 10-2 Virtual Servers and Hosts page

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



Click Next on the Welcome page (see Figure 10-4 on page 441).

Figure 10-4 Create Virtual Server wizard Welcome page



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.

Figure 10-5 Create Virtual Server wizard Name page



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.

Figure 10-6 Create Virtual Server wizard Source page



Specify a number of virtual CPUs to assign to the virtual server. Type 2 and click Next, see Figure 10-7 on page 444.

Figure 10-7 Create Virtual Server wizard Processor page



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.

Figure 10-8 Create Virtual Server wizard Memory page

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



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).

Figure 10-9 Create Virtual Server wizard Disks page



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.

Figure 10-10 Create Virtual Server wizard Network page



Review the Summary page and click Finish (Figure 10-11 on page 448).

Figure 10-11 Create Virtual Server wizard Summary page



Click OK in the Launch Job window to launch the virtual server creation immediately, see Figure 10-12 on page 449.

Figure 10-12 Create Virtual Server Launch Job window

Click Display Properties in the Create Virtual Server job message box to see the job status (see Figure 10-13).

Figure 10-13 Create Virtual Server job message box



Ensure the Create Virtual Server job completed successfully (Figure 10-14 on page 450) and close the Active and Scheduled Jobs tab.

Figure 10-14 Create Virtual Server job details page

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.




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.

Figure 10-16 Virtual server creation informational event in Problems page

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



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



Click OK to launch the Power On job immediately, see Figure 10-19.

Figure 10-19 Power On Launch Job window



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.



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



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.

Figure 10-23 Relocate wizard Target page

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.

Figure 10-24 Relocate wizard Save Plan page



Verify the relocation Summary and click Finish (see Figure 10-25).

Figure 10-25 Relocate wizard Summary page

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



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.



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



You can select a specific Target host or choose Relocate by CPU utilization. Select PF-ESXi-Node2 and click Next, see Figure 10-30.

Figure 10-30 Relocate wizard Target page

Select Relocate and save plan and provide a descriptive Relocation plan name, as shown in Figure 10-31.

Figure 10-31 Relocate wizard Save Plan page



Review the Summary page and click Finish, see Figure 10-32.

Figure 10-32 Relocate wizard Summary page

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.




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.

Figure 10-34 Relocation Plans for Farms page

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.



10.5 Modify Virtual Server resource allocation

Right-click on the virtual server vm002 and select Power On/Off → Shut down and power off, as shown in Figure 10-35 on page 463. This will initiate a graceful OS shutdown before powering off the virtual server.

Figure 10-35 Shut down and power off menu item on Virtual Servers and Hosts page

Note: Ensure that you always have up-to-date version of VMware tools installed in the Guest OS of your VMware virtual machines. Graceful OS shutdown is just one of the many features that makes VMware tools strongly recommended.



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



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



Edit Virtual Server window opens. Click the Memory tab, as shown in Figure 10-38 on page 466.

Figure 10-38 Edit Virtual Server window

Observe the current memory assigned to the virtual server, as seen in Figure 10-39 on page 466.

Figure 10-39 Memory tab of Edit Virtual Server window

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.



Figure 10-40 Updated memory value in Edit Virtual Server window

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.



10.6 Enable DRS

VMware Distributed Resource Scheduler (DRS) is a cluster feature that can perform dynamic load balancing of compute resources (CPU and memory) across physical hosts that are members of the cluster. When configured in Fully Automated mode, DRS uses VMware vMotion to perform live migration of virtual machines (VMs) whenever needed. DRS continuously monitors the CPU and memory resource usage for all cluster physical hosts and their VMs. DRS evaluates these metrics and ensures an optimal VM placement to achieve relatively even load on all cluster physical hosts.

Let us now enable DRS in Fully Automated mode for Cluster1 in our environment.

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-42 on page 468. Observe the vCenter server and all discovered datacenter and cluster objects listed under it.

Figure 10-42 Platform Managers and Members page

Note: A best practice, valid for most vSphere environments, is to configure DRS in Fully Automated mode. To use DRS for load balancing, you must have a vMotion network configured in your cluster and your virtual machines must meet vMotion requirements. Ensure you have the proper vSphere license to use DRS. Find detailed information on DRS in the vSphere Resource Management Guide: http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-501-resource-management-guide.pdf

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.


http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-501-resource-management-guide.pdf


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.

Figure 10-44 Edit Virtual Farm wizard Welcome page



Verify the cluster name and click Next, as shown in Figure 10-45.

Figure 10-45 Edit Virtual Farm wizard Name page

Select VMware Distributed Resource Scheduler (DRS) and leave VMotion rate as Normal, as shown in Figure 10-46 on page 470. Click Next.

Figure 10-46 Edit Virtual Farm wizard Capabilities Details page

Review the Summary page and click Finish, as shown in Figure 10-47.



Figure 10-47 Edit Virtual Farm wizard Summary page

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.

10.7 Put a host in maintenance mode

Place a host in maintenance mode in order to perform service tasks on it. A vSphere host in maintenance mode cannot have any virtual machines in powered on state. If a host entering maintenance mode has powered on virtual machines and it is a member of a fully automated DRS cluster, DRS would automatically migrate all running virtual machines to other hosts in the cluster before placing it in maintenance mode.

In the previous section, we enabled DRS in Fully Automated mode for Cluster1. Let us now place PF-ESXi-Node2 in maintenance mode. PF-ESXi-Node2 is currently running one virtual server - vm003.



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



Return to Virtual Servers and Hosts page and observe that all virtual servers are now running on PF-ESXi01 (see Figure 10-49).




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



Click OK to launch the job immediately, as shown in Figure 10-51 on page 475.

Figure 10-51 Exit Maintenance Mode Launch Job window

Before continuing with our event automation scenario, let us quickly review another option we have in FSM to view and manage our virtual infrastructure.

10.8 Topology view

So far we used table resource view to operate our virtual infrastructure via FSM. In this section we will explore the topology view.

You can use the Virtualization Basic Topology perspective to view and manage your vCenter, Datacenters, Clusters, Hosts, Virtual Servers, Operating Systems and physical compute nodes. The Virtualization Basic Topology interactive map shows you the logical relationships between the above mentioned components of your virtual infrastructure. This view can be useful also to troubleshoot a problem by determining problematic components and their logical connections to the rest of the infrastructure.



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.

Figure 10-52 Platform Managers and Members page



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



Click the Cluster1 icon and click the maximize button of the Details window, as shown in Figure 10-54 on page 478.

Figure 10-54 Virtualization Basic Topology view



The details for the selected object appear as shown in Figure 10-55 on page 479.

Figure 10-55 Details window in Virtualization Basic Topology view



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.

Figure 10-56 menu item in Virtualization Basic Topology view

Note: Click Actions → Layout → Tree to change the default Radial layout if it does not suit your purposes.



10.9 Automating preventive actions in response to hardware alerts

Earlier in the chapter we illustrated common virtualization tasks that can be performed manually by the FSM administrator. In this section we will demonstrate how to automate tasks that can prevent from potential service outage. We will configure automation based on hardware alerts.

In the IBM Flex System Manager Web interface navigation area, expand Automation and click Event Automation Plans, as shown in Figure 10-57 on page 481. Click Create to create a new automation plan.




Click Next on the Create Event Automation Plan Wizard Welcome page, as shown in Figure 10-58 on page 482.

Figure 10-58 Create Event Automation Plan Wizard Welcome page



Type a Name and Description for the automation plan, as shown in Figure 10-59 on page 483.




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.

Figure 10-60 Create Event Automation Plan Wizard Targets page



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.



Click Create to create a new event action, as shown in Figure 10-62 on page 486.


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.

Figure 10-63 Create Action window actions list



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.

Figure 10-64 Create Action window action properties

Select the newly created Enter maintenance mode event action, as shown in Figure 10-65. Click Next.




Click Next on the Time Range page as shown in Figure 10-66.

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.




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.

Figure 10-69 Chassis Map showing PF-ESXi-Node2 with a Critical error



The generated error is also listed in PF-ESXi-Node2 Event Log, as shown in Figure 10-70 on page 490.

Figure 10-70 Event Log page for selected node



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.




Select PF-ESXi-Node2 and click Actions → System Status and Health → Active Status, as shown in Figure 10-72 on page 492.

Figure 10-72 Active Status



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.

Figure 10-73 Active Status page for selected node



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


Draft Document for Review August 18, 2012 12:15 am Managing_Hyper-V_FSM.fm

Chapter 11. Managing Hyper-V environment with IBM Flex System Manager

This chapter is focused on managing the Hyper-V-based virtualization environment with IBM Flex System Manager. We discuss how to enable Hyper-V to be managed by FSM, and how to perform typical virtualization management tasks including virtual machine’s lifecycle management, automation capabilities, and maintenance.


� 11.1, “Operate the FSM in the Hyper-V environment” on page 496� 11.2, “Manage Hyper-V from FSM” on page 502

11


Managing_Hyper-V_FSM.fm Draft Document for Review August 18, 2012 12:15 am

11.1 Operate the FSM in the Hyper-V environment

IBM Flex System Manager is able to perform basic tasks for the Microsoft Hyper-V hypervisor. The advantage is that you can start, stop, restart, suspend, create and delete your virtual servers running on Microsoft hypervisors with the same tool which also manages other hypervisors in the market.

11.1.1 Install agent on an Hyper-V node

Before managing an Hyper-V virtual environment you need:

– Prepare you Hyper-V system, please refer to 5.2.5, “Planning for Hyper-V virtualization” on page 110

– To discover your system without any agent and perform an inventory collection.

– Download the Windows Common Agent for Remote Installation from the URL bellow: https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=dmp&lang=en_US&S_PKG=dir_63_x86_RDagents

– Import the Common Agent for Windows x64 operating systems as described in “Import Common Agent for Windows”.

– Discover your system without any agent, grant access to it and run Collect Inventory task before installing the agent with FSM.

– Install a Platform or a Common Agent on your hypervisor to allow your FSM management appliance to manage your Microsoft hypervisor.

Discover your Hyper-V serverTo discover an Hyper-V server, you can use Discovery Manager as described in 6.7.1, “Discovery Manager” on page 157.

Specify the IP address of you operating system and click Discover Now as shown in Figure 11-1, then wait till the job is complete.

Figure 11-1 Discover Hyper-V node

496 Implementing Systems Management of the IBM PureFlex System

https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=dmp&lang=en_US&S_PKG=dir_63_x86_RDagents


Import Common Agent for WindowsSelect Release Management, then Agent as shown in Figure 11-2.

Figure 11-2 Release Management

Select agent, then click Import, as shown in Figure 11-3.

Figure 11-3 Importing agent

Specify the path to import the agent and click OK, as shown in Figure 11-4.

Figure 11-4 Path to import agent

Chapter 11. Managing Hyper-V environment with IBM Flex System Manager 497


After a couple of time you get a blue information window as shown in Figure 11-5.

Figure 11-5 Agent imported

Grant Access and Collect Inventory on an Hyper-V node with FSMFind your server in Resource Explorer, click No Access as shown in Figure 11-6.

Figure 11-6 Request access to Hyper-V node

When the job is completed, your access is OK as shown in Figure 11-7 and you can install your common agent imported previously.

Figure 11-7 Hyper-V access granted

Note: You can note that six agents have been imported because six agent where present in the local FSM directory /home/USERID/RemoteAgentInstall



Install Common Agent on Hyper-VGo to Release Management as shown in Figure 11-2 on page 497.

Figure 11-8 Select CommonAgent 6.3 for an installation on Hyper-V

A welcome Agent Installation window appears as shown in Figure 11-9.

Figure 11-9 Agent Installation: Welcome screen



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.

Figure 11-10 Agent Installation: Package selection

Select your Hyper-V host as shown in Figure 11-11.

Figure 11-11 Agent Installation: Target selection



Check the summary of Common agent installation as shown in Figure 11-12.

Figure 11-12 Agent installation: Summary

Click OK to run the installation as shown in Figure 11-13.

Figure 11-13 Agent Installation: Launch Job

Click Display Properties button as shown in Figure 11-14.




Go to you Windows 2008 R2 Hyper-V server and check in the programs installed that the Common Agent is present.

11.2 Manage Hyper-V from FSM

The following tasks can be performed in an Hyper-V environment from the FSM appliance:

� 11.2.1, “Deploy virtual servers”� 11.2.2, “Edit virtual server” on page 506� 11.2.3, “Delete a virtual server” on page 507� 11.2.4, “View virtual server network topology” on page 507

11.2.1 Deploy virtual servers

Go to VMControl then select Virtual Servers/Hosts tab as shown in Figure 11-15.

Figure 11-15 VMControl



Right click on your Hyper-V host and select System Configuration → Create Virtual Server as shown in Figure 11-16.

Figure 11-16 VMControl: Create Virtual Server

You get a Welcome screen as shown in Figure 11-17.

Figure 11-17 Create Virtual Server: Welcome screen

Click Next and choose a name for your virtual server as shown in Figure 11-18

Figure 11-18 Name a virtual server



Click Next and choose the number of processors as shown in Figure 11-19.

Figure 11-19 Number of virtual server processors

Click Next and select your virtual server memory size as shown in Figure 11-20.

Figure 11-20 virtual server memory size

Click Next and select your disk size as shown in Figure 11-21.

Figure 11-21 Virtual server disk size

Click Next and select the virtual switch to which you want to connect your virtual server as shown in Figure 11-22.

Figure 11-22 Configure virtual server network



Click Next and check your virtual server summary configuration as shown in Figure 11-23.

Figure 11-23 Virtual server configuration summary

Click Finish then click OK to run you virtual server creation task as shown in Figure 11-24.

Figure 11-24 Run now

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.

Figure 11-25 Information blue box



Job is completed as shown in Figure 11-26.

Figure 11-26 Job is completed

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.

Figure 11-27 Virtual server created on Hyper-V

11.2.2 Edit virtual server

Right click your virtual server and select System Configuration → Edit Virtual Server as shown in Figure 11-28.

Figure 11-28 Edit virtual server



You get information on processor and memory size as shown in Figure 11-29.

Figure 11-29 Virtual server details

11.2.3 Delete a virtual server

Right click your virtual server and select Permanently Delete Virtual Server as shown in Figure 11-30.

Figure 11-30 Delete a virtual server

11.2.4 View virtual server network topology

Select your virtual server as shown in Figure 11-31.

Figure 11-31 Select virtual server



Right click the server and select Topology Perspective → Network → Basic as shown in Figure 11-32.

Figure 11-32 select a basic network topology

You get a network topology view of your virtual server within the infrastructure as shown in Figure 11-33.

Figure 11-33 Topology view


Draft Document for Review August 18, 2012 12:15 am 8060glos.fm

Glossary

Your glossary term, acronym or abbreviation Term definitionSort term names:highlight rows → Table → Sort → Column1 → Sort

Term1 Term1 definition



© Copyright IBM Corp. 2012. All rights reserved.
509

8060glos.fm Draft Document for Review August 18, 2012 12:15 am


Draft Document for Review August 18, 2012 12:15 am 8060abrv.fm

ronyms

This abbreviations and acronyms file is optional.

Use this file by adding names and descriptions to it. Sort these names: highlight rows → Table → Sort → Sort By: Column 1 → Sort oroptionally add names and descriptions to the Index file instead of this file by indexing the first use of an abbreviation or acronym: highlight text → Special → Marker → Index → New Marker

abbreviation1 Description1


IBM International Business Machines Corporation

ITSO International Technical Support Organization



Abbreviations and ac

511

8060abrv.fm Draft Document for Review August 18, 2012 12:15 am


Draft Document for Review August 18, 2012 12:15 am 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:




Online resources

These websites are also relevant as further information sources:

� Description1

http://????????.???.???/

� Description2

http://????????.???.???/

� Description3

http://????????.???.???/

Help from IBM

IBM Support and downloads




8060bibl.fm Draft Document for Review August 18, 2012 12:15 am

ibm.com/support

IBM Global Services

ibm.com/services


http://www.ibm.com/support/

http://www.ibm.com/support/

http://www.ibm.com/services/

http://www.ibm.com/services/

Draft Document for Review August 18, 2012 12:15 am 8060IX.fm

Index

Numerics00D7554 1868Y7030 118731 1890Y4217 1890Y4222 1890Y4249 1890Y9338 1294Y9219 1994Y9220 1995Y1174 1995Y1179 19

Aagents 87

Bblades

See compute nodes

CChassis Management Module

connections 12default IP address 29factory defaults 12functions 13IPv6 29LEDs 12ports 12reset 12web interface 29

cloud 3Common Agent 87compute nodes

management 13overview 7

Ddefault IP addresses 13

EEthernet

internal management network 10expert integrated systems 3Express, PureFlex System 5

FFlex System Manager

agents 87chassis management 130Common Agent 87


discovery 130features 19, 82hardware 19importing update files 137inital setup 114Java 117licenses 18management network 120networking 21NTP setup 119out-of-band management 87overview 7, 82part numbers 18partitions 21planar 20Platform Agent 87power control 118preload 22remote control 117setup 114software 22storage 21system board 20user accounts 120wizard 114

foundations 5FSM

See Flex System ManagerFSP 14

IIMMv2

See Integrated Management Module IIIntegrated Management Module II

features 13overview 13

integrated systems 3internal management network 10Internet connection 133IP addresses 13

Chassis Management Module 29

LLEDs

Chassis Management Module 12

Mmanagement 9

See also Chassis Management Modulecompute nodes 13FSP 14I/O modules 15Integrated Management Module II 13

515

8060IX.fm Draft Document for Review August 18, 2012 12:15 am

IP addresses 13

Oout-of-band management 87

Pp260 Compute Node

FSP 14p460 Compute Node

FSP 14Platform Agent 87PureFlex System 4–5

RRedbooks website 513

Contact us xireset the CMM 12

SSerial-over-LAN 14storage

overview 8systems management 9

See also Chassis Management Modulecompute nodes 13FSP 14I/O modules 15Integrated Management Module II 13IP addresses 13

VVideoStopped_OutOfRange 117

Wwizards

Flex System Manager 114

Xx220 Compute Node

Integrated Management Module II 13x240 Compute Node

Integrated Management Module II 13IPMI compliance 14


To determine the spine w

idth of a book, you divide the paper PP

I into the number of pages in the book. A

n example is a 250 page book using P

lainfield opaque 50# smooth w

hich has a PP

I of 526. Divided

250 by 526 which equals a spine w

idth of .4752". In this case, you would use the .5” spine. N

ow select the S

pine width for the book and hide the others: S

pecial>C

on

ditio

nal

Text>Sh

ow/H

ide>S

pin

eSize(-->H

ide:)>S

et . Move the changed C

onditional text settings to all files in your book by opening the book file with the spine.fm

still open and File>Im

po

rt>Fo

rmats the

Conditional Text S

ettings (ON

LY!) to the book files.

Draft D

ocument for R

eview A

ugust 18, 2012 12:15 am8060sp

ine.fm

517

(0.1”spine)0.1”<

->0.169”

53<->

89 pages

(0.2”spine)0.17”<

->0.473”

90<->

249 pages

(1.5” spine)1.5”<

-> 1.998”

789 <->

1051 pages

(1.0” spine)0.875”<

->1.498”

460 <->

788 pages

(0.5” spine)0.475”<

->0.873”

250 <->

459 pages

Implem

enting Systems M

anagement of IBM

PureFlex System

Implem

enting Systems M

anagement

of IBM PureFlex System

Implem

enting Systems

Managem

ent of IBM PureFlex

System

Implem

enting Systems M

anagement of IBM

PureFlex System

(2.0” spine)2.0” <

-> 2.498”

1052 <->

1314 pages

(2.5” spine) 2.5”<

->nnn.n”

1315<->

nnnn pages

To determine the spine w

idth of a book, you divide the paper PP

I into the number of pages in the book. A

n example is a 250 page book using P

lainfield opaque 50# smooth w

hich has a PP

I of 526. Divided

250 by 526 which equals a spine w

idth of .4752". In this case, you would use the .5” spine. N

ow select the S

pine width for the book and hide the others: S

pecial>C

on

ditio

nal

Text>Sh

ow/H

ide>S

pin

eSize(-->H

ide:)>S

et . Move the changed C

onditional text settings to all files in your book by opening the book file with the spine.fm

still open and File>Im

po

rt>Fo

rmats the

Conditional Text S

ettings (ON

LY!) to the book files.

Draft D

ocument for R

eview A

ugust 18, 2012 12:15 am8060sp

ine.fm

518

Implem

enting Systems

Managem

ent of IBM PureFlex

System

Implem

enting Systems

Managem

ent of IBM PureFlex

System

®

SG24-8060-00 ISBN

Draft Document for Review August 18, 2012 12:19 am

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

®


ExploresIBM PureFlex Systemand its management capabilities

Provides planningand deployment considerations

Explains step-by-step implementation instructions

To meet today’s 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 heterogenous virtualization environments can be managed from a single panel.

This IBM Redbooks publication introduces IBM PureFlex System, describes its management devices and solutions, 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.

Back cover




sg 248060

Documents

chassis management module112

chassis management module574

management network102

chassis management module

integrated management

copyright ibm

ibm redbooks

compute node management