Unable to make the qfx5110 work as a PTP Boundary Clock.
Topology:
A PTPv2 grandmaster --> QFX5100 (Boundary clock) ---> PTP Slave devices
Requirement to distribute the clock of a PTP grandmaster device to other PTP slave devices. The slave only suports multi-cast ipv4 transport PTP and the grandmaster supports multi-cast ipv4 transport PTP
Boundary clock configuration:-
ptp {
clock-mode boundary;
profile-type enterprise-profile; ---> Profile
slave {
delay-request 0;
interface ge-0/0/10.0 {
multicast-mode {
transport {
ipv4;
}
local-ip-address x.x.x.x;
QFX5110(Boundary clock) receives on its slave port GM’s information and recognise it but it does not synchronise its local clock to the GM - it does not propagate the GMs information to the slaves.
Example outputs:-
Admin@root> show ptp slave detail
PTP Slave Interface Details:
Interface : ge-0/0/10.0
Status : Slave, Active
Clock Info
Local Address : x.x.x.x Status: Configured, Slave, Active
Remote Master: y.y.y.y Status: Configured, Master, Active
Total Remote Masters: 1
> show ptp master detail
PTP Master Interface Details:
Interface : irb.100
Status : Master, Active
Clock Info :
Local Address: z.z.z.z Status: Configured, Master, Active
l2-ifl: ge-0/0/0.0
Remote Address: a.a.a.a Status: Learned, Slave, Active
Remote Address: b.b.b.b Status: Configured, Slave, Active
Total Remote Slaves: 2
l2-ifl: ge-0/0/1.0
Remote Address: a.a.a.a Status: Configured, Slave, Active
Total Remote Slaves: 1
QFX5110(Boundary clock) internal clock does not synchronize with PTP master. However, it does exchange PTP messages with the PTP master.
QFX5110(Boundary clock) does send does not reply to PTP delay request messages sent by the slave, however it does send Announce and Sync messages.
The boundary clock is configured with enterprise-profile , which is not supported on QFX5110 switch. Feature-Explorer
Find the supported profiles over the below link. Supported profiles
AES67 profile is supported by qfx5110, and this profile supports PTP over IPv4 multicast and ordinary and boundary clocks.
2024-07-18: Article validated2024-07-11 : Article Created