Merging upstream version 1.44.3.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

8 files changed, 260 insertions, 0 deletions

diff --git a/health/guides/vcsa/vcsa_applmgmt_health.md b/health/guides/vcsa/vcsa_applmgmt_health.md
new file mode 100644
index 000000000..06f391b3d
--- /dev/null
+++ b/health/guides/vcsa/vcsa_applmgmt_health.md
@@ -0,0 +1,40 @@
+### Understand the alert
+
+The `vcsa_applmgmt_health` alert is related to the health of VMware vCenter Server Appliance (VCSA) components. This alert is triggered when the health of one or more components is in a degraded or critical state, meaning that your VMware vCenter Server Appliance may be experiencing issues.
+
+### Troubleshoot the alert
+
+1. Access the vSphere Client for the affected vCenter Server Appliance
+
+   Log in to the vSphere Client to check detailed health information and manage your VCSA.
+
+2. Check the health status of VCSA components
+
+   In the vSphere Client, navigate to `Administration` > `System Configuration` > `Services` and `Nodes` tab. The component health status will be shown in the `Health` column.
+
+3. Inspect the affected component(s)
+
+   If any components show a status other than "green" (healthy), click on the component to view more details and understand the issue.
+
+4. Check logs related to the affected component(s)
+
+   Access the vCenter Server Appliance Management Interface (VAMI) by navigating to `https://<appliance-IP-address-or-FQDN>:5480` and logging in with the administrator account.
+
+   In the VAMI, click on the `Monitoring` tab > `Logs`. Download and inspect the logs to identify the root cause of the issue.
+
+5. Take appropriate actions
+
+   Depending on the nature of the issue identified, perform the necessary actions or modifications to resolve it. Consult the VMware documentation for recommended solutions for specific component health issues.
+
+6. Monitor the component health
+
+   After performing appropriate actions, continue to monitor the VCSA component health in the vSphere Client to ensure they return to a healthy status.
+
+7. Contact VMware support
+
+   If you are unable to resolve the issue, contact VMware support for further assistance.
+
+### Useful resources
+
+1. [VMware vCenter Server 7.0 Documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-52AF3379-8D78-437F-96EF-25D1A1100BEE.html)
+2. [VMware Support](https://www.vmware.com/support.html)
diff --git a/health/guides/vcsa/vcsa_database_storage_health.md b/health/guides/vcsa/vcsa_database_storage_health.md
new file mode 100644
index 000000000..eb978b07b
--- /dev/null
+++ b/health/guides/vcsa/vcsa_database_storage_health.md
@@ -0,0 +1,33 @@
+### Understand the alert
+
+The `vcsa_database_storage_health` alert monitors the health of database storage components in a VMware vCenter Server Appliance (vCSA). When this alert is triggered, it indicates that one or more components have a health status of Warning, Critical or Unknown.
+
+### What do the different health statuses mean?
+
+- Unknown (`-1`): The system is unable to determine the component's health status.
+- Healthy (`0`): The component is functioning correctly and has no known issues.
+- Warning (`1`): The component is currently operating but may be experiencing minor problems.
+- Critical (`2`): The component is degraded and might have significant issues affecting functionality.
+- Critical (`3`): The component is unavailable or expected to stop functioning soon, requiring immediate attention.
+- No health data (`4`): There is no health data available for the component.
+
+### Troubleshoot the alert
+
+1. **Identify the affected components**: To begin troubleshooting the alert, you need to identify which components are experiencing health issues. You can check the vCenter Server Appliance Management Interface (VAMI) to review the health status of all components.
+
+   - Access the VAMI by navigating to `https://<appliance-IP>/ui` in your web browser.
+   - Log in with your vCenter credentials.
+   - Click on the `Health` tab in the left-hand menu to view the health status of all components.
+
+2. **Investigate the issues**: Once you have identified the affected components, review the alarms and events in vCenter to determine the root cause of the problems. Pay close attention to any recent changes or updates that may have impacted system functionality.
+
+3. **Review the vCenter Server logs**: If necessary, examine the logs in vCenter Server to gather more information about any possible issues. The logs can be accessed via SSH, the VAMI, or using the Log Browser in the vSphere Web Client.
+
+4. **Take corrective actions**: Based on your findings from the previous steps, address the issues affecting the health status of the components.
+
+   - In the case of insufficient storage, increasing the storage capacity or deleting unnecessary files might resolve the problem.
+   - If the issues are caused by hardware failures, consider replacing or repairing the affected hardware components.
+   - For software-related issues, ensure that all components are up-to-date and properly configured.
+
+5. **Monitor the component health**: After taking corrective actions, continue to monitor the health statuses of the affected components through the VAMI to ensure that the issues have been successfully resolved.
+
diff --git a/health/guides/vcsa/vcsa_load_health.md b/health/guides/vcsa/vcsa_load_health.md
new file mode 100644
index 000000000..026138d52
--- /dev/null
+++ b/health/guides/vcsa/vcsa_load_health.md
@@ -0,0 +1,18 @@
+### Understand the alert
+
+The `vcsa_load_health` alert indicates the current health status of the VMware vCenter Server Appliance (VCSA) system components. The color-coded health indicators help quickly understand the overall state of the system.
+
+### Troubleshoot the alert
+
+1. **Log in to the vCenter Server Appliance Management Interface (VAMI):** Open a web browser and navigate to `https://vcsa_address:5480`, where `vcsa_address` is the IP address or domain name of the VCSA. Log in with the appropriate credentials (by default, the `root` user).
+
+2. **Inspect the health status of VCSA components:** Once logged in, go to the `Summary` tab, which displays the health status of various components, such as Database, Management, and Networking. You can hover over the component's health icon to get more information about its status.
+
+3. **Check for specific component warnings or critical issues:** If any component has a warning or critical health status, click on the `Monitor` tab and then on the component in question to get more details about the specific problem.
+
+4. **Review log files:** For further investigation, review the log files associated with the affected VCSA component. The log files can be accessed on the VAMI interface under the `Logs` tab.
+
+5. **Resolve the issue:** Based on the information gathered from the VAMI interface and log files, take appropriate action to resolve the issue or contact VMware support for assistance.
+
+6. **Monitor VCSA Health:** After resolving the issue, monitor the health status of the VCSA components on the `Summary` tab in VAMI to ensure that the health indicators return to a normal state.
+
diff --git a/health/guides/vcsa/vcsa_mem_health.md b/health/guides/vcsa/vcsa_mem_health.md
new file mode 100644
index 000000000..1e3604656
--- /dev/null
+++ b/health/guides/vcsa/vcsa_mem_health.md
@@ -0,0 +1,36 @@
+### Understand the alert
+
+The `vcsa_mem_health` alert indicates the memory health status of a virtual machine within the VMware vCenter. If you receive this alert, it means that the system's memory health could be compromised, and might lead to degraded performance, serious problems, or stop functioning.
+
+### Troubleshoot the alert
+
+1. **Check the vCenter Server Appliance health**:
+   - Log in to the vSphere Client and select the vCenter Server instance.
+   - Navigate to the Monitor tab > Health section.
+   - Check the Memory Health status, and take note of any concerning warnings or critical issues.
+
+2. **Analyze the memory usage**:
+   - Log in to the vSphere Client and select the virtual machine.
+   - Navigate to the Monitor tab > Performance section > Memory.
+   - Evaluate the memory usage trends and look for any unusual spikes or prolonged high memory usage.
+
+3. **Identify processes consuming high memory**:
+   - Log in to the affected virtual machine.
+   - Use the appropriate task manager or command, depending on the OS, to list processes and their memory usage.
+   - Terminate any unnecessary processes that are consuming high memory, but ensure that the process is not critical to system operation.
+
+4. **Optimize the virtual machine's memory allocation**:
+   - If the virtual machine consistently experiences high memory usage, consider increasing the allocated memory or optimizing applications running on the virtual machine to consume less memory.
+
+5. **Update VMware tools**:
+   - Ensuring that the VMware tools are up to date can help in better memory management and improve overall system health.
+
+6. **Check hardware issues**:
+   - If the problem persists, check hardware components such as memory sticks, processors, and data stores for any faults that could be causing the problem.
+
+7. **Contact VMware Support**:
+   - If you can't resolve the `vcsa_mem_health` alert or are unable to identify the root cause, contact VMware Support for further assistance.
+
+### Useful resources
+
+1. [VMware vCenter Server Documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-ACEC0944-EFA7-482B-84DF-6A084C0868B3.html)
diff --git a/health/guides/vcsa/vcsa_software_updates_health.md b/health/guides/vcsa/vcsa_software_updates_health.md
new file mode 100644
index 000000000..505e20f5c
--- /dev/null
+++ b/health/guides/vcsa/vcsa_software_updates_health.md
@@ -0,0 +1,35 @@
+### Understand the alert
+
+The `vcsa_software_updates_health` alert monitors the software updates availability status for a VMware vCenter Server Appliance (VCSA). The alert can have different statuses depending on the software updates state, with critical indicating that security updates are available.
+
+### Troubleshoot the alert
+
+Follow these troubleshooting steps according to the alert status:
+
+1. **Critical (security updates available):**
+
+   - Access the vCenter Server Appliance Management Interface (VAMI) by browsing to `https://<vcsa-address>:5480`.
+   - Log in with the appropriate user credentials (typically `root` user).
+   - Click on the `Update` menu item.
+   - Review the available patches and updates, especially those related to security.
+   - Click `Stage and Install` to download and install the security updates.
+   - Monitor the progress of the update installation and, if needed, address any issues that might occur during the process.
+
+2. **Warning (error retrieving information on software updates):**
+
+   - Access the vCenter Server Appliance Management Interface (VAMI) by browsing to `https://<vcsa-address>:5480`.
+   - Log in with the appropriate user credentials (typically `root` user).
+   - Click on the `Update` menu item.
+   - Check for any error messages in the `Update` section.
+   - Ensure that the VCSA has access to the internet and can reach the VMware update repositories.
+   - Verify that there are no issues with the system time or SSL certificates.
+   - If the issue persists, consider searching for relevant information in the VMware Knowledge Base or contacting VMware Support.
+
+3. **Clear (no updates available, non-security updates available, or unknown status):**
+
+   - No immediate action is required. However, it's a good practice to periodically check for updates to ensure the VMware vCenter Server Appliance remains up-to-date and secure.
+
+### Useful resources
+
+1. [VMware vCenter Server Appliance Management](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-52AF3379-8D78-437F-96EF-25D1A1100BEE.html)
+2. [VMware Knowledge Base](https://kb.vmware.com/)
diff --git a/health/guides/vcsa/vcsa_storage_health.md b/health/guides/vcsa/vcsa_storage_health.md
new file mode 100644
index 000000000..9dbfe69cb
--- /dev/null
+++ b/health/guides/vcsa/vcsa_storage_health.md
@@ -0,0 +1,28 @@
+### Understand the alert
+
+The `vcsa_storage_health` alert indicates the health status of the storage components in your VMware vCenter Server Appliance (vCSA). It notifies you when the storage components are experiencing issues or are at risk of failure.
+
+### Troubleshoot the alert
+
+1. Identify the affected component(s): Check the alert details and note the component(s) with the corresponding health codes to determine their status.
+
+2. Access the vCenter Server Appliance Management Interface (VAMI): Open a supported browser and enter the URL: `https://<appliance-IP-address-or-FQDN>:5480`. Log in with the administrator or root credentials.
+
+3. Navigate to the Storage tab: In the VAMI, click on the 'Monitor' tab and then click on 'Storage.'
+
+4. Analyze the storage health: Review the reported storage health status for each component, match the health status with the information in the alert, and identify any issues.
+
+5. Remediate the issue: Depending on the identified problem, take the necessary actions to resolve the issue. Examples include:
+
+   - Check for any hardware faults and replace faulty components.
+   - Investigate possible disk space issues and free up space or increase the storage capacity.
+   - Verify that the storage subsystem is properly configured, and no misconfigurations are causing the issue.
+   - Look for software issues, such as failed updates, and resolve them or rollback changes.
+   - Consult VMware support if further assistance is needed.
+
+6. Verify resolution: After resolving the issue, verify that the storage health status has improved by checking the current status in the VAMI Storage tab.
+
+### Useful resources
+
+1. [VMware vCenter Server Appliance Management Interface](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-ACEC0944-EFA7-482B-84DF-6A084C0868B3.html)
+2. [VMware vSphere Documentation](https://docs.vmware.com/en/VMware-vSphere/index.html)
diff --git a/health/guides/vcsa/vcsa_swap_health.md b/health/guides/vcsa/vcsa_swap_health.md
new file mode 100644
index 000000000..6e236ed34
--- /dev/null
+++ b/health/guides/vcsa/vcsa_swap_health.md
@@ -0,0 +1,35 @@
+### Understand the alert
+
+The vcsa_swap_health alert presents the swap health status of the VMware vCenter virtual machine. It is an indicator of the overall health of memory swapping on the vCenter virtual machine.
+
+### Troubleshoot the alert
+
+1. First, identify the health status of the alert by checking the color and its corresponding description in the table above.
+
+2. Log in to the VMware vSphere Web Client:
+   - Navigate to `https://<vCenter-IP-address-or-domain-name>:<port>/vsphere-client`, where `<vCenter-IP-address-or-domain-name>` is your vCenter Server system IP or domain name, and `<port>` is the port number over which to access the vSphere Web Client.
+   - Enter the username and password, and click Login.
+
+3. Navigate to the vCenter virtual machine, and select the Monitor tab.
+
+4. Verify the swap file size by selecting the `Performance` tab, and choosing `Advanced` view.
+
+5. Monitor the swap usage on the virtual machine:
+   - On the `Performance` tab, look for high swap usage (`200 MB` or above). If necessary, consider increasing the swap file size.
+   - On the `Summary` tab, check for any warning or error messages related to the swap file or its usage.
+
+6. Check if there are any leading processes consuming an unreasonable amount of memory:
+   - If running a Linux-based virtual machine, use command-line utilities like `free`, `top`, `vmstat`, or `htop`. Look out for processes with high `%MEM` or `RES` values.
+   - If running a Windows-based virtual machine, use Task Manager or Performance Monitor to check for memory usage.
+
+7. Optimize the virtual machine memory settings:
+   - Verify if the virtual machine has sufficient memory allocation.
+   - Check the virtual machine's memory reservation and limit settings.
+   - Consider enabling memory ballooning for a better utilization of available memory.
+
+8. If the swap health status does not improve or you are unsure how to proceed, consult VMware documentation or contact VMware support for further assistance.
+
+### Useful resources
+
+1. [Configuring VMware vCenter 7.0](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-ACEC0944-EFA7-482B-84DF-6A084C0868B3.html)
+2. [Virtual Machine Memory Management Concepts](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/perf-vsphere-memory_management.pdf)
diff --git a/health/guides/vcsa/vcsa_system_health.md b/health/guides/vcsa/vcsa_system_health.md
new file mode 100644
index 000000000..6e58a68dc
--- /dev/null
+++ b/health/guides/vcsa/vcsa_system_health.md
@@ -0,0 +1,35 @@
+### Understand the alert
+
+The `vcsa_system_health` alert indicates the overall health status of your VMware vCenter Server Appliance (vCSA). If you receive this alert, it means that one or more components in the appliance are in a degraded or unhealthy state that could lead to reduced performance or even appliance unresponsiveness.
+
+### Troubleshoot the alert
+
+Perform the following steps to identify and resolve the issue:
+
+1. Log in to the vCenter Server Appliance Management Interface (VAMI).
+
+   You can access the VAMI by navigating to `https://<your_vcenter_address>:5480` in a web browser. Log in with the appropriate credentials.
+
+2. Check the System Health status.
+
+   In the VAMI, click on the `Monitor` tab, and then click on `Health`. This will provide you with an overview of the different components and their individual health status.
+
+3. Analyze the affected components.
+
+   Identify the components that are displaying warning (yellow), degraded (orange), or critical (red) health status. These components may be causing the overall `vcsa_system_health` alert.
+
+4. Investigate the problematic components.
+
+   Click on each affected component to find more information about the issue. This may include error messages, suggested actions, and links to relevant documentation.
+
+5. Resolve the issues.
+
+   Follow the recommended actions or consult the VMware documentation to resolve the issues with the affected components.
+
+6. Verify the system health.
+
+   Once the issues have been resolved, refresh the Health page in the VAMI to ensure that all components now display a healthy (green) status. The `vcsa_system_health` alert should clear automatically.
+
+### Useful resources
+
+1. [VMware vSphere 7.0 vCenter Appliance Management](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-52AF3379-8D78-437F-96EF-25D1A1100BEE.html)