DOCSLIB.ORG

Inside the RS/6000 SP

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Inside the RS/6000 SP Inside the RS/6000 SP Marcelo R. Barrios, Mohammad Arif Kalem, Yoshimichi Kosuge, Philippe Lamarche Belinda Schmolke, George Sohos, Juan Jose Vasquez, Tim Wherle International Technical Support Organization http://www.redbooks.ibm.com SG24-5145-00 SG24-5145-00 International Technical Support Organization Inside the RS/6000 SP July 1998 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix A, “Special Notices” on page 379. First Edition (July 1998) This edition applies to Version 2 Release 4 of IBM Parallel System Support Programs for AIX (5765-529) for use with the AIX Version 4 Operating System. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. HYJ Mail Station P099 522 South Road Poughkeepsie, New York 12601-5400 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1998. All rights reserved Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures. .xi Tables. xvii Preface. .xix The Team That Wrote This Redbook . xix Comments Welcome . xxi Part 1. The Big Picture . 1 Chapter 1. History and Design Philosophy. 3 1.1 Ultra-Large Computing Problems . 3 1.2 Origins of the SP . 4 1.3 High-Level System Characteristics . 6 1.3.1 Scalability. 6 1.3.2 Use of Mainstream Architectures and Technologies . 7 1.3.3 Flexibility . 8 1.3.4 Manageability . 8 Chapter 2. System Architectures . 9 2.1 Way of Categorizing Computers . 9 2.2 Single Instruction, Single Data Uniprocessor . 10 2.2.1 Everyday Examples . 12 2.2.2 Limitations of SISD Architecture . 12 2.3 Parallelism . 13 2.4 Single Instruction, Multiple Data (SIMD) Machines . 14 2.4.1 Everyday Examples of SIMD Machines . 14 2.4.2 Limitations of the SIMD Architecture. 14 2.5 Multiple Instruction, Single Data Machines . 15 2.6 Multiple Instruction, Multiple Data Machines. 15 2.6.1 Shared Memory MIMD Machines . 15 2.6.2 Shared Nothing MIMD Machines . 18 Part 2. System Implementation . 23 Chapter 3. Hardware Components . 25 3.1 Frames. 25 3.1.1 Power Supplies . 26 3.1.2 Hardware Control and Supervision . 27 3.2 Nodes . 27 3.2.1 Internal Nodes . 27 © Copyright IBM Corp. 1998 iii 3.2.2 Extension Nodes . 33 3.3 Control Workstation . 35 3.3.1 High Availability Control Workstation . 36 3.3.2 Supported Control Workstations . 36 3.4 High-Performance Communication Network . 38 3.4.1 Hardware Concepts . 38 3.4.2 SP Switch Network . 42 3.4.3 SP Switch Products . 45 3.5 Peripheral Devices . 47 3.6 Configuration Rules . 48 3.6.1 Hardware Components . 48 3.6.2 Basic Configuration Rules . 49 3.6.3 Short Frame Configurations . 50 3.6.4 Tall Frame Configurations . 53 3.6.5 Numbering Rules . 73 Chapter 4. Software Components . 81 4.1 System Data Repository (SDR) . 82 4.1.1 Introduction . 82 4.1.2 SDR Data Model. 82 4.1.3 User Interface to SDR . 84 4.1.4 SDR Daemons . 84 4.1.5 Client/Server Communication . 85 4.1.6 Locking. 86 4.1.7 Manipulating SDR Data . 87 4.1.8 Useful SDR Commands . 88 4.1.9 The SDR Log File . 89 4.1.10 Backup and Restore of SDR . 89 4.2 The Hardware Control Subsystem . 89 4.2.1 What Can Be Monitored and Controlled? . 89 4.2.2 How It Works . 90 4.2.3 User Interfaces . 92 4.3 Overview of Switch Software . 93 4.3.1 Introduction to the Switch . 93 4.3.2 Switch Operating Principles . 94 4.3.3 Primary Node Behavior. 95 4.3.4 Secondary Nodes Behavior . 96 4.3.5 Switch Topology File . 96 4.3.6 Routing in SP Switch . 101 4.3.7 Switch Initialization . 104 4.3.8 Switch Clocks . 105 4.3.9 Switch Log Files . 105 4.3.10 The out.top File . 106 iv Inside the RS/6000 SP 4.3.11 Managing the Switch . 107 4.4 Time Service . 110 4.4.1 Why Network Time Protocol? . 110 4.4.2 NTP Architecture . 110 4.4.3 NTP Modes . 111 4.5 High Availability Infrastructure (HAI). 112 4.5.1 "In the Beginning ...". 113 4.5.2 HAI Packaging . 114 4.5.3 HAI Architecture Overview - "The Picture" . 114 4.5.4 Topology Services . 115 4.5.5 Group Services. 120 4.5.6 Event Management. 127 4.5.7 Putting It All Together - A Simple Example of Exploiting HAI . 136 4.6 SP Security . 141 4.6.1 General Security Concepts . 141 4.6.2 AIX Security . ..
Load more

