• Share
  • Email
  • Embed
  • Like
  • Private Content
Jak skutecznie wykorzystać zBX
 

Jak skutecznie wykorzystać zBX

on

  • 527 views

 

Statistics

Views

Total Views
527
Views on SlideShare
527
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Jak skutecznie wykorzystać zBX Jak skutecznie wykorzystać zBX Presentation Transcript

    • IBM zEnterprise - Freedom through DesignIBM Blade Center Extension – How to effectively use it ?Mike StorzerCertified Senior IT SpecialistTMCC R&D Client Centers, Boeblingen Lab © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerAgendazEnterprise/zBX Technical Overview – Update – Unified Resource Manager – zBX Blades – zBX HighAvailabilityUnified Resource Manager – live demo2 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerWhat is zEnterprise all about ? … it’s ALL about the workload… Subset representing a specific workload Web Firewall Servers Database Storage Router Server Router Connected Integrated Flexible, Dynamic, and Responsive Aligned with Business Application Objectives Servers3 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource Manager It’s ALL about the workload… Unified Resource and Workload Management zBladeCenter Extension Private, secure networks Firewall Web Servers Connected Integrated Storage Flexible, Dynamic, and Responsive Application Servers – Database z/OS – zLinux – AIX – Aligned with Business Distr. Linux - Windows Server – z/OS Objectives zEnterprise 4 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerA “System of Systems” for Predictable Service Delivery IBM zEnterprise™ 196 (z196) or IBM zEnterprise 114 (z114)  Optimized to host transaction, and mission-critical applications  The most efficient platform for large-scale Linux® consolidation  Massive scale-up – 26 MIPS to over 50K MIPS zEnterprise Unified Resource Manager  Unifies management of resources, extending IBM System z® qualities of service end-to-end across workloads  Provides platform, hardware and workload management zEnterprise BladeCenter® Extension (zBX)  Selected IBM POWER7® blades and IBM System x® blades for deploying applications in a multi-tier architecture  High-performance optimizers and appliances to accelerate time to insight and reduce cost  Dedicated high-performance private network5 © 2011 IBM Corporation © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerWhat is a Ensemble?  An ensemble is a collection of up to eight x86 Power Linux Linux Linux Virtual Machine Virtual Machine Virtual Machine Virtual Machine Virtual Machine zOS zOS zOS zOS zOS Linux Linux Linux AIX AIX AIX Linux Linux Linux AIX AIX AIX ISS Linux Linux Linux zEnterprise nodes that are managed collectively AIX AIX AIX ISS DP Linux Linux Linux AIX AIX AIX ISS Cell DP Linux Linux Linux AIX AIX AIX DWA Cell DP DWA HPC z/VM DWA xHyp pHyp xHyp pHyp PR/SM xHyp pHyp by the Unified Resource Manager as a single xHyp pHyp xHyp pHyp Z CPU, Memory and IO AMM AMM SE AMM SE z Blade Extension z Blade Extension logical virtualized system z Blade Extension  A zEnterprise node is a z196/z114 with 0 or 1 HMC – Unified Resource Manager Linux Linux Linux Virtual Machin e Virtual Machin e Virtual Machin e Virtual Machin e Virtual Machin e Virtual Machin e zOS zOS zOS zOS zOS zBX. The zBX may contain from 1 to 4 racks z/VM each containing up to two BladeCenters. At Z CPU, Mem or y an d IO PR/SM least one node must have a zBX installed SE SE  zEnterprise nodes are deployed within a single x86 Power Linux Linux Linux Virtual Machine Virtual Machine Virtual Machine Virtual Machine Virtual Machine zOS zOS zOS zOS zOS Linux Linux Linux AIX AIX AIX Linux Linux Linux AIX AIX AIX ISS Linux Linux Linux AIX AIX AIX ISS site DP Linux Linux Linux AIX AIX AIX ISS Cell DP Linux Linux Linux AIX AIX AIX DWA Cell DP DWA HPC z/VM DWA x Hyp pHyp xHyp pHyp PR/SM xHyp pHyp xHyp pHyp  Automated failover to ensemble back up HMC xHyp pHyp Z CPU, Memory and IO AMM AMM AMM SE z Blade Extension SE z Blade Extension z Blade Extension x86 Power An ensemble allows you to have a single Linux Linux Linux Virtual Machine Virtual Machine Virtual Machine Virtual Machine Virtual Machine zOS zOS zOS zOS zOS Linux Linux Linux AIX AIX AIX Linux Linux Linux AIX AIX AIX ISS Linux Linux Linux pool of resources –integrating system AIX AIX AIX ISS DP Linux Linux Linux AIX AIX AIX ISS Cell DP Linux Linux Linux AIX AIX AIX DWA Cell DP DWA HPC z/VM DWA x Hyp pHyp and workload management across the xHyp pHyp PR/SM xHyp pHyp xHyp pHyp xHyp pHyp Z CPU, Memory and IO AMM multi-system, multi-tier, multi-architecture AMM AMM SE SE z Blade Extension z Blade Extension z Blade Extension environment. zEnterprise Node zEnterprise Ensemble6 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerzBX – A Uniquely Configured Extension of the zEnterpriseLooks like a rack with BladeCenters in it … but so much more  Creating an integrated solution experience … blades are easier to deploy and manage – Increased optics for fibre channel connections – Infrastructure built and tested at the factory – zBX hardware redundancy provides improved availability – IBM System z engineer for installation, service and upgrade process  Improving the connectivity between blades and IBM System z – Isolated, secure, redundant network dynamically configured – High speed 10Gb/EN dedicated network for data – New 1 GbE optics for access from zBX to customer network (routers only) – Lower latency due to fewer devices  Preserving the customer application architecture – No modifications required for operating systems or applications – No System z software running in IBM zEnterprise BladeCenter Extension (zBX) – Customer network and storage architectures unchanged … managed by the zEnterprise Unified Resource Manager7 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerNew Blades Provide Added Flexibility for Workload Deployment andIntegration IBM zEnterprise  IBM System x Blades BladeCenter Extension (zBX) – IBM BladeCenter HX5 7873 dual-socket 16-core blades Machine Type: 2458 Mod 002 – Four supported memory configurations for zBX – 64 GB, 128 GB, 192 GB, 256 GB Optimizers • IBM WebSphere DataPower Integration  IBM POWER7 Blades Appliance XI50z for zEnterprise – IBM BladeCenter PS701 8-core processor 3.0GHz – Three configurations supported in zBX - 32 GB, 64 GB, 128 GB Select IBM Blades  Flexibility in ordering – acquired though existing channels, • IBM BladeCenter PS701 Express including IBM • IBM BladeCenter HX5 (7873)  Unified Resource Manager will install hypervisor on blades in One to four – 42u racks – capacity for the zBX up to 112 blades – Integrated hypervisor (KVM-based) for System x blades – PowerVM Enterprise Edition for POWER7 blades • Up to 112 PS701 Power blades • Up to 28* HX5 System x blades  Up to 112 Blades supported on zBX • Up to 28 DataPower XI50z blades (double- wide) – Ability to mix and match blades in the same chassis – Number of blades supported varies by type  Blades assume System x warranty and maintenance when installed in the zBX *Support for 56 System x blades (March 30, 2012)8 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerPutting zEnterprise System to the TaskUse the smarter solution to improve your application design System z Hardware Management Console (HMC) System z Host Select IBM Blades Optimizers with Unified Resource Manager DataPower XI50z DataPower XI50z z/TPF Linux on Linux Linux on Windows AIX on z/OS ® System z on System x on System POWER7 z/VSE® System z x z/VM Blade Blade Blade Virtualization Virtualization Virtualization System z PR/SM™ z HW Resources Blade HW Resources Support Element zBX Private data network (IEDN) Unified Resource Private Management Network INMN Manager Private Management Network (information only) Customer Network Private High Speed Data Network IEDN Customer Network9 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerzEnterprise Unified Resource ManagerHardware Management Hypervisor Management Energy Management  Monitoring and trend reporting of CPU energy  Integrated deployment and configuration of efficiency hypervisor  Hypervisors (except z/VM) shipped and serviced as firmware  Management of ISO images  Creation of virtual networks Hypervisors Energy Operational Controls  Auto-discovery and configuration support for new resources (including storage) Operations Performance  Cross platform hardware problem detection, reporting and call home  Physical hardware configuration, backup and restore Networks Virtual  Delivery of system activity using new user Servers interface HMC Network Management  Monitoring and collecting metrics of networking resources  Management of virtual networks including access control Key  Manage suite  Adv Mgmt suite10  Automate suite © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerzEnterprise Unified Resource ManagerPlatform Management Hypervisor Management Energy Management  Manage and control communication  Static power savings between virtual server operating systems  Ability to query maximum potential power and the hypervisor Resource Workload Hypervisors Energy Awareness and Platform Performance Management  HMC provides a single consolidated and Operations Performance consistent view of resources   Wizard-driven set up of resources in accordance with specified business process   Ability to monitor and report performance Networks Virtual   Load balance recommendations Servers  Manage to a performance policy HMC Virtual Server Lifecycle Management  Single view of virtualization across platforms.  Ability to deploy multiple, cross-platform virtual servers within minutes  Management of virtual networks including access Key control  Manage suite  Integration of HiperSockets network with IEDN  Adv Mgmt suite11  Automate suite © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource Manager Heterogeneous Virtual Infrastructure Management APP APP APP APP APP APPServiceManagement MIDDLEWARE MULTIPLE OPERATING SYSTEMS Linux on System x e.g., z/OS, z/TPF, z/VSE, z/VM, AIX 1 Linux on System zPlatformManagement VIRTUALIZATION – PR/SM, z/VM, PowerVM, System x Hypervisor FIRMWAREHardwareManagement System z Power System x1 IBM Optimizers Unified Resource Manager 12 1 All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, © 2011 IBM Corporation and represents goals and objectives only.
    • IBM zEnterprise zBX & Unified Resource ManagerUnified Resource Manager APIsEnabling external management tools  New API support allows programmatic access to the same underlying functions exploited by the HMC user interface (UI) – Same resource types, instances and policies – HMC UI steps are accomplished using panels in a wizard- style task while API steps are accomplished by calling API management primitives UI API – Therefore the API functions correspond to views and tasks in the UI such as: HMC Listing resource instances Creating, changing, deleting resource instances Operational control of resource instances  Access to these functions will enable tools external zEnterprise System to the HMC to manage the Unified Resource Manager  Initially the priority scenarios will be the discovery, monitoring, and provisioning use cases13 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerzEnterprise Unified Resource ManagerManagement of zEnterprise from external tools Application Programming API allows programmatic access Interface (API) is a new to the same functions exploited implementation in the HMC by the HMC UI. Corresponding to  Build on existing SNMP/CIM views and tasks in the UI such function plus new Unified as: Hypervisors Energy Resource manager capabilities  List and get properties for core  TCP/IP Sockets/HTTP is (traditional) entities, ensemble, underlying network support workloads, virtual networks, with SSL for connection Operations Performance virtual hosts, virtual servers, security storage, zBX infrastructure (as  Supports modern scripting well as provide start/stop/restart languages (e.g., Perl, Python) for many of these also) that have HTTP supporting Networks Virtual  Can provide service oriented libraries Servers functions like metrics retrieval  Fully documented and and inventory supported for customer and HMC  Manage energy management third-party use modes  HMC UI remains in place,  Help on recover actions of supported and will continue to virtual actions be extended as Unified  And more … Resource Manager evolves  APIs are governed by the functions they involve such as ‘Manage’ or ‘Automate’14 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerHMC API and UI Provide Same Level of Function• Example: Creating a Virtual Server on an IBM Blade• Regardless of the interface used, this is accomplished through a series of steps: Assign virtual server Create virtual server Activate virtual server to workload Select hypervisor for Define virtual server Define virtual server Add storage to virtual Specify virtual server new virtual server characteristics network connectivity server options •Name, description • Select from among •Select from storage •Example: Specify •Virtual or dedicated defined virtual resources previously the boot device type virtual processors networks defined to hypervisor and instance: •Number of virtual • Disk processors • Network •Amount of memory • ISO15 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerHMC API and UI Provide Same Level of Function (con’t)• HMC UI: Steps are accomplished using panels in a wizard-style task Assign virtual server Create virtual server Activate virtual server to workload Select hypervisor for Define virtual server Define virtual server Add storage to virtual Specify virtual server new virtual server characteristics network connectivity server options16 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerHMC API and UI Provide Same Level of Function (con’t)• zManager API: Steps are accomplished by calling management primitives of the API Note: Function names listed below are conceptual, not the actual API syntax Assign virtual server Create virtual server Activate virtual server to workload Select hypervisor for Define virtual server Define virtual server Add storage to virtual Specify virtual server new virtual server characteristics network connectivity server options•Call List-Hypervisors •<Create VS> •Call List-VNetworks •Call List-Stg-Resourcces •<Select bootfunction to obtain a list •Call Create-VS function to obtain function to obtain list of device>of hypervisors function specifying current virtual available volumes •Call Update-VS•<Invoking application selected hypervisor networks •<Select volume> function to setselects desired as target and basic •<Select network> Call Add-VDisk function boot devicehypervisor> VS parameters to get •Call Add-VNIC specifying new VS as target base VS created function specifying and selected storage new VS as target and resource virtual network parameters17 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerService Management extends zEnterprise Firmware Functionality forHeterogeneous Environments zEnterprise zEnterprise extended by Unified Resource Manager IBM Service Management Center  Workload-based Resource Allocation & provisioning  Visibility, Control and Automation for Applications, for zEnterprise Transactions, Databases, all Datacenter Resources  Physical & Virtual Resource Management  Goal Oriented Management of zEnterprise resources  End-to End Workload Management and Service Level (Availability, Performance, Energy, Security) Objectives Align IT Management with Business Goals  Faster transaction processing with reduced network latency  Common usage and accounting for business accounting  Dynamic/Centralized management of Application Workloads based on policies  End-to-End Enterprise Security  Business Resiliency for Multi-site recovery  Multi-site Storage management and disaster recovery  High availability and disaster recovery for the cloud  Cloud provisioning and management  Operational Controls for Hardware/Firmware  Asset and Change Management for physical and virtual resources  Service & Support for Hardware/Firmware  Hardware configuration management18 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerIBM WebSphere DataPower Integration Appliance XI50 for zEnterprise(DataPower XI50z) helps extend the value of zEnterprise Purpose-built hardware for simplified deployment and hardened security helps businesses quickly react to change and reduce time to market What is it? How is it different? The IBM WebSphere DataPower Integration  Security: VLAN support provides enforced Appliance XI50 for zEnterprise can help simplify, isolation of network traffic with secure private govern, secure and integrate XML and IT services networks. by providing connectivity, gateway functions, data transformation, protocol bridging, and intelligent  Improved support: Monitoring of hardware with “call home” for current/expected problems and load distribution. support by System z Service Support Representative.  System z packaging: Increased quality with pre- testing of blade and zBX. Upgrade history available to ease growth. HTTP MQ JMS FTP IMS  Operational controls: Monitoring rolled into System z environment from single console. Consistent change management with Unified CSV Resource Manager. COBOL XML SOAP19 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerIBM WebSphere DataPower Integration Appliance XI50 for zEnterprise DataPower XI50z (2462-4BX) – Same hardware as DataPower XI50B (4195-4BX) “Double-wide” Blade: 2 BladeCenter slots IBM HS22 Blade + DataPower expansion unit – Current firmware based on DataPower firmware v3.8.1 – New firmware based on DataPower firmware v4.0.1 – Same Acceleration, Security, and Integration capabilities Can coexist with POWER7 and IBM System x blades in the same zBX BladeCenter Leverages advanced zBX BladeCenter networking infrastructure – 2 x 1 GbE interfaces to zBX 1 GbE top of rack switches (INMN) – 2 x 10 GbE interfaces to zBX 10 GbE top of rack switches (IEDN) Ordering, configuration and installation – Hardware and firmware are configured and ordered by eConfig as zBX features – Ships installed in a new-build zBX or field installed by IBM service as an MES Tightly integrated with zEnterprise – Hardware and firmware management by Unified Resource Manager – Inherits zEnterprise Ensemble serviceability, monitoring and reporting capabilities20 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerIBM POWER7 PS701Express Blade General-purpose computing platform – Housed in standard BladeCenter H chassis inside IBM zEnterprise BladeCenter Extension enclosure – Up to 112 blades • 14 blades per BladeCenter • 2 BladeCenters per rack • 4 racks per zBX Model 2 Managed by the IBM zEnterprise Unified Resource Manager Virtualized with firmware-supplied hypervisor  8 cores Entitled through System z firmware  Single Wide• Performance and Energy Efficiency  3.0GHz POWER7 • Single-wide 8-core with three configurations  Up to 128GB of Memory • POWER7 processor-based PS blades automatically optimize performance • Ideal for highly virtualized environments with demanding commercial workload performance • Virtualization performance and scalability superior to IBM System x Blades • Pioneering EnergyScale technology and IBM Systems Director Active Energy Manager™ software • Take advantage of the power of IBM’s industry-leading UNIX operating system, AIX21 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerIBM BladeCenter PS701 (8406-71Y) Configurations for zBX  IBM BladeCenter PS701 (8406-71Y) – POWER7 8 Core Processor Blade FC# Config 1 Config 2 Config 3 – 8 Processor Cores activated Processor 1 1 1 3.0GHz@150W – 1 Processor socket – Single wide Blade only Processor Activations 8411 4 4 4 – 3.0GHz 8412 4 4 4 – 16 dimm slots (4 or 8 GB DIMMs) Memory kits 32 GB 64 GB 128 GB – 300GB HDD Internal Disk 8 GB (2 x 4 GB) 8208 4 8 0  3 Configurations shown are supported 16 GB (2 x 8 GB) 8209 0 0 8  POWER7 Blades may be acquired by the HDD 300GB 8274 1 1 1 customer through existing channels or through IBM 8406-8275 QLogic 2-port 10Gb Converged Network Adapter (CFFh) 8275 1 1 1  PowerVM Enterprise Edition licence and 8406-8242 QLogic 8Gb Fibre Channel 8242 1 1 1 Software Maintenance Agreement is required Expansion Card (CIOv) for all 8 Cores, and must be maintained for PowerVM EE 5228 8 8 8 the duration of use. Required SW PID  PowerVM Enterprise Edition is controlled as PowerVM EE 5765-PVE zEnterprise Licensed Internal Code (LIC) SW License PID 8 8 8 (0001) – pHyp 2.1, VIOS 2.1.3 – Extensions for configuration and systems PowerVM EE 5771-PVE Choose Qty 8 of 1 YR or 3 YR management: Hardware setup, FFDC, Heartbeat, 1 YR SWMA PID (1991) PPM daemon PowerVM EE 5773-PVE Choose Qty 8 of 1 YR or 3 YR 3 YR SWMA PID (0999) Warranty and Maintenance Separate blade warranty is NOT required if in a zBX under IBM maintenance. zBX maintenance includes 24x7 on-site support for parts (including blades) and service during the 1 year System z Reference – ITSO Redpaper REDP-4655 warranty and subsequent post warranty maintenance IBM BladeCenter PS700, PS701, and PS702 Technical Overview and Introduction22 © 2011 IBM Corporation terms
    • IBM zEnterprise zBX & Unified Resource ManagerIBM PowerVM23 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource Manager IBM System x blades: IBM BladeCenter HX5 7873-A4x/A5x/A6X/A7x Four Supported Configurations: SBB Part Option Part Feature Config 0 Config 1 Config 2 Config 3 Blade * Number (7873- (7873- (7873- (7873- Client acquired, not configured or Number (for SSCT) Code A4x*) A5x*) A6x*) A7x*) shipped by System z Blade base - HX5 (7873) 1 1 1 1 manufacturing Initial Processor 1 1 1 1 Processor Chips 2.13 GHz 105W (E7-2830 8C) 69Y3071 69Y3074 A16S – Intel® Xeon® E7-2830 processor Additional Processor 69Y3072 69Y3074 A179 1 1 1 1 2.13 GHz 105W (E7-2830 8C) Nehalem microarchitecture # Intel Processors (Sockets) 2 2 2 2 Westmere-EX core (32 nm) Blade width Single Single Single Single Memory DIMMs Total Cores 16 16 16 16 – DDR3, 1333 Mhz capable Memory 8 GB 1333 MHz 46C0558 46C0570 A17Q 8 16 8 0 – Operating frequency 1066 MHz Memory 16 GB 1333 MHz 49Y1527 46C0599 2422 0 0 8 16 – 6.4 GT per second GB/Core 4 8 12 16 Speed Burst Card Speed Burst Card 46M6843 59Y5889 1741 1 1 1 1 SSD Expansion Card SSD Exp Card 46M6906 46M6908 5765 1 1 1 1 50GB MLC SSD 43W7727 43W7726 5428 2 2 2 2 SSD Internal Disks (Two 50 GB) 9012 1 1 1 1 No Internal Raid – Hypervisor storage controlled by Broadcom 10Gb virtual fabric 1 1 Unified Resource Manager CFFh 46M6170 46M6168 0099 1 1 10 GbE 2-port Expansion Card Qlogic 8 Gb Fibre Channel Expansion Card CIOv 44X1946 44X1945 1462 1 1 1 1 – CFFh PCIe 2.0 x16 slot Link to the IBM Standalone Solutions Configuration Tool (SSCT): http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=MIGR-62168 QLogic 8Gb FC Expansion Card *The last character in the SSCT model is determined by geography. “U” is correct in the USA. – CIOv PCIe 2.0 x4 slot It is not necessary to order extended warranty or enhanced service response. – 2 ports When a supported System x blade is installed in the zBX under IBM warranty or service, a System z SSR services the blade as part of the zBX. Typically 24 x 7, 2 hour response. 24 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerIBM System x Blade Hypervisor and Operating Systems zBX Integrated Hypervisor for IBM System x Blades – Linux Kernel-based Virtual Machine (KVM) technology – License included in z196 or z114 FC 0042 – “Manage Firmware for a System x blade”) – Supports both Linux on System x and Windows on the same blade – Includes Certified Windows1 VirtIO Drivers with installation support using the Unified Resource Manager Operating Systems – Separately acquired and licensed by the customer For license, System x blades are “2-socket servers”. Consider the number of guests required. – 64-bit Linux on System x Red Hat® Enterprise Linux (RHEL) 5.5, 5.6 and 6.0 http://www.redhat.com/rhel/versions/rhel5/ Novell® SUSE® Linux Enterprise Server (SLES) 10 (SP4) and SLES11 (SP1) http://www.suse.com/products/server/ – 64-bit Windows Server Windows Server 2008 R2 – Datacenter Edition, 64 bit version Windows Server 2008 (SP2) – Datacenter Edition, 64 bit version25 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerKVM Based - Virtualization26 © 2011 IBM Corporation
    • Discovery of Storage Resource Discovery of storage resources –Instructs Hypervisors to scan SAN for available storage resources (and paths) –Lists available storage resources and paths –Allows direct import, or creation of a Storage Access List for later import –Benefit: • Avoids issues associated with manually adding storage resource information –Supports all Hypervisor types (x86 hypervisor, PowerVM, z/VM) • Note: for z/VM, Discovery only works if the host WWPN is freePage 27 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerRecommended external network access to the zBX  There are 2 ways to get to the IEDN from an outside network. They are not mutually exclusive 1. Connect your external network router directly into an IEDN TOR switch on the zBX, using the ports designated for external connectivity 2. Connect your external network into a zEnterprise OSD OSA port. Traffic would flow through this port to a zCPC operating system (z/OS® or Linux® on System z), which would then route the traffic into the IEDN via an OSX CHPID  One is not necessarily better than the other in terms of availability. Both approaches must implement redundancy to provide high availability. Option (1) requires router redundancy, option (2) requires operating system and CPC redundancy. 1. Enter through a Router 1 connection to the TOR – Switch External Customer Data Router connections not permitted! External Customer Data L3 Network Network Virtual Server MAC Filtering TCPIP1 (z/OS1) VLAN & VMAC Enforcement IP Filtering Top of Rack OSD OSX VLAN & VMAC VLAN & VMAC Enforcement Enforcement Switch L2 2 IP Filtering Router L3 Virtual Server10B External Customer 2. Enter through an OSD External Customer VMAC-B Data Network Connection attached to an Data Network Ensemble Member.28 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerzEnterprise Ensemble with zBX: Availability Overview To ensure maximum availability for workloads in an ensemble with zBX, configure multiple nodes with sufficient zBX capacity to accommodate the work of a failing zBX. This can be accomplished in two phases: develop a single node with a zBX, deploy additional node(s). 1. zBX and CPC are designed and delivered with high levels of hardware and firmware redundancy, so losing either one is unlikely. Nevertheless, both are a single point of failure and must be redundantly configured on another ensemble node for high availability. 2. BladeCenters and blades also contain single points of failure, so virtual servers and disks needing high availability must be redundantly configured on failure isolated components. (e.g. back up blades in a different BladeCenter in a different frame or zBX.) Because of eConfig tool constraints, extra blade entitlements may need to be purchased to protect from a BladeCenter failure. (Multiple sparsely populated BladeCenter Chassis are not supported) 3. High availability of Virtual Servers running in zBX can be achieved through automated failover and recovery to/from redundant blades in the same or different zBX. 4. High availability of external data can be achieved by means of synchronous mirroring, using capabilities like Metro Mirror. If the primary disk storage system fails, a copy of the virtual server containing the secondary storage definitions can be started automatically, using scripts, to access the mirrored disks.29 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerHigh Availability Architecture: Phase 1, Start with a single zBX z196 OSD zBX TOR External OSX IP Routers ( Firewall Load HMC P TOR Balancers Network Linux® on System z BladeCenter Chassis IEDN P z/OS® S Application Server Blades DataPower HMC A (Example: single rack with 2 BladeCenters)  Blade and BladeCenter chassis configuration – Blades are a SPoF. Install redundant capacity across multiple BladeCenter Chassis  Network configuration – Deploy redundant load-balancing solutions in the external network for requests into the ensemble. Connect to redundant OSD OSA ports on the zEnterprise or to redundant ports in the TOR switches in the zBX, or both. Load Balancing solutions can receive workload insight from Unified Resource Manager APIs.  Storage and Data configuration – Follow normal best practices for HA SAN configuration, such as cabling the dual SAN switches in the zBX to two SAN fabrics with disk storage systems that have dual storage controllers. – Provide application server blades with access to primary and secondary disk systems Establish synchronous data replication with LVM, Metro Mirror and TPC-R management.  Virtual server configuration – Follow normal best practices for clustering virtual severs across blades and chassis using standard clustering technologies – Configure shared access to the same primary disks and networks for each member of the cluster – Define a copy of the virtual server configuration with access to the disks on the secondary storage system, instead of the primary storage system. This virtual server configuration is to be used when the primary storage system fails. – Plan to configure each blade with a redundant “migration partner” blade to which its virtual servers can be migrated if/when30 needed. © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerPhase 2: Deploy at least a two-node ensemble, each with its own zBX Load Balancers/Firewalls z196 zBX TOR Linux on System z HMC P z/OS TOR Sysplex Distributor Redundant Hardware IEDN – Removes CPC and zBX as potential single P points of failure – Extend clustering approaches to span the multiple ensemble nodes z196 or z114 S zBX TOR z/OS Linux on System z TOR Application Server Blades DataPower HMC A Ensemble31 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource Manager (back to Q&A)Overview of Performance Management Architecture32 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource Manager (back to Q&A)How does Ensemble SASP Load Balancing Work? Incoming ts HTTP Server Requests es u Req Load ed GPMP ard Balancer rw Fo Forwarded Communication HTTP Server Requests Fo GPMP rw ard SASP ed Re qu HTTP Server es ts Internet GPMP URM Communication HMC33 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerExample (below) external router attachment to a single zBX S W I Router #A TSample C HConventional VRRP or [ VRRP #ADesign for HSRP or HTTP1 HSRP ] SRouter WAttachment I Router #B C T Non-zBX H #B BladeCenter TOR SWITCH #A Sample IEDN Design TOR SWITCH #B for External Router Router #A Attachment to I VRRP or [ VRRP E zEnterprise ensemble HSRP or HTTP1 D node HSRP ] N with a zBX Each Router Connects Router #B to Both TORs zBX34 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerExample external router attachment to multiple zBX’s Sample IEDN Design for External Router Attachment to Ensemble: Each Router Connects to TOR A in one zBX and TOR B in a 2nd zBX TOR SWITCH #A TOR SWITCH #B Router #A VRRP or [ VRRP HSRP or HTTP1 HSRP ] zBX I Router #B E D TOR SWITCH #A N TOR SWITCH #B HTTP1 zBX35 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerRedundant Fibre Channel Topology for IBM Blades in zBX QLOGIC Switch 1 int. ports ext. ports FC1 : P FC2 : DATA FP LUNs FCn QLOGIC Switch 2 int. ports ext. ports Metro Mirror LVM S : DATA FP LUNs zBX BladeCenter Switches SAN Switches Primary and Blade Expansion Cards  1 2-port FC HBA adapter  2 8 Gb QLOGIC SAN SM per  2 separate SANs Secondary Disk per Blade Chassis  SAN switch Storage Systems  8 Gb QLOGIC  Run in‚ transparent mode connected to zBX  Each with dual storge  Connection to external switch must be NPIV- controllers through up to 6 ports capable switch36 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerzBX Change Scenarios  Configuration Management  Serviceability Management  Upgrade Management – Firmware Update: BladeCenters, Switches (TORs, ESMs), Blades Applying Firmware for zBX Components – CPC Enhanced Driver Maintenance  IBM zBX Change Policy: Minimize disruption, Maximize Concurrency 1. zBX Change Scenarios are concurrent with all CPC operations. 2. zBX Redundant Hardware Components key for zBX concurrency approach. 3. zBX Change Scenario algorithms prioritize concurrency over performance e.g. Updating one member of a pair of switches at a time, but in parallel with others. 4. HMC/SE Automated Controls, including toleration (hardening/retry) support, orchestrate the concurrency operations37 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerConfiguration Scenarios: 1.Ensemble Node components can be added concurrently – Expand the Ensemble Node whenever the business requires it. – Adding zBX to a CPC is concurrent to CPC operations and running workloads – Adding Loose Piece MES to existing zBX (Racks, BladeCenter Chassis, Blades) is concurrent to CPC and existing zBX operations and running workloads – Updating Blade Type High Water Marks (LICCC) Concurrent for increasing values No formal support for decreasing values (RPQ only) Any active blades exceeding new high water mark total must be powered off 2.Ensemble Node components can be removed concurrently – Be sure the component to be removed is not accessing Ensemble resources. – If the workload in the host CPC uses IEDN in another node in the Ensemble, the CPC must be cabled for IEDN access through the IEDN switch in a second zBX.38 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerServiceability Scenarios All but 2 zBX FRU replacements and repair actions are concurrent: For High availability, use clustering and automation to move all work to an alternate * 1. BladeCenter Chassis Mid-plane – Replacement of BladeCenter midplane impacts workloads for all blades in that BladeCenter – All blades in other BladeCenters in zBX are not impacted. 2. Blades – Any blade FRU replacement will impact zBX workload for that blade, but only that blade – FRU replacement containing key persistence data restores that data upon completion Firmware, serial number, any firmware customization data: Networking information / other customization data for DataPower XI50z Virtualization Blades firmware customization data stored on HMC/SE using existing backup/restore infrastructure No additional actions needed to bring zBX workloads back online after repair * Alternatively, planned blade outages can be addressed through the use of static virtual server migration to move virtual servers across blade boundaries This requires the virtual servers to be shut down prior to the move, and rebooted after the move. (IBM will never take a blade offline until work is quiesced.)39 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerUpgrade Scenarios:Applying Firmware for the zBX Components 1. All TOR and BladeCenter Switches firmware updates are concurrent to zBX workloads – Switches updated in parallel, but only one of the redundant pair is updated at a time – Approach allows no impact IEDN or INMN 2. All BladeCenter firmware updates are concurrent to zBX workloads – Primary AMM is updated without impact to blade workloads – Standby AMM is updated in background after Primary AMM update complete40 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerUpgrade Scenarios:Applying Firmware for the zBX Components 3. Impact of blade firmware updates on zBX workloads varies by blade type – Each blade type has at least one firmware component update that disrupts workloads running on the blade. See Appendix – It is possible to know in advance what is disruptive. See Screen shots in Appendix – For non-disruptive updates (the Service Element (SE) determines if the updates are disruptive) If the blade is up, the updates are installed and activated If the blade is down, the updates are queued. When the blade is powered back up, those updates are automatically installed during boot of the hypervisor. – Disruptive updates are deferred to be installed until the service user logs on to the SE and runs the Manage zBX Internal Code Dialog and directs updates to specific blades. Apply non-concurrent blade firmware updates in the least disruptive manner possible. e.g. one at a time, or a subset of all blades at a time, but not all blades at once. Group all non-concurrent blade firmware upgrades within a blade to one blade outage event. Quiesce or move work to another blade41 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerUpgrade Scenarios:Applying CPC Driver Upgrades Enhanced Driver Maintenance (Concurrent Driver upgrade) requires a zBX blade outage*  All CPC firmware upgrades are current  All zBX firmware components change – zBX TOR Switch firmware upgrades are concurrent – BladeCenter firmware upgrade is concurrent – Blade Firmware upgrade is not concurrent and impacts running workloads: (each blade type has at least one non-concurrent firmware component) Apply non-concurrent blade firmware updates in the least disruptive manner possible. e.g. one at a time, or a subset of all blades at a time, but not all blades at once. Group all non-concurrent blade firmware upgrades within a blade to one blade outage event. Quiesce or move work to another blade *Typically CPC and zBX firmware are shipped together in a single CPC driver42 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource ManagerUpgrade Scenarios: zBX Firmware Update Times  All blades are done in parallel, there is little to no time added for multiples  Mixing of blade types results in total time equal to blade type having longest update time  AMM: 20 – 30 min – Primary AMM completed in 20 – 30 min. – Standby AMM done in background taking 20 – 30 min Standby AMM update time doesn’t affect update time total  zBX Switches: 1.5 hours Parallel update to all switches of each redundant pair  zBX Blades: 1 hour 45 min – DataPower: 6 min or 30 min (if licensing file level change) DataPower update times will increase when Platform FW update support added System x Blade: 1 hour Power Blade: 1 hour 45 min43 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource Manager Questions ? No ? Then let‘s start the live demo44 © 2011 IBM Corporation
    • IBM zEnterprise zBX & Unified Resource Manager45 © 2011 IBM Corporation