Appendix - Deploying UFM Appliance from an ISO File

This section provides a step-by-step guide for deploying UFM Enterprise Appliance from an ISO file.

The ISO installation is set to use interface "eno8303" via a DHCP as default; if DHCP is unavailable, the installer will request manual intervention to set the IP address manually on "eno8303" or to skip the IP settings altogether.

If IP settings are skipped, they can be set manually after the installation. Refer to Getting Started.

If a different interface should be used, skip the IP settings when prompted.

Extract the ufm-appliance-<version>-omu.tar to a temporary directory.

Extract TAR file

Copy
Copied!
            

tar xzf /path/to/tar.tar -C /tmp

An ISO file and an upgrade script will be present inside the directory.

Extract TAR file

Copy
Copied!
            

ls -ltrh /tmp/ufm-appliance-<version>/

Follow the following steps based on the desired method of installation.

Virtual Media via Management Port

  1. Open a web browser and navigate to https://<IDRAC-ILO-address>

  2. On the Dashboard pane, click on the virtual console icon on the bottom right corner of the screen.

    1-version-1-modificationdate-1682552409900-api-v2.png

  3. A new virtual console window will pop out, on the top right corner, click on the virtual media.

    2-version-1-modificationdate-1682552409973-api-v2.png

    A new console window will appear

  4. Click on the "Connect Media" button.

    3-version-1-modificationdate-1682552410027-api-v2.png

  5. Under the "Map CD/DVD" section, click on "Choose file" and select the ufm-appliance-<version>.iso file extracted from the tar archive previously extracted and click on the "Map Device" button. Then, "Close".

    4-version-1-modificationdate-1682552410080-api-v2.png

  6. Click on the "Boot" menu button on the top left, on the opened menu choose "Virtual CD/DVD/ISO".

    5-version-1-modificationdate-1682552410137-api-v2.png

  7. Click on the "Power" menu button and select "Reset System (warm boot)" entry.

    6-version-1-modificationdate-1682552410187-api-v2.png

  8. At this point an automatic installation should start.

    7-version-1-modificationdate-1682552410237-api-v2.png

    Installation will auto start after 30 seconds, press the enter key to start it immediately.

  9. Proceed to Finalizing the Installation.

Physical USB

Burn ISO to USB

Windows

  1. Download and open Rufus (Rufus).

  2. Select the USB device from the drop down menu under "Devices".
    Click on "SELECT" and select ufm-appliance-<version>.iso
    Validate that the "Partition Scheme" is MBR and "Target System" is "BIOS or UEFI", as seen in the screenshot below.
    Click "START".

    8-version-1-modificationdate-1682552410313-api-v2.JPG

  3. An "ISOHybrid image detected" prompt will pop up, choose "Write in DD mode" and click "OK".

    9-version-1-modificationdate-1682552410373-api-v2.png

  4. Another message will appear stating that all data on the USB device will be lost, click "OK and continue".

    10-version-1-modificationdate-1682552410440-api-v2.png

  5. Wait for Rufus to finish.

Linux

  1. Identify the USB drive:

    Important

    Do not run the following commands on a hard drive device, but only on the USB. The USB drive in the below command is mapped to sdb.

    Copy
    Copied!
                

    root@ubuntu18:~# ls -ltrh /dev/disk/by-id/usb* lrwxrwxrwx 1 root root  9 Jan  2 13:44 /dev/disk/by-id/usb-SanDisk_Cruzer_Glide_3.0_4C530000040724111091-0:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Jan  2 13:44 /dev/disk/by-id/usb-SanDisk_Cruzer_Glide_3.0_4C530000040724111091-0:0-part1 -> ../../sdb1

  2. Copy the ufm-appliance-<version>.iso to the USB using the following dd command:

    Important

    Do NOT run the following commands on a hard drive device but only on the USB. The USB drive in the below command is mapped to /dev/sdb.

    Copy
    Copied!
                

    dd if=/path/to/ufm-appliance-<version>.iso of=/dev/sdb bs=4M status=progress oflag=sync

  3. Verify that the USB is bootable:

    Copy
    Copied!
                

    root@ubuntu18:~# fdisk -l /dev/sdb Disk /dev/sdb: 14.9 GiB, 16005464064 bytes, 31260672 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x594ec03e   Device     Boot Start      End  Sectors  Size Id Type /dev/sdb1  *       64 15679439 15679376  7.5G 17 Hidden HPFS/NTFS

  4. Unplug the USB.

Manufacture UFM Appliance via the USB

  1. Plugin the USB device to the back panel (Front panel USB is disabled).

  2. Open a web browser and navigate to https://<IDRAC-ILO-address>.

  3. Navigate to "Configuration" → "BIOS Settings" → "Boot Settings" and set "Generic USB boot" option to enabled.

    11-version-1-modificationdate-1682552410533-api-v2.JPG

  4. On the same pane, scroll down to "One-Time Boot" → "One-Tome Boot Device List" select "UEFI Boot Sequence Device".
    In "UEFI Boot Sequence Device", select the connected USB device and click apply.
    On the bottom of the page click on "Apply And Reboot" button.

    12-version-1-modificationdate-1682552410593-api-v2.png

  5. A popup message will appear click on "Job Queue" button.

    13-version-1-modificationdate-1682552410683-api-v2.png

  6. A "Job Queue" pane will open to monitor the progress of the created job.

    14-version-1-modificationdate-1682552410757-api-v2.png

  7. Navigate to the Dashboard pane, click on the virtual console icon on the bottom right corner of the screen.

    15-version-1-modificationdate-1682552410807-api-v2.png

    A new console window will appear that shows the progress of restarting the node to USB.

    16-version-1-modificationdate-1682552410857-api-v2.png

  8. At this point an automatic installation should start.

    17-version-1-modificationdate-1682552410930-api-v2.png

    The installation will auto start after 30 seconds, press the enter key to start it immediately.

  9. Proceed to the following section to proceed with the installation.

Finalizing the Installation

Installation may take 20-90 minutes and depends on the chosen media; with USB it takes around 20 minutes and via the virtual media take around 90 minutes (this may vary and depends on network speed).

  1. Installation should start automatically, and the progress is presented on the screen.

    18-version-1-modificationdate-1682552411007-api-v2.png

  2. In case a DHCP is not available or not configured, a prompt will pop up with notification stating that DHCP cannot be set.

    19-version-1-modificationdate-1682552411093-api-v2.png

  3. Press "Enter" to continue, a sub menu will appear.

    20-version-1-modificationdate-1682552411180-api-v2.png

    You can choose the preferred option and follow the instructions on the screen by configuring it manually, or skip network configuration and add them at a later point.

  4. The installation procedure should continue.

    21-version-1-modificationdate-1682552411267-api-v2.JPG

    Warning

    The installer may seem stuck when the status bar gets to "Running preseed" (14-16 %) - it takes a while to pass this, the script runs in the background and the progress can be seen by switching to tty4 (optional) by opening the virtual keyboard.

    Important

    This should be done on the virtual keyboard, otherwise it will close the installation window. The installation window can be opened by pressing "ALT+F4" on the virtual keyboard.

    22-version-1-modificationdate-1682552411847-api-v2.JPG

    tty4 will open and the install log will show current status.

    23-version-1-modificationdate-1682552411920-api-v2.JPG

    To return to the progress screen, click on "ALT+F1" on the virtual keyboard.

  5. The server will automatically reboot when the installation procedure is completed.

  6. At this point, the login screen will appear

    Important

    The installation procedure is not finished yet. At this point, an automatic service will install additional SW (including the UFM Enterprise Appliance).

    Upon installation completion, a message will appear on any attached terminal stating UFM-OS-FISTBOOT-SUCESS for successful installation, or UFM-OS-FISTBOOT-FAILED for failed installation.
    A log can be checked in /var/log/ufm-os-firstboot.log.
    The below is an example from an attached ssh session:

    24-version-1-modificationdate-1682552412493-api-v2.JPG

    Example from the console web screen:

    25-version-1-modificationdate-1682552412577-api-v2.JPG

    To manually check if the installation procedure has completed or is still running:

    Copy
    Copied!
                

    systemctl status ufm-os-firstboot.service

    If the installation is still running, the below status will be presented:

    26-version-1-modificationdate-1682552413147-api-v2.png

    If the installation is completed, an error message stating that ufm-os-firstboot.service does not exist (as it is deleted when the installation is finished).

    27-version-1-modificationdate-1682552413217-api-v2.png

  7. The installation is now finished and the UFM Enterprise Appliance can be started. If the network configuration step is skipped in previous steps, it can now be configured.

© Copyright 2023, NVIDIA. Last updated on Dec 13, 2023.