Server Time Protocol Implementation Considerations

Server Time Protocol Implementation Considerations

Agenda General HMC Panel Overview
Setting up a Coordinated Timing Network (CTN) Configuring an External Time Source Configure Dial Out on HMC Configure an NTP Server Migration from ETR to STP-only CTN Configuring an STP-only CTN Restoring STP configuration information Power outage affecting both servers of two server CTN Across a Power on Reset for single server CTN Additional Information

System (Sysplex) Time task
Timing Network tab

General HMC Panel Overview
ETR Feature Installed ETR Feature NOT Installed STP Feature Installed STP Feature NOT Installed ETR Configuration  System (Sysplex) Time task is not available ETR Status Timing Network Network Configuration STP Configuration STP Status ETS Configuration

Configuring an External Time Source (ETS)
The ETS can be configured as: Dial out to a telephone time service NIST Automated Computer Time Service (ACTS) NRC Canadian Time Service (CTS) IEN Telephone Date Code (CTD) NTP server NTP server with pulse per second (PPS) output

Configuring Dial out as ETS
Steps include: Configure an HMC to dial out to a telephone time service. At the Customize Outbound Connectivity task on the HMC, check both: Enable local system as a call-home server Allow external time source dialing using the local modem Add scheduled operations to the Preferred Time Server (PTS) and the Backup Time Server (BTS), if applicable, to access the ETS.

HMC Setup for ETS Dial out configuration
Customize Outbound Connectivity: External Time Source

HMC Setup for ETS Dial out configuration
Test External Time Source Phone number

Configure ETS Dial Out Schedule
These panels are specific to the Support Element (SE) that you are setting up for Need to set up for CTS Recommended to set up for BTS also

Setup Scheduled Operation/Repeat

NTP Server on HMC as ETS

Configuring an NTP Server on HMC
Customize Console Date and Time – initial view

Add a corporate NTP server The server host name or the IP address of a known NTP server must be entered in this window. This is the IP address of a NTP server on the corporate network

Enable NTP service on this console To turn on the NTP service, check the “Enable NTP service on this console” checkbox and click OK. When you click OK, you should be able to see the console clock at the bottom right corner get updated to the server's time. Even though the time change is instantaneous, it still takes time for the console's NTP code to ensure that the HMC’s NTP server has started properly.

Enable this Hardware Management Console to act as a time server To allow another HMC console, TKE console, or an STP-only CTN to use the HMC as a NTP server, check the “Enable this Hardware Management Console to act as a time server” checkbox and click the OK button.

Configuring an NTP server on the PTS/CTS or BTS
This is the IP address of the HMC NTP Server residing on the private network. It is different from the IP address of the NTP server on the corporate network.

DISCLAIMER Forward Migration
The following example of a forward migration is comprised of excerpts from System z Expo customer presentation, with the customer’s permission STP Implementation Guide (SG ) Some displays will not match the configuration diagrams. The examples shown were not meant to have continuity, they are used to show the logical migration flow for learning purposes.

Starting Environment Site 1 Data Center * ETR Blue Lines
Z9CD z/OS 1.8 SYSC SYSD CFCC CF14 ETR Timing Mode Z9BE z/OS 1.8 SYSB SYSE ETR Timing Mode Z9G z/OS 1.8 SYSG ETR Timing Mode Site 1 Data Center * Z9LPC CFCC CF14 ETR Timing Mode ETR ID = 01 ETR1 ETR ID = 01 ETR2 Z9OC z/OS 1.8 SYSA GDPS/CBU SYSK CFCC CF14 ETR Timing Mode ETR Blue Lines STP (Coupling Links) Solid Green Lines = ICB4+3 Dash Green Lines = ISC3 * Link redundancy not shown Site 2 Data Center * * DWDM not shown Site 1 and Site 2 Data Centers are located approx X km apart.

Preparatory Work General Pre-Implementation Tasks Hardware Software
Install FC 1021 to STP-enable our processors Check hardware and HMC driver levels Installed 9037 LIC upgrade Check STP website to ensure that DWDMs are qualified Software All systems at a STP-supported z/OS release with latest RSUs applied. Enhanced PSP Bucket (FUNCTION_STP). www14.software.ibm.com/webapp/set2/psp/srchBroker CLOCKxx was updated (Note: These are the default values) STPMODE=YES STPZONE=YES IPL all systems*. * Images must be IPL’ed after installing new STP maintenance and STP FC 1021.

