IEC TC57 WG10 New Orleans, Hubert Kirrmann, Solutil

Slides:



Advertisements
Similar presentations
IETF TICTOC Considerations about IEEE1588 version 2 for Telecom usage.
Advertisements

1588V2 Telecom Profile Framework
G.8275.x telecom time profiles
Innovation in Substation Ethernet Networks
Connecting LANs: Section Figure 15.1 Five categories of connecting devices.
M. Kreider, T. Fleck WhiteRabbit 1 WhiteRabbit Timing System.
IED Time Synchronization John Levine, P.E. Levine Lectronics and Lectric.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.1 Troubleshooting Working at a Small-to-Medium Business or ISP – Chapter 9.
V4 – Executive Summary 1.Provide online add/delete of I/O to support continuous operation. 2.Provide redundant control of remote I/O to support improved.
PTP Update & 1588 Switches.
Layer 2 Switch  Layer 2 Switching is hardware based.  Uses the host's Media Access Control (MAC) address.  Uses Application Specific Integrated Circuits.
Prof. Dr. Hubert Kirrmann ABB Switzerland Ltd Corporate Research, Baden. HSR – High Availability Seamless Redundancy Fault-tolerance in Ethernet networks.
Herbert Falk UCA IOP Group Meeting April 1, 2011 UCA Paris 2011 IOP Results Report ©2011 UCAIug Paris 2011 IOP Results - IEC UCAIug Pv1 1.
VLAN Trunking Protocol (VTP) W.lilakiatsakun. VLAN Management Challenge (1) It is not difficult to add new VLAN for a small network.
IEEE-1588 IEEE-1588 – Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems Defines a Precision Time Protocol.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 2: LAN Redundancy Scaling Networks.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialBCMSN BCMSN v3.0—2-1 Correcting Common VLAN Configuration Errors BSMSN Module.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 LAN Switching and Wireless Implement Spanning Tree Protocols (STP) Chapter.
CCNA 3 Week 9 VLAN Trunking. Copyright © 2005 University of Bolton Origins Dates back to radio and telephone Trunk carries multiple channels over a single.
IEEE P1722 technical issues and talking points
Enterprise PTP profile Doug Arnold, Symmetricom Heiko Gerstung, Meinberg November 8, 2012.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 1: Introduction to Scaling Networks Scaling Networks.
Cisco 3 - Switching Perrine. J Page 16/4/2016 Chapter 4 Switches The performance of shared-medium Ethernet is affected by several factors: data frame broadcast.
Click to edit Master subtitle style
Page 1 Switching Technologies Lecture 4C Hassan Shuja 03/28/2006.
Cisco Network Devices Chapter 6 powered by DJ 1. Chapter Objectives At the end of this Chapter you will be able to:  Identify and explain various Cisco.
Switching Topic 3 VTP. Agenda VTP basics Components Frames and advertisements Domains and revision numbers VTP operations VTP pruning VTP issues.
1 VLANs Relates to Lab 6. Short module on basics of VLAN switching.
Precise measurement of physical link delay 802.1as, IEEE 802 plenary Lu Huang
Instrument Control System Seminar, 20 th -24 th October 2014 Time Synchronisation via Ethernet An introduction to IEEE 1588 Andreas Jost.
Research Unit for Integrated Sensor Systems and Oregano Systems Cern Timing Workshop 2008 Patrick Loschmidt, Georg Gaderer, and Nikolaus Kerö.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Implement Spanning Tree Protocols (STP) LAN Switching and Wireless – Chapter.
Residence Time Measurement draft-mirsky-mpls-residence-time-04 Greg Mirsky John Drake
Precision Time Protocol over MPLS draft-ronc-ptp-mpls-00.txt PWE3 WG IETF Chicago 2007 Ron Cohen
+ Lecture#2: Ethernet Asma ALOsaimi. + Objectives In this chapter, you will learn to: Describe the operation of the Ethernet sublayers. Identify the major.
Chapter-5 STP. Introduction Examine a redundant design In a hierarchical design, redundancy is achieved at the distribution and core layers through additional.
Exploration 3 Chapter 4. What is VTP? VTP allows a network manager to configure a switch so that it will propagate VLAN configurations to other switches.
TICTOC -Topology-Discovery and Clock-Discovery
IEEE-1588 IEEE-1588 – Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems Defines a Precision Time Protocol.
Time Sync Network Limits: Status, Challenges
Advanced Network Tap application for
What is a Protocol A set of definitions and rules defining the method by which data is transferred between two or more entities or systems. The key elements.
Pedro Moreira CERN BE-CO-HT
Youngstown State University Cisco Regional Academy
PTP version 3 in FTI? Øyvind Holmeide/Markus Schmitz by 01/13/2016.
Improving IEEE 1588 synchronization accuracy in 1000BASE-T systems
Instructor Materials Chapter 3: STP
Redundant network topologies for dependable time transfer
Synchronization Quality of IEEE 802
© 2002, Cisco Systems, Inc. All rights reserved.
Networking Devices.
PTPv1 and PTPv2 translation IN FTI Systems
PTP profile for FTI Øyvind Holmeide/Markus Schmitz by 01/13/2016.
G.8275.x telecom time profiles
The White Rabbit Fieldbus
Hubs Hubs are essentially physical-layer repeaters:
Lecture#10: LAN Redundancy
VLAN Trunking Protocol
8th White Rabbit Workshop
T-BERD/MTS TEM Introduction to Sync/Timing for LTE Advanced Mobile Networks Joe Gomez May 2017.
Configuring Catalyst Switch Operations
IEC enabled UniGear Tenders
Hubs Hubs are essentially physical-layer repeaters:
© 2002, Cisco Systems, Inc. All rights reserved.
Precision Time Protocol
Routing and Switching Essentials v6.0
DETERMINISTIC ETHERNET FOR SCALABLE MODULAR AVIONICS
SAASM PRODUCTS OVERVIEW
PTP SOLUTIONS: Using PTP as a backup to GPS
XRAN (eCPRI) S-Plane Sync Update
Presentation transcript:

IEC TC57 WG10 New Orleans, 2017-10-23 Hubert Kirrmann, Solutil Time Synchronization Test Interoperability test, New Orleans 2017, October 14-19 Summary report for IEC TC57 WG10 IEC TC57 WG10 New Orleans, 2017-10-23 Hubert Kirrmann, Solutil

Participants Manufacturers Witnesses ABB NIST Belden – Hirschmann Solutil Doble Cisco GE – Alstom Meinberg MOXA NR OMICRON (lead) Siemens - RuggedCom SEL KERI Vizimax

Tests Grandmasters (GM) individual (9) Transparent clocks (TC) individual (10) Transparent clocks chain (16) Boundary clocks (BC) individual (7) Boundary clocks chain (5) Leap second insertion in boundary clocks chain

Hirschmann RSPE35 1 Gbit/s Full-scale TC test GPS emulator Keri 1 Gbit/s Hirschmann RSPE35 1 Gbit/s GE H29 100 Mbit/s Siemens 2288 100 Mbit/s GE H49 100 Mbit/s Siemens 2488 100 Mbit/s Siemens 2488 100 Mbit/s CISCO IE 4010 100 Mbit/s Meinberg 1 Gbit/s GM TC TC TC TC TC TC TC TC Hirschmann RSP20 100 Mbit/s GE 620 100 Mbit/s Hirschmann RSP35 100 Mbit/s Hirschmann EES35 100 Mbit/s Hirschmann EES25 100 Mbit/s Hirschmann RPS35 100 Mbit/s Hirschmann 1040 100 Mbit/s MOXA PTG 100 Mbit/s Omicron 100 Mbit/s TC TC TC TC TC TC TC GM TC OC OC OC OC OC GE Omicron Visimax Opal Hirschmann netgear deviation less than 300ns , jitter up to 500 ns when changing masters with timeout or priority NIST dashboard Wireshark 1 PPS output

