IBM z13s, Техническое руководство

Страница: 495 / 588

Appendix B. IBM z Systems Advanced Workload Analysis Reporter (IBM zAware)
467
monitored clients. FC 0101 and FC 0102 are mutually exclusive. Therefore, if you have one,
you cannot have the other. In addition, in most cases, the number of FC 0102 features on DR
must match the number of FC 0101 features on the IBM zAware host server.
B.4.2 IBM zAware operating requirements
This section describes the components that are required for IBM zAware.
IBM zAware host system requirements
The z13s and z13 servers can host the IBM zAware Version 2 server. The zEC12, or zBC12
can host a IBM zAware Version 1 server. The IBM zAware server requires a dedicated LPAR
and runs its own self-contained firmware stack.
The following components are required:
򐂰 Processors
– General-purpose CP or IFL that can be shared with other LPARs in the z13s, z13,
zEC12, or zBC12 server
– Usage estimates between a partial engine to two engines, depending on the size of the
configuration
򐂰 Memory
– Minimum 4 GB initial memory for the first six z/OS clients
– 256 MB required for each additional z/OS client above the first six z/OS clients
– 256 MB required for each additional LINUX client
– Flash Express is not supported
򐂰 DASDs
– 500 GB persistent DASD storage
– Only extended count key data (ECKD) format is supported
– Fibre Channel Protocol (FCP) devices are not supported
– IBM zAware manages its own data store
򐂰
Network (for both instrumentation data gathering and outbound alerting/communications)
– HiperSockets for the z/OS and Linux LPARs running on the same z13s, z13, zEC12, or
zBC12 server as the IBM zAware LPAR
– OSA ports for the z/OS LPARs running on a different CPC than where the IBM zAware
LPAR runs and for browser access to the GUI
– Dedicated IP address for IBM zAware LPAR
Note: Host system resources (processors, memory, direct access storage devices
(DASDs), and so on) depend on the number of monitored clients, amount of message
traffic, and length of time that data is retained.