Selection of Qualified DWDM Products
Selecting qualified WDM vendor does not mean that WDM model selected is qualified Vendors do not qualify all models Selecting qualified WDM model does not mean that specific Release level is qualified Vendors do not qualify all release levels Ensure that the vendor qualification letter is inspected carefully by a DWDM technical expert. Letter specifies model number, release level, interface modules qualified, protocols, application limitations, etc Vendors to date having qualified DWDM models: Adva Optical Networking Ciena Corporation Cisco Systems Ericsson AB Huawei Technology Lucent Technologies (qualified 2002 – not current technologies) Nortel The latest list of qualified DWDM vendor products can be found on the Resource Link™ Web site at: They are listed under the Hardware Products for Servers on the Library page

Implementation Migrate ETR Network to Mixed CTN
Set CTN ID on all servers Migrate first server to STP timing mode Migrate next two servers to STP timing mode Migrate from Mixed to STP-Only CTN

A T T E N T I O N ! Selecting the System (Sysplex) Time icon results in this panel Do not be alarmed! This is normal The user should read this panel To be aware of what is disruptive Answer Yes to get to the STP panels

Set CTN ID Note: In ETR mode, the ETR Network ID cannot be changed.
Note: Enter STP Network ID here, then hit Apply.

Timing Network - after assigning CTN ID to FIRST server
Mixed CTN

STP Status - after assigning CTN ID to FIRST server

STP Status - after assigning CTN ID to SECOND server

SYSLOG Message IXC438I COORDINATED TIMING INFORMATION HAS BEEN UPDATED
FOR SYSTEM: SYSA PREVIOUS ETR NETID: 01 CURRENT CTNID: DDS_STP1-01 CTN ID! We are now in a Mixed CTN Mixed CTN

“D ETR” output, Before and After
IEA282I TIMING STATUS SYNCHRONIZATION MODE = ETR CPC PORT ACTIVE ==> CPC PORT 1 OPERATIONAL OPERATIONAL ENABLED ENABLED ETR NET ID= ETR NET ID=01 ETR PORT= ETR PORT=05 ETR ID= ETR ID=02 BEFORE D ETR IEA282I TIMING STATUS SYNCHRONIZATION MODE = ETR CPC PORT ACTIVE ==> CPC PORT 1 OPERATIONAL OPERATIONAL ENABLED ENABLED ETR NET ID= ETR NET ID=01 ETR PORT= ETR PORT=05 ETR ID= ETR ID=02 THIS SERVER IS PART OF TIMING NETWORK DDS_STP1-01 AFTER CTN ID Displayed Mixed CTN

“D XCF,S,ALL” output, Before and After
IXC335I DISPLAY XCF SYSTEM TYPE SERIAL LPAR STATUS TIME SYSTEM STATUS SYSA XXXX /07/ :44:21 ACTIVE TM=ETR SYSH XXXX /07/ :44:23 ACTIVE TM=ETR BEFORE As Expected, Nothing Changed! D XCF,S,ALL IXC335I DISPLAY XCF SYSTEM TYPE SERIAL LPAR STATUS TIME SYSTEM STATUS SYSA XXXX /07/ :48:34 ACTIVE TM=ETR SYSH XXXX /07/ :48:33 ACTIVE TM=ETR AFTER

Environment – After CTN ID Set on ALL servers
Z9CD z/OS 1.8 SYSC SYSD CFCC CF15 ETR Timing Mode Stratum 1, DDS_STP1-01 Z9BE z/OS 1.8 SYSB SYSE ETR Timing Mode Stratum 1, DDS_STP1-01 Z9G z/OS 1.8 SYSG ETR Timing Mode Stratum 1, DDS_STP1-01 Site 1 Data Center * Z9LPC CFCC CF15 ETR Timing Mode Stratum 1, DDS_STP1-01 ETR ID = 01 ETR1 ETR ID = 01 ETR2 Z9OC z/OS 1.8 SYSA GDPS/CBU SYSK CFCC CF15 ETR Timing Mode Stratum 1, DDS_STP1-01 ETR Blue Lines STP (Coupling Links) Solid Green Lines = ICB4+3 Dash Green Lines = ISC3 * Link redundancy not shown Site 2 Data Center * * DWDM not shown Site 1 and Site 2 Data Centers are located approx X km apart.

Migrate to STP timing mode – STP Status tab Verification
Before disabling ETR ports, attached systems connectivity must be verified from STP Status tab

Migrate to STP timing mode – Display ETR Ports

Migrate to STP timing mode – Disable ETR Ports
Note: Ports can be disabled at the same time Click Port 1 State -> Disabled radio button, then Apply. Repeat for Port 0.

Migrate to STP timing mode – SYSLOG Messages
*IEA393I ETR PORT 1 IS NOT OPERATIONAL. THIS MAY BE A CTN CONFIGURATION CHANGE. IEA390I TOD CLOCKS DYNAMICALLY ADJUSTED TO MAINTAIN STP SYNCHRONISM. *IEA393I ETR PORT 0 IS NOT OPERATIONAL. THIS MAY BE A CTN IEA380I THIS SYSTEM IS NOW OPERATING IN STP TIMING MODE. JOHN Mixed CTN All systems still alive, CPR (or resume) NOT Required!

Migrate to STP timing mode – STP Status tab verification
After the ports have been disabled, the timing mode can be checked using the STP Status tab. Timing mode Stratum level

Z9OC Hardware Messages Do not be alarmed!
These messages are normal when ETR ports are disabled.

Z9OC Hardware Messages

Migrate to STP timing mode – ETR Status After

Z9OC D ETR Before and After
IEA282I TIMING STATUS 514 SYNCHRONIZATION MODE = ETR CPC PORT ACTIVE ==> CPC PORT 1 OPERATIONAL OPERATIONAL ENABLED ENABLED ETR NET ID= ETR NET ID=01 ETR PORT= ETR PORT=08 ETR ID= ETR ID=02 THIS SERVER IS PART OF TIMING NETWORK DDS_STP1-01 D ETR IEA386I TIMING STATUS SYNCHRONIZATION MODE = STP THIS SERVER IS A STRATUM 2 CTN ID = DDS_STP1-1 NUMBER OF USABLE TIMING LINKS = 9

Z9OC D XCF Before and After
D XCF,S,ALL IXC335I DISPLAY XCF SYSTEM TYPE SERIAL LPAR STATUS TIME SYSTEM STATUS SYSA XXXX /19/ :05:43 ACTIVE TM=ETR SYSH XXXX /19/ :05:41 ACTIVE TM=ETR D XCF,S,ALL IXC335I DISPLAY XCF SYSTEM TYPE SERIAL LPAR STATUS TIME SYSTEM STATUS SYSA XXXX /19/ :09:47 ACTIVE TM=STP SYSH XXXX /19/ :09:41 ACTIVE TM=STP

Diagram 1 (Z9OC to STP timing mode)
Site 1 / Site 2 – Mixed CTN Diagram 1 (Z9OC to STP timing mode) Z9CD z/OS 1.8 SYSC SYSD CFCC CF15 ETR Timing Mode Stratum 1, DDS_STP1-01 Z9BE z/OS 1.8 SYSB SYSE ETR Timing Mode Stratum 1, DDS_STP1-01 Z9G z/OS 1.8 SYSG ETR Timing Mode Stratum 1, DDS_STP1-01 Site 1 Data Center * Z9LPC CFCC CF15 ETR Timing Mode Stratum 1, DDS_STP1-01 ETR ID = 01 ETR1 ETR ID = 02 ETR2 X X Z9OC z/OS 1.8 SYSA GDPS/CBU SYSK CFCC CF15 STP Timing Mode Stratum 2, DDS_STP1-01 ETR Blue Lines STP (Coupling Links) Solid Green Lines = ICB4+3 Dash Green Lines = ISC3 * Link redundancy not shown Site 2 Data Center * * DWDM not shown Site 1 and Site 2 Data Centers are located approx X km apart.

Diagram 2 (Z9BE and Z9G to STP timing mode)
Site 1 / Site 2 – Mixed CTN Diagram 2 (Z9BE and Z9G to STP timing mode) Z9CD z/OS 1.8 SYSC SYSD CFCC CF15 ETR Timing Mode Stratum 1,DDS_STP1-01 Z9BE z/OS 1.8 SYSB SYSE ETR Timing Mode Stratum 2, DDS_STP1-01 Z9G z/OS 1.8 SYSG STP Timing Mode Stratum 2, DDS_STP1-01 X X X X Site 1 Data Center * Z9LPC CFCC CF15 ETR Timing Mode Stratum 1,DDS_STP1-01 ETR ID = 01 ETR1 ETR ID = 02 ETR2 Z9OC z/OS 1.8 SYSA GDPS/CBU SYSK CFCC CF15 STP Timing Mode Stratum 2, DDS_STP1-01 ETR Blue Lines STP (Coupling Links) Solid Green Lines = ICB4+3 Dash Green Lines = ISC3 * Link redundancy not shown Site 2 Data Center * * DWDM not shown Site 1 and Site 2 Data Centers are located approx X km apart.

