DXi9000 Series DAE Installation

The following items are required to successfully install and configure DAE on a DXi system.

Make sure the following conditions are met before you continue with DAE installation:

• All backup jobs are completed and there is no pending I/O.
• All replication jobs are completed, and replication is paused (Replication > Actions page).
• All space reclamation tasks are completed without errors (Utilities > Space Reclamation page).
• All healthchecks are completed without errors (Utilities > Space Reclamation page).
• All components in the system display Normal status (Status > Hardware page).
• All outstanding administration alerts are deleted (Alerts > Admin Alerts page).
• All service tickets are closed (Alerts > Service Tickets page).

For more information, click Help in the remote management console to display the DXi online help. To access remote management, see Step 3 - Access Remote Management).

To access the remote management console, do the following:

1. Launch a supported Web browser on a workstation that has network access to the DXi

   The DXi GUI is compatible with Chromium-based web browsers. Quantum-tested Chromium-based browsers include Brave, Google Chrome, Microsoft Edge, Opera and Vivaldi. Mozilla Firefox is also compatible with the DXi GUI.

2. In the browser address box, type the IP address of the DXi, and then press <Enter>.

   The Login window displays.

   

   If the Login window does not display, verify that the IP address is correct and that the network path to the DXi system is valid. Also verify that you are using a supported Web browser. Then try again. If you are still unable to access the Login window, contact the DXi GUI administrator.

3. Select Administrator and enter the GUI Administrator user password.
4. Click Login.

5. If a security banner message has been specified for the DXi, click Accept.

   The Home page displays.

To add a DXi9000 Series license key, perform the following steps:

1. Open a Web browser on a computer with Internet access.

2. Enter http://www.quantum.com/licensekeys in the browser address box.

   The License Key Management page displays.

   

3. Enter the DXi system serial number in the Serial Number box and click Submit.

   The Licensed Feature page displays. Preinstalled licenses will be shown and no additional action is required.

   Note: The serial number displays on the License Keys page, above the New Key box.

4. If required, enter the authorization code (included on the DXi9000 Series License Certificate) and click Get License Key.

   The Licensed Feature page returns a license key. Print out or write down the license key, or save it to a text file.

5. Access the DXi remote management console (see Step 3 - Access Remote Management).

6. Click the Utilities menu, and then click the License Keys tab.

   The License Keys page displays.

7. Enter the DXi9000 Series license key in the New Key box, and then click Add.

   The DXi9000 Series license key is added to the system.

To add a VM NAS share:

1. In the DXi remote management console, select Configuration > NAS. The NAS Summary page displays.

   

2. Click Add.

   The Add NAS Share page displays.

   

3. Under NAS Share Settings, enter information about the share:

Name	Enter the name of the DXi9000 CIFS/SMB or NFS share. VM CIFS/SMB or NFS shares must be named VM (upper case).
Description	(Optional) Enter a brief description of the share.
Protocol	Select either: The NFS option to use the share on a UNIX or Linux network. The CIFS/SMB option to use the share in a Windows network.
Hide from network browsing	Do not select. This is for CIFS/SMB shares only.
Enable deduplication	Deselect the check box. The VM NAS share must have deduplication disabled.

4. Click Apply.

In the DXi remote management console, select Configuration > System > App Environment. The Application Environment page displays.

1. Select the Enable DAE check box.
2. To enable Apache Guacamole for accessing the DAE VM, select the Use Guacamole check box.

IMPORTANT INFORMATION The account created for Guacamole is admin. A virtual machine (VM) NAS or CIFS/SMB share must be created before DAE is enabled (see Adding a NAS Share). If the DXi SW version is prior to 4.1, the Use Guacamole check box will not appear. Your browser must support HTML5 in order to support Guacamole.

3. Enter the New Password to use for the Guacamole admin account.

4. Enter the same password in the Confirm Password box.



