pc37.238™/d5.5 draft standard for use of ieee std. 1588 ...testing.ucaiug.org/testing/subcommittee...

PC37.238™/D5.5, September 2010

Copyright © 2010 IEEE. All rights reserved. This is an unapproved IEEE Standards Draft, subject to change.

PC37.238™/D5.5 1

Draft Standard for Use of IEEE 2

Std. 1588 Precision Time Protocol in 3

Power System Applications 4

Sponsor 5

Power System Relaying Committee and Substations Committee 6 of the 7 IEEE Power and Energy Society 8

Approved <XX MONTH 20XX> 9

IEEE-SA Standards Board 10 11

Copyright © 2010 by the Institute of Electrical and Electronics Engineers, Inc. 12 Three Park Avenue 13 New York, New York 10016-5997, USA 14

All rights reserved. 15

This document is an unapproved draft of a proposed IEEE Standard. As such, this document is subject to 16 change. USE AT YOUR OWN RISK! Because this is an unapproved draft, this document must not be 17 utilized for any conformance/compliance purposes. Permission is hereby granted for IEEE Standards 18 Committee participants to reproduce this document for purposes of international standardization 19 consideration. Prior to adoption of this document, in whole or in part, by another standards development 20 organization, permission must first be obtained from the IEEE Standards Activities Department 21 ([email protected]). Other entities seeking permission to reproduce this document, in whole or in part, must 22 also obtain permission from the IEEE Standards Activities Department. 23

IEEE Standards Activities Department 24 445 Hoes Lane 25 Piscataway, NJ 08854, USA 26

27



Abstract: This standard specifies a common profile for use of IEEE 1588-2008 Precision Time 1 Protocol (PTP) in power system protection, control, automation and data communication 2 applications utilizing an Ethernet communications architecture. 3 Keywords: IEEE 1588, precise time synchronization, precision time protocol, grandmaster clock, 4 transparent clock, slave-only clock, sample synchronization, synchrophasors, power substation. 5 6

7

8

The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright © 20XX by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published <XX MONTH 20XX>. Printed in the United States of America. IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and Electronics Engineers, Incorporated. PDF: ISBN 978-0-XXXX-XXXX-X STDXXXXX Print: ISBN 978-0-XXXX-XXXX-X STDPDXXXXX IEEE prohibits discrimination, harassment and bullying. For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher.



IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of 1 the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus 2 development process, approved by the American National Standards Institute, which brings together volunteers 3 representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the 4 Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote 5 fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy 6 of any of the information or the soundness of any judgments contained in its standards. 7

Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other 8 damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly 9 resulting from the publication, use of, or reliance upon this, or any other IEEE Standard document. 10

The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly 11 disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific 12 purpose, or that the use of the material contained herein is free from patent infringement. IEEE Standards documents 13 are supplied “AS IS.” 14

The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, 15 market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint 16 expressed at the time a standard is approved and issued is subject to change brought about through developments in the 17 state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least 18 every five years for revision or reaffirmation, or every ten years for stabilization. When a document is more than five 19 years old and has not been reaffirmed, or more than ten years old and has not been stabilized, it is reasonable to 20 conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are 21 cautioned to check to determine that they have the latest edition of any IEEE Standard. 22

In publishing and making this document available, the IEEE is not suggesting or rendering professional or other 23 services for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other 24 person or entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon his or 25 her independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the 26 advice of a competent professional in determining the appropriateness of a given IEEE standard. 27

Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to 28 specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate 29 action to prepare appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is 30 important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, 31 IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant 32 response to interpretation requests except in those cases where the matter has previously received formal consideration. 33 A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual 34 shall not be considered the official position of IEEE or any of its committees and shall not be considered to be, nor be 35 relied upon as, a formal interpretation of the IEEE. At lectures, symposia, seminars, or educational courses, an 36 individual presenting information on IEEE standards shall make it clear that his or her views should be considered the 37 personal views of that individual rather than the formal position, explanation, or interpretation of the IEEE. 38

Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation 39 with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with 40 appropriate supporting comments. Recommendations to change the status of a stabilized standard should include a 41 rationale as to why a revision or withdrawal is required. Comments and recommendations on standards, and requests 42 for interpretations should be addressed to: 43

Secretary, IEEE-SA Standards Board 44 445 Hoes Lane 45 Piscataway, NJ 08854 46 USA 47

Authorization to photocopy portions of any individual standard for internal or personal use is granted by The Institute 48 of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. 49 To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood 50 Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for 51 educational classroom use can also be obtained through the Copyright Clearance Center. 52

iv Copyright © 2010 IEEE. All rights reserved.

This is an unapproved IEEE Standards Draft, subject to change.

Introduction 1

This introduction is not part of IEEE PC37.238/D5.3, Draft Standard Profile for Use of IEEE Std 1588 Precision Time 2 Protocol in Power System Applications. 3

This standard specifies a common profile for use of IEEE 1588-2008 Precision Time Protocol (PTP) in 4 power system protection, control, automation and data communication applications utilizing an Ethernet 5 communications architecture. 6

The profile can be used for precise time synchronization of the devices in a substation, and between 7 substations in a larger geographical area, if performance requirements of this standard are met. 8

The use of different physical layer communication technologies to carry Ethernet frames, including 9 SONET/SDH and wireless technologies, are not precluded if they can meet performance requirements of 10 this standard. 11

Notice to users 12

Laws and regulations 13

Users of these documents should consult all applicable laws and regulations. Compliance with the 14 provisions of this standard does not imply compliance to any applicable regulatory requirements. 15 Implementers of the standard are responsible for observing or referring to the applicable regulatory 16 requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in 17 compliance with applicable laws, and these documents may not be construed as doing so. 18

Copyrights 19

This document is copyrighted by the IEEE. It is made available for a wide variety of both public and 20 private uses. These include both use, by reference, in laws and regulations, and use in private self-21 regulation, standardization, and the promotion of engineering practices and methods. By making this 22 document available for use and adoption by public authorities and private users, the IEEE does not waive 23 any rights in copyright to this document. 24

Updating of IEEE documents 25

Users of IEEE standards should be aware that these documents may be superseded at any time by the 26 issuance of new editions or may be amended from time to time through the issuance of amendments, 27 corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the 28 document together with any amendments, corrigenda, or errata then in effect. In order to determine whether 29 a given document is the current edition and whether it has been amended through the issuance of 30 amendments, corrigenda, or errata, visit the IEEE Standards Association web site at 31 http://ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously. 32

For more information about the IEEE Standards Association or the IEEE standards development process, 33 visit the IEEE-SA web site at http://standards.ieee.org. 34

v Copyright © 2010 IEEE. All rights reserved.


Errata 1

Errata, if any, for this and all other standards can be accessed at the following URL: 2 http://standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL 3 for errata periodically. 4

Interpretations 5

Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/ 6 index.html. 7

Patents 8

[If the IEEE has not received letters of assurance prior to the time of publication, the following notice 9 shall appear:] 10

Attention is called to the possibility that implementation of this<opt_trial-use><gde./rec. prac./std.> may 11 require use of subject matter covered by patent rights. By publication of this<opt_trial-use><gde./rec. 12 prac./std.>, no position is taken with respect to the existence or validity of any patent rights in connection 13 therewith. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be 14 required, for conducting inquiries into the legal validity or scope of Patents Claims or determining whether 15 any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, 16 or in any licensing agreements are reasonable or non-discriminatory. Users of this<opt_trial-use><gde./rec. 17 prac./std.> are expressly advised that determination of the validity of any patent rights, and the risk of 18 infringement of such rights, is entirely their own responsibility. Further information may be obtained from 19 the IEEE Standards Association. 20

[The following notice shall appear when the IEEE receives assurance from a known patent holder or 21 patent applicant prior to the time of publication that a license will be made available to all applicants 22 either without compensation or under reasonable rates, terms, and conditions that are demonstrably free 23 of any unfair discrimination.] 24

Attention is called to the possibility that implementation of this<opt_trial-use><gde./rec. prac./std.> may 25 require use of subject matter covered by patent rights. By publication of this<opt_trial-use><gde./rec. 26 prac./std.>, no position is taken with respect to the existence or validity of any patent rights in connection 27 therewith. A patent holder or patent applicant has filed a statement of assurance that it will grant licenses 28 under these rights without compensation or under reasonable rates, with reasonable terms and conditions 29 that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses. Other 30 Essential Patent Claims may exist for which a statement of assurance has not been received. The IEEE is 31 not responsible for identifying Essential Patent Claims for which a license may be required, for conducting 32 inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or 33 conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing 34 agreements are reasonable or non-discriminatory. Users of this<opt_trial-use><gde./rec. prac./std.> are 35 expressly advised that determination of the validity of any patent rights, and the risk of infringement of 36 such rights, is entirely their own responsibility. Further information may be obtained from the IEEE 37 Standards Association. 38

39

vi Copyright © 2010 IEEE. All rights reserved.


Participants 1

At the time this draft<opt_trial-use><gde./rec. prac./std.> was submitted to the IEEE-SA Standards Board 2 for approval, the <Working Group Name> Working Group had the following membership: 3

<Chair Name>, Chair 4 <Vice-chair Name>, Vice Chair 5

6 Participant1 7 Participant2 8 Participant3 9

Participant4 10 Participant5 11 Participant6 12

Participant7 13 Participant8 14 Participant9 15

16 17 The following members of the <individual/entity> balloting committee voted on this<opt_trial-18 use><gde./rec. prac./std.>. Balloters may have voted for approval, disapproval, or abstention. 19 20 (to be supplied by IEEE) 21 22 Balloter1 23 Balloter2 24 Balloter3 25

Balloter4 26 Balloter5 27 Balloter6 28

Balloter7 29 Balloter8 30 Balloter9 31

32 33 When the IEEE-SA Standards Board approved this<opt_trial-use><gde./rec. prac./std.> on <XX MONTH 34 20XX>, it had the following membership: 35

(to be supplied by IEEE) 36 <Name>, Chair 37

<Name>, Vice Chair 38 <Name>, Past President 39

<Name>, Secretary 40 41 SBMember1 42 SBMember2 43 SBMember3 44

SBMember4 45 SBMember5 46 SBMember6 47

SBMember7 48 SBMember8 49 SBMember9 50

*Member Emeritus 51

52 53 Also included are the following nonvoting IEEE-SA Standards Board liaisons: 54

<Name>, NRC Representative 55 <Name>, DOE Representative 56 <Name>, NIST Representative 57

58 <Name> 59

IEEE Standards Program Manager, Document Development 60 61

<Name> 62 IEEE Standards Program Manager, Technical Program Development 63

64 65

vii Copyright © 2010 IEEE. All rights reserved.


Contents 1

1. Overview .................................................................................................................................................... 1 2 1.1 Scope ................................................................................................................................................... 1 3 1.2 Purpose ................................................................................................................................................ 1 4

2. Normative references .................................................................................................................................. 2 5

3. Definitions and special terms ..................................................................................................................... 2 6 3.1 Definitions ........................................................................................................................................... 2 7 3.2 Special terms........................................................................................................................................ 5 8

4. Abbreviations ............................................................................................................................................. 5 9

5. Standard Profile for Power System Applications ....................................................................................... 6 10 5.1 Identification ........................................................................................................................................ 6 11 5.2 PTP attribute values ............................................................................................................................. 6 12 5.3 Path Delay Mechanism ........................................................................................................................ 7 13 5.4 Best Master Clock Algorithm .............................................................................................................. 7 14 5.5 Management Mechanism ..................................................................................................................... 7 15 5.6 Transport Mechanism ........................................................................................................................ 10 16 5.7 Clock Types ....................................................................................................................................... 10 17 5.8 Communication Model ...................................................................................................................... 11 18 5.9 Timescale ........................................................................................................................................... 11 19 5.10 Clause 16 and 17 Annex K and L Options ...................................................................................... 11 20 5.11 clockIdentity .................................................................................................................................... 12 21 5.12 TLVs ................................................................................................................................................ 12 22

Annex A (informative) Operating modes ..................................................................................................... 13 23 A.1 Overview .......................................................................................................................................... 13 24 A.2 Description ........................................................................................................................................ 13 25

Annex B (normative) Time performance requirements ................................................................................ 15 26

Annex C (informative) Time performance parameters and their use for IEC 61850 and IEEE C37.118 27 applications ................................................................................................................................................... 16 28

C.1 Time performance parameters........................................................................................................... 16 29 C.2 Use of IEEE C37.238 MIB for time performance parameters .......................................................... 17 30 C.3 Use of IEEE C37.238 for IEC 61850 applications ............................................................................ 17 31 C.4 Use of IEEE C37.238 for IEEE C37.118 applications ...................................................................... 18 32

Annex D (informative) Use of IEEE C37.238 messages for Slave-Only clocks (IRIG-B replacement) ...... 20 33 D.1 Use of received IEEE C37.238 Sync and Follow_Up messages to obtain a PTP Time ................... 20 34 D.2 Use of received IEEE C37.238 Announce messages to determine UTC time and Local time ......... 21 35 D.3 Use of received IEEE C37.238 Announce messages to determine the time’s quality ...................... 22 36

Annex E (informative) Use of IEEE C37.238 for IEC 62439-3 ................................................................... 24 37 E.1 Overview ........................................................................................................................................... 24 38 E.2 PRP Mapping .................................................................................................................................... 24 39 E.3 HSR Mapping.................................................................................................................................... 25 40

Annex F (normative) Management Information Base .................................................................................. 27 41

viii Copyright © 2010 IEEE. All rights reserved.


Annex G (informative) Bibliography ........................................................................................................... 52 1 2

PC37.238/D5.5, September 2010

1 Copyright © 2010 IEEE. All rights reserved.


Draft Standard for Use of IEEE 1

Std. 1588 Precision Time Protocol in 2

Power System Applications 3

IMPORTANT NOTICE: This standard is not intended to ensure safety, security, health, or 4 environmental protection. Implementers of the standard are responsible for determining appropriate 5 safety, security, environmental, and health practices or regulatory requirements. 6

This IEEE document is made available for use subject to important notices and legal disclaimers. 7 These notices and disclaimers appear in all publications containing this document and may 8 be found under the heading “Important Notice” or “Important Notices and Disclaimers 9 Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at 10 http://standards.ieee.org/IPR/disclaimers.html. 11

1. Overview 12

1.1 Scope 13

This standard specifies a common profile for use of IEEE 1588-2008 Precision Time Protocol (PTP) in 14 power system protection, control, automation and data communication applications utilizing an Ethernet 15 communications architecture. 16

The profile specifies a well-defined subset of IEEE 1588-2008 mechanisms and settings aimed at enabling 17 device interoperability, robust response to network failures, and deterministic control of delivered time 18 quality. It specifies the preferred physical layer (Ethernet), higher level protocol used for PTP message 19 exchange and the PTP protocol configuration parameters. Special attention is given to ensuring consistent 20 and reliable time distribution within substations, between substations, and across wide geographic areas. 21

1.2 Purpose 22

The purpose of this standard is to facilitate adoption of IEEE Std 1588-2008 for power system applications 23 requiring high precision time synchronization. It specifies a common subset of PTP parameters and options 24 to provide global time availability, device interoperability and failure management. This set of PTP 25 parameters and options allows IEEE 1588-2008 based time synchronization to be used in mission critical 26 power system protection, control, automation and data communication applications. 27




2. Normative references 1

The following referenced documents are indispensable for the application of this document (i.e., they must 2 be understood and used, so each referenced document is cited in text and its relationship to this document is 3 explained). For dated references, only the edition cited applies. For undated references, the latest edition of 4 the referenced document (including any amendments or corrigenda) applies. 5

