Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Hyper-V – Installing and configuring a virtual SMU

Downloading the SMU OS files

Download the Hyper-V SMU zip file from which you can install the SMU OS.

Before you begin

Verify that you have a suitable Microsoft Hyper-V environment installed and ready to use, such as Microsoft Windows Server 2019 with the Hyper-V role added.

Procedure

  1. Copy the Hyper-V SMU zip file, for example SMU-OS-HYPERV-3.0.zip file to the windows server.

  2. Extract the contents of the zip file to a location that is easy to find, such as C:\VSMU.

Deploying the SMU OS

Deploy the pre-configured SMU OS template.

The SMU-OS-HYPERV-3.0 template is version 9 that can be deployed on a Windows Server 2019 Hyper-V host and above. To deploy on earlier Windows Server versions, instead of importing the VM from the extracted template, you need to create a new VM and then chose an existing VHDX (from the template) during its creation.

Before you begin

  • Create a unique folder in which to store the VM files. The following example uses C:\vSMU\smu1\.
NoteEach virtual SMU that you create needs its own unique ID and its own unique folder.

Procedure

  1. In Hyper-V Manager, in the Actions pane, select Import Virtual Machine.

  2. In the Import Virtual Machine dialog box, click Next.

  3. Click Browse, and then locate the folder that contains the contents of the Hyper-V SMU zip file (C:\vSMU).

  4. Click Select Folder, and then click Next.

  5. Select the SMU OS file, and then click Next.

  6. Select Copy the virtual machine (create a new unique ID), and then click Next.

  7. Select Store the virtual machine in a different location.

    1. In the Virtual Machine configuration folder, Checkpoint store, and Smart Paging folder boxes, enter your folder path (C:\vSMU\smu1\), and then click Next.

  8. In the Location box, again enter your folder path, and then click Next.

  9. On the Connect Network page, an error may indicate that the configuration “Could not find the External Virtual Switch” (a switch that connects through a physical network adapter to a physical network). The template file looks for a virtual switch with a specific name, but it needs only a virtual switch with an external connection type. Either:

    • Select an existing virtual switch with an external connection type from the Connection list.
    • Create a new virtual switch with the Virtual Switch Manager in the Actions pane.
  10. Click Next, review the settings on the Summary tab, and then click Finish.

    A progress bar appears while the system sets up the virtual SMU.

Renaming the virtual SMU VM

Give the virtual SMU VM a unique name.

Note Hyper-V allows more than one VM to have the same name, so give each VM a unique name to avoid any confusion.

Procedure

  1. In Hyper-V Manager, under Virtual Machines, right-click the new VM and select Rename.

  2. Give the VM a unique name.

Modify the SMU VM resource and network settings

Before you add extra managed servers or clusters to the virtual SMU, increase the memory and the CPU resource allocations to reserve sufficient resources for each VM.

The following example is for four managed servers.

Procedure

  1. In Hyper-V Manager, under Virtual Machines, right-click the VM and select Turn Off.

  2. Right-click the VM again and select Settings.

  3. (Best practice*) In the left pane, under Hardware, select Memory.

    1. Change the Startup RAM to 4096 MB.

    2. Select Enable Dynamic Memory. This ensures that Hyper-V receives accurate information about the memory architecture of the host when the VM starts.

    3. Change the Minimum RAM to 4096 MB.

  4. Under Hardware, select Processor.

    1. Change the Number of Virtual Processors to 4.

    2. Click Apply, and then click OK.

  5. Under Settings Network Adaptor configure the adaptor to use a static MAC address. If not using System Center Virtual Machine Manager (SCVMM), assign a static MAC address outside all assigned dynamic ranges of all nodes in the cluster. If using SCVMM, assign a static MAC address from the appropriate pool.

  6. Right-click the VM and select Start.

  7. At the bottom of the Hyper-V Manager dialog box, click the Memory tab and check that all of your settings are correct.

*Best practice

Although resource reservations are not required, it is best to reserve a portion of the host's physical RAM to guarantee the responsiveness of the virtual SMU and its quorum device. Ultimately, if you over provision the host, do so responsibly so that the virtual SMU is not starved of resources.

The critical virtual SMU requirement is that the quorum device must respond to cluster heartbeats (over UDP) within five seconds to prevent the possibility of dependent and degraded HNAS clusters rebooting.

Installing the SMU software

The SMU software is a virtual solution that runs on the Hyper-V server. After you install the SMU OS template, set up and connect the SMU software image to the newly created guest virtual machine.

  1. In Hyper-V Manager, under Virtual Machines, right-click the VM and select Settings.

    1. In the left pane, under Hardware, select DVD drive.

    2. Under Media, select Image File.

    3. Click Browse, and then locate the folder that contains the contents of the Hyper-V zip file.

    4. Select the SMU setup ISO file, and then click Open.

    5. Click Apply, and then click OK.

  2. Under Virtual Machines, right-click the VM, and then select Connect.

  3. On the toolbar, click the Start button GUID-D0681DE7-1656-4798-8DE3-6BAC47E66226-low.png to start the VM console.

  4. Log in as root.

    The default SMU passwords for root and admin can be obtained by service partners and employees via the support site "Hitachi NAS Upgrade, Deployment and Procedures Documentation".
    Note

    The default password for root used by the CentOS Stream 8 template differs from that previously used by the CentOS 6 template.

  5. Run mount /media/cdrom (or mount /media/cdrecorder on CentOS 6).

  6. Run /media/cdrom/autorun (or /media/cdrecorder/autorun on CentOS 6) to start the installation. Note that the installation may take a few minutes to complete, after which the system reboots.

Configuring the SMU software

After you have installed the virtual SMU software, configure the virtual SMU network settings.

  1. In Hyper-V Manager, under Virtual Machines, Right-click the VM and select Connect.

  2. On the toolbar, click the Start button GUID-D0681DE7-1656-4798-8DE3-6BAC47E66226-low.png to start the VM console.

  3. Log in as root.

  4. Run smu-config, and then follow the prompts to configure the network.

  5. Review all of the settings, and then type Y to confirm.

    The script sets up the network interfaces and the default properties, and then the SMU reboots.
  6. On your laptop or desktop, open a web browser and point it to one of the SMU IP addresses.

  7. Log in to NAS Manager with the admin user.

    The NAS Manager GUI opens.GUID-E37CBBD0-5D58-4273-A331-4A0084EB0D4C-low.png
  8. Before you set up the server, navigate to Home SMU Administration SMU Setup Wizard to configure the SMU settings.

    Note

    For more information about using the SMU Setup Wizard, see the

    Server and Cluster Administration Guide.

Guidelines and requirements

Follow these guidelines when you use Hyper-V to ensure that your system operates correctly.

  • Do not manually install or change Linux Integration Services (LIS) on the virtual SMU. Red Hat LIS is set up automatically in software version 12.7.411.xx or later.
  • Avoid using checkpoints (formerly snapshots), as doing so will affect the virtual SMU’s performance.
  • The virtual SMU is a generation 1 VM. The SMU OS does not support generation 2 VMs.
  • The virtual SMU has not been tested with a System Center Virtual Machine Manager (SCVMM) or a VMM guest agent. Use these options at your own risk.
  • Avoid using Dynamic HW MAC Addresses. If not using SCVMM, assign a static MAC Address outside all assigned dynamic ranges of all nodes in the cluster. If using SCVMM, assign a static MAC Address from the appropriate pool.

 

  • Was this article helpful?