5. Click Apply. A Save Changes dialog box appears stating that the system will require a reboot.

   

   Select one of the following options.

   Option	Description
   Defer Reboot	Defers the system reboot. A Reboot Required alert message will appear in the GUI banner until the system is rebooted. Deferring a reboot is only recommended if additional system changes that require a reboot need to be made (Network, Application Environment, Data Encryption changes) or ingest (backup jobs) are currently in progress on the system. Note: Once a reboot is in a deferred state, the applied changes cannot be reset.
   Reboot Now	Starts the system reboot. A system reboot can take up to 15 minutes.
   Cancel	No reboot occurs and the Application Environment page reappears. Changes made to the settings remain but are not applied. Click the DAE Settings Reset to reset settings to their original state.

   Note: After the reboot and a VM has been created using syscli --add dae and with the VM running, the Open Console button will be enabled.

Note: This step is for the SSH and VNC View option only. If you are using Guacamole or MobaXterm, go to step 2.

To install the Virtual Machine OS:

1. Open an SSH session to the DXi using a Linux host. Example: ssh -Y cliadmin@<DXi IP>

2. Enter the cliadmin password

Once the DXi system has been configured for DAE, a Linux type or Windows Server (2008, 2012, or 2016) operating system .iso image file must be copied over from your host system to the DXi system. The .iso file must then be mounted to the virtual machine (VM) NAS share created on the DXi during the DXi system configuration.

Note: The following method is for a Linux host. In this case, we will mount a directory to the DXi.

To copy the .ISO image to the target DXi, log on to the host system and perform the following commands:

1. Go to the user host directory:

   Note: This procedure assumes that the .iso image file is located under the /home/user directory.

   cd /home/user

2. Create a directory. In this example, the directory is VM.

   mkdir VM

3. Mount the filesystem

   sudo mount -t nfs -o resvport,rw <dxi data IPaddress>:/Q/shares/VM /home/user/VM

   Additional Information

   • <linx_type_os>.iso - the Linux bootable ISO image to use for the DAE VM.
   • <dxi data IP address> - the DXi data IP address that has access to the DXi NAS

4. Copy the .iso file to the DXi.

   cp /home/user/<linux_type_os>.iso cp /home/user/VM/Iso/

   Additional Information

   • The Iso directory is automatically created when the DAE feature was enabled in the DXi.

5. Unmount the file system.

   sudo umount /home/user/VM

The .iso image file is now placed at the VM share as required to create the virtual machine.

Note: Alternatively, a Windows host and a program such as WinSCP can be used to copy the .iso file to the DXi @ /Q/share/VM/Iso. Use the ServiceLogin username and password to login to the DXi from within WinSCP.

Before creating a VM on the DXi, you will need to define the following VM parameters:

Use the syscli --getlimits dae command to review the current DAE resources available on the DXi.

DAE Resources Example

Output Definitions for syscli --getlimits dae

Review .ISO Images on the DXi

Use the syscli --list daeiso command to verify the .ISO images copied over to the DXi system.

Note: If you use the –path parameter, that path defines the iso image to use, which must be located under the /Q/shares/VM/Iso share or below.

Command Attributes

Review the following attribute descriptions.

‑‑list daeiso	Retrieves a list of .iso files in the specified directory.
‑‑path <iso path>	The directory to search for the .iso files.

Example: List of .ISO Images on a DXi

Once you have defined the VM parameters and .ISO image list, use the syscli --add dae command to create a new VM.

Command Attributes

Review the following attribute descriptions.

‑‑add dae	Create a new VM instance.
‑‑name <vm name>	The name of the VM.
‑‑cpus <num cpus>	The number of CPUs for the VM.
‑‑memory <ram>	Amount of RAM memory (in MB) for the VM.
‑‑diskspace <vm diskspace>	Amount of disk space (in GB) for the VM operating system.
‑‑isoimage <iso pathToImage>	Selection of the path and image file to use for the operating system install. Note: In this instance, the ISO filename is also needed, so the command is /Q/shares/VM/Iso/<iso filename>
‑‑appnetwork <dxi nic port>	Selection of the application network devices (NIC ports) on the DXi. More than one may be specified.
‑‑autostart yes|no]	Autostart the VM on the system boot. The default is no. WARNING: Do not enable autostart at this time.
‑‑password <password>	Password for accessing the console over VNC.
‑‑sure	If specified, this command will execute immediately without asking for confirmation.
‑‑getlimits dae	Output data: Minimum CPUs = 2 Maximum CPUs = 4 Minimum Memory (RAM) = 1024 MB Maximum Memory (RAM) = 32768 MB Minimum Disk Space = 8 GB Maximum Disk Space = 100 GB