IEEE Std 1588TM – 2008, IEEE Standard for a Precision Clock Synchronization Protocol for Networked 6 Measurement and Control Systems. 7

3. Definitions and special terms 8

For the purposes of this document, the following terms and definitions apply. The IEEE Standards 9 Dictionary: Glossary of Terms & Definitions should be referenced for terms not defined in this clause.1 10

For the purposes of this document, the following terms and definitions and special terms apply. 11

3.1 Definitions 12

3.1.1 accuracy: The mean of the time or frequency error between the clock under test and a perfect 13 reference clock, over an ensemble of measurements. Stability is a measure of how the mean varies with 14 respect to variables such as time, temperature, and so on. The precision is a measure of the deviation of the 15 error from the mean. 16

3.1.2 boundary clock: A clock that has multiple Precision Time Protocol (PTP) ports in a domain and 17 maintains the timescale used in the domain. It may serve as the source of time, i.e., be a master clock, and 18 may synchronize to another clock, i.e., be a slave clock. 19

3.1.3 clock: A device participating in the Precision Time Protocol (PTP) that is capable of providing a 20 measurement of the passage of time since a defined epoch. 21

NOTE—In the case of PTP ordinary and boundary clocks that are properly synchronized, the epoch is the epoch of the 22 timescale in use. In the case of PTP transparent clocks, the epoch is locally defined and not necessarily aligned with the 23 timescale. 24

3.1.4 device: a node with one or more Ethernet ports that is compliant to IEEE C37.238 standard. 25

NOTE—Devices are network devices and ordinary clocks. 26

3.1.5 default: When applied to attribute values and options means the configuration of a Precision Time 27 Protocol (PTP) device as it is delivered from the manufacturer. 28

3.1.6 domain: A logical grouping of clocks that synchronize to each other using the protocol, but that are 29 not necessarily synchronized to clocks in another domain. 30

3.1.7 end device: an application specific device with slave-only clock functionality. 31

3.1.8 epoch: The origin of a timescale. 32

1 The IEEE Standards Dictionary: Glossary of Terms & Definitions is available at http://shop.ieee.org/.




3.1.9 event: An abstraction of the mechanism by which signals or conditions are generated and 1 represented. 2

3.1.10 HSR node: a device with HSR functionality compliant to IEC 62439-3 with hybrid clock. 3

3.1.11 hybrid clock: a device with transparent clock and ordinary clock. 4

3.1.12 grandmaster-capable clock: An ordinary clock that is currently capable of PTP Master state. 5

3.1.13 grandmaster clock: Within a domain, a clock that is the ultimate source of time for clock 6 synchronization using the protocol. 7

3.1.14 holdover: A clock previously synchronized/syntonized to another clock (normally a primary 8 reference or a master clock) but now free-running based on its own internal oscillator, whose frequency is 9 being adjusted using data acquired while it had been synchronized/syntonized to the other clock. It is said 10 to be in holdover or in the holdover mode, as long as it is within its accuracy requirements. 11

3.1.15 link: A network segment between two Precision Time Protocol (PTP) ports supporting the peer 12 delay mechanism of this standard. The peer delay mechanism is designed to measure the propagation time 13 over such a link. 14

3.1.16 multicast communication: A communication model in which each Precision Time Protocol (PTP) 15 message sent from any PTP port is capable of being received and processed by all PTP ports on the same 16 PTP communication path. 17

3.1.17 network device: a device used on PTP communication path to connect grandmaster clock to one or 18 more ordinary clocks directly or through one or more network devices. 19

NOTE—Ethernet bridges and HSR nodes are network devices. 20

3.1.18 one-step clock: A clock that provides time information using a single event message. 21

3.1.19 ordinary clock: A clock that has a single Precision Time Protocol (PTP) port in a domain and 22 maintains the timescale used in the domain. It may serve as a source of time, i.e., be a master clock, or may 23 synchronize to another clock, i.e., be a slave clock. 24

NOTE—An ordinary clock can be grandmaster-capable or slave-only clock. 25

3.1.20 parent clock: The master clock to which a clock is synchronized. 26

3.1.21 peer-to-peer transparent clock: A transparent clock that, in addition to providing Precision Time 27 Protocol (PTP) event transit time information, also provides corrections for the propagation delay of the 28 link connected to the port receiving the PTP event message. In the presence of peer-to-peer transparent 29 clocks, delay measurements between slave clocks and the master clock are performed using the peer-to-30 peer delay measurement mechanism. 31

3.1.22 portNumber: An index identifying a specific Precision Time Protocol (PTP) port on a PTP node. 32

3.1.23 precision: See: accuracy. 33

3.1.24 Precision Time Protocol (PTP): The protocol defined by IEEE Std. 1588-2008. As an adjective, it 34 indicates that the modified noun is specified in or interpreted in the context of IEEE Std. 1588-2008. 35

3.1.25 primary reference: A source of time and or frequency that is traceable to international standards. 36 See also: traceability. 37




3.1.26 profile: The set of allowed Precision Time Protocol (PTP) features applicable to a device. 1

3.1.27 Precision Time Protocol (PTP) communication: Information used in the operation of the protocol, 2 transmitted in a PTP message over a PTP communication path. 3

3.1.28 Precision Time Protocol (PTP) communication path: The signaling path portion of a particular 4 network enabling direct communication among ordinary and boundary clocks. 5

3.1.29 Precision Time Protocol (PTP) message: One of the message types defined in IEEE Std. 1588-6 2008. 7

3.1.30 Precision Time Protocol (PTP) port: A logical access point of a clock for PTP communications to 8 the communications network. 9

3.1.31 recognized standard time source: A recognized standard time source is a source external to 10 Precision Time Protocol (PTP) that provides time and/or frequency as appropriate that is traceable to the 11 international standards laboratories maintaining clocks that form the basis for the International Atomic 12 Time (TAI) and Universal Coordinated Time (UTC) timescales. Examples of these are Global Positioning 13 System (GPS), NTP, and National Institute of Standards and Technology (NIST) timeservers. 14

3.1.32 residence time: The time difference between ingress and egress timestamps for a IEEE C37.238 15 Sync message. 16

3.1.33 slave-only clock: An ordinary clock that is not currently capable of PTP Master state. 17

3.1.34 stability: See: accuracy. 18

3.1.35 synchronized clocks: Two clocks are synchronized to a specified uncertainty if they have the same 19 epoch and their measurements of the time of a single event at an arbitrary time differ by no more than that 20 uncertainty. 21

3.1.36 syntonized clocks: Two clocks are syntonized if the duration of the second is the same on both, 22 which means the time as measured by each advances at the same rate. They may or may not share the same 23 epoch. 24

3.1.37 timeout: A mechanism for terminating requested activity that, at least from the requester’s 25 perspective, does not complete within the specified time. 26

3.1.38 timescale: A linear measure of time from an epoch. 27

3.1.39 traceability: A property of the result of a measurement or the value of a standard whereby it can be 28 related to stated references, usually national or international standards, through an unbroken chain of 29 comparisons all having stated uncertainties. (adapted from the International Vocabulary of Basic and 30 General Terms in Metrology [B7]) 31

3.1.40 transparent clock: A device that measures the time taken for a Precision Time Protocol (PTP) 32 event message to transit the device and provides this information to clocks receiving this PTP event 33 message. See also: end-to-end transparent clock; peer-to-peer transparent clock. 34

3.1.41 two-step clock: A clock that provides time information using the combination of an event message 35 and a subsequent general message. See also: one-step clock. 36




3.2 Special terms 1

3.2.1 IEEE C37.238 message: a PTP message compliant to IEEE C37.238 standard. 2

4. Abbreviations 3

The following abbreviations are used in this standard: 4

API Application Programming Interface 5

BMC best master clock 6

BC boundary clock 7

DANP double attached node implementing PRP 8

DANH double attached node implementing HSR 9

DNP Distributed Network Protocol 10

IERS International Earth Rotation and Reference Systems Service 11

GPS Global Positioning System 12

HSR High-availability Seamless Redundancy 13

ID identification 14

IED Intelligent Electronic Device 15

LN Logical Node 16

MAC media access control [according to IEEE Std. 802.3-2005] 17

MIB Management Information Base 18

OUI organizational unique identifier (allocated by the IEEE) 19

NOTE—The OUI is typically used in specifications or the implementation of devices for the purpose of identification. 20 It identifies the organization that owns the OUI-dependent subidentifier and may not necessarily be the organization 21 that defines the specification or provides the hardware. The IEEE OUI listing can be obtained at 22 http://standards.ieee.org/regauth/oui/index.shtml. 23

P2P peer-to-peer 24

RCT Redundancy Control Trailer 25

PRP Parallel Redundancy Protocol 26

PTP Precision Time Protocol 27

SCADA Supervisory Control and Data Acquisition 28




SNMP Simple Network Management Protocol 1

SV Sampled Value 2

TC transparent clock 3

TLV type, length, value [according to IEEE Std. 802.1AB] 4

UTC Coordinated Universal Time 5

5. Standard Profile for Power System Applications 6

5.1 Identification 7

PTP Profile 8

IEEE Standard Profile for Use of IEEE 1588 Precision Time Protocol in Power System Applications 9

Version: 1.0 10

Profile identifier: 1C-12-9D-00-00-00 11

This profile is specified by the IEEE 1588 Profile for Power System Applications Working Group of the 12 IEEE Power System Relaying Committee and IEEE Power System Substation Committee. A copy may be 13 obtained by ordering IEEE Std C37.238-2011 from IEEE Standards Organization http://standards.ieee.org. 14

5.2 PTP attribute values 15

All nodes shall support the ranges and shall have the default initialization values for attributes as follows: 16

— portDS.logAnnounceInterval: the value shall be 0. 17

— portDS.logSyncInterval: the value shall be 0. 18

— portDS.announceReceiptTimeout: the value shall be 3. 19

— τ, see IEEE Std 1588-2008 7.6.3.2: the value shall be 1.0 seconds. 20

— portDS.logMinPdelayReqInterval: the default initialization value shall be 0. The configurable 21 range shall be -3 to 5. Delay measurements should be done in bursts with pauses of several 22 seconds. 23

— defaultDS.priority1: the default initialization value shall be 128 for grandmaster-capable devices 24 and 255 for slave-only devices. 25

— defaultDS.priority2: the default initialization value shall be 128 for grandmaster-capable devices 26 and 255 for slave-only devices. 27

— defaultDS.slaveOnly: the default initialization value shall be FALSE for grandmaster-capable 28 devices and TRUE for slave-only devices. 29




— defaultDS.domainNumber: the default initialization value shall be 0. Only one domain is 1 supported by a device at a time. The configurable range shall be as specified by IEEE Std 1588-2 2008 7.1 and Table 2. 3

— transparentClockdefaultDS.primaryDomain: the value shall be 0. Configurable range shall be as 4 specified by IEEE Std 1588-2008 7.1 and Table 2. 5

5.3 Path Delay Mechanism 6

The Peer delay request mechanism of IEEE Std 1588-2008 shall be the only path delay measurement 7 mechanism in operation when this profile is deployed. 8

Path delay measurement and correction for the link to a slave-only IED is optional, if it is not functioning 9 as a TC. Such IEDs shall use Timestamp and CorrectionField value to adjust its clock. 10

5.4 Best Master Clock Algorithm 11

5.4.1 Default best master clock algorithm 12

The master-slave hierarchy shall be determined using the default best master clock algorithm, specified in 13 IEEE Std 1588-2008 9.3.2, 9.3.3, and 9.3.4. 14

All devices except slave-only clocks shall support the full functionality of the default best master clock 15 algorithm. 16

5.4.2 Default settings 17

Default device settings shall be determined by the most likely device function. 18

Unless a device’s primary function is a grandmaster clock, its default configuration shall be slave-only 19 clock. 20

Slave-only clocks: 21

• shall not transmit IEEE C37.238 Announce messages, in order to avoid advertising themselves as 22 potential grandmasters 23

• shall have priority1 and ClockClass values set to 255, IEEE Std 1588-2008 7.6.2.2 and 7.6.2.4. 24

5.5 Management Mechanism 25

All grandmaster-capable devices shall report local time accuracy and traceability to a standard recognized 26 time source. 27

Grandmaster-capable devices shall support SNMP MIB. 28

SNMP support for all other devices is optional. When supported IEEE C37.238 MIB shall be used. 29




All devices that do not support IEEE C37.238 MIB except transparent clocks shall specify whether and 1 how the following information is made available 2

- local time accuracy 3

- traceability to a standard recognized time source 4

- offset from the grandmaster 5

- if the offset from a grandmaster exceeds a configurable limit. 6

NOTE - Refer to Annex C.3, C4 for reporting mechanisms for IEC 61850 and IEEE C37.118 applications. 7

5.5.1 Management Information Base Objects 8

IEEE C37.238 MIB Objects are listed in the Table 1. 9

Table 1— IEEE C37.238 MIB Objects 10

IEEE C37.238 MIB Objects Description N Name IEEE Std 1588 -2008 clause unless otherwise specified R/W

Boundary and Ordinary Clocks Objects 1 ieeeC37238defaultDS 8.2.1 2 TwoStepFlag 8.2.1.2.1 R/W3 ClkIdentity 8.2.1.2.2 R 4 NumberPorts 8.2.1.2.3 R 5 ClkClass 8.2.1.3.1.1 R 6 ClkAccuracy 8.2.1.3.1.2 R 7 OfsScdLogVar 8.2.1.3.1.3 R 8 Priority1 8.2.1.4.1 R/W 9 Priority2 8.2.1.4.2 R/W 10 DomainNumber 8.2.1.4.3 R/W 11 SlaveOnly 8.2.1.4.4 R/W 12 GMIdentity GM identity to be transmitted in GRANDMASTER_ID TLV R/W 13 OfstFrMLimit Offset from Master Limit to generate OfstExceedsLimit event R/W 14 ieeeC37238currentDS 8.2.2 15 StepsRemoved 8.2.2.2 R 16 OfstFrMaster 8.2.2.3 R 17 ieeeC37238parentDS 8.2.3 18 ClkIdentity 8.2.3.2 R 19 PortNumber 8.2.3.2 R 20 Stats 8.2.3.3 R 21 ObsOfstScdLVar 8.2.3.4 R 22 ObsPhChgRate 8.2.3.5 R 23 GMClkIdentity 8.2.3.6 R 24 GMClkClass 8.2.3.7 R 25 GMClkAccuracy 8.2.3.7 R 26 GMOfstScdLVar 8.2.3.7 R 27 GMPriority1 8.2.3.8 R 28 GMPriority2 8.2.3.9 R 29 GMIdentity GM identity received in GRANDMASTER_ID TLV R




30 ieeeC37238timePropDS 8.2.4 31 CurUTCOfst 8.2.4.2 R 32 CurUTCOfstVd 8.2.4.3 R 33 Leap59 8.2.4.4 R 34 Leap61 8.2.4.5 R 35 TmeTraceable 8.2.4.6 R 36 FrqTraceable 8.2.4.7 R 37 PTPTimescale 8.2.4.8 R 38 TimeSource 8.2.4.9 R 39 LocalTCurOfs 16.3.3.4 R/W40 LocalTJumpS 16.3.3.5 R/W41 LocalTNtJump 16.3.3.6 R/W42 LocalTName 16.3.3.7 R/W43 LeapEvLatest The seconds portion of PTP time for the second prior to the latest

IERS-announced leap-second event (may be past or future) R/W

44 UTCOfstNext Seconds offset between TAI and UTC timescales after LeapEvLatest. (same as CurUTCOfst after LeapEvLatest time)