Network Configuration (Where to go to Assign)
Important: Assignment of server roles must be done on the server that will become the Current Time Server for the STP-only CTN.

Assign STP Roles

Z9CD SYSLOG Messages – STP-Only CTN
IEA390I TOD CLOCKS DYNAMICALLY ADJUSTED TO MAINTAIN STP SYNCHRONISM. *IEA393I ETR PORT 0 IS NOT OPERATIONAL. THIS MAY BE A CTN CONFIGURATION CHANGE. *IEA393I ETR PORT 1 IS NOT OPERATIONAL. THIS MAY BE A CTN CONFIGURATION CHANGE. IEA380I THIS SYSTEM IS NOW OPERATING IN STP TIMING MODE. IXC438I COORDINATED TIMING INFORMATION HAS BEEN UPDATED FOR SYSTEM: SYSC PREVIOUS CTNID: DDS_STP1-01 CURRENT CTNID: DDS_STP1

Z9CD SYSLOG Messages – STP-Only CTN
At 00:10:30.89 *IXC439E ALL SYSTEMS IN SYSPLEX HQPLEX1 ARE NOT SYNCHRONIZED TO THE SAME TIME REFERENCE. SYSTEM: SYSK IS USING CTNID: DDS_STP1 SYSTEM: SYSB IS USING CTNID: DDS_STP1 SYSTEM: SYSG IS USING CTNID: DDS_STP1 SYSTEM: SYSC IS USING CTNID: DDS_STP1-01 SYSTEM: SYSD IS USING CTNID: DDS_STP1-01 SYSTEM: SYSE IS USING CTNID: DDS_STP1 BEFORE At 00:10:31.90 IXC435I ALL SYSTEMS IN SYSPLEX HQPLEX1 ARE NOW SYNCHRONIZED TO THE SAME TIME REFERENCE. SYSTEM: SYSK IS USING CTNID: DDS_STP1 SYSTEM: SYSB IS USING CTNID: DDS_STP1 SYSTEM: SYSG IS USING CTNID: DDS_STP1 SYSTEM: SYSC IS USING CTNID: DDS_STP1 SYSTEM: SYSD IS USING CTNID: DDS_STP1 SYSTEM: SYSE IS USING CTNID: DDS_STP1 AFTER

Site 1 / Site 2 – Migrate to STP CTN
Diagram 3 (STP LIC disables ETR ports on z9CD & Z9LPC4 when roles assigned) Z9CD z/OS 1.8 SYSC SYSD CFCC CF15 STP Timing Mode Stratum 1,DDS_STP1 Z9BE z/OS 1.8 SYSB SYSE STP Timing Mode Stratum 2, DDS_STP1 Z9G z/OS 1.8 SYSG STP Timing Mode Stratum 2, DDS_STP1 Arbiter X PTS/CTS X Site 1 Data Center * Z9LPC CFCC CF15 STP Timing Mode Stratum 2,DDS_STP1 ETR ID = 01 ETR1 ETR ID = 02 ETR2 X X Z9OC z/OS 1.8 SYSA GDPS/CBU SYSK CFCC CF15 STP Timing Mode Stratum 2, DDS_STP1 ETR Blue Lines STP (Coupling Links) Solid Green Lines = ICB4+3 Dash Green Lines = ISC3 * Link redundancy not shown Site 2 Data Center * * DWDM not shown Site 1 and Site 2 Data Centers are located approx X km apart. BTS

Z9CD “D ETR” output, Before and After
IEA282I TIMING STATUS SYNCHRONIZATION MODE = ETR CPC PORT ACTIVE ==> CPC PORT 1 OPERATIONAL OPERATIONAL ENABLED ENABLED ETR NET ID= ETR NET ID=01 ETR PORT= ETR PORT=00 ETR ID= ETR ID=02 THIS SERVER IS PART OF TIMING NETWORK DDS_STP1-01 BEFORE AFTER D ETR IEA386I TIMING STATUS SYNCHRONIZATION MODE = STP THIS SERVER IS A STRATUM 1 CTN ID = DDS_STP1 THE STRATUM 1 NODE ID = S18.IBM XXXXX THIS IS THE PREFERRED TIME SERVER

Z9CD “D XCF,S,ALL” Before and After
IXC335I DISPLAY XCF 976 SYSTEM TYPE SERIAL LPAR STATUS TIME SYSTEM STATUS SYSK XXXX /03/ :04:14 ACTIVE TM=STP SYSB XXXX /03/ :04:17 ACTIVE TM=STP SYSG XXXX /03/ :04:17 ACTIVE TM=STP SYSC XXXX /03/ :04:15 ACTIVE TM=ETR SYSD XXXX /03/ :04:16 ACTIVE TM=ETR SYSE XXXX /03/ :04:17 ACTIVE TM=STP BEFORE AFTER D XCF,S,ALL IXC335I DISPLAY XCF 134 SYSTEM TYPE SERIAL LPAR STATUS TIME SYSTEM STATUS SYSK XXXX /03/ :10:50 ACTIVE TM=STP SYSB XXXX /03/ :10:50 ACTIVE TM=STP SYSG XXXX /03/ :10:50 ACTIVE TM=STP SYSC XXXX /03/ :10:50 ACTIVE TM=STP SYSD XXXX /03/ :10:49 ACTIVE TM=STP SYSE XXXX /03/ :10:51 ACTIVE TM=STP

Selected “RO *ALL,D ETR” output
Z9BE Systems RESPONSES SYNCHRONIZATION MODE = STP THIS SERVER IS A STRATUM 2 THIS IS THE ARBITER SERVER THE STRATUM 1 NODE ID = S18.IBM ZZZZZ Z9CD Systems RESPONSES THIS SERVER IS A STRATUM 1 THIS IS THE PREFERRED TIME SERVER Z9G Systems RESPONSES Z9OC Systems RESPONSES THIS IS THE BACKUP TIME SERVER

STP Status – after migrating to STP-Only CTN

Site 1 / Site 2 – STP only CTN
Z9CD z/OS 1.8 SYSC SYSD CFCC CF15 STP Timing Mode Stratum 1,DDS_STP1 Z9BE z/OS 1.8 SYSB SYSE STP Timing Mode Stratum 2, DDS_STP1 ARB Z9G z/OS 1.8 SYSG STP Timing Mode Stratum 2, DDS_STP1 Arbiter PTS/CTS Site 1 Data Center * Z9LPC CFCC CF15 STP Timing Mode Stratum 2,DDS_STP1 To be used as a Backup server for outages on the PTS, BTS or ARB servers. Manually reassign roles……. Z9OC z/OS 1.8 SYSA GDPS/CBU SYSK CFCC CF15 STP Timing Mode Stratum 2, DDS_STP1 ETR Blue Lines STP (Coupling Links) Solid Green Lines = ICB4+3 Dash Green Lines = ISC3 * Link redundancy not shown Site 2 Data Center * * DWDM not shown Site 1 and Site 2 Data Centers are located approx X km apart. BTS

Setting the Time Zone Offset - Initial

Set Time Zone Automatically adjust is selected by default when the time zone selected supports automatic adjustment of daylight saving time. Otherwise, this button is disabled. Even if automatic adjustment is supported, the user still has the option of selecting Set standard time or Set daylight saving time.

Adjust Time Zone Offset

Setting the Time Zone Offset

DONE! Implementation Migrate ETR Network to Mixed CTN
Set CTN ID on all servers Migrate servers to STP timing mode Migrate from Mixed to STP-Only CTN DONE!

Ending Environment for STP-Only CTN Example

Implementation – Configuring a STP-Only CTN
Set CTN ID Initialize the time Assign CTN Roles

Set CTN ID The same CTN ID must be entered on every server that will participate in the STP-only CTN.

Initialize the time Initialize Time button enabled ONLY IF
Initialize Time button is accessed from the Network Configuration tab Initialize Time button enabled ONLY IF CTS and PTS roles have not been assigned AND After CTN ID has been defined for server that will become CTS/PTS. Important: Initializing the time must be done on the server that will become the Current Time Server for the STP-only CTN.

Set Leap Seconds Clicking Initialize Time on the Network Configuration tab displays the Initialize Time window There are three radio buttons on the window, each representing a task that needs to be completed before a Network Configuration can be applied to an STP-only CTN.