Create a New Virtual Machine Example

Note: When the syscli --add dae command completes successfully, you must perform the same type of OS installation procedures as are usually performed with a physical machine.

Once the virtual machine (VM) has been installed, it is the responsibility of the user to correctly configure the VM. Review the following recommendations for VM configuration.

Before starting the virtual machine (VM), verify that the VM is in a "shut off" state using the syscli --list dae command.

Example: Verify the Virtual Machine

To start the VM, use the --start dae syscli command. Once the VM starts, it will be in a "running" state.

Command Attributes

Review the following attribute descriptions.

‑‑start dae	Starts the VM instance.
‑‑name <vm name>	The name of the VM to start.

Example: Running the Virtual Machine

Note: The virtual machine iso file resides on the virtual machine cdrom. The iso file must be ejected from the cdrom. Use syscli --eject daeiso --name <vm name>

Note: This step is for the Guacamole only. Skip this step if you are using MobaXterm or SSH and VNC Viewer.

1. In the DXi remote management console, select Configuration > System > App Environment. The Application Environment page displays.

Application Environment - DAE Enabled with Guacamole



2. Note: If DAE is not running, see Troubleshooting DAE.

3. Next to the Use Guacamole check box, click on Open Console.

A new tab displays the VM console.

Note: The first time you click Open Console displays the Apache Guacamole Login screen.



Note: Because the Apache Guacamole credentials are saved in a cookie, the login will not be required again, unless cookies are cleared.

4. Enter Username admin and use the password specified when Guacamole was enabled.
5. Complete the OS installation procedures as necessary for the OS you have installed.
6. After the virtual machine OS is installed, you will need to configure network connections.
7. When finished, continue with 5. Finish the OS Installation.

Troubleshooting DAE

If you encounter problems when enabling the DAE feature, see the table below for troubleshooting steps.

Problem	Corrective Action
System alerts	Review any Admin Alerts (see Admin Alerts) or Service Tickets (see Service Tickets) that were generated when enabling DAE.
System memory	Depending on the current system configuration, additional memory may be required to run DAE, or the additional memory was installed incorrectly. Contact Quantum.

Once the virtual machine (VM) operating system (OS) has been installed, it must be set up and configured. It is the responsibility of the user to correctly set up the VM OS.

Security

It is the responsibility of the user to correctly set up the VM OS firewall and security. This is not configured by the DXi.

Linux Configuration

Complete installation of the Linux OS.

1. Define the following network configuration parameters in the Linux OS. If the guest OS is Linux-based (Red Hat or CentOS), follow these steps.
• Ethernet Interface eth0 (required)
• Additional Ethernet Interfaces (optional)

Note: Do a service network restart to save any network changes.

Ethernet Interface eth0

Each VM is configured with at least one virtual Ethernet port. You must set eth0 to connect on boot using DHCP protocol. eth0 is connected via a VPN to the DXi.

The DXi system will appear on this network at the address of 192.168.122.1. When connecting to DXi shares from the VM OS, use this network address to obtain the best performance for the VM application that needs to access the DXi shares.

Do a service network restart to save any network changes.

Additional Ethernet Interfaces

• If you are using more than one physical DXi network port for a VM, the first network port will be eth1, where eth1 will be the DXi's lowest named network device.
• For each network port, you must define the network settings as needed for the applications running in the VM.
• The lowest physical NIC port used for the VM will be labeled eth1.

Windows Network Configuration

Complete these steps to setup your Windows Server VM network:

1. Open an SSH session to the DXi using ServiceLogin as the login user.
2. Enter the password for the ServiceLogin account.
3. Enter the command sudo -i
4. Enter the command ls /Q/shares/VM/Iso
5. If the iso file of the Windows Server OS is listed in the Iso directory, remove the iso file, using rm /Q/shares/VM/Iso/<iso file name>