R/W

45 LeapEvExpiry The seconds portion of PTP time for the expiry of the latest IERS-announced leap-second event. If PTP time > LeapEvExpiry, devices shall set CurUTCOfstVd to False.

R/W

46 ieeeC37238portDS 8.2.5 47 ClkIdentity 8.2.5.2.1 R 48 PortNumber 8.2.5.2.1 R 49 PortState 8.2.5.3.1 R 50 MPathDly 8.2.5.3.3 R 51 LogAnnounceInt 8.2.5.4.1 R/W 52 AnnounceRctTout 8.2.5.4.2 R/W 53 LogSyncInt 8.2.5.4.3 R/W 54 DelayMech 8.2.5.4.4 R/W 55 LogMinPdlyRInt 8.2.5.4.5 R/W 56 VersionNumber 8.2.5.4.6 R 57 PortEnabled True if port is enabled. R/W 58 DlyAsymmetry Path delay asymmetry. R/W 59 ProfileId Indicates the PTP Profile in use. R/W 60 NetProtocol Indicates Network Protocol in use. R/W 61 VlanId Port VLAN ID R/W 62 Priority Port Priority R/W

Transparent Clock Objects 63 ieeeC37238TCDefaultDS 8.3.2 64 ClkIdentity 8.3.2.2.1 R 65 NumberPorts 8.3.2.2.2 R 66 DelayMech 8.3.2.3.1 R/W 67 PriDomain 8.3.2.3.2 R/W 68 Syntonize True if syntonization is enabled. R/W 69 CurGMaster Comprises current grandmaster identity. R 70 TwoStepFlag 8.2.1.2.1 R/W 71 GMIdentity GM identity received in GRANDMASTER_ID TLV R 72 NetProtocol Indicates Network Protocol in use. R/W 73 VlanId Port VLAN ID R/W 74 Priority Port Priority R/W 75 ieeeC37238TCPortDS 8.3.3 76 PortNumber 8.3.3.2.1 R




77 LMinPdlyRInt 8.3.3.3.1 R/W 78 Faulty 8.3.3.3.2 R 79 MeanPDly 8.3.3.3.3 R 80 DlyAsymm Path delay asymmetry. R/W

Boundary and Ordinary Clock Objects (Optional for Transparent Clocks) 81 ieeeC37238Events 82 ChangeOfMaster Indicates that new grandmaster has been selected. 83 MasterStepChange Indicates that a step change occurred in current grandmaster time. 84 FaultyState Indicates that a clock has entered faulty state. 85 PortStateChange Indicates that port state has changed. 86 OfstExceedsLimit Indicates that for a clock in a slave state Offset from Master

exceeds configurable limit.

87 OtherProfileDetect Indicates that other PTP profile has been detected 88 LeapSecAnnounced Indicates that a leap second has been announced. 89 PTPServiceStarted Indicates that PTP service has started. 90 PTPServiceStopped Indicates that PTP service has stopped.

5.6 Transport Mechanism 1

The PTP over IEEE 802.3 transport mapping, specified in IEEE Std 1588-2008 Annex F, shall be the 2 default transport mechanism in all IEEE 1588 IEDs devices used in a substation system. 3

All IEEE C37.238 messages shall be mapped into IEEE 802.1Q-tagged Ethernet frames with configurable 4 priority and configurable VLAN ID. Default priority shall be 4. Default VID shall be 0. Full range of 5 priority and VID values shall be supported per [B5]. 6

5.7 Clock Types 7

5.7.1 One-step and two-step clocks 8

All devices’ ingress ports shall support both one-step and two-step modes. 9

All devices’ egress ports may support either one-step or two-step modes. 10

It is recommended that one-step operation would be the only mode of operation supported as it results in a 11 less network traffic, faster possible IEEE C37.238 Sync messages rates, and potentially simpler IED 12 implementations. However, allowing for either one-step or two-step operation in a transparent clock allows 13 for potentially simpler silicon solutions for Ethernet switches and the use of commercially available 14 chipsets. 15

5.7.2 Slave-only clocks 16

IEDs may be designed as slave-only clocks, as specified in IEEE 1588-2008 9.2.2. 17

NOTE—It is recommended that slave-only clocks use the IEEE C37.238 message bytes as described in Annex D. 18 (IEEE C37.238 compliant devices provide all these bytes). 19




5.8 Communication Model 1

The multicast communication model specified in IEEE Std 1588-2008 7.3 shall be used. The multicast 2 MAC addresses shall conform to IEEE Std 1588-2008 Annex F: 01 – 80 – C2 – 00 – 00 – 0E for 3 IEEE C37.238 Pdelay messages and 01 – 1B – 19 – 00 – 00 – 00 for all other IEEE C37.238 messages. 4

5.9 Timescale 5

5.9.1 PTP timescale 6

The timescale of a substation system shall be the PTP timescale, IEEE Std 1588-2008 7.2. 7

5.9.2 Grandmaster clockClass 8

Any clock specifically designed to be the grandmaster clock shall be designed to operate as a clockClass 6 9 clock, IEEE Std 1588-2008 7.6.2.4. 10

5.9.3 Grandmaster clockClass degradation 11

Any clock specifically designed to be the grandmaster clock shall be designed to degrade to a clockClass 7 12 or 187 clock when appropriate, IEEE Std 1588-2008 7.6.2.4. 13

5.9.4 Grandmaster clockAccuracy degradation 14

Any clock specifically designed to be the grandmaster clock shall be designed to degrade its clockAccuracy 15 when appropriate (e.g. when in holdover), IEEE Std 1588-2008 7.6.2.5. 16

5.9.5 Grandmaster timescale 17

All ordinary and boundary clocks in a substation system shall be designed to support the PTP timescale in 18 the event they become the grandmaster. 19

5.9.6 Grandmaster ID 20

Grandmaster clocks shall have a configurable 1-byte ID. Grandmaster ID shall be communicated using 21 profile specific GRANDMASTER_ID TLV, defined in 5.12.2. 22

5.10 Clause 16 and 17 Annex K and L Options 23

From the options specified in IEEE Std 1588-2008 16, 17, Annex K and Annex L only 24 ALTERNATE_TIME_OFFSET_INDICATOR TLV is required 25




5.11 clockIdentity 1

clockIdentity values, IEEE Std 1588-2008 7.5.2.2, shall be EUI-64 constructed based on EUI-48. 2

5.12 TLVs 3

5.12.1 IEEE Std 1588-2008 TLVs 4

The following TLV defined in IEEE Std 1588-2008 14 shall be supported by all devices: 5

• ALTERNATE_TIME_OFFSET_INDICATOR TLV (IEEE Std 1588-2008 16.3) for determining Local 6 time 7

• ORGANIZATION_EXTENSION (IEEE Std 1588-2008 14.3), as defined in 5.12.2. 8

These TLVs shall be appended to IEEE C37.238 Announce messages. 9 10 The order of the mandatory TLVs shall be as follows: 11

‐ ALTERNATE_TIME_OFFSET_INDICATOR TLV 12 ‐ ORGANIZATION_EXTENSION (GRANDMASTER_ID TLV) 13

Additional (non-IEEE C37.238) TLVs if supported shall follow the mandatory TLVs. 14

5.12.2 Profile specific TLVs 15

The following profile specific TLV shall be supported: 16

• GRANDMASTER_ID TLV 17

This TLV shall be used to communicate the current Grandmaster ID. The dataField is user configurable. 18

The implementation of this TLV shall conform to the terms of IEEE Std 1588-2008 14.3. 19

The GRANDMASTER_ID TLV field values shall be as follows: 20

• tlvType (Enumeration16); ORGANIZATION_EXTENSION value = 0003 hex 21

• lengthField (UInteger16) value = 0008 hex. The number of octets in the dataField 22

• organizationId (Octet[3]); The OUI value assigned by IEEE RAC = 1C129D hex 23

• organizationSubType (Enumeration24) value = 000001hex 24

• dataField (2 octets) value 0003-00FE hex, most significant byte is reserved and shall be 0. 25

The GRANDMASTER_ID TLV shall not be sent until the grandmaster clock has been assigned a unique 26 GRANDMASTER_ID. 27




Annex A 1

(informative) 2

Operating modes 3

A.1 Overview 4

This profile for use of IEEE 1588 precision time protocol (PTP) in power system applications describes a 5 robust, Ethernet based method for precise clock synchronization. Although optimized for stringent timing 6 applications, it is versatile enough to allow simple implementations while retaining good balance between 7 time precision and the complexity of implementation. 8

Substation applications can be broadly divided into following categories: 9

1. General purpose, visually observed time indicators (< +/-100 ms) 10

2. Time stamping of SCADA data and operational data logs (< +/-1 ms) 11

3. IRIG-B replacement applications with limited distance to the PTP grandmaster (< +/-1 µs) 12

4. Extended distance applications (full PTP support, < +/-1 µs) 13

First three categories operate as simple slaves and are not allowed to participate in the BMC election 14 process. They are located at the network edge (last device), and cannot pass traffic to others, meaning they 15 are not required to support transparent clock functionality. Devices in the first three categories are expected 16 to process IEEE C37.238 Sync, Follow_Up and Announce messages, but do not need to support Pdelay 17 exchange or transmit IEEE C37.238 Pdelay messages. They process all IEEE C37.238 Sync message fields 18 (including correctionField), support one-step and two-step operation (with and without Follow_Up), and 19 correctly process the leap second events, as specified in Annex D. 20

A.2 Description 21

Category 1 devices typically target general purpose processors, and do not require PTP specific hardware. 22 Although some evaluation of the software stack delays may be required, this category does not generally 23 need specialized software techniques. Software stack needs to be capable of receiving and analyzing layer 2 24 messages. 25

Category 2 devices may target general purpose processors and do not necessarily require PTP specific 26 hardware. Due to additional precision requirements, this implementation may need to use interrupts, or 27 careful / customized software implementation. While it may be possible to use general purpose software 28 stack, some optimization is likely to be required. 29

Category 3 devices are intended for direct replacement of IRIG-B (pulse per second) distribution networks 30 in which the distance between the last PTP source (PTP grandmaster, boundary clock or transparent clock) 31 and the category 3 slave does not exceeding 100m (propagation delay < 0.5 µs). It is intended to replicate 32 current applications which do not explicitly compensate IRIG cable length. Category 3 devices may target 33 general purpose microprocessors, but require PTP specific hardware support (hardware based 34 timestamping). With exception of not measuring the length of the last cable / fiber segment (not supporting 35 IEEE C37.238 Pdelay message exchange), in all other aspects, Category 3 devices are expected to emulate 36 the Category 4 slave behavior. 37




Category 4 devices support full implementation of this profile. They require hardware assisted 1 timestamping, and participate in the IEEE C37.238 Pdelay message exchange. Category 4 devices may be 2 placed anywhere in the network. 3

4




Annex B 1

(normative) 2

Time performance requirements 3

This Annex specifies performance requirements for the devices and networks providing time distribution 4 service to the end devices. These devices include grandmaster clocks, transparent clocks and ordinary 5 clocks that are part of the PTP communication path. Performance requirements for the end devices are 6 application dependent and are out of scope of this Annex. 7

Network devices shall be able to distribute time from a grandmaster clock to the end devices over 16 8 network hops. Time accuracy available at the end devices shall be +/- 1 µs with 10-4 out-of-spec probability 9 [B1]. This shall apply for network loads up to 80% wire-speed. Random-length Ethernet frames shall be 10 used: 80% with priority 4 and 20% with lower priority. 11

Maximum time error introduced by grandmaster clocks compliant to IEEE C37.238 shall be 0.2 µs. 12

NOTE—Grandmaster clocks with time accuracy that exceeds 0.2 µs may be used for shorter PTP communication paths 13 (less than 16 network hops), if the max time error accumulated in the communication path is less than 1 µs. 14

Maximum time error introduced by transparent clocks compliant to IEEE C37.238 shall be 50 ns. 15

Holdover drift of grandmaster-capable devices shall be within 2 µs for up to 5 seconds at a constant 16 temperature. 17

The time it takes a device to report its status and start IEEE C37.238 associated stack and processes on 18 start-up shall be specified by the manufacturer. 19




Annex C 1

(informative) 2

Time performance parameters and their use for IEC 61850 and 3

IEEE C37.118 applications 4

This Annex describes 5

- IEEE C37.238 time performance parameters 6

- Time performance parameters mapping into IEEE C37.238 management MIB 7

- Use of time performance parameters for IEC 61850 and IEEE C37.118 applications 8

- IEC 61850 Logical Node for switch function and IEEE C37.238 9

C.1 Time performance parameters 10

Power substation applications require accurate time synchronization and time quality information for 11 phasor estimations relative to UTC time, sample synchronization, event time stamping, and other functions. 12

Time quality information generally includes 13

- local clock accuracy, and 14

- traceability to a recognized standard time source. 15

Grandmaster time accuracy is transmitted in the clockAccuracy parameter of the grandmasterClockQuality 16 field of the IEEE C37.238 Announce message, IEEE Std 1588-2008 13.5 and Table 25. Local clock uses 17 received grandmaster accuracy and internal knowledge of its own accuracy to determine local 18 clockAccuracy. 19

Supported values and encoding for clockAccuracy parameter as provided in Tables C1 and C3. 20

Grandmaster clocks normally interact with a primary reference, such as GPS, by a means that is outside this 21 standard. Traceability to a recognized standard time source, such as GPS, is indicated by grandmaster 22 clocks in the timeTraceable bit of the flagField located in the IEEE C37.238 Announce message. This flag 23 lets other clocks know whether the grandmaster is traceable to a recognized time source. 24

In addition, grandmaster ID parameter is provided in IEEE C37.238 GRANDMASTER_ID TLV for 25 grandmaster identification, particularly useful during transitions to a new grandmaster. 26

Currently selected grandmaster clockAccuracy and local clockAccuracy, as well as timeTraceable flag are 27 provided in the IEEE C37.238 management MIB for status reporting, see Table 1 and Annex F. 28

IEEE C37.238 time performance parameters also have to be mapped into application specific parameters. 29 Their use for IEC 61850 and IEEE C37.118 applications is described in C.3 and C.4. 30




More detailed information regarding clock performance can be obtained from PTP datasets. Boundary, 1 ordinary, and transparent clocks are required to support specific datasets, IEEE Std 1588-2008 subcause 8. 2 If these clocks also support another protocol, such as DNP3 or Modbus, they may also support the mapping 3 of the data available from the either the clock data sets or transparent clock data sets to provide that data via 4 that supported protocol. Mapping of these values is outside the scope of this standard. Another option 5 outside the scope of this standard is to use a data concentrator that supports SNMP and use the data 6 concentrator to map the IEEE C37.238 management MIB data to another protocol, provided that the 7 management MIB supports all of the required datasets. 8 9 Slave clocks may need to track the performance of their parent in order to determine whether the parent's 10 signal is a valid signal, IEEE Std 1588-2008 A.4. Remote substations utilizing PTP may be subject to 11 grandmaster clock failure when time or frequency can become incorrect, plus deliberate effects such as 12 GPS spoofing that substitutes the real GPS signals with other signals. Mechanisms to provide this 13 performance monitoring may be considered in a future revision of the IEEE C37.238 standard. 14

C.2 Use of IEEE C37.238 MIB for time performance parameters 15

Local clock time accuracy and traceability to a standard recognized time source are available in the 16 IEEE C37.238 MIB as specified in Table 1 and Annex F. 17

Grandmaster clockAccuracy is available as ieeeC37238ParentDSGrandmasterClockAccuracy, object 8 of 18 the Parent dataset ieeeC37238ParentDS. 19

