SimpliVity OmniCube Setup Continued – Attaching/Integrating the SimpliVity OmniCube to an existing VMWare installation.
This next portion of the install I like to refer as “attaching the OmniCube to your existing VMWare Installation”. At a high level it is adding the correct items to the VMWare environment setting up IP addresses and making sure that everything works properly. This is generally a straight forward process and took me about an hour and a half to finish after the system was racked.
There are only a few steps to get this all accomplished. First off the QuickStart guide that is included with each OmniCube is a great tool to get everything up and running in the correct order. In the first deployment of the OmniCube I also referenced the OmniCube_Config_Mgmt-xxxxx.pdf located on the SimpliVity supplied USB drive.
- Deploy the VMWare OVF tools to the administrative machine running the VMWare Client software.
- Install the SimpliVity supplied Arbiter software on the vCenter Server. This software comes with the OmniCubes and is loaded on a USB memory stick that is included with each OmniCube.
- Setup/Customize the ESXi servers that are installed on the OmniCubes. This is where the network configuration happens (use of a Static IP is always recommended), see the detail installation instructions for the passwords and other items that need to be changed.
- Create a service user on your domain for SimpliVity communications, (follow the directions in the manual to create the proper VMWare rights.)
- You need to have 3 subnets to do a full install, one for management, one for the data networking (10GB/s) and one for federated data.
- Setup NTP – I used the defaults since they are the same as I use on my domain.
- Deploy the OmniCubes into a SimpliVity federation by logging into the VMWare Client, Select the OmniCube navigating to the SimpliVity tab, the verifications run.
- When the verification finishes follow the prompts to deploy the OmniCube. The prompts are user created in step 4, adding the management and storage networks. The only thing I noticed to be aware of is to make sure that when you setup the storage network that the correct port group is selected.
- Wait for 15-20 minutes as everything is being deployed. Other tasks can be performed in the vCenter Server while this is going on. I opened up a console to the built in virtual host and watched all the commands go by to insure that the process was working.
- After the deployment goto the data store, The first datastore that is auto created is the SimpliVity Virtual Datastore. Do not delete or change this data store.
Create your own Datastore, click SimpliVity – Create Datastore. I created a 1 TB Windows Data Store and a 1 TB Linux Data Store. Creating the datastore within the SimpliVity architecture is what gives the product its compression and de-duplication coolness.
The system is now ready to have Guest OS’s installed onto it.
Next Blog – Guest OS’s, SimpliVity Backups and Moves.