IBM zEnterprise zManager Workshop · © 2011 IBM Corporation IBM Washington Systems Center 8 The Unified Resource Manager (“zManager”) A set of management function for z196+zBX

© 2011 IBM Corporation

IBMIBMIBMIBM zEnterprise

zManager Workshop


IBM Washington Systems Center

2

ZMAN1 – IBM zEnterprise and Unified Resource Manager (zManager) workshopWorkshop webpage: ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4685

Wildfire workshops presented by the IBM Advanced Technical Skills (ATS) organizationGaithersburg, MD



3

Workshop Agenda

• zEnterprise Overview and zManager Review

• zBX Power Blades and Storage Considerations

• Review of the Lab System Setup and Use Case

• Lab – Define Virtual Servers

• Platform Performance Management

• Lab – Enable Middleware, Define Workloads and Monitor Performance

• Usage Scenario – Co:Z Processing

• Lab – Co:Z and PDF Generation on Virtual Server



Introduction and Overview



5

Five Essential Components of the zEnterpriseThis picture illustrates a schematic view of the five components:

z196 zBX

Unified Resource Manager“zManager”

NetworkingIEDN and INMN

Performance and Workloads



6

The z196IBM’s newest generation of mainframe …

• 5.2 GHz quad-core processor; up to 96 cores supported

• New superscalar, out-of-order pipeline and 100 new instructions

• Each core with 64 KB L1 instruction cache, 128 KB L1 data cache and a 1.5 MB L2 cache.

• Up to 3 TB of redundant array of independent memory(RAIM)

• PR/SM (Processor Resource/System Manager) type-1 Hypervisor

• Operating systems: z/OS, z/VM, z/VSE, and z/TPF and Linux for System z

By itself an interesting topic to explore further, but this is not the focus of this workshop

It’s part of the workshop, but not the focus



7

Top of Rack Switches(TOR)

The zEnterprise Blade Extension (zBX)This is a rack frame that hosts blade servers and optimizer blades:

• Machine Type 2458 - Model 002

Blade Center 1

Blade Center 2

Networking

Up to 14

blades or optimizers

Up to 14

blades or optimizers

Many details yet to cover!In particular we need to cover zManager to make the

value of this become more evident

Up to four frames may be combined to form one “zBX”



8

The Unified Resource Manager (“zManager”)A set of management function for z196+zBX = zEnterprise

First we need to establish a baseline of concept understanding

Then we can explore how zManager provides this management

• Software and Firmware with a user interface that allows you to manage many elements of the zEnterprise as a logical system

• Runs in HMC and Support Element (SE) along with microcode and software components in virtual servers

• Provides …

� Hardware management

� Hypervisor management

� Virtual Server management

� Workload management

� Energy management



9

Performance and Workload ManagementBoth monitoring performance as well as defining what makes up a business

workload and what performance policies you wish to apply to them

Many details yet to cover!We have an entire section devoted to this broad topic

• The zManager has visibility into the

performance metrics of hardware and virtual servers (this provides monitoring)

• Workloads are comprised of one to many middleware and applications across different parts of this system

• Performance policies indicate the relative importance you provide to the workload

• zManager then has the ability to try to manage to your defined policies



10

NetworkingThe zEnterprise has two internal networks …

A very broad and potentially detailed topicWe’ll cover some of this but leave the deep details to other workshops

• An internal management network so zManager can do its work (the “IMNM”)

• An internal data network virtual servers

within the zEnterprise can use (the “IEDN”)

• Virtual LANs (VLANs) that provide logical

separation of virtual servers

Intra-Node Management Network (INMN)1Gb IPv6 on standard copper Ethernet

Intra-Ensemble Data Network (IEDN)10Gb IPv4 (or IPv6) on fiber



11

zEnterprise = Sum of the PartsThis is the essential message … there’s value in the sum of the parts:

That’s the goal of this workshop …To give you enough of an understanding to see the “big picture” so that

you may then dig deeper into topics of specific interest to you



Key Concepts and Terminology



13

HMC and Unified Resource ManagerThe functions of the Unified Resource Manager are accessible through the

HMC. The HMC communicates with the SEs, which manages ensemble

Primary Alternate

Web Interface

Support

Elements

Router or Firewall

You will use the HMC to define your virtual

servers and workloads

Internal Management Network (INMN)



14