Note: Ethernet drivers are not included when creating a Windows Server setup in a VM.

6. Enter the command wget https://fedorapeople.org/groups/virt/virtio-win/virtio-win.repo -O /etc/yum.repos.d/virtio-win.repo
7. Enter the command yum install virtio-win
8. Enter the command ls /usr/share/virtio-win
9. Observe the virtio-win iso file.

Example: virtio-win-0.1.171.iso

10. Copy the virtio-win<version number>.iso file to /Q/shares/VM/Iso
11. Edit the file /etc/libvirt/qemu/<name of VM>.xml as below:

<disk type='file' device='cdrom'>

<driver name='qemu' type='raw'/>

<source file='/Q/shares/VM/Iso/virtio-win-<version number).iso' startupPolicy='optional'/>

<target dev='hdc' bus='ide'/>

<readonly/>

<address type='drive' controller='0' bus='1' target='0' unit='0'/>

</disk>

12. Enter the command /hurricane/syscli --list dae --name <vm name>
13. If the DAE is shown as Running, enter the command /hurricane/syscli --shutdown dae --name <name of VM>
14. Reboot the DXi. Use command hurricane/syscli --nodemanage --reboot

The ssh sessions will terminate during the DXi reboot.

15. Open the DXi GUI after approximately 10 minutes to see if DXi is in Normal state. When the DXi is in Normal state, continue with the next step.
16. Reconnect ssh sessions from the host: ssh -Y cliadmin@<DXi IP>

17. Enter the cliadmin password.

18. Verify the VM is running by using syscli --list dae --name <vm name> If the State is not Running, start the VM by using syscli --start dae --name <vm name>
19. Click the following links for the configuration instructions applicable to your network:
For Configuration using Guacamole
1. Navigate to the VM console. From the management console, select Configuration > System > App Environment.
2. Press Ctrl-Alt-Shift to activate the Guacamole console.
3. Select On-Screen keyboard.
4. Click Ctrl, then click Alt, then click Del.

The Windows login screen is displayed.

5. Press Ctrl-Alt-Shift (on the physical keyboard) to access the Guacamole menu and change the input back to None.
6. Enter the Windows Server password.
For Configuration using Linux
1. At the bash prompt, enter vncviewer 127.0.0.1:0.
2. Enter the password to access the QEMU console.
For Configuration using Windows
1. For a Windows host using MobaXterm, open an ssh session to the cliadmin account.
2. Enter the cliadmin password.
3. At the bash prompt, enter vncviewer 127.0.0.1:0.
4. Enter the password to access the QEMU console.

20. If installing a Windows Server OS in the virtual machine, press F8 to open a dialog to allow entering Ctrl-Alt-Del to allow entering the Windows Server password.

21. Open Device Manager for the Windows Server VM to add a driver to Ethernet controller(s).

22. Browse to find the driver from the cdrom.
23. Look for the NetKVM folder and find the operating system folder.

Example: NetKVM/2k16/amd64

24. Connect an Ethernet cable from the Ethernet port on the DXi that was called out in the --appnetwork parameter of the --add dae command.

There are two methods to add applications to the VM OS:

• Use an assigned network interface to the VM OS and download or copy files to your VM OS.
• Copy the application software to the /Q/shares/VM folder and mount the share through the VM OS by using 192.168.122.1:/Q/shares/VM.

To mount a DXi host NAS share in the virtual machine (VM), do the following:

1. Log in to the VM through the VNC connection (see ).

2. Create a directory. In this example, the directory is named "mybackupshare" and the NAS share is "MyBackupShare".

   mkdir mybackupshare

3. Mount the file system.

   mount -t nfs -o resvport,rw 192.168.122.1:/Q/shares/MyBackupShare ./mybackupshare

Example: Mounting a DXi Host NAS Share within a Virtual Machine

When you have finished using the .ISO image file used to create the VM, unmount the image on the DXi using the syscli --ejectiso dae command.

