DELL Technologies PowerScale OneFS Simulator

Specifications

• Product: PowerScale OneFS Simulator
• Installation Guide: 9.5.0.0
• Date: January 2023

Product Information

The PowerScale OneFS Simulator is a virtual version of the physical storage nodes that can be deployed in a physical infrastructure. It allows users to monitor and manage virtual clusters and run virtual nodes on virtualization products supported by VMware.

Please note that the OneFS Simulator is intended for demonstration and noncommercial purposes only, and should not be installed in a production environment.

System Requirements
Before installing a virtual node, ensure that your system meets the requirements for the PowerScale OneFS Simulator. At least three virtual nodes are required to create a virtual cluster. Please note that virtual nodes are for demonstration purposes only and are ineligible for support or repair by Dell Technologies Support.

requirement. More memory improves virtual
node performance. Virtual nodes might not function correctly if
they do not meet the recommended memory requirements.
Processor| VT-capable processor| Virtualization technology must be enabled in the BIOS.
Hard drive| 100 GB of disk space per virtual node| The hard drive size is set at 100 GB. There is currently no
option available to increase the size. Giving a larger size will
not change the total space per node of 100 GB.
Operating system| Microsoft Windows (recommended)| Ubuntu 12.04.5 and 14.04 (Linux)| CentOS 6.6 (Linux)
Virtual infrastructure| VMware Server| VMware Fusion| VMware Workstation| VMware Player

Product Usage Instructions

Installation

1. Ensure that your system meets the specified system requirements.
2. Download the PowerScale OneFS Simulator installation package.
3. Follow the installation wizard to install the OneFS Simulator.
4. If prompted, enable the necessary protocols for your intended use.
5. Once the installation is complete, launch the OneFS Simulator application.

Configuring Virtual Clusters

To configure virtual clusters in the PowerScale OneFS Simulator:

1. Open the OneFS Simulator application.
2. Create three or more virtual nodes within the application.
3. Connect the virtual nodes to form a virtual cluster.
4. Configure the desired settings and protocols for the virtual cluster.
5. Save the cluster configuration.

Managing Virtual Nodes
To manage virtual nodes in the PowerScale OneFS Simulator:

1. Open the OneFS Simulator application.
2. Select the virtual node you want to manage.
3. Perform the desired management tasks, such as monitoring, configuring, or troubleshooting.
4. Save any changes made to the virtual node configuration.

FAQ

Q: Can I install the OneFS Simulator in a production environment?
A: No, the OneFS Simulator is for demonstration and noncommercial purposes only and should not be installed in a production environment.

Q: What are the system requirements for the PowerScale OneFS Simulator?
A: The system requirements include a minimum of 6 GB RAM per virtual node, a VT-capable processor with virtualization technology enabled in the BIOS, and 100 GB of disk space per virtual node. The supported operating systems are Microsoft Windows, Ubuntu (12.04.5 and 14.04), and CentOS 6.6. The virtual infrastructure can be VMware Server, VMware Fusion, VMware Workstation, or VMware Player.

Q: How many virtual nodes are required to create a virtual cluster?
A: At least three virtual nodes are required to create a PowerScale OneFS virtual cluster.

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

OneFS Simulator Installation

This section contains the following topics:

Topics:

• About this guide
• OneFS Simulator overview
• System requirements
• Network settings
• Installing OneFS Simulator
• Updating the Network Interface on Dell OneFS Simulator
• Configure a virtual cluster
• OneFS Management
• Uninstall OneFS Simulator
• Where to get help

About this guide
This guide describes how you can install and configure OneFS Simulator to monitor and manage virtual clusters. This guide also describes how to run virtual nodes on the virtualization products supported by VMware.

NOTE: OneFS Simulator is for demonstration and noncommercial purposes only and should not be installed in a production environment.

OneFS Simulator overview
OneFS Simulator is a virtual version of the physical storage nodes that you can deploy in a physical infrastructure.
On new installations of OneFS 9.0.0.0, all protocols are disabled by default. The customer needs to enable any protocols that they plan to use. On new installations of OneFS 9.0.0.0, the default /ifs export and ifs share no longer exist. Upgrading is not affected.

Throughout this document, the following conventions are used:

• A virtual node refers to a virtual machine.
• A host refers to a physical host with a virtual infrastructure, such as VMware ESXi or VMware Workstation.

System requirements
Before you install a virtual node, verify that your system meets the requirements for the virtual version of OneFS. At least three virtual nodes are required to create an PowerScale OneFS virtual cluster.

NOTE: Virtual nodes are for demonstration purposes only and are ineligible for support or repair by Dell Technologies Support.

Table 1. Host system requirements

populated virtual cluster. This minimum is the default requirement. More memory does improve virtual node performance as| Virtual nodes might not function correctly if they do not meet the recommended memory requirements.

NOTE: Other nodes that are added to your virtual environment to

 | long as the amount of RAM is consistent across all nodes.| provide services, such as the Active Directory domain controller service or DNS service, have additional memory requirements.
---|---|---
Processor| VT-capable processor| Virtualization technology must be enabled in the BIOS.
Hard drive| 100 GB of disk space per virtual node for a fully populated virtual cluster| NOTE: Hard drive size is set at 100 GB, no option is currently available to increase size. Giving a larger size will not change the total space per node of 100 GB.
Operating system| The following operating systems have been tested for and validated for the installation:

●       Microsoft Windows (recommended)

●       Ubuntu 12.04.5 and 14.04 (Linux)

●       CentOS 6.6 (Linux)

| All the procedures in this guide are based on the Microsoft Windows operating system. Some of the steps in the procedures might differ based on your host operating system.
Virtual infrastructure| Standalone components:| Install at least one stand- alone component.

If you are installing VMware Workstation, VMware Player, or VMware Fusion, ensure that the external network is configured as a bridged network and

not as a nat network. This configuration allows the clients to access the virtual nodes.

VMware Player is available at: http:// www.vmware.com/products/player/

Network settings

It is critical that you set up the internal and external network of a virtual cluster according to the networking setup on your host system.

Follow these guidelines to set up your virtual network:

• Reserve an IP address range for configuring your virtual cluster. You must be able to route the IP range through the hardware host for your virtual cluster. You can perform this step by setting up a virtual interface on your system with an IP address from the same subnet as your virtual cluster. Alternatively, you can configure IP addresses from the same subnet as your hardware host for your virtual cluster.
• Virtual clusters have two network interfaces: NAT and bridged. The NAT interface facilitates internal communication within the virtual cluster and does not need to be public and routable. The bridged interface facilitates client access and must be public and routable. If you are setting up VMware Workstation, VMware Player, or VMware Fusion as a host, ensure that the external network is configured as a bridged interface to enable clients to access the virtual nodes.
• It is recommended that you allocate sufficient internal IP addresses to accommodate any changes that you might want to make to your virtual cluster. If your virtual cluster does not have an available internal IP address, you cannot add new virtual nodes to your virtual cluster.

Record network configuration data

Record the configuration information for your internal and external networks before installing the virtual nodes and configuring your virtual cluster.

1. Type ipconfig at the Windows command prompt.
   The network information appears as shown in the following sample output :

2. Record the following internal and external network configuration details:

Installing OneFS Simulator

You can install OneFS Simulator through the OVA file that is in the ZIP file. You can set up VMware Workstation, VMware Fusion, or VMware ESXi to run the OneFS Simulator virtual nodes.
You can configure a virtual cluster for a single virtual node. However, three- to four-node virtual clusters are recommended for testing and experimentation. For configuring a virtual cluster with more than four virtual nodes, ensure that the host system has a minimum of 6 GB of available RAM per virtual node.

