SA installation configuration parameters

Please enter the database password for the opsware_admin user. This password is used to connect to the Oracle database. If you are installing Oracle with SA the opsware_admin user will be created with this password. Make sure the password complexity matches the security guidelines in your organization.

Parameter:
truth.oaPwd

Specify the opsware_admin password created by your database administrator.

opsware_admin is an Oracle user that the Installer uses during installation to perform required tasks.

If you are installing the SA-supplied Oracle database created by the Installer, the password you provide here will be associated with opsware_admin during installation of the database.

If you have an existing Oracle database installation, this must be the password that your DBA set for the opsware_admin user when setting up the Oracle instance on the server.

Source: Oracle DBA

Enter the short name of the facility where the SA Installer is being run (no spaces).

Parameter:
truth.dcNm

Specify the short name of the facility where the Installer is being run. This would also be the location of the First Core.

Some SA processes use this name internally. It must be in uppercase, less than 25 characters, and cannot contain spaces or special characters (underscores are allowed, dashes are not allowed).

Source: Variable

Example: HEADQUARTERS

Enter the directory that contains the Microsoft patching utilities. (Press Ctrl-I for a list of required files) or enter "none" if you do not wish to upload these utilities.

Parameter:
windows_util_loc

Specify the directory to which you have already copied the Microsoft utilities required for Window’s Patch Management or enter “none” if you do not plan to perform Windows patching and do not want to upload these files.

Should you decide later that you need to perform Windows patching, you will need to install the required Windows Patch Management files either by using the SA Client’s Import feature or the populate-opsware-update-library command line script as described in the
Server Patching.

Source: Variable, however, this directory must exist on the same server as the Software Repository (part of the Slice Component bundle).

Example: /tmp

Please enter the IP address of the Management Gateway.

Parameter:
mgw_address

Specify the IP address of the Management Gateway. The Management Gateway manages Core-to-Core communications.

Core Gateways installed on Secondary Cores and/or Satellite Gateways also communicate with the Management Gateway.

Source: Variable

Example: 192.168.165.242

Do you want SA to be in FIPS mode? (y/n) [n]

Parameter:
fips.mode

Specify is FIPS mode will be enabled or disabled for the SA installation.

Source: Variable

Example: y

Enter the hashing algorithm for the SA cryptographic module. [SHA256]:

Parameter:
crypto.hash_algorithm

Specify the hashing algorithm that SA should use for the cryptographic module.

Source: Variable

Valid Values: SHA1, SHA224, SHA256, SHA384, or SHA512.

Enter the key length [2048 or 4096] used for hashing algorithm of SA cryptographic module. [2048]:

Parameter:
crypto.key_length

Specify the key length to use for the cryptographic module hashing algorithm.

Source: Variable

Valid Values: 2048 or 4096

Enter the hostname/IPaddress of the Oracle database server

Parameter:
db.host

Specify the hostname/IPaddress of the Oracle database server.

Source: Variable

Example: 192.168.165.242

Enter the service name of the Model Repository instance in the facility where Opsware Installer is being run

Parameter:
truth.servicename

Specify the service name, also known as the alias, for the Model Repository. For a Single Core, this is the server on which you are running the Installer.

If you are installing the default Oracle database created by the Installer, the service name you provide here will be associated with the database during installation.

If you intend to use an existing Oracle database, you can find the service name by looking in the tnsnames.ora file on the Model Repository instance. The service name is the value before the first equals sign (=) in the file. The location of this file can vary, so check with your DBA if you are not sure where to find it.

Source: Check with the DBA who created the Oracle database.

Example: truth.example.com

Enter the SID of the Oracle instance containing the Model Repository

Parameter:
db.sid

Specify the database system ID (SID) that was set when Oracle was installed on the server where the Model Repository is installed.

If you are installing the SA-supplied Oracle database created by the Installer, the SID is truth.

If you will be using an existing SA-supplied Oracle database, you will not be asked to supply this parameter.

For an existing non-SA-supplied Oracle database, you can find the SID by looking in the tnsnames.ora file. The location of this file can vary, so check with your DBA if you are not sure where to find it.

Source: Check with the DBA who created the Oracle database.

Default: truth

Example: DTC05

Enter the port on which the database is listening

Parameter:
db.port

Specify the port on which the Model Repository database listens.

Source: Variable

Example: 1521

Enter the path of the Oracle home directory.

Parameter:
db.orahome