Set Leap Seconds Although the installation may not be sensitive to leap seconds, a valid Leap Seconds Offset value needs to be entered to complete the Initialize Time task. If Leap Seconds are not used, enter a zero value.

Set Time Zone Automatically adjust is selected by default when the time zone selected supports automatic adjustment of daylight saving time. Otherwise, this button is disabled. Even if automatic adjustment is supported, the user still has the option of selecting Set standard time or Set daylight saving time.

Adjust Time Zone Offset

Set date and time If the local date and time are to be set to specific values, click the Set date and time button. If an ETS is configured, the date and time should be initialized by selecting the option Use External Time Source to set date and time Regardless of the method chosen, STP uses the information to calculate the Coordinated Server Time and set the servers’ TOD clock when the OK button is clicked.

Set date and time At this point, the three tasks on the Initialize Time window have a check mark in the Complete column The user needs to click Cancel to exit the Initialize Time task and return to the Network Configuration tab. The Coordinated Server Time will be passed to other participating servers in the CTN when the server roles and the Current Time Server are assigned

Assign Server Roles Initialize Time task is complete Apply button is enabled Server roles can now be assigned Important: Assignment of server roles must be done on the server that will become the Current Time Server for the STP-only CTN.

Assign PTS/CTS Because the PTS will be the only server assigned in this first step, it has to be the CTS Force configuration box must be specified when configuring a new STP-only CTN for the first time in order to bypass connectivity verification, as a Current Time Server does not yet exist.

Assign BTS Because the CTS already exists, the Force configuration option is not required or recommended – allows STP to perform connectivity check between PTS and BTS.

Verify on HMC – Timing Network tab
Time field of the Coordinated Server Time section identifies the current time on the server.

Verify on HMC- STP Status tab
STP Timing Mode – Stratum 1

Verify on HMC – STP Status tab
STP Timing Mode – Stratum 2

z/OS Verification – DISPLAY ETR
Synchronization mode Stratum level Node ID of Stratum 1 Server Server role (if applicable) Number of usable links This is the PTS/CTS NUMBER OF USABLE TIMING LINKS message will not appear here because it is not applicable for the CTS

z/OS Verification – DISPLAY XCF,SYSPLEX,ALL
DISPLAY XCF,SYSPLEX,ALL identifies the timing mode of all sysplex members that are STP

Set CTN ID Initialize the time Assign CTN Roles DONE!

STP configuration and time information saved across Power on Resets or power outages – two server CTN Previously If both servers experienced an unplanned or planned power outage, user had to: Initialize the Time; Redefine the PTS, BTS, CTS roles System Management Enhancement STP CTN configuration (PTS/CTS, BTS) can be configured so that PTS/CTS, BTS roles possibly restored after IML/POR Initialize Time not required

Prerequisites / required set up
MCLs required: z9 EC and BC Bundle 44 z10 EC and BC Bundle 26 Function not available on D55 (z990, z890) If migrating from ETR network PTS/CTS and BTS must first be assigned using procedures outlined in Server Time Protocol Implementation Guide, SG , section 2.5.1 If setting up a new STP-only CTN PTS/CTS and BTS must first be assigned using procedures outlined in Server Time Protocol Implementation Guide, SG section 3.4 STP-only CTN can only have two servers to enable this function If more than two servers in operational CTN, Remove additional servers in the CTN by assigning them to a different to a different CTN, if possible Cannot proceed with this enhancement with more than two servers in CTN

Enable “Save configuration” enhancement
Launch the System (Sysplex) Time task of the server that is the CTS Go to the Network Configuration tab Check the box “Only allow the server(s) specified above to be in the CTN” Click Apply “Only allow the server(s) specified above to be in the CTN” can be enabled only if two servers can communicate over coupling links Cannot select “Force Configuration” and “Only allow the server(s) specified above to be in the CTN” at the same time – error message generated Note: Recovery and re-takeover rules unchanged for a CTN with PTS and BTS assigned

STP configuration and time information saved across Power on Reset or power outage – Single server CTN Previously For an already operational single server CTN, when IML/POR done, user was required to: Initialize the Time Redefine that server as the stratum 1 System Management enhancement Customer selects the option to not allow any other servers to join the single server CTN when configuring the CTN STP CTN configuration (PTS/CTS) will be reinstated after IML/POR Initialize Time not required Also available on z990, z890

