IBM Washington Systems Center IBM zEnterprise Pre-Workshop Setup © 2011 IBM Corporation IBM Washington Systems Center This page intentionally left blank 2 © 2011 IBM Corporation IBM Washington Systems Center Sources of Information zEnterprise System Ensemble Planning and Configuring Guide GC27-2608-02 IBM zEnterprise Unified Resource Manager SG24-7921 Purpose of this presentation is to give you an overview and a sense for the tasks. Documentation gives details. 3 © 2011 IBM Corporation IBM Washington Systems Center Checklist Status 4 Create the Ensemble Performed through the System z hardware manager console Define INMN and IEDN Networks Involves a few relatively simple updates to the TCP definitions in z/OS Install and Entitle Blades Involves physically installing the blades and having zManager install the hypervisor and virtual I/O server to the blade Define Virtual Networks Virtual Networks map onto the IEDN and segregate elements of the zEnterprise. Done through the HMC. Add Storage Resources to Blades Storage Logical Units (LUNs) are assigned to blades through the HMC © 2011 IBM Corporation IBM Washington Systems Center Infrastructure – Starting Point This picture gives a sense for the state of the infrastructure prior to the activities we’ll show in this unit: INMN Switches DB2 LPAR LPAR z/OS • zBX installed next to z196 IEDN Switches Blade Center • Physical network wiring established between z196 and top of rack switches (TOR) in zBX Blade Center • z/OS LPARs defined and configured PR/SM zCPC • z196 delivered and installed • DB2 configured Bulk Pwr Hub OSA 1Gb HMC SE OSA 10Gb 5 Now ready to establish the zManager definitions © 2011 IBM Corporation IBM Washington Systems Center Ensemble Management Guide We start with a pointer to some good HMC resources: This provides an entry point to the ensemble creation process along with some good information on the process 6 © 2011 IBM Corporation IBM Washington Systems Center Ensemble Creation Process Is a relatively simple process … Specify the alternate HMC Give the ensemble a name In this case the one member was the z196 CEC named “TSYS”. Remember, the zBX was already physically installed next to the z196 and the next step will be enabling the INMN and IEDN networks. Say “Yes” to adding a member at the present time The resulting ensemble 7 © 2011 IBM Corporation IBM Washington Systems Center Checklist Status 8 Create the Ensemble Performed through the System z hardware manager console Define INMN and IEDN Networks Involves a few relatively simple updates to the TCP definitions in z/OS Install and Entitle Blades Involves physically installing the blades and having zManager install the hypervisor and virtual I/O server to the blade Define Virtual Networks Virtual Networks map onto the IEDN and segregate elements of the zEnterprise. Done through the HMC. Add Storage Resources to Blades Storage Logical Units (LUNs) are assigned to blades through the HMC © 2011 IBM Corporation IBM Washington Systems Center Implement IPv6 for Management Network (INMN) The INMN definitions added to the BPXPRMxx member: BPXPRMxx FILESYSTYPE TYPE(INET) ENTRYPOINT(EZBPFINI) NETWORK DOMAINNAME(AF_INET) DOMAINNUMBER(2) MAXSOCKETS(64000) TYPE(INET) NETWORK DOMAINNAME(AF_INET6) DOMAINNUMBER(19) MAXSOCKETS(30000) TYPE(INET) The INMN must be IPv6 9 © 2011 IBM Corporation IBM Washington Systems Center OSM CHPID Definitions for INMN Example of the INMN CHPID definitions: IOCP Definitions Showing one of two CHPID PATH=(CSS(0,1,2),10),SHARED, INMN CHPID definitions PARTITION=((CSS(2),(TOSP21,TOSP22,TOSP24),(=))), for actual system CHPARM=02,PCHID=120,TYPE=OSM CHPID PORT 0 CNTLUNIT CUNUMBR=0A00, PATH=((CSS(0),10),(CSS(1),10),(CSS(2),10)), “OSM” UNIT=OSM IODEVICE ADDRESS=(A00,015),MODEL=M,CUNUMBR=(0A00), PARTITION=((CSS(2),TOSP21,TOSP22,TOSP24)), NOTPART=((CSS(0),TOSP3,TOSPC),(CSS(1),TOSP18, TOSP19)),UNIT=OSA CHPID PORT 0 z/OS Definitions OSM Connections are dynamically created when an Ensemble is created 10 Must use Port 0 Ensemble Planning and Configuring Guide GC27-2608-02 © 2011 IBM Corporation IBM Washington Systems Center The OSX CHPID Definitions for IEDN Example of the IEDN CHPID definitions: IOCP Definitions Showing one of two CHPID PATH=(CSS(0,1,2),2C),SHARED, IEDN CHPID definitions PARTITION=((CSS(2),(TOSP21,TOSP22,TOSP24),(=))), for actual system PCHID=100,TYPE=OSX CNTLUNIT CUNUMBR=0BC0, “OSX” PATH=((CSS(0),2C),(CSS(1),2C),(CSS(2),2C)),UNIT=OSX IODEVICE ADDRESS=(BC0,015),MODEL=X,UNITADD=00, CUNUMBR=(0BC0), PARTITION=((CSS(2),TOSP21,TOSP22,TOSP24)), NOTPART=((CSS(0),TOSP3,TOSPC),(CSS(1),TOSP18, TOSP19)),UNIT=OSA OSA Express3 10 GbE 2 CHPIDS 1 PORT/CHPID CCIN 57A3 FC3370 (LR) Single Mode 9 micron LC duplex CCIN 57AD FC3371 (SR) Multi Mode 50/62.5 micron LC duplex z/OS Definitions VTAM Definitions Dynamic or Manually defined TRLEs TCP/IP Definitions INTERFACE IPAQENET, or INTERFACE IPAQENET6 11 The IEDN may be IPv4 or IPv6 … your choice Supports IOCP CHPID types: OSD and OSX (ONLY 10 GbE). PCHID = xxx0 & xxx1 Ensemble Planning and Configuring Guide GC27-2608-02 © 2011 IBM Corporation IBM Washington Systems Center Communications Server Definitions Examples of the definitions for IEDN to CommServer: Sample SYS1.VTAMLST(ATCSTRxx) APPNCOS=NONE, This is what allows ENSEMBLE=YES, the z/OS instance to CONFIG=00, participate in the CONNTYPE=APPN, ensemble CPCP=YES, CSALIMIT=0, CDRDYN=YES, DYNLU=YES, You may also dynamically MODIFY: DYNADJCP=YES, F NET,VTAMOPTS,ENSEMBLE=YES ISTCOSDF=INDLU, NETID=USIBMWZ, SSCPID=&SUBAREA., SSCPNAME=S&SUBAREA.CDRM, SUPP=NOSUP, CRPLBUF=(33,,4,,1,8), IOBUF=(100,508,8,,14,15), LFBUF=(2,,0,,1,1), LPBUF=(36,,0,,1,1), NODETYPE=EN, SFBUF=(14,,0,,1,1), XNETALS=YES 12 Sample TCPPARMS ;OSX ---- TSYS CHPID 2C -------INTERFACE OSX2C4 DEFINE IPAQENET CHPIDTYPE OSX Two CHPIDs for the IPADDR 192.168.162.10/24 IEDN, defined as 2C CHPID 2C and 2E on type OSX MTU 8992 and using IPv4 VLANID 162 VMAC ROUTALL ;OSX ---- TSYS CHPID 2E -------INTERFACE OSX2E4 DEFINE IPAQENET CHPIDTYPE OSX IPADDR 192.168.168.11/24 CHPID 2E MTU 8992 VLANID 162 VMAC ROUTEALL © 2011 IBM Corporation IBM Washington Systems Center INMN & IEDN Initialization Messages – Console Log Validation of IEDN and INMN interfaces at system startup: EZZ0162I HOST NAME FOR TCPIP IS zblc EZZ0300I OPENED PROFILE FILE DD:PROFILE EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE EZZ0700I IPV6 FORWARDING FWDMULTIPATH PERPACKET SUPPORT IS ENABLED EZZ0702I IPV6 SOURCEVIPA SUPPORT IS ENABLED EZZ0704I IPV6 MULTIPATH PERCONNECTION SUPPORT IS ENABLED EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIP EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE. EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE. IEF196I IEF237I BC2D ALLOCATED TO SYS00051 EZZ4313I INITIALIZATION COMPLETE FOR DEVICE GIG25 EZZ4340I INITIALIZATION COMPLETE FOR INTERFACE OSX2C4 IEDN EZZ4340I INITIALIZATION COMPLETE FOR INTERFACE OSX2E4 EZZ4340I INITIALIZATION COMPLETE FOR INTERFACE EZ6OSM02 INMN EZZ4340I INITIALIZATION COMPLETE FOR INTERFACE EZ6OSM01 EZD1176I TCPIP HAS SUCCESSFULLY JOINED THE TCP/IP SYSPLEX GROUP EZBTCPCS 13 © 2011 IBM Corporation IBM Washington Systems Center Other Validations of Success D NET,VTAMOPTS IST097I DISPLAY ACCEPTED : IST1189I ENCRPREF = NONE IST1189I ENHADDR = NO IST1189I ESIRFMSG = ALLSSCP ENCRYPTN = 31 ENSEMBLE = YES EXPFLTRM = 0 z/OS is participating in ensemble D NET,TRL IST097I DISPLAY ACCEPTED IST350I DISPLAY TYPE = TRL 332 IST924I ----------------------------------------------------IST1954I TRL MAJOR NODE = ISTTRL IST1314I TRLE = IUTXT02E STATUS = ACTIV CONTROL = MPC IST1314I TRLE = IUTXT02C STATUS = ACTIV CONTROL = MPC IST1314I TRLE = IUTMT020 STATUS = ACTIV CONTROL = MPC IST1314I TRLE = IUTMT010 STATUS = ACTIV CONTROL = MPC IST1314I TRLE = IUTIQDIO STATUS = NEVAC CONTROL = MPC Shows the two IEDN and two INMN TRLEs D TCPIP,,NETSTAT,DEV INTFNAME: OSX2C4 PORTNAME: IUTXP02C CHPIDTYPE: OSX SPEED: 0000010000 INTFTYPE: IPAQENET INTFSTATUS: READY DATAPATH: 0BC2 DATAPATHSTATUS: READY CHPID: 2C INTFNAME: EZ6OSM02 INTFTYPE: IPAQENET6 INTFSTATUS: READY PORTNAME: IUTMP020 DATAPATH: 0B02 DATAPATHSTATUS: READY CHPIDTYPE: OSM QUESIZE: 0 SPEED: 0000001000 14 IEDN CHPID 2C showing ready, type=OSX and speed of 10Gb CHPID 2E not shown here INMN CHPID 20 showing ready, type=OSM and speed of 1Gb CHPID 10 not shown here © 2011 IBM Corporation IBM Washington Systems Center Checklist Status 15 Create the Ensemble Performed through the System z hardware manager console Define INMN and IEDN Networks Involves a few relatively simple updates to the TCP definitions in z/OS Install and Entitle Blades Involves physically installing the blades and having zManager install the hypervisor and virtual I/O server to the blade Define Virtual Networks Virtual Networks map onto the IEDN and segregate elements of the zEnterprise. Done through the HMC. Add Storage Resources to Blades Storage Logical Units (LUNs) are assigned to blades through the HMC © 2011 IBM Corporation IBM Washington Systems Center Flowchart of Process of Installing/Entitling Blade We’ll show you the screens … first a high-level flowchart review: Indicate in HMC where you wish to add a blade or blades 16 This readies zManager to expect a blade insertion and begins the process of entitlement Physically insert the blade(s) in the selected slots of Blade Center zManager detects inserted blade and validates its acceptability Perform a “Model Conversion” which entitles the blade(s) This is what tells zManager to load the hypervisor code and virtual I/O code across the INMN to the inserted blade © 2011 IBM Corporation IBM Washington Systems Center Key Point – Microcode Load Indicates Entitlements Initial installation or MES performed by IBM CE is what tells the zManager what blades of what type are permitted in which locations: Authorized for 10 Power Blades in slots 1 – 10 of 14 in Blade Center 1 IBM CE doing initial install or MES update What we’ll show you next assumes the blades being installed are properly authorized 17 © 2011 IBM Corporation IBM Washington Systems Center Manage zBX Hardware Task Blade entitlement starts here … you see what’s already in place and begin the process for entitling new blades: Shows physical layout of two blade centers in a zBX frame Top blade center is full populated and all blades are valid, entitled and powered on Lower blade center has six of 14 slots populated. Eight slots open for additional blades 18 This specifies the seventh slot in the lower frame as the location to add a blade, or the starting point for a range of multiple contiguous blades © 2011 IBM Corporation IBM Washington Systems Center Physical Insertion of Blade zManager now expects a blade to be inserted into the blade center … In our case we inserted two blades starting at the designated slot. This screen appeared … we then went and inserted the blades zManager is now showing them as “Valid” but not yet entitled nor powered on Showing the “Blade Details” yielded this 19 © 2011 IBM Corporation IBM Washington Systems Center Perform Model Conversion This is what loads the hypervisor code, the virtual I/O server code and powers the blade on … Two new blades not yet entitled. They’re eligible for PWRBLADE based on microcode load Smart Optimizer blades already entitled Power blades previously entitled 20 © 2011 IBM Corporation IBM Washington Systems Center Complete the Model Conversion Select the two new blades and begin the entitlement … The hypervisor, not AIX 21 © 2011 IBM Corporation IBM Washington Systems Center Results of Power Blade Entitlement Select the two new blades and begin the entitlement … Two views of the new blades showing entitlement and “Operating” But AIX is not on them. You’ll do that in lab. 22 © 2011 IBM Corporation IBM Washington Systems Center Checklist Status 23 Create the Ensemble Performed through the System z hardware manager console Define INMN and IEDN Networks Involves a few relatively simple updates to the TCP definitions in z/OS Install and Entitle Blades Involves physically installing the blades and having zManager install the hypervisor and virtual I/O server to the blade Define Virtual Networks Virtual Networks map onto the IEDN and segregate elements of the zEnterprise. Done through the HMC. Add Storage Resources to Blades Storage Logical Units (LUNs) are assigned to blades through the HMC © 2011 IBM Corporation IBM Washington Systems Center Virtual Network Overview Virtual Networks provide a way to segment the IEDN so groups of virtual servers appear to be segregated on a separate network from others z/OS Virtual Server Team 1 AIX Virtual Server Team 1 AIX Virtual Server Team 1 AIX Virtual Server WAS Server HTTP Server Work Driver VLAN 701 VLANs for each lab team as well as for other work Physical IEDN Network (10Gb Flat Network Spanning Ensemble) Three elements to this task: 1. Creating the VLAN definition We’ll show screen shots for these activites 2. Giving it access to a port (or ports) on the Top of Rack Switch (TOR) 3. Granting virtual servers access to the VLAN 24 We did some of this ahead of the workshop, but you’ll get to do this yourself when you create your virtual servers © 2011 IBM Corporation IBM Washington Systems Center Creating New Virtual Network Definition Defining the VLAN definition is a relatively simple few steps: List of VLANs already defined The display Name and the VLAN ID are required. Description is optional. 25 © 2011 IBM Corporation IBM Washington Systems Center Configure Top-of-Rack Switch (TOR) This is what allows a VLAN to access a port on the TOR … Our ensemble has one node Select the IEDN TOR you wish to configure Select the TOR port Select the allowed VLANs 26 Internal Trunk means multiple VLANs may access and it stays inside the ensemble Select the VLAN you wish to use TOR and click on OK © 2011 IBM Corporation IBM Washington Systems Center Checklist Status 27 Create the Ensemble Performed through the System z hardware manager console Define INMN and IEDN Networks Involves a few relatively simple updates to the TCP definitions in z/OS Install and Entitle Blades Involves physically installing the blades and having zManager install the hypervisor and virtual I/O server to the blade Define Virtual Networks Virtual Networks map onto the IEDN and segregate elements of the zEnterprise. Done through the HMC. Add Storage Resources to Blades Storage Logical Units (LUNs) are assigned to blades through the HMC © 2011 IBM Corporation IBM Washington Systems Center Quick Review of Storage Issue We saw some of this in the second unit of the workshop … a quick review here to refresh the essential concepts: Storage LUNs logically represented in the zManager Import list of available storage resources: names, sizes and pathing (Storage Access List) Internal HDD LUNs available to the blade Perform storage device and SAN setup work LUN LUN LUN LUN LUN LUN LUN LUN SAN Storage Devices 28 Entitled blade Physical disk storage in the device Logical disks defined from the physical But not to the virtual server … you’ll do that in lab Physically the storage resides on the network-attached storage devices The zManager is informed of the SAN storage resources Blades are given access to some number of LUNs from the pool of available LUNs © 2011 IBM Corporation IBM Washington Systems Center Managing Storage Resources for a Blade With the Storage Access List imported into zManager, you may then assign LUNs to blades. And yes, they may be shared between blades in blade center. You may then elect to “Add Storage Resources” … The “Blades” tab shows all the blades known to zManager. Selecting a blade enables a small “twisty” that brings up a context menu to get to storage The result is what you’ll see in lab – each team will only “see” their own four 12GB LUNs, even though many more are available to the zEnterprise as a whole 29 … which allows you to provide a name, size and pathing information for the LUN you wish to make available to the blade © 2011 IBM Corporation IBM Washington Systems Center Checklist Status 30 Create the Ensemble Performed through the System z hardware manager console Define INMN and IEDN Networks Involves a few relatively simple updates to the TCP definitions in z/OS Install and Entitle Blades Involves physically installing the blades and having zManager install the hypervisor and virtual I/O server to the blade Define Virtual Networks Virtual Networks map onto the IEDN and segregate elements of the zEnterprise. Done through the HMC. Add Storage Resources to Blades Storage Logical Units (LUNs) are assigned to blades through the HMC © 2011 IBM Corporation IBM Washington Systems Center Review of Labs 1 and 2 The Co:Z lab is different and we’ll explain that later 31 © 2011 IBM Corporation IBM Washington Systems Center Lab One – Build Four AIX Virtual Servers The first lab will have you using zManager to build four AIX virtual servers on your team’s dedicated Power blade: Will run the “Trade” Java application that calls DB2 on z/OS Hosts the WAS plugin that serves as entry point for users JMeter simulates users at browsers driving workload This will serve as “CPU donor” in the second lab Virtual Server Virtual Server Virtual Server Virtual Server WebSphere Application Server IBM HTTP Server plus WAS Plugin JMeter workload driver Co:Z server (serves as “soaker”) Your Team’s Power Blade 1. Create the virtual servers on the entitled blade 2. Install AIX from NIM and activate on all four servers 3. Enable IPv6 on each to allow access 4. Log onto AIX and create a non-root userid 32 © 2011 IBM Corporation IBM Washington Systems Center Lab Two – Platform Performance Management The second lab will have you enabling ARM, defining workloads and service classes and driving it using JMeter to watch resource adjustments: z/OS DB2 ARM GPMP Will run the “Trade” Java application that calls DB2 on z/OS Hosts the WAS plugin that serves as entry point for users JMeter simulates users at browsers driving workload This will serve as “CPU donor” in the second lab Virtual Server Virtual Server Virtual Server Virtual Server WebSphere Application Server IBM HTTP Server plus WAS Plugin JMeter workload driver Co:Z server (serves as “soaker”) GPMP CPU ARM GPMP ARM CPU CPU Your Team’s Power Blade 1. ARM-enable HTTP and WAS 2. Configure workload, performance policies and service class definitions in zManager 3. Start JMeter driver to simulate users 4. Watch zManager adjust resources by taking CPU from the Co:Z donor VS and give it to HTTP and WAS 33 Enabling GPMP on AIX virtual servers is really done in first lab when the VS is created © 2011 IBM Corporation