Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-55740

[4.17]T-GM traceability flags are incorrect in some cases

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • CNF RAN Sprint 270, CNF RAN Sprint 271
    • 2
    • Done
    • Bug Fix
    • Hide
      Previously, the Grandmaster Timekeeper (T-GM) operation unexpectedly set the Precision Time Protocol (PTP) announce message internal signal flags incorrectly. This caused the loss of time synchronization across the network. With this release, the PTP announce message flags are correctly initialized ensuring accurate and standardized time synchronization information is disseminated across the network. (link:https://issues.redhat.com/browse/OCPBUGS-55740[OCPBUGS-55740])
      Show
      Previously, the Grandmaster Timekeeper (T-GM) operation unexpectedly set the Precision Time Protocol (PTP) announce message internal signal flags incorrectly. This caused the loss of time synchronization across the network. With this release, the PTP announce message flags are correctly initialized ensuring accurate and standardized time synchronization information is disseminated across the network. (link: https://issues.redhat.com/browse/OCPBUGS-55740 [ OCPBUGS-55740 ])
    • None
    • None
    • None
    • None

      Description of problem:

      WPC event notification design document defines grandmaster settings for the clock class 248. This definition differs from the values provided in ITU-T recommendation G.8275.

      Version-Release number of selected component (if applicable):

          4.17

      How reproducible:

          100%

      Steps to Reproduce:

          1. Run T-GM configuration
    2. Monitor PTP announce flags when the clock is unlocked or holdover

      Actual results:

           Flags differ from the ITU-T recommendation G.8275

      Expected results:

          Flags comply with the ITU-T recommendation G.8275

      Additional info:

      Frequency traceability flag should be always derived from eec DPLL (except when locked - it is TRUE).
Time traceability flag should be false in freerun and holdover-out-of-spec.
The synchronizationUncertain flag should be initialized according to the state.
Some ambiguity exists between "Free run" and "Acquiring" modes leaving some freedom for implementation-specific settings.

       

       

       

              vgrinber@redhat.com Vitaly Grinberg
              vgrinber@redhat.com Vitaly Grinberg
              None
              None
              Bonnie Block Bonnie Block
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: