Server Time Protocol Planning Guide
Front coverServer Time ProtocolPlanning GuideConcepts and terminologyConfiguration planningOperations and recoveryplanningOctavian LascuHans-Peter EckamGeorge KozakosPaulo Vitor Pereiraibm.com/redbooks
International Technical Support OrganizationServer Time Protocol Planning GuideJune 2013SG24-7280-03
Note: Before using this information and the product it supports, read the information in “Notices” onpage vii.Fourth Edition (June 2013)This edition applies to Server Time Protocol Facility on IBM System z10 Enterprise Class (z10 EC), Systemz10 Business Class (z10 BC), System z9 Enterprise Class (z9 EC), System z9 Business Class (z9 BC), andzSeries z990 and z890 servers. Copyright International Business Machines Corporation 2006, 2013. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.
ContentsNotices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixAuthors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixNow you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiStay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiSummary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiJune 2013, Fourth Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiChapter 1. Introduction to Server Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Introduction to time synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.1 Time-of-Day clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1.2 Time synchronization in a Parallel Sysplex. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1.3 Overview of External Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Overview of Server Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 STP concepts and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.1 STP facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.2 TOD clock synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.3 STP servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3.4 Coordinated Timing Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.5 STP stratum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.6 Server roles in an STP-only CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4 Timing network types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4.1 Mixed CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4.2 STP-only CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.5 Coupling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.5.1 Link redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.5.2 Coupling link requirements in a non-sysplex configuration . . . . . . . . . . . . . . . . . . 231.6 External time source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.7 Summary of STP terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Chapter 2. Planning hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1 Planning hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1.1 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1.2 Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1.3 Support Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1.4 EC levels and MCLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1.5 Installing the STP feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1.6 z/BX considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2 Planning connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2.1 Planning for coupling links for STP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2.2 Planning for timing-only links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2.3 Considerations for multi-site sysplex. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3 External time source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3.1 Dial-out on the Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . .2.3.2 NTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copyright IBM Corp. 2006, 2013. All rights reserved.313232333637373838384446464748iii
2.3.3 NTP server with pulse per second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.4 Internal Battery Feature (IBF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.5 Planning z/OS software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.5.1 z/OS requirements for STP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.5.2 CLOCKxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.6 Planning for z/VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.6.1 STP state flow in z/VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.6.2 Updated CP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.6.3 z/VM IOCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.6.4 VM guests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.6.5 z/TPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.7 Special considerations for a single server STP-only CTN. . . . . . . . . . . . . . . . . . . . . . .2.7.1 Software planning: z/OS currently running in a sysplex . . . . . . . . . . . . . . . . . . . .2.7.2 Software planning: z/OS systems currently not in a sysplex. . . . . . . . . . . . . . . . .2.7.3 Software planning: z/OS systems currently in a sysplex using ETR. . . . . . . . . . .2.8 Planning for zBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.9 Operating systems with no STP support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.9.1 Linux for System z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.9.2 z/VSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54575757596768696969707072737474757575Chapter 3. Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.1 Displaying and monitoring the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.1.1 CPC Detail panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.1.2 System (Sysplex) Time panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.1.3 z/OS display commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.1.4 z/OS messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.2 Configuring the Coordinated Timing Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.2.1 Configuring a Mixed CTN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.2.2 Configuring an STP-only CTN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.3 Managing the time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.3.1 STP time adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.3.2 STP offset adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083.3.3 Changes in local time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153.3.4 Logical partition time offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183.3.5 Parallel Sysplex and multiple time zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203.4 Managing the CTN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253.4.1 Changing the CTN ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253.4.2 Single-server or dual-server auto resume after power-on reset. . . . . . . . . . . . . 1253.4.3 Changing the Current Time Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273.4.4 Changing the server roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1293.4.5 Deconfiguring a CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333.5 Operational considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343.5.1 Migrating timing-only links to coupling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343.5.2 Coupling link path validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353.5.3 Last timing link validation and operational safeguards . . . . . . . . . . . . . . . . . . . . 1363.5.4 Last timing link condition examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373.5.5 Disruptive actions on the Current Time Server . . . . . . . . . . . . . . . . . . . . . . . . . . 1433.5.6 Disruptive actions on the BTS or Arbiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453.5.7 Restarting a CTN power outage or power-on reset (unplanned) . . . . . . . . . . . . 1453.5.8 Planned single-site maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1483.6 MES upgrade considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1483.6.1 Mixed CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1493.6.2 STP-only CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149ivServer Time Protocol Planning Guide
Chapter 4. Recovery concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.1 Terminology overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2 Freewheel interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.3 Server offline signal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.4 Going Away Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.5 Arbiter-assisted recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.6 Console-assisted recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.6.1 Console-assisted recovery in a CTN with BTS . . . . . . . . . . . . . . . . . . . . . . . . . .4.6.2 Console-assisted recovery in a CTN with BTS and Arbiter. . . . . . . . . . . . . . . . .4.7 Island condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.8 Switch to local timing mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.9 External Time Source (ETS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153154154155155156158158158159159160Appendix A. Migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preparation and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .z/OS preparation and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Server roles in an STP-only CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Plan for high availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration between an ETR network and a Mixed CTN . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration from an ETR network to a Mixed CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration from a Mixed CTN to an ETR network . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration between a Mixed CTN and an STP-only CTN. . . . . . . . . . . . . . . . . . . . . . . . . .Migration from a Mixed CTN to an STP-only CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration from an STP-only CTN to a Mixed CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . .Migration from an ETR network to an STP-only CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . .Installation of a new STP-only CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Installation of a single-server STP-only CTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Enhancing a single-site ETR network to a Mixed CTN across two sites . . . . . . . . . . . . . 90191192193194Appendix B. Server Time Protocol (STP) messages in z/OS . . . . . . . . . . . . . . . . . . .Supervisor messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .XCF messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .XES messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Automating-related messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199200201201201Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to get Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203203203204205205Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Contentsv
viServer Time Protocol Planning Guide
NoticesThis information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBM product,program, or service may be used. Any functionally equivalent product, program, or service that does notinfringe any IBM intellectual property right may be used instead. However, it is the user's responsibility toevaluate and verify the operation of any non-IBM product, program, or service.IBM may have patents or pending patent applications covering subject matter described in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, inwriting, to:IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement may not apply to you.This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout notice.Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.IBM may use or distribute any of the information you supply in any way it believes appropriate without incurringany obligation to you.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm theaccuracy of performance, compatibility or any other claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to the suppliers of those products.This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which the sampleprograms are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,cannot guarantee or imply reliability, serviceability, or function of these programs. Copyright IBM Corp. 2006, 2013. All rights reserved.vii
TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business MachinesCorporation in the United States, other countries, or both. These and other IBM trademarked terms aremarked on their first occurrence in this information with the appropriate symbol ( or ), indicating USregistered or common law trademarks owned by IBM at the time this information was published. Suchtrademarks may also be registered or common law trademarks in other countries. A current list of IBMtrademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtmlThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:BladeCenter CICSPlex CICS DataPower ESCON FICON GDPS Geographically Dispersed ParallelSysplex Global Technology Services IBM MVS Parallel Sysplex POWER7 PowerVM PR/SM Processor Resource/SystemsManager Redbooks Redpapers Redbooks (logo) Resource Link RMF S/390 Sysplex Timer System Storage System x System z10 System z9 System z z/Architecture z/OS z/VM z/VSE z10 z9 zEnterprise zSeries The following terms are trademarks of other companies:Linux is a trademark of Linus Torvalds in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Other company, product, or service names may be trademarks or service marks of others.viiiServer Time Protocol Planning Guide
PrefaceServer Time Protocol (STP) is a server-wide facility that is implemented in the LicensedInternal Code (LIC) of the IBM zEnterprise EC12 (zEC12), IBM zEnterprise 196 (z196),IBM zEnterprise 114 (z114), IBM System z10 Enterprise Class (z10 EC), System z10Business Class (z10 BC), IBM System z9 Enterprise Class (z9 EC), and System z9Business Class (z9 BC). It provides improved time synchronization in a sysplex ornon-sysplex configuration.This IBM Redbooks publication is intended for infrastructure architects and systemprogrammers who need to understand the IBM STP functions. Readers are expected to begenerally familiar with System z technology and terminology.This book provides planning information for Server Time Protocol functions and associatedsoftware support. For more detailed installation, operation, and recovery information, refer tothe companion books Server Time Protocol Implementation Guide, SG24-7281, and ServerTime Protocol Recovery Guide, SG24-7380.AuthorsThis book was produced by a team of specialists from around the world working at theInternational Technical Support Organization, Poughkeepsie Center.Octavian Lascu is a Project Leader at the International Technical Support Organization,Poughkeepsie Center. He writes extensively and teaches IBM classes worldwide on areassuch as cross-paltform clustering and High Performance Computing. Before joining the ITSO10 years ago, Octavian worked in Global Technology Services , Romania, as Senior ITConsultant.Hans-Peter Eckam is a Support Center Specialist in the IBM Hardware Support Center inMainz, Germany. Hans-Peter joined IBM in 1986 and has 22 years of experience insupporting System z customers. His areas of expertise include System z, Sysplex Timer ,Server Time Protocol, and connectivity such as ESCON , FICON , and InfiniBand.George Kozakos is a Senior IT Specialist with IBM Australia. He has more than 25 years ofexperience in MVS system programming. George’s areas of expertise include Server TimeProtocol and GDPS . He holds degrees in Computing Science and Pure Mathematics.Paulo Vitor Pereira is an IT Specialist in STG Lab Services in São Paulo, Brazil. He hasjoined IBM in 2009 and has 6 years of experience in System z. His areas of expertise include,z/OS , WLM, z/BX and System z Hardware.Thanks to the following people for their contributions to this project:William G WhiteInternational Technical Support Organization, Poughkeepsie CenterDonald J Smith, Richard M Hamilton, Steve Cherniak, Glen PoulsenIBM PoughkeepsieGregory K. HutchisonIBM Gaithersburg Copyright IBM Corp. 2006, 2013. All rights reserved.ix
Thanks to the authors of the previous editions of this book: Authors of third edition of Server Time Protocol Planning Guide, published in September2010 were:Noshir Dhondy, Hans-Peter Eckam, Andy Kilhoffer, Jeremy Koch, Hao Shen, Martin Söllig,Ray Takabe, Octavian Lascu. Authors of the second edition, Server Time Protocol Planning Guide, published in June2009, were:Noshir Dhondy, Hans-Peter Eckam, Marcel Jaeckel, Jeff McDonough, George Ng, FrankPackheiser, and Bernard Tanguy Authors of the first edition of Server Time Protocol Planning Guide, published inDecember 2006 and Server Time Protocol NTP Client Support, published in September2007, were:Noshir Dhondy, Greg Hutchison, Paul Hagen, Dick Jorna, George Kozakos, and IainNeville.Thanks to the ITSO support team:Robert Haimowiz, Donald R Brennan and Roy P CostaInternational Technical Support Organization, Poughkeepsie CenterNow you can become a published author, too!Here's an opportunity to spotlight your skills, grow your career, and become a publishedauthor - all at the same time! Join an ITSO residency project and help write a book in yourarea of expertise, while honing your experience using leading-edge technologies. Your effortswill help to increase product acceptance and customer satisfaction, as you expand yournetwork of technical contacts and relationships. Residencies run from two to six weeks inlength, and you can participate either in person or as a remote resident working from yourhome base.Find out more about the residency program, browse the residency index, and apply online at:ibm.com/redbooks/residencies.htmlxServer Time Protocol Planning Guide
Comments welcomeYour comments are important to us!We want our books to be as helpful as possible. Send us your comments about this book orother IBM Redbooks publications in one of the following ways: Use the online Contact us review Redbooks form found at:ibm.com/redbooks Send your comments in an e-mail to:redbooks@us.ibm.com Mail your comments to:IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South RoadPoughkeepsie, NY 12601-5400Stay connected to IBM Redbooks Find us on s/178023492563?ref ts Follow us on twitter:http://twitter.com/ibmredbooks Look for us on LinkedIn:http://www.linkedin.com/groups?home &gid 2130806 Explore new Redbooks publications, residencies, and workshops with the IBM Redbooksweekly sf/subscribe?OpenForm Stay current on recent Redbooks publications with RSS i
xiiServer Time Protocol Planning Guide
Summary of changesThis section describes the technical changes made in this edition of the book. This editionmay also include minor corrections and editorial changes that are not identified.Summary of Changesfor SG24-7280-03for Server Time Protocol Planning Guideas created or updated on April 11, 2016.June 2013, Fourth EditionThis revision reflects the addition, deletion, or modification of new and changed informationdescribed below.New information STP Version 4 support updatesInformation update includes IBM zEnterprise Servers (zEC12, z196, and z114).Dual-server auto resume after power-on reset.External Time Source: Hardware Management Console acting as NTP server.Removal of HMC dial out support Copyright IBM Corp. 2006, 2013. All rights reserved.xiii
xivServer Time Protocol Planning Guide
1Chapter 1.Introduction to Server TimeProtocolThis chapter discusses time synchronization and introduces the Server Time Protocol (STP)facility. The following topics are covered: Introduction to time synchronizationOverview of Server Time ProtocolSTP concepts and terminologyTiming network typesCoupling linksExternal time sourceSummary of STP terminology Copyright IBM Corp. 2006, 2013. All rights reserved.1
1.1 Introduction to time synchronizationHistorically, the most important requirement for highly accurate time is for na
Server Time Protocol Planning Guide Octavian Lascu Hans-Peter Eckam George Kozakos Paulo Vitor Pereira Concepts and terminology Configuration planning Operations and recovery . 3.4.2 Single-server or dual-server auto resume
When provisioning a Windows Server for a specific role there are additional items to consider for further securing the server. When planning and provisioning your server layout, designate one primary purpose per server. Whenever possible, designate one server as the database server, one server as the web server, and one server as the file server.
Server 2005 , SQL Server 2008 , SQL Server 2008 R2 , SQL Server 2012 , SQL Server 2014 , SQL Server 2005 Express Edition , SQL Server 2008 Express SQL Server 2008 R2 Express , SQL Server 2012 Express , SQL Server 2014 Express .NET Framework 4.0, .NET Framework 2.0,
Introduction 1-2 Oracle Forms Server and Reports Server Installation Guide Introduction Oracle Forms Server and Reports Server is an integrated set of database tools i Oracle Forms i. Oracle Forms Server Server and Reports Server Server. UNIX. Installation Guide Compaq Tru64 .
EGP Exterior Gateway Protocol OSPF Open Shortest Path First Protocol IE-IRGP Enhanced Interior Gateway Routing Protocol VRRP Virtual Router Redundancy Protocol PIM-DM Protocol Independent Multicast-Dense Mode PIM-SM Protocol Independent Multicast-Sparse Mode IGRP Interior Gateway Routing Protocol RIPng for IPv6 IPv6 Routing Information Protocol PGM
Administrasi Server Sementara itu peta konsep mata pelajaran menjelaskan struktur urutan kegiatan belajar dan topik materi pelajaran. Gambar 2 dibawah ini menjelaskan peta konsep mata pelajaran Administrasi Server kelas XI semester 2. Administrasi Server 2 1. Server FTP 2. Server e-Mail 3. Server WebMail 4. Server Remote 5. Server NTP 6. Server .
SNMP V1/V2/V3 Simple Network Management Protocol SNTP Simple Network Time Protocol RFC RFC 768 UDP (User Datagran Protocol) RFC 783 TFTP (Trivial File Transfer Protocol) RFC 791 IP (Internet Protocol) RFC 792 ICMP (Internet Control Message Protocol) RFC 793 TCP (Transmission Control Protocol) R
System x3650 Type 7979 Turn off the server and install options. Did the server start correctly? Yes No Go to the Server Support flow chart on the reverse side of this page. Start the server. Did the server start correctly? Yes No Install the server in the rack cabinet and cable the server and options; then, restart the server. Was the server .
Archaeological Research & Consultancy at the University of Sheffield Graduate School of Archaeology West Court 2 Mappin Street Sheffield S1 4DT Phone 0114 2225106 Fax 0114 2797158 Project Report 873b.3(1) Archaeological Building Recording and Watching Brief: Manor Oaks Farm, Manor Lane, Sheffield, South Yorkshire Volume 1: Text and Illustrations July 2007 By Mark Douglas and Oliver Jessop .
