Install the HVM ISO on the host ensuring they match the original hosts
Set time zone and NTP on host by following https://vmanalyst.com/part-4-configuring-networking-on-hvm-host/
Record all Network Interfaces correctly by running hvmcli interfaces list –filter ethernet
hvmadmin@hvm-n4:~$ hvmcli interfaces list --filter ethernet
Interface Type MAC Speed Link Driver Firmware SR-IOV Max VFs Configured VFs Manufacturer LLDP
--------- -------- ----------------- ----- ---- ---------- -------- ------------- ------- -------------- ------------- ----
ens1 Ethernet bc:24:11:24:11:f8 - down virtio_net - not supported 0 0 Red Hat, Inc. -
ens18 Ethernet bc:24:11:b1:6a:4d - up virtio_net - not supported 0 0 Red Hat, Inc. -
ens19 Ethernet bc:24:11:a3:38:32 - down virtio_net - not supported 0 0 Red Hat, Inc. -
ens2 Ethernet bc:24:11:04:03:b2 - down virtio_net - not supported 0 0 Red Hat, Inc. -
ens20 Ethernet bc:24:11:67:f0:94 - down virtio_net - not supported 0 0 Red Hat, Inc. -
ens21 Ethernet bc:24:11:e2:6d:16 - down virtio_net - not supported 0 0 Red Hat, Inc. -
ens22 Ethernet bc:24:11:fb:79:4a - down virtio_net - not supported 0 0 Red Hat, Inc. -
ens23 Ethernet bc:24:11:7a:53:06 - down virtio_net - not supported 0 0 Red Hat, Inc. -
hvmadmin@hvm-n4:~$
hvmadmin@hvm-n4:~$
Locate the IQN number on host
hvmadmin@hvm-n4:~$ sudo cat /etc/iscsi/initiatorname.iscsi
[sudo] password for hvmadmin:
## DO NOT EDIT OR REMOVE THIS FILE!
## If you remove this file, the iSCSI daemon will not start.
## If you change the InitiatorName, existing access control lists
## may reject this initiator. The InitiatorName must be unique
## for each iSCSI initiator. Do NOT duplicate iSCSI InitiatorNames.
InitiatorName=iqn.2024-12.com.hpe:hvm-n4:28299
Map existing luns to host
root@sitea-san:~# targetcli /iscsi/iqn.2026-10.lab.sitea:vme/tpg1/acls create iqn.2004-10.com.ubuntu:01:299f839dd87
targetcli saveconfig
Created Node ACL for iqn.2004-10.com.ubuntu:01:299f839dd87
Created mapped LUN 0.
Configuration saved to /etc/rtslib-fb-target/saveconfig.json
In the Manager, go to Cluster → Hosts → Add HVM Hypervisor
Give the hostname
Give the IP details and username to connect to host
In the advanced zone ensure we set domain to our DNS
In the next, nothing needs to be done as it will pick up the settings from current topology so just validate
Again, this will prepopulated for us
Review and Click Finish to add a host
4th host joined to VME Cluster
Run our ping script across all existing nodes to see if it passes
for ip in 172.16.11.{1,5,70,71,72,73} 172.16.12.{71,72,73} 172.16.17.{19,71,72,73} 172.16.18.{19,71,72,73}; do
ping -c1 -W1 $ip >/dev/null && echo "OK $ip" || echo "FAIL $ip"
done
hvmadmin@hvm-n4:~$ for ip in 172.16.11.{1,5,70,71,72,73} 172.16.12.{71,72,73} 172.16.17.{19,71,72,73} 172.16.18.{19,71,72,73}; do
ping -c1 -W1 $ip >/dev/null && echo “OK $ip” || echo “FAIL $ip”
done
OK 172.16.11.1
OK 172.16.11.5
OK 172.16.11.70
OK 172.16.11.71
OK 172.16.11.72
OK 172.16.11.73
OK 172.16.12.71
OK 172.16.12.72
OK 172.16.12.73
OK 172.16.17.19
OK 172.16.17.71
OK 172.16.17.72
OK 172.16.17.73
OK 172.16.18.19
OK 172.16.18.71
OK 172.16.18.72
OK 172.16.18.73
Authenticate to San targets
hvmadmin@hvm-n4:~$ sudo iscsiadm -m discovery -t sendtargets -p 172.16.17.19:326 0
172.16.18.19:3260,1 iqn.2026-10.lab.sitea:vme
172.16.17.19:3260,1 iqn.2026-10.lab.sitea:vme
172.16.17.19:3260,1 iqn.2026-10.lab.sitea:san
hvmadmin@hvm-n4:~$ sudo iscsiadm -m session
iscsiadm: No active sessions.
hvmadmin@hvm-n4:~$ sudo iscsiadm -m node -T iqn.2026-10.lab.sitea:vme --login
Login to [iface: default, target: iqn.2026-10.lab.sitea:vme, portal: 172.16.17.1 9,3260] successful.
Login to [iface: default, target: iqn.2026-10.lab.sitea:vme, portal: 172.16.18.1 9,3260] successful.
hvmadmin@hvm-n4:~$ sudo iscsiadm -m session
tcp: [7] 172.16.17.19:3260,1 iqn.2026-10.lab.sitea:vme (non-flash)
tcp: [8] 172.16.18.19:3260,1 iqn.2026-10.lab.sitea:vme (non-flash)
hvmadmin@hvm-n4:~$ sudo multipath -ll
3600140530d15e7c1cd54047bce911360 dm-0 LIO-ORG,vme_gfs2_01
size=200G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=50 status=active
|- 8:0:0:0 sdc 8:32 active ready running
`- 7:0:0:0 sdb 8:16 active ready running
Validate by moving 1 VM to it.
That’s it to add new hosts in cluster
Placing a host into Maintainence
In the Manager, go to Cluster → Hosts
Go inside the host – Choose Actions – Enter Maintenance
This works similar to DRS so just click Confirm
The host changes to Maintenance status
The host changes to Maintenance mode
