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
@@ -54,7 +54,7 @@ If you install {op-system} from an ISO image, you can add kernel arguments manua
54
54
When adding networking arguments manually, you must also add the `rd.neednet=1` kernel argument to bring the network up in the initramfs.
55
55
====
56
56
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.
58
58
59
59
[NOTE]
60
60
====
@@ -63,150 +63,185 @@ Ordering is important when adding the kernel arguments: `ip=`, `nameserver=`, an
63
63
64
64
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.
65
65
66
-
.Networking and bonding options for ISO installations
67
66
endif::ibm-z-kvm[]
68
67
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.
70
69
71
70
[NOTE]
72
71
====
73
72
Ordering is important when adding the kernel arguments: `ip=` and `nameserver=`.
74
73
====
75
74
76
75
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
79
76
endif::ibm-z-kvm[]
80
-
|===
81
-
|Description |Examples
82
77
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
84
82
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`
89
89
* The DNS server address to `4.4.4.41`
90
90
* The auto-configuration value to `none`. No auto-configuration is required when IP networking is configured statically.
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.
=== Configuring an IP address without a static hostname
102
105
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:
104
107
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`
108
111
* The DNS server address to `4.4.4.41`
109
112
* The auto-configuration value to `none`. No auto-configuration is required when IP networking is configured statically.
a|Optional: You can configure routes to additional networks by setting an `rd.route=` value.
131
+
[discrete]
132
+
=== Configuring default gateway and route
126
133
134
+
Optional: You can configure routes to additional networks by setting an `rd.route=` value.
135
+
136
+
[NOTE]
137
+
====
127
138
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
+
====
130
140
141
+
* Run the following command to configure the default gateway:
142
+
+
143
+
[source,terminal]
131
144
----
132
145
ip=::10.10.10.254::::
133
146
----
134
147
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]
137
151
----
138
152
rd.route=20.20.20.0/24:20.20.20.254:enp2s0
139
153
----
140
154
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:
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:
237
278
238
279
* The syntax for configuring a team interface is: `team=name[:network_interfaces]`
239
280
+
@@ -244,15 +285,15 @@ _name_ is the team device name (`team0`) and _network_interfaces_ represents a c
244
285
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].
245
286
====
246
287
247
-
a|
248
-
To configure a network team:
288
+
Use the following example to configure a network team:
0 commit comments