This guide covers installing and configuring HPE VM Essentials (VME) with StorMagic SvSAN, including the Morpheus Manager and distributed worker, HVM cluster and networking, shared storage, high availability, and validation and troubleshooting.
Information:
The commands and network addresses below document a deployment example. The IP addresses, VLANs, hostnames, and package versions reflect that environment and should be checked against your own configuration and the HPE documentation.
Important:
Some high-availability and storage-recovery steps describe custom lab-tested scripts and configuration rather than standard product installation procedures. Review them against your support and production requirements before implementation. Disk attachment and datastore reformatting operations can affect existing data.
Deploying StorMagic SvSAN on HPE VM Essentials (VME)
Expand each numbered section to follow the deployment process. Code examples and sample outputs are included from the deployment guide.
Install HVM
Example lab environment
Management network — VLAN 80
| Hostname | Management IP address |
|---|---|
ih-hpvme1 |
10.10.80.34/24 |
ih-hpvme2 |
10.10.80.35/24 |
ih-hpworker |
10.10.80.36/24 |
Storage VLANs
| VLAN ID | Physical interface |
|---|---|
206 |
ens2f0 |
306 |
ens2f1 |
Verify that the BIOS settings are optimized for performance and virtualization.
Mount Media and Boot using F11
HPE_HVM_Install_24.04_S5Q83-11092.iso (note there could now be a newer version).
Run through Installation Wizard.
Configure your Bond and VLAN for Management and leave the rest for later.
Example Config
Bond0 VLAN 80
Mount the ISO to your workstation and then copy: (note versions could be different when deploying - verify with HPE-VME documentation).
hpe-vm_1.0.16-1_amd64.deb to both Hosts and HPE_Morpheus_Manager-9.1.0-2.qcow2.gz to the host where you will install Morpheus.
SSH onto the hosts using the user account previously configured.
SSH onto the hosts and set up the time services using chrony
Command to check the existing config
sudo chronyc sources -v
# sample output
root@ih-hpvme1:/tmp# sudo chronyc sources -v
.-- Source mode '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current best, '+' = combined, '-' = not combined,
| / 'x' = may be in error, '~' = too variable, '?' = unusable.
|| .- xxxx [ yyyy ] +/- zzzz
|| Reachability register (octal) -. | xxxx = adjusted offset,
|| Log2(Polling interval) --. | | yyyy = measured offset,
|| \ | | zzzz = estimated error.
|| | | \
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^? prod-ntp-4.ntp1.ps5.cano> 0 10 0 - +0ns[ +0ns] +/- 0ns
^? prod-ntp-3.ntp4.ps5.cano> 0 10 0 - +0ns[ +0ns] +/- 0ns
^? prod-ntp-5.ntp1.ps5.cano> 0 10 0 - +0ns[ +0ns] +/- 0ns
^? alphyn.canonical.com 0 10 0 - +0ns[ +0ns] +/- 0ns
^? ntpsvr1.npl.co.uk 0 10 0 - +0ns[ +0ns] +/- 0ns
^? ntpsvr2.npl.co.uk 0 10 0 - +0ns[ +0ns] +/- 0ns
^? ntp0.sotaconnect.net 0 10 0 - +0ns[ +0ns] +/- 0ns
^? ntp5.leontp.com 0 10 0 - +0ns[ +0ns] +/- 0ns
^? slideaway.preshweb.co.uk 0 10 0 - +0ns[ +0ns] +/- 0ns
^? ntp01.ix1.inferno.net.uk 0 10 0 - +0ns[ +0ns] +/- 0ns
^? mail.fangfufu.co.uk 0 10 0 - +0ns[ +0ns] +/- 0ns
^? pool.ntp1.cam.ac.uk 0 10 0 - +0ns[ +0ns] +/- 0ns
root@ih-hpvme1:/tmp#
NOTE the ^? = not able to connect.
edit the config file and restart the services
sudo vi /etc/chrony/chrony.conf
restart services and check again
sudo systemctl restart chrony
sudo chronyc sources -v
Output
smadmin@sm-node1:~$ sudo systemctl restart chrony
smadmin@sm-node1:~$ sudo chronyc sources -v
.-- Source mode '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current best, '+' = combined, '-' = not combined,
| / 'x' = may be in error, '~' = too variable, '?' = unusable.
|| .- xxxx [ yyyy ] +/- zzzz
|| Reachability register (octal) -. | xxxx = adjusted offset,
|| Log2(Polling interval) --. | | yyyy = measured offset,
|| \ | | zzzz = estimated error.
|| | | \
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* pool.ntp1.cam.ac.uk 3 6 17 3 -3281ns[+5444ns] +/- 5159us
NOTE the ^* means it can connect.
Update version of HPE-VM on the hosts (if required).
sudo chmod +x hpe-vm_1.0.15-1_amd64.deb
sudo apt install ./hpe-vm_1.0.15-1_amd64.deb
# Confirm the new version has been installed
sudo hpe-vm
Repeat on Other Node
Deploy VME Manager (Morpheus appliance).
On Node 1, or whichever node will host the VME Manager (Morpheus appliance),
launch the hpe-vm tool
sudo hpe-vm
Configure the Manager by filling in the required fields
Note: Enter the subnet mask in dotted-decimal notation (for example, 255.255.255.0), not CIDR prefix notation (for example, /24).
Note: In this example the option is Small VM size = 100GB footprint - this can differ according to requirements.
Wait for install to complete
Completed successfully
Continue Configuring in the Morpheus UI
Follow the setup wizard.
Configure backups as required. Backups were not configured in this lab (excluding the VSAs).
License or accept the default 60 days eval
Complete form and press SAVE.
Create the Group
Infrastructure > Groups > Create - Fill in details.
- Note: Advanced options are only relevant if wanting to enforce extended Morpheus platform capabilities (such as multi-cloud orchestration, role-based governance across multiple clusters, and integrated provisioning workflows) otherwise the default of embedded console is ok and advanced options may be skipped.
Create the Cloud
- Infrastructure > Clouds > Create > Private Cloud - Morpheus Click next and follow the wizard - Select the group created in previous step
- Note: DO NOT SELECT worker from the dropdown - LEAVE BLANK
Install and configure the worker
Install a standard Ubuntu 24.04 server (another Linux distribution may be used; check the HPE documentation).
Steps below to configure correct Time
# install updates
sudo apt update && sudo apt upgrade -y
# install chrony
sudo apt install chrony
# enable the chrony service
sudo systemctl status chrony --no-pager
sudo systemctl enable --now chrony
# configure the time server
sudo vi /etc/chrony/chrony.conf
Comment out current non reachable services and add
server 10.25.1.12 iburst
#pool ntp.ubuntu.com iburst maxsources 4
#pool 0.ubuntu.pool.ntp.org iburst maxsources 1
#pool 1.ubuntu.pool.ntp.org iburst maxsources 1
#pool 2.ubuntu.pool.ntp.org iburst maxsources 2
server 10.25.1.12 iburst
# restart and check again
smadmin@ih-hpworker:~$ sudo systemctl restart chrony
smadmin@ih-hpworker:~$ sudo chronyc sources -v
.-- Source mode '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current best, '+' = combined, '-' = not combined,
| / 'x' = may be in error, '~' = too variable, '?' = unusable.
|| .- xxxx [ yyyy ] +/- zzzz
|| Reachability register (octal) -. | xxxx = adjusted offset,
|| Log2(Polling interval) --. | | yyyy = measured offset,
|| \ | | zzzz = estimated error.
|| | | \
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* 10.25.1.12 3 6 17 4 -16us[-6581ns] +/- 5507us
smadmin@ih-hpworker:~$ date
Fri 9 Oct 15:21:07 UTC 2026
smadmin@ih-hpworker:~$
Upload the Installation file
winscp or scp the worker install file
HPE_Morpheus_Manager_Appliance_9.1.0-1_Worker_debian_x86_64_S6E64-11274.deb
Install worker Software
# make file executable
-rw-rw-r-- 1 smadmin smadmin 114005396 Sep 2 10:15 HPE_Morpheus_Enterprise_Appliance_9.0.2-1_Worker_debian_x86_64_S6E64-11256.deb
smadmin@ih-hpworker:~$ chmod +x HPE_Morpheus_Enterprise_Appliance_9.0.2-1_Worker_debian_x86_64_S6E64-11256.deb
smadmin@ih-hpworker:~$ sudo apt install -y ./HPE_Morpheus_Enterprise_Appliance_9.0.2-1_Worker_debian_x86_64_S6E64-11256.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'morpheus-worker' instead of './HPE_Morpheus_Enterprise_Appliance_9.0.2-1_Worker_debian_x86_64_S6E64-11256.deb'
The following packages were automatically installed and are no longer required:
libfwupd2 libgusb2
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
morpheus-worker
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/114 MB of archives.
After this operation, 399 MB of additional disk space will be used.
Get:1 /home/smadmin/HPE_Morpheus_Enterprise_Appliance_9.0.2-1_Worker_debian_x86_64_S6E64-11256.deb morpheus-worker amd64 9.0.2-1 [114 MB]
Selecting previously unselected package morpheus-worker.
(Reading database ... 89250 files and directories currently installed.)
Preparing to unpack .../HPE_Morpheus_Enterprise_Appliance_9.0.2-1_Worker_debian_x86_64_S6E64-11256.deb ...
Unpacking morpheus-worker (9.0.2-1) ...
Setting up morpheus-worker (9.0.2-1) ...
Thank you for installing Morpheus Worker!
Configure and start the Worker by running the following command:
sudo morpheus-worker-ctl reconfigure
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...
Running kernel seems to be up-to-date.
The processor microcode seems to be up-to-date.
Restarting services...
Service restarts being deferred:
/etc/needrestart/restart.d/dbus.service
systemctl restart systemd-logind.service
systemctl restart unattended-upgrades.service
No containers need to be restarted.
User sessions running outdated binaries:
smadmin @ session #176: sshd[5625]
smadmin @ user manager service: systemd[5631]
No VM guests are running outdated hypervisor (qemu) binaries on this host.
N: Download is performed unsandboxed as root as file '/home/smadmin/HPE_Morpheus_Enterprise_Appliance_9.0.2-1_Worker_debian_x86_64_S6E64-11256.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
smadmin@ih-hpworker:~$
Proceed to configure worker
sudo morpheus-worker-ctl reconfigure
[reconfigure] Starting Morpheus Worker reconfiguration...
[reconfigure] Parsing /etc/morpheus/morpheus-worker.rb ...
[reconfigure] Worker URL: https://ih-hpworker
[reconfigure] Appliance URL: YOUR_MORPHEUS_APPLIANCE
[reconfigure] Server name: ih-hpworker
[reconfigure] SSL enabled: true
[reconfigure] Guacd enabled: true
[reconfigure] Set /proc/sys/fs/file-max to 1000000
[reconfigure] Generating SSL private key...
[reconfigure] Generating self-signed SSL certificate...
[reconfigure] Using pre-generated DH parameters.
[reconfigure] SSL configuration complete.
Doing /etc/morpheus/ssl/trusted_certs
[reconfigure] Generating application.yml ...
[reconfigure] Generating worker environment file...
[reconfigure] Generating nginx configuration...
[reconfigure] Configuring log rotation (matching svlogd defaults)...
[reconfigure] Log rotation configured.
[reconfigure] Restarting services...
[reconfigure] Worker service restarted.
[reconfigure] Nginx service restarted.
[reconfigure] Guacd service restarted.
[reconfigure]
[reconfigure] Reconfiguration complete!
This will create a file here: /etc/morpheus/morpheus-worker.rb
Which needs to be configured after adding the Worker to MorpheusUI.
Add Distributed Worker to the Morpheus UI
Administration > Integrations > Distributed Workers > + Add Worker
This will create an API Key and this is needed to finish configuring the worker.
Complete configuration on the worker server
On the Shell prompt of the worker configure the following using the API key just created.
Example below.
# Example config based on the api key generated in the previous steps.
sudo vi /etc/morpheus/morpheus-worker.rb
## Url on which Morpheus Worker will be reachable.
## For more details on configuring worker_url see:
## https://docs.morpheusdata.com
worker_url 'https://ih-hpworker'
worker['appliance_url'] = 'https://10.10.80.37/'
worker['apikey'] = '98a55f28-c105-4359-851a-b6df6a04c86a'
worker['worker_key'] = '98a55f28-c105-4359-851a-b6df6a04c86a'
smadmin@ih-hpworker:~$
# Then reconfigure
smadmin@ih-hpworker:~$ sudo morpheus-worker-ctl reconfigure
[reconfigure]
[reconfigure] Reconfiguration complete!
# check if working
smadmin@ih-hpworker:~$ sudo morpheus-worker-ctl tail worker
==> /var/log/morpheus-worker/worker/current <==
*******************************************'
16:00:00.603 [main] INFO c.m.worker.quorum.QuorumCheckService [] - Loading Persisted Cluster Nodes
16:00:01.082 [main] WARN i.m.h.c.n.ssl.NettyClientSslBuilder [] - HTTP Client is configured to trust all certificates ('insecure-trust-all-certificates' is set to true). Trusting all certificates is not secure and should not be used in production.
16:00:01.208 [main] INFO c.m.worker.appliance.MorpheusClient [] - Post construct
16:00:01.213 [main] INFO c.m.worker.appliance.MorpheusClient [] - Initializing Websocket Connection to Appliance...
16:00:02.524 [nioEventLoopGroup-3-1] INFO c.m.a.w.WebSocketClientHandler [] - WebSocket Client connected!
16:00:03.528 [main] INFO c.m.worker.appliance.MorpheusClient [] - Stomp Client Connection Status: true
16:00:03.807 [main] INFO c.m.w.c.WebSocketDeflateCustomizer [] - Registering WebSocket Compression Handler
16:00:03.838 [main] INFO io.micronaut.runtime.Micronaut [] - Startup completed in 3858ms. Server Running: http://localhost:8080
==> /var/log/morpheus-worker/nginx/error.log <==
==> /var/log/morpheus-worker/nginx/morpheus-worker-ssl-access.log <==
Create HVM Cluster
Note: Ensure DNS is working properly and all hosts can resolve IP addresses and hostnames. If DNS is hosted within the cluster, consider configuring /etc/hosts on each host and the worker.
Add the nodes and specify:
- Hostname and IP
- SSH USERNAME
- SSH PASSWORD
- MANAGEMENT NET INTERFACE + other Networking options (depending on how complex the network is )
- Power Policy = High Performance
- witness worker = worker previously installed (if you cannot see this - check connectivity etc)
- uncheck Bypass Proxy.
This example is just a very simple Network layout with the bond0.80 VLAN created when deploying the hosts for Management.
Confirm config and press Complete.
Progress can be checked by drilling into the Cluster and viewing the History
Prepare Hosts for SvSAN Cluster
Configure Networking
If using the hpe-vm tool, configure networking from the physical NIC through the remaining layers.
Create Interfaces
On both Servers the 10Gbps links are:
10: ens2f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 80:30:e0:14:d6:a0 brd ff:ff:ff:ff:ff:ff
altname enp55s0f0
11: ens2f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 80:30:e0:14:d6:a4 brd ff:ff:ff:ff:ff:ff
altname enp55s0f1
- ens2f0 = vlan 206 = iscsi1
- ens2f1 = vlan 306 = iscsi2
- Create for each one & set MTU 9000
Create VLANs
- select link
- VLAN id
- MTU size
Repeat for other interface
This configuration can also be performed through the Morpheus web UI.
Network > Routers > + Add
Example Below is for the iscsi2brg (These steps can be repeated for other Network Routers/bridges).
End result
Check on the hosts using the ovs-vsctl commands.
smadmin@sm-host1:~/Install$ sudo ovs-vsctl show
1e329916-8dc7-4c65-8bde-c9be60d56d94
Bridge iscsi2brg
Port iscsi2brg
Interface iscsi2brg
type: internal
Port ens2f1.306
Interface ens2f1.306
Bridge iscsi1brg
Port ens2f0.206
Interface ens2f0.206
Port iscsi1brg
Interface iscsi1brg
type: internal
Bridge mgmt
fail_mode: standalone
Port vnet0
Interface vnet0
Port bond0.80
Interface bond0.80
Port mgmt
Interface mgmt
type: internal
ovs_version: "3.3.9"
smadmin@sm-host1:~/Install$
Create iSCSI bridges on Both hosts
- Repeat for other interfaces.
End result
smadmin@sm-host2:/etc/netplan$ sudo virsh net-list --all
Name State Autostart Persistent
-----------------------------------------------
iscsi1brg active yes yes
iscsi2brg active yes yes
Management active yes yes
smadmin@sm-host2:/etc/netplan$
- Repeat the configuration on the second host before proceeding.
For the Open vSwitch configuration shown, verify that Spanning Tree is disabled (false). Consult with Network Admin to confirm the settings.
Final recommended configuration adjustment for the management interface
parameters:
mode: active-backup
mii-monitor-interval: 100
up-delay: 200
down-delay: 200
Repeat both Nodes.
Example Netplan for a Simple Management, and two iSCSI/Mirror Network Topology.
network:
version: 2
ethernets:
eno1: {}
eno2: {}
ens2f0:
mtu: 9000
ens2f1:
mtu: 9000
vlans:
bond0.80:
id: 80
link: bond0
ens2f0.206:
mtu: 9000
id: 206
link: ens2f0
ens2f1.306:
mtu: 9000
id: 306
link: ens2f1
bridges:
mgmt:
addresses:
- 10.10.80.35/24
nameservers:
addresses:
- 10.10.80.254
search:
- ts.stormagic.com
interfaces:
- bond0.80
openvswitch: {}
routes:
- to: default
via: 10.10.80.254
iscsi1brg:
addresses:
- 172.16.26.35/24
mtu: 9000
interfaces:
- ens2f0.206
parameters:
stp: false
openvswitch:
rstp: false
iscsi2brg:
addresses:
- 172.16.36.35/24
mtu: 9000
interfaces:
- ens2f1.306
parameters:
stp: false
openvswitch:
rstp: false
bonds:
bond0:
interfaces:
- eno2
- eno1
parameters:
mode: active-backup
mii-monitor-interval: 100
up-delay: 200
down-delay: 200
Useful Commands for Checking/correcting config
# to check the Open vSwitch configuration for any issues
sudo ovs-vsctl show
Check for any errors such as:
error: "could not add network device iscsi2brg to ofproto (File exists)"
# to drill into particular config
ovs-vsctl list-ports iscsi2brg
# if there are ports that have been added that should not be there
ovs-vsctl del-port iscsi2brg bond0
# 3. Apply the updated Netplan
sudo netplan apply
Deploy SvSAN
Step 1 upload the OVA/ISO
Library > Virtual Images. + Add VMware (vmdk/ovf/ova)
Fill in Details
- OS = Red Hat 8 64-bit
- 2 GB RAM
- deselect IS CLOUD INIT ENABLED
-
deselect INSTALL AGENT?
Upload the OVA file
Advanced
- uncheck virtio drivers loaded
Step 2 Deploy the VSA using the OVA
Fill in details and click Next
No Backup
Progress can be tracked in Instances > VSA name > History
Check the console
Configure an IP to then continue the deployment via the web UI using default password: password
Click in Console and navigate to:
Network:
- given hostname
- DNS server
If using DHCP you can navigate via https to the IP given or configure Static
Network Interfaces > Interface 0 > Edit and set the desired IP.
Note: If you are unsure of the interface, use the MAC address and the following virsh command to identify it
# to list all VMs
smadmin@ih-hpvme1:~$ sudo virsh list --all
[sudo] password for smadmin:
Id Name State
-----------------------------
2 ih-morpheus running
3 ih-hpvsa1 running
# to list all the interfaces assgined to a VM or VSA
smadmin@ih-hpvme1:~$ sudo virsh domiflist ih-hpvsa1
Interface Type Source Model MAC
--------------------------------------------------------------
vnet2 bridge mgmt virtio 52:54:00:0c:44:f6
vnet3 bridge iscsi1brg virtio 52:54:00:8d:6a:4e
vnet4 bridge iscsi2brg virtio 52:54:00:6e:6b:4c
smadmin@ih-hpvme1:~$
Then configure in the usual way using the VMConsole.
Step 3 Ensure the VSAs are set to autostart
smadmin@ih-hpvme1:~$ sudo virsh list --all
Id Name State
------------------------------
1 ih-hpvsa1 running
2 ih-morpheus running
3 ih-hpwin2025 running
smadmin@ih-hpvme1:~$ sudo virsh autostart ih-hpvsa1
Domain 'ih-hpvsa1' marked as autostarted
smadmin@ih-hpvme1:~$
# double check Autostart Enable.
smadmin@ih-hpvme1:~$ sudo virsh dominfo ih-hpvsa1
Id: 1
Name: ih-hpvsa1
UUID: 64e25a16-af9d-4363-804c-a951b8a76553
OS Type: hvm
State: running
CPU(s): 1
CPU time: 1761.2s
Max memory: 2097152 KiB
Used memory: 2097152 KiB
Persistent: yes
Autostart: enable
Managed save: no
Security model: apparmor
Security DOI: 0
Security label: libvirt-64e25a16-af9d-4363-804c-a951b8a76553 (enforcing)
Messages: tainted: custom configuration parameters specified
Step 4 Attach storage to the VSA
Note: So far, only single-disk passthrough has been tested; PCI passthrough has not been tested.
Identify the device on the host and attach it to the VSA using virsh. A corresponding HPE VME web UI option was not identified during testing.
# using lsblk - in this example I am using a 1.7T SSD - device sdc
smadmin@ih-hpvme1:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 1.7T 0 disk
├─sda1 8:1 0 1G 0 part /boot/efi
├─sda2 8:2 0 2G 0 part /boot
└─sda3 8:3 0 1.7T 0 part
└─ubuntu--vg-ubuntu--lv 252:0 0 1.7T 0 lvm /
sdb 8:16 1 0B 0 disk
sdc 8:32 0 1.7T 0 disk
smadmin@ih-hpvme1:~$
# check for the id value
smadmin@ih-hpvme1:~$ sudo ls -n /dev/disk/by-id/
total 0
lrwxrwxrwx 1 0 0 10 Oct 8 08:28 dm-name-ubuntu--vg-ubuntu--lv -> ../../dm-0
lrwxrwxrwx 1 0 0 10 Oct 8 08:28 dm-uuid-LVM-yU0Em5hfhPQs6rSzca79QLUg2vl1h9ISuPX9c5N5LZt13KEXldtydblFiRrPbh1Z -> ../../dm-0
lrwxrwxrwx 1 0 0 10 Oct 8 08:28 lvm-pv-uuid-SKm5LT-nCGJ-0d0t-Dq0k-dv2I-aRBo-cXNJJ3 -> ../../sda3
lrwxrwxrwx 1 0 0 9 Oct 8 08:28 scsi-0HPE_LOGICAL_VOLUME_00000000 -> ../../sda
lrwxrwxrwx 1 0 0 10 Oct 8 08:28 scsi-0HPE_LOGICAL_VOLUME_00000000-part1 -> ../../sda1
lrwxrwxrwx 1 0 0 9 Oct 8 08:28 scsi-360000d10001cf79f466d3d4ce73056ab -> ../../sdc **** this is the id for the disk currently in sdc
lrwxrwxrwx 1 0 0 9 Oct 8 08:28 scsi-SHPE_LOGICAL_VOLUME_PEYHC0DRHBY7E0 -> ../../sda
# check how the virtual disks are currenty assigned to the VSA using virsh
smadmin@ih-hpvme1:~$ sudo virsh domblklist ih-hpvsa1
Target Source
------------------------------------------------------------------
sda /var/morpheus/kvm/local/ih-hpvsa1/hvm_1-disk-0-e711dc0
sdb /var/morpheus/kvm/local/ih-hpvsa1/hvm_1-disk-1-b355a0d
# mount disk using a new target and the correct id
Attach with native kernel AIO and caching disabled
sudo virsh attach-disk ih-hpvsa1 \
/dev/disk/by-id/scsi-360000d10001cf79f466d3d4ce73056ab \
sdc \
--targetbus scsi \
--driver qemu \
--subdriver raw \
--cache none \
--io native \
--live \
--persistent
Disk attached successfully
#
smadmin@ih-hpvme1:~$ sudo virsh domblklist ih-hpvsa1
Target Source
------------------------------------------------------------------
sda /var/morpheus/kvm/local/ih-hpvsa1/hvm_1-disk-0-e711dc0
sdb /var/morpheus/kvm/local/ih-hpvsa1/hvm_1-disk-1-b355a0d
sdc /dev/disk/by-id/scsi-360000d10001cf79f466d3d4ce73056ab
Repeat if more disk if using StorMagic SW Raid for instance.
# not explored but there is also an option to use PCI passthrough.
Step 5 Continue configuration in the web UI
Follow deployment wizard:
- Activate license
- configure hostname/domain
- set new password
- Finish wizard and log in with new password
Configure Network
# on the host use sudo virsh domiflist ih-hpvsa1 to identify the correct MAC address
smadmin@ih-hpvme1:~$ sudo virsh domiflist ih-hpvsa1
Interface Type Source Model MAC
--------------------------------------------------------------
vnet2 bridge mgmt virtio 52:54:00:0c:44:f6
vnet3 bridge iscsi1brg virtio 52:54:00:8d:6a:4e
vnet4 bridge iscsi2brg virtio 52:54:00:6e:6b:4c
Configure as required - this example is:
1 x Management - flags management, mirror failover
1 x iSCSI1 - flags mirror and preferred - iSCSI
1 x iSCSI2 - flags mirror and preferred - iSCSI
In this example
52:54:00:8d:6a:4e = iscsi1
52:54:00:6e:6b:4c = iscsi2
- change to MTU 9000
- change interface name
- remove DHCP flag
- configure ip/netmask
- remove Management
- add iSCSI and mirror - preferred
Repeat for other iSCSI/Mirror interfaces
Check Management is set to Mirror - failover
Using ping tool check working to local and remote Host
Repeat for other VSA.
Step 6 Check for any other configuration needed
- ntp server = System > Set System Date & Time
- events management = Events - SMTP/SNMP/Syslog
Step 7 Create Pool
Pools > Create Pool
Select the device, enter a name, and click CREATE
Repeat other VSA.
Create Shared Datastore
Step 1 Network speed test
Before creating the shared storage it is advised to verify that the Mirror network is performing as expected due to nature of a Synchronous Mirrored Target presented over iSCSI.
This is an example of the expected throughput for the 10 Gbps Network Interfaces used in this lab environment.
Step 2 Create Mirrored Target
Create the Target in SvSAN and add Mirror and Partner/witness details
The lightweight StorMagic Witness can be installed on the worker node or a WAAS witness service or any other StorMagic Witness can be used providing this is not running on either of the HPE-VME Cluster nodes.
Step 3 Add SvSAN iSCSI IPs to Cluster in UI
Add iSCSI IP address of the SvSAN VSAs to Cluster in the UI
Clusters > SvSANCluster > iSCSI Add
For each IP add and Save Changes
Example.
Then Actions > Refresh Short
Step 4 Check for Host Initiators and add to ACL in SvSAN
Check the Initiators Tab in the VSAs this should now contain the Hosts IQN
Add these to the ACL of the Target via
Targets > Target Name > Actions > Initiators
Use the + button to add the Host IQN and apply
End Result
Step 5 Customize MPIO and iSCSI Settings
Configure on Both Hosts.
Configure MPIO
#make custom StorMagc.cof
sudo mkdir /etc/multipath/conf.d
# create the StorMagc.conf in the new directory
sudo vi /etc/multipath/conf.d/StorMagc.conf
#use the following config
defaults {
polling_interval 2
max_polling_interval 4
find_multipaths "yes"
}
blacklist {
devnode "^(ram|raw|loop|fd|md|sr|scd|st|sda)[0-9]*"
}
devices {
device {
user_friendly_names "no"
no_path_retry 5
detect_checker "no"
path_checker "tur"
path_grouping_policy "group_by_prio"
detect_prio "no"
prio "alua"
prio_args "exclusive_pref_bit"
hardware_handler "1 alua"
vendor "StorMagc"
product "iSCSI Volume"
}
}
*** save and then restart services and reload config ***
sudo systemctl restart multipathd.service
sudo multipath -r
sudo multipath -ll
Configure iSCSI
# edit the existing .conf file
sudo vi /etc/iscsi/iscsid.conf
# uncomment
node.startup = automatic
#
# comment out
#node.startup = manual
save config.
# test to see if config saved
smadmin@ih-hpvme2:~$ grep "^node.startup" /etc/iscsi/iscsid.conf
node.startup = automatic
Step 6 Log into iSCSI storage from the Hosts
Scan for storage on the Hosts and log into the iSCSI target
# example command to check for iscsi Storage
smadmin@ih-hpvme1:~$ sudo iscsiadm -m discovery -t st -p 172.16.26.38
# output showing all paths available
172.16.36.38:3260,1 iqn.2006-06.com.stormagic:426bba0200000025.datastore
172.16.26.38:3260,1 iqn.2006-06.com.stormagic:426bba0200000025.datastore
172.16.36.39:3260,3 iqn.2006-06.com.stormagic:426bba0200000025.datastore
172.16.26.39:3260,3 iqn.2006-06.com.stormagic:426bba0200000025.datastore
# log into all paths
smadmin@ih-hpvme1:~$ sudo iscsiadm -m node -l
Logging in to [iface: default, target: iqn.2006-06.com.stormagic:426bba0200000025.datastore, portal: 172.16.26.38,3260]
Logging in to [iface: default, target: iqn.2006-06.com.stormagic:426bba0200000025.datastore, portal: 172.16.26.39,3260]
Logging in to [iface: default, target: iqn.2006-06.com.stormagic:426bba0200000025.datastore, portal: 172.16.36.38,3260]
Logging in to [iface: default, target: iqn.2006-06.com.stormagic:426bba0200000025.datastore, portal: 172.16.36.39,3260]
Login to [iface: default, target: iqn.2006-06.com.stormagic:426bba0200000025.datastore, portal: 172.16.26.38,3260] successful.
Login to [iface: default, target: iqn.2006-06.com.stormagic:426bba0200000025.datastore, portal: 172.16.26.39,3260] successful.
Login to [iface: default, target: iqn.2006-06.com.stormagic:426bba0200000025.datastore, portal: 172.16.36.38,3260] successful.
Login to [iface: default, target: iqn.2006-06.com.stormagic:426bba0200000025.datastore, portal: 172.16.36.39,3260] successful.
# check/confirm settings
smadmin@ih-hpvme1:/$ sudo iscsiadm -m node -o show | grep node.startup
node.startup = automatic
node.startup = automatic
node.startup = automatic
node.startup = automatic
smadmin@ih-hpvme1:/$
# check mpio
# reload the mpio settings to apply the custom settings and check paths
smadmin@ih-hpvme1:/$ sudo multipath -r
[sudo] password for smadmin:
smadmin@ih-hpvme1:/$ sudo multipath -ll
2000339426bba0005 dm-1 StorMagc,iSCSI Volume
size=500G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=50 status=active
|- 2:0:0:0 sdd 8:48 active ready running
|- 3:0:0:0 sde 8:64 active ready running
|- 4:0:0:0 sdf 8:80 active ready running
`- 5:0:0:0 sdg 8:96 active ready running
smadmin@ih-hpvme1:/$
# Check Storage is mounted
smadmin@ih-hpvme1:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 1.7T 0 disk
├─sda1 8:1 0 1G 0 part /boot/efi
├─sda2 8:2 0 2G 0 part /boot
└─sda3 8:3 0 1.7T 0 part
└─ubuntu--vg-ubuntu--lv 252:0 0 1.7T 0 lvm /
sdb 8:16 1 0B 0 disk
sdc 8:32 0 1.7T 0 disk
sdd 8:48 0 500G 0 disk
└─2000339426bba0005 252:1 0 500G 0 mpath
sde 8:64 0 500G 0 disk
└─2000339426bba0005 252:1 0 500G 0 mpath
sdf 8:80 0 500G 0 disk
└─2000339426bba0005 252:1 0 500G 0 mpath
sdg 8:96 0 500G 0 disk
└─2000339426bba0005 252:1 0 500G 0 mpath
Repeat other node
Step 7 Create the GFS2 or HPE Clustered Datastore
In the morpheus UI
Clusters > SvSANCluster > Storage > Add+ Data Stores
Fill in
- Name
- Type = HPE Clustered Datastore (Shared LUN)
- Block Device = dev/mapper/…… (MPIO device)
- Image Target - Designates this datastore as an authorized location for storing virtual machine image templates, ISO files, and system virtual disks (like OS boot volumes).
- Enable Group Access to allow VM provisioning on the datastore (selected by default).
Optional:
- Allow Reformatting - As noted in the UI, if this LUN already contains data or an existing filesystem, enabling this will wipe all existing data.
Datastore creation may take several minutes, and the interface may not immediately show progress. Refresh the page (F5) to check the current status.
If a duplicate GFS2 volume is created or an issue occurs during configuration, it may be necessary to delete the affected volume and restart the creation process.
Expected Result.
Edit the Newly created Datastore to
Enable
- HEARTBEAT TARGET
- SUPPORTS VM SECURE METADATA - important for failover Clustering and if using Secure Boot. (need new screenshot for external documentation with this ticked).
Save Changes.
Set up the HA Configuration
Following is based upon input from our partner Jan Terai at http://dns.sk
The Cluster is recovered based on a combination of the native SvSAN cluster logic and the Morpheus logic with a lightweight timer and service to ensure the hosts reconnect to the iSCSI targets from SvSAN.
With an addition of a multipath optimization using the StorMagc.conf (created in Step 5)
Key Features:
- ALUA-Aware: Respects storage array priority scores and groups paths accordingly.
- Non-Disruptive Recovery: Connects missing iSCSI sessions silently without resetting active I/O queues.
-
State-Aware Optimization: Once all expected paths are successfully established, it triggers a one-time
multipath -rto finalize the load-balanced path groups, setting a state flag so it never runs unnecessarily again. - Fragmentation Correction: Detects if ALUA priorities are upgraded (e.g., after a VSA resync) and automatically merges split priority groups.
- Self-Healing: If a path drops in the future, the state flag is automatically cleared so the system re-optimizes when the path returns.
Note: This is for a graceful recovery that relies on the logic of Morpheus and the SvSAN cluster. If there are issues with the GFS2 mounts this will need to be addressed manually.
When running the script there will be prompts to fill in the following values — gather this information before creating and running the script (or have a duplicate SSH session open).
- Enter TARGET (e.g., iqn.2006-06.com.stormagic:a7784c0200000018.datastore):
# command to generate the target iqn
smadmin@sm-host1:~$ sudo iscsiadm -m session
[sudo] password for smadmin:
tcp: [1] 172.16.26.38:3260,1 iqn.2006-06.com.stormagic:a7784c0200000018.datastore (non-flash)
tcp: [2] 172.16.36.38:3260,1 iqn.2006-06.com.stormagic:a7784c0200000018.datastore (non-flash)
tcp: [3] 172.16.26.39:3260,3 iqn.2006-06.com.stormagic:a7784c0200000018.datastore (non-flash)
tcp: [4] 172.16.36.39:3260,3 iqn.2006-06.com.stormagic:a7784c0200000018.datastore (non-flash)
smadmin@sm-host1:~$
- "Enter WWID (e.g., 2000339a7784c0001):
# command to show the WWID the long number in the output efg. 2000....
smadmin@sm-host1:~$ sudo multipath -ll
2000339a7784c0001 dm-0 StorMagc,iSCSI Volume
size=500G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=50 status=active
|- 2:0:0:0 sdf 8:80 active ready running
|- 3:0:0:0 sdg 8:96 active ready running
|- 4:0:0:0 sdh 8:112 active ready running
`- 5:0:0:0 sdi 8:128 active ready running
smadmin@sm-host1:~$
- Enter PORTALS separated by spaces i.e VSA iSCSI IPs
# if not known they are also dispalyed in the iscsiadm - m session cmd
Create the Script as below.
sudo vi install-stormagic-recovery.sh
Fill in the following.
#!/bin/bash
set -euo pipefail
if [ "$EUID" -ne 0 ]; then
echo "FATAL: This script must be run as root."
exit 1
fi
echo "====================================================="
echo " StorMagic Smart Path Recovery & Optimizer Installer"
echo "====================================================="
echo ""
read -p "Enter TARGET (e.g., iqn.2006-06.com.stormagic:a7784c0200000018.datastore): " INPUT_TARGET
read -p "Enter WWID (e.g., 2000339a7784c0001): " INPUT_WWID
read -p "Enter PORTALS separated by spaces (e.g., 172.16.26.38 172.16.26.39): " INPUT_PORTALS
echo ""
echo "Deploying smart services with your configuration..."
# 1. Create Config File
cat << EOF > /etc/stormagic-recovery.conf
TARGET='$INPUT_TARGET'
WWID='$INPUT_WWID'
PORTALS=($INPUT_PORTALS)
EOF
echo " -> Created /etc/stormagic-recovery.conf"
# 2. Create the Smart Script
cat << 'EOF' > /usr/local/sbin/stormagic-path-recovery.sh
#!/usr/bin/env bash
# StorMagic iSCSI path recovery & smart multipath optimizer.
set -uo pipefail
if [[ -f "/etc/stormagic-recovery.conf" ]]; then
source "/etc/stormagic-recovery.conf"
else
logger -t stormagic-path-recovery "FATAL: /etc/stormagic-recovery.conf not found."
exit 1
fi
MIN_HEALTHY=2
EXPECTED_PATHS="${#PORTALS[@]}"
LOCK="/run/lock/stormagic-path-recovery.lock"
OPT_FLAG="/run/lock/stormagic-multipath-optimized.flag"
log() { printf '%s %s\n' "$(date -Is)" "$*"; logger -t stormagic-path-recovery -- "$*" 2>/dev/null || true; }
for bin in iscsiadm multipath flock awk grep; do
command -v "$bin" >/dev/null 2>&1 || { log "ERROR: missing command $bin"; exit 1; }
done
exec 9>"$LOCK"
flock -n 9 || { log 'Another recovery check is already running; skipping.'; exit 0; }
# 1. Path Recovery Phase
sessions="$(iscsiadm -m session 2>/dev/null || true)"
for portal in "${PORTALS[@]}"; do
if printf '%s\n' "$sessions" | grep -Fq "${portal}:3260,"; then
continue
fi
log "Missing iSCSI session to ${portal}:3260; attempting login"
if timeout 20s iscsiadm -m node -T "$TARGET" -p "${portal}:3260" --login >/dev/null 2>&1; then
log "iSCSI login succeeded: ${portal}:3260"
else
log "WARN: iSCSI login unavailable or failed: ${portal}:3260 (will retry next run)"
fi
done
# 2. Health Check Phase
mp_output="$(multipath -ll "$WWID" 2>/dev/null || true)"
if [[ -z "$mp_output" ]]; then
log "WARN: multipath map $WWID is not available; no filesystem actions taken"
exit 0
fi
healthy="$(printf '%s\n' "$mp_output" | awk '
/[[:space:]]sd[a-z]+[[:space:]]/ && /[[:space:]]active[[:space:]]+ready[[:space:]]+running([[:space:]]|$)/ {n++}
END {print n+0}
')"
session_count="$(iscsiadm -m session 2>/dev/null | grep -Fc "$TARGET" || true)"
log "StorMagic $WWID: healthy_paths=$healthy/$EXPECTED_PATHS active_sessions=$session_count/$EXPECTED_PATHS threshold=$MIN_HEALTHY"
if (( healthy < MIN_HEALTHY )); then
log "WARN: only $healthy healthy multipath paths; storage/HA decisions remain with Morpheus."
fi
# 3. Smart Optimization Phase
# Check if StorMagic upgraded ALUA priorities, resulting in split optimal groups
SPLIT_GROUPS="$(multipath -ll "$WWID" | grep -c "prio=50" || true)"
if (( healthy == EXPECTED_PATHS )); then
if [[ ! -f "$OPT_FLAG" ]] || (( SPLIT_GROUPS > 1 )); then
log "Optimization triggered (Paths: $healthy, Split Priority Groups: $SPLIT_GROUPS). Running multipath -r..."
multipath -r >/dev/null 2>&1 || true
touch "$OPT_FLAG"
log "Multipath optimization complete."
fi
else
# If paths drop below the expected total, remove the flag so it re-optimizes when they return
if [[ -f "$OPT_FLAG" ]]; then
log "Paths dropped to $healthy. Resetting optimization flag for future recovery."
rm -f "$OPT_FLAG"
fi
fi
EOF
echo " -> Created /usr/local/sbin/stormagic-path-recovery.sh"
# 3. Create the Service
cat << 'EOF' > /etc/systemd/system/stormagic-path-recovery.service
[Unit]
Description=Non-disruptive StorMagic iSCSI path recovery and multipath health check
Wants=network-online.target
After=network-online.target
[Service]
Type=oneshot
ExecStart=/usr/local/sbin/stormagic-path-recovery.sh
TimeoutStartSec=120
EOF
echo " -> Created /etc/systemd/system/stormagic-path-recovery.service"
# 4. Create the Timer
cat << 'EOF' > /etc/systemd/system/stormagic-path-recovery.timer
[Unit]
Description=Periodically check and recover StorMagic iSCSI paths
[Timer]
OnBootSec=90s
OnUnitInactiveSec=60s
AccuracySec=10s
Unit=stormagic-path-recovery.service
[Install]
WantedBy=timers.target
EOF
echo " -> Created /etc/systemd/system/stormagic-path-recovery.timer"
# 5. Apply and Activate
chmod +x /usr/local/sbin/stormagic-path-recovery.sh
systemctl daemon-reload
systemctl enable stormagic-path-recovery.timer
systemctl restart stormagic-path-recovery.timer
echo "Installation complete! The script will now automatically optimize multipath once all paths connect."
Save and Make executable and run on BOTH the hosts
chmod +x install-stormagic-recovery.sh
sudo ./install-stormagic-recovery.sh
When running the script you should then be prompted to fill in the following values:
- Enter TARGET (e.g., iqn.2006-06.com.stormagic:a7784c0200000018.datastore):
- "Enter WWID (e.g., 2000339a7784c0001):
- Enter PORTALS separated by spaces
Verification:
Run sudo systemctl list-timers | grep stormagic to confirm the timer is scheduled, and
sudo systemctl status stormagic-path-recovery.timer to ensure it is active and waiting.
REPEAT OTHER NODE
Further HA settings
Pin the VSAs to their local host.
During failover testing in a nested environment, the VSA on host2 attempted to fail over to host1.
To prevent this
Compute > VSA name > Actions > Manage Placement > set the host and select Pinned.
repeat other VSA.
Turn the Morpheus appliance to a managed VM and migrate to the GFS2 Datastore
If running the Morpheus appliance on the shared storage you will need to do the following
Change the VM from a discovered VM to a Managed VM
In the UI click on the VM - Compute > VMs
Then Actions > Convert to Managed
Fill in the details and Execute.
smadmin@ih-morpheus:/var/log/morpheus$ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.5 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
Follow for progress
Move the Morpheus Appliance (VME VM) to the GFS2 Datastore
Actions > Reconfigure
Change Volume to the SvSANDS (GFS2 DS) and Reconfigure.
Check job in History
Note: Do not forget to eject any CD ROMS etc before trying to migrate. This must be done from the Instances menu.
Test Migration
Actions > Manage Placement
progress can be monitored here
Note: In version 9.1, the Move function is comparable to VMware vMotion and Storage vMotion.
Actions > Move
- here you select the Target Host
- Datastore Mapping leave as it is - or you can choose a new Storage Mapping (though it seems for cluster migrations)
- Note there is Target Cloud/Cluster - so it is also for moving between clusters
Guest Deployment
Upload the ISO as you did for the SvSAN deployment
Library > Virtual Image > + Add
Create the Instance
Provisioning > Instance
Install the agent
Note: Ensure the Guest tools have been installed first.
https://www.hpe.com/h40132/filelib/hu/hu/639002843447558642_7e4ac04f3818499d04662c46bfeb329b.pdf
Issues:
Useful Commands/Troubleshooting
Check Quorum of the Cluster from each node
smadmin@ih-hpvme1:~$ sudo grep Quorum /var/log/morpheus-node/morphd/current.log | tail -n 10
# healthy output
026-10-15T08:57:13.290Z [scheduled-executor-thread-45] [] INFO c.m.a.services.QuorumCheckService - Quorum Achieved: 3 of 3 nodes reachable
2026-10-15T08:58:13.289Z [scheduled-executor-thread-82] [] INFO c.m.a.services.QuorumCheckService - Witness credit granted: witness confirms all unreachable peers are also dead to it
2026-10-15T08:58:13.289Z [scheduled-executor-thread-82] [] INFO c.m.a.services.QuorumCheckService - Quorate election: creditWitness=true sameSiteReachable=2 electionsNeeded=2 (stretch=false)
2026-10-15T08:58:13.289Z [scheduled-executor-thread-82] [] INFO c.m.a.services.QuorumCheckService - Quorum Checkup: 3 of 3 nodes reachable (need 2 for quorum)
2026-10-15T08:58:13.289Z [scheduled-executor-thread-82] [] INFO c.m.a.services.QuorumCheckService - Quorum Achieved: 3 of 3 nodes reachable
2026-10-15T08:58:21.926Z [pool-1-thread-682] [] INFO com.morpheus.agent.ActionHandler - handleAction: com.morpheus.agent.services.QuorumStatusAction@5042f8d5
2026-10-15T08:59:13.289Z [scheduled-executor-thread-150] [] INFO c.m.a.services.QuorumCheckService - Witness credit granted: witness confirms all unreachable peers are also dead to it
2026-10-15T08:59:13.289Z [scheduled-executor-thread-150] [] INFO c.m.a.services.QuorumCheckService - Quorate election: creditWitness=true sameSiteReachable=2 electionsNeeded=2 (stretch=false)
2026-10-15T08:59:13.290Z [scheduled-executor-thread-150] [] INFO c.m.a.services.QuorumCheckService - Quorum Checkup: 3 of 3 nodes reachable (need 2 for quorum)
2026-10-15T08:59:13.290Z [scheduled-executor-thread-150] [] INFO c.m.a.services.QuorumCheckService - Quorum Achieved: 3 of 3 nodes reachable
# if communication issues between nodes and worker ensure https connectivity
smadmin@ih-hpvme1:~$ curl -kv https://ih-hpworker
* Uses proxy env variable no_proxy == '10.10.80.37'
* Host ih-hpworker:443 was resolved.
* IPv6: (none)
* IPv4: 10.10.80.36
* Trying 10.10.80.36:443...
* Connected to ih-hpworker (10.10.80.36) port 443
* ALPN: curl offers h2,http/1.1
# check services on the Nodes
smadmin@ih-hpvme1:~$ sudo systemctl status morpheus-morphd
[sudo] password for smadmin:
● morpheus-morphd.service - Morpheus Agent (morphd)
Loaded: loaded (/etc/systemd/system/morpheus-morphd.service; enabled; preset: enabled)
Active: active (running) since Wed 2026-10-14 10:52:11 MDT; 16h ago
Main PID: 14449 (java)
Tasks: 595 (limit: 618621)
Memory: 1.2G (peak: 1.3G)
CPU: 40min 33.568s
CGroup: /system.slice/morpheus-morphd.service
└─14449 /opt/morpheus-node/embedded/java/bin/java -XX:+UseG1GC -Xms32m -Xmx1024m -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -jar /opt/morpheu>
Oct 15 03:15:57 ih-hpvme1 sudo[1022824]: pam_unix(sudo:session): session closed for user root
Oct 15 03:15:57 ih-hpvme1 sudo[1022827]: morpheus-node : PWD=/tmp ; USER=root ; COMMAND=/usr/bin/cat /mnt/494a310b-c67e-42a3-a82c-494ce509dab3/mvm-hb/7f2d4732-91d1-47b7-ac9f-04789771463f-2/10a6b6c9b9627635f859>
Oct 15 03:15:57 ih-hpvme1 sudo[1022827]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=996)
Oct 15 03:15:57 ih-hpvme1 sudo[1022827]: pam_unix(sudo:session): session closed for user root
Oct 15 03:16:01 ih-hpvme1 sudo[1022838]: morpheus-node : PWD=/ ; USER=root ; COMMAND=/usr/bin/timeout 20 virsh domstats --nowait --raw
Oct 15 03:16:01 ih-hpvme1 sudo[1022838]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=996)
Oct 15 03:16:01 ih-hpvme1 sudo[1022838]: pam_unix(sudo:session): session closed for user root
Oct 15 03:16:13 ih-hpvme1 sudo[1022856]: morpheus-node : PWD=/ ; USER=root ; COMMAND=/usr/sbin/dlm_tool ls
Oct 15 03:16:13 ih-hpvme1 sudo[1022856]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=996)
Oct 15 03:16:13 ih-hpvme1 sudo[1022856]: pam_unix(sudo:session): session closed for user root
# main log/directories
root@ih-hpvme1:/var/log/morpheus-node/morphd# ls -l
total 223500
-rw-r--r-- 1 root root 17336316 Oct 15 03:21 current.log
-rw-r--r-- 1 root root 121590499 Oct 15 00:00 current.log.1
-rw-r--r-- 1 root root 17377704 Oct 14 00:00 current.log.2.gz
-rw-r--r-- 1 root root 19310981 Oct 13 00:00 current.log.3.gz
-rw-r--r-- 1 root root 20734408 Oct 12 00:00 current.log.4.gz
-rw-r--r-- 1 root root 32494981 Oct 11 00:00 current.log.5.gz
# scripts
root@ih-hpvme1:/opt/hpe-vm/scripts# ls -l
total 32
-rwxr-xr-x 1 root root 1878 May 21 12:19 build-compute.sh
-rwxr-xr-x 1 root root 10073 May 21 12:19 build-ovs.py
-rwxr-xr-x 1 root root 851 May 21 12:19 build-ovs.sh
-rwxr-xr-x 1 root root 393 May 21 12:19 check_rom.sh
-rwxr-xr-x 1 root root 1348 May 21 12:19 prepare-kvm.sh
-rwxr-xr-x 1 root root 191 May 21 12:19 reset_host.sh
root@ih-hpvme1:/opt/hpe-vm/scripts#
Check the worker logs
smadmin@ih-hpworker:~$ morpheus-worker-ctl tail worker
==> /var/log/morpheus-worker/worker/current <==
09:09:43.575 [scheduled-executor-thread-123] INFO c.m.worker.quorum.QuorumCheckService [] - Checking quorum status for host ih-hpworker in cluster 7f2d4732-91d1-47b7-ac9f-04789771463f
09:09:43.575 [scheduled-executor-thread-123] INFO c.m.worker.quorum.QuorumCheckService [] - Checking quorum status for host ih-hpvme2 in cluster 7f2d4732-91d1-47b7-ac9f-04789771463f
09:10:03.565 [scheduled-executor-thread-43] INFO c.m.worker.quorum.QuorumCheckService [] - Checking quorum status for host ih-hpvme1 in cluster 7f2d4732-91d1-47b7-ac9f-04789771463f
09:10:03.575 [scheduled-executor-thread-43] INFO c.m.worker.quorum.QuorumCheckService [] - Checking quorum status for host ih-hpworker in cluster 7f2d4732-91d1-47b7-ac9f-04789771463f
09:10:03.575 [scheduled-executor-thread-43] INFO c.m.worker.quorum.QuorumCheckService [] - Checking quorum status for host ih-hpvme2 in cluster 7f2d4732-91d1-47b7-ac9f-04789771463f
09:10:03.620 [pool-3-thread-1666] INFO c.m.worker.appliance.MorpheusClient [] - handleAction: com.morpheus.worker.action.QuorumInfoAction@43ccff65
09:10:03.620 [pool-3-thread-1666] INFO c.m.worker.appliance.MorpheusClient [] - handleAction results: [success:true]
09:10:23.565 [scheduled-executor-thread-92] INFO c.m.worker.quorum.QuorumCheckService [] - Checking quorum status for host ih-hpvme1 in cluster 7f2d4732-91d1-47b7-ac9f-04789771463f
09:10:23.575 [scheduled-executor-thread-92] INFO c.m.worker.quorum.QuorumCheckService [] - Checking quorum status for host ih-hpworker in cluster 7f2d4732-91d1-47b7-ac9f-04789771463f
09:10:23.575 [scheduled-executor-thread-92] INFO c.m.worker.quorum.QuorumCheckService [] - Checking quorum status for host ih-hpvme2 in cluster 7f2d4732-91d1-47b7-ac9f-04789771463f
==> /var/log/morpheus-worker/nginx/error.log <==
==> /var/log/morpheus-worker/nginx/morpheus-worker-ssl-access.log <==
10.10.80.34 - - [15/Oct/2026:09:08:53 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.35 - - [15/Oct/2026:09:08:57 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.34 - - [15/Oct/2026:09:09:13 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.35 - - [15/Oct/2026:09:09:17 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.34 - - [15/Oct/2026:09:09:33 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.35 - - [15/Oct/2026:09:09:37 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.34 - - [15/Oct/2026:09:09:53 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.35 - - [15/Oct/2026:09:09:57 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.34 - - [15/Oct/2026:09:10:13 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
10.10.80.35 - - [15/Oct/2026:09:10:17 +0000] "GET /witness/7f2d4732-91d1-47b7-ac9f-04789771463f/quorum HTTP/1.1" 200 397 "-" "Apache-HttpClient/4.5.14 (Java/17.0.14)"
# worker services
morpheus-worker-guacd.service enabled enabled
morpheus-worker-nginx.service enabled enabled
morpheus-worker-worker.service enabled enabled
# main directory
smadmin@ih-hpworker:/var/log/morpheus-worker/worker$ cd ../
smadmin@ih-hpworker:/var/log/morpheus-worker$ ls -l
total 12
drwxr-xr-x 2 guac-morpheus guac-morpheus 4096 Oct 11 00:00 guacd
drwxr-xr-x 2 morpheus-app morpheus-app 4096 Oct 9 15:37 nginx
drwxr-xr-x 2 morpheus-app morpheus-app 4096 Oct 15 00:00 worker
smadmin@ih-hpworker:/var/log/morpheus-worker$
Check the logs on Morpheus Appliance - HPE-VME
# tracking errors when installing agents/migration issues etc
smadmin@ih-morpheus:~$ sudo tail -f /var/log/morpheus/morpheus-ui/current
2026-10-14T15:12:26.31057 at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1009)
2026-10-14T15:12:26.31057 at groovy.lang.Closure.call(Closure.java:433)
2026-10-14T15:12:26.31058 at groovy.lang.Closure.call(Closure.java:412)
2026-10-14T15:12:26.31058 at com.morpheus.util.BoundedExecutor$6.run(BoundedExecutor.java:135)
2026-10-14T15:12:26.31058 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2026-10-14T15:12:26.31058 at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
2026-10-14T15:12:26.31058 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
2026-10-14T15:12:26.31059 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
2026-10-14T15:12:26.31059 at java.base/java.lang.Thread.run(Unknown Source)
2026-10-14T15:12:31.31258 '[2026-10-14T15:12:31.312Z] [appJobHigh-12] [59a759a95d5258441075b0a57266b9c2] WARN c.m.MorpheusComputeService - WinRM Connection Error Occurred. It may not be ready yet to accept con
2026-10-14T15:12:31.31262 ''[2026-10-14T15:12:52.014Z] [appJobHigh-12] [59a759a95d5258441075b0a57266b9c2] ERROR c.m.RpcService - Error Executing WinRM Command via JRuby Task: (WinRMAuthorizationError) WinRM::Wi
2026-10-14T15:12:52.01474 'org.jruby.exceptions.StandardError: (WinRMAuthorizationError) WinRM::WinRMAuthorizationError
# checking the services
smadmin@ih-morpheus:~$ sudo morpheus-ctl status
[sudo] password for smadmin:
run: /opt/morpheus/service/appliance-reporter: (pid 849) 59413s; run: log: (pid 838) 59413s
run: /opt/morpheus/service/check-server: (pid 2276) 59375s; run: log: (pid 853) 59413s
run: /opt/morpheus/service/guacd: (pid 860) 59413s; run: log: (pid 839) 59413s
run: /opt/morpheus/service/morpheus-ui: (pid 2055) 59402s; run: log: (pid 843) 59413s
run: /opt/morpheus/service/mysql: (pid 859) 59413s; run: log: (pid 834) 59413s
run: /opt/morpheus/service/nginx: (pid 877) 59413s; run: log: (pid 841) 59413s
run: /opt/morpheus/service/opensearch: (pid 861) 59413s; run: log: (pid 836) 59413s
run: /opt/morpheus/service/rabbitmq: (pid 868) 59413s; run: log: (pid 844) 59413s
smadmin@ih-morpheus:~$
# main directory
smadmin@ih-morpheus:/var/log/morpheus$ ls -l
total 32
drwxr-x--- 2 morpheus-app morpheus-app 4096 Oct 9 10:36 appliance
drwxr-x--- 2 morpheus-app morpheus-app 4096 Oct 13 11:01 check-server
drwxr-x--- 2 morpheus-app morpheus-app 4096 Oct 14 16:44 guacd
drwxr-x--- 2 morpheus-app morpheus-app 4096 Oct 14 16:44 morpheus-ui
drwxr-x--- 2 mysql-morpheus mysql-morpheus 4096 Oct 13 11:01 mysql
drwxr-x--- 2 morpheus-app morpheus-app 4096 Oct 13 11:01 nginx
lrwxrwxrwx 1 root root 35 Oct 9 10:25 opensearch -> /var/log/morpheus/opensearch-2.19.4
drwxr-x--- 2 es-morpheus es-morpheus 4096 Oct 14 16:44 opensearch-2.19.4
drwxr-x--- 2 rabbitmq-morpheus rabbitmq-morpheus 4096 Oct 13 11:01 rabbitmq
smadmin@ih-morpheus:/var/log/morpheus$
Checking Logs and services
1. Custom Automation Services and dependencies
sudo journalctl -b -u stormagic-path-recovery.timer -u morpheus-morphd.service -u stormagic-path-recovery.service --since "15 minutes ago"
- Check the native iSCSI daemon for login failures or dropped sessions:
sudo journalctl -u iscsid.service --since "24 hours ago"
Look for *connection closed or login failed messages indicating the StorMagic VSA dropped the target.*
- Track multipath routing changes and path failures:
sudo journalctl -k | grep -iE 'multipath|device-mapper'
Because multipath operates at the kernel level, *-k ensures you see when paths are physically added or removed by the OS.*
2. GFS2 and Cluster Locking (The Filesystem Layer)
GFS2 relies entirely on Corosync for quorum and DLM (Distributed Lock Manager) to prevent data corruption. If GFS2 hangs during a mount, it is almost always a lock issue.
- Check kernel logs for GFS2 mount/unmount events:
sudo journalctl -k | grep -i gfs2
GFS2 logs its state directly to the kernel ring buffer. Look for *Joined cluster or recovery complete messages.*
- Check the Distributed Lock Manager for fencing or blocking issues:
sudo journalctl -u dlm.service --since "1 hour ago"
If GFS2 is freezing your terminal when you try to access it, DLM has likely lost contact with Corosync. Use a time filter to narrow the log output.
- Verify Corosync quorum status:
sudo journalctl -u corosync.service | grep -i quorum
4. The "All-in-One" Troubleshooting Command
If the cluster fails a cold start and you need to see exactly how the iSCSI daemon, the kernel, and your custom scripts interacted chronologically, use this combined command for the current boot (-b):
sudo journalctl -b --since "1 hour ago" | grep -iE 'stormagic|iscsi|multipath|gfs2|dlm'
Note: The Morpheus Worker and morpheus-morphd.service manage the associated clustering operations.
See Also
Additional resources and related documentation:

Comments
0 comments
Article is closed for comments.