Most laptops can only support a three-node virtual cluster. More CPU, RAM, and disk space are consumed for each virtual node you add to the virtual cluster.
Installing OneFS Simulator by importing the OVA file Follow the steps in this procedure to install OneFS Simulator through the OVA file.
Ensure that you have installed VMware Workstation, VMware Fusion, or VMware ESXi to deploy and configure the OneFS Simulator virtual node. This procedure assumes that you have installed VMware Workstation.

1. Download the ZIP file from the product download page and extract the OVA file from the archive by following the download process specific to your browser and save the file to your local drive.

2. Open VMware Workstation and click File > Open.

3. Browse to the folder where you have downloaded the OVA file, select the file, and then click Open.
   The Import Virtual Machine dialog box opens.

4. Specify a name for the virtual machine and a path to store it and then click Import. VMware Workstation imports the OVA virtual machine and the virtual machine appears in the virtual machine library.

5. To import more virtual machines, repeat the previous two steps by selecting the same OVA file but by specifying a different name and path for the imported virtual machines in the Import Virtual Machine dialog box.

6. Click VM > Power > Power on from the VMware console to power on the first virtual machine.
   A series of checks are performed as the virtual machine powers on.

7. Click anywhere inside the virtual machine console to obtain the control of the mouse and keyboard on the host system.

8. Configure the settings for the virtual cluster through the configuration wizard that appears in the virtual machine command console.

9. Power on the other virtual machines that you have imported and repeat the previous two steps individually for each of the
   virtual machines by selecting the Join an existing cluster option in the configuration wizard.
   The virtual machines are added as virtual nodes to the virtual cluster.

Deploy OneFS Simulator on an ESXi server
You can run virtual nodes on an ESXi server by deploying the OVA file on a selected ESXi host.

1. Log in to the VMware vSphere Web Client through the following URL:
   https://:9443/vsphere-client/

2. On the vCenter home page, click Hosts and Clusters.

3. Select a local host from a virtual cluster and click Actions > Deploy OVF Template to open the Deploy OVF Template wizard.

4. On the Select source page, browse to the folder where you have downloaded the OVA file and select the file. Alternatively, provide the URL to the OVA file and then click Next.

5. On the Review details page, review the details, and then click Next.

6. On the Select name and folder page, perform the following actions:

   • Type a name for the deployed template.
   • Select a folder or data center within the inventory where OneFS Simulator will reside.
   • Click Next.

7. On the Select a resource page, select a virtual cluster or host to run the virtual machine after it is deployed.

8. On the Select storage page, select the following parameters:

   • A virtual disk format from the list.
   • A virtual machine storage policy, if applicable.
   • A datastore for storing the virtual machine configuration files on the destination resource that you selected in the previous step.
   • Click Next.

9. On the Setup networks page, configure the networking parameters and click Next.

10. Review the summary on the Ready to complete page.

11. Click Power on after deployment and then click Finish to deploy the virtual node as a virtual machine.

12. Configure the cluster. See Network Settings and Record network configuration data for cluster configuration settings.

13. NOTE: This step activates advanced features that are activated through the license option in the UI or CLI. The baseline configuration does not require this step, and advanced features can be activated at any time.
    (Optional) Open an SSH client and at the command prompt, type the following command to activate the advanced features:

isi license add —evaluation
ONEFS, SMARTQUOTAS, SNAPSHOTIQ, SMARTCONNECT_ADVANCED, SYNCIQ, SMARTPOOLS, SMARTLOCK, HDFS, SM
ARTDEDUPE,CLOUDPOOLS,SWIFT,HARDENING

If the amount of RAM in the deployed virtual node has increased, you can convert the virtual machine to a template and create additional virtual nodes from the template. You do not need to create a template if the configuration of the virtual machine has not been changed.

NOTE: Do not create templates from a virtual machine that has ever been booted.

Updating the Network Interface on Dell OneFS Simulator
This section explains the process of upgrading the E1000 network interfaces used with the OneFS simulator to the newer vmxnet3 network interfaces.

Update the network interfaces
This section explains how to update the network interfaces from E1000 to VMXNET3 drivers.
The following steps explain how to add the additional interface to the OneFS level.

1. Deploy the virtual machine and name it node1.

2. Add the three networking interfaces in the VMware settings and set them to vmxnet3.

3. Start the virtual machine and go through the install.

4. When installation finishes, edit the /etc/rc.conf file.

   • a. Add if_vmx to kld_list=”aio cpuctl if_bxe if_vmx if_cxgb if_cxgbe if_em if_igb mthca mlx4ib mlxen ipoib”.
   • b. Add the following lines to rc.conf after ldconfig_paths=.
   • ifconfig_vmx0_name=em0
   • ifconfig_vmx1_name=em1
   • ifconfig_vmx2_name=em2

5. Shut the virtual machine off and remove the E1000 network interfaces in the VMware settings.

6. Clone 2 more virtual machines, calling them node2 and node3.

7. Start the virtual machine for node3 and let it boot while watching in a VMRC console.

   • a. Log in and run isi_reformat_node –nolkg.
   • b. Wait for it to go back to the menu screen to create or join a cluster.

8. Start the virtual machine for node2 and let it boot watching in a VMRC console.

   • a. Log in and run isi_reformat_node –nolkg.
   • b. Wait for it to go back to the menu screen to create or join a cluster.

9. Start node1 and let it boot all the way up.

10. Log in to it and ensure it is ok.

11. Launch a VMRC console and ensure it boots all the way to the login screen.

12. When node1 is up, log in to the GUI to watch the other nodes join.

13. Go back to the node2 VMRC screen to select join and select the cluster. Wait until it completes.

14. Go back to node 3 vmrc screen and select join and select the cluster.
    Wait until it completes.

15. Log in and run ifconfig.

16. Verify 10G interfaces.
    Below is an example of an unedited /etc/rc.conf file.

background_fsck=”NO”
blanktime=”NO”
dumpdev=”NO”
dumppid=”NO”
ipv6_ipv4mapping=”YES”
kld_list=”aio cpuctl if_bxe if_cxgb if_cxgbe if_em if_igb mthca mlx4ib mlxen ipoib”
ldconfig_paths=”/usr/lib/compat /usr/local/lib /usr/likewise/lib /usr/local/apache2/lib
/usr/local/apache2/bin /usr/local/lib/compat/pkg”
netfs_types=”efs:IFS ${netfs_types}”
rcshutdown_timeout=”570″

Daemon options.

isi_clear_webui_enable=”YES”
isi_drive_d_enable=”YES”
isi_eth_mixer_enable=”YES”
isi_flexnet_enable=”YES”
isi_ipmi_d_enable=”YES”
isi_initial_enable=”YES”
isi_km_d_enable=”YES”
isi_lcd_enable=”YES”
isi_mcp_enable=”YES”
isi_watchdog_enable=”YES”
local_startup=””
netwait_enable=”NO”
netwait_timeout=”60″ # Total number of seconds to perform pings.
netwait_if_timeout=”30″ # Total number of seconds to monitor link state.
newsyslog_flags=”-N -CC”
nfs_async=”NO”
portmap_enable=”YES”
rpcbind_enable=”YES”
sendmail_enable=”NONE”
snmptrapd_enable=”NO”
syslogd_flags=”-c”
update_motd=”YES”
xinetd_enable=”YES”
xntpd_enable=”NO”

Below is an example of a modified /etc/rc.conf file. Changes are italicized.

background_fsck=”NO”
blanktime=”NO”
dumpdev=”NO”
dumppid=”NO”
ipv6_ipv4mapping=”YES”
kld_list=”aio cpuctl if_bxe if_vmx if_cxgb if_cxgbe if_em if_igb mthca mlx4ib mlxen
ipoib”
ifconfig_vmx0_name=em0
ifconfig_vmx1_name=em1
ifconfig_vmx2_name=em2
ldconfig_paths=”/usr/lib/compat /usr/local/lib /usr/likewise/lib /usr/local/apache2/lib
/usr/local/apache2/bin /usr/local/lib/compat/pkg”
netfs_types=”efs:IFS ${netfs_types}”
rcshutdown_timeout=”570″

Daemon options.

isi_clear_webui_enable=”YES”
isi_drive_d_enable=”YES”
isi_eth_mixer_enable=”YES”
isi_flexnet_enable=”YES”
isi_ipmi_d_enable=”YES”
isi_initial_enable=”YES”
isi_km_d_enable=”YES”
isi_lcd_enable=”YES”
isi_mcp_enable=”YES”
isi_watchdog_enable=”YES”
local_startup=””
netwait_enable=”NO”
netwait_timeout=”60″ # Total number of seconds to perform pings.
netwait_if_timeout=”30″ # Total number of seconds to monitor link state.
newsyslog_flags=”-N -CC”
nfs_async=”NO”
portmap_enable=”YES”
rpcbind_enable=”YES”
sendmail_enable=”NONE”
snmptrapd_enable=”NO”
syslogd_flags=”-c”
update_motd=”YES”
xinetd_enable=”YES”
xntpd_enable=”NO”

Configure a virtual cluster

After installing one or more virtual nodes, you can configure a virtual cluster through the configuration wizard. The wizard provides step-by-step guidance for configuring a new virtual cluster or for adding a new virtual node to an existing virtual cluster.
After a virtual node has been booted, the PowerScale IQ configuration wizard options appear in the same command window.

1. In the configuration wizard, select one of the following options:

   • To create a new virtual cluster, type 1.
   • To join the virtual node to an existing virtual cluster, type 2.
   • To exit the wizard and configure the virtual node manually, type 3.
   • To reboot into SmartLock Compliance mode, type 4.
     NOTE: You cannot mix enterprise nodes with compliance nodes. If you choose to configure as SmartLock Compliance mode nodes, all nodes must have option 4 selected, and rebooted to configure up the cluster.

2. Follow the prompts to configure the virtual cluster. See the Virtual cluster configuration settings section for details.

3. Open an SSH client and type the lowest IP address from the external range.

4. Log in with the root username and password.

5. NOTE: This step activates advanced features that are activated through the license option in the UI or CLI.
   (Optional) At the command prompt, run the following command to activate the permanent evaluation license:

isi license add —evaluation
ONEFS, SMARTQUOTAS,SNAPSHOTIQ, SMARTCONNECT_ADVANCED,SYNCIQ, SMARTPOOLS,SMARTLOCK,HDFS,SM
ARTDEDUPE,CLOUDPOOLS,SWIFT,HARDENING

Virtual cluster configuration settings

Cluster configuration review and acceptance of stated configuration.
The configuration wizard prompts you a complete overview of the initial configuration of the cluster. You can customize your virtual cluster in a series of steps by typing yes to approve and move forward or no to go back and make changes.

Note: Upon completing of the cluster configuration, you will move to the management section on how to manage your virtual cluster using SSH or UI.
The following table provides information about each step in the configuration wizard. Enter values that are appropriate for your virtual cluster.

Secure: Will not allow a node to join unless a password is entered, thus securing the access to the cluster.

Name| Type a name to identify the virtual cluster.
Encoding| Specify the character encoding for the virtual cluster. The default character encoding is UTF-8.
Interface int-a| Specify the network settings for the int-a network which facilitates communication between the virtual nodes.

1. Specify an IP address to configure the netmask. Refer to the table in Record network configuration data for the values you recorded for the internal IP range (VMnet1).

| 2. Retain the existing value for MTU.

3. Specify a low IP address and a high IP address for the internal IP range of your network.

Press ENTER to retain the existing configuration.

---|---
Interface int-b| To skip configuring the failover back-end network press ENTER.

If you chose to fully configure the failover interface, you need three matching IP ranges to support this. The Dell Technologies official Infiniband/Ethernet network address ranges are:

128.221.252.1.-254

128.221.253.1.-254

128.221.254.1.-254

