Skip to content

Commit 3c4fe9f

Browse files
xenolinuxxenolinux
committed
OCPBUGS#2810: remove the table
1 parent 3d6e8c6 commit 3c4fe9f

File tree

1 file changed

+100
-59
lines changed

1 file changed

+100
-59
lines changed

‎modules/installation-user-infra-machines-static-network.adoc

Lines changed: 100 additions & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ If you install {op-system} from an ISO image, you can add kernel arguments manua
5454
When adding networking arguments manually, you must also add the `rd.neednet=1` kernel argument to bring the network up in the initramfs.
5555
====
5656
ifndef::ibm-z-kvm[]
57-
The following table provides examples for configuring networking and bonding on your {op-system} nodes for ISO installations. The examples describe how to use the `ip=`, `nameserver=`, and `bond=` kernel arguments.
57+
The following information provides examples for configuring networking and bonding on your {op-system} nodes for ISO installations. The examples describe how to use the `ip=`, `nameserver=`, and `bond=` kernel arguments.
5858

5959
[NOTE]
6060
====
@@ -63,150 +63,185 @@ Ordering is important when adding the kernel arguments: `ip=`, `nameserver=`, an
6363

6464
The networking options are passed to the `dracut` tool during system boot. For more information about the networking options supported by `dracut`, see the `dracut.cmdline` manual page.
6565

66-
.Networking and bonding options for ISO installations
6766
endif::ibm-z-kvm[]
6867
ifdef::ibm-z-kvm[]
69-
The following table provides examples for configuring networking on your {op-system} nodes for ISO installations. The examples describe how to use the `ip=` and `nameserver=` kernel arguments.
68+
The following information provides examples for configuring networking on your {op-system} nodes for ISO installations. The examples describe how to use the `ip=` and `nameserver=` kernel arguments.
7069

7170
[NOTE]
7271
====
7372
Ordering is important when adding the kernel arguments: `ip=` and `nameserver=`.
7473
====
7574

7675
The networking options are passed to the `dracut` tool during system boot. For more information about the networking options supported by `dracut`, see the `dracut.cmdline` manual page.
77-
78-
.Networking options for ISO installations
7976
endif::ibm-z-kvm[]
80-
|===
81-
|Description |Examples
8277

83-
a|To configure an IP address, either use DHCP (`ip=dhcp`) or set an individual static IP address (`ip=<host_ip>`). If setting a static IP, you must then identify the DNS server IP address (`nameserver=<dns_ip>`) on each node. This example sets: +
78+
The following examples are the networking options for ISO installation.
79+
80+
[discrete]
81+
=== Configuring DHCP or static IP addresses
8482

85-
* The node's IP address to `10.10.10.2` +
86-
* The gateway address to `10.10.10.254` +
87-
* The netmask to `255.255.255.0` +
88-
* The hostname to `core0.example.com` +
83+
To configure an IP address, either use DHCP (`ip=dhcp`) or set an individual static IP address (`ip=<host_ip>`). If setting a static IP, you must then identify the DNS server IP address (`nameserver=<dns_ip>`) on each node. The following example sets:
84+
85+
* The node's IP address to `10.10.10.2`
86+
* The gateway address to `10.10.10.254`
87+
* The netmask to `255.255.255.0`
88+
* The hostname to `core0.example.com`
8989
* The DNS server address to `4.4.4.41`
9090
* The auto-configuration value to `none`. No auto-configuration is required when IP networking is configured statically.
9191

92+
[source,terminal]
93+
----
94+
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp1s0:none
95+
nameserver=4.4.4.41
96+
----
97+
9298
[NOTE]
9399
====
94100
When you use DHCP to configure IP addressing for the {op-system} machines, the machines also obtain the DNS server information through DHCP. For DHCP-based deployments, you can define the DNS server address that is used by the {op-system} nodes through your DHCP server configuration.
95101
====
96102

97-
a|
98-
----
99-
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp1s0:none
100-
nameserver=4.4.4.41
101-
----
103+
[discrete]
104+
=== Configuring an IP address without a static hostname
102105

103-
a|You can configure an IP address without assigning a static hostname. If a static hostname is not set by the user, it will be picked up and automatically set by a reverse DNS lookup. To configure an IP address without a static hostname:
106+
You can configure an IP address without assigning a static hostname. If a static hostname is not set by the user, it will be picked up and automatically set by a reverse DNS lookup. To configure an IP address without a static hostname refer to the following example:
104107

