Skip to main content
Hitachi Vantara Knowledge

Installing the SVP software on a VMware ESXi host

You can use a virtual SVP with the VSP Gx00 models, VSP Nx00, and VSP Fx00 models. The virtual SVP is a software application that runs on either Windows 7 Professional x64 (64-bit) on a VMware ESXi 6.0.0 host or on Windows 7 Professional Service Pack 1 (64-bit) on a VMware ESXi 6.0 U2 host.

Observe the following guidelines when installing a virtual SVP:

  • vSphere Cluster Failover: Due to the numerous vSphere server/cluster configurations and workloads, validate failover prior to placing the virtual SVP in production environments.
  • Number of SVP virtual machines per vSphere cluster: One server supports up to eight VMs. Each VM can communicate independently with one storage system. Due to the wide variety of vSphere server/cluster configurations and workloads, perform simultaneous multi-system performance monitoring and log collections to verify trouble-free management.

To provide the highest level of trouble-free operations, observe the following rules:

  • Do not locate a virtual machine on a storage system being managed by the same virtual machine.
  • Do not start the SVP virtual machine from the storage system it is managing.

Setting up the SVP locale

The SVP and storage management software support the English and Japanese languages.

If you intend to install the SVP software using a language other than English and Japanese, change the SVP's locale setting to reflect the appropriate language using the procedure for the Windows version installed on the SVP. For more information, see the instructions for your Windows operating system.

Network connection for virtual SVP

The SVP and storage system connection ports located at the rear of the components.

The following figure shows the physical network connection for a virtual SVP and Hitachi Virtual Storage Platform G800. Adjust your connections appropriately if using different VSP Gx00 models, VSP Nx00, or VSP Fx00 models.


NoteThe ESXi server running the VM instance cannot be used with the storage system they belong to different subnets, and if a router or a firewall is filtering packets according to a defined condition. There is no distance limit between the server running the SVP application and the storage array being managed if they belong to the same subnet.

Virtual SVP requirements

The virtual SVP must meet the following minimum requirements.

ESX Server (provided by the customer)

  • VMware ESXi server 6.x
  • Two quad core processors, Intel Xeon 2.29 GHz
  • One port network interface card (NIC)
  • SVP guest OS
  • 32 GB RAM

SVP Guest OS (maximum one DKC per SVP guest OS)

For the latest interoperability updates and details, see


  • WinZip


To support a virtual SVP, verify that hyper-threading is active for the ESXi server and VM guest host.

NoteHyper-threading is enabled by default.


Configuring the virtual SVP

After preparing the environment, activating hyper-threading on both the ESXi server and VM guest host, and verifying the configuration layout, configure the virtual SVP.


  1. Create a Windows 7 Professional x64 Service Pack 1 environment on the ESXi host.

  2. Verify the virtual network connection is properly assigned to the appropriate virtual machine network.

  3. Configure network settings for the VM. The specified IP address must allow communication with the storage system controllers.GUID-829D5563-9A32-41B6-AC48-AD9752A1B4C9-low.png

  4. Configure a Remote Desktop connection.GUID-F1EBBD86-A375-44BA-9933-4A3FD4ADA720-low.png

    NoteAfter completing the configuration task, configure the SVP guest OS.

Configuring the SVP guest OS

Before you begin, ensure Hyper-Threading is active for the ESXi server and VM guest host is configured.

For more information on configuring the operating system on the SVP, see Configuring the operating system.

Installing the SVP software

You install the SVP software from the SVP ISO image for your storage system. This image is part of the microcode distribution set and has the file name H8-SVP-XXX-XX.iso.

  1. Obtain the appropriate SVP ISO image for your storage system from the firmware distribution set. Verify the ISO image corresponds to the firmware currently running on the storage system.

  2. Download the SVP ISO from TISC to the CE notebook, and then use an ISO reader to mount the SVP ISO as the next available drive letter.

  3. Launch Remote Desktop Connection and click the Show Options drop-down menu.

  4. Click the Local Resources tab, and then click More.

  5. Expand Drives, and then check the drive that has the ISO.

  6. Click Connect.

  7. When prompted to enter your credentials, enter your SVP password and click OK.

  8. Perform the appropriate step:

    • If you have WinZip installed on the VM, extract the ISO locally, and then go to step 9 to run the setup application.
    • Otherwise, click the mapped drive in the left pane and double-click the Setup application in the workspace to the right of the pane (see the following figures), and then go to step 9.
    NoteUsing WinZip is the preferred method. The alternative method performs the installation over the network and can take significantly longer to complete.
  9. In the Windows Security Alert window, select Private networks, such as my home or work network. Then clear Public networks, such as those in airports and coffee shops (not recommended because the networks often have little or no security).

  10. Type the SVP IP address and click Apply.

  11. Add the storage system.

  12. Register the storage system.

  13. Click the storage system.

    You are presented with the following two options:
    • Upgrading the firmware and adding the storage system
    • Adding the storage system without upgrading the firmware
  14. If the storage system firmware is current, click Select Update Objects and clear Firmware (Storage System). Doing so adds the storage system without upgrading the firmware Click Apply, and then click Confirm to added the storage system to the SVP.

  15. On the Desktop, click the Open StorageDevice List shortcut.GUID-AF22A48E-F667-4D68-A845-A8D16E9AC8E0-low.png

    Wait 10-to-15 minutes for all the services to start.GUID-C80E3174-7460-4E99-A03E-B8622C73F89D-low.png
  16. After the services are ready, click the storage system to start Hitachi Device Manager - Storage Navigator.GUID-5EE1A936-989C-4D8D-B4D3-BA9A353A69D5-low.png

Deploying a cloned virtual SVP

To avoid management outages for the working storage system, clone a virtual SVP image to an unregistered storage system.


  1. Prepare a master virtual SVP image:

    1. Create the virtual SVP using the procedure in Configuring the virtual SVP. You do not have to set up the network at this time.

    2. Configure the SVP guest OS using the procedure in Configuring the SVP guest OS.

    3. Install the SVP using the procedure in Completing the configuration. You do not have to configure the SVP IP address at this time. In addition, do not register a DKC using the Storage Device List.

  2. Turn off the master virtual SVP.

  3. Clone the master virtual SVP, and then start the cloned virtual SVP.

  4. Configure the Windows OS network information in the cloned virtual SVP.

  5. Set the IP address for the SVP. This IP address is used to communicate with the storage system.

  6. Register a storage system using the Storage Device List.

Detecting SVP failures

SVP failures are detected and resolved using the following methods.

Failure detection method How a failure is detected Action to be taken

Hitachi Remote Ops

No report from the agent during a 24-hour health check

Remote Ops detects SVP failure -> SVP replacement. Contact a Hitachi Vantara representative or authorized service provider.

Hitachi Command Suite

RMI connection error (not alert)

See the Hitachi Command Suite Administrator Guide (MK-90HC175).

Hitachi Ops Center Administrator Hardware alerts appear in Alert tiles, along with drill-down views for detailed information.

See Hitachi Storage Advisor User Guide (MK-94HSA004).