Test results Clocks accuracy is about twice better than what IEC/IEEE 61850-9-3 requires. Chain accuracy better than IEC/IEEE 61850-9-3 and substation applications require (± 300ns after 16 transparent clocks, ± 600ns after 7 boundary clocks) Largest excursion occur when switching grandmasters and removing / restoring GPS, but still well below 1 µs (except for one case between two specific clocks) All grandmasters degrade their clockAccuracy in holdover, but some BC do not. BCs introduce longer time constants in the network which lengthens recovery from loss of grandmaster. Users should avoid BCs where TCs can be used, but BCs are useful to keep synchronized islands (e.g. process bus) in case of failure of the grandmaster. Network is plug-and-play, except for 1-step <> 2-step and 100 Mbit/s <> 1 Gbit/s (an implementation issue). Domains worked in parallel without interference. VLAN and priority are useless for PTP traffic, which is always treated as high priority by the bridges (hardware time-stamping ensures precision). VLANs were not used. Incompatibilities were limited to the optional ALTERNATE_TIME_OFFSET TLV (IRIG-B connection).

Implementation issues All Some clocks do not accept indifferently 1-step and 2-step at ingress Grandmasters: Some GMs indicate a high accuracy even in holdover (no GPS) Few GMs adjust the variance (use a fixed value) which makes it useless. GMs adjust “TimeTraceable” and “FrequencyTraceable” differently GMs interpret Alternate_Time_Offset_Indicator TLV differently. GMs should use the port MAC address as source, not the GM identity GM switchover causes temporary excursions of up to 2.5 µs (one case) Transparent clocks: Some TCs do not respond outside of their primary time domain. Boundary clocks: Few BCs in holdover degrade their clockAccuracy. Some BCs do not forward IP traffic. BCs should indicate the time source of their grandmaster, not “PTP” BCs in holdover (loss of GM) clear leap second indicator when not time traceable Slaves: Some slaves do not observe 2-step correction both in Sync and in Follow_Up (?) Media converters: Need calibration and symmetric behavior.

Standard issues IEC/IEEE 61850-9-3 should: Require padding Sync to the same length as Pdelay_Req (Pdelay_Resp) hat to avoid large errors in media converters (1Gbit/s <> 100 Mbit/s) . Define the behavior of Grandmasters at startup / loss of GPS for the TimeTraceable/FrequencyTraceable flags. Define the behavior of Boundary Clocks at startup / loss / restore Grandmaster to avoid that a bad quality BC takes over as master while it is not yet in sync with its GM. Specify if the leap second indication is also valid when TimeTraceable == false (otherwise the slaves miss the leap second). Insist that slaves must select the best master when several are available, which can be the case momentarily. Relate PTP clock quality to 61850-7-2 TimeStamp and SmpSync. Specify lock-in time or at least ask the manufacturer to provide it. General agreement that all technical traffic should use TAI time scale, not UTC.

Testing issues Companies did not prepare sufficiently for the test All clocks brought to the test should have a 1-page datasheet / PICS (only 3 manufacturers did) Manufacturers should implement network management (SNMP / IEC 61850) Poor discipline: e.g. test rigs disrupted because a participant makes changes without telling Future tests need sniffing device capable of logging the exact moment of the leap second. We need better tools (time-triggered Ethernet frame generator as fake grandmaster). Clocks should have a 1 PPS electrical output for substation network commissioning.

What we could not test Exact behavior at leap second insertion Traffic insertion with L3 traffic on the same domain (should never occur) BMCA switchover with a master set at a different time (but result is predictable) High traffic load Behavior in redundant network topology (PRP / HSR) (this was done in the integration test on Substation 1)

IEEE C37.238 issues Few clocks support C37.238-2017, some support only C37.238-2011, most neither. Unclear what makes C37.238 devices compliant: domain number, TLV? Only one clock passed the (simplified) ALTERNATE_TIME_OFFSET TLV test since C37.238-2017 prescribes unnecessary differences from IEEE 1588 §16.3. (the full ATOI test was skipped). No TC updates dynamically the timeInaccuracy field in the IEEE_C37_238_TLV. IEEE_C37_238_TLV (with timeInaccuracy) is useless for the main inaccuracy source, which is master switchover. General agreement that IEEE C37.238:2017 adds no value, but just confusion and development / testing effort.

Utility Communication Architecture