HP 3PAR 7200 Simulator

Deploying HP 3PAR 7200 Simulator with Windows Server 2012 in VMware Workstation as a part of Virtual LAB environment.

This article is about building/expanding lab environment about HP 3PAR clustered simulator with Windows 2012 Server with Active Directory and DNS server.

Prerequisites for HP 3PAR Simulator Lab

HP 3PAR Simulator for VMware Workstation

Below notes about features and requirements are coming from document HP3PAR StoreServ Simulator Version 3.2.1 MU2 (June 2015) – HP_3PAR_Simulator_Release_Notes_v3.2.1_Z7550-96179.pdf

  • Supported FeaturesThe following 3PAR StoreServ Storage System features are supported:
    • Up to 48 HDDs, 4 cage configuration
    • Cage types – DCN1, DCS1, DCS2
    • Disk types – FC, SSD, NL
    • 3PAR Management Console support
    • CLI and Remote CLI support
    • CIM-API (SMI-S) and WS-API support
    • Storage Provisioning including Thin-Provisioning
    • Exporting Virtual Volumes
    • Adaptive Optimization (AO)
    • Dynamic Optimization (DO)
    • Local Replication (Snapshot)
    • Remote Replication (RCIP) – requires 2 instances of the simulator ( Requires more resources )

    System Requirements

    The 3PAR Simulator requires a VMware ESXi 5.5 or a VMware Workstation 11 setup. The simulator configuration requires deploying three VMs; two VMs simulating the cluster nodes, a third VM to simulate the enclosure and private network configuration to enable communication between the three VMs. The simulator has been tested on the platforms mentioned above, the users can choose to run the tool on other versions of these platforms if they choose to do so. No assistance or help can be provided in these cases.

    The minimum system resources required for each VM are:

    • One virtual CPU (single core)
    • Three virtual NICs
    • 2GB RAM
    • 50GB disk space (full or thin-provisioned)
  • Important
    • For deploying the 3PAR Simulator with RCIP, the VMs would require more resources. 4 GB of RAM is needed for each cluster node.

Windows Server 2008 R2

Windows Server 2008 System Requirements

Windows Server 2008 R2 – Download 180 days Trial

Hypervisor  VMware Workstation 11
VMware Workstation 11

Planning our 3PAR lab environment

What we need to do is just adding another simulator into already existed lab environment. Comparing to previously created environment I am just leaving at the table strict related instances to HP 3PAR.

Name IP address Interface Purpose
Gateway Vmware Gateway
dc.regmen.com local Windows 2008 Domain Controller, DNS server
3par1.regmen.com  Active node0  HP 3PAR
HP 3PAR Simulator Lab schema
Picture 1. HP 3PAR Simulator Lab schema.

Network configuration for  VMware Workstation 11

The same configuration as it is at 7-Mode Data ONTAP Simulator 8.2.3 – building lab

Picture 2. Network configuration for 7-Mode Data ONTAP Simulator lab with VMware configuration.
Picture 2. Network configuration for HP 3PAR lab with VMware configuration.

HP 3PAR Simulator – Windows 2012 Server configuration

Add entry in DNS server to recognize your

Picture 3. HP 3PAR Simulator - Windows 2012 Server, DNS configuration.
Picture 3. HP 3PAR Simulator – Windows 2012 Server, DNS configuration.

HP 3PAR Simulator – first steps in VMware Workstation

With simulator we have provided whole configuration of VM (OVF) that we can recreate in VMware. We can distinguish files designated for cluster and enclosure. Our goal is to build cluster from two nodes with enclosure.

Cluster related files:

  • clus_node_template_3.2.1.MU2_field_mode.ovf
  • clus_node_template_3.2.1.MU2_field_mode -disk1.vmdk
  • clus_node_template_3.2.1.MU2_field_mode.mf

Enclosure related files:

  • esd_node_template_3.2.1.MU2.ovf
  • esd_node_template_3.2.1.MU2 -disk1.vmdk
  • esd_node_template_3.2.1.MU2.mf

Cluster deployment in VMware

