Specifications

Chapter 15. Virtualization 163
Figure 15-2 zBX configuration
Each of our guest systems had a 200 GB and an 800 GB disk drive. We placed zPDT
emulated 3390 volumes on the 800 GB drive. This arrangement is not required; a guest could
use a single logical drive. The 192.168.50.xx IP addresses were intended for external
connections. The other IP ranges (192.168.51.xx and 192.168.52.xx) were for cross
communication between the guests.
SCSI tape drives are not supported with a zBX system.
Extensive information about configuring zBX systems can be found in Building an Ensemble
Using IBM zEnterprise Unified Resource Manager, SG24-7921.
15.3 Security and control
Both VMWare and zBX require careful consideration for their control points: vCenter for
VMWare and an HMC for zBX. These control points provide controls for all the virtual
machines and there might be concerns about the number of people with this level of authority.
This becomes an issue when booting a virtual machine. Before booting, the virtual machine is
in a logical Power Off state and this can be changed to a Power On state (which starts the
booting process) only through one of the control points. If a user of a virtual machine performs
a shutdown operation (resulting in a logical Power Off), then a control point must be used to
Power On and reboot that virtual machine. However, the user of a virtual machine can
restart the machine (resulting in a reboot without the Power Off function) without needing
control point access.
zBX slot 12 (x86 blade)
Linux
(guest)
VS2
192.168.50.20
192.168.51.20
192.168.52.20
SLES 16 GB
OpenVPN
Server
192.168.50.2
VLAN 52
192.168.52.0/24
Linux
(guest)
VS1
192.168.50.10
192.168.51.10
192.168.52.10
RHEL 8 GB
Linux
(guest)
VS3
192.168.50.30
192.168.51.30
192.168.52.30
RHEL 32 GB
Linux
(guest)
VS4
192.168.50.40
192.168.51.40
192.168.52.40
SLES 64 GB
zPDT
Token and UIM
Servers
192.168.50.19.xxx.xxx.xxx
External
network
WWPNs
SAN
LUNs
4 x 200 GB
4 x 800 GB
WWPNs
VLAN 50
192.168.50.0/24
VLAN 51
192.168.51.0/24