Skip to content

Commit 373ab6b

Browse files
Add note on NM behavior with additional networks
When using additional networks on a dual-stack cluster, the same network manager connection would be enforced to all the additional networks. This commit, informes the users about that behavior and recommends an alternative if different connections are desired. Co-authored-by: Max Bridges <mbridges@redhat.com>
1 parent fb40d96 commit 373ab6b

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

modules/install-osp-deploy-dualstack.adoc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -164,4 +164,10 @@ ipv6.addr-gen-mode=0
164164
----
165165
166166
After you create and edit the file, reboot the installation host.
167+
====
168+
169+
[NOTE]
170+
====
171+
The `ip=dhcp,dhcp6` kernel argument, which is set on all of the nodes, results in a single Network Manager connection profile that is activated on multiple interfaces simultaneously.
172+
Because of this behavior, any additional network has the same connection enforced with an identical UUID. If you need an interface-specific configuration, create a new connection profile for that interface so that the default connection is no longer enforced on it.
167173
====

0 commit comments

Comments
 (0)