z/vm Data Collection for zpcr and zcp3000 Collecting the Right Input Data for a zcp3000 Capacity Planning Model

Transcription

1 IBM z Systems Masters Series z/vm Data Collection for zpcr and zcp3000 Collecting the Right Input Data for a zcp3000 Capacity Planning Model Session ID: cp3kvmxt 1

2 Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. For a complete list of IBM Trademarks, see *FICON, IBM, IBM (logo), S/390, Sysplex Timer, System z, System z9, System z10, zenterprise, z9, z10, z/architecture, z/os, z/vm, z/vse, zseries The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-ibm products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the 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. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. 2

3 Complex Environment

4 Complex Environment 2012 z/196 with 22.6 engines 3 different SCPs : 10 z/os images 5 z/vm images 30+ Linux guests Sysplex and at least one more mainframe Complex Environment 2013: Let s put all of the z/vms with production Linux guests into an SSI! 4

5 How to model a complex environment Find out what will make your customer s plan successful. Who are your loved ones now? Who will be your loved ones next year? Who needs to be playing nicely in the same sandbox? Do backup/recovery systems need to be included in the capacity plan? Have you thought about the RNI and other hardware implications of partition weighting, etc? Have you thought about how to exploit new hw features? 5

6 How much data should I collect? What are you trying to do? Normal upgrade, regular growth, keep up with technology Server Consolidation no growth, just slap em all together as little as one image per mainframe* Extraordinary growth of existing applications (ie, bank merger) Bring new z applications online Port non-z applications Capture the *right* period of time, that is representative of what you want to do. Collect 1 week, maybe 2 if variability is not well understood. Assume 24x7 unless proven otherwise (global timezones, z/os batch window, Linux cron tasks ) All production systems, as identified by the customer All sysplex members; include Test/Dev sysplexes, if sysplex link consolidation is one of the objectives. CPUMF to get zpcr workloads correct. All partitions that belong together as a production group * Partition data for all partitions is collected by z/os and z/vm if HMC Global Performance Data setting is enabled. 6

7 Data Extract Utilities Build an EDF for One Image Supporting: z/os, z/vm, z/vse CP Monitor =~ SMF Processor configuration Detail on SCP, workload and i/o Coupling Facility activity For VSE, use CPU Monitor Tool to collect data, then zcp3000 to create the EDF. Note: VSE data collection does not include CPUMF data. Intervals are accumulated into longer durations, which will be the reporting interval One EDF per data extract run EDFs from *different* sysids can be (have to be) loaded at the same time into zcp3000. EDFs from the same sysid must be merged (zcp3000 function) *BEFORE* they can be loaded. 7

8 Data Flow zpcr Study z/vse VSE2EDF z/vm CPU Monitor Tool VM Monitor Data CP3KVMXT Business Unit Definition PGNMAP SYSID..EDF One per partition. Add next graph Dynamically Build a zcp3000 Report z/os SMF + RMF/CMF CP3KEXTR Type 30 Data Disk Magic Data HTML document +images Done? CSV BCUMAP I/O Config Definition SMF 30 Analysis Browser Standard Office Software 8

9 Merge vs load EDF Merge EDFs: same sysid, different days Load EDFs: different sysids, *same intervals* Merge, then load merged EDFs + z/os EDFs Top left partition always has data Partiton name ^= sysid -> you have data Partition name == sysid -> maybe you have data If only one workload WORK_SYS_partitionName -> no data collected for this sys. 9

10 z/vm: Data Collection Requirements Monitor Records used by CP3KVMXT Processor - sample and event (includes 113 CPUMF) Storage - sample User - sample and event I/O* - sample and event (class dasd only) (i/o collection is optional, not required for zcp3000) Records not used by CP3KVMXT Network Scheduler Seeks Application SSI - should *NOT* be enabled for events - should *NOT* be enabled for events 10

11 Data Collection for systems running under z/vm Most of the time, this is not going to work for you. Therefore, most of the time, you will need to treat the system image running as z/vm guest, as a black box, and *not* try to look at the 2 nd level detail. And therefore, a 2 nd level guest under z/vm won t be able to use detailed analysis such as ztpm More on this in the backup slides. 11

12 Data Collection for z/vm : Collecting Monitor Data Domains: Sample Processor Storage User I/O Dasd Event Processor Storage User I/O Dasd Interval 1-5 minutes 12

13 Default monitor settings before z/vm 6.2 are not enough Before z/vm 6.2, the default settings can support only about 3600 online & offline devices. MONDCSS Sample Config Space z/vm 5.4 default zvm2a actual zvm2a minus non-dasd Pages If MONDCSS Sample Config fills up, the monitor data will be missing key configuration records required by zcp3000, and the data collected will be unusable. 13

14 How much space for monitor data? ZVMD1A system : z/196 w/ 8 real engines, 9 partitions, 27 partition engines, Workload : 62 userids, 66 virtual engines 37 minutes of data, using a 1 minute interval 59,046 records Here s part of the problem: 22,295 device config records 317 online dasd devices 58 other online devices 21,920 offline subchannels 13,838 device activity (37*375) 5420 cache activity (37*146) 74.2% total space k block (21.3 cylinders) : 37 minutes 62,230 4k block (345 cylinders) : 10 hours Enable only dasd class 3.9% eliminate non-dasd activity records? eliminate idle dasd activity records Use a longer sampling interval 17.4% using a 2 minute interval 27.9% using a 5 minute interval * Savings would be higher as this considers only space for i/o records 14

15 Making the process easier with CP3KVMXT PREVIEW System ZVMD1 - processing Monitor records All records required for zcp3000 are present. CPUMF Hardware monitor records are not present in this data. APAR VM64961 must be installed on Z/VM to generate CPUMF records. Data collection started: :19: last timestamp: :56: CP monitor interval = 1 minute. use this to select duration SCP version/release = Z/VM Hipervisor = LPAR CPU model = Also, which domains are Devices monitored = enabled for: Logged on users = 61 Users w/ active CMMR = 41 event monitoring General purpose CPs = 3 IFL engines = 4 sample monitoring ziip engines = 0 zaap engines = 0 ICF engines = 1 15

16 Making the process easier do a small test run Use a 5 minute duration (for 1 minute interval) Specify a limit of 2 durations Look for error messages and fix them now. Using DURLIMIT = 2 durations. Scanning monitor data file for configuration records. CP3KVMXT Version V2R6I all users put in DEFAULT uclass enterprise=zvmd :19:54.. User event domain disabled (should be enabled). User workload values may be wrong for intervals when that user logged on & off. Processor event domain disabled; it should be enabled. 16

17 Making the process easier with a small test run If it makes it through duration 0, you re probably good. 08/29 15:19 Read monitor record 2... D1 system configuration 08/29 15:19 Read monitor record D1 system configuration 08/29 15:19 Read monitor record D1 system configuration 08/29 15:19 Read monitor record D1 system configuration 08/29 15:19 Read monitor record D1 system configuration 08/29 15:21 Read monitor record D4 user sample 08/29 15:21: D1RB end of interval. Elapsed= /29 15:22: D1RB end of interval. Elapsed= /29 15:23: D1RB end of interval. Elapsed= /29 15:24: D1RB end of interval. Elapsed= /29 15:25: D1RB end of duration 0. Elapsed = 5.00 secs = end of duration processing time = Load the test EDF into zcp

18 Using EDFs in zpcr On zpcr main menu, select Define LPAR Host Load the LPAR configuration from EDF(s) Select an interval. zpcr will use CPUMF to pick the workload. 18

19 Resources Get tools, guides, education from the CPSTools Alerts & Ideas & the zcp3000 Google Group: (restricted access, please request access from cpstools@us.ibm.com) Tech support cpstools@us.ibm.com Need help? Work with Global Techline for the study and to collect the data. Use the link on the CPSTools page. 19

20 Backup Slides 20

21 Data Collection for z/os systems running under z/vm 2098-Q04 : 4 GCPs, 1 ziip, 1 ICF, and 1 IFL 2098-E10 : 5 GCPs 21