Specify the base directory of the Oracle database installation.

If you are installing the SA-supplied Oracle database created by the Installer, the default location of ORACLE_HOME is
/u01/app/oracle/product/12.1.0.2/db_2.

If you have an existing SA-supplied Oracle database, you will not be prompted for this parameter.

For an existing non-SA-supplied Oracle database, you can determine the Oracle home directory by logging in as the oracle user on the Model Repository server, and checking the value of the $ORACLE_HOME environment variable. (For a remote database installation, this parameter refers to the Oracle Client on the Model Repository server.)

Source: The DBA who created the Oracle database.

Example: /u01/app/oracle/product/12.1.0.2/db_2

Please enter the host (NFS server) where Software Repository Content resides.

Parameter
word.store.host

Specify the host name of the server where Software Repository content is stored.

Source: Variable

Example: 192.168.165.243

Please enter the path to the server where Software Respiratory content resides.

Parameter
word.store.path

Specify the path to the server where Software repository content is stored. This will be to the server specified in word.store.host.

Source: Variable

Please enter the OS Provisioning Boot Server IP address or hostname.

Parameter:
bootagent.host

Specify the IP address for server on which you installed the SA Provisioning Boot Server.

Important: You must provide a valid IP address or host name that can be resolved from the server on which you installed the SA Provisioning Boot Server component and the Build Manager. Additionally, the host name must be resolvable by SA managed servers for SA Provisioning.

Source: Variable

Example: foo.example.com

Please enter the database password for the opsware_admin user. This password is used to connect to the Oracle database. If you are installing Oracle with SA the opsware_admin user will be created with this password. Make sure the password complexity matches the security guidelines in your organization.

Parameter:
truth.oaPwd

Specify the opsware_admin password created by your database administrator.

opsware_admin is an Oracle user that the Installer uses during installation to perform required tasks.

If you are installing the SA-supplied Oracle database created by the Installer, the password you provide here will be associated with opsware_admin during installation of the database.

If you have an existing Oracle database installation, this must be the password that your DBA set for the opsware_admin user when setting up the Oracle instance on the server.

Source: Oracle DBA

Enter the short name of the facility where the SA Installer is being run (no spaces).

Parameter:
truth.dcNm

Specify the short name of the facility where the Installer is being run. This would also be the location of the First Core.

Some SA processes use this name internally. It must be in uppercase, less than 25 characters, and cannot contain spaces or special characters (underscores are allowed, dashes are not allowed).

Source: Variable

Example: HEADQUARTERS

Enter the hashing algorithm for the SA cryptographic module [SHA256]:

Parameter:
crypto.hash_algorithm

Specify the hashing algorithm that SA should use for the cryptographic module.

Source: Variable

Valid Values: SHA1, SHA224, SHA256, SHA384, or SHA512.

Enter the key length [2048 or 4096] used for hashing algorithm of SA cryptographic module. [2048]:

Parameter:
crypto.key_length

Specify the key length to use for the cryptographic module hashing algorithm.

Source: Variable

Valid Values: 2048 or 4096

Enter the directory that contains the Microsoft patching utilities. (Press Ctrl-I for a list of required files) or enter "none" if you do not wish to upload these utilities.

Parameter:
windows_util_loc

Specify the directory to which you have already copied the Microsoft utilities required for Window’s Patch Management or enter “none” if you do not plan to perform Windows patching and do not want to upload these files.

Should you decide later that you need to perform Windows patching, you will need to install the required Windows Patch Management files either by using the SA Client’s Import feature or the populate-opsware-update-library command line script as described in the
Server Patching.

Source: Variable, however, this directory must exist on the same server as the Software Repository (part of the Slice Component bundle).

Example: /tmp

Please enter the IP address of the Management Gateway.

Parameter:
mgw_address

Specify the IP address of the Management Gateway. The Management Gateway manages Core-to-Core communications.

Core Gateways installed on Secondary Cores and/or Satellite Gateways also communicate with the Management Gateway.

Source: Variable

Example: 192.168.165.242

Please enter the password for the cryptographic material.

Parameter:
decrypt_passwd

Specify the password to use for decrypting cryptographic material.

This password must be the same across all cores in a Multimaster Mesh.

If you have an existing SA installation, this must be the password previously set for decrypting cryptographic material.

Password Restrictions: The password cannot contain spaces and it must be between 4 and 20 characters long.

Source: Variable

Example: x145_pwd03

Enter the path of the Oracle home directory.

Parameter:
db.orahome

Specify the base directory of the Oracle database installation.

If you are installing the SA-supplied Oracle database created by the Installer, the default location of ORACLE_HOME is
/u01/app/oracle/product/12.1.0.2/db_2.

If you have an existing SA-supplied Oracle database, you will not be prompted for this parameter.

For an existing non-SA-supplied Oracle database, you can determine the Oracle home directory by logging in as the oracle user on the Model Repository server, and checking the value of the $ORACLE_HOME environment variable. (For a remote database installation, this parameter refers to the Oracle Client on the Model Repository server.)

Source: The DBA who created the Oracle database.

Example: /u01/app/oracle/product/12.1.0.2/db_2

Please enter the host (NFS server) where Software Repository Content resides.

Parameter
word.store.host

Specify the host name of the server where Software Repository content is stored.

Source: Variable

Example: 192.168.165.243

Please enter the path to the server where Software Respiratory content resides.

Parameter:
word.store.path

Specify the path to the server where Software repository content is stored. This will be to the server specified in word.store.host.

Source: Variable

Please enter the OS Provisioning Boot Server IP address or hostname.

Parameter:
bootagent.host

Specify the IP address for server on which you installed the SA Provisioning Boot Server.

Important: You must provide a valid IP address or host name that can be resolved from the server on which you installed the SA Provisioning Boot Server component and the Build Manager. Additionally, the host name must be resolvable by SA managed servers for SA Provisioning.

Source: Variable

Example: foo.example.com

Please enter the password for the cryptographic material.

Parameter:
decrypt_passwd

Specify the password to use for decrypting cryptographic material.

This password must be the same across all cores in a Multimaster Mesh.

If you have an existing SA installation, this must be the password previously set for decrypting cryptographic material.

Password Restrictions: The password cannot contain spaces and it must be between 4 and 20 characters long.

Source: Variable

Example: x145_pwd03

Please enter the password for the SA admin user. this is the password that will be used to authenticate the user admin to SA.

Parameter:
cast.admin_pwd

Specify the password for the SA admin user.

Password Restrictions: This password cannot contain spaces.

The Installer automatically creates the admin user.

The first time you log in to the SA Client to access a new Facility, you must log in as the admin user.

Source: Variable

Example: x145_pwd03

Enter the fully qualified path to the directory where the export file will be saved.

Parameter:
truth.dest

You must create this directory on the Model Repository server before you run the Installer.

Specify the directory in which the truth.<new_facility>.tar.gz file will be saved. This directory must reside on the Model Repository server in the source facility. You will see this prompt only when defining a new facility (hpsa_add_dc_to_mesh.sh).

Note: When adding a facility to a Multimaster Mesh, you must export the Model Repository from the source facility, then copy it to the destination facility.

Source: Variable

Default: /var/opt/opsware/truth/

Enter the fully qualified path to the directory that contains the export file.

Parameter:
truth.sourcePath

This parameter is used when a new facility is added to a Multimaster Mesh and the source export file is copied to the new facility. This directory must exist on the server and contain the database export file before you run the Installer on the server.

Specify the directory on the destination facility’s Model Repository server to which you copied the export data file from the source facility.

Source: Variable

Default: /var/opt/opsware/truth/

Please enter the Facility ID (number only, less than or equal to 950, with no leading zeros).

Parameter:
truth.dcId

Specify an ID that uniquely identifies the facility.

When you install the First Core, you will be prompted to provide this ID.

When you install Secondary Cores in the same Multimaster Mesh, SA automatically generates the Facility ID when you add a new facility using the SA Client.

You can determine the Secondary Core’s Facility ID by logging in to the SA Client at the First Core facility, then select Facilities under Administration in the Navigation pane and click the facility’s name.

ID Restrictions: The Facility ID value is capped at 950. Therefore, you must specify a number for the first facility that is far enough below 950 that you will have sufficient IDs available to continue adding facilities to your Multimaster Mesh.

Source: Variable for the first facility; set by the SA for subsequent facilities.

Default: 1

Would you like this facility to mirror all Software Repository content in the mesh?

Parameter:
word.enable_content_mirroring

Enables mirroring (replication) of the Software Repository (word).

Source: Variable

Default: Y

Enter the SID of the Oracle instance that contains the Data Model Repository.

Parameter:
db.sid

Specify the database system ID (SID) that was set when Oracle was installed on the server where the Model Repository is installed.

