Fixed
Details
Assignee
Christian PapeChristian PapeReporter
Christian PapeChristian PapeHB Grooming Date
Nov 18, 2024HB Backlog Status
Refined BacklogSprint
NoneFix versions
Priority
High
Details
Details
Assignee
Christian Pape
Christian PapeReporter
Christian Pape
Christian PapeHB Grooming Date
Nov 18, 2024
HB Backlog Status
Refined Backlog
Sprint
None
Fix versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created November 15, 2024 at 8:17 AM
Updated December 2, 2024 at 9:34 PM
Resolved November 22, 2024 at 10:22 AM
The customer’s use case is set in a audio/video streaming environment. In order to maintain the quality of streams they need to synchronize time via the PTP protocol. They are using a PTP grandmaster clock appliance and the time is synchronizied across their network. They want to assure, that on a switch the time is learned on a specific port.
In PTP terminology a port participating in the clock synchronzation process is called a clockPort and each of these ports have a so called clockState indicating whick role these ports have related to their directly connected neighbors. To assure that the time is synchronized by using a specific neighbor the port connecting this neighbor need to be in slave mode, which means the neighbor is master. The port states are defined as follows:
Our idea for a poller is that we use our pattern scheme, like PTP-<clockPort>-<clockState> to bind a service to switch node. The poller will then check whether the given port is in the desired state and will go down if it is not.