105-
* The node's IP address to `10.10.10.2` +
106-
* The gateway address to `10.10.10.254` +
107-
* The netmask to `255.255.255.0` +
108+
* The node's IP address to `10.10.10.2`
109+
* The gateway address to `10.10.10.254`
110+
* The netmask to `255.255.255.0`
108111
* The DNS server address to `4.4.4.41`
109112
* The auto-configuration value to `none`. No auto-configuration is required when IP networking is configured statically.
110113

111-
a|
114+
[source,terminal]
112115
----
113116
ip=10.10.10.2::10.10.10.254:255.255.255.0::enp1s0:none
114117
nameserver=4.4.4.41
115118
----
116119

117-
a|Specify multiple network interfaces by specifying multiple `ip=` entries.
120+
[discrete]
121+
=== Specifying multiple network interfaces
122+
123+
You can specify multiple network interfaces by setting multiple `ip=` entries.
118124

119-
a|
125+
[source,terminal]
120126
----
121127
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp1s0:none
122128
ip=10.10.10.3::10.10.10.254:255.255.255.0:core0.example.com:enp2s0:none
123129
----
124130

125-
a|Optional: You can configure routes to additional networks by setting an `rd.route=` value.
131+
[discrete]
132+
=== Configuring default gateway and route
126133

134+
Optional: You can configure routes to additional networks by setting an `rd.route=` value.
135+
136+
[NOTE]
137+
====
127138
When you configure one or multiple networks, one default gateway is required. If the additional network gateway is different from the primary network gateway, the default gateway must be the primary network gateway.
128-
a|
129-
To configure the default gateway:
139+
====
130140

141+
* Run the following command to configure the default gateway:
142+
+
143+
[source,terminal]
131144
----
132145
ip=::10.10.10.254::::
133146
----
134147

135-
To configure the route for the additional network:
136-
148+
* Enter the following command to configure the route for the additional network:
149+
+
150+
[source,terminal]
137151
----
138152
rd.route=20.20.20.0/24:20.20.20.254:enp2s0
139153
----
140154

141-
a|Disable DHCP on a single interface, such as when there are two or more network interfaces and only one interface is being used. In the example, the `enp1s0` interface has a static networking configuration and DHCP is disabled for `enp2s0`, which is not used.
142-
a|
155+
[discrete]
156+
=== Disabling DHCP on a single interface
157+
158+
You can disable DHCP on a single interface, such as when there are two or more network interfaces and only one interface is being used. In the example, the `enp1s0` interface has a static networking configuration and DHCP is disabled for `enp2s0`, which is not used:
159+
160+
[source,terminal]
143161
----
144162
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp1s0:none
145163
ip=::::core0.example.com:enp2s0:none
146164
----
147165

148-
a|You can combine DHCP
149-
and static IP configurations on systems with
150-
multiple network interfaces.
151-
a|
166+
[discrete]
167+
=== Combining DHCP and static IP configurations
168+
169+
You can combine DHCP and static IP configurations on systems with multiple network interfaces, for example:
170+
171+
[source,terminal]
152172
----
153173
ip=enp1s0:dhcp
154174
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp2s0:none
155175
----
156176

157-
a|Optional: You can configure VLANs on individual interfaces by using the `vlan=` parameter.
158-
a|
159-
To configure a VLAN on a network interface and use a static IP address:
177+
[discrete]
178+
=== Configuring VLANs on individual interfaces
179+
180+
Optional: You can configure VLANs on individual interfaces by using the `vlan=` parameter.
160181

182+
* To configure a VLAN on a network interface and use a static IP address, run the following command:
183+
+
184+
[source,terminal]
161185
----
162186
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp2s0.100:none
163187
vlan=enp2s0.100:enp2s0
164188
----
165189

166-
To configure a VLAN on a network interface and to use DHCP:
167-
190+
* To configure a VLAN on a network interface and to use DHCP, run the following command:
191+
+
192+
[source,terminal]
168193
----
169194
ip=enp2s0.100:dhcp
170195
vlan=enp2s0.100:enp2s0
171196
----
172197

