diff --git a/guides/common/assembly_planning-project-server-installation.adoc b/guides/common/assembly_planning-project-server-installation.adoc index 006a9656ba5..5e15761cede 100644 --- a/guides/common/assembly_planning-project-server-installation.adoc +++ b/guides/common/assembly_planning-project-server-installation.adoc @@ -14,4 +14,8 @@ endif::[] include::modules/ref_port-and-firewall-requirements.adoc[leveloffset=+1] +ifeval::["{mode}" == "connected"] +include::modules/ref_ipv6-and-ipv4-requirements.adoc[leveloffset=+1] +endif::[] + include::modules/con_aws-requirements.adoc[leveloffset=+1] diff --git a/guides/common/assembly_preparing-environment-for-project-server-installation.adoc b/guides/common/assembly_preparing-environment-for-project-server-installation.adoc index e9f2f455c3f..776eabaa539 100644 --- a/guides/common/assembly_preparing-environment-for-project-server-installation.adoc +++ b/guides/common/assembly_preparing-environment-for-project-server-installation.adoc @@ -6,14 +6,4 @@ include::modules/proc_enabling-client-connections-to-project-server.adoc[levelof include::modules/proc_verifying-dns-resolution.adoc[leveloffset=+1] -ifdef::installing-satellite-server-connected[] -include::modules/proc_requirements-for-installation-in-an-ipv4-network.adoc[leveloffset=+1] - -include::modules/con_preparing-your-environment-for-project-installation-in-an-ipv6-network.adoc[leveloffset=+1] - -include::modules/con_limitations-of-installation-in-an-ipv6-network.adoc[leveloffset=+2] - -include::modules/con_requirements-for-installation-in-an-ipv6-network.adoc[leveloffset=+2] -endif::[] - include::modules/proc_preparing-for-using-external-databases.adoc[leveloffset=+1] diff --git a/guides/common/modules/con_limitations-of-installation-in-an-ipv6-network.adoc b/guides/common/modules/con_limitations-of-installation-in-an-ipv6-network.adoc deleted file mode 100644 index a167b24c4d9..00000000000 --- a/guides/common/modules/con_limitations-of-installation-in-an-ipv6-network.adoc +++ /dev/null @@ -1,15 +0,0 @@ -:_mod-docs-content-type: CONCEPT - -[id="limitations-of-installation-in-an-ipv6-network_{context}"] -= Limitations of {Project} installation in an IPv6 network - -{Project} installation in an IPv6 network has the following limitations: - -* You can install {Project} and {SmartProxies} in IPv6-only systems, dual-stack installation is not supported. - -* Although {Project} provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the only tested and certified provisioning workflow is the UEFI HTTP Boot provisioning. -This limitation only relates to users who plan to use {Project} to provision hosts. - -* {Project} does not support configuring an HTTP proxy using a direct IPv6 address. -Instead, configure the HTTP proxy with a FQDN that resolves to the IPv6 address. -Using an IPv6 address as the HTTP proxy URL causes it to fail. diff --git a/guides/common/modules/con_preparing-your-environment-for-project-installation-in-an-ipv6-network.adoc b/guides/common/modules/con_preparing-your-environment-for-project-installation-in-an-ipv6-network.adoc deleted file mode 100644 index ac36ac015c6..00000000000 --- a/guides/common/modules/con_preparing-your-environment-for-project-installation-in-an-ipv6-network.adoc +++ /dev/null @@ -1,10 +0,0 @@ -:_mod-docs-content-type: CONCEPT - -[id="preparing-your-environment-for-{project-context}-installation-in-a-ipv6-network"] -= Preparing your environment for {Project} installation in an IPv6 network - -You can install and use {Project} in an IPv6 network. -Before installing {Project} in an IPv6 network, view the limitations and ensure that you meet the requirements. - -To provision hosts in an IPv6 network, after installing {Project}, you must also configure {Project} for the UEFI HTTP boot provisioning. -For more information, see xref:configuring-for-uefi-http-boot-provisioning-in-an-ipv6-network_{context}[]. diff --git a/guides/common/modules/con_requirements-for-installation-in-an-ipv6-network.adoc b/guides/common/modules/con_requirements-for-installation-in-an-ipv6-network.adoc deleted file mode 100644 index 13cec74e51b..00000000000 --- a/guides/common/modules/con_requirements-for-installation-in-an-ipv6-network.adoc +++ /dev/null @@ -1,22 +0,0 @@ -:_mod-docs-content-type: CONCEPT - -[id="requirements-for-installation-in-an-ipv6-network_{context}"] -= Requirements for {Project} installation in an IPv6 network - -Before installing {Project} in an IPv6 network, ensure that you meet the following requirements: - -* You must deploy an external DHCPv6 server and configure it manually to communicate with the network boot process and to manage IP address assignment because {Project} cannot integrate with a DHCPv6 server and manage its configuration. -For more information about DHCPv6 server configuration, see {ProvisioningDocURL}options-in-unmanaged-dhcpv6[Options in unmanaged DHCPv6] in _{ProvisioningDocTitle}_. - -ifdef::satellite[] -* You must deploy an external HTTP proxy server that supports both IPv4 and IPv6. -This is required because Red Hat Content Delivery Network distributes content only over IPv4 networks, therefore you must use this proxy to pull content into the {Project} on your IPv6 network. -endif::[] - -ifndef::satellite[] -* Optional: If you rely on content from IPv4 networks, you must deploy an external IPv4 HTTP proxy server. -This is required to access Content Delivery Networks that distribute content only over IPv4 networks, therefore you must use this proxy to pull content into {Project} on your IPv6 network. -endif::[] - -* You must configure {Project} to use this dual stack (supporting both IPv4 and IPv6) HTTP proxy server as the default proxy. -For more information, see {InstallingServerDocURL}adding-a-default-http-proxy_{project-context}[Adding a Default HTTP Proxy to {Project}]. diff --git a/guides/common/modules/proc_requirements-for-installation-in-an-ipv4-network.adoc b/guides/common/modules/proc_requirements-for-installation-in-an-ipv4-network.adoc deleted file mode 100644 index 1ab5331914a..00000000000 --- a/guides/common/modules/proc_requirements-for-installation-in-an-ipv4-network.adoc +++ /dev/null @@ -1,15 +0,0 @@ -:_mod-docs-content-type: PROCEDURE - -[id="requirements-for-installation-in-an-ipv4-network"] -= Requirements for installation in an IPv4 network - -The following requirements apply to installations in an IPv4 network: - -* An IPv6 loopback must be configured on the base system. -The loopback is typically configured by default. -Do not disable it. -* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter. -ifdef::satellite[] -+ -For a supported way to disable the IPv6 protocol, see link:https://access.redhat.com/solutions/5045841[How do I disable the IPv6 protocol on Red Hat Satellite and/or Red Hat Capsule server?] in Red{nbsp}Hat Knowledgebase. -endif::[] diff --git a/guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc b/guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc new file mode 100644 index 00000000000..a5c592236c0 --- /dev/null +++ b/guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc @@ -0,0 +1,42 @@ +[id="ipv6-and-ipv4-requirements"] += IPv6 and IPv4 requirements + +You can install {Project} in an IPv4 network or in an IPv6 network. +ifdef::satellite[] +Dual-stack {Project} installations that use both IPv4 and IPv6 are not supported. +endif::[] + +The following requirements apply to installations in an IPv4 network: + +* Ensure an IPv6 loopback is configured on the base system. +The loopback is typically configured by default. +Do not disable it. +* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter. + +The following requirements apply to installations in an IPv6 network: + +ifdef::satellite[] +* Deploy an external HTTP proxy server that supports both IPv4 and IPv6. +This is required because Red Hat Content Delivery Network distributes content only over IPv4 networks, therefore you must use this HTTP proxy to pull content into the {Project} on your IPv6 network. +You must configure {Project} to use this dual-stack (supporting both IPv4 and IPv6) HTTP proxy as the default HTTP proxy. +endif::[] +ifndef::foreman-deb,foreman-el,satellite[] +* If you rely on content from IPv4-only networks, use an external dual-stack HTTP proxy. +Configure {Project} to use this dual-stack (supporting both IPv4 and IPv6) HTTP proxy as the default HTTP proxy. +endif::[] +* {Project} does not support configuring an HTTP proxy using a direct IPv6 address. +Instead, configure the HTTP proxy with a FQDN that resolves to the IPv6 address. + +If you intend to provision hosts in an IPv6 network, the following requirements also apply: + +* Deploy an external DHCPv6 server and configure it manually to communicate with the network boot process and to manage IP address assignment because {Project} cannot integrate with a DHCPv6 server and manage its configuration. +For more information about DHCPv6 server configuration, see {ProvisioningDocURL}options-in-unmanaged-dhcpv6[Options in unmanaged DHCPv6] in _{ProvisioningDocTitle}_. +* Configure {Project} for UEFI HTTP boot provisioning. +Although {Project} provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the UEFI HTTP Boot provisioning is the only tested and certified provisioning workflow. +For more information, see xref:common/modules/proc_configuring-for-uefi-http-boot-ipv6-provisioning.adoc#configuring-for-uefi-http-boot-provisioning-in-an-ipv6-network_{context}[]. + +.Additional resources +ifdef::satellite[] +* link:https://access.redhat.com/solutions/5045841[_How do I disable the IPv6 protocol on Red Hat Satellite and/or Red Hat Capsule server?_ in Red Hat Knowledgebase] +endif::[] +* xref:common/modules/proc_adding-a-default-http-proxy.adoc#adding-a-default-http-proxy_{context}[]