IBM Washington Systems Center
IBM zEnterprise
Pre-Workshop Setup
© 2011 IBM Corporation
Unit 3 - 1
IBM Washington Systems Center
This page intentionally left blank
© 2011 IBM Corporation
2
Unit 3 - 2
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.
© 2011 IBM Corporation
3
Before we get into screen shots we need to point you to the complete source of information for setting
up the zEnterprise like what was done for this workshop. The “Ensemble Planning and Configuration
Guide” is the product documentation, the Redbook does what Redbooks do well – provide a “real world”
example and illustrate the steps associated with constructing that scenario.
In this workshop we can’t make you deep experts on the topics we’ll cover in this unit. This unit is
designed to give you an overview and a sense for the steps taken prior to your arrival.
Unit 3 - 3
IBM Washington Systems Center
Checklist Status
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
4
We’re finished with the first major activity and now onto the next …
Unit 3 - 4
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
Now ready to
establish the
zManager definitions
OSA 10Gb
© 2011 IBM Corporation
5
The workshop setup employs a handful of Power blades in a zBX that is connected to a z196 with a
z/OS LPAR. Much of the physical setup of the machine was done by the IBM CE who was onsite during
installation. So what we show you in this unit is what we did after the CE had done the work of physical
installation.
The z196 work to setup the LPARs and install z/OS is really the same as in the past. It’s a bigger, faster
machine, but those steps are the same.
The physical wiring of the zBX to the z196 is covered in some detail in the “Ensemble Planning and
Configuration Guide.” Here we stress that for networking the internal management network is provided
by a standard copper ethernet connection from the Bulk Power Hub (BPH) to the Top of Rack (TOR)
switches in the zBX, and the internal data network is provided with a fiber OSA 10Gb connection from
the z196 to a different set of Top of Rack switches. Again, the CE does this cabling.
This was our starting point.
Unit 3 - 5
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
© 2011 IBM Corporation
6
With the physical infrastructure in place and the IEDN and INMN definitions established on the intended
z/OS LPAR we may now go into the HMC and defined the ensemble. This is done through the links
shown on the chart.
Unit 3 - 6
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
© 2011 IBM Corporation
7
This chart shows the steps to create the ensemble. It’s surprisingly easy. At this point the ensemble is
really a definition maintained in the zManager without much else. But providing a name and the anchor
z196 CEC is an important first start.
You’ll notice that we did not specify the zBX. That’s because it’s already been physically installed next
to the TSYS z196 CEC and the INMN networking has been constructed. So zManager knows about the
zBX through its connection to the TSYS z196.
Unit 3 - 7
IBM Washington Systems Center
Checklist Status
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
8
Status at this point …
Unit 3 - 8
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
© 2011 IBM Corporation
9
The first thing was to implement IPv6 for the management network. The INMN network must be IPv6.
The chart shows the definition we put in place in the BPXPRMxx member for IPv6.
Unit 3 - 9
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
Must use Port 0
OSM Connections are dynamically
created when an Ensemble is created
Ensemble Planning and
Configuring Guide
GC27-2608-02
© 2011 IBM Corporation
10
The next thing was the CHPID definitions for the management network. Here we’re showing one of the
two CHPID definitions (the other CHPID for our INMN was “20”). The key here is that the type and unit
is defined as “OSM.”
The “Ensemble Planning and Configuration Guide” indicates that you must use port 0 for the INMN
connections.
Unit 3 - 10
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
Supports IOCP CHPID types:
OSD and OSX (ONLY 10 GbE).
PCHID = xxx0 & xxx1
VTAM Definitions
Dynamic or Manually defined TRLEs
TCP/IP Definitions
INTERFACE IPAQENET, or
INTERFACE IPAQENET6
The IEDN may be IPv4
or IPv6 … your choice
Ensemble Planning and
Configuring Guide
GC27-2608-02
© 2011 IBM Corporation
11
The CHPID definitions for the IEDN data network are shown here, along with some information
regarding cabling specifics from the “Ensemble Planning and Configuration Guide.” We are showing
one of two CHPID definitions for the IEDN (the other is “2E”). The Type and Unit for this is “OSX.”
The IEDN may be IPv4 or IPv6. For this workshop we have it defined as IPv4, which means our TCP/IP
definition has INTERFACE IPAQENET. The TRLEs may be manually or dynamically defined.
Unit 3 - 11
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
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
12
The ENSEMBLE=YES statement in the ATCSTRxx member is what allows the z/OS instance to
participate in the ensemble. You may also using the MODIFY command to do that dynamically. The
TCPPARMS shows the IEDN interfaces.
Unit 3 - 12
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
© 2011 IBM Corporation
13
The z/OS console log output showing validation of the initialization of the IEDN and INMN networks.
Unit 3 - 13
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
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
14
More examples of validations steps you may use.
Unit 3 - 14
IBM Washington Systems Center
Checklist Status
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
15
Status at this point …
Unit 3 - 15
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
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
16
This chart is providing a high-level flow diagram of the steps taken to install and entitle a blade in the
zBX. We offer this so the following screen shots and diagrams have some context. At a very high level
the process involves the system detecting the insertion of a blade and then loading the hypervisor code
over to the new blade. How that’s done you’ll see next.
Unit 3 - 16
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
© 2011 IBM Corporation
17
It’s important to note that installation and entitlement of a blade in the zBX must be supported by proper
licensing with IBM and recording in the zManager itself. So when the CE does the initial installation
information about the authorizations are loaded into the zManager. Authorizations may be added later
with an MES. In both cases the information in the zManager must support the actual activity you are
attempting. You can’t install and entitle a blade without the zManager understanding you’re properly
licensed for that blade.
Unit 3 - 17
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
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
18
This chart begins the story for installing and entitling a blade in the zBX. Again, recall that the zBX has
been properly installed and the management and data networks have been defined.
The “Manage zBX Hardware” task will give you the opportunity (under “Details”) to “Add zBX Blade.”
That pops up a pulldown list that allows you to specify the slot in which the blade will be installed, or the
starting point for the installation of a contiguous range of blades. The screen shots we’ll show illustrate
the installation of two blades.
The illustration to the left shows you what zManager sees as the current states of the blades in the slots
of the two blade centers in the attached zBX. You’ll notice that the top racks is fully populated with
blades that are black, red and green. The legend shows what that means – black=valid, red=powered
on, and green=entitled.
The lower blade center has six blades in that same state. We are about to show the installation of two
more blades into slots 7 and 8 of the lower blade center.
Once you select the blade center slot into which a blade will be inserted, the zManager will prompt you
to physically insert the blade. We show that on the next chart …
Unit 3 - 18
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
© 2011 IBM Corporation
19
As we mentioned on the previous chart, the zManager will prompt you to put the blade in the blade
center. That’s the graphic in the upper-left. At that point you walk to the zBX, install the blade, then
come back and click “OK” on that panel.
The zManager then reads the hardware information from the blade (or blades) inserted and determines
if what you have inserted is valid and authorized for the blade center. When it determines they are valid,
the slots are painted solid black in the graphic. You may also show “blade details” and see precisely
what zManager reports as having been installed at that location.
A status of “black=valid” does not mean it’s ready to be used. It needs to be entitled and powered on.
That is shown next.
Unit 3 - 19
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
© 2011 IBM Corporation
20
The next step in this process is to “entitle” the blades that have just been inserted into the blade center,
which implies loading the hypervisor code and other microcode to the blade. The zManager refers to
this as performing a “model conversion.” That task allows you to “Manage” and then “Add Entitlement”
to the hardware in the zBX.
The panel that displays shows the state of blades in the zBX. As we saw, some are already entitled
(those were the ones that were black, green and red). But two now show as “Not entitled,” though
they’re showing as authorized for “PWRBLADE.” It is from this panel that you initiate the entitlement
process. That is done by selecting the blades you wish to entitle and beginning the entitlement process.
That’s done under the “Select Action” pulldown list as we’ll see next.
Unit 3 - 20
IBM Washington Systems Center
Complete the Model Conversion
Select the two new blades and begin the entitlement …
The hypervisor,
not AIX
© 2011 IBM Corporation
21
With the two blades selected we then clicked on “Entitle as PWRBLADE” and then OK.
The blade moves through a series of states, from “updating” to “installing the OS” (which as indicated is
not AIX but rather the hypervisor and virtual I/O server code), then to “updating the firmware” and finally
to “install completed successfully. The “Elapsed time” shows two hours as you see. This is due to the
fairly large size of the code being loaded over the management network to the installed blade.
Unit 3 - 21
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.
© 2011 IBM Corporation
22
This chart shows the results of the entitlement … those two slots are now showing the current
entitlements and on the “Hypervisor report” they show green and “Operating.” That means the blade is
powered on and communicating with zManager.
AIX is not on these blades at this point in time. Just the lower microcode and the hypervisor code. The
installation of AIX does not take place until virtual servers are defined on the hypervisor and AIX
installation is initiated by you. You’ll do that in lab.
Unit 3 - 22
IBM Washington Systems Center
Checklist Status
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
23
Status at this point …
Unit 3 - 23
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
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
24
Earlier we made reference to internal data network called the IEDN. We indicated that is a 10Gb “flat”
network … meaning there are no routers or firewalls between endpoints on the IEDN.
Rather than having everyone see everyone else, zManager permits the creation of “virtual LANs” that
segment network traffic virtually. Servers that are assigned to a VLAN “see” only those other servers on
the VLAN. They can’t see or send traffic to other servers on other VLANs unless one of the Top of Rack
switches is configured to permit it.
In this workshop you’ll each be using your own VLAN. Each VLAN will host the three AIX servers you
create as well as the z/OS LPAR (itself a “virtual server” to zManager).
There are three steps to this process – creating the VLAN definition, configuring the Top of Rack
switches to allow the VLAN, and finally the granting of the virtual servers to the established VLANs. We
did 1 and 2 ahead of time since those are more “one time setup” activities and require higher access
authority than your lab IDs are permitted. But the 3rd one you will do as part of the lab exercises.
Unit 3 - 24
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.
© 2011 IBM Corporation
25
The “Manage Virtual Networks” task is the starting point for creating a new VLAN. Initially it will show
you the existing VLANs, and the “Select Action” pulldown will have an option for “New Virtual Network.”
Here is where you provide it a name, a description and a VLAN ID not already in use elsewhere.
Unit 3 - 25
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
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
Select the
allowed
VLANs
© 2011 IBM Corporation
26
Once the VLANs are defined we then granted the VLANs access to the IEDN top of rack switch. This is
what allows traffic to get to other blades centers in the frame, other zBX frames and to the z196 CEC.
The Top of Rack switches have numerous ports on them. Some are considered internal, some external,
some “trunk” and some “access”. Trunk means multiple VLANs may use it; access limits to a single
VLAN. For this workshop we are granting access to lab exercise VLANs to the “internal trunk” on port 9.
That’s done by selecting the task, then the node (we have one note … “TSYS”), the TOR (there are two,
it is possible to configure them identically or separately), then the port (9 internal trunk), then the VLANs
that will have access. We configured VLAN 701 – 706 for this workshop and all are granted access to
the internal trunk on the TOR.
Unit 3 - 26
IBM Washington Systems Center
Checklist Status
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
27
Status at this point …
Unit 3 - 27
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
LUN LUN
LUN LUN
LUN LUN
But not to the virtual
server … you’ll do
that in lab
Physically the storage resides
on the network-attached
storage devices
Perform storage device and
SAN setup work
LUN LUN
Entitled blade
Physical disk storage
in the device
Logical disks defined
from the physical
SAN 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
28
In Unit 2 of this workshop we went through in some detail the planning and allocation of the storage
resources on the Storage Area Network (SAN) to the zManager and the blades themselves.
The key things to keep in mind about this are:
• While there is an internal hard drive on the blade, most of the blade storage is hosted off-blade in a
SAN device somewhere
• A storage administrator has configured the physical storage on the SAN device into Logical Units
(LUNs) that are available to devices on the SAN network. The zEnterprise is one such define on the
SAN network.
• The information about the SAN device, the LUNs and pathing to that storage is imported into the
zManager by way of a “Storage Access List” which tells zManager what’s available.
• From there storage is made available to the blades, which we’ll see next.
This tells the blade and the hypervisor what’s available but what any given virtual server has access to
is something you indicate when you create the virtual server. You’ll see that in lab.
Unit 3 - 28
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
… 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
29
The Storage Access List provides the zManager with a view of all the LUNs available, the “Manage
Storage Resources” task allows you to allocate them to blade center or blade resources. For this
workshop we have a small handful of LUNs available to each blade. Each virtual server you will create
will be given a 12GB LUN for purposes of hosting AIX and other software that’s part of the lab exercises.
Unit 3 - 29
IBM Washington Systems Center
Checklist Status
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
30
Status at this point …
Unit 3 - 30
IBM Washington Systems Center
Review of Labs 1 and 2
The Co:Z lab is different and we’ll explain that later
© 2011 IBM Corporation
31
Let’s now turn to a review of the first two labs in this workshop which have steps related to the things
shown in this unit.
Unit 3 - 31
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
© 2011 IBM Corporation
32
The first lab will have you create four virtual servers on a Power blade dedicated to your team. Those
four virtual servers will run AIX and they serve these purposes:
• On virtual server will host WebSphere Application Server (WAS) with a deployed copy of the
“DayTrader” simulated stock trader application. This application will use DB2 on z/OS for its data.
DB2 is not shown on this picture but we’ll bring it into the picture when we discuss the Platform
Performance Management (PPM) function. This server will have a “w” in its name for “WebSphere.”
• Another virtual server will host the IBM HTTP Server with the WAS Plugin function. This will act as
the “entry point” to the the distributed workflow that hops from AIX to AIX and then up to DB2 z/OS.
This server will have an “h” in its name for “HTTP Server.”
• A third virtual server will act as the place where the simulated user workload driver tool called
JMeter. We’ll use this tool to drive HTTP requests into the workload so we can see “real”
performance results rather than trivial results from you being the only user and clicking the mouse a
few times. This JMeter server will have a “d” in its name for “driver.”
• The final virtual server is going play a dual role – in the first two labs it will serve as the “donor”
server and will give up its CPU resources to the to other servers when zManager determines the
performance goals are not being met. We will have you run “soaker” programs which use CPU. In
the last lab will will go in an entirely different direction and show how a tool called “Co:Z” can be
used to offload certain work from z/OS to the zBX blades. Because of this last “Co:Z” element the
name of this virtual server will have a “c” in its name. But the Co:Z part isn’t really used until the last
lab.
The steps to create your virtual server and install AIX are shown on the chart. The full details of this are very
clearly spelled out in the lab instructions you’ll receive.
Unit 3 - 32
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:
Will run the “Trade”
Java application that
calls DB2 on z/OS
z/OS
DB2
ARM
GPMP
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
In the second lab you’ll then use the virtual servers you created to drive a workload and observe how
zManager’s Platform Performance Management (PPM) function will monitor performance and make
adjustments to meet your defined goals.
The workload we’ll have you run is a fairly standard 3-tier design that hops from HTTP Server to WAS to
DB2 on z/OS. But driving the workload is not really the objective … the objective is to define a
zManager workload with performance goals and see how zManager reacts. To do this you’ll make use
of Guest Platform Management Provider (GPMP) and Application Response Measurement (ARM)
mechanisms so zManager can see how things are performing and adjust as needed and allowed.
We mentioned the Co:Z “soaker” server earlier … this will be the “donor” for CPU. zManager will see
that the defined workload running on your HTTP and WAS servers is not meeting the defined goals. So
it’s going to take CPU from the soaker AIX and give it to the WAS and HTTP virtual servers. In so
doing, you’ll see the “Performance Index” (PI) value come down from a “I’m not meeting goals!” level to
a value closer to “1” which means goals are being met.
We have a whole unit on Platform Performance Management so you’ll see much more on what GPMP
and ARM are and how they work with zManager in managing performance.
End of Unit
Unit 3 - 33