Local clockAccuracy is available as ieeeC37238DefaultDSClockAccuracy, object 5 in the Default dataset 20 ieeeC37238DefaultDS. 21

timeTraceable flag is available as ieeeC37238DefaultDSTimeTraceable, object 5 in the Time Properties 22 dataset ieeeC37238DefaultDS. 23

Currently selected grandmaster identity is communicated via GRANDMASTER_ID TLV and is available 24 in the IEEE C37.238 management MIB object GMIdentity, object 11 in the Default dataset 25 ieeeC37238DefaultDS and object 8 in the transparent clock default dataset ieeeC37238TCDefaultDS. 26

C.3 Use of IEEE C37.238 for IEC 61850 applications 27

IEC 61850 standard specifies TimeStamp type for time stamping all data provided by IEDs and SmpSynch 28 parameter for time quality information for the sampled value service [B2, B3]. 29

C.3.1 IED data time stamping 30

The IEC 61850 TimeStamp represents a UTC time with the epoch of midnight (00:00:00) of 1970-01-01 31 [B2]. 32

IEC 61850 TimeAccuracy attribute defines the number of significant bits in the FractionOfSecond, n, of the 33 IEC 61850 TimeStamp, based on clock time accuracy information. 34

IEEE C37.238 local clockAccuracy provides information for determining IEC 61850 TimeAccuracy value. 35

Mapping between the IEC 61850 TimeAccuracy and IEEE C37.238 local clockAccuracy is shown in 36 Table C1. 37




Table C.1— Mapping between IEEE C37.238 local clockAccuracy and IEC 61850 1 TimeAccuracy 2

IEEE C37.238 local clockAccuracy IEC 61850-7-2 TimeAccuracy Value,

hex Description n,

hex Time Accuracy

(2**n) Time performance class defined in IEC 61850-5

00-1F

2C-FF

reserved

unused, reserved for alternate PTP profiles

1F - unspecified

2A-2B The time is accurate to within 2.5 -10 ms 7 approx. 7.8 ms 10 ms (performance class T0)

28-29 The time is accurate to within 250 s -1 ms A approx. 0.9 ms 1 ms (performance class T1)

