... | @@ -326,24 +326,6 @@ The enhancements to current IEEE 802.1AS include |
... | @@ -326,24 +326,6 @@ The enhancements to current IEEE 802.1AS include |
|
picosecond level
|
|
picosecond level
|
|
- auto-calibration of link asymmetry (single fiber and DDMTD phase
|
|
- auto-calibration of link asymmetry (single fiber and DDMTD phase
|
|
detection)
|
|
detection)
|
|
- support of network redundancy and seamless (no time) reconfiguration
|
|
|
|
- fault tolerance /isolation:
|
|
|
|
- isolation of different acceleration networks
|
|
|
|
synchronization-wise (but not within accelerator network)
|
|
|
|
[page 9](https://www.ohwr.org/project/white-rabbit/uploads/1244844e3c3cf850fad84e575f3b3f61/wrCernControlAndTiming.v1.1.pdf),
|
|
|
|
|
|
|
|
- tracking of time provided from different (redundant) sources
|
|
|
|
(many ports can work in slave mode). This gives possibility of
|
|
|
|
some comparison or voting logic which has not been investigated
|
|
|
|
yet.
|
|
|
|
- as soon as we detect that no connection to a grandmaster is not
|
|
|
|
valid (link down), we kill all the master ports (in a boundary
|
|
|
|
clock) not to propagate wrong time downstream - this is because
|
|
|
|
in the static state we synchronize simultaneously through
|
|
|
|
multiple paths, in a fault condition we do switching to backup
|
|
|
|
source rather then holdoff -- this is to meet very stringent
|
|
|
|
stability requirements, in less stringent applications holdoff
|
|
|
|
can be considered.
|
|
|
|
|
|
|
|
### Reliability
|
|
### Reliability
|
|
|
|
|
... | | ... | |