Skip to content

Commit 807bb6d

Browse files
authored
Merge pull request #44946 from stevsmit/BZ2052635
Makes minor updates to Network and Bonding options
2 parents 390656d + 0ef98a8 commit 807bb6d

File tree

2 files changed

+15
-1
lines changed

2 files changed

+15
-1
lines changed

modules/installation-network-user-infra.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ ifndef::ibm-z,azure[]
148148
[id="installation-host-names-dhcp-user-infra_{context}"]
149149
== Setting the cluster node hostnames through DHCP
150150

151-
On {op-system-first} machines, the hostname is set through NetworkManager. By default, the machines obtain their hostname through DHCP. If the hostname is not provided by DHCP, it is obtained through a reverse DNS lookup. Reverse DNS lookup occurs after the network has been initialized on a node and can take time to resolve. Other system services can start prior to this and detect the hostname as `localhost` or similar. You can avoid this by using DHCP to provide the hostname for each cluster node.
151+
On {op-system-first} machines, the hostname is set through NetworkManager. By default, the machines obtain their hostname through DHCP. If the hostname is not provided by DHCP, set statically through kernel arguments, or another method, it is obtained through a reverse DNS lookup. Reverse DNS lookup occurs after the network has been initialized on a node and can take time to resolve. Other system services can start prior to this and detect the hostname as `localhost` or similar. You can avoid this by using DHCP to provide the hostname for each cluster node.
152152

153153
Additionally, setting the hostnames through DHCP can bypass any manual DNS record name configuration errors in environments that have a DNS split-horizon implementation.
154154
endif::ibm-z,azure[]

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

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,20 @@ ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp1s0:none
100100
nameserver=4.4.4.41
101101
----
102102

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:
104+
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 DNS server address to `4.4.4.41`
109+
* The auto-configuration value to `none`. No auto-configuration is required when IP networking is configured statically.
110+
111+
a|
112+
----
113+
ip=10.10.10.2::10.10.10.254:255.255.255.0::enp1s0:none
114+
nameserver=4.4.4.41
115+
----
116+
103117
a|Specify multiple network interfaces by specifying multiple `ip=` entries.
104118

105119
a|

0 commit comments

Comments
 (0)