27 The time is accurate to within 100 s E approx. 61 s 100 s (performance class T2

25-26 The time is accurate to within 10 - 25 s 10 approx. 15 s 25 s (performance class T3)

24 The time is accurate to within 2.5 s 12 approx. 3.8 s 4 s (performance class T4)

20-23 The time is accurate to within 25ns -1 s 14 approx. 0.9 s 1 s (performance class T5)

C.3.2 Sampled Value service 3

IEC 61850 SmpSynch contains time quality information for the sampled value service [B3]. 4

IEEE C37.238 timeTraceable flag corresponds to IEC 61850 reporting in SmpSynch that SV are 5 synchronized by a global area clock. 6

IEEE C37.238 Grandmaster ID should be used in IEC 61850 SmpSynch to report what local area clock the 7 SV are synchronized to. 8

C.3.3 IEC 61850 Logical Node for switch function and IEEE C37.238 9

Future edition of the IEC 61850 standard may include a part on Logical Node (LN) for switch function. 10 The intention is to create a data model with a dedicated LN for the switch function which could include the 11 IEEE C37.238. The impact of adding such IEC 61850 LN cannot be integrated yet, and may be considered 12 in a future revision of the IEEE C37.238 standard. 13

C.4 Use of IEEE C37.238 for IEEE C37.118 applications 14

IEEE C37.118 Synchrophasor applications require information on time quality and traceability to a 15 recognized standard time source, e.g. UTC [B6]. 16

IEEE C37.238 provides time quality and traceability via local clockAccuracy and timeTraceable flag as 17 listed in C.1. 18

timeTraceable flag maps directly into bit[13] of the STAT in the Synchrophasor Data frame. This bit is set 19 if provided time is traceable to UTC. 20




Mapping between the IEEE C37.118 Time Quality nibble and IEEE C37.238 clockAccuracy is shown in 1 Table C3. 2

Table C.2— Mapping between IEEE C37.238 clockAccuracy and IEEE C37.118 Time Quality 3

IEEE C37.238 clockAccuracy IEEE C37.118 Time Quality nibble Value,

hex Description

Value,

hex Description

(worst case accuracy) 00-1F,

31-FF

Reserved

The time is accurate to >10 s, reserved for profile use

F Fault--clock failure, time not reliable

30 The time is accurate to within 10 s B 1 s ≤ time < 10 s

2E, 2F The time is accurate to within 250 ms - 1 s A 100 ms ≤ time < 1 s

2C, 2D The time is accurate to within 25 - 100 ms 9 10 ms ≤ time < 100 ms

2A, 2B The time is accurate to within 2.5 ms - 10 ms 8 1 ms ≤ time < 10 ms

28, 29 The time is accurate to within 250 s - 1 ms 7 100 μs ≤ time < 1 ms

26, 27 The time is accurate to within 25 - 100 s 6 10 μs ≤ time < 100 μs

24, 25 The time is accurate to within 2.5 - 10 s 5 1 μs ≤ time < 10 μs

22, 23 The time is accurate to within 250 ns - 1 s 4 100 ns ≤ time < 1 μs

20, 21 The time is accurate to within 25 - 100 ns 3 10 ns ≤ time < 100 ns

- Not specified 2 1 ns ≤ time < 10 ns

- Not specified 1 time < 1 ns

- Not specified 0 reserved

4




Annex D 1

(informative) 2

Use of IEEE C37.238 messages for Slave-Only clocks (IRIG-B replacement) 3

It is recommended that slave-only clocks use the IEEE C37.238 message bytes as described below. (IEEE 4 C37.238 compliant devices provide all these bytes). 5

NOTE—For this annex, a frame’s bytes’ positions are designated by the integer Bn, with n starts at 0 for the byte after 6 the frame’s Ether Type field. 7

D.1 Use of received IEEE C37.238 Sync and Follow_Up messages to obtain a PTP 8 Time 9

IEEE C37.238 Sync messages are Ethernet frames with: 10

a. A Destination MAC Address of 01-1B-19-00-00-00 11

b. An EtherType field of 88F716 12

c. B0 = 0016 (identifier for IEEE C37.238 Sync messages) 13

d. B2, B3 = 4410 (indicates the message has 44 bytes). 14

If B6[1]=0 the PTP Timestamp (the time when the IEEE C37.238 Sync message entered the link cable, as 15 the number of seconds since the start of 1970) comprises the sum of the following three fields of the 16 IEEE C37.238 Sync message: 17

- The 48-bit unsigned-integer B34 through B39 (in seconds), this is the originTimestamp's 48 most-18 significant bits. 19

- The 32-bit unsigned-integer B40 through B43 (in nanoseconds), this is the originTimestamp's 32 least-20 significant bits. 21

- The 64-bit signed-integer B8 through B15 (in 2-16 nanoseconds), this is the 64-bit correctionField. 22

If B6[1]=1 the PTP Time (the time when the IEEE C37.238 Sync message entered the link cable, as the 23 number of seconds since the start of 1970) comprises the sum of the IEEE C37.238 Sync message’s 64-bit 24 correctionField B8 through B15 (in 2-16 nanoseconds), plus the following three fields of the next received 25 IEEE C37.238 Follow_Up message (same bytes except B0 = 0816): 26

- The 48-bit unsigned-integer B34 through B39 (in seconds). 27

- The 32-bit unsigned-integer B40 through B43 (in nanoseconds). 28

- The 64-bit signed-integer B8 through B15 (in 2-16 nanoseconds). 29




D.2 Use of received IEEE C37.238 Announce messages to determine UTC time and 1 Local time 2

NOTE—Each IEEE C37.238 Announce message comprises an IEEE Std 1588-2008 Announce message, extended 3 using an IEEE Std 1588-2008 ALTERNATE_TIME_OFFSET_INDICATOR TLV (for local time), followed by an 4 ORGANIZATION_EXTENSION TLV (for GRANDMASTER_ID). 5

IEEE C37.238 Announce messages are Ethernet frames with: 6

(a) A Destination MAC Address of 01-1B-19-00-00-00 7

(b) An EtherType field of 88F716 8

(c) B0 = 0B16 (identifier for IEEE C37.238 Announce messages) 9

(d) B2, B3 = 10810 (indicates the message has 108 bytes). 10

D.2.1 Determining UTC time 11

The frame’s bytes B44B45 have the number of seconds to be subtracted (from the PTP Timestamp) to get 12 UTC time. 13

If the frame’s byte B7[2] is set, the above shall be considered invalid. 14

D.2.2 Determining future leap-second adjustments to UTC time 15

If the frame’s byte B7[0] is set, the last minute of the current UTC day will have 61 seconds. 16

If the frame’s byte B7[1] is set, the last minute of the current UTC day will have 59 seconds. 17

D.2.3 Determining Local time 18

Check that bytes B64B65 = ‘000916’ (flags the IEEE Std 1588-2008 TLV for Local time). 19

Check that bytes B66B67 = ‘001C16’ (for a fixed-length (32 bytes) TLV). 20

Ignore B68 21

The signed 32-bit field currentOffset comprising B69 through B72 is added to the UTC time to get Local 22 time. 23

D.2.4 Determining Daylight-time events 24

A non-zero signed-32-bit field jumpSeconds comprising B73 through B76 indicates that when the PTP 25 seconds-field becomes the unsigned-48-bit field timeOfNextJump comprising B77 through B82, the 26 currentOffset is incremented by jumpSeconds. 27

NOTE—To tolerate the network delay of IEEE C37.238 Announce messages, since the currentOffset field may be 28 incorrect this field should be ignored for a few seconds after an event. 29




D.2.5 Determining Name of Local Time 1

Bytes B83 up to B94 encode the name of the local time (e.g. “PDST”) using 16-bit ASCII which is the Basic 2 Latin block specified by ISO/IEC 10646 [B8] for UTF-8 (to conform with IEEE Std 1588-2008). 3

If the number of characters is less than 6 (the maximum), the unused bytes are set to ‘0016’. 4

Reference: http://www.cs.tut.fi/~jkorpela/ucs.html8 5

Examples of UTF-8 codes are given in Table D1. 6

Table D.1— Examples of UTF-8 codes 7

8

9 10

The last IEEE C37.238 Announce message byte, B95, are set to ‘0016’. 11

D.3 Use of received IEEE C37.238 Announce messages to determine the time’s 12 quality 13

D.3.1 Valid-Time flags 14

Check that the frame’s B7[3] bit is set (denotes timescale is PTP) 15

Check that the frame’s B7[4] bit is set (denotes that time is traceable to a recognized standard time source, 16 e.g. GPS signal is present) 17

D.3.2 Time Accuracy 18

B49 provides some information on the accuracy of the received time, e.g. 2316 for 1us, 2516 for 10us, 2916 for 19 1ms. See the Annex C for the mapping table, and refer to the IEEE C37.118-2005 Synchrophasor standard 20 and to the IEEE Std 1588-2008 for the full accuracy encoding tables. 21




D.3.3 Determining the Grandmaster clock sourcing the time 1

Check that bytes B96B97 = ‘000316’ (flags the IEEE C37.238 TLV for GRANDMASTER_ID). 2

Check that bytes B98B99 = ‘000816’ (for a fixed-length (8 bytes) TLV). 3

Check that bytes B100B101B102 = ‘1C129D24’ (OUI from IEEE for IEEE C37.238). 4

Check that bytes B103B104B105 = ‘00000124’ 5

Ignore B106 6

Use B107 to identify the Grandmaster clock sourcing the received PTP time. 7




Annex E 1

(informative) 2

Use of IEEE C37.238 for IEC 62439-3 3

E.1 Overview 4

This annex specifies the mapping of the IEEE C37.238 time distribution to the protocols defined by 5 IEC 62439-3, namely Parallel Redundancy Protocol (PRP) and High-availability Seamless Redundancy 6 (HSR) [B4]. PRP is a redundant protocol applied to devices connected to two independent and parallel 7 Local Area Networks (LANs). HSR is a ring redundancy protocol. Both protocols are based on data 8 duplication on each link and simultaneous sending of the information to provide seamless recovery, i.e. 9 zero recovery time, in case of a single failure of an inter-switch link or a switch in the network. 10

E.2 PRP Mapping 11

A double attached node implementing PRP, (DANP) implements an ordinary clock with the property that 12 both ports of the DANP are handled as a single aggregated port. This implies only one port state machine 13 and both ports always have the same state. 14

A Grandmaster should always be attached to a RedBox or natively support the PRP protocol by duplicating 15 the sending of all its IEEE C37.238 messages over both paths. 16

NOTE 1—Grandmaster time stamp logic over PRP should be adjusted correctly. For example single IEEE C37.238 17 Sync message from PTP stack will results in 2 timestamp events (one per PRP port). If PRP supports two-step clock 18 then DANP nodes must be port aware and correlate IEEE C37.238 Sync and Follow_Up messages on the same port. 19

A PRP redundancy box (RedBox) implements either: 20

• a peer-to-peer transparent clock and may include an ordinary clock if the local applications require 21 synchronization 22

• a boundary clock with the non-redundant port being the master port and the two other redundant ports 23 are slave ports, or vice versa. 24

NOTE 2—In a cascaded network, e.g., a network made of multiple RedBoxes in series, the peer-to-peer transparent 25 clock implementation should be preferred in order to avoid the cumulative effect of cascading servo loops implemented 26 by each boundary clock. 27

All IEEE C37.238 messages, except Pdelay messages, i.e. Pdelay_Req, Pdelay_Resp, Pdelay_Follow_Up, 28 need to include the PRP Redundancy Control Trailer (RCT) four-octet field at the end of the frame. This 29 trailer shall not be removed by the transparent clocks in the redundant networks. The source address given 30 by the PTP grandmaster shall not be changed. These rules imply that there are no boundary clocks in the 31 redundant networks unless the boundary clock is connected to the two PRP links. 32

IEEE C37.238 Pdelay messages do not follow the PRP rules, i.e. no duplicate sending and no discarding at 33 the receiver side, and are dedicated to one specific link between two devices. 34

One-step or two-step clocks can be implemented on PRP. It is however recommended to implement a 35 homogeneous PRP network, i.e. either one-step or two-step clock but not a mix of both. 36




Figure E.1 illustrates the different IEEE C37.238 messages on a typical PRP network with the Grandmaster 1 connected to the PRP network through a RedBox. 2

3 Figure E.1—IEEE C37.238 messages in PRP network 4

E.3 HSR Mapping 5

All HSR devices are hybrid clocks, made of at least of a transparent clock and an ordinary clock. The 6 ordinary clock is either in the grandmaster, slave or slave-only mode. All HSR devices do not require to be 7 synchronized but need to be syntonized if the maximum cumulative error of all devices’ residence time 8 exceeds 1 microsecond. As an example, a HSR ring made of 50 HSR nodes, each with a 100ppm clock, has 9 a maximum cumulated error of 0.6 microseconds, assuming a 100 Mbits/sec network and a maximum 10 frame length of 1542 octets (frame length and inter frame gap). 11

One-step clock mode is the preferred mode for all devices involved in an HSR network. 12 Both ports of a device belonging to the same HSR network are in the same state, i.e. either slave or 13 grandmaster. 14

All devices within the ring have to be HSR-capable. 15

If an HSR node is also connected to a network outside the ring, i.e. a RedBox, the HSR node can 16 implement a boundary clock or a transparent clock between the two HSR ports and the outside port. The 17 outside port can be either slave or grandmaster, and can implement either a one-step or two-step clock. 18




IEEE C37.238 Pdelay messages are exchanged by all devices in a HSR network, even by the slave-only 1 devices. The IEEE C37.238 Pdelay messages do not follow the HSR rules, and are only exchanged between 2 two devices directly connected. Therefore, IEEE C37.238 Pdelay messages do not contain any HSR tag. 3 Upon reception of a IEEE C37.238 Pdelay_Req or a Pdelay_Resp message, the HSR device does not 4 forward the message to its other HSR ports, but may forward it to its host port. 5

All IEEE C37.238 messages, except Pdelay messages, are following the HSR rules and handled like any 6 other HSR traffic. 7

In addition to the IEEE Std 1588-2008 Ethertype, all IEEE C37.238 messages, except Pdelay messages, 8 have the HSR Ethertype, 0x88FB, in the HSR tag. 9

Figure E.2 illustrates the paths of the different IEEE C37.238 messages in a HSR ring network. 10

11 Figure E.2—IEEE C37.238 messages in HSR ring network 12




Annex F 1

(normative) 2

Management Information Base 3

IEEEC37-238-MIB DEFINITIONS ::= BEGIN 4 --===================================================================== 5 -- MIB for support of IEEE C37.238 Standard Profile for Use of 6 -- IEEE 1588 Precision Time Protocol in Power System Applications 7 --===================================================================== 8 IMPORTS 9 10 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32, 11 Integer32 12 FROM SNMPv2-SMI -- [RFC2578] 13 TEXTUAL-CONVENTION, TruthValue 14 FROM SNMPv2-TC -- [RFC2579] 15 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP -- [RFC2580] 16 FROM SNMPv2-CONF 17 ifGeneralInformationGroup 18 FROM IF-MIB; -- [RFC2863] 19 20 ieeeC37238TSMib MODULE-IDENTITY 21 LAST-UPDATED "201009150000Z" -- Sept 15, 2010 22 ORGANIZATION "IEEE PSRC / SUB Working Group H7/SubC7" 23 CONTACT-INFO 24 "WG-URL: http://www.pes-psrc.org/h/ 25 WG-EMail: 26 Contact: Galina S. Antonova 27 Postal: 600-3731 North Fraser Way 28 Burnaby, BC V5J 5J2 Canada 29 E-mail: [email protected]" 30 31 DESCRIPTION 32 "The Management Information Base module for 33 IEEE C37.238 time synchronization protocol." 34 35 REVISION "201009150000Z" -- Sept 15, 2010 36 DESCRIPTION 37 "Published as part of IEEE PC37.238 Draft D5.5 38 Copyright (C) IEEE (2010)." 39 40 -- IEEE C37.238 MIB info. 41 ::= { iso(1) org(3) ieee(111) standards-association-c-series-42 standards (3) std-c37 (37) part238 (238) 9999 } 43 44 ieeeC37238Notifications OBJECT IDENTIFIER ::= { ieeeC37238TSMib 0 } 45 ieeeC37238Objects OBJECT IDENTIFIER ::= { ieeeC37238TSMib 1 } 46 ieeeC37238Conformance OBJECT IDENTIFIER ::= { ieeeC37238TSMib 2 } 47 48 --===================================================================== 49 -- Textual Conventions 50 --===================================================================== 51




ClockIdentity ::= TEXTUAL-CONVENTION 1 DISPLAY-HINT 2 "1x:" 3 STATUS current 4 DESCRIPTION 5 "IEEE 802 MAC address represented in the `canonical' order, 6 EUI-64. EUI-48 converts to EUI-64 as specified by IEEE." 7 REFERENCE "IEEE Std 1588-2008 5.3.4 and 7.5.2.2" 8 SYNTAX OCTET STRING (SIZE (8)) 9 10 IEEEC37238ClockClassValue ::= TEXTUAL-CONVENTION 11 STATUS current 12 DESCRIPTION 13 "Clock Class Value from IEEE Std 1588-2008 7.6.2.4, with the 14 following interpretation placed on the value: 15 6: A clock that is synchronized to a primary reference 16 time source, 17 7: A clock that has previously been designated as clockClass 18 6 but that has lost the ability to synchronize to primary 19 reference time source and is in holdover mode and within 20 holdover specifications, 21 13: A clock that is synchronized to an application-specific 22 source of time, 23 14: A clock that has previously been designated as clockClass13 24 but that has lost the ability to synchronize to an 25 application-specific source of time and is in holdover mode 26 and within holdover specifications, 27 52: Degradation alternative A for a clock of clockClass 7 that 28 is not within holdover specification, 29 58: Degradation alternative A for a clock of clockClass 14 that 30 is not within holdover specification, 31 68..122: For use by alternate PTP profiles (68..122), 32 133..170: For use by alternate PTP profiles (133..170), 33 187: Degradation alternative B for a clock of clockClass 7 that 34 is not within holdover specification, 35 193: Degradation alternative B for a clock of clockClass 14 that 36 is not within holdover specification, 37 216..232: For use by alternate PTP profiles, 38 248: Default none of the other clockClass definitions apply, 39 255: A slave-only clock(255)." 40 REFERENCE "IEEE Std 1588-2008 7.6.2.4" 41 SYNTAX INTEGER { 42 primarySync(6), 43 primarySyncLost(7), 44 applicationSpecificSync(13), 45 applicationSpecficSyncLost(14), 46 primarySyncAlternativeA(52), 47 applicationSpecificAlternativeA(58), 48 primarySyncAlternativeB(187), 49 applicationSpecficAlternativeB(193), 50 default(248), 51 slaveOnlyClock(255) 52 } 53 54 IEEEC37238ClockAccuracyValue ::= TEXTUAL-CONVENTION 55 STATUS current 56 DESCRIPTION 57




"Clock Accuracy Value from IEEE Std 1588-2008 8.6.2.3, with the 1 following interpretation placed on the value: 2 32: The time is accurate to within 25 ns, 3 33: The time is accurate to within 100 ns, 4 34: The time is accurate to within 250 ns, 5 35: The time is accurate to within 1 us, 6 36: The time is accurate to within 2.5 us, 7 37: The time is accurate to within 10 us, 8 38: The time is accurate to within 25 us, 9 39: The time is accurate to within 100 us, 10 40: The time is accurate to within 250 us, 11 41: The time is accurate to within 1 ms, 12 42: The time is accurate to within 2.5 ms, 13 43: The time is accurate to within 10 ms, 14 44: The time is accurate to within 25 ms, 15 45: The time is accurate to within 100 ms, 16 46: The time is accurate to within 250 ms, 17 47: The time is accurate to within 1 s, 18 48: The time is accurate to within 10 s, 19 49: The time is accurate to within > 10 s, 20 254: Default indicating unknown" 21 REFERENCE "IEEE Std 1588-2008 7.6.2.5 and Table 6" 22 SYNTAX INTEGER { 23 timeAccurateTo25ns(32), 24 timeAccurateTo100ns(33), 25 timeAccurateTo250ns(34), 26 timeAccurateTo1us(35), 27 timeAccurateTo2to5us(36), 28 timeAccurateTo10us(37), 29 timeAccurateTo25us(38), 30 timeAccurateTo100us(39), 31 timeAccurateTo250us(40), 32 timeAccurateTo1ms(41), 33 timeAccurateTo2to5ms(42), 34 timeAccurateTo10ms(43), 35 timeAccurateTo25ms(44), 36 timeAccurateTo100ms(45), 37 timeAccurateTo250ms(46), 38 timeAccurateTo1s(47), 39 timeAccurateTo10s(48), 40 timeAccurateToGT10s(49), 41 timeAccurateToUnknown(254) 42 } 43 44 IEEEC37238TimeSourceValue ::= TEXTUAL-CONVENTION 45 STATUS current 46 DESCRIPTION 47 "The timeSource is an information only attribute indicating 48 the type of source of time used by a grandmaster clock. 49 The following value are defined: 50 16: Atomic Clock, 51 32: GPS, 52 48: Terrestrial Radio, 53 64: PTP, 54 80: NTP, 55 96: Hand Set, 56 144: Other, 57




160: Internal Oscillator" 1 REFERENCE "IEEE Std 1588-2008 7.6.2.6 and Table 7" 2 SYNTAX INTEGER { 3 atomicClock(16), 4 gps(32), 5 terrestrialRadio(48), 6 ptp(64), 7 ntp(80), 8 handSet(96), 9 other(144), 10 internalOscillator(160) 11 } 12 13 Integer48 ::= TEXTUAL-CONVENTION 14 DISPLAY-HINT "12d" 15 STATUS current 16 DESCRIPTION 17 "48bit Integer value" 18 SYNTAX OCTET STRING (SIZE (6)) 19 20 --===================================================================== 21 -- Subtrees in the IEEEC37-238-MIB IEEE C37.238 system Parameters 22 --===================================================================== 23 24 --===================================================================== 25 -- The Default data set represents native time capability of a IEEE 26 -- C37.238 system 27 --===================================================================== 28 29 ieeeC37238DefaultDS OBJECT IDENTIFIER ::= { ieeeC37238Objects 1 } 30 31 ieeeC37238DefaultDSTwoStepFlag OBJECT-TYPE 32 SYNTAX TruthValue 33 MAX-ACCESS read-write 34 STATUS current 35 DESCRIPTION 36 "True if the clock is a two-step clock, False otherwise." 37 REFERENCE "IEEE Std 1588-2008 8.2.1.2.1" 38 ::= { ieeeC37238DefaultDS 1 } 39 40 ieeeC37238DefaultDSClkIdentity OBJECT-TYPE 41 SYNTAX ClockIdentity 42 MAX-ACCESS read-only 43 STATUS current 44 DESCRIPTION 45 "ClockIdentity of the local clock" 46 REFERENCE "IEEE Std 1588-2008 7.6.2.1 and 8.2.1.2.2" 47 ::= { ieeeC37238DefaultDS 2 } 48 49 ieeeC37238DefaultDSNumberPorts OBJECT-TYPE 50 SYNTAX Unsigned32(0..255) 51 MAX-ACCESS read-only 52 STATUS current 53 DESCRIPTION 54 "The number of PTP ports on the device. For an ordinary clock, 55 this value shall be 1." 56 REFERENCE "IEEE Std 1588-2008 8.2.1.2.3" 57




::= { ieeeC37238DefaultDS 3 } 1 2 ieeeC37238DefaultDSClkClass OBJECT-TYPE 3 SYNTAX IEEEC37238ClockClassValue 4 MAX-ACCESS read-only 5 STATUS current 6 DESCRIPTION 7 "ClockClass of the local clock." 8 REFERENCE "IEEE Std 1588-2008 7.6.2.4 and 8.2.1.3.1" 9 ::= { ieeeC37238DefaultDS 4 } 10 11 ieeeC37238DefaultDSClkAccuracy OBJECT-TYPE 12 SYNTAX IEEEC37238ClockAccuracyValue 13 MAX-ACCESS read-only 14 STATUS current 15 DESCRIPTION 16 "ClockAccuracy of the local clock." 17 REFERENCE "IEEE Std 1588-2008 8.2.1.3.1.2" 18 ::= { ieeeC37238DefaultDS 5 } 19 20 ieeeC37238DefaultDSOfsScdLogVar OBJECT-TYPE 21 SYNTAX Integer32(-32768..32767) 22 23 MAX-ACCESS read-only 24 STATUS current 25 DESCRIPTION 26 "The value is scaled, offset representation of an estimate of the 27 PTP variance. The PTP variance characterizes the precision and 28 frequency stability of the grandmaster clock." 29 REFERENCE "IEEE Std 1588-2008 8.2.1.3.1.3" 30 ::= { ieeeC37238DefaultDS 6 } 31 32 ieeeC37238DefaultDSPriority1 OBJECT-TYPE 33 SYNTAX Unsigned32(0..255) 34 MAX-ACCESS read-write 35 STATUS current 36 DESCRIPTION 37 "Priority1 attribute of the local clock." 38 REFERENCE "IEEE Std 1588-2008 7.6.2.2 and 8.2.1.4.1" 39 ::= { ieeeC37238DefaultDS 7 } 40 41 ieeeC37238DefaultDSPriority2 OBJECT-TYPE 42 SYNTAX Unsigned32 43 MAX-ACCESS read-write 44 STATUS current 45 DESCRIPTION 46 "Priority2 attribute of the local clock." 47 REFERENCE "IEEE Std 1588-2008 7.6.2.3 and 8.2.1.4.2" 48 ::= { ieeeC37238DefaultDS 8 } 49 ieeeC37238DefaultDSDomainNumber OBJECT-TYPE 50 SYNTAX Integer32 51 MAX-ACCESS read-write 52 STATUS current 53 DESCRIPTION 54 "Default domain of the local clock" 55 REFERENCE "IEEE Std 1588-2008 7.1 and 8.2.1.4.3" 56 ::= { ieeeC37238DefaultDS 9 } 57




ieeeC37238DefaultDSSlaveOnly OBJECT-TYPE 1 SYNTAX TruthValue 2 MAX-ACCESS read-write 3 STATUS current 4 DESCRIPTION 5 "True if the local clock is a slave-only clock, False otherwise." 6 REFERENCE "IEEE Std 1588-2008 9.2.2, 9.2.3 and 8.2.1.4.4" 7 ::= { ieeeC37238DefaultDS 10 } 8 9 ieeeC37238DefaultDSGMIdentity OBJECT-TYPE 10 SYNTAX Integer32 11 MAX-ACCESS read-write 12 STATUS current 13 DESCRIPTION 14 "Grandmaster Identity to be transmitted in GRANDMASTER_ID TLV. 15 Configurable for grandmaster-capable devices only." 16 ::= { ieeeC37238DefaultDS 11 } 17 18 ieeeC37238DefaultDSOfstFrMLimitM OBJECT-TYPE 19 SYNTAX Integer32 20 UNITS "2**-16 ns * 2**64" 21 MAX-ACCESS read-write 22 STATUS current 23 DESCRIPTION 24 "Offset from Master Limit to generate OfstExceedsLimit event. The 25 most signigicant 4 bytes." 26 ::= { ieeeC37238DefaultDS 12 } 27 28 ieeeC37238DefaultDSOfstFrMLimitL OBJECT-TYPE 29 SYNTAX Integer32 30 UNITS "2**-16 ns * 2**64" 31 MAX-ACCESS read-write 32 STATUS current 33 DESCRIPTION 34 "Offset from Master Limit to generate OfstExceedsLimit event. The 35 least significant 4 bytes." 36 ::= { ieeeC37238DefaultDS 13 } 37 38 --===================================================================== 39 -- The Current data set represents this system’s topological location 40 -- relative to the known Grandmaster system. 41 --===================================================================== 42 43 ieeeC37238CurrentDS OBJECT IDENTIFIER ::= { ieeeC37238Objects 2 } 44 45 ieeeC37238CurrentDSStepsRemoved OBJECT-TYPE 46 SYNTAX Integer32(-32768..32767) 47 MAX-ACCESS read-only 48 STATUS current 49 DESCRIPTION 50 "The number of communication paths traversed between the local 51 clock and the grandmaster clock. The initialization value shall be 0." 52 REFERENCE "IEEE Std 1588-2008 8.2.2.2" 53 DEFVAL { 0 } 54 ::= { ieeeC37238CurrentDS 1 } 55 56 57




ieeeC37238CurrentDSOfstFrMasterM OBJECT-TYPE 1 SYNTAX Integer32 2 UNITS "2**-16 ns * 2**64" 3 MAX-ACCESS read-only 4 STATUS current 5 DESCRIPTION 6 "Implementation-specific representation of the current value of 7 the time difference between a master and a slave as computed by the 8 slave; i.e., <offsetFromMaster> = <Time on the slave clock> ? <Time on 9 the master clock>. The most significant 4 bytes. The data type should 10 be TimeInterval." 11 REFERENCE "IEEE Std 1588-2008 8.2.2.3" 12 ::= { ieeeC37238CurrentDS 2 } 13 14 ieeeC37238CurrentDSOfstFrMasterL OBJECT-TYPE 15 SYNTAX Integer32 16 UNITS "2**-16 ns * 2**64" 17 MAX-ACCESS read-only 18 STATUS current 19 DESCRIPTION 20 "Implementation-specific representation of the current value of 21 the time difference between a master and a slave as computed by the 22 slave; i.e., <offsetFromMaster> = <Time on the slave clock> ? <Time on 23 the master clock>. The least significant 4 bytes. The data type should 24 be TimeInterval." 25 REFERENCE "IEEE Std 1588-2008 11.2 and 8.2.2.3" 26 ::= { ieeeC37238CurrentDS 3 } 27 28 --===================================================================== 29 -- The Parent data set represents timing towards Grandmaster system’s 30 -- parameters as measured at this system. 31 --===================================================================== 32 33 ieeeC37238ParentDS OBJECT IDENTIFIER ::= { ieeeC37238Objects 3 } 34 35 ieeeC37238ParentDSClkIdentity OBJECT-TYPE 36 SYNTAX ClockIdentity 37 MAX-ACCESS read-only 38 STATUS current 39 DESCRIPTION 40 "Clock Identity of the master that synchronizes this clock." 41 REFERENCE "IEEE Std 1588-2008 8.2.3.2" 42 ::= { ieeeC37238ParentDS 1 } 43 44 ieeeC37238ParentDSPortNumber OBJECT-TYPE 45 SYNTAX Unsigned32(0..65535) 46 MAX-ACCESS read-only 47 STATUS current 48 DESCRIPTION 49 "Port Number of the port on the master that issues the Sync 50 messages used in synchronizing this clock." 51 REFERENCE "IEEE Std 1588-2008 8.2.3.2" 52 DEFVAL { 0 } 53 ::= { ieeeC37238ParentDS 2 } 54 55 ieeeC37238ParentDSStats OBJECT-TYPE 56 SYNTAX TruthValue 57




MAX-ACCESS read-only 1 STATUS current 2 DESCRIPTION 3 "True if all of the following 2 conditions are satisfied: 4 - The clock has a port in the SLAVE state. 5 - The clock has computed statistically valid estimates of 6 parentDS.observedParentOffsetScaledLog Variance and the 7 parentDS.observedParentClockPhaseChangeRate members. 8 False otherwise. The initialization value shall be FALSE." 9 REFERENCE "IEEE Std 1588-2008 8.2.3.3" 10 DEFVAL { false } 11 ::= { ieeeC37238ParentDS 3 } 12 13 ieeeC37238ParentDSObsOfstScdLVar OBJECT-TYPE 14 SYNTAX Unsigned32(0..65535) 15 MAX-ACCESS read-only 16 STATUS current 17 DESCRIPTION 18 "An estimate of the parent clock PTP variance as observed by 19 the slave clock, computed and represented as described in IEEE Std 20 1588-2008 7.6.3.5. The initialization value shall be FFFF." 21 REFERENCE "IEEE Std 1588-2008 7.6.3.3, 7.6.3.5 and 8.2.3.4" 22 DEFVAL { 65535 } 23 ::= { ieeeC37238ParentDS 4 } 24 25 ieeeC37238ParentDSObsPhChgRate OBJECT-TYPE 26 SYNTAX Unsigned32(0..65535) 27 MAX-ACCESS read-only 28 STATUS current 29 DESCRIPTION 30 "An estimate of the parent clock phase change rate as observed 31 by the slave clock as defined in IEEE Std 1588-2008 7.6.4.4. If the 32 estimate exceeds the capacity of its data type, this value shall be set 33 to 7FFF FFFF or 8000 0000, as appropriate. A positive sign indicates 34 that the parent clock phase change rate is greater than the rate of the 35 slave clock. The initialization value shall be 7FFF FFFF." 36 REFERENCE "IEEE Std 1588-2008 7.6.4.4, 15.5.3.5.1.4 and 8.2.3.5" 37 DEFVAL { 65535 } 38 ::= { ieeeC37238ParentDS 5 } 39 40 ieeeC37238ParentDSGMClkIdentity OBJECT-TYPE 41 SYNTAX ClockIdentity 42 MAX-ACCESS read-only 43 STATUS current 44 DESCRIPTION 45 "ClockIdentity of the grandmaster clock." 46 REFERENCE "IEEE Std 1588-2008 7.6.2.1 and 8.2.3.6" 47 ::= { ieeeC37238ParentDS 6 } 48 49 ieeeC37238ParentDSGMClkClass OBJECT-TYPE 50 SYNTAX IEEEC37238ClockClassValue 51 MAX-ACCESS read-only 52 STATUS current 53 DESCRIPTION 54 "ClockClass of the grandmaster clock." 55 REFERENCE "IEEE Std 1588-2008 8.2.3.7" 56 ::= { ieeeC37238ParentDS 7 } 57




ieeeC37238ParentDSGMClkAccuracy OBJECT-TYPE 1 SYNTAX IEEEC37238ClockAccuracyValue 2 MAX-ACCESS read-only 3 STATUS current 4 DESCRIPTION 5 "ClockAccuracy of the grandmaster clock." 6 REFERENCE "IEEE Std 1588-2008 8.2.3.7" 7 ::= { ieeeC37238ParentDS 8 } 8 9 ieeeC37238ParentDSGMOfstScdLVar OBJECT-TYPE 10 SYNTAX Integer32(-32768..32767) 11 MAX-ACCESS read-only 12 STATUS current 13 DESCRIPTION 14 "OffsetScaledLog Variance of the grandmaster clock." 15 REFERENCE "IEEE Std 1588-2008 8.2.3.7" 16 ::= { ieeeC37238ParentDS 9 } 17 18 ieeeC37238ParentDSGMPriority1 OBJECT-TYPE 19 SYNTAX Unsigned32(0..255) 20 MAX-ACCESS read-only 21 STATUS current 22 DESCRIPTION 23 "Priority1 attribute of the grandmaster clock." 24 REFERENCE "IEEE Std 1588-2008 8.2.3.8" 25 ::= { ieeeC37238ParentDS 10 } 26 27 ieeeC37238ParentDSGMPriority2 OBJECT-TYPE 28 SYNTAX Unsigned32(0..255) 29 MAX-ACCESS read-only 30 STATUS current 31 DESCRIPTION 32 "Priority2 attribute of the grandmaster clock." 33 REFERENCE "IEEE Std 1588-2008 8.2.3.9" 34 ::= { ieeeC37238ParentDS 11 } 35 36 ieeeC37238ParentDSGMIdentity OBJECT-TYPE 37 SYNTAX Integer32 38 MAX-ACCESS read-only 39 STATUS current 40 DESCRIPTION 41 "Grandmaster Identity received in GRANDMASTER_ID TLV." 42 ::= { ieeeC37238ParentDS 12 } 43 44 --===================================================================== 45 -- Time Properties data set represents the grandmaster’ parameters, as 46 -- measured at this system and are derived from IEEE C37.238 protocol. 47 --===================================================================== 48 49 ieeeC37238TimePropDS OBJECT IDENTIFIER ::= { ieeeC37238Objects 4 } 50 51 ieeeC37238TimePropDSCurUTCOfst OBJECT-TYPE 52 SYNTAX Integer32(-32768..32767) 53 MAX-ACCESS read-only 54 STATUS current 55 DESCRIPTION 56 "The current offset between TAI and UTC in units of seconds." 57




REFERENCE "IEEE Std 1588-2008 8.2.4.2" 1 ::= { ieeeC37238TimePropDS 1 } 2 3 ieeeC37238TimePropDSCurUTCOfstVd OBJECT-TYPE 4 SYNTAX TruthValue 5 MAX-ACCESS read-only 6 STATUS current 7 DESCRIPTION 8 "True if the the currentUtcOffset is known to be correct." 9 REFERENCE "IEEE Std 1588-2008 8.2.4.3" 10 ::= { ieeeC37238TimePropDS 2 } 11 12 ieeeC37238TimePropDSLeap59 OBJECT-TYPE 13 SYNTAX TruthValue 14 MAX-ACCESS read-only 15 STATUS current 16 DESCRIPTION 17 "True value indicates that the last minute of the current UTC 18 day contains 59 seconds." 19 REFERENCE "IEEE Std 1588-2008 8.2.4.4" 20 ::= { ieeeC37238TimePropDS 3 } 21 22 ieeeC37238TimePropDSLeap61 OBJECT-TYPE 23 SYNTAX TruthValue 24 MAX-ACCESS read-only 25 STATUS current 26 DESCRIPTION 27 "True value indicates that the last minute of the current UTC 28 day contains 61 seconds." 29 REFERENCE "IEEE Std 1588-2008 8.2.4.5" 30 ::= { ieeeC37238TimePropDS 4 } 31 32 ieeeC37238TimePropDSTmeTraceable OBJECT-TYPE 33 SYNTAX TruthValue 34 MAX-ACCESS read-only 35 STATUS current 36 DESCRIPTION 37 "True if the timescale and the value of currentUtcOffset are 38 traceable to a primary reference; False otherwise." 39 REFERENCE "IEEE Std 1588-2008 8.2.4.6" 40 ::= { ieeeC37238TimePropDS 5 } 41 42 ieeeC37238TimePropDSFrqTraceable OBJECT-TYPE 43 SYNTAX TruthValue 44 MAX-ACCESS read-only 45 STATUS current 46 DESCRIPTION 47 "True if the frequency determining the timescale is 48 traceable to a primary reference, False otherwise." 49 REFERENCE "IEEE Std 1588-2008 8.2.4.7" 50 ::= { ieeeC37238TimePropDS 6 } 51 52 ieeeC37238TimePropDSPTPTimescale OBJECT-TYPE 53 SYNTAX TruthValue 54 MAX-ACCESS read-only 55 STATUS current 56 DESCRIPTION 57




"True if the clock timescale of the grandmaster clock is PTP. 1 This value shall always be True for IEEE C37.238 compliant 2 implementations." 3 REFERENCE "IEEE Std 1588-2008 7.2.1 and 8.2.4.8" 4 ::= { ieeeC37238TimePropDS 7 } 5 6 ieeeC37238TimePropDSTimeSource OBJECT-TYPE 7 SYNTAX IEEEC37238TimeSourceValue 8 MAX-ACCESS read-only 9 STATUS current 10 DESCRIPTION 11 "The source of time used by the grandmaster clock." 12 REFERENCE "IEEE Std 1588-2008 8.2.4.9" 13 ::= { ieeeC37238TimePropDS 8 } 14 15 ieeeC37238TimePropDSLocalTCurOfs OBJECT-TYPE 16 SYNTAX Integer32(-32768..32767) 17 MAX-ACCESS read-write 18 STATUS current 19 DESCRIPTION 20 "The offset of the alternate time, in seconds, from the node 21 time. The alternate time is the sum of this value and the node time." 22 REFERENCE "IEEE Std 1588-2008 16.3.3.4" 23 ::= { ieeeC37238TimePropDS 9 } 24 25 ieeeC37238TimePropDSLocalTJumpS OBJECT-TYPE 26 SYNTAX Integer32(-32768..32767) 27 MAX-ACCESS read-write 28 STATUS current 29 DESCRIPTION 30 "The size of the next discontinuity, in seconds, of the 31 alternate time. A value of zero indicates that no discontinuity is 32 expected. A positive value indicates that the discontinuity will cause 33 the currentOffset of the alternate time to increase." 34 REFERENCE "IEEE Std 1588-2008 16.3.3.5" 35 ::= { ieeeC37238TimePropDS 10 } 36 37 ieeeC37238TimePropDSLocalTNtJump OBJECT-TYPE 38 SYNTAX Integer48 39 MAX-ACCESS read-write 40 STATUS current 41 DESCRIPTION 42 "The value of the seconds portion of the transmitting node 43 time at the time that the next discontinuity will occur. The 44 discontinuity occurs at the start of the second indicated by this 45 value." 46 REFERENCE "IEEE Std 1588-2008 16.3.3.6" 47 ::= { ieeeC37238TimePropDS 11 } 48 ieeeC37238TimePropDSLocalTName OBJECT-TYPE 49 SYNTAX OCTET STRING(SIZE(4)) 50 MAX-ACCESS read-write 51 STATUS current 52 DESCRIPTION 53 "The value of displayName shall be the text name of the alternate 54 timescale" 55 REFERENCE "IEEE Std 1588-2008 16.3.3.7" 56 ::= { ieeeC37238TimePropDS 12 } 57




1 ieeeC37238TimePropDSLeapEvLatest OBJECT-TYPE 2 SYNTAX Integer48 3 MAX-ACCESS read-write 4 STATUS current 5 DESCRIPTION 6 "The seconds portion of PTP time for the second prior to the 7 latest IERS-announced leap-second event (may be past or future)." 8 ::= { ieeeC37238TimePropDS 13 } 9 10 ieeeC37238TimePropDSUTCOfstNext OBJECT-TYPE 11 SYNTAX Integer32(-32768..32767) 12 MAX-ACCESS read-write 13 STATUS current 14 DESCRIPTION 15 "Seconds offset between TAI and UTC timescales after 16 LeapEvLatest(same as CurUTCOfst after LeapEvLatest time)." 17 ::= { ieeeC37238TimePropDS 14 } 18 19 ieeeC37238TimePropDSLeapEvExpiry OBJECT-TYPE 20 SYNTAX Integer48 21 MAX-ACCESS read-write 22 STATUS current 23 DESCRIPTION 24 "The seconds portion of PTP time for the expiry of the latest 25 IERS-announced leap-second event. If PTP time > LeapEvExpiry, devices 26 shall set CurUTCOfstVd to False." 27 ::= { ieeeC37238TimePropDS 15 } 28 29 --===================================================================== 30 -- Port data set parameters for each IEEE C37.238 capable port. 31 --===================================================================== 32 33 ieeeC37238PortDSIfTable OBJECT-TYPE 34 SYNTAX SEQUENCE OF IeeeC37238PortDSIfEntry 35 MAX-ACCESS not-accessible 36 STATUS current 37 DESCRIPTION 38 "A table of port related variables. A value of 1 is used 39 in device that does not have multiple ports." 40 ::= { ieeeC37238Objects 5 } 41 42 ieeeC37238PortDSIfEntry OBJECT-TYPE 43 SYNTAX IeeeC37238PortDSIfEntry 44 MAX-ACCESS not-accessible 45 STATUS current 46 DESCRIPTION 47 "A list of objects pertaining to a port." 48 INDEX { ifIeeeC37238PortDSifIndex } 49 ::= { ieeeC37238PortDSIfTable 1 } 50 51 IeeeC37238PortDSIfEntry ::= 52 SEQUENCE { 53 ifIeeeC37238PortDSifIndex Unsigned32, 54 ifIeeeC37238PortDSClkIdentity ClockIdentity, 55 ifIeeeC37238PortDSPortNumber Unsigned32, 56 ifIeeeC37238PortDSPortState INTEGER, 57




ifIeeeC37238PortDSMPathPDlyM Integer32, 1 ifIeeeC37238PortDSMPathPDlyL Integer32, 2 ifIeeeC37238PortDSLogAnnounceInt Integer32, 3 ifIeeeC37238PortDSAnnounceRcTout Unsigned32, 4 ifIeeeC37238PortDSLogSyncInt Integer32, 5 ifIeeeC37238PortDSDelayMech INTEGER, 6 ifIeeeC37238PortDSLogMinPdlyRInt Integer32, 7 ifIeeeC37238PortDSVersionNumber Unsigned32, 8 ifIeeeC37238PortDSPtpPortEnabled TruthValue, 9 ifIeeeC37238PortDSDlyAsymmetryM Integer32, 10 ifIeeeC37238PortDSDlyAsymmetryL Integer32, 11 ifIeeeC37238PortDSProfileId INTEGER, 12 ifIeeeC37238PortDSNetProtocol INTEGER, 13 ifIeeeC37238PortDSVlanId Unsigned32, 14 ifIeeeC37238PortDSPriority Unsigned32 15 } 16 17 ifIeeeC37238PortDSifIndex OBJECT-TYPE 18 SYNTAX Unsigned32(0..65535) 19 MAX-ACCESS not-accessible 20 STATUS current 21 DESCRIPTION 22 "Index for PortDS Table" 23 ::= { ieeeC37238PortDSIfEntry 1 } 24 25 ifIeeeC37238PortDSClkIdentity OBJECT-TYPE 26 SYNTAX ClockIdentity 27 MAX-ACCESS read-only 28 STATUS current 29 DESCRIPTION 30 "Clock Identity of the local clock." 31 REFERENCE "IEEE Std 1588-2008 8.2.5.2.1" 32 ::= { ieeeC37238PortDSIfEntry 2 } 33 34 ifIeeeC37238PortDSPortNumber OBJECT-TYPE 35 SYNTAX Unsigned32(0..65535) 36 MAX-ACCESS read-only 37 STATUS current 38 DESCRIPTION 39 "Port Number of the local port." 40 REFERENCE "IEEE Std 1588-2008 8.2.5.2.1" 41 ::= { ieeeC37238PortDSIfEntry 3 } 42 43 ifIeeeC37238PortDSPortState OBJECT-TYPE 44 SYNTAX INTEGER { 45 initalizing (1), 46 faulty (2), 47 disabled (3), 48 listening (4), 49 premaster (5), 50 master (6), 51 passive (7), 52 uncalibrated (8), 53 slave (9) 54 } 55 MAX-ACCESS read-only 56 STATUS current 57




DESCRIPTION 1 "The current state of the PTP protocol engine associated with 2 this port." 3 REFERENCE "IEEE Std 1588-2008 8.2.5.2.1 and Table 8" 4 DEFVAL { 3 } 5 ::= { ieeeC37238PortDSIfEntry 4 } 6 7 ifIeeeC37238PortDSMPathPDlyM OBJECT-TYPE 8 SYNTAX Integer32 9 MAX-ACCESS read-only 10 STATUS current 11 DESCRIPTION 12 "An estimate of the current one-way propagation delay on the 13 link, attached to this port computed using the peer delay mechanism. 14 The most significant 4 bytes. The initialization value shall be zero." 15 REFERENCE "IEEE Std 1588-2008 11.4 and 8.2.5.3.3" 16 ::= { ieeeC37238PortDSIfEntry 5 } 17 18 ifIeeeC37238PortDSMPathPDlyL OBJECT-TYPE 19 SYNTAX Integer32 20 MAX-ACCESS read-only 21 STATUS current 22 DESCRIPTION 23 "An estimate of the current one-way propagation delay on the 24 link, attached to this port computed using the peer delay mechanism. 25 The least significant 4 bytes. The initialization value shall be zero." 26 REFERENCE "IEEE Std 1588-2008 11.4 and 8.2.5.3.3" 27 ::= { ieeeC37238PortDSIfEntry 6 } 28 29 ifIeeeC37238PortDSLogAnnounceInt OBJECT-TYPE 30 SYNTAX Integer32(-128..127) 31 MAX-ACCESS read-write 32 STATUS current 33 DESCRIPTION 34 "The logarithm to the base 2 of the mean announceInterval." 35 REFERENCE "IEEE Std 1588-2008 7.7.2.2 and 8.2.5.4.1" 36 DEFVAL { 0 } 37 ::= { ieeeC37238PortDSIfEntry 7 } 38 39 ifIeeeC37238PortDSAnnounceRcTout OBJECT-TYPE 40 SYNTAX Unsigned32(0..255) 41 MAX-ACCESS read-write 42 STATUS current 43 DESCRIPTION 44 "The AnnounceReceiptTimeout, an integral multiple of 45 announceInterval." 46 REFERENCE "IEEE Std 1588-2008 7.7.3.1 and 8.2.5.4.2" 47 DEFVAL { 3 } 48 ::= { ieeeC37238PortDSIfEntry 8 } 49 50 ifIeeeC37238PortDSLogSyncInt OBJECT-TYPE 51 SYNTAX Integer32 (-128..127) 52 MAX-ACCESS read-write 53 STATUS current 54 DESCRIPTION 55 "The logarithm to the base 2 of the mean SyncInterval for 56 multicast messages." 57




REFERENCE "IEEE Std 1588-2008 7.7.2.3 and 8.2.5.4.3" 1 DEFVAL { 0 } 2 ::= { ieeeC37238PortDSIfEntry 9 } 3 4 ifIeeeC37238PortDSDelayMech OBJECT-TYPE 5 SYNTAX INTEGER { 6 e2e (1), 7 p2p (2), 8 disabled (254) 9

} 10 MAX-ACCESS read-write 11 STATUS current 12 DESCRIPTION 13 "The propagation delay measuring option used by the port. For 14 IEEE C37.238 compliant implementations this value shall be 2 (p2p)." 15 REFERENCE "IEEE Std 1588-2008 8.2.5.4.4 and Table 9" 16 DEFVAL { 2 } 17 ::= { ieeeC37238PortDSIfEntry 10 } 18 19 ifIeeeC37238PortDSLogMinPdlyRInt OBJECT-TYPE 20 SYNTAX Integer32(-128..127) 21 MAX-ACCESS read-write 22 STATUS current 23 DESCRIPTION 24 "The logarithm to the base 2 of the minPdelayReqInterval." 25 REFERENCE "IEEE Std 1588-2008 7.7.2.5 and 8.2.5.4.5" 26 DEFVAL { 0 } 27 ::= { ieeeC37238PortDSIfEntry 11 } 28 29 ifIeeeC37238PortDSVersionNumber OBJECT-TYPE 30 SYNTAX Unsigned32(0..63) 31 MAX-ACCESS read-only 32 STATUS current 33 DESCRIPTION 34 "The PTP version in use on the port. For IEEE C37.238 compliant 35 implementations this value shall be 2." 36 REFERENCE "IEEE Std 1588-2008 8.2.5.4.6" 37 DEFVAL { 2 } 38 ::= { ieeeC37238PortDSIfEntry 12 } 39 40 ifIeeeC37238PortDSPtpPortEnabled OBJECT-TYPE 41 SYNTAX TruthValue 42 MAX-ACCESS read-write 43 STATUS current 44 DESCRIPTION 45 "True if port is enabled." 46 DEFVAL { false } 47 ::= { ieeeC37238PortDSIfEntry 13 } 48 ifIeeeC37238PortDSDlyAsymmetryM OBJECT-TYPE 49 SYNTAX Integer32 50 MAX-ACCESS read-write 51 STATUS current 52 DESCRIPTION 53 "Path delay asymmetry. The most significant 4 bytes." 54 ::= { ieeeC37238PortDSIfEntry 14 } 55 56 57




ifIeeeC37238PortDSDlyAsymmetryL OBJECT-TYPE 1 SYNTAX Integer32 2 MAX-ACCESS read-write 3 STATUS current 4 DESCRIPTION 5 "Path delay asymmetry. The least significant 4 bytes." 6 ::= { ieeeC37238PortDSIfEntry 15 } 7 8 ifIeeeC37238PortDSProfileId OBJECT-TYPE 9 SYNTAX INTEGER { 10 ieee1588Default (0), 11 power (1), 12 ieee8021as (2), 13 lxi (3), 14 telecom (4) 15 } 16 MAX-ACCESS read-write 17 STATUS current 18 DESCRIPTION 19 "Indicates the PTP Profile in use." 20 DEFVAL { 1 } 21 ::= { ieeeC37238PortDSIfEntry 16 } 22 23 ifIeeeC37238PortDSNetProtocol OBJECT-TYPE 24 SYNTAX INTEGER { 25 ieee8023 (1), 26 udpIpv4 (2) 27 } 28 MAX-ACCESS read-write 29 STATUS current 30 DESCRIPTION 31 "Indicates Network Protocol in use. For IEEE C37.238 compliant 32 implementations this value shall be 1 (ieee8023)." 33 DEFVAL { 1 } 34 ::= { ieeeC37238PortDSIfEntry 17 } 35 36 ifIeeeC37238PortDSVlanId OBJECT-TYPE 37 SYNTAX Unsigned32(0..4095) 38 MAX-ACCESS read-write 39 STATUS current 40 DESCRIPTION 41 "Indicates VLAN ID in use." 42 DEFVAL { 0 } 43 ::= { ieeeC37238PortDSIfEntry 18 } 44 45 ifIeeeC37238PortDSPriority OBJECT-TYPE 46 SYNTAX Unsigned32(0..7) 47 MAX-ACCESS read-write 48 STATUS current 49 DESCRIPTION 50 "Indicates VLAN tag Priority in use." 51 DEFVAL { 4 } 52 ::= { ieeeC37238PortDSIfEntry 19 } 53 --===================================================================== 54 -- Transparent Clock Default data set represents default Transparent 55 -- Clock parameters. 56 --===================================================================== 57




ieeeC37238TCDefaultDS 1 OBJECT IDENTIFIER ::= { ieeeC37238Objects 6 } 2 3 ieeeC37238TCDefaultDSClkIdentity OBJECT-TYPE 4 SYNTAX ClockIdentity 5 MAX-ACCESS read-only 6 STATUS current 7 DESCRIPTION 8 "The Clock Identity of the local clock." 9 REFERENCE "IEEE Std 1588-2008 7.6.2.1 and 8.3.2.2.1" 10 ::= { ieeeC37238TCDefaultDS 1 } 11 12 ieeeC37238TCDefaultDSNumberPorts OBJECT-TYPE 13 SYNTAX Unsigned32(0..255) 14 MAX-ACCESS read-only 15 STATUS current 16 DESCRIPTION 17 "The number of PTP ports of the device." 18 REFERENCE "IEEE Std 1588-2008 8.3.2.2.2" 19 ::= { ieeeC37238TCDefaultDS 2 } 20 21 ieeeC37238TCDefaultDSDelayMech OBJECT-TYPE 22 SYNTAX INTEGER { 23 e2e (1), 24 p2p (2), 25 disabled (254) 26

} 27 MAX-ACCESS read-write 28 STATUS current 29 DESCRIPTION 30 "The Delay Mechanism used by the device.For IEEE C37.238 31 compliant implementations this value shall be 2 (p2p)." 32 REFERENCE "IEEE Std 1588-2008 8.3.2.3.1 and Table 9" 33 DEFVAL { 254 } 34 ::= { ieeeC37238TCDefaultDS 3 } 35 36 ieeeC37238TCDefaultDSPriDomain OBJECT-TYPE 37 SYNTAX Integer32 38 MAX-ACCESS read-write 39 STATUS current 40 DESCRIPTION 41 "Domain number of the primary syntonization domain. The 42 initialization value shall be 0." 43 REFERENCE "IEEE Std 1588-2008 10.1 and 8.3.2.3.2" 44 ::= { ieeeC37238TCDefaultDS 4 } 45 46 ieeeC37238TCDefaultDSSyntonize OBJECT-TYPE 47 SYNTAX TruthValue 48 MAX-ACCESS read-write 49 STATUS current 50 DESCRIPTION 51 "True if syntonization enabled." 52 ::= { ieeeC37238TCDefaultDS 5 } 53 54 ieeeC37238TCDefaultDSCurGMaster OBJECT-TYPE 55 SYNTAX ClockIdentity 56 MAX-ACCESS read-only 57




STATUS current 1 DESCRIPTION 2 "Comprises current grandmaster identity." 3 ::= { ieeeC37238TCDefaultDS 6 } 4 5 ieeeC37238TCDefaultDSTwoStepFlag OBJECT-TYPE 6 SYNTAX TruthValue 7 MAX-ACCESS read-write 8 STATUS current 9 DESCRIPTION 10 "True if the clock is a two-step clock." 11 REFERENCE "IEEE Std 1588-2008 8.2.1.2.1" 12 ::= { ieeeC37238TCDefaultDS 7 } 13 14 ieeeC37238TCDefaultDSGMIdentity OBJECT-TYPE 15 SYNTAX Integer32 16 MAX-ACCESS read-only 17 STATUS current 18 DESCRIPTION 19 "Grandmaster Identity received in GRANDMASTER_ID TLV." 20 ::= { ieeeC37238TCDefaultDS 8 } 21 22 ieeeC37238TCDefaultDSNetProtocol OBJECT-TYPE 23 SYNTAX INTEGER { 24 ieee8023 (1), 25 udpIpv4 (2) 26 } 27 MAX-ACCESS read-write 28 STATUS current 29 DESCRIPTION 30 "Indicates Network Protocol in use. For IEEE C37.238 compliant 31 implementations this value shall be 1 (ieee8023)." 32 DEFVAL { 1 } 33 ::= { ieeeC37238TCDefaultDS 9 } 34 35 ieeeC37238TCDefaultDSVlanId OBJECT-TYPE 36 SYNTAX Unsigned32(0..4095) 37 MAX-ACCESS read-write 38 STATUS current 39 DESCRIPTION 40 "Indicates VLAN ID in use." 41 DEFVAL { 0 } 42 ::= { ieeeC37238TCDefaultDS 10 } 43 44 ieeeC37238TCDefaultDSPriority OBJECT-TYPE 45 SYNTAX Unsigned32(0..7) 46 MAX-ACCESS read-write 47 STATUS current 48 DESCRIPTION 49 "Indicates VLAN tag Priority in use." 50 DEFVAL { 4 } 51 ::= { ieeeC37238TCDefaultDS 11 } 52 53 --===================================================================== 54 -- Transparent Clock per port data set represents per port Transparent 55 -- Clock parameters. 56 --===================================================================== 57




ieeeC37238TCPortDSIfTable OBJECT-TYPE 1 SYNTAX SEQUENCE OF IeeeC37238TCPortDSIfEntry 2 MAX-ACCESS not-accessible 3 STATUS current 4 DESCRIPTION 5 "A table of Transparent Clock port related variables." 6 ::= { ieeeC37238Objects 7 } 7 8 ieeeC37238TCPortDSIfEntry OBJECT-TYPE 9 SYNTAX IeeeC37238TCPortDSIfEntry 10 MAX-ACCESS not-accessible 11 STATUS current 12 DESCRIPTION 13 "A list of objects pertaining to a transparent clock port." 14 INDEX { ifIeeeC37238TCPortDSIfIndex } 15 ::= { ieeeC37238TCPortDSIfTable 1 } 16 17 IeeeC37238TCPortDSIfEntry ::= 18 SEQUENCE { 19 ifIeeeC37238TCPortDSIfIndex Unsigned32, 20 ifIeeeC37238TCPortDSPortNumber Unsigned32, 21 ifIeeeC37238TCPortDSLMinPdlyRInt Integer32, 22 ifIeeeC37238TCPortDSFaulty TruthValue, 23 ifIeeeC37238TCPortDSMPathPDlyM Integer32, 24 ifIeeeC37238TCPortDSMPathPDlyL Integer32, 25 ifIeeeC37238TCPortDSDlyAsymmM Integer32, 26 ifIeeeC37238TCPortDSDlyAsymmL Integer32 27 } 28 29 ifIeeeC37238TCPortDSIfIndex OBJECT-TYPE 30 SYNTAX Unsigned32(0..65535) 31 MAX-ACCESS not-accessible 32 STATUS current 33 DESCRIPTION 34 "Index for TCPortDS Table" 35 ::= { ieeeC37238TCPortDSIfEntry 1 } 36 37 ifIeeeC37238TCPortDSPortNumber OBJECT-TYPE 38 SYNTAX Unsigned32(0..65535) 39 MAX-ACCESS read-only 40 STATUS current 41 DESCRIPTION 42 "Port number of the local port." 43 REFERENCE "IEEE Std 1588-2008 7.5.2 and 8.3.3.2.1" 44 ::= { ieeeC37238TCPortDSIfEntry 2 } 45 ifIeeeC37238TCPortDSLMinPdlyRInt OBJECT-TYPE 46 SYNTAX Integer32(-128..127) 47 MAX-ACCESS read-write 48 STATUS current 49 DESCRIPTION 50 "The logarithm to the base 2 of the minPdelayReqInterval." 51 REFERENCE "IEEE Std 1588-2008 7.7.2.5 and 8.3.3.3.1" 52 DEFVAL { 0 } 53 ::= { ieeeC37238TCPortDSIfEntry 3 } 54 55 ifIeeeC37238TCPortDSFaulty OBJECT-TYPE 56 SYNTAX TruthValue 57




MAX-ACCESS read-only 1 STATUS current 2 DESCRIPTION 3 "True if the port is faulty and False if the port 4 is operating normally. The initialization value shall be False." 5 REFERENCE "IEEE Std 1588-2008 8.3.3.3.2" 6 ::= { ieeeC37238TCPortDSIfEntry 4 } 7 8 ifIeeeC37238TCPortDSMPathPDlyM OBJECT-TYPE 9 SYNTAX Integer32 10 MAX-ACCESS read-only 11 STATUS current 12 DESCRIPTION 13 "The estimate of the current one-way propagation delay. The most 14 significant 4 bytes." 15 REFERENCE "IEEE Std 1588-2008 8.3.3.3.3" 16 ::= { ieeeC37238TCPortDSIfEntry 5 } 17 18 ifIeeeC37238TCPortDSMPathPDlyL OBJECT-TYPE 19 SYNTAX Integer32 20 MAX-ACCESS read-only 21 STATUS current 22 DESCRIPTION 23 "The estimate of the current one-way propagation delay. The least 24 significant 4 bytes." 25 REFERENCE "IEEE Std 1588-2008 8.3.3.3.3" 26 ::= { ieeeC37238TCPortDSIfEntry 6 } 27 28 ifIeeeC37238TCPortDSDlyAsymmM OBJECT-TYPE 29 SYNTAX Integer32 30 MAX-ACCESS read-write 31 STATUS current 32 DESCRIPTION 33 "Path delay asymmetry. The most significant 4 bytes." 34 ::= { ieeeC37238TCPortDSIfEntry 7 } 35 36 ifIeeeC37238TCPortDSDlyAsymmL OBJECT-TYPE 37 SYNTAX Integer32 38 MAX-ACCESS read-write 39 STATUS current 40 DESCRIPTION 41 "Path delay asymmetry. The least significant 4 bytes." 42 ::= { ieeeC37238TCPortDSIfEntry 8 } 43 44 45 -- =============================================================== 46 -- IEEE C37.238 M I B N O T I F I C A T I O N S 47 -- =============================================================== 48 49 ieeeC37238Events OBJECT IDENTIFIER ::= { ieeeC37238Notifications 0 } 50 51 ieeeC37238EventChangeOfMaster NOTIFICATION-TYPE 52 STATUS current 53 DESCRIPTION 54 "Indicates that new grandmaster has been selected." 55 ::= { ieeeC37238Events 1 } 56 57




ieeeC37238EventMasterStepChange NOTIFICATION-TYPE 1 STATUS current 2 DESCRIPTION 3 "Indicates that a step change occurred in current grandmaster 4 time." 5 ::= { ieeeC37238Events 2 } 6 7 ieeeC37238EventFaultyState NOTIFICATION-TYPE 8 STATUS current 9 DESCRIPTION 10 "Indicates that a clock has entered faulty state." 11 ::= { ieeeC37238Events 3 } 12 13 ieeeC37238EventPortStateChange NOTIFICATION-TYPE 14 STATUS current 15 DESCRIPTION 16 "Indicates that port state has changed." 17 ::= { ieeeC37238Events 4 } 18 19 ieeeC37238EventOfstExceedsLimit NOTIFICATION-TYPE 20 STATUS current 21 DESCRIPTION 22 "Indicates that for a clock in a slave state Offset from Master 23 exceeds configurable limit." 24 ::= { ieeeC37238Events 5 } 25 26 ieeeC37238EventOtherProfileDetect NOTIFICATION-TYPE 27 STATUS current 28 DESCRIPTION 29 "Indicates that other PTP profile has been detected." 30 ::= { ieeeC37238Events 6 } 31 32 ieeeC37238EventLeapSecAnnounced NOTIFICATION-TYPE 33 STATUS current 34 DESCRIPTION 35 "Indicates that a leap second has been announced." 36 ::= { ieeeC37238Events 7 } 37 38 ieeeC37238EventPTPServiceStarted NOTIFICATION-TYPE 39 STATUS current 40 DESCRIPTION 41 "Indicates that PTP service has started." 42 ::= { ieeeC37238Events 8 } 43 44 ieeeC37238EventPTPServiceStopped NOTIFICATION-TYPE 45 STATUS current 46 DESCRIPTION 47 "Indicates that PTP service has stopped." 48 ::= { ieeeC37238Events 9 } 49 50 --===================================================================== 51 -- IEEE C37.238 MIB Module - Conformance Information 52 --===================================================================== 53 ieeeC37238Compliances OBJECT IDENTIFIER ::= { ieeeC37238Conformance 1 } 54 ieeeC37238Groups OBJECT IDENTIFIER ::= { ieeeC37238Conformance 2 } 55 56 ieeeC37238SystemDefaultReqdGroup OBJECT-GROUP 57




OBJECTS { 1 ieeeC37238DefaultDSTwoStepFlag, 2 ieeeC37238DefaultDSClkIdentity, 3 ieeeC37238DefaultDSNumberPorts, 4 ieeeC37238DefaultDSClkClass, 5 ieeeC37238DefaultDSClkAccuracy, 6 ieeeC37238DefaultDSOfsScdLogVar, 7 ieeeC37238DefaultDSPriority1, 8 ieeeC37238DefaultDSPriority2, 9 ieeeC37238DefaultDSDomainNumber, 10 ieeeC37238DefaultDSSlaveOnly, 11 ieeeC37238DefaultDSGMIdentity, 12 ieeeC37238DefaultDSOfstFrMLimitM, 13 ieeeC37238DefaultDSOfstFrMLimitL 14 } 15 STATUS current 16 DESCRIPTION 17 "Objects in the System Default required global group." 18 ::= { ieeeC37238Groups 1 } 19 20 ieeeC37238SystemCurrentGroup OBJECT-GROUP 21 OBJECTS { 22 ieeeC37238CurrentDSStepsRemoved, 23 ieeeC37238CurrentDSOfstFrMasterM, 24 ieeeC37238CurrentDSOfstFrMasterL 25 } 26 STATUS current 27 DESCRIPTION 28 "Objects in the System Current global group." 29 ::= { ieeeC37238Groups 2 } 30 31 ieeeC37238SystemClockParentGroup OBJECT-GROUP 32 OBJECTS { 33 ieeeC37238ParentDSClkIdentity, 34 ieeeC37238ParentDSPortNumber, 35 ieeeC37238ParentDSStats, 36 ieeeC37238ParentDSObsOfstScdLVar, 37 ieeeC37238ParentDSObsPhChgRate, 38 ieeeC37238ParentDSGMClkIdentity, 39 ieeeC37238ParentDSGMClkClass, 40 ieeeC37238ParentDSGMClkAccuracy, 41 ieeeC37238ParentDSGMOfstScdLVar, 42 ieeeC37238ParentDSGMPriority1, 43 ieeeC37238ParentDSGMPriority2, 44 ieeeC37238ParentDSGMIdentity 45 } 46 STATUS current 47 DESCRIPTION 48 "Objects in the Clock Parent global group." 49 ::= { ieeeC37238Groups 3 } 50 51 ieeeC37238SystemTimePropGroup OBJECT-GROUP 52 OBJECTS { 53 ieeeC37238TimePropDSCurUTCOfst, 54 ieeeC37238TimePropDSCurUTCOfstVd, 55 ieeeC37238TimePropDSLeap59, 56 ieeeC37238TimePropDSLeap61, 57




ieeeC37238TimePropDSTmeTraceable, 1 ieeeC37238TimePropDSFrqTraceable, 2 ieeeC37238TimePropDSPTPTimescale, 3 ieeeC37238TimePropDSTimeSource, 4 ieeeC37238TimePropDSLocalTCurOfs, 5 ieeeC37238TimePropDSLocalTJumpS, 6 ieeeC37238TimePropDSLocalTNtJump, 7 ieeeC37238TimePropDSLocalTName, 8 ieeeC37238TimePropDSLeapEvLatest, 9 ieeeC37238TimePropDSUTCOfstNext, 10 ieeeC37238TimePropDSLeapEvExpiry 11 } 12 STATUS current 13 DESCRIPTION 14 "Objects for the Time Properties Global group." 15 ::= { ieeeC37238Groups 4 } 16 17 ieeeC37238PortDataSetGlobalGroup OBJECT-GROUP 18 OBJECTS { 19 ifIeeeC37238PortDSClkIdentity, 20 ifIeeeC37238PortDSPortNumber, 21 ifIeeeC37238PortDSPortState, 22 ifIeeeC37238PortDSMPathPDlyM, 23 ifIeeeC37238PortDSMPathPDlyL, 24 ifIeeeC37238PortDSLogAnnounceInt, 25 ifIeeeC37238PortDSAnnounceRcTout, 26 ifIeeeC37238PortDSLogSyncInt, 27 ifIeeeC37238PortDSDelayMech, 28 ifIeeeC37238PortDSLogMinPdlyRInt, 29 ifIeeeC37238PortDSVersionNumber, 30 ifIeeeC37238PortDSPtpPortEnabled, 31 ifIeeeC37238PortDSDlyAsymmetryM, 32 ifIeeeC37238PortDSDlyAsymmetryL, 33 ifIeeeC37238PortDSProfileId, 34 ifIeeeC37238PortDSNetProtocol, 35 ifIeeeC37238PortDSVlanId, 36 ifIeeeC37238PortDSPriority 37 } 38 STATUS current 39 DESCRIPTION 40 "Objects for the port dataset media independent global group." 41 ::= {ieeeC37238Groups 5 } 42 43 ieeeC37238TCPropertiesGroup OBJECT-GROUP 44 OBJECTS { 45 ieeeC37238TCDefaultDSClkIdentity, 46 ieeeC37238TCDefaultDSNumberPorts, 47 ieeeC37238TCDefaultDSDelayMech, 48 ieeeC37238TCDefaultDSPriDomain, 49 ieeeC37238TCDefaultDSSyntonize, 50 ieeeC37238TCDefaultDSCurGMaster, 51 ieeeC37238TCDefaultDSTwoStepFlag, 52 ieeeC37238TCDefaultDSGMIdentity, 53 ieeeC37238TCDefaultDSNetProtocol, 54 ieeeC37238TCDefaultDSVlanId, 55 ieeeC37238TCDefaultDSPriority 56 } 57




STATUS current 1 DESCRIPTION 2 "Objects for the Transparent Clock group." 3 ::= { ieeeC37238Groups 6 } 4 5 ieeeC37238TCPortDataSetGroup OBJECT-GROUP 6 OBJECTS { 7 ifIeeeC37238TCPortDSPortNumber, 8 ifIeeeC37238TCPortDSLMinPdlyRInt, 9 ifIeeeC37238TCPortDSFaulty, 10 ifIeeeC37238TCPortDSMPathPDlyM, 11 ifIeeeC37238TCPortDSMPathPDlyL, 12 ifIeeeC37238TCPortDSDlyAsymmM, 13 ifIeeeC37238TCPortDSDlyAsymmL 14 } 15 STATUS current 16 DESCRIPTION 17 "Per port Objects for the Transparent Clock group." 18 ::= { ieeeC37238Groups 7 } 19 20 ieeeC37238EventsPropertiesGroup NOTIFICATION-GROUP 21 NOTIFICATIONS { 22 ieeeC37238EventChangeOfMaster, 23 ieeeC37238EventMasterStepChange, 24 ieeeC37238EventFaultyState, 25 ieeeC37238EventPortStateChange, 26 ieeeC37238EventOfstExceedsLimit, 27 ieeeC37238EventOtherProfileDetect, 28 ieeeC37238EventLeapSecAnnounced, 29 ieeeC37238EventPTPServiceStarted, 30 ieeeC37238EventPTPServiceStopped 31 } 32 STATUS current 33 DESCRIPTION 34 "Objects for the Notification Properties group." 35 ::= { ieeeC37238Groups 8 } 36 37 --===================================================================== 38 -- MIB Module Compliance statements 39 --===================================================================== 40 41 ieeeC37238Compliance MODULE-COMPLIANCE 42 STATUS current 43 DESCRIPTION 44 "The compliance statement for support by a bridge of 45 the IEEEC37-238-MIB module." 46 47 MODULE SNMPv2-MIB -- The SNMPv2-MIB [RFC3418] 48 MANDATORY-GROUPS { 49 systemGroup 50 } 51 52 MODULE IF-MIB -- The interfaces MIB [RFC2863] 53 MANDATORY-GROUPS { 54 ifGeneralInformationGroup 55 } 56 57




MODULE 1 MANDATORY-GROUPS { 2 ieeeC37238SystemDefaultReqdGroup, 3 ieeeC37238SystemCurrentGroup, 4 ieeeC37238SystemClockParentGroup, 5 ieeeC37238SystemTimePropGroup, 6 ieeeC37238PortDataSetGlobalGroup, 7 ieeeC37238TCPropertiesGroup, 8 ieeeC37238TCPortDataSetGroup, 9 ieeeC37238EventsPropertiesGroup 10 } 11 ::= { ieeeC37238Compliances 1 } 12 13 END 14 15 16




Annex G 1

(informative) 2

Bibliography 3

[B1] IEC 60834-1 Ed. 2.0 Teleprotection Equipment of Power Systems - Performance and Testing – 4 Part 1: Command Systems. 5

[B2] IEC 61850-7-2 Ed. 1.0 Communication networks and systems in substations - Part 7-2: Basic 6 communication structure for substation and feeder equipment – Abstract communication service interface 7 (ACSI). 8

[B3] IEC 61850-9-2 Ed. 1.0 Communication networks and systems in substations - Part 9-2: Specific 9 communication service mapping (SCSM) – Sampled values over ISO/IEC 8802-3. 10

[B4] IEC 62439-3 Industrial communication networks high availability automation networks - Part 3: 11 Parallel Redundancy Protocol (PRP) and High availability Seamless Ring (HSR). 12

[B5] IEEE Std 802.1Q-2005 IEEE Standard for Local and Metropolitan Area Networks - Virtual Bridged 13 Local Area Networks. 14

[B6] IEEE Std C37.118-2005 IEEE Standard for Synchrophasors for Power Systems. 15

[B7] International Vocabulary of Basic and General Terms in Metrology. 16

[B8] ISO/IEC 10646:2003 Information technology - Universal Multiple-Octet Coded Character Set 17 (UCS). 18