Time for building 2-node cluster.

  1. Open clus_node_template_3.2.1.MU2_field_mode.ovf
  2. Put name of your first node e.g. 3PARNODE1, choose directory for it and import. It takes a while so be patient.
  3. Right click on your newly created 3PARNODE1 and choose from submenu Manage → Clone.
  4. Choose linked clone, go next and then type the name of the second node like 3PARNODE2 and location (do not put the same directory as for 3PARNODE1).
  5. Make sure that your network configuration for 3PARNODE1 looks like on the Picture 3. However at 3PARNODE2 the first NIC should be visible as default (Bridged).
  6. Remember about Network Adapter 3. In both nodes it should be marked as LAN Segment. Within that you should add your own LAN Segment (inside LAN Segments… button). The name is not important, you can choose whatever you want, but remember that in both nodes and also in enclosure LAN Segment name for NIC3 should be the same.
Picture 4. HP 3PAR Simulator - network configuration for cluster.
Picture 4. HP 3PAR Simulator – network configuration for cluster.

Enclosure deployment in VMware

Now similar with enclosure.

  1. Open esd_node_template_3.2.1.MU2.ovf
  2. Put name of your first node e.g. 3PARENC1, choose directory for it and import.
  3. Make sure that your network configuration for 3PARENC1 looks like on the Picture 4.
  4. Remember about Network Adapter 3. You should add your own LAN Segment as you do for both nodes (inside LAN Segments… button). Remember that both nodes and also enclosure should have the same LAN Segment name for NIC3.
Picture 5. HP 3PAR Simulator - network configuration for enclosure.
Picture 5. HP 3PAR Simulator – network configuration for enclosure.

Network configuration for HP 3PAR simulator

To explain why we have to keep network configuration as presented above, let me briefly summarize statement from documentation.

  • NIC-1  dedicated for management traffic. Tools are connecting to this IP, which is cluster IP after Out of the Box procedure.
  • NIC-2  dedicated to Remote Copy over IP.NIC-2  dedicated to Remote Copy over IP.
  • NIC-3   dedicated for traffic between all simulators. LAN Segment gives possibility to route traffic locally.

HP 3PAR Simulator – initialization

The whole process is quite simple and we talk about possible troubles at the end of this article. Now it is the time to run all three virtual machines that contain simulator and Windows 2012 Server.

As advised in documentation be prepared with some data that you need provide during setup. That is:
• HP 3PAR StoreServ storage system name, an alphanumeric name up to 31 characters.
• IP address, subnet mask and Gateway IP address. The IP address must be a statically assigned address. Contact your administrator for the address information.
• Gateway IP address
• NTP server IP address (optional)
• DNS server IP address (optional)

In terms of our lab it would be like in table presented below.

Cluster name 3PARLAB
IP address

Enclosure initialization – first step

  1. Go to 3PARENC1 simulator and log inside with root/root credentials.
  2. Run command createcages to create desired cage configuration as presented on screen below. For example choose 3.

    Picture 6. HP 3PAR Simulator - Cage configuration.
    Picture 6. HP 3PAR Simulator – Cage configuration.
  3. After successfully configuration you have to run ESD deamon.

    Picture 7. HP 3PAR Simulator - starting ESD deamon.
    Picture 7. HP 3PAR Simulator – starting ESD deamon.
  4. That is all. Now you can move to controller/cluster configuration.

Cluster initialization – second step

In this step you should prepare your nodes to work in cluster configuration. To do this follow below steps.

Activities on 3PARNODE1:

  1. Log in to the first node (3PARNODE1) with console/cmp43pd credentials.
  2. Choose option 1 (Simulator Cluster Node Configuration) from menu.

    Picture 8. HP 3PAR Simulator - node configuration for cluster.
    Picture 8. HP 3PAR Simulator – node configuration for cluster.
  3. For node ID enter 0, as this is our first node.
  4. Important: Assign serial number. It could be 1699678 or 1699679. Both nodes in cluster are working with the same serial. I am choosing 1699678.
  5. Confirm entered configurations.

Activities on 3PARNODE2:

  1. Go to second node (3PARNODE2) and log in with console/cmp43pd credentials.
  2. Choose Option 1 (Simulator Cluster Node Configuration) from menu.
  3. For node ID enter 1, as this is our second node.
  4. Assign the same serial number as for previously configured node. So I enter 1699678.
  5. Confirm entered configurations.

Activities on 3PARNODE1 and 3PARNODE2:

  1. Go to both nodes and choose option 5: Reboot the node. It is important step that let you finalize new configuration.

HP 3PAR Simulator – building cluster

Time to build cluster. This is the last step, also should not give much trouble.

  1. Log in to the first node (3PARNODE1) with console/cmp43pd credentials.
  2. Choose Option 2 (Out Of The Box procedure) which do for us whole initialization of cluster.
  3. Confirm by entering yes.
  4. Follow the wizard. You will be promted for some information about network configuration that you collected earlier, time zone, etc.
  5. After OOTB procedure your cluster is ready to rumble!
  6. You should be able to ping created cluster – 10.2.100 (3PARLAB) from Windows Server 2012. If not then take a look at next chapter of this article.
  7. You can also log in to your cluster via SSH to InServ shell using 3paradm/3pardata credentials.

HP 3PAR Simulator – tips&tricks

Cannot ping my cluster.

If you did all above steps and at the end you cannot ping your cluster, it is a good time to look at your cluster network configuration. It is possible that the reason lies in wrongly addressed network configuration in terms of nodes, which means that you have configured network for node0, but suddenly node1 is Active and that makes your cluster unreacheable.

  1. Log in to node1 with 3paradm/3pardata credentials and run shownet command. As you can see Node1 is Active instead of Node0.

    Picture 9. HP 3PAR Simulator - cluster network configuration.
    Picture 9. HP 3PAR Simulator – cluster network configuration.
  2. Now you have to simply change Active node to Node0. Do this with command setnet changenode 0, as shown below.

    Picture 10. HP 3PAR Simulator - changing Active Node in network configuration for cluster.
    Picture 10. HP 3PAR Simulator – changing Active Node in network configuration for cluster.
  3. Confirm new settings with shownet command and do SSH to cluster from Windows Server 2012.

18 thoughts to “HP 3PAR 7200 Simulator”

  1. Hi:

    Thanks for 3PAR simulator instructions..

    I have the simulator downloaded as a partner a while ago, trying to deploy it.

    Unfortunately, under the ZIP file:

    HP_3PAR_StoreServ_Simulator_v2.0_Z7550-10555.zip\HP-3PAR-StoreServ-Simulator-v2.0\clus_node\clu_node-disk1.vmdk — this is showing size of 127 TB compressed (127,417,176,630,860 KB !! YES !!), and 6.5 PB (yes PetaBytes) un-compressed size.

    The ZIP file wouldn’t even unzip – saying you don’t have that much free/available space on the server .. how you are getting around this problem ?


  2. Hello,

    I am not sure whether your download is corrupted or you just got some weird version of simulator. Please download it again. If you need access to download page I am sure it can be provided by Ivan Iannaccone
    https://twitter.com/IvanIannaccone. The version that I am using is HP_3PAR_StoreServ_Simulator_v3.2.1_Z7550-10574 and release is for June 2015. The size before simulator deploy is around 10GB.

    Cheers and have much fun with it.

    1. Dear Peter,

      thank you for comment. If you would like to build another 3PAR instance which would be work in some relationship (RCIP at this case), you have to build the cluster (2 nodes) and another virtual appliance for cages. However please remember, that with RCIP you have to add NIC2 on both to the same LAN segment, and assign to all cluster nodes (2 nodes from cluster1 and 2 nodes from cluster2) 4GB RAM on each.

      Have fun!

  3. Sorry, another question, how can i export volumen to one host?. The simulator only have FC Adaprtar and not iSCSI. You can help me with the steps?

    1. Dear Peter,

      it is not fancy in 3PAR simulator and this functionality is very limited. To simulate host connectivity, log in to cluster console (with credentials for “console user”). Then from menu choose option 3 for “Simulator Host Connection”. After that you will be able to perform LUN masking. Remember that created host connection is not persistent after reboot.


    1. Simulator is available for HP partners/customers. However you can try your luck asking Ivan Iannaccone (@IvanIannaccone) on Twitter. He is 3PAR guru and if you play it well you will receive access to download page 🙂

    1. Officially it’s not supported, however I’ve never tried it. Proper network configuration is the key here, so if you will manage to do this, feel free to share.

  4. Hi,

    I have downloaded the version HP-3PAR-StoreServ-Simulator-3.2.1MU2.zip file but i do not see the ESD files, there is only Cluster files in my package, now how can i deploy the Vlab without the ESD files, does it mean m downloaded files are corrupt or there is any other released vesrion for this simulator?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.