diff --git a/_includes/configuration-advanced.md b/_includes/configuration-advanced.md
index 007f991b8..45aab6ba8 100644
--- a/_includes/configuration-advanced.md
+++ b/_includes/configuration-advanced.md
@@ -13,75 +13,66 @@ configuration of the appliance:
Description |
-Configure Network |
-Provides options for configuring the network for your {{ site.data.product.title_short }} appliance. The appliance is initially configured as a DHCP client with bridged networking.
-You can use DHCP to obtain the IP address and network configuration for your {{ site.data.product.title_short }} appliance, or use an IPv4 or IPv6 static network configuration by providing specific IP address and network settings.
-This menu also provides options to test the network configuration to check that name resolution is working correctly, and to set the appliance’s host name.
-
- A valid fully qualified hostname for the {{ site.data.product.title_short }} appliance is required for SmartState analysis to work correctly.
- |
-
-
Restore Database from Backup |
Restore the Virtual Management Database (VMDB) from a previous backup. |
-
+
Configure Application |
Configure the VMDB and Kafka. Use this option to configure the database and messaging for the appliance after installing and running it for the first time. |
-
+
Configure Database Replication |
Configure a primary or standby server for VMDB replication. |
-
+
Logfile Configuration |
Provides options for configuring a new logfile disk volume, and changing the saved logrotate count. |
-
+
Configure Application Database Failover Monitor |
Start or stop VMDB failover monitoring. |
-
+
Extend Temporary Storage |
Add temporary storage to the appliance. The appliance formats an unpartitioned disk attached to the appliance host and mounts it at /var/www/miq_tmp . The appliance uses this temporary storage directory to perform certain image download functions. |
-
+
Configure External Authentication (httpd) |
Configure authentication through an IPA server. |
-
+
Update External Authentication Options |
Enable or disable external authentication methods: single sign-on, SAML, and local login. For example, if the current state is Enabled , the prompt indicates the option should be Disabled . |
-
+
Generate Custom Encryption Key |
Regenerate the encryption key used to encode plain text password. |
-
+
Harden Appliance Using SCAP Configuration |
Apply Security Content Automation Protocol (SCAP) standards to the appliance. You can view these SCAP rules in the /var/www/miq/lib/appliance_console/config/scap_rules.yml file. |
-
+
Stop EVM Server Processes |
Stop all server processes. You may need to do this to perform maintenance. |
-
+
Start EVM Server Processes |
Start the server. You may need to do this after performing maintenance. |
-
+
Restart Appliance |
Restart the {{ site.data.product.title_short }} appliance. You can either restart the appliance and clear the logs or just restart the appliance. |
-
+
Shut Down Appliance |
Power down the appliance and exit all processes. |
-
+
Summary Information |
Go back to the network summary screen for the {{ site.data.product.title_short }} appliance. |
-
+
Quit |
Leave the {{ site.data.product.title_short }} appliance console. |
diff --git a/high_availability_guide/_topics/installation.md b/high_availability_guide/_topics/installation.md
index 2d2e50423..2fcbe42ba 100644
--- a/high_availability_guide/_topics/installation.md
+++ b/high_availability_guide/_topics/installation.md
@@ -18,14 +18,8 @@ the non-database {{ site.data.product.title_short }} appliances.
`/etc/chrony.conf` with valid NTP server information.
3. From your host environment, open the appliance and configure the
- network:
-
- 1. Log in to the appliance and run the `appliance_console` command
- to access the appliance console menu.
-
- 2. Configure networking as desired by selecting the **Set DHCP
- Network Configuration** or **Set Static Network Configuration**
- option.
+ network and hostname using nmcli or nmtui from the console or from your
+ web browser using Cockpit on port 9090
4. Resynchronize time information across the appliances:
@@ -34,21 +28,19 @@ the non-database {{ site.data.product.title_short }} appliances.
5. In the appliance console, configure the following:
- 1. Configure the hostname by selecting **Set Hostname**.
+ 1. Select **Configure Application**.
- 2. Select **Configure Application**.
-
- 3. Select **Create key** to create the encryption key. You can
+ 2. Select **Create key** to create the encryption key. You can
create a new key, or use an existing key on your system by
selecting **Fetch key from remote machine** and following the
prompts.
- 4. Select **Create Internal Database**.
+ 3. Select **Create Internal Database**.
- 5. Select the database disk. {{ site.data.product.title_short }} then activates
+ 4. Select the database disk. {{ site.data.product.title_short }} then activates
the configuration.
- 6. For **Should this appliance run as a standalone database
+ 5. For **Should this appliance run as a standalone database
server?**, select `y`. Selecting this option configures this
appliance as a database-only appliance, and therefore the
{{ site.data.product.title_abbr_uc }} application and `evmserverd` processes
@@ -59,7 +51,7 @@ the non-database {{ site.data.product.title_short }} appliances.
This configuration is not reversible.
- 7. Create the database password.
+ 6. Create the database password.
**Note:**
@@ -104,14 +96,8 @@ and secondary database-only appliances can be configured.
`/etc/chrony.conf` with valid NTP server information.
3. From your host environment, open the appliance and configure the
- network:
-
- 1. Log in to the appliance and run the `appliance_console` command
- to access the appliance console menu.
-
- 2. Configure networking as desired by selecting the **Set DHCP
- Network Configuration** or **Set Static Network Configuration**
- option.
+ network and hostname using nmcli or nmtui from the console or from your
+ web browser using Cockpit on port 9090
4. Re-synchronize time information across the appliances:
@@ -120,11 +106,9 @@ and secondary database-only appliances can be configured.
5. In the appliance console, configure the following:
- 1. Configure the hostname by selecting **Set Hostname**.
-
- 2. Select **Configure Application**.
+ 1. Select **Configure Application**.
- 3. Configure this appliance to use the encryption key from the
+ 2. Configure this appliance to use the encryption key from the
primary database-only appliance:
1. For **Encryption Key**, select **Fetch key from remote
@@ -146,7 +130,7 @@ and secondary database-only appliances can be configured.
- 4. Configure the database:
+ 3. Configure the database:
1. Select **Create Region in External Database**, since the
database is external to the appliances.
@@ -164,7 +148,7 @@ and secondary database-only appliances can be configured.
4. For **Are you sure you want to continue?** Select `y`.
- 5. Enter the primary database-only appliance’s name and access
+ 4. Enter the primary database-only appliance’s name and access
details:
1. Enter the hostname for the primary database-only appliance.
@@ -236,23 +220,14 @@ standby appliance to the cluster.
`/etc/chrony.conf` with valid NTP server information.
3. From your host environment, open the appliance and configure the
- network:
-
- 1. Log in to the appliance and run the `appliance_console` command
- to access the appliance console menu.
-
- 2. Configure networking as desired by selecting the **Set DHCP
- Network Configuration** or **Set Static Network Configuration**
- option.
+ network and hostname using nmcli or nmtui from the console or from your
+ web browser using Cockpit on port 9090
4. Re-synchronize time information across the appliances:
# systemctl enable chronyd.service
# systemctl start chronyd.service
-5. In the appliance console, configure the hostname by selecting **Set
- Hostname**.
-
You can now configure this appliance as a standby database-only
appliance in the cluster.
@@ -322,14 +297,8 @@ and any additional appliances in the region using the following steps:
`/etc/chrony.conf` with valid NTP server information.
3. From your host environment, open the appliance and configure the
- network:
-
- 1. Log in to the appliance and run the `appliance_console` command
- to access the appliance console menu.
-
- 2. Configure networking as desired by selecting the **Set DHCP
- Network Configuration** or **Set Static Network Configuration**
- option.
+ network and hostname using nmcli or nmtui from the console or from your
+ web browser using Cockpit on port 9090
4. Re-synchronize time information across the appliances:
@@ -338,11 +307,9 @@ and any additional appliances in the region using the following steps:
5. In the appliance console, configure the following:
- 1. Configure the hostname by selecting **Set Hostname**.
-
- 2. Select **Configure Application**.
+ 1. Select **Configure Application**.
- 3. Configure this appliance to use the encryption key from the
+ 2. Configure this appliance to use the encryption key from the
primary database-only appliance:
1. For **Encryption Key**, select **Fetch key from remote
@@ -363,7 +330,7 @@ and any additional appliances in the region using the following steps:
7. Select **Join Region in External Database** from the
appliance console menu.
- 4. Enter the primary database-only appliance’s name and access
+ 3. Enter the primary database-only appliance’s name and access
details:
1. Enter the hostname for the primary database-only appliance.
diff --git a/high_availability_guide/_topics/renaming_ha_appliances.md b/high_availability_guide/_topics/renaming_ha_appliances.md
index 6f2172088..35d992a18 100644
--- a/high_availability_guide/_topics/renaming_ha_appliances.md
+++ b/high_availability_guide/_topics/renaming_ha_appliances.md
@@ -42,8 +42,8 @@ following:
Run the following steps on your primary database-only appliance:
-1. In the appliance console menu, configure the new hostname or IP
- address from the **Configure Network** option.
+1. Configure the network and hostname using nmcli or nmtui from the console or
+ from your web browser using Cockpit on port 9090
2. Restart the appliance.
@@ -54,8 +54,8 @@ Run the following steps on your primary database-only appliance:
Run the following steps on your standby database-only appliances:
-1. In the appliance console menu, configure the new hostname or IP
- address from the **Configure Network** option.
+1. Configure the network and hostname using nmcli or nmtui from the console or
+ from your web browser using Cockpit on port 9090
2. Restart the appliance.