Merging upstream version 1.44.3.

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

1 files changed, 41 insertions, 0 deletions

diff --git a/health/guides/vsphere/vsphere_inbound_packets_errors.md b/health/guides/vsphere/vsphere_inbound_packets_errors.md
new file mode 100644
index 000000000..ef56fd6ee
--- /dev/null
+++ b/health/guides/vsphere/vsphere_inbound_packets_errors.md
@@ -0,0 +1,41 @@
+### Understand the alert
+
+The `vsphere_inbound_packets_errors` alert is generated when there are inbound network errors in a VMware vSphere virtual machine. It calculates the number of inbound errors for the network interface in the last 10 minutes. If you receive this alert, it indicates that your virtual machine's network is experiencing errors, which could lead to issues with network performance, reliability, or availability.
+
+### Causes of network errors
+
+There are several reasons for network errors, including:
+
+1. Faulty hardware: physical problems with network adapters, cables, or switch ports.
+2. Configuration issues: incorrect network settings or driver issues.
+3. Network congestion: heavy traffic leading to packet loss or delays.
+4. Corrupted packets: data transmission errors caused by software bugs or electro-magnetic interference.
+
+### Troubleshoot the alert
+
+Follow these steps to troubleshoot the `vsphere_inbound_packets_errors` alert:
+
+1. Log in to the vSphere client and select the affected virtual machine.
+
+2. Check the VM's network settings:
+  - Verify that the network adapter is connected.
+  - Check if the network adapter's driver is up-to-date.
+
+3. Review network performance:
+  - Examine the virtual machine's performance charts to identify high network utilization or packet loss.
+  - Use network monitoring tools, like `ping`, `traceroute`, and `mtr`, to check the network connectivity and latency.
+
+4. Inspect the physical network:
+  - Look for damaged cables or disconnected switch ports.
+  - Ensure that the network equipment, like switches and routers, is operating correctly and is up-to-date.
+
+5. Analyze system logs:
+  - Check the virtual machine's logs for any network-related errors or warnings.
+  - Investigate the vSphere host logs for issues involving network hardware or configurations.
+
+6. If errors persist, consult VMware support or documentation for further guidance.
+
+### Useful resources
+
+1. [vSphere Networking Documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-2B11DBB8-CB3C-4AFF-8885-EFEA0FC562F4.html)
+2. [Troubleshooting VMware Network Issues](https://kb.vmware.com/s/article/1004109)