Nodes and EnsemblesThe terms are associated with the physical topology of the zEnterprise …

z196zBX

Blade Center

Blade Center

Up to Four Frames

Blade Center

Blade Center

NodeA z196 CEC plus up to four zBX frames

Defines the domain of the

internal management network (INMN)

Up to eight nodes in an ensemble

EnsembleOne to eight nodes

Defines the domain of the

internal data network (IEDN)

Defines the domain of control by zManager



15

“Zero zBX” ConfigurationIt is possible to have a “zEnterprise” system without having a zBX in the

picture. We call that a “zero zBX” configuration:

z/OS LPAR

z/OS LPAR

z/VM Hypervisor

Linux for System z

Linux for System z

Linux for System z

Intra-Node Management Network (INMN)

Intra-Ensemble Data Network (IEDN)

Node and Ensemble

A node and an ensemble, with zManager, IEDN and INMN … just no zBXYou can use zManager to configure and create the guest machine on zVM. Other tools then used to

populate with the Linux binaries. Linux virtual server may then be managed by zManager, including share processor adjustments to achieve workload performance goals (more on that later).

PR/SM HypervisorSupport Elements



16

Blade “Entitlement”This is what takes place when a new blade server is placed in the blade

center of a zBX …

zManager (HMC)

Support Element

Blade Center

Intra-Node Management Network (INMN)

• You order the number and type of blades you want. zManger must see Licensed Internal Code Controlled Configuration (LICCC)

record to proceed

• Blade center firmware detects blade and sends information about

blade to support element

• zManager confirms the inserted hardware is acceptable

• zManager tells the blade center to power on the inserted blade

• zManager installs hypervisor and virtual I/O server code

• Blade is then ready for creation of virtual servers



17

Survey of Hypervisors and Virtual ServersThe following picture shows the currently supported hypervisors and

virtual servers across the zEnterprise system:

zBX Model 2

PS701

Express® bladeSystem x HX5

7873 blade

PR/SM

z/OS

z/VM 6.1with PTFs *

V1.10+PTFsV1.11V1.12V1.13

AIX 7.1, AIX 6.1 TL5 or V5.3 TL12

PowerVMIntegrated x Hypervisor

x Hyp

64-bit Red Hat Enterprise

Linux (RHEL) 5.5

64-bit Novell SUSE Linux Enterprise Server (SLES) 11

Red Hat Enterprise Linux (RHEL) 6, 5.5, 5.4, or 5.3

Novell SUSE Linux Enterprise Server (SLES) 11 or 10

z/OS V1R13, V1R12, V1R11, or V1R10 with PTFs

Up to 16 virtual servers Up to 8 virtual serversHundreds or more

* http://www.vm.ibm.com/service/vmrequrm.html



18

Operating System Image ManagementThe zManager will work with the hypervisor to create the virtual server, but

it does not provide a way to install or backup OS images.From “Ensemble Planning and Configuring Guide” GC27-2608

Install from an ISO Image

It works but has limitationsThe virtual DVD image needs to be mounted to each virtual server. Images over 2GB in size must be copied using HMC’s real DVD drive, not from HMC browser.

Install from a network device

AIX NIM server or Linux Boot ServerMore flexible and allows for multiple concurrent installations. You’ll use this in lab.

Install using

provisioning manager

Will work today for Linux for System z on z/VMThe z/VM Systems Management API (SMAPI) may be accessed directly. Systems Director with VMControl works quite well. Tivoli Provisioning Manager does as well.

By using the zManager APIszManager exposes many of its functions through a set of APIs. The manual SC27-2616 does a good job outlining all the APIs and their functions. When IBM and other vendors develop products to exploit the APIs then virtual server creation and provisioning through the APIs will be possible.

AIX or Linux on x Hyp. Linux on z/VM has other image copy mechanisms to use.



19

High Level: Storage ConsiderationsThe blades have internal hard drives but they’re used by zManager for

hypervisor code. External SAN storage is needed:

PS701 Express®

bladeSystem x HX5 7873 blade


x Hypz/VM 6.1with PTFs

Linux Virtual Server

AIX Virtual Server

Linux Virtual Server

Virtual Disk

Virtual Disk

Virtual Disk

zManager

Physical Storage

LUNs

LUNs made available to zManager through import of Storage Access List

Internal HDD Internal HDD

Storage administration is very much the same with zManager as without

There is coordination required between the zManager storage administrator and the SAN storage administrator

Import of Storage Access List gives zManager a view of storage logical units (LUNs) available

At the time of virtual server creation you specify what LUNs from those visible to the blade will be assigned to the virtual server

z/VM has additional considerations. See GC27-2608.



20

High Level: Network ConsiderationsTwo internal networks – INMN (management) and IEDN (data). Virtual LAN

definitions (VLANs) apply to IEDN. Issues to consider:

Linux or AIX Virtual Server

Creation of VLANsRelatively simple HMC task. We did this ahead of the workshop.

Access to IEDN and assignment to VLANVirtual servers must be assigned to a VLAN to access to the IEDN. This is done at time of virtual server creation. You’ll

do this in lab.

Access to INMNGenerally speaking this is handled automatically when you

enable certain functions for the virtual server, such as GPMP or Processor Management on AIX.

Access to other networks from IEDNThis is a network administrator task and involves allowing

VLAN access to “outside” routing functions.

IEDN• VLAN 701• VLAN 702• VLAN 703

INMN

Other NetworkRouter

ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4160

Want more detail?



21

Extent of zManager ManagementzManager’s focus is on the lower portionof the management stack. The

higher-level service management is left to other existing solutions:

Hardware Management

Platform Management

Service Management

• Monitor hardware

• Manage energy usage

• Manage hypervisors• Create virtual servers

• Monitor performance

• Provision OS

• Configure middleware• Monitor applications

IBM Unified Resource Manager



22

Management “Suites”From “Ensemble Planning and Configuring Guide” (GC27-2608) comes

details on three management suites:

Entitle blades and deploy hypervisor

Manage hypervisor and microcode updates

Create and manage HMC user access

Create virtual networks

Create virtual servers

Start/Stop virtual servers

Monitor hypervisor and virtual server performance

Monitor energy usage

Create workloads, service classes and performance policies

Adjust CPU between virtual servers to manage to performance goals

Falls under “Manage” suite, which is a no-charge feature

Automate – charge feature for z/VM

and Power blades

Advanced Management – charge

feature for System x blades the includes everything Automate does

except adjustment of CPU resources,

which xHyp does not support

With some restrictions on z/VM for the creation and hypervisor code



23

Performance WorkloadsA key piece of the zManager function, this allows you to define collections

of virtual servers and have zManager monitor and manage resources

z/OSVirtual Server

AIXVirtual Server

AIXVirtual Server

z/OSVirtual Server

zLinuxVirtual Server

zLinuxVirtual Server

xHypVirtual Server

xHypVirtual Server

Workload: Production

Performance Goal: Fastest

Business Importance: Highest

Workload: Reporting

Performance Goal: Fast

Business Importance: High

Workload: Development

Performance Goal: Moderate

Business Importance: Medium

zManager monitors the relative performance of virtual servers against defined goals and, where possible, makes adjustments to

allocated CPU to help meet the performance goals for the workloads



24

Adjusting Virtual Server ResourcesSome of the hypervisors support dynamic adjustments of CPU resources

between virtual servers to meet zManager workload performance goals:

PR/SM

z/OS

z/VM 6.1with PTFs

V1.10+PTFsV1.11V1.12V1.13


x Hyp

zManager can influence the relative processor

SHARE values on z/VM

zManager can influence the CPU allocation on Power if “Shared” and

“Processor Management” enabled

The integrated System x hypervisor does not support dynamic adjustment of processor allocations

Adjustment of resources between LPARs on PR/SM may be

influenced by IRD but not zManager zManager workloads and goals tie directly to this … zManager is watching all the workloads and virtual server performance and adjusts as able



25

Summary, Part 1

M

RoutersFirewalls

M M M

MM M

Traditional Multi-system approach …

Multiple points of management … often without coordinated integration

It may be working for you … or it may not



26

Summary, Part 2

INMN

IEDN

zManager M

IBM-written software and firmware integrated into key elements of the zEnterprise system

Hardware Management

Hypervisor Management

Energy Management

Workload Management

Network Management

Virtual Server Management

HMCHMC

Documents

IBM zEnterprise zManager Workshop · © 2011 IBM Corporation IBM Washington Systems Center 8 The Unified Resource Manager (“zManager”) A set of management function for z196+zBX