[Simplivity VME] HPE Simplivity Deployment Package issue

[Tony59]

Hello,

I'm currently deploying a new Simplivity VME 2 nodes cluster.

I'm on the step where I have to deploy Virtual Controllers on the cluster thanks to the addon package.

Unfortunately the follwing error appears :

Integration Failed

Integration error: Unable to retrieve cluster information. Close this form and retry the deployment.

I tried many times but still not working.

Support case was open but not answer for now.

Have you ever see this ?

Thank you.

Regards.

[support_s]

System recommended content:

1. HPE SimpliVity VME – SimpliVity Hosts Not Visible During Deployment Of SimpliVity Virtual Controllers Due To Access Token Expiration

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Tony59]

Hello,

Thank you for your answer.

Simplivity version is 6.2.0, the access Token validity value is as default value.

I check log files, nothing significant on orchestrator log, but on current log I see this error:

[2026-08-21 15:01:56,043] [http-nio-127.0.0.1-8080-exec-6] ERROR c.s.d.c.r.r.ActionResult - Failed to authenticate
2026-08-21_15:01:56.04383 'com.simplivity.deploy.common.exceptions.RestAuthenticationException: HMS IP not available in authentication data. Please check integration configuration.

Thank you,

Regards.

[NeetSat]

Hello Tony59

Good day.

As per the log information that HMS IP is not available, could be due to, if the VME Manager IP was changed OR if it is on a different subnet? 
Also you may want to reupload the package just in case and this would be on both the hosts:
Login to both hosts using the hvadmin creds
browse to the directory after evelating to root
cd /scratch/hpe-svt-packages/
Here try to delete the QCOW2 file and re-upload this package as you might have done during the Initial Setup.
Once done, logoff and then login back on the VME Manager and give a try again, it should hopefully proceed with allowing you to see the Hosts to select the NICs for the Storage and Federation.

If you are still facing issues, let us know and we shall have the support team involved.

Regards
NeetSat

[Tony59]

Hello NeetSat,

Thank you for your answer.

I try the plan of action but unfortunately it does'nt work.

Still the same error message and on the logs too :

-2026-08-26 09_32_39.png

Indeed Manager and host are on different subnet, but for troublesh

ooting all is open between these network.

I've already open a case on the support team, it's elevated on level 2 but no feedback for now.

Regards,

Tony

[NeetSat]

Hi Tony59,

Good day

Thank you so much for the confirmation. 

Just wanted to confirm, could you help with, what is the version of the VME manager (Ubuntu) and the Cluster details that was chosen on the Cluster creation please?

Regards,
NeetSat

[Tony59]

Hello NeetSat,

Thank you for your feedback

The version of OS Manager is : Ubuntu 22.04.5 LTS and vme manger 8.0.11-1.

For the cluster details:

Structure : HVM 1.1 Cluster on Ubuntu 22.04

Management net interface : bond-mgmt

Compute net interface: bond-mgmt

CPU Type : x84_64.

Regards.

[NeetSat]

Thank you, Tony59, for providing the details.

It surely does look like something where the support team needs to be involved into further analysis and see what really might be causing this issue, given the fact the details related to VME Manager and Cluster details are all good. 

Could you help provide the case number raised for this issue with the support, so we can check and probably keep the team informed on it? 

Regards
NeetSat