Front cover -- Contents -- Figures -- Tables -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. Introduction -- 1.1 What is consolidation? -- 1.2 Consolidation methodologies -- 1.2.1 Consolidation by resource concentration -- 1.2.2 pSeries LPAR -- 1.2.3 Consolidation by resource distribution -- 1.3 Consolidation and on demand/utility computing -- 1.3.1 Terminology of on demand -- 1.3.2 Technology of on demand -- Chapter 2. Reasons for consolidation -- 2.1 Why consolidate? -- 2.2 Consolidation benefits -- 2.2.1 Improving service levels -- 2.2.2 Reducing complexity -- 2.2.3 Improving system management -- 2.2.4 Improving data security -- 2.3 The total cost of ownership (TCO) -- 2.3.1 Defining total cost of ownership -- 2.3.2 Total cost of operation (TCOp) -- 2.3.3 Total cost of asset (TCA) -- 2.4 TCO for ERP and CRM solutions -- 2.4.1 TCOnow! components -- 2.4.2 Scope and deliverables -- 2.4.3 Requesting a TCOnow! study -- 2.5 Decision criteria -- 2.5.1 Risks -- 2.6 Disaster recovery -- 2.6.1 Seven tiers model for disaster recovery -- 2.6.2 pSeries/AIX platforms and disaster recovery enablement -- 2.6.3 Enterprise Storage Server (ESS) and disaster recovery -- Chapter 3. Consolidation methodologies -- 3.1 Overview -- 3.2 ALIGN methodology -- 3.3 ALIGN-lite methodology (pSeries Consolidation Approach) -- 3.4 Scorpion -- 3.4.1 Project methodology -- 3.4.2 Scope and steps -- 3.4.3 Data collection -- 3.4.4 Data analysis -- 3.4.5 Outline solution design -- 3.5 Case study -- 3.5.1 Scope -- 3.5.2 Data collection -- 3.5.3 Solution design -- 3.5.4 Conclusion -- Chapter 4. Hardware infrastructure resources -- 4.1 pSeries servers consolidation capabilities -- 4.1.1 pSeries family -- 4.1.2 POWER4 processor -- 4.1.3 POWER3 processor -- 4.1.4 RS64 processor.

4.1.5 pSeries 690 server -- 4.2 Logical partitioning (LPAR) technology overview -- 4.2.1 LPAR objectives -- 4.2.2 LPAR and server consolidation -- 4.2.3 System requirements for LPAR implementation -- 4.2.4 LPAR planning -- 4.2.5 Dynamic LPAR (DLPAR) -- 4.2.6 LPAR/DLPAR security considerations -- 4.2.7 Reliability, Availability, and Serviceability and LPAR -- 4.2.8 LPAR profiles and resource selection -- 4.3 Storage -- 4.3.1 Direct attached storage (DAS) -- 4.3.2 Network Attached Storage (NAS) -- 4.3.3 Storage Area Network (SAN) -- 4.3.4 IBM storage product offerings -- Chapter 5. Software environment resources -- 5.1 Base software -- 5.1.1 Reliable Scalable Cluster Technology (RSCT) -- 5.1.2 Resource Monitoring Control (RMC) -- 5.1.3 Workload Manager (WLM) -- 5.1.4 Additional AIX features for consolidation -- 5.2 Cluster software -- 5.2.1 Parallel System Support Program (PSSP) -- 5.2.2 Cluster System Management (CSM) -- 5.2.3 Transition from PSSP to CSM -- 5.2.4 High Availability Cluster Multi-Processing (HACMP) -- 5.2.5 General Parallel File System (GPFS) -- 5.2.6 Storage management -- Chapter 6. IBM messaging consolidation -- 6.1 Considerations for this consolidation -- 6.2 Phases and outcome -- 6.2.1 Phase 1 (pilot) -- 6.2.2 Phase 2 -- 6.2.3 Phase 3 -- 6.2.4 Phase 4 -- Chapter 7. SAP R3 server consolidation scenario -- 7.1 Consolidation decision driving factors -- 7.1.1 Initial configuration -- 7.1.2 Components overview -- 7.1.3 Assumptions for this project -- 7.2 Phase 1: Implementation of SAP on a pSeries p690 -- 7.2.1 Data migration -- 7.2.2 Benefits/value for the customer -- 7.3 Phase 2: S80 server migration -- 7.4 Conclusions -- Abbreviations and acronyms -- Related publications -- IBM Redbooks -- Other publications -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.