If you are installing the SA-supplied Oracle database created by the Installer, the SID is truth.

If you have an existing SA-supplied Oracle database, you will not be asked to supply this parameter.

For an existing non SA-supplied Oracle database, you can find the SID by looking in the tnsnames.ora file. The location of this file can vary, so check with your DBA if you are not sure where to look.

Source: The DBA who created the Oracle database.

Default: truth

Example: DTC05

Enter the fully-qualified path to the TNS admin directory (where the tnsnames.ora file resides).

Parameter:
truth.tnsdir

Specify the directory that contains the tnsnames.ora file.

Note: This directory and path must be the same on all servers in a core.

For example, since the Data Access Engine must access the tnsnames.ora file to connect to the Model Repository, the location of tnsnames.ora directory on the Data Access Engine server must be the same as the directory location on the Model Repository server.

If you are installing the SA-supplied Oracle database created by the Installer, the tnsnames.ora file will be installed under /var/opt/oracle.

If you have an existing SA-supplied Oracle database installed, you will not be prompted for this parameter.

If you have an existing non-SA-supplied Oracle database, the location of the tnsnames.ora file can vary, so check with your DBA if you are not sure where to look.

Source: The DBA who created the Oracle database.

Example: /var/opt/oracle

Please enter the port on which the Model Repository database is listening.

Parameter:
db.port

Specify the port on which the Model Repository database listens.

If you have an existing SA-supplied Oracle database, you will not be asked to supply this parameter.

Source: Variable

Default: 1521

Please enter the absolute path on the NFS server for the Opsware Global File System (/user, /home, and /tmp directories). This value should be different from ogfs.audit.path and word.store.path.

Parameter:
ogfs.store.path

Specify the absolute path on the NFS server for the Global File System (/user, /home, and /tmp directories). This value should be different from ogfs.audit.path and word.store.path.

Source: Variable

Default: /var/opt/opsware/ogfs/export/store

Please enter the absolute path on the NFS server for the Opsware Global File System where the audit streams will be stored. This value should be different from ogfs.store.path and word.store.path.

Parameter:
ogfs.audit.path

Specify the absolute path on the NFS server for the Global File System where the audit streams will be stored. This value should be different from ogfs.store.path and word.store.path.

Source: Variable

Default: /var/opt/opsware/ogfs/export/audit

Please enter the port on which Management Gateway in the First Core listens for connections from other Gateways (this value should match the value of mgw_tunnel_listener_port parameter in First Core's CDF. Typically it's set to 2001.)

Parameter:
masterCore.mgw_tunnel_
listener_port

