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

PTP4L output in T-GM

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-20183. The following is the description of the original issue:
      —
      Description of problem:

      T-GM ptp4l output in Announce Messages

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

      PTP Operator Version: 4.14.0-202309202002

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy linuxptp-daemon
2. Capture ptp4l output using tcpdump
3. Results:
      PTPv2 Announce Messages flags indicate TIME_TRACEABLE: FALSE and UTC_REASONABLE: False 
TimeSource: INTERNAL_OSCILLATOR (0xa0)

      Expected results according to IEEE 1588 PTP spec:

      PTPv2 Announce Messages should indicate TIME_TRACEABLE: TRUE and UTC_REASONABLE: True
TimeSource: GPS (0x20)
      How to veirfy 
pmc -u -b0 -f /var/run/ptp4l.0.config 'GET GRANDMASTER_SETTINGS_NP'
sending: GET GRANDMASTER_SETTINGS_NP
        507c6f.fffe.1fb4e8-0 seq 0 RESPONSE MANAGEMENT GRANDMASTER_SETTINGS_NP
                clockClass              6
                clockAccuracy           0x21
                offsetScaledLogVariance 0x4e5d
                currentUtcOffset        37
                leap61                  0
                leap59                  0
                currentUtcOffsetValid   1
                ptpTimescale            1
                timeTraceable           1
                frequencyTraceable      1
                timeSource              0x20

      TimeSourceAtomicClock TimeSource = 0x10
      TimeSourceGNSS TimeSource = 0x20
      TimeSourceTerrestrialRadio TimeSource = 0x30

              aputtur@redhat.com Aneesh Puttur
              openshift-crt-jira-prow OpenShift Prow Bot
              Bonnie Block Bonnie Block
              Pasi Vaananen
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: