Bug 1549015
| Summary: | [RFE] timemaster does not support bonding | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Daniele <dconsoli> |
| Component: | linuxptp | Assignee: | Miroslav Lichvar <mlichvar> |
| Status: | CLOSED ERRATA | QA Contact: | Qiao Zhao <qzhao> |
| Severity: | low | Docs Contact: | Marie Hornickova <mdolezel> |
| Priority: | high | ||
| Version: | 7.7 | CC: | mlichvar, qzhao, salmy, thozza |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | linuxptp-1.8-6.el7 | Doc Type: | Release Note |
| Doc Text: |
*timemaster* now supports bonding devices
The *timemaster* program can be used to synchronize the system clock to all available time sources in case that there are multiple PTP domains available on the network, or fallback to NTP is needed.
This update adds the possibility to specify bonding devices in the active-backup mode in the timemaster configuration file. *timemaster* now checks if the active interface supports software or hardware timestamping and starts *ptp4l* on the bonding interface.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-30 09:48:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1549614 | ||
|
Description
Daniele
2018-02-26 08:56:46 UTC
Patches submitted upstream: https://www.mail-archive.com/linuxptp-devel@lists.sourceforge.net/msg02668.html The patches have been accepted. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3102 |