<commit_before>// Module included in the following assemblies:
//
// * installing/installing_bare_metal_ipi/ipi-install-prerequisites.adoc

[id='network-requirements_{context}']
= Network requirements

Installer-provisioned installation of {product-title} involves several network requirements by default. First, installer-provisioned installation involves a non-routable `provisioning` network for provisioning the operating system on each bare metal node and a routable `baremetal` network. Since installer-provisioned installation deploys `ironic-dnsmasq`, the networks should have no other DHCP servers running on the same broadcast domain. Network administrators must reserve IP addresses for each node in the {product-title} cluster.

.Network Time Protocol (NTP)

Each {product-title} node in the cluster must have access to an NTP server.

.Configuring NICs

{product-title} deploys with two networks:

- `provisioning`: The `provisioning` network is an *optional* non-routable network used for provisioning the underlying operating system on each node that is a part of the {product-title} cluster. When deploying using the `provisioning` network, the first NIC on each node, such as `eth0` or `eno1`,
*must* interface with the `provisioning` network.

- `baremetal`: The `baremetal` network is a routable network. When deploying using the `provisioning` network, the second NIC on each node, such as `eth1` or `eno2`, *must* interface with the `baremetal` network. When deploying without a `provisioning` network, you can use any NIC on each node to interface with the `baremetal` network.

[IMPORTANT]
====
Each NIC should be on a separate VLAN corresponding to the appropriate network.
====

.Configuring the DNS server

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.

----
<cluster-name>.<domain-name>
----
<commit_msg>Clarify NTP server requirement<commit_after>// Module included in the following assemblies:
//
// * installing/installing_bare_metal_ipi/ipi-install-prerequisites.adoc

[id='network-requirements_{context}']
= Network requirements

Installer-provisioned installation of {product-title} involves several network requirements by default. First, installer-provisioned installation involves a non-routable `provisioning` network for provisioning the operating system on each bare metal node and a routable `baremetal` network. Since installer-provisioned installation deploys `ironic-dnsmasq`, the networks should have no other DHCP servers running on the same broadcast domain. Network administrators must reserve IP addresses for each node in the {product-title} cluster.

.Network Time Protocol (NTP)

It is recommended that each {product-title} node in the cluster have access to a Network Time Protocol (NTP) server that is discoverable using DHCP. While installation without an NTP server is possible, asynchronous server clocks can cause errors. Using an NTP server can prevent this issue.

.Configuring NICs

{product-title} deploys with two networks:

- `provisioning`: The `provisioning` network is an *optional* non-routable network used for provisioning the underlying operating system on each node that is a part of the {product-title} cluster. When deploying using the `provisioning` network, the first NIC on each node, such as `eth0` or `eno1`,
*must* interface with the `provisioning` network.

- `baremetal`: The `baremetal` network is a routable network. When deploying using the `provisioning` network, the second NIC on each node, such as `eth1` or `eno2`, *must* interface with the `baremetal` network. When deploying without a `provisioning` network, you can use any NIC on each node to interface with the `baremetal` network.

[IMPORTANT]
====
Each NIC should be on a separate VLAN corresponding to the appropriate network.
====

.Configuring the DNS server

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.

----
<cluster-name>.<domain-name>
----

{'fraction_non_alphanumeric': 0.07171789373361925, 'fraction_numerical': 0.0019061234214915416, 'mean_word_length': 5.128467153284672, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3739504', 'n_tokens_mistral': 1133, 'n_tokens_neox': 1060, 'n_words': 532}