Command Attributes

Review the following attribute descriptions.

‑‑eject daeiso	Ejects the .iso file for the VM.
‑‑name <vm name>	The name of the VM to eject the .iso file.

Once the .iso image file has been ejected from the VM on the DXi, delete the file from the /Q/shares/VM/Iso directory

Note: The cliadmin user account does have permisson to remove files. To remove the .iso image file, log in to the DXi system using the ServiceLogin user account.

Example: Delete an Image File

This command deletes an existing virtual machine (VM) instance.

WARNING: The VM MUST be shut down before running this command. A running VM will not be deleted.

Command Attributes

Review the following attribute descriptions.

‑‑delete dae	Delete the VM instance.
‑‑name <vm name	The name of the VM to be deleted.
‑‑sure	If specified, this command will execute immediately without asking for confirmation.

This command exports a virtual machine (VM) image to a file suitable for import on another system.

Note: VM image exports can take 10 or more minutes to complete.

Command Attributes

Review the following attribute descriptions.

‑‑export dae	Export a VM image.
‑‑name <vm name>	The name of the VM image to save.
‑‑path <path for image>	(Optional) Destination for the exported image. The default path is /Q/shares/VM/VMExportedImages.

This command imports a virtual machine (VM) image exported using --import dae.

Command Attributes

Review the following attribute descriptions.

‑‑import dae	Import a VM image.
‑‑image <path name>	The name of file containing the VM image to import.
‑‑name <new name>	The name of the imported VM if different from the original name.

This command lists current DAE virtual machines (VMs) and summary information on each VM.

Note: Only the cliadmin can access the VM with VNC Viewer

Command Attributes

Review the following attribute descriptions.

‑‑list dae	List the VM instance(s).
‑‑name <vm name>	The name of a specific VM to show (optional).

This command lists DAE virtual machine (VM) image files in a specified directory.

Command Attributes

Review the following attribute descriptions.

‑‑list daeexport	Retrieves a list of VM image export files in a specified directory.
‑‑path <export file path>	The directory to search for VM image export files. If not specified, the default path is /Q/shares/VM.

This command performs a clean operating system (OS) shutdown of the virtual machine (VM). All services are cleanly shutdown within the VM before it is powered off.

Command Attributes

Review the following attribute descriptions.

‑‑shutdown dae	Shutdown the VM instance.
‑‑name <vm name>	The name of the VM to shutdown.
‑‑poweroff	If specified, the VM instance is immediately powered off. The current state is not preserved, so any open files or active I/O could result in VM corruption.
‑‑sure	If specified, this command will execute immediately without asking for confirmation.

This command starts a virtual machine (VM) that has been shutdown or stopped.

Command Attributes

Review the following attribute descriptions.

‑‑start dae	Starts the VM instance.
‑‑name <vm name>	The name of the VM to start.

This command stops a virtual machine (VM) and saves the current state to disk.

Command Attributes

Review the following attribute descriptions.

‑‑stop dae	Stops the VM instance.
‑‑name <vm name>	The name of the VM to stop.
‑‑sure	If specified, this command will execute immediately without asking for confirmation.

This command allows for the modification of an existing DAE virtual machine (VM) instance.

In order to update VM settings, the VM must be in a shut off state. You can put a DAE VM into a shut off state by either stopping or shutting down the VM (see and ).

Note: If VM is stopped and has a saved RAM state file, updating that VM will remove the RAM saved state file.

Command Attributes

Review the following attribute descriptions.

‑‑edit dae	Edit VM instance.
‑‑name <vm name>	Edit the name of the VM.
‑‑cpus <num cpus>	Edit the number of CPUs for the VM.
‑‑memory <ram>	Modify the amount of RAM memory (in MB) for the VM.
‑‑appnetwork <nic port>	Modify the application network devices (NIC ports). More than one may be specified.
‑‑autostart yes|no]	Change the autostart status of the VM on the system boot. The default is no.
‑‑password <password>	Change the password for accessing the console over VNC.
‑‑sure	If specified, this command will execute immediately without asking for confirmation.