You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before installation, you must configure the networking on the provisioner node. Installer-provisioned clusters deploy with a bare-metal bridge and network, and an optional provisioning bridge and network.
9
+
Before installation, you must configure networking settings for the provisioner node. Installer-provisioned clusters deploy with a bare-metal bridge and network resources, and an optional provisioning bridge and network resources.
You can also configure networking from the web console.
15
+
You can also configure networking settings from the {product-title} web console.
16
16
====
17
17
18
-
.Procedure
18
+
.Prerequisites
19
19
20
-
. Export the bare-metal network NIC name by running the following command:
21
-
+
22
-
[source,terminal]
23
-
----
24
-
$ export PUB_CONN=<baremetal_nic_name>
25
-
----
20
+
* You installed the `nmstate` package with the `sudo dnf install -y <package_name>` command. The package includes the `nmstatectl` CLI.
21
+
22
+
.Procedure
26
23
27
24
. Configure the bare-metal network:
28
25
+
29
26
[NOTE]
30
27
====
31
-
The SSH connection might disconnect after executing these steps.
28
+
When configuring the bare-metal network and the secure shell (SSH) connection disconnects, NMState has a rollback mechanism that automatically reverts any configurations. You can also use the `nmstatectl gc` tool to generate configuration files for specified network state files.
32
29
====
33
-
34
-
.. For a network using DHCP, run the following command:
35
30
+
36
-
[source,terminal]
31
+
.. For a network using DHCP, run the following command to delete the `/etc/sysconfig/network-scripts/ifcfg-eth0` legacy style:
32
+
+
33
+
[source,yaml,subs="+quotes"]
34
+
----
35
+
$ nmcli con delete "System <baremetal_nic_name>"
37
36
----
38
-
$ sudo nohup bash -c "
39
-
nmcli con down \"$PUB_CONN\"
40
-
nmcli con delete \"$PUB_CONN\"
41
-
# RHEL 8.1 appends the word \"System\" in front of the connection, delete in case it exists
42
-
nmcli con down \"System $PUB_CONN\"
43
-
nmcli con delete \"System $PUB_CONN\"
44
-
nmcli connection add ifname baremetal type bridge <con_name> baremetal bridge.stp no <1>
45
-
nmcli con add type bridge-slave ifname \"$PUB_CONN\" master baremetal
46
-
pkill dhclient;dhclient baremetal
47
-
"
48
-
----
49
-
<1> Replace `<con_name>` with the connection name.
50
-
51
-
.. For a network using static IP addressing and no DHCP network, run the following command:
52
37
+
53
-
[source,terminal]
38
+
where:
39
+
+
40
+
`<baremetal_nic_name>`:: Replace `<baremetal_nic_name>` with the name of your network interface controller (NIC).
41
+
+
42
+
.. For a network that uses Dynamic Host Configuration Protocol (DHCP), create an NMState YAML file and specify the bare-metal bridge interface and any physical interfaces in the file:
43
+
+
44
+
.Example bare-metal bridge interface configuration that uses DHCP
45
+
[source,yaml]
46
+
----
47
+
# ...
48
+
interfaces:
49
+
- name: <physical_interface_name>
50
+
type: ethernet
51
+
state: up
52
+
ipv4:
53
+
enabled: false
54
+
ipv6:
55
+
enabled: false
56
+
- name: baremetal
57
+
type: linux-bridge
58
+
state: up
59
+
ipv4:
60
+
enabled: true
61
+
dhcp: true
62
+
bridge:
63
+
options:
64
+
stp:
65
+
enabled: false
66
+
port:
67
+
- name: <physical_interface_name>
68
+
# ...
69
+
----
70
+
+
71
+
.. For a network using static IP addressing and no DHCP network, create an NMState YAML file and specify the bare-metal bridge interface details in the file:
72
+
+
73
+
.Example bare-metal bridge interface configuration that uses static IP addressing and no DHCP network
74
+
[source,yaml]
75
+
----
76
+
# ...
77
+
dns-resolver:
78
+
config:
79
+
server:
80
+
- <dns_ip_address>
81
+
routes:
82
+
config:
83
+
- destination: 0.0.0.0/0
84
+
next-hop-interface: baremetal
85
+
next-hop-address: <gateway_ip>
86
+
interfaces:
87
+
- name: <physical_interface_name>
88
+
type: ethernet
89
+
state: up
90
+
ipv4:
91
+
enabled: false
92
+
ipv6:
93
+
enabled: false
94
+
- name: baremetal
95
+
type: linux-bridge
96
+
state: up
97
+
ipv4:
98
+
enabled: true
99
+
dhcp: false
100
+
address:
101
+
- ip: <static_ip_address>
102
+
prefix-length: 24
103
+
bridge:
104
+
options:
105
+
stp:
106
+
enabled: false
107
+
port:
108
+
- name: <physical_interface_name>
109
+
# ...
54
110
----
55
-
$ sudo nohup bash -c "
56
-
nmcli con down \"$PUB_CONN\"
57
-
nmcli con delete \"$PUB_CONN\"
58
-
# RHEL 8.1 appends the word \"System\" in front of the connection, delete in case it exists
59
-
nmcli con down \"System $PUB_CONN\"
60
-
nmcli con delete \"System $PUB_CONN\"
61
-
nmcli connection add ifname baremetal type bridge con-name baremetal bridge.stp no ipv4.method manual ipv4.addr "x.x.x.x/yy" ipv4.gateway "a.a.a.a" ipv4.dns "b.b.b.b" <1>
62
-
nmcli con add type bridge-slave ifname \"$PUB_CONN\" master baremetal
63
-
nmcli con up baremetal
64
-
"
65
-
----
66
-
<1> Replace `<con_name>` with the connection name. Replace `x.x.x.x/yy` with the IP address and CIDR for the network. Replace `a.a.a.a` with the network gateway. Replace `b.b.b.b` with the IP address of the DNS server.
111
+
+
112
+
where:
113
+
+
114
+
`<dns-resolver>`:: Defines the DNS server for your bare-metal system.
115
+
`<server>`:: Replace `<dns_ip_address>` with the IP address for the DNS server.
116
+
`<type>`:: Defines the bridge interface and its static IP configuration.
117
+
`<gateway>`:: Replace `<gateway_ip>` with the IP address of the gateway.
118
+
`<name>`:: Details the physical interface that you set as the bridge port.
67
119
68
-
. Optional: If you are deploying with a provisioning network, export the provisioning network NIC name by running the following command:
120
+
. Apply the network configuration from the YAML file to the network interfaces for the host by entering the following command:
69
121
+
70
122
[source,terminal]
71
123
----
72
-
$ export PROV_CONN=<prov_nic_name>
124
+
$ nmstatectl apply <path_to_network_yaml>
73
125
----
74
126
75
-
. Optional: If you are deploying with a provisioning network, configure the provisioning network by running the following command:
127
+
. Back up the network configuration YAML file by entering the following command:
76
128
+
77
129
[source,terminal]
78
130
----
79
-
$ sudo nohup bash -c "
80
-
nmcli con down \"$PROV_CONN\"
81
-
nmcli con delete \"$PROV_CONN\"
82
-
nmcli connection add ifname provisioning type bridge con-name provisioning
83
-
nmcli con add type bridge-slave ifname \"$PROV_CONN\" master provisioning
. Optional: If you are deploying your cluster in a provisioning network, create or edit an NMState YAML file and specify the details in the file.
89
135
+
90
136
[NOTE]
91
137
====
92
-
The SSH connection might disconnect after executing these steps.
93
-
94
-
The IPv6 address can be any address that is not routable through the bare-metal network.
138
+
The IPv6 address can be any address that does not route through the bare-metal network.
95
139
96
-
Ensure that UEFI is enabled and UEFI PXE settings are set to the IPv6 protocol when using IPv6 addressing.
140
+
Ensure that you enabled Unified Extensible Firmware Interface (UEFI) and set UEFI PXE settings for the IPv6 protocol when using IPv6 addressing.
97
141
====
98
-
99
-
. Optional: If you are deploying with a provisioning network, configure the IPv4 address on the provisioning network connection by running the following command:
. SSH back into the `provisioner` node (if required) by running the following command:
143
+
.Example NMState YAML file for a provisioning network
144
+
[source,yaml]
145
+
----
146
+
# ...
147
+
interfaces:
148
+
- name: eth1
149
+
type: ethernet
150
+
state: up
151
+
ipv4:
152
+
enabled: false
153
+
ipv6:
154
+
enabled: false
155
+
- name: provisioning
156
+
type: linux-bridge
157
+
state: up
158
+
ipv4:
159
+
enabled: true
160
+
dhcp: false
161
+
address:
162
+
- ip: 172.22.0.254
163
+
prefix-length: 24
164
+
ipv6:
165
+
enabled: true
166
+
dhcp: false
167
+
address:
168
+
- ip: fd00:1101::1
169
+
prefix-length: 64
170
+
bridge:
171
+
options:
172
+
stp:
173
+
enabled: false
174
+
port:
175
+
- name: eth1
176
+
# ...
177
+
----
178
+
179
+
. Optional: Establish an SSH connection into the `provisioner` node by running the following command:
107
180
+
108
181
[source,terminal]
109
182
----
110
-
# ssh kni@provisioner.<cluster-name>.<domain>
183
+
# ssh kni@provisioner.<cluster_name>.<domain>
111
184
----
185
+
+
186
+
where
187
+
+
188
+
`<cluster_name>.<domain>`:: Replace `<cluster_name>` with the name of your cluster and `<domain>` with the fully qualified domain name (FQDN) of your cluster.
112
189
113
190
. Verify that the connection bridges have been properly created by running the following command:
0 commit comments