173-
a|You can provide multiple DNS servers by adding a `nameserver=` entry for each server.
174-
a|
198+
[discrete]
199+
=== Providing multiple DNS servers
200+
201+
You can provide multiple DNS servers by adding a `nameserver=` entry for each server, for example:
202+
203+
[source,terminal]
175204
----
176205
nameserver=1.1.1.1
177206
nameserver=8.8.8.8
178207
----
179208
ifndef::ibm-z-kvm[]
180-
a|Optional: Bonding multiple network interfaces to a single interface is supported
181-
using the `bond=` option. In these two examples:
209+
210+
[discrete]
211+
=== Bonding multiple network interfaces to a single interface
212+
213+
Optional: You can bond multiple network interfaces to a single interface by using the `bond=` option. Refer to the following examples:
182214

183215
* The syntax for configuring a bonded interface is: `bond=name[:network_interfaces][:options]`
184216
+
185217
_name_ is the bonding device name (`bond0`), _network_interfaces_
186218
represents a comma-separated list of physical (ethernet) interfaces (`em1,em2`),
187219
and _options_ is a comma-separated list of bonding options. Enter `modinfo bonding` to see available options.
188-
* When you
189-
create a bonded interface using `bond=`, you must specify how the IP address
190-
is assigned and other
220+
221+
* When you create a bonded interface using `bond=`, you must specify how the IP address is assigned and other
191222
information for the bonded interface.
192-
a|
193-
To configure the bonded interface to use DHCP, set the bond's IP address
194-
to `dhcp`. For example:
195223

224+
* To configure the bonded interface to use DHCP, set the bond's IP address to `dhcp`. For example:
225+
+
226+
[source,terminal]
196227
----
197228
bond=bond0:em1,em2:mode=active-backup
198229
ip=bond0:dhcp
199230
----
200231

201-
To configure the bonded interface to use a static IP address,
232+
* To configure the bonded interface to use a static IP address,
202233
enter the specific IP address you want and related information. For example:
203234
ifndef::ibm-z[]
235+
+
236+
[source,terminal]
204237
----
205238
bond=bond0:em1,em2:mode=active-backup
206239
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:bond0:none
207240
----
208241
endif::ibm-z[]
209242
ifdef::ibm-z[]
243+
244+
[source,terminal]
210245
----
211246
bond=bond0:em1,em2:mode=active-backup,fail_over_mac=1
212247
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:bond0:none
@@ -215,25 +250,31 @@ ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:bond0:none
215250
Always set option `fail_over_mac=1` in active-backup mode, to avoid problems when shared OSA/RoCE cards are used.
216251
endif::ibm-z[]
217252

218-
a|Optional: You can configure VLANs on bonded interfaces by using the `vlan=` parameter.
219-
a|
220-
To configure the bonded interface with a VLAN and to use DHCP:
253+
[discrete]
254+
=== Bonding multiple network interfaces to a single interface
255+
256+
Optional: You can configure VLANs on bonded interfaces by using the `vlan=` parameter and to use DHCP, for example:
221257

258+
[source,terminal]
222259
----
223260
ip=bond0.100:dhcp
224261
bond=bond0:em1,em2:mode=active-backup
225262
vlan=bond0.100:bond0
226263
----
227264

228-
To configure the bonded interface with a VLAN and to use a static IP address:
265+
Use the following example to configure the bonded interface with a VLAN and to use a static IP address:
229266

267+
[source,terminal]
230268
----
231269
ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:bond0.100:none
232270
bond=bond0:em1,em2:mode=active-backup
233271
vlan=bond0.100:bond0
234272
----
235273

236-
a|Optional: Network teaming can be used as an alternative to bonding by using the `team=` parameter. In this example:
274+
[discrete]
275+
=== Using network teaming
276+
277+
Optional: You can use a network teaming as an alternative to bonding by using the `team=` parameter:
237278

238279
* The syntax for configuring a team interface is: `team=name[:network_interfaces]`
239280
+
@@ -244,15 +285,15 @@ _name_ is the team device name (`team0`) and _network_interfaces_ represents a c
244285
Teaming is planned to be deprecated when {op-system} switches to an upcoming version of {op-system-base}. For more information, see this https://access.redhat.com/solutions/6509691[Red Hat Knowledgebase Article].
245286
====
246287

247-
a|
248-
To configure a network team:
288+
Use the following example to configure a network team:
249289

290+
[source,terminal]
250291
----
251292
team=team0:em1,em2
252293
ip=team0:dhcp
253294
----
254295
endif::ibm-z-kvm[]
255-
|===
296+
256297
ifndef::ibm-z,ibm-z-kvm,ibm-power[]
257298
[id="installation-user-infra-machines-coreos-installer-options_{context}"]
258299
== `coreos-installer` options for ISO and PXE installations

0 commit comments

Comments
 (0)