Versions Compared

Old Version 5

changes.mady.by.user Shirly Tsang

Saved on

compared with

New Version Current

changes.mady.by.user Alex Mandel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Log in to the Cloud Services Portal.

  2. Go to Administration - > Downloads.

  3. On the Downloads page, click Download Package for OVA in the On-Prem the BloxOne Hosts section.
    Choose an applicable package from the drop-down menu

  4. BloxOne downloads the .ova file to your system. Note that if you are deploying the a Data Connector host, choose the high-capacity increase the disk size of the BloxOne host to 750 GB OVA package.Click Download Package for VM, and then save the package on your system. For information on how to change the disk size of your BloxOne host, see Increasing Disk Size for NIOS-X Servers in OVA.
  5. Connect to VMware vSphere Client 6.5.0.

    The screenshot shows the About VMware vSphere dialog, which contains and OK button.Image Modified

Select the OVA image downloaded from the Cloud Services Portal. Click Next. 

The screenshot shows the Source tab of the Deploy OVF Template dialog. The tab contains the Deploy from a file or URL Selection field with a Browse button next to it, as well as the Back, Next, and Cancel buttons.Image Modified

  1. Verify the OVF Template Details. Click Next. 

    The screenshot shows a summary of details on the OVF Template Details tab of the Deploy OVF Template dialog. Image Modified

  2. Specify the Name and Location for the deployment image. Click Next. 

    The screenshot shows the Name and Location tab of the Deploy OVF Template dialog. The tab contains a text field called Name.Image Modified

  3. Select the Resource Pool. Click Next.
  4. Select the Storage where the virtual machine is stored. Click Next. 

    The screenshot shows the Storage tab of the Deploy OVF Template dialog. The tab shows available destination storages for the virtual machine files.Image Modified

  5. Select the Disk Format. Click Next.

    The screenshot shows the Disk Format tab of the Deploy OVF Template dialog. The tab shows the fields for datastore, available space, and three types of provisioning, which are Thick Provision Lazy Zeroed, Thick Provision Eager Zeroed, and Thin Provision.Image Modified

  6. Configure the Network Mapping. Click Next.

    The screenshot shows the Network Mapping tab of the Deploy OVF Template dialog. The upper section shows the table of Source Networks and Destination Networks, and the lower section shows the description of the selected network.Image Modified

  7. Customize the image for this deployment in Properties. Click Next.
    In the Cloud Credentials section, specify the Join Token and HTTPS Proxy.

    The screenshot shows the Properties tab of the Deploy OVF Template dialog. The tab contains the Cloud Credentials section with the Join Token and HTTPS Proxy fields, and the IPv4 Network Settings section with the required fields IPv4 Address, IPv4 Netmask, and IPv4 Gateway.Image Modified

  8. Verify the configuration in the Ready to Complete screen. Check the Power on after deployment box to launch the virtual machine. 

    The screenshot shows the Ready to Complete tab of the Deploy OVF Template dialog. The tab shows the settings, a checkbox called Power on after deployment, and the Back, Finish, and Cancel buttons. Image Modified

  9. Click Finish.
  10. To configure multiple network interfaces for your host, select the VM from Inventory (in power off state), and then right-click the VM and select Edit Settings. For information about configureing multiple interfaces for hosts, see Configuring Multiple Network Interfaces.
  11. In the Virtual Machine Properties screen, select the Hardware tab, and then click Add -> Add Hardware, as illustrated below:
    The screenshot shows the Hardware tab of the Virtual Machine Properties screen. The tab contains a Hardware Summary table, a Memory Configuration section, an OK button, and a Cancel button.Image Modified
  12. In the Add Hardware -> Device Type screen, select Ethernet Adapter, and then click Next, as illustrated below:

    The screenshot shows the Add Hardware screen on the Hardware tab of the Virtual Machine Properties screen. On the Add Hardware screen, the Device Type screen is open and shows the list of available devices, where Ethernet Adapter is selected. Image Modified
  13. In the Add Hardware -> Network Type screen, select the Adapter Type and Network Label, and then click Next, as illustrated below:

    The screenshot shows the Add Hardware screen on the Hardware tab of the Virtual Machine Properties screen. On the Add Hardware screen, the Network Type screen is open and shows the Adapter Type and Network Connection fields, which are both dropdown lists.Image Modified
  14. The Ready to Complete screen appears and displays the summary of the settings. Click Finish.
  15. On the Hardware tab, the new network interface appears as New NIC (adding), as illustrated below. Click OK.

    The screenshot shows the Hardware tab of the Virtual Machine Properties screen. In the Hardware Summary table, New NIC (adding) is selected. In the right pane of the tab, the properties of New NIC (adding) are shown.Image Modified
  16. Power on the VM.
  17. Note the IP address shown on the VM Console.

    The screenshot shows the console, which shows the IP address and other properties of the VMImage Modified

  18.  Launch the bootstrap UI using the IP address shown in the console and with Login = admin and Password = the last 8 characters of the Product serial number.
    Click Login.

    The screenshot shows the login dialog. Image Modified

  19. Specify other required network configuration, and then click Apply, as shown below:

    The screenshot shows addition required network configuration.Image Modified




  20. The host is also visible on the Cloud Services Portal, as shown below:

    The screenshot shows the dialog for specifying required network configuration. Image Modified

Note
titleNote

You can perform the preceding steps directly on the virtual machine without connecting to the virtual machine with the VMware vSphere Client. 

...