External subnet| Specify the network settings for the ext-1 network. The ext-1 network provides client access to the virtual cluster.

1. Specify an IP address to configure the netmask. Refer to the table in Record network configuration data for the values you recorded for the external IP range (VMnet8).

2. Retain the existing value for MTU.

3. Specify a low IP address and a high IP address for the external IP range of your network.

Default gateway| Specify the gateway IP address of your network to optionally configure the gateway server through which the virtual cluster communicates with clients outside the subnet.
SmartConnect| Specify the SmartConnect zone name and service IP address. Press ENTER to retain the default settings.
DNS| Specify the gateway IP address of your network to configure the DNS server.
External subnet| Specify the network settings for the external network interface. Press ENTER to retain the default settings.
Date and time zone| By default, the virtual node is set to the time and date settings based on your host computer. However, you can configure a different date and time zone.

OneFS Management

Manage a virtual cluster
OneFS nodes can be managed individually or as a minimum three node cluster.

You can access the nodes or cluster using:

x’s represent the IP address of a node in the cluster or “https://clustername.com:8080.”

NOTE: Connection can be made through FQDN rather than IP address when the full IP range of information, including SmartConnect, has been configured in DNS.

After you have joined at least three virtual nodes to a virtual cluster, you can connect to one of the virtual nodes and manage the virtual cluster.
When connecting to a virtual node, provide the information that is configured on the virtual cluster.

Connect to a virtual node through SSH

You can connect to a virtual node through SSH and manage a virtual cluster.
Ensure that the ext-1 interface is set to bridged before you proceed.

1. Open an SSH client and type the lowest IP address from the external range.
2. Log in with the root username and password.
3. At the command prompt, type the required isi commands to monitor and manage your virtual cluster.
   For example, type the following command at the command prompt to monitor the health and performance of the virtual cluster:
   isi status

NOTE: OneFS supports tab completion. When typing an isi command, you can press the TAB key to identify or complete the command syntax.
For more information about the OneFS commands, see the OneFS CLI Administration Guide at Dell Online Support.

Connect to a virtual node through the web administration interface
You can connect to a virtual node through the web administration interface and manage a virtual cluster.

NOTE: Optionally, connection can be made through FQDN rather than the IP address if full IP information has been configured in DNS.

1. Open a browser and type the lowest IP address from the external range.
2. Click Continue to this website (not recommended).
3. Log in with the root or admin username and password.
4. Suppress any warning events by going to Cluster Status > Events > Summary and clicking Quiet against the event that you want to suppress.
   For example, for each configured virtual node, select Quiet to remove the warning that the virtual machine has four hard drives when a physical node has

Uninstall OneFS Simulator

You can uninstall and remove OneFS Simulator by removing all the virtual nodes and virtual clusters that you configured.

1. Power off the virtual machine nodes.
2. Delete the virtual machines and all the associated files and folders.

Where to get help
The Dell Technologies Support site (https://www.dell.com/support) contains important information about products and services including drivers, installation packages, product documentation, knowledge base articles, and advisories.
A valid support contract and account might be required to access all the available information about a specific Dell Technologies product or service.

Additional options for getting help
This section contains resources for getting answers to questions about PowerScale products.

Dell Technologies Support| ●       https://www.dell.com/support/incidents- online/en-us/contactus/product/ isilon- onefs
---|---
Telephone support| ● United States: 1-800-SVC-4EMC (1-800-782-4362)

● Canada: 1-800-543-4782

● Worldwide: 1-508-497-7901

● Local phone numbers for a specific country or region are available at https:// www.dell.com/support/incidents-online/en- us/contactus/product/isilon-onefs.

PowerScale OneFS Documentation Info Hubs| ● https://www.dell.com/support/kbdoc/en-us/000152189/powerscale-onefs- info- hubs
Dell Community Board for self-help| ● https://www.dell.com/community

References

• VMware Workstation Player | VMware
• PowerScale OneFS Info Hubs | Dell US

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>