This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
There was a post here regarding the M4300 PTPv2 and boundary clock and although replies answered *some* of the questions, not all were resolved; but the thread was closed. I would have replied to that thread...
Some time has gone by now and I'm curious about changes regarding PTPv2 support in the 4300 range as well as boundary clock. I've seen some posts on-line that PTPv2 is only supported on smaller swtiches less than 24 ports. Is this accurate? Specs says "selected models" - which models?
It also looks like the current spec sheets show only E2E Transparent clock? Plans for supporting boundary clock? Road-map timeframe?
Thanks for reopening this up and giving us a chance to address it because I know alot of the people using our switches out there are curious about this new feature.
Most of the M4300 switch series as of the latest firmware 12.0.9.3 support PTPv2 E2E transparent mode. This is the only addition that has been made to support PTPv2. There is currently no plan to add any more functionality to PTPv2. Models that do not support due to hardware limitation are M4300-24x24F, M4300-48X, m4300-48XF
For all other models, 1-step Transparent Clock mode using the residence time of the PTPv2 packet at the egress port level.
Thanks for reopening this up and giving us a chance to address it because I know alot of the people using our switches out there are curious about this new feature.
Most of the M4300 switch series as of the latest firmware 12.0.9.3 support PTPv2 E2E transparent mode. This is the only addition that has been made to support PTPv2. There is currently no plan to add any more functionality to PTPv2. Models that do not support due to hardware limitation are M4300-24x24F, M4300-48X, m4300-48XF
For all other models, 1-step Transparent Clock mode using the residence time of the PTPv2 packet at the egress port level.
