Once the cloning process has completed we can move on to the next step – deploying the enclosure OVF.

Review your settings and click Finish to begin the cloning process.

We do not need to change settings at this point

Select a cluster/node for the VM to start on.

Give the cloned VM a name – in this instance I will append 02 to help me identify the second cluster node.

Below I have included screenshots of the cloning process – The process for deploying the second node is simple – either clone the node you have just deployed or work through the OVF deployment wizard a second time using the same settings as above but with a new VM name. Once you have deployed the first cluster node you will need to deploy a second – if you are curious as to why then think about how the physical array works it requires at least two physical controllers and the simulator is emulating this behaviour. The VMs have 3 vNICs and we do not want to configure them at this stage

Pick the network for the VM – in this case leave the setting on ‘VM Network’.

Select a datastore and provisioning format.

Again I have to blank some of this information out

Select the ESXi cluster and potentially a specific node for the VM to start on.

You will also need to select a folder from within your vSphere inventory, I have to blank out this section as it includes company specific information.

Give the cluster node a name – choose something meaningful, for example I have named mine 3PARSIMCN01 (CN = cluster node).

Select the cluster node – click ‘Local file’ and use the ‘Browse’ button.

I have taken screenshots from the vCenter web client interface for guidance – Open vSphere and work your way through the ‘Deploy OVF Template’ wizard. We will start by deploying the cluster node OVF. The simulator comes with two OVF files, one for the cluster nodes and the other for the enclosure node. The first step is to deploy the OVF package to our virtual environment. HP suggest 4 GB of RAM is needed for each cluster node. Note – If you are going to deploy the 3PAR Simulator with Remote Copy over IP (RCIP) the cluster node VMs will require more resources. 50GB disk space (full or thin-provisioned).The minimum system resources required for each VM are: Network configuration to enable communication between the three VMs. Requires deploying three VMs two VMs simulating the cluster nodes, a third VM to simulate the enclosure and private The 3PAR Simulator requires a VMware ESXi 5.x or a VMware Workstation 9 or 10 setup. Please note this is quite a long post as it includes many screenshots and notes. You can also deploy the simulator on VMware Workstation however the steps are slightly different. Today we will deploy the HP 3PAR simulator on VMware vSphere ESXi 5.5.

3par ssmc user guide