1161 content change(s) across 7 bundle(s)
1161 sidecar metadata update(s)
7 new bundle(s) added
Bundles with content changes:
hvm_deployment_guide (NEW): 32 page(s)
- GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA
- GUID-28F18596-4902-4CD1-83F3-1411430C5534
- GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259
- GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C
- GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB
... and 27 more
hvm_release_notes_8_1_0 (NEW): 1 page(s)
- sd00007497en_us
hvm_release_notes_8_1_1 (NEW): 1 page(s)
- sd00007609en_us
hvm_release_notes_8_1_2 (NEW): 1 page(s)
- sd00007734en_us
hvm_user_manual_8_1_0 (NEW): 374 page(s)
- GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
- GUID-02679208-A796-4A58-80AC-33DCF6A4899F
- GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
- GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
- GUID-0503F050-177F-4360-9B1A-49439AF366B8
... and 369 more
hvm_user_manual_8_1_1 (NEW): 376 page(s)
- GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
- GUID-02679208-A796-4A58-80AC-33DCF6A4899F
- GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
- GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
- GUID-0503F050-177F-4360-9B1A-49439AF366B8
... and 371 more
hvm_user_manual_8_1_2 (NEW): 376 page(s)
- GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
- GUID-02679208-A796-4A58-80AC-33DCF6A4899F
- GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
- GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
- GUID-0503F050-177F-4360-9B1A-49439AF366B8
... and 371 more
4.0 KiB
Installing the VM Essentials manager
About this task
Deploy the VM Essentials manager virtual appliance in one of your HVM hosts. The VM Essentials virtual appliance is delivered inside an ISO (HPE_VM_Essentials_SW_image_´*****.iso) containing the needed .qcow2 file; you can either upload the qcow2 file to your HVM host or upload the complete iso and mount it. This example will run you through the ISO method.
Procedure
-
Upload the HPE_VM_Essentials_SW_image_´*****.iso downloaded from My HPE Software Center using your preferred SCP client.
NOTE
There are multiple SCP client options available for Windows client machines.
-
Mount the ISO to a path in your HVM host system:
sudo mount -o loop HPE_VM_Essentials_SW_image_v8.0.12_S5Q83-11039.iso /media
NOTE
- The indicated filename might be different, this is dictated by your download.
- The mount point can be any one you choose, /media is used as an example.
-
Enter
sudo hpe-vmto open the hpe-vm console, and select . -
Fill in the required information.
-
When filling the information, consider the following guidelines:
-
Use the IP address that will be configured for the VM Essentials manager
-
For DNS Server, if multiple entries are needed, a comma-delimited list may be added. Bear in mind, the installer does not currently validate for the proper delimiter. This will be fixed in a future release but for now the user must validate the delimiter for themselves.
-
The appliance URL should be resolvable via DNS (including related PTR record) from the hosts to enable communications between them and the VM Essentials manager.
-
The username is the user with admin privilege that will be used to login to the manager’s CLI.
-
For the Image URI, you can select and browse to the qcow2 file in the ISO you mounted previously
-
If your VM Essentials manager will use the same network for management access as the host’s management network, select the same vlan tagged network interface you configured for the HVM host.
NOTE
Leave the Use Compute VLAN box unchecked unless you want your VM Essentials manager to use a different network than the management one.
-
-
Wait for the installation to finish.
NOTE
At a certain phase in the install process, you’ll see a message in the progress bar modal stating “Starting Morpheus Services…”. At this point, you can direct a web browser to the appliance URL and see if you can access the appliance. If you get a response returned, even if it is just telling you the appliance is still loading, that is a good sign the web server is installed and things are working even if your progress bar seems to get stuck at a high percentage.
The exact time for this installation to complete is highly dependent on the amount of compute available, the size of the network pipe, and the level of network congestion. It is common for this process to take long enough for the "Morpheus is Loading" graphic to change to a timeout graphic. This is not an indicator that the process has failed. If there are no other failure indicators, allow at least an hour before considering the installation to be irrecoverably stuck (though it would be very rare for the process to take anywhere near that length of time). To view the setup logs, run the
sudo morpheus-ctl tail morpheus-uicommand from the manager VM through SSH.


