Node with a Vlan type PTP interface is not syncing with the GM.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Caio Bruchert |
Bug Description
Brief Description
VLAN type ptp slave port configured on a pci-sriov interface. The system comes fine from locked/unlocked. Ptp process auto starts but the node never syncs with the Boundry clock.
Severity
Standard.
Steps to Reproduce
Steps to reproduce:
Customer configures ptp=slave role on a VLAN type interface.
Node comes up after lock/unlock
No alarms except ptp not locked to GM
ptp4l and phc2sys process running fine
user.log sitting on "master clock not ready.. waiting"
The user does the following steps to sync the node:
1) Kill ptp4l & phc2sys process
2) Run below 2 commands:
sudo ptp4l -i vlan192 -f /etc/ptp4l.conf
sudo phc2sys -u 10 -s vlan192 -w -m -n 24 | awk '{ print strftime("%c: "), $0; fflush(); }'
The node will start syncing with the GM.
Expected Behavior
The node should sync with PTP GM through a vlan type PTP=slave interface.
Reproducibility
Seen in the overall customer environment.
System Configuration
Standalone AIO-SX
Timestamp/Logs
Alarms
Workaround
User has to first kill ptp process (ptp4l and phc2sys) and issue a manual ptp4l command with the vlan interface specified followed by starting phc2sys to sync the node with BC.
Changed in starlingx: | |
assignee: | nobody → Caio Bruchert (cbrucher) |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.8.0 stx.networking |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/857946
Review: https:/