Specify the port on which Management Gateway in the First Core listens for connections from other Gateways (this value should match the value of mgw_tunnel_listener_port parameter in First Core's CDF.

Source: Variable

Default: None

Enter the port on which the Management Gateway will listen for connections from other gateways.

Parameter:
mgw_tunnel_listener_port

Specify the port on which the First and Secondary Cores’ Management Gateways will listen for connections from other Core and Satellite gateways.

Source: Variable

Example: 2001

Please enter the port on which Agents can contact the Agent Gateway to request connections to Core Components.

Parameter:
agw_proxy_port

Specify the port that agents should use to connect to the SA Core.

Source: Variable

Default: 3001

Please enter the pathname to the Linux media.

Parameter:
media_server.linux_media

Specify the path to the Linux OS media on the server on which the Media Server will be installed.

Providing the path to the Linux OS media does not actually copy the media to the Media Server.

See the "OS Provisioning" section in the the SA 10.50 Administration Guide for the steps required to set up the media on the Media Server for SA Provisioning.

Source: Variable, however, this directory must exist on the server where the Media Server is installed.

Default: /media/opsware/linux

Please enter the pathname to the Solaris OS media.

Parameter:
media_server.sunos_media

Specify the path to the Sun Solaris OS media on the server on which the Media Server will be installed.

Providing the path to the Solaris OS media does not actually copy the media to the Media Server

See the "OS Provisioning" section in the the SA 10.50 Administration Guide for the steps required to set up the media on the Media Server for SA Provisioning.

Source: Variable, however, this directory must exist on the server where the Media Server is installed.

Default: /media/opsware/solaris/

Please enter the pathname to the Windows OS media.

Parameter:
media_server.windows_media

Specify the path to the Microsoft Windows OS media on the server on which the Media Server will be installed.

The SA Provisioning feature exports Windows OS media to SMB clients through a Samba share.

Providing the path to the Windows OS media does not actually copy the media to the Media Server.

See the "OS Provisioning" section in the the SA 10.50 Administration Guide for the steps required to set up the media on the Media Server for SA Provisioning.

Source: Variable, however, this directory must exist on the server where the Media Server is installed.

Default: /media/opsware/windows/

Please enter the host name or IP address of the Network Automation (NA) server. (Enter “none” if NA is not installed.)

Parameter:
twist.nasdata.host

Specify the host name or IP address of the server running HPE Network Automation (NA), if installed. If NA is not installed, accept the default value none.

Enter a value without spaces.

Source: The network administrator/SA administrator who installed HPE Network Automation.

Example: 192.168.165.242

Please enter the username used to connect to HPE Live Network. (Leave as "none" if HPELN is not being configured.)

Parameter:
hpln_user_name

Specify the username used to connect to the HPE Live Network (HPELN).

The value should adhere to HPELN's standard. A minimum of 5 characters and it cannot contain the special characters &, |, or *. Also, any of the invalid characters defined for the SA install also apply, such as leading #, quotes, and so on

Source: Variable

Default: None

Please enter the password associated with the username used to connect to HPE Live Network. (Leave as "none" if HPELN is not being configured.)

Parameter:
hpln_password

Specify the HPELN user password used to connect to the HPE Live Network (HPELN).

The value must follow the same rules as hpln_user_name, except the minimum characters accepted is 6.

Source: Variable

Default: None

Please enter the address of the proxy used to connect to the HPE Live Network. (Leave as "none" if HPELN is not being configured or no proxy is needed to connect to HPE Live Network.)

Parameter:
hpln_proxy

Specify the IP address or hostname of the proxy used to connect to the HPE Live Network (HPELN)

The value must follow the following format: <protocol>://<host> or <protocol>:
//<host>:<port>.

If no <port> value is provided, the default 3128 is used.

Source: Variable

Default: None

Please enter the username of the proxy user required to connect to the HPE Live Network. (Leave as "none" if HPELN is not being configured, no proxy is configured or if no username is needed.)

Parameter:
hpln_proxy_user

Specify the username for the HPELN proxy user.

The invalid characters for this parameter follow the SA convention for usernames, such as no leading #, no quotes, no whitespace, and so on.

Source: Variable

Default: None

Please enter the password of the proxy user required to connect to the HPE Live Network. (Leave as "none" if HPELN is not being configured, no proxy is configured or if no username is needed.)

Parameter:
hpln_proxy_pwd

Specify the password for the HPELN proxy user.

The invalid characters for this parameter follow the SA convention for usernames, such as no leading #, no quotes, no whitespace, and so on.

Source: Variable

Default: None

Please enter the gateway Bandwidth Configuration Management for remote connections port.

Parameter:
opswgw.ConfigPort

Specify the port to be used for pushing bandwidth configurations to Satellite Gateways.

Source: Variable

Default: None

Please enter the gateway bandwidth usage channel port.

Parameter:
opswgw.BwUsageChannelPort

Specify the port to be used for retrieving Satellite Gateway bandwidth usage information.

Source: Variable

Default: None

Enter the short name of the new facility you would like to define

Parameter:
newCore.dcNm

Specify the default facility name for the Secondary Core.

Some SA processes use this name internally. It must be less than 25 characters, and cannot contain spaces or special characters (both dashes and underscores are allowed).

Source: Variable

Example: NORTHSIDE

Enter the IP address of the host where you want to install the Model Repository in the new facility.

Parameter:
newCore.dbHost

Specify the IP address of the host on which you will install the Model Repository for the new target core.

Source: Variable

Example: 192.168.165.242

Please enter the SID of the Oracle instance containing the Model Repository for the new facility.

Parameter:
newCore.dbSid

Specify the database system ID (SID) of the Oracle instance that will contain the Model Repository for the new facility.

You will need to supply this parameter only if you will be using a remote non-SA supplied Oracle database.

Source: Variable

Example: truth

Please enter the port on which the database is listening for the new facility.

Parameter:
newCore.dbPort

Specify the port on which the new facility’s Model Repository database will listen.

You will need to supply this parameter only if you will be using a remote non-SA supplied Oracle database.

Source: Variable

Example: 1521

Please enter the IP address of the device where you are planning to install the Infrastructure component in the new facility (or where the management gateway will be installed).

Parameter:
newCore.mgwIP

Specify the IP address of the host on which you will install the Infrastructure Component bundle or the host on which the Management Gateway will be installed.

Source: Variable

Example: 192.168.165.202

Enter the subdomain for the facility you are about to create (lowercase, no spaces).

Parameter: newCore.dcSubDom

Specify the fully-qualified DNS subdomain where the Destination Multimaster Core is to be deployed.

This value must be unique for each core in the Multimaster Mesh, both Source and Destination Cores. The value is based on the VLAN for the facility in which you are installing the Multimaster core.

The subdomain name must be in lowercase with no spaces, less than 50 characters, and in subdomain format.

Source: Your network administrator.

Example: dc2.example.com

Enter the service name (aka TNS name) of the Model Repository instance.

Parameter: newCore.servicename

Specify the service name, also known as the alias, for the core’s Model Repository. You will see this prompt only when installing a new First Core.

If this is a new installation, the service name you specify will be associated with the Model Repository during installation.

If you plan to use an existing Model Repository, you can find the service name by looking in the tnsnames.ora file on the Model Repository instance. The location of this file can vary, so check with your DBA if you are not sure where to look.

Source: The DBA who created the Oracle database.

Example: truth02.example.com

Are you absolutely sure you want to remove all packages in the repository? [Y/N]

Parameter:
word.remove_files

If you answer Yes, the packages, logs, and cryptographic material for the Software Repository are removed.

Default: None

Are you absolutely sure you want to remove users' OGFS home and audit directories? (home and audit directories will only be removed if they are stored on the Software Repository server) (Y/N)?

Parameter:
ogfs.remove_home_dirs

Respond Yes if you want the uninstall to remove all users’ OGFS home and audit directories. Backup any information you want to retain.

Source: Variable

Default: None

Do you need to preserve any of the data in this database? [Y/N]

Parameter: truth.uninstall.needdata

Uninstalling the Model Repository permanently deletes all data in the database, therefore, the uninstallation process stops if you reply Yes to this prompt.

If you want to do an uninstallation, backup your data, run the uninstallation again and answer No to this prompt. Remember, the Installer does not preserve any data.

Default: Y

Are you sure you want to remove all data and schema from this database? [Y/N

Parameter:truth.uninstall.aresure

Uninstalling the Model Repository by responding Yes permanently deletes all data in the database. You can stop the uninstallation by responding No to this prompt.

Default: None

Would you like to preserve the database of cryptographic material? [Y/N]

Parameter:
save_crypto

If you answer Yes, the database of cryptographic material is saved. If you answer No, the material is deleted as part of the uninstallation.

Default: None

Would you like to preserve the HPELN content? (Y/N)

Parameter:
hpln.uninstall.keepcontent

Responding No uninstalls all HPE Live Network content.

Source: Variable

Default: None

Parameter

Description

Are you absolutely sure you want to remove all packages in the repository? [Y/N]

Parameter:
word.remove_files

If you answer Yes, the packages, logs, and cryptographic material for the Software Repository are removed.

Default: None

Are you absolutely sure you want to remove users' OGFS home and audit directories? (home and audit directories will only be removed if they are stored on the Software Repository server) (Y/N)?

Parameter:
ogfs.remove_home_dirs

Respond Yes if you want the uninstall to remove all users’ OGFS home and audit directories. Backup any information you want to retain.

Source: Variable

Default: None

Do you need to preserve any of the data in this database? [Y/N]

Parameter: truth.uninstall.needdata

Uninstalling the Model Repository permanently deletes all data in the database, therefore, the uninstallation process stops if you reply Yes to this prompt.

If you want to do an uninstallation, backup your data, run the uninstallation again and answer No to this prompt. Remember, the Installer does not preserve any data.

Default: Y

Are you sure you want to remove all data and schema from this database? [Y/N

Parameter: truth.uninstall.aresure

Uninstalling the Model Repository by responding Yes permanently deletes all data in the database. You can stop the uninstallation by responding No to this prompt.

Default: None

Would you like to preserve the database of cryptographic material? [Y/N]

Parameter:
save_crypto

If you answer Yes, the database of cryptographic material is saved. If you answer No, the material is deleted as part of the uninstallation.

Default: None

Would you like to preserve the HPELN content? (Y/N)

Parameter:
hpln.uninstall.keepcontent

Responding No uninstalls all HPE Live Network content.

Source: Variable

Default: None