We use cookies on this website. To find out more about cookies and how they are used on this website, see our Privacy Policy.
By clicking ‘Continue’, you hereby agree with our use of cookies.

{{vmH.selected.familySearch.replace("EonStor ", "")}} Maintenance Guide

{{vmH.selected.familySearch.replace("EonStor ", "")}} User Guide

Maintenance Guide

Monitoring a Virtual Machine

KS / KS 5000U / KSi 5016U

IEC provides dashboards and monitoring tools to help you monitor the operation of virtual machines and entire Kubernetes clusters. In addition, you can view resource usage of CPU/memory/ and set alerts to notify you when resources reach critical levels. By integrating tools such as Prometheus and Grafana, IEC can provide detailed data analysis and visual reports to help manage and optimize resource usage.

If any of the following issues occur, follow the troubleshooting steps below.

Failed to start a virtual machine

  • View event logs: In the virtual machine details page, view related events and logs to identify the root cause of the problem. This may include issues such as insufficient resources, misconfiguration, or unavailability of dependent Kubernetes resources such as PVCs or networks.
  • Check Resources: Check if the required CPU, memory, and storage are available, and that there are enough nodes to allocate virtual machines. If the virtual machine or cluster resources are insufficient, adjust the resource allocation and/or add nodes.
  • Check the virtual machine configurations: Check if the virtual machine configurations are correct, for example, the boot sequence, settings of the disk and network, etc.

Failed to connect to a virtual machine

  • VNC / Console connection: Check if the virtual machine's network settings are configured correctly and if the VNC server or other remote connection service is running. If you are connecting using SSH or RDP, verify if the IP address and port settings are correct and if the firewall allows the connection.
  • SSH connection: Ensure that the virtual machine is configured with the correct SSH public key and that the key used matches the configuration in the virtual machine. Check if you have the necessary network routing and firewall rules to allow SSH traffic.