# Monitoring the Cluster

After onboarding the cluster into HPE Morpheus Enterprise, a new Cluster object is added to the Clusters list page. Clicking into the Cluster reveals the Cluster detail page. Note the following subtabs and the cluster details we can monitor in each:

- **Nodes:** Master and worker nodes making up the cluster are shown here. Click into any of them to see a node detail page
- **VMs:** A list of all virtual machines within the scope of the OpenShift cluster are shown. When creating or editing the cluster, an option is given to inventory all existing instances. If selected, all running virtual machines will be onboarded and shown here even if they were provisioned outside of HPE Morpheus Enterprise. If this option is not selected, then only the OpenShift virtual machines provisioned through HPE Morpheus Enterprise are shown. High level details about each virtual machine are also shown, such as power state and resource usage. Click into any virtual machine to see a detail page with additional options
- **Virtual Images:** A list of virtual images synced to HPE Morpheus Enterprise is shown. Only custom user images are synced, images which are part of the large OpenShift default catalog are not synced. Click into any virtual image to see a detail page and to edit configurations for any images, if necessary

  IMPORTANT

  Virtual Images used for provisioning OpenShift workloads from HPE Morpheus Enterprise must be updated to set appropriate properties prior to use. Edit the Virtual Image to uncheck the "Install Agent?" configuration and check either "Is Cloud Init Enabled?" or "Sysprepped/Generalized Image" depending on the workload-type. Ensure the OpenShift template has VirtIO drivers and QEMU VM agent tools installed. For Windows images, only the "Sysprepped/Generalized Image" option is currently supported. Do not use the Cloudbase-init option until support is added. For Linux-based images, HPE Morpheus Enterprise expects standardized NIC names (eth0, eth1, etc) on templates so that cloud-init can reliably apply network configuration. For Windows templates, HPE Morpheus Enterprise relies on OpenShift standard interface naming (ex. Ethernet Instance 0) in templates. Currently on Windows Instances, configuration of the first network interface is supported as part of deployment via Sysprep.
- **Networks:** NetworkAttachmentDefinitions (NADs) define virtual network interfaces that can be attached to VMs, acting as network bridges

IMPORTANT

Edit and update synced network objects (OpenShift NADs) in HPE Morpheus Enterprise with appropriate IPv4/IPv6 configuration details (DHCP, Gateway, DNS, Subnet, etc.)

TIP

IP Pools can be associated with the network definitions synced from OpenShift. These can be Morpheus-type IP Pools created within the HPE Morpheus Enterprise UI or can be IP Pools sourced from IPAM integrations. If IP Pools are used, HPE Morpheus Enterprise can manage IP addresses across the Instance lifecycle (claim a free address at provision time, release an address at teardown, etc)
