UCSD - Updated script to configure Custom ESXi ISO Image on UCS Director BMA 5.x

Version 2

    Script Name:




    UCS Director Baremetal Agent (BMA) 5.0 provides a new script called 'isoExtractor.sh' under /opt/infra folder which simplifies in configuring PXE OS images for Baremetal automated OS Installation. The limitation with this script is, it doesn't configure Custom ESXi ISO images appropriately. The new updated script 'isoExtractor_updated.sh' attached to this document supports Custom ESXi ISO images as well.


    Compatible UCS Director BMA version:

    UCS Director BMA 5.0 & above


    Instructions for use:

    1. Download the attached 'isoExtractor_updated.sh' file below to your computer.
    2. Remember the location of the saved file on your computer.
    3. Copy the file 'isoExtractor_updated.sh' to UCS Director Baremetal Agent using ssh client into /opt/infra folder.
    4. Change the file permissions using the command 'chmod 755 /op/infra/isoExtractor_updated.sh'


    Steps to run the script:



    Copy the ESXi ISO image(s) to an appropriate location in the Baremetal Agent directory structure.


    Navigate to /opt/infra and run isoExtractor_Updated.sh

    The following is a sample provisioning scenario:

    root@localhost infra]# pwd /opt/infra

    root@localhost infra]# ./isoExtractor_Updated.sh     

    Please select the OS Type         

    1)  ESXi 4.1        

    2)  ESXi 5.0        

    3)  ESXi 5.1        

    4)  ESXi 5.5        

    5)  CentOS        

    6)  SUSE Linux        

    7)  Other        

    SELECT> 4    


    Image path : /opt/image/VMWare-VMvisor-Installer-5.5.0-1111.x86_64.iso           

    OS catalog name : BMA-184-ESXi5.5


    When prompted, choose the ESXi Image OS Type (2 or 3 or 4) and provide the ESXi ISO image path location and Catalog name.


    After the script execution is completed, navigate to /opt/cnsaroot/images/catalogname and confirm that the image is available in that location.


    Navigate to /opt/cnsaroot/templates/catalogname and confirm that the PXE configuration files are available in that location. (Files: boot.cfg, ks.cfg & pxe.cfg)