Recommended publications
  • Fencing Cyberspace: Drawing Borders in a Virtual World Maureen A
    University of Minnesota Law School Scholarship Repository Minnesota Law Review 1998 Fencing Cyberspace: Drawing Borders in a Virtual World Maureen A. O'Rourke Follow this and additional works at: https://scholarship.law.umn.edu/mlr Part of the Law Commons Recommended Citation O'Rourke, Maureen A., "Fencing Cyberspace: Drawing Borders in a Virtual World" (1998). Minnesota Law Review. 1923. https://scholarship.law.umn.edu/mlr/1923 This Article is brought to you for free and open access by the University of Minnesota Law School. It has been accepted for inclusion in Minnesota Law Review collection by an authorized administrator of the Scholarship Repository. For more information, please contact [email protected]. Fencing Cyberspace: Drawing Borders in a Virtual World Maureen A. O'Rourke* Introduction ............................................................................... 610 I. An Introduction to the Internet and the World W ide W eb .................................................................. 615 A. Origins of the Internet ................................................... 615 B. Development of the World Wide Web ........................... 619 C. Emergence of the Internet as a Commercial Marketplace ............................................... 624 1. Development of the Marketplace .............................. 624 2. Web Business Models ................................................ 625 a. Advertising-Based Models ................................... 626 b. Subscription-Based Models .................................
    [Show full text]
  • Survey of Methodologies, Approaches, and Challenges in Parallel Programming Using High-Performance Computing Systems
    Hindawi Scientific Programming Volume 2020, Article ID 4176794, 19 pages https://doi.org/10.1155/2020/4176794 Review Article Survey of Methodologies, Approaches, and Challenges in Parallel Programming Using High-Performance Computing Systems Paweł Czarnul ,1 Jerzy Proficz,2 and Krzysztof Drypczewski 2 1Dept. of Computer Architecture, Faculty of Electronics, Telecommunications and Informatics, Gdansk University of Technology, Gda´nsk, Poland 2Centre of Informatics–Tricity Academic Supercomputer & Network (CI TASK), Gdansk University of Technology, Gdan´sk, Poland Correspondence should be addressed to Paweł Czarnul; [email protected] Received 11 October 2019; Accepted 30 December 2019; Published 29 January 2020 Guest Editor: Pedro Valero-Lara Copyright © 2020 Paweł Czarnul et al. ,is is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. ,is paper provides a review of contemporary methodologies and APIs for parallel programming, with representative tech- nologies selected in terms of target system type (shared memory, distributed, and hybrid), communication patterns (one-sided and two-sided), and programming abstraction level. We analyze representatives in terms of many aspects including programming model, languages, supported platforms, license, optimization goals, ease of programming, debugging, deployment, portability, level of parallelism, constructs enabling parallelism and synchronization, features introduced in recent versions indicating trends, support for hybridity in parallel execution, and disadvantages. Such detailed analysis has led us to the identification of trends in high-performance computing and of the challenges to be addressed in the near future. It can help to shape future versions of programming standards, select technologies best matching programmers’ needs, and avoid potential difficulties while using high- performance computing systems.
    [Show full text]
  • SAP Solutions on Vmware Vsphere Guidelines Summary and Best Practices
    SAP On VMware Best Practices Version 1.1 December 2015 © 2015 VMware, Inc. All rights reserved. Page 1 of 61 SAP on VMware Best Practices © 2015 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. This product is covered by one or more patents listed at http://www.vmware.com/download/patents.html. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave Palo Alto, CA 94304 www.vmware.com © 2015 VMware, Inc. All rights reserved. Page 2 of 61 SAP on VMware Best Practices Contents 1. Overview .......................................................................................... 5 2. Introduction ...................................................................................... 6 2.1 Support ........................................................................................................................... 6 2.2 SAP ................................................................................................................................ 6 2.3 vCloud Suite ................................................................................................................... 9 2.4 Deploying SAP with vCloud Suite ................................................................................ 11 3. Virtualization Overview ..................................................................
    [Show full text]
  • Programming Languages, Database Language SQL, Graphics, GOSIP
    b fl ^ b 2 5 I AH1Q3 NISTIR 4951 (Supersedes NISTIR 4871) VALIDATED PRODUCTS LIST 1992 No. 4 PROGRAMMING LANGUAGES DATABASE LANGUAGE SQL GRAPHICS Judy B. Kailey GOSIP Editor POSIX COMPUTER SECURITY U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 100 . U56 4951 1992 NIST (Supersedes NISTIR 4871) VALIDATED PRODUCTS LIST 1992 No. 4 PROGRAMMING LANGUAGES DATABASE LANGUAGE SQL GRAPHICS Judy B. Kailey GOSIP Editor POSIX COMPUTER SECURITY U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 October 1992 (Supersedes July 1992 issue) U.S. DEPARTMENT OF COMMERCE Barbara Hackman Franklin, Secretary TECHNOLOGY ADMINISTRATION Robert M. White, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director - ;,’; '^'i -; _ ^ '’>.£. ; '':k ' ' • ; <tr-f'' "i>: •v'k' I m''M - i*i^ a,)»# ' :,• 4 ie®®;'’’,' ;SJ' v: . I 'i^’i i 'OS -.! FOREWORD The Validated Products List is a collection of registers describing implementations of Federal Information Processing Standards (FTPS) that have been validated for conformance to FTPS. The Validated Products List also contains information about the organizations, test methods and procedures that support the validation programs for the FTPS identified in this document. The Validated Products List is updated quarterly. iii ' ;r,<R^v a;-' i-'r^ . /' ^'^uffoo'*^ ''vCJIt<*bjteV sdT : Jr /' i^iL'.JO 'j,-/5l ':. ;urj ->i: • ' *?> ^r:nT^^'Ad JlSid Uawfoof^ fa«Di)itbiI»V ,, ‘ isbt^u ri il .r^^iytsrH n 'V TABLE OF CONTENTS 1.
    [Show full text]
  • Oracle Solaris and Oracle SPARC Systems—Integrated and Optimized for Mission Critical Computing
    An Oracle White Paper September 2010 Oracle Solaris and Oracle SPARC Servers— Integrated and Optimized for Mission Critical Computing Oracle Solaris and Oracle SPARC Systems—Integrated and Optimized for Mission Critical Computing Executive Overview ............................................................................. 1 Introduction—Oracle Datacenter Integration ....................................... 1 Overview ............................................................................................. 3 The Oracle Solaris Ecosystem ........................................................ 3 SPARC Processors ......................................................................... 4 Architected for Reliability ..................................................................... 7 Oracle Solaris Predictive Self Healing ............................................ 7 Highly Reliable Memory Subsystems .............................................. 9 Oracle Solaris ZFS for Reliable Data ............................................ 10 Reliable Networking ...................................................................... 10 Oracle Solaris Cluster ................................................................... 11 Scalable Performance ....................................................................... 14 World Record Performance ........................................................... 16 Sun FlashFire Storage .................................................................. 19 Network Performance ..................................................................
    [Show full text]
  • Cluster Suite Overview
    Red Hat Enterprise Linux 4 Cluster Suite Overview Red Hat Cluster Suite for Red Hat Enterprise Linux Edition 1.0 Last Updated: 2020-03-08 Red Hat Enterprise Linux 4 Cluster Suite Overview Red Hat Cluster Suite for Red Hat Enterprise Linux Edition 1.0 Landmann [email protected] Legal Notice Copyright © 2009 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Arxiv:1312.1411V2 [Cs.LO] 9 Jun 2014 Ocretporm R Adt Einadipeet Seilyw Especially Implement, Buffering and Implement Design Multiprocessors to Tectures
    Don’t sit on the fence A static analysis approach to automatic fence insertion Jade Alglave1, Daniel Kroening2, Vincent Nimal2, and Daniel Poetzl2 1 University College London, UK 2University of Oxford, UK Abstract Modern architectures rely on memory fences to prevent undesired weakenings of memory consistency. As the fences’ semantics may be subtle, the automation of their placement is highly desirable. But precise methods for restoring consistency do not scale to deployed systems code. We choose to trade some precision for genuine scalability: our technique is suitable for large code bases. We implement it in our new musketeer tool, and detail experiments on more than 350 executables of packages found in Debian Linux 7.1, e.g. memcached (about 10000 LoC). 1 Introduction Concurrent programs are hard to design and implement, especially when running on multiprocessor archi- tectures. Multiprocessors implement weak memory models, which feature e.g. instruction reordering, store buffering (both appearing on x86), or store atomicity relaxation (a particularity of Power and ARM). Hence, multiprocessors allow more behaviours than Lamport’s Sequential Consistency (SC) [Lam79], a theoretical model where the execution of a program corresponds to an interleaving of the different threads. This has a dramatic effect on programmers, most of whom learned to program with SC. Fortunately, architectures provide special fence (or barrier) instructions to prevent certain behaviours. Yet both the questions of where and how to insert fences are contentious, as fences are architecture-specific and expensive. Attempts at automatically placing fences include Visual Studio 2013, which offers an option to guarantee acquire/release semantics (we study the performance impact of this policy in Sec.
    [Show full text]
  • Installation: Getting Started
    Tivoli® IBM Tivoli NetView for z/OS Version 5 Release 4 Installation: Getting Started SC31-8872-06 Tivoli® IBM Tivoli NetView for z/OS Version 5 Release 4 Installation: Getting Started SC31-8872-06 Note Before using this information and the product it supports, read the information in “Notices” on page 145. This edition applies to version 5, release 4 of IBM Tivoli NetView for z/OS (product number 5697-ENV) and to all subsequent versions, releases, and modifications until otherwise indicated in new editions. This edition replaces SC31-8872-05. © Copyright International Business Machines Corporation 2001, 2009. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ...................................vii About this publication .............................ix Intended audience .................................ix Publications ...................................ix IBM Tivoli NetView for z/OS library ..........................ix Related publications ...............................xi Accessing terminology online ............................xi Using NetView for z/OS online help ..........................xii Using LookAt to look up message explanations ......................xii Accessing publications online ............................xii Ordering publications...............................xiii Accessibility ...................................xiii Tivoli technical training ...............................xiii Downloads ...................................xiii
    [Show full text]
  • High Performance Virtual Machine Recovery in the Cloud
    High Performance Virtual Machine Recovery in the Cloud Valentina Salapura1 and Richard Harper2 1IBM T. J. Watson Research Center, 1101 Kitchawan Rd, NY, Yorktown Heights, U.S.A. 2IBM T. J. Watson Research Center, Research Triangle Park, NC, U.S.A. Keywords: Cloud Computing, High Availability, Virtualization, Automation, Enterprise Class. Abstract: In this paper, we outline and illustrate concepts that are essential to achieve fast, highly scalable virtual machine planning and failover at the Virtual Machine (VM) level in a data center containing a large number of servers, VMs, and disks. To illustrate the concepts a solution is implemented and analyzed for IBM’s Cloud Managed Services enterprise cloud. The solution enables at-failover-time planning, and keeps the recovery time within tight service level agreement (SLA) allowed time budgets via parallelization of recovery activities. The initial serial failover time was reduced for an order of magnitude due to parallel VM restart, and to parallel VM restart combined with parallel storage device remapping. 1 INTRODUCTION originally designed for smaller managed environments, and do not scale well as the system Cloud computing is being rapidly adopted across the size and complexity increases. Detecting failures, IT industry as a platform for increasingly more determining appropriate failover targets, re-mapping demanding workloads, both traditional and a new storage to those failover targets, and restarting the generation of mobile, social and analytics virtual workload have to be carefully designed and applications. In the cloud, customers are being led parallelized in order to meet the service level to expect levels of availability that until recently agreement (SLA) for large systems.
    [Show full text]
  • Comparing and Improving Centralized and Distributed Techniques for Coordinating Massively Parallel Shared-Memory Systems
    Comparing and Improving Centralized and Distributed Techniques for Coordinating Massively Parallel Shared-Memory Systems by Eric Freudenthal A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy Department of Computer Science New York University May 2003 Approved: Research Advisor: Allan Gottlieb c Eric Freudenthal All Rights Reserved 2003 In memory of my father, Dr. Peter Charles Freudenthal, Ph.D., NYU 1970. iii Acknowledgment I was fortunate to work with the many exceptionally talented people who partic- ipated in the NYU Ultracomputer research project lead by Allan Gottlieb and Malvin Kalos. My collaboration with Jan Edler designing coordination algo- rithms for Symunix and its runtime libraries greatly influenced my early work on algorithms described in this dissertation. I benefited much from Allan Gottlieb’s generous commitment to refining my ideas and writing style. In particular, his insistence on precise language and reasoning nurtured the maturation of both my analytical and communication skills. The contributions of three other faculty to my dissertation research are also deserving of recognition: Alan Siegel encouraged me to identify and narrow my research focus to a small set of interesting phenomena. Vijay Karamcheti and Benjamin Goldberg generously read drafts of this dissertation and assisted me in developing a clear overall narrative. Finally, this project would never have been completed without the continuous support and encouragement I received from my family and friends. iv Abstract Two complementary approaches have been proposed to achieve high per- formance inter-process coordination on highly parallel shared-memory systems. Gottlieb et. al. introduced the technique of combining concurrent memory refer- ences, thereby reducing hot spot contention and enabling the “bottleneck-free” execution of algorithms referencing a small number of shared variables.
    [Show full text]
  • Scale-Out Deployments of SAP HANA on Vsphere
    Best Practices and Recommendations for Scale-Out Deployments of SAP HANA on VMware vSphere August 2015 DEPLOYMENT AND TECHNICAL CONSIDERATIONS GUIDE Best Practices and Recommendations for Scale-Out Deployments of SAP HANA on VMware vSphere Table of Content Introduction. 4 Audience . 4 Production Support . 5 SAP HANA System Types . 6 Overview . 6 SAP HANA Scale-Up Option. 8 SAP HANA Scale-Out Option . 9 SAP HANA Appliance Model . 11 SAP HANA Tailored Datacenter Integration . 11 Co-Deployment of Mixed Workloads in VMware vSphere Virtualized SAP HANA Scale-Out TDI Multi-VM Environments .. 12 SAP HANA Tailored Datacenter Integration Support Process . 15 Benefits of Leveraging the TDI Deployment Option for SAP HANA Scale-Out Configurations with VMware vSphere . 16 Virtualized SAP HANA Scale-Out TDI Reference Architecture . 17 General Concepts and Overview . 17 SAP Scale-Out on vSphere Storage Considerations. 19 NAS Over NFS Storage Option . 22 Fibre Channel-based SAN Storage Option . 22 SAP Scale-Out on vSphere Network Considerations . 25 SAP HANA Scale-Out on vSphere High Availability . 29 SAP HANA Data Persistence. 30 VMware HA-protected SAP HANA Systems . 31 SAP HANA Auto-Restart Feature with VMware HA . 33 SAP HANA Systems Protected with Host Auto-Failover to a Standby VM . 34 Host Auto-Failover. 34 SAP HANA Disaster Recovery Solutions with VMware vSphere . 37 Summary SAP HANA HA and Disaster Recovery Solutions with VMware vSphere . 39 VMware vSphere Site Recovery Manager . 40 DEPLOYMENT AND TECHNICAL CONSIDERATIONS GUIDE / 2 Best Practices and Recommendations for Scale-Out Deployments of SAP HANA on VMware vSphere Virtualized SAP HANA Business Warehouse Scale-Out Sizing .
    [Show full text]
  • Manage Your Software Budget with IBM Software Subscription for AIX
    Software Announcement September 13, 1999 Manage Your Software Budget with IBM Software Subscription for AIX Overview Highlights Include At a Glance • Software Subscription for AIX Agreement with no signature enables a single-site or worldwide required The Software Subscription for AIX enterprise customer to maintain • No minimum contract value includes: software version and release • currency. The offering, which • One-year contract Either one agreement for the includes base license, users, and entire enterprise under one • Automatic notification of program additional license upgrades, is a customer number or an upgrades one-year term agreement that helps agreement at the machine level you better manage your software • Automatic renewal and invoicing • Predictable budgeting for migration strategy at a known cost. upgrade maintenance • Ability to order multiple media You are billed annually with supply types with quantities on • Annual billing with automatic automatic renewal unless IBM is the same order renewal notified in writing. • Guidelines for IBM development For ordering, contact: With this subscription you can easily laboratories that release products Your IBM representative, an IBM acquire and manage selected AIX under this program Business Partner, or IBM Americas software upgrades and better Call Centers at • Clarification of area and customer manage your software budget. 800-IBM-CALL Reference: RE001 responsibilities Software Subscription for AIX EXTRA! EXTRA! . replaces the IBM Software Upgrade Key Prerequisites Protection Plan for AIX and UNIX Subscribe to IBM iSource, your electronic Original licensed program eligible for source for customized IBM information! Operating System Based Software Go to our Web site at (5692-ADV) for new and expired upgrade protection http://www.ibm.com/isource contracts.
    [Show full text]