STP configuration and time information saved across Power on Resets or power outages (continued)
Launch the System (Sysplex) Time task of the server that is the CTS Go to the Network Configuration tab Check the box “Only allow the server(s) specified above to be in the CTN” Click Apply

Setting up a Coordinated Timing Network (CTN) Configuring an External Time Source Configure Dial Out on HMC Configure an NTP Server Migration from ETR to STP-only CTN Configuring an STP-only CTN Restoring STP configuration information Across a Power on Reset for single server CTN Power outage affecting both servers of two server CTN Additional Information

Additional Information
Redbooks® Server Time Protocol Planning Guide SG Server Time Protocol Implementation Guide SG Education Introduction to Server Time Protocol (STP) Available on Resource Link™ STP Web site Systems Assurance The IBM team is required to complete a Systems Assurance Review (SAPR Guide SA06-012) and to complete the Systems Assurance Confirmation Form via Resource Link Techdocs and WSC Flashes Search on “STP”

IBM Implementation Services for System z – Server Time Protocol (6948-J56)
Offering Description This offering is designed to assist clients to quickly and safely implement Server Time Protocol within their existing environments. STP provides clients with the capability to efficiently manage time synchronization within their multi-server infrastructure. Following best practices and using detailed planning services, IBM helps clients identify various implementation models and engage in the appropriate configuration required to effectively support STP for driving a more responsive business and IT infrastructure. Program, Play, Industry Alignment Infrastructure Improvement; Energy Efficiency; Better performance and lower operational cost Client Value (enables customers to...) Swift and secure implementation of STP for improved availability, integrity and performance Improves multi-server time synchronization without interrupting operations Enables integration with next generation of System z infrastructure Target Audience Primarily core, Large Enterprise customers. Existing z midrange clients Key Competitors In house staff Competitive Differentiation Leverages best practices with secure implementation Short implementation time – lower risk Provides support and facilitates knowledge sharing through IBM’s mainframe expertise Proof Points & Claims for Client Value / Differentiation Need to safely implement a reliable replacement for Sysplex Timer® while maintaining continuous operations Cost of providing and maintaining hardware, floor space and solution support for additional Sysplex Timer intermediate site Lack of in-house expertise, skills and resources for implementing Server Time Protocol Engagement Portfolio Offering Manager Anna Lee/Southbury/IBM, , T/L:

IBM Announces – IBM Implementation Services for System z – Server Time Protocol Implementation of STP for improved availability and performance Offering Assist clients to quickly and safely implement Server Time Protocol within their existing environments. IBM helps clients identify various implementation models and engage in the appropriate configuration required to effectively support STP for driving a more responsive business and IT infrastructure Customer Value: - Improves multi-server time synchronization without interrupting operations - Enables integration with next generation of System z infrastructure - Swift and secure implementation of STP for improved availability, integrity, and performance - Reduces hardware maintenance and power costs while eliminating intermediate site requirements for Sysplex Timer Leverages IBM’s knowledge and best practices to help implementation of Server Time Protocol

Reference Material - Terminology
APAR Authorized Program Analysis Report ARB Arbiter BTS Backup Time Server CF Coupling Facility CTS Current Time Server CTN Coordinated Timing Network DWDM Dense Wave Division Multiplexer ETR External Time Reference ETS External Time Source FC Feature Code HMC Hardware Management Console HCA Host Channel Adapter ICB Integrated Cluster Bus IPL Initial Program Load ISC InterSystem Coupling Channel LAN Local Area Network LIC Licensed Internal Code LPAR Logically Partition NTP Network Time Protocol PR/SM Processor Resource / Systems Manager PSIFB Parallel Sysplex Infiniband PTF Temporary Program Fix PTS Preferred Time Server SW Software (programs and operating systems) SE Support Element TPF Operating System UTC Coordinated Universal Time zVM Operating System zVSE Operating System z/OS Operating System z/VM Operating System

Questions?

Thank You! The End

Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. For a complete list of IBM Trademarks, see *, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA, WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, System z10®, BladeCenter® The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. 102

Server Time Protocol Implementation Considerations

Similar presentations

Presentation on theme: "Server Time Protocol Implementation Considerations"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Server Time Protocol Implementation Considerations

Similar presentations

Presentation on theme: "Server Time Protocol Implementation Considerations"— Presentation transcript:

Similar presentations

About project

Feedback