Skip to content

Commit b79adf0

Browse files
committed
OCPBUGS-9194: Workaround for inconsistency in network connection settings
1 parent 643d46a commit b79adf0

File tree

2 files changed

+64
-0
lines changed

2 files changed

+64
-0
lines changed

installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,8 @@ include::modules/ipi-install-configuring-host-network-interfaces-in-the-install-
4848

4949
include::modules/ipi-install-configuring-host-network-interfaces-for-subnets.adoc[leveloffset=+2]
5050

51+
include::modules/ipi-install-modifying-install-config-for-slaac-dual-stack-network.adoc[leveloffset=+2]
52+
5153
include::modules/ipi-install-configuring-host-dual-network-interfaces-in-the-install-config.yaml-file.adoc[leveloffset=+2]
5254

5355
[role="_additional-resources"]
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
// This is included in the following assemblies:
2+
//
3+
// ipi-install-configuration-files.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id='ipi-install-modifying-install-config-for-slaac-dual-stack-network_{context}']
7+
= Optional: Configuring address generation modes for SLAAC in dual-stack networks
8+
9+
For dual-stack clusters that use Stateless Address AutoConfiguration (SLAAC), you must specify a global value for the `ipv6.addr-gen-mode` network setting. You can set this value using NMState to configure the ramdisk and the cluster configuration files. If you don't configure a consistent `ipv6.addr-gen-mode` in these locations, IPv6 address mismatches can occur between CSR resources and `BareMetalHost` resources in the cluster.
10+
11+
.Prerequisites
12+
13+
* Install the NMState CLI (`nmstate`).
14+
15+
.Procedure
16+
17+
. Optional: Consider testing the NMState YAML syntax with the `nmstatectl gc` command before including it in the `install-config.yaml` file because the installation program will not check the NMState YAML syntax.
18+
19+
.. Create an NMState YAML file:
20+
+
21+
[source,yaml]
22+
----
23+
interfaces:
24+
- name: eth0
25+
ipv6:
26+
addr-gen-mode: <address_mode> <1>
27+
----
28+
<1> Replace `<address_mode>` with the type of address generation mode required for IPv6 addresses in the cluster. Valid values are `eui64`, `stable-privacy`, or `random`.
29+
30+
.. Test the configuration file by running the following command:
31+
+
32+
[source,terminal]
33+
----
34+
$ nmstatectl gc <nmstate_yaml_file> <1>
35+
----
36+
<1> Replace `<nmstate_yaml_file>` with the name of the test configuration file.
37+
38+
. Add the NMState configuration to the `hosts.networkConfig` section within the install-config.yaml file:
39+
+
40+
[source,yaml]
41+
----
42+
hosts:
43+
- name: openshift-master-0
44+
role: master
45+
bmc:
46+
address: redfish+http://<out_of_band_ip>/redfish/v1/Systems/
47+
username: <user>
48+
password: <password>
49+
disableCertificateVerification: null
50+
bootMACAddress: <NIC1_mac_address>
51+
bootMode: UEFI
52+
rootDeviceHints:
53+
deviceName: "/dev/sda"
54+
networkConfig:
55+
interfaces:
56+
- name: eth0
57+
ipv6:
58+
addr-gen-mode: <address_mode> <1>
59+
...
60+
61+
----
62+
<1> Replace `<address_mode>` with the type of address generation mode required for IPv6 addresses in the cluster. Valid values are `eui64`, `stable-privacy`, or `random`.

0 commit comments

Comments
 (0)