Skip to content
Closed
Changes from all commits
Commits
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
17 changes: 17 additions & 0 deletions modules/installation-vsphere-installer-infra-requirements.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -300,3 +300,20 @@ 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
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Here cnf10, cnf11 are cluster name, suggest to describe the usage of podman command. For example:
$ podman run quay.io/openshift/origin-baremetal-runtimecfg:[TAG] vr-ids [CLUSTER_NAME]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@dpateriya, will you please update your PR?

APIVirtualRouterID: 147
IngressVirtualRouterID: 2
----
Where TAG is the release you are going to install, e.g., 4.9. 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.
====