Skip to content

Updated Networking Requirements for Vsphere IPI #40472

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.

Sign up for GitHub

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

Closed
dpateriya wants to merge 2 commits into from
Closed

Updated Networking Requirements for Vsphere IPI #40472

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e03bd18
Updated Networking Requirements for Vsphere IPI
dpateriya Jan 11, 2022
0d27d4d
Update installation-vsphere-installer-infra-requirements.adoc
dpateriya Jan 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions modules/installation-vsphere-installer-infra-requirements.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -299,3 +299,24 @@ endif::[]
ifeval::["{context}" == "installing-restricted-networks-vmc"]
:!restricted:
endif::[]

[IMPORTANT]
====
While provisioning more than one OCP cluster in same multicast domain with installer-provisioned vSphere installation, make sure that the VRRP router IDs should not be conflicting.

----
$ podman run quay.io/openshift/origin-baremetal-runtimecfg:TAG vr-ids cnf10
APIVirtualRouterID: 147
IngressVirtualRouterID: 2
----

Where TAG is the release you are going to install, e.g., 4.8. Let's see another example:

----
$ podman run quay.io/openshift/origin-baremetal-runtimecfg:TAG vr-ids cnf11
APIVirtualRouterID: 228
IngressVirtualRouterID: 147
----

In the example output above two clusters in the same multicast domain with names cnf10 and cnf11 would lead to a conflict.
====