22 Data Collection for z/os systems running under z/vm MVSPRODA z/os sees z/vm sees How can the z/os and z/vm view differ so much? lutil% lutil% 12/12/12 5:59 94% 82.9% 12/12/12 6:59 90% 74.2% 12/12/12 7:59 93% 72.3% 12/12/12 8:59 86% 69.1% 12/12/12 9:59 95% 73.0% 12/12/12 10:59 94% 73.1% 12/12/12 11:59 88% 71.0% 12/12/12 12:59 89% 73.5% 12/12/12 13:59 98% 73.2% 12/12/12 14:59 95% 78.8% 12/12/12 15:59 96% 74.1% 12/12/12 16:59 93% 68.8% 12/12/12 17:59 85% 69.5% 12/12/12 18:59 68% 57.0% 12/12/12 19:59 60% 47.7% 12/12/12 20:59 56% 42.9% 12/12/12 21:59 49% 35.1% z/vm reports 4 virtual GCPs and 1 virtual ziip for MVSPRODA. The z/os edf reports 5 GCP engines, but one of these is actually the ziip. Partition Data Report is invalid for a VM guest, so for z/os, utilization is based on CPUWAIT. CPU seconds used should equal total possible time minus CPUWAIT, *unless* you are using shared engines. When engines are shared, z/os does not know about the time other users/partitions are using. All other users on VMPROD (except the CFs) are sharing the GCP resource. 22

23 Using Specialty Engines in z/vm Partitions w/ mixed engine types can be tricky Why doesn t VMPROD use any IFL? CPU Affinity says a virtual processor should run on the same real processor type if possible. Most VM users and Service Machines do not have a CPU definition, defaulting to CPU 0, type GCP. How could VMPROD use the IFL? Define Linux or CMS guests with Linux VCONFIG mode COMMAND SET VCONFIG MODE LINUX Define the guest/user with virtual IFL engines COMMAND DEFINE CPU 00 TYPE IFL 23

24 Using Specialty Engines in z/vm Partition Mode ESA390 mode (default) supports real GCP, ziip, zaap Linux mode IFL *or* GCP, runs CMS or Linux SCP guests VM mode supports GCP and all specialty engines Testcase z10bc w/ VMPROD & zvm1 VMPROD has 3 z/os guests which use ziip, 1 Linux guest, 2 Coupling Facilities, and 35 or so CMS users and service machines VMPROD uses virtual GCP, ziip, ICF, and IFL engines. ESA390 Mode Linux Mode ESA390 Mode : Guests can have virtual specialty engines, which execute on real GCP engines. z/os guests are using virtual GCP & ziip Linux guest is using virtual IFL CFs are using virtual ICF 35 other VM users are using virtual GCP 24

25 Using Specialty Engines in z/vm ESA390 Mode Linux Mode VMPROD will use real GCP and real ziip. z/os guests are using virtual GCP & ziip, which execute on real GCP and real ziip. Linux guest is using virtual IFL on real GCP. CFs are using virtual ICF on real GCP. 35 other VM users are using virtual GCP VM Mode Linux Mode VMPROD will use real GCP, ziip, IFL, and ICF. z/os guests are using virtual GCP & ziip, which execute on real GCP and real ziip. Linux guest is using virtual IFL on real GCP. CFs are using virtual ICF on real GCP. 35 other VM users are using virtual GCP 25

26 Cookbooks, and useful stuff in the CP3KVMXT user s guide Table of Contents OVERVIEW PLANNING FOR CP3KVMXT DATA COLLECTION CP Monitor Requirements Using Monwrite To Save Monitor Data in a File Estimating the Space Needed for a Monitor Data File CP3KVMXT INSTALLATION AND SETUP RUNNING CP3KVMXT Start with a Small Test Run Preview the Saved Monitor File COOKBOOK: Using Realtime Monitor Data COOKBOOK: Using Saved Monitor Data APPENDIX A: SYNTAX APPENDIX B: PROBLEMS AND SOLUTIONS APPENDIX C: SPEEDING UP CP3KVMXT 26

27 Thank you! 27