At a certain point, you’ll lose the connection with the webserver and any CLI session.
Log in with your HPE Passport and download the package.Make sure all the keytool commands are run from : C:Program FilesHewlett Packard EnterpriseSSMCssmcbaseetc.
Navigate to HPE’s Software Depot and locate SSMC URL or click here. I think from another post I read that when you upgrade the SSMC version this will over-write the certificate change and you will have to do this again, i have not tested this theory yet.In my case, I’m running SSMC version 3.4.1 star file which is provided together with the SSMC package. All we need to do is download the executables, an upgrade. Upgrading to StoreServ Management Console 3.6 is very simple and straight forward. Please note that when upgrading from 3.x to 3.6 the GUI Admin User is removed and instead the same userid is used as when logging into the SSMC appliance through CLI “ssmcadmin”.The Administrator Guide for SSMC 3.6 can also be downloaded here.For an extended list of new features, the Release Notes document of SSMC 3.6 is available here.The latest version is visually not much different compared to previous versions but its engine to process data has been improved. Next, we initialize the ESD’s storage configuration by typing the command createcages and selecting from one of the menu options provided.HPE recently released a new version of its management tool 3PAR arrays, called StoreServ Management Console 3.6.
Log into the node using the username root and the password root. Configuring the ESD NodeĪfter the VMs complete their boot processes, open a console session to the ESD node. Before doing so, I suggest creating a snapshot of all 3 VMs in case you need to revert and start the configuration process again. The next step in the process is to power on all three virtual machines. After the VMs are deployed, configure the networks assigned to each NIC as described above. Again, because the deployment of the node does not require any input other than necessary infrastructure resource selection, you can follow VMware’s documentation to Deploy an OVF or OVA Template. For this walkthrough, the ESD node hostname is vLAB-3PAR-ESD.
The simulator uses only one instance of this virtual machine.
With Native IP as well as Fibre Channel (FC) support, 3PAR Remote. (SSMC) GUI with a performance dashboard, custom reports capability. The ESD node provides for simulation of the HPE 3PAR drive enclosure/cages and hard drives. The HPE 3PAR File Persona Software Suite is a feature of the 3PAR OS that enables a rich set of file protocols. Because the deployment of the management cluster nodes does not require any input other than necessary infrastructure resource selection, you can follow VMware’s documentation to Deploy an OVF or OVA Template.
Deploying the Management Cluster Nodesįor this walkthrough, the two management node VM hostnames are vLab-3PAR-Node0 and vLab-3PAR-Node1. The third NIC provides communication between the three nodes and requires a private network connection. The second NIC allows connectivity to the Remote Copy network if the feature is required. The first NIC of each VM provides management connectivity to the VMs. One OVF template contains the management node software, while the other includes the virtualized enclosure/disk shelves.Īdditionally, each VM deployed for the HPE 3PAR StoreServ Simulator has three virtual NICs. The tarball file provided by HPE contains instructions, as well as two OVF templates. For this walkthrough, I’m using version 3.2.2 MU4 of the simulator. Preparing for Deploymentīefore we can begin, we need to download the HPE 3PAR StoreServ Simulator from the My HPE Software Center. In this post, we walk through the process to deploy and configure the simulator. While the simulator does not offer storage services to external devices, it is fully functional in almost all aspects allowing for complete testing of most features and management functions. For several years now, HPE has provided a simulated version of its 3PAR StoreServ storage array available for deployment in virtualized environments.