Skip to content

OCPBUGS-54148-sdn: Added PTP and OVNK limitation to SDN docs #92083

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: enterprise-4.16
Choose a base branch
from

Conversation

dfitzmau
Copy link
Contributor

@dfitzmau dfitzmau commented Apr 11, 2025

Version(s):
4.12 to 4.16

Issue:
OCPBUGS-54148

Link to docs preview:

  • SME has approved this change (Christian Passarelli/comment in team-ocp-dsn doc).
  • QE has approved this change (Zhanqi Zhao).

@ocpdocs-previewbot
Copy link

Copy link

openshift-ci bot commented Apr 11, 2025

@dfitzmau: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@dfitzmau dfitzmau changed the title OCPBUGS-54148-sdn: Added PTP and OVNK limitation to SDN ddocs OCPBUGS-54148-sdn: Added PTP and OVNK limitation to SDN docs Apr 11, 2025
@@ -88,6 +88,8 @@ During the limited live migration, both OVN-Kubernetes and OpenShift SDN run in

* OVN-Kubernetes reserves the `100.64.0.0/16` and `100.88.0.0/16` IP address ranges. These subnets cannot be overlapped with any other internal or external network. If these IP addresses have been used by OpenShift SDN or any external networks that might communicate with this cluster, you must patch them to use a different IP address range before starting the limited live migration. See "Patching OVN-Kubernetes address ranges" for more information.

* If your cluster uses the OVN-Kubernetes network plugin and PTP uses the User Datagram Protocol (UDP) for hardware time stamping, the hardware time stamping cannot be applied to primary interface devices, such as an Open vSwitch (OVS) bridge.
Copy link

@zhaozhanqi zhaozhanqi Apr 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assumed users is using openshfit-sdn plugin when reading this part. and want to migration to ovn-kubernetes cluster. so can we update to like this

if your openshift-sdn cluster with PTP uses the User Datagram Protocol (UDP) for hardware time stamping,  Please note, after migration to ovn-kubernetes. the hardware time stamping cannot be applied to primary interface devices, such as an Open vSwitch (OVS) bridge. So configurations like UDPv4 cannot work with the `br-ex` interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants