When did it begin and how often does it occur?
Enabling new feature, never had it working.
What errors do you see?
We can verify that the registry setting "SoftwareTimestampSettings" is set to 5 for the NIC.
Get-SWTimestamping also returns correct NIC and setting.
NIC is restarted using Restart-NetAdapter.
When enabling w32time logging as per guide, we get no messages with ASD/ETD.
Also we see no message with "RX timestamp not returned and may be unsupported on the current network interface."
What's the environment and are there recent changes?
Windows server 2019 standard with all updates up to now.
Version: 10.0.17763 Build 17763
HW PowerEdge R610
NIC: Intel Ethernet Converged Network Adapter X710-4
What have you tried to troubleshoot this?
Tried on 2 other machines.
Tried disabling/enabling via cmdlets, via registry.
No log entries as described in the guide.
We also setup PTP synced linux machine to monitor PTP traffic from the windows server.
When we measure the difference between linux machine system time and "Delay Request Message".origintimestamp coming from windows server we see around 60us average difference.
This difference does not change when we enable/disable SW timestamping feature, hence the hypothesis that SW timestamping might not be working as it doesn't affect the "Delay Request Message".origintimestamp.
Please describe the issue in 2-3 sentences. Include what you're trying to accomplish when the issue occurs. We have setup PTP as per: https://github.com/microsoft/W32Time/blob/master/Precision%20Time%20Protocol/docs/Validation%20Guide%20-%20Precision%20Time%20Protocol.docx And it's working fine. Now we try to setup "SW timestamping" as per: https://github.com/microsoft/W32Time/blob/master/Timestamping/docs/Validation%20Guide%20-%20Software%20Timestamping.docx But it doesn't seem to work.
When did it begin and how often does it occur? Enabling new feature, never had it working.
What errors do you see? We can verify that the registry setting "SoftwareTimestampSettings" is set to 5 for the NIC. Get-SWTimestamping also returns correct NIC and setting. NIC is restarted using Restart-NetAdapter. When enabling w32time logging as per guide, we get no messages with ASD/ETD. Also we see no message with "RX timestamp not returned and may be unsupported on the current network interface."
What's the environment and are there recent changes? Windows server 2019 standard with all updates up to now. Version: 10.0.17763 Build 17763 HW PowerEdge R610 NIC: Intel Ethernet Converged Network Adapter X710-4
What have you tried to troubleshoot this? Tried on 2 other machines. Tried disabling/enabling via cmdlets, via registry. No log entries as described in the guide. We also setup PTP synced linux machine to monitor PTP traffic from the windows server. When we measure the difference between linux machine system time and "Delay Request Message".origintimestamp coming from windows server we see around 60us average difference. This difference does not change when we enable/disable SW timestamping feature, hence the hypothesis that SW timestamping might not be working as it doesn't affect the "Delay Request Message".origintimestamp.