Guides and Tutorials
- Analytics — capacity explorer
- Analytics — capacity trends
- Analytics — integrated analytics
- Analytics — IOPS hot spots
- Analytics —Throughput hot spots
- Analytics activity by path
- Analytics activity by client
- Continuous replication
- Configure the network for static addresses
- Create a Qumulo File Fabric (QF2) virtual cluster on a Mac
- Create a Qumulo File Fabric (QF2) virtual cluster on Windows
- Create a quota
- Create an NFS export
- Create an SMB share
- Creating snapshots using the QF2 dashboard
- Safe shutdown
- Scripting Qumulo with S3 via Minio
Create a Qumulo File Fabric (QF2) virtual cluster on Windows
(This procedure assumes that you’ve already downloaded the .ova file. If you haven’t, go here to download.)
In this tutorial, you’ll simulate an on-premises QF2 cluster by using VMware virtual machines (VM) to create four nodes. A cluster is a collection of nodes, where an on-premises node is a single hardware chassis (simulated in the tutorial by a VM). An on-premises cluster requires a minimum of four nodes because of the way the Qumulo block protection scheme works.
Here are the system requirements.
- For best performance, we recommend at least 8GB of RAM and an SSD to host the virtual images. You need to have VMware Fusion installed on your computer.
- You need Internet access.
- We recommend that you use the Chrome browser. The first time you access the cluster with the browser, you may get a warning that your connection is not private. If you do:
- Scroll down and click Advanced.
- Click Proceed to *IP Address*
- Log in to the cluster as admin.
The tutorials walk you through everything you need to know to set up a cluster but it’s helpful if you have some understanding of the network you’ll be using. Try to find out if your environment uses the Dynamic Host Configuration Protocol (DHCP) to assign IP addresses or if you need to assign the addresses yourself. If you do need to assign the addresses manually, collect the following information:
- The subnet mask
- The gateway
- The IP addresses of the DNS servers
- The search domains
- The maximum transmission unit (MTU)
Familiarity with VMware Fusion is helpful.
In this section you open the VMware file.
- Go to the directory where you downloaded the VMware .ova file and click on it.
- The VMware Workstation opens.
- In the Import Virtual Machine dialog box, the name for the virtual machine is filled in, by default.
- Use the default path or enter a local storage path where you want to save the VM image. If possible, save it to an SSD device.
- Click Import.
- A warning message appears.
- Ignore the message and click Retry.
- VMWare Fusion imports the VM.
- Once the image is imported, the VMware Workstation shows the following view. The new instance should appear in the left pane, under My Computer.
- Under My Computer, click the new instance.
- In the right pane, click Edit virtual machine settings.
- The Virtual Machine Settings window opens.
- Choose the appropriate networking option for your environment. Here is an example that uses a bridged connection.Note: NAT uses the IP address of the machine that the VMs run on and hides the internal IP addresses from your network.
If your environment uses DHCP, then the VMs are automatically assigned IP addresses. Otherwise, you’ll need to assign the IP addresses yourself. We’ll cover this later in the tutorial. You can always change these settings but you’ll need to restart the VMs.
You need to create three more VMs to complete your cluster. Follow the same steps as you did for the first instance. Each VM is automatically named sequentially and all the images are stored in the path you specified. Here is an example dialog box for a second VM.
![Launch instance #2](https://d11xhuj61ozf67.cloudfront.net/production/media/original_images/vmware-instance2.png)
In this section, you power on each of the instances you’ve created.
- In the VMware Workstation, under My Computer, you should see all four instances listed.
- Select the first instance and then click Power on this virtual machine.
- Some code scrolls by and after a few seconds, the Qumulo End User License Agreement (EULA) appears.
- Scroll down to the end of the agreement, select both boxes and click Submit.
- Under My Computer, select the second instance, power it on, and accept the EULA. Do the same for the third and fourth instances.
- The Qumulo configuration page appears, showing all four instances.
In this section you create a cluster.
- On the configuration page, in the Cluster name field, enter a name for your cluster.
- Scroll down to set the password for the admin account.
- Click Create cluster.
- You’re asked for a confirmation. Click Yes, Create Cluster.
- A message appears saying that the cluster is being created.
- After a few seconds, you will see the dashboard.
- If DHCP is available, then the cluster self-assigns IPv4 addresses. In this example, the IP address is 10.0.0.12. You can use this address to access the dashboard from your browser. The address is http://10.0.0.12.
- If you use DHCP then congratulations! You’ve set up your cluster. Skip the following section and go to What’s Next? If you don’t use DHCP, go to the following section, “Assign IPv4 static IP addresses.”
- Go to the dashboard. Point to Cluster and then click Network Configuration in the drop-down list.
- The Network Configuration IPv4 page opens.
- Fill in the subnet mask, the gateway, the IP addresses of the DNS servers, and the search domains. If necessary, change the MTU size.
- Scroll down and set the static IP addresses for each node. Optionally, you can assign floating IP addresses that will be redistributed in case a node fails.
- Click Save.
- A message appears saying that the network configuration view is being refreshed.
- The new view, with the correct information, appears.
- Scroll down to see the IPv4 addresses assigned to the nodes.
Your cluster is now set up and ready to share data. The next step is to create exports and shares. Here are the tutorials.
To safely shut down your cluster, see the Safe Shutdown tutorial. Once a cluster is shut down, you have to power on the VMs again to restart it.