Skip to content

Commit 2116986

Browse files
rohennesrohennes
committed
TELCODOCS-898: BM IPI customer feedback regarding NTP sync and L2 connectivity
1 parent 20032d0 commit 2116986

File tree

3 files changed

+78
-7
lines changed

3 files changed

+78
-7
lines changed

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

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,15 @@ include::modules/ipi-install-installing-rhel-on-the-provisioner-node.adoc[levelo
1010

1111
include::modules/ipi-install-preparing-the-provisioner-node-for-openshift-install.adoc[leveloffset=+1]
1212

13+
include::modules/ipi-install-checking-ntp-sync.adoc[leveloffset=+1]
14+
15+
[role="_additional-resources"]
16+
.Additional resources
17+
18+
* xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#configuring-ntp-for-disconnected-clusters_ipi-install-installation-workflow[Optional: Configuring NTP for disconnected clusters]
19+
20+
* xref:../../installing/installing_bare_metal_ipi/ipi-install-prerequisites.adoc#network-requirements-ntp_ipi-install-prerequisites[Network Time Protocol (NTP)]
21+
1322
include::modules/ipi-install-configuring-networking.adoc[leveloffset=+1]
1423

1524
include::modules/ipi-install-establishing-communication-between-subnets.adoc[leveloffset=+1]

‎modules/ipi-install-checking-ntp-sync.adoc

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * list of assemblies where this module is included
4+
// ipi-install-installation-workflow.adoc
5+
6+
:_content-type: PROCEDURE
7+
[id="checking-ntp-sync_{context}"]
8+
= Checking NTP server synchronization
9+
10+
The {product-title} installation program installs the `chrony` Network Time Protocol (NTP) service on the cluster nodes. To complete installation, each node must have access to an NTP time server. You can verify NTP server synchronization by using the `chrony` service.
11+
12+
For disconnected clusters, you must configure the NTP servers on the control plane nodes. For more information see the _Additional resources_ section.
13+
14+
.Prerequisites
15+
16+
* You installed the `chrony` package on the target node.
17+
18+
.Procedure
19+
20+
. Log in to the node by using the `ssh` command.
21+
22+
. View the NTP servers available to the node by running the following command:
23+
+
24+
[source,terminal]
25+
----
26+
$ chronyc sources
27+
----
28+
+
29+
.Example output
30+
[source,terminal]
31+
----
32+
MS Name/IP address Stratum Poll Reach LastRx Last sample
33+
===============================================================================
34+
^+ time.cloudflare.com 3 10 377 187 -209us[ -209us] +/- 32ms
35+
^+ t1.time.ir2.yahoo.com 2 10 377 185 -4382us[-4382us] +/- 23ms
36+
^+ time.cloudflare.com 3 10 377 198 -996us[-1220us] +/- 33ms
37+
^* brenbox.westnet.ie 1 10 377 193 -9538us[-9761us] +/- 24ms
38+
----
39+
40+
. Use the `ping` command to ensure that the node can access an NTP server, for example:
41+
+
42+
[source,terminal]
43+
----
44+
$ ping time.cloudflare.com
45+
----
46+
+
47+
.Example output
48+
[source,terminal]
49+
----
50+
PING time.cloudflare.com (162.159.200.123) 56(84) bytes of data.
51+
64 bytes from time.cloudflare.com (162.159.200.123): icmp_seq=1 ttl=54 time=32.3 ms
52+
64 bytes from time.cloudflare.com (162.159.200.123): icmp_seq=2 ttl=54 time=30.9 ms
53+
64 bytes from time.cloudflare.com (162.159.200.123): icmp_seq=3 ttl=54 time=36.7 ms
54+
...
55+
----

‎modules/ipi-install-network-requirements.adoc

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
// * installing/installing_bare_metal_ipi/ipi-install-prerequisites.adoc
44

55
:_content-type: CONCEPT
6-
[id='network-requirements_{context}']
6+
[id="network-requirements_{context}"]
77
= Network requirements
88

99
Installer-provisioned installation of {product-title} involves several network requirements. First, installer-provisioned installation involves an optional non-routable `provisioning` network for provisioning the operating system on each bare metal node. Second, installer-provisioned installation involves a routable `baremetal` network.
@@ -49,7 +49,7 @@ Certain ports must be open between cluster nodes for installer-provisioned insta
4949

5050
Before deploying {product-title}, increase the network maximum transmission unit (MTU) to 1500 or more. If the MTU is lower than 1500, the Ironic image that is used to boot the node might fail to communicate with the Ironic inspector pod, and inspection will fail. If this occurs, installation stops because the nodes are not available for installation.
5151

52-
[id='network-requirements-config-nics_{context}']
52+
[id="network-requirements-config-nics_{context}"]
5353
== Configuring NICs
5454

5555
{product-title} deploys with two networks:
@@ -67,7 +67,7 @@ The `provisioning` network is optional, but it is required for PXE booting. If y
6767
When using a VLAN, each NIC must be on a separate VLAN corresponding to the appropriate network.
6868
====
6969

70-
[id='network-requirements-dns_{context}']
70+
[id="network-requirements-dns_{context}"]
7171
== DNS requirements
7272

7373
Clients access the {product-title} cluster nodes over the `baremetal` network. A network administrator must configure a subdomain or subzone where the canonical name extension is the cluster name.
@@ -120,14 +120,14 @@ For example, `console-openshift-console.apps.<cluster_name>.<base_domain>` is us
120120
You can use the `dig` command to verify DNS resolution.
121121
====
122122

123-
[id='network-requirements-dhcp-reqs_{context}']
123+
[id="network-requirements-dhcp-reqs_{context}"]
124124
== Dynamic Host Configuration Protocol (DHCP) requirements
125125

126126
By default, installer-provisioned installation deploys `ironic-dnsmasq` with DHCP enabled for the `provisioning` network. No other DHCP servers should be running on the `provisioning` network when the `provisioningNetwork` configuration setting is set to `managed`, which is the default value. If you have a DHCP server running on the `provisioning` network, you must set the `provisioningNetwork` configuration setting to `unmanaged` in the `install-config.yaml` file.
127127

128128
Network administrators must reserve IP addresses for each node in the {product-title} cluster for the `baremetal` network on an external DHCP server.
129129

130-
[id='network-requirements-reserving-ip-addresses_{context}']
130+
[id="network-requirements-reserving-ip-addresses_{context}"]
131131
== Reserving IP addresses for nodes with the DHCP server
132132

133133
For the `baremetal` network, a network administrator must reserve a number of IP addresses, including:
@@ -179,7 +179,14 @@ The following table provides an exemplary embodiment of fully qualified domain n
179179
If you do not create DHCP reservations, the installer requires reverse DNS resolution to set the hostnames for the Kubernetes API node, the provisioner node, the control plane nodes, and the worker nodes.
180180
====
181181

182-
[id='network-requirements-ntp_{context}']
182+
[id="network-requirements-provisioner_{context}"]
183+
== Provisioner node requirements
184+
185+
You must specify the MAC address for the provisioner node in your installation configuration. The `bootMacAddress` specification is typically associated with PXE network booting. However, the Ironic provisioning service also requires the `bootMacAddress` specification to identify nodes during the inspection of the cluster, or during node redeployment in the cluster.
186+
187+
The provisioner node requires layer 2 connectivity for network booting, DHCP and DNS resolution, and local network communication. The provisioner node requires layer 3 connectivity for virtual media booting.
188+
189+
[id="network-requirements-ntp_{context}"]
183190
== Network Time Protocol (NTP)
184191

185192
Each {product-title} node in the cluster must have access to an NTP server. {product-title} nodes use NTP to synchronize their clocks. For example, cluster nodes use SSL certificates that require validation, which might fail if the date and time between the nodes are not in sync.
@@ -191,7 +198,7 @@ Define a consistent clock date and time format in each cluster node's BIOS setti
191198

192199
You can reconfigure the control plane nodes to act as NTP servers on disconnected clusters, and reconfigure worker nodes to retrieve time from the control plane nodes.
193200

194-
[id='network-requirements-out-of-band_{context}']
201+
[id="network-requirements-out-of-band_{context}"]
195202
== Port access for the out-of-band management IP address
196203

197204
The out-of-band management IP address is on a separate network from the node. To ensure that the out-of-band management can communicate with the provisioner node during installation, the out-of-band management IP address must be granted access to port `6180` on the provisioner node and on the {product-title} control plane nodes. TLS port `6183` is required for virtual media installation, for example, by using Redfish.

0 commit comments

Comments
 (0)