OpenManage Enterprise can be deployed programmatically (using a script) on VMWare ESXi version 6.5 or later.
NOTE: Programmatic/scripted deployment is only supported using the primary interface.
NOTE: If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as
DISABLED and must be configured by the user.
NOTE: You must use the latest versions of OVF Tool and Python 3.0 or later for the programmatic deployment.
To programmatically deploy OpenManage Enterprise, do the following:
Download and extract the
openmanage_enterprise_ovf_format.zip file or download the following OVF files individually from the support site:
Open the
ovf_properties.configovf_properties.config and set the following parameters:
Table 1. Parameters used in
ovf_properties.configovf_properties.configThe following table lists the parameters used in
ovf_properties.configovf_properties.config.
Parameter
Accepted Values
Description
bEULATxt
true or false
By setting this value to true, you agree to the terms and conditions in the End-User License Agreement (EULA). The EULA is available at the bottom of the ovf_properties.config file.
adminPassword
Must contain at least one character in: uppercase, lowercase, digit, and special character. For example, Dell123$
Type a new administrator password for the OpenManage Enterprise.
bEnableDHCP
true or false
Set to true if you want the appliance to enable IPv4 DHCP and to ignore the static IPv4.
bEnableIpv6AutoConfig
true or false
Set to true if you want the appliance to enable IPv6 auto configuration and to ignore the static IPv6.
staticIP
static IP in CIDR format
Can be IPv4 or IPv6. (You cannot set both the IPv4 and IPv6 types at a time.)
gateway
IPv4 or IPv6
You cannot set static Gateway as IPv4 and IPv6 types at a time.
Run the
update_ovf_property.pyupdate_ovf_property.py script.
This script modifies the openmanage_enterprise.x86_64-0.0.1.ovf openmanage_enterprise.x86_64-0.0.1.ovf file for deployment in accordance with the values set in the ovf_properties.config file. When the script finishes execution, a sample ovftool command is displayed. It contains tags such as
<DATASTORE>, <user>, <password>, <IP address><DATASTORE>, <user>, <password>, <IP address>, and so on, that you must replace as per your deployment environment. These settings define the resources that are used on the target ESXi system and also the credentials and IP address of the target system.
NOTE: Remember to replace the entire tag including the
<< and
>> symbols.
Run the modified ovftool command from the previous step.
NOTE: The ovftool command must be run with the --X:injectOvfEnv and --powerOn flags because they are required for programmatic deployment.
After the ovftool command is run, the manifest validates and the deployment begins.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\