Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Full SA Core configuration parameter listing
The SA Installer provides an Expert level interview which displays and allows modifications of all SA Core configuration parameters, some of which are not displayed during the Simple or Advanced interviews. Modifying these parameters requires extensive knowledge of SA Core capabilities and configuration and applying incorrect values will cause unexpected results.
The following table lists all SA Core configuration parameters as seen when you perform an installation using the Expert level interview.
For a detailed description of these parameters their values and ranges, see SA Core parameter reference.
Parameter |
Default Value |
Description |
---|---|---|
agw_proxy_port |
3001 |
This port must be open between the Agents in this facility and the Agent Gateway. Agents will contact the Agent Gateway on this port to request connections to core components |
bootagent.host |
Provisioning Boot Server host |
Specify the SA Provisioning Boot Server IP address or hostname. |
cast.admin_pwd |
Value of truth.oaPwd |
Specify the password for the SA admin user. 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. Password Restrictions: This password cannot contain spaces. |
cgw_admin_port |
8085 |
Specify the port for the administrative interface of the core Gateway. The Gateway has a browser-based administrative interface that allows you to view configuration and monitor traffic. |
cgw_proxy_port |
3002 |
Specify the port on which core components can contact this core Gateway to request tunneled connections. |
cgw_slice_tunnel_ |
2003 |
Specify the port on which the core Gateway on the Slice Component bundle will listen for connections from other Gateways (only used if the Infrastructure component bundle is installed on the same box as the Slice Component bundle). |
crypto.hash_algorithm |
SHA256 |
Please enter the hashing algorithm for SA cryptographic module. |
crypto.key_length |
2048 |
Specify the key length [2048 or 4096] used for hashing algorithm of SA cryptographic module. |
db.host |
none |
Specify the hostname/IP address of the Oracle database server. |
db.orahome |
|
Specify the path of the |
db.port |
1521 |
Specify the port on which the database listens for incoming connections. This value is recorded in the |
db.sid |
truth |
Specify the SID of the Oracle instance containing the Model Repository. |
decrypt_passwd |
Value of truth.oaPwd |
Specify the password for the 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. |
hpln_password |
none |
Specify the user password used to connect to the HPE Live Network (HPELN). Specify "none" if HPELN is not being configured. The value must follow the same rules as |
hpln_proxy |
3128 |
Specify the IP address or hostname of the proxy used to connect to the HPE Live Network (HPELN). Specify "none" if HPELN is not being configured or no proxy is needed to connect to HPE Live Network. The value must follow the following format: <protocol>://<host> or <protocol>: //<host>:<port>. If no |
hpln_proxy_pwd |
none |
Specify the password for the HPELN proxy user. Specify "none" if HPELN is not being configured, no proxy is configured, or no password is required. The invalid characters for this parameter follow the SA convention for usernames, such as no leading |
hpln_proxy_user |
none |
Specify the username for the HPELN proxy user. Specify "none" if HPELN is not being configured, no proxy is configured, or no username is required. The invalid characters for this parameter follow the SA convention for usernames, such as no leading |
hpln_user_name |
none |
Specify the username used to connect to the HPE Live Network (HPELN). Specify "none" if HPELN is not being configured. 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. |
masterCore.mgw_ |
2001 |
Specify the port on which Management Gateway in the First Core listens for connections from other Gateways (this value should match the value of the mgw_tunnel_listener_port parameter for the First Core (typically 2001). |
media_server.linux_ |
|
Specify the path to the location on the Media Server where the Linux media shouldbe placed when SA Provisioning components are installed. Note 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 SA 10.51 This directory must exist on the Media Server host. |
media_server.sunos_ |
|
Specify the path to the location on the Media Server where the Oracle Sun Solaris OS media should be placed when SA Provisioning components are installed. Note: 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 SA 10.51 This directory must exist on the Media Server host. |
media_server.windows_media |
|
Specify the path to the location on the Media Server where the Windows OS media should be placed when SA Provisioning components are installed. The SA Provisioning feature exports Windows OS media to SMB clients through a Samba share. Note 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 SA 10.51 This directory must exist on the Media Server host. |
media_server.windows_share_name |
OSMEDIA |
Specify the share name to use for the Windows media sharing server . Note Share names that are longer than 8 characters may give errors while browsing or may not be accessible to some older clients. |
media_server.windows_share_password |
Value of truth.oaPwd |
Specify a password to write-protect the Windows media share. The |
mgw_address |
none |
Specify the IP address of the Management Gateway. |
mgw_proxy_port |
3003 |
Specify the port number through which Core Components can request tunneled connections to other components through the Management Gateway. |
mgw_tunnel_listener_ |
2001 |
Specify the port on which the First and Subsequent Cores’ Management Gateways will listen for connections from other Core and Satellite gateways. |
ogfs.audit.host.ip |
Value of word.store.host |
Specify the IP address of the NFS server for the Global File System where audit streams will be stored. |
ogfs.audit.path |
|
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.host.ip |
Value of word.store.host |
Specify the IP address of the NFS server for the Opsware Global File System (user, home, and tmp directories). |
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 |
spoke.cachedir |
|
Specify the directory in which the Global File System service will cache snapshots and audits for quick access. This directory can require a large amount of disk space (4Gb by default) |
truth.aaaPwd |
Value of truth.oaPwd |
Enter database password for the |
truth.authDom |
MY.CUSTOMER.COM |
Enter the authorization domain used by the Access and Authentication Directory. |
truth.dcNm |
none |
Specify the short name of the facility in which the SA Installer is being run (no spaces). |
truth.dcSubDom |
Value of truth.dcNm |
Specify the subdomain for the facility in which the SA Installer is being run (lowercase, no spaces). The value must be a valid domain name (for example, SUB.DOMAIN.COM) and is limited to 50 characters. |
truth.detuserpwd |
Value of truth.oaPwd |
Specify the password to use for the DCML exchange tool (DET) user. |
truth.gcPwd |
Value of truth.oaPwd |
Specify database password for the |
truth.lcrepPwd |
Value of truth.oaPwd |
Specify the database password for the |
truth.oaPwd |
None |
Specify the password for the 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. |
truth.pubViewsPwd |
Value of truth.oaPwd |
Specify the database password for the |
truth.servicename |
truth.<value of truth.dcNm> |
Specify the service name of the Model Repository instance in the facility where SA Installer is being run. For Oracle, you can identify the service name by looking in the |
truth.sourcePath |
|
Specify the full path to the directory containing the When adding a facility to a multimaster mesh, the Model Respository (truth) data must be exported from the source facility, then copied to the destination facility. The destination directory path must be the same as the directory on the Model Repository (truth) server as the source directory path. |
truth.spinPwd |
Value of truth.oaPwd |
Specify the database password for the |
truth.tnsdir |
|
Specify the path to the TNS admin directory (where the |
truth.truthPwd |
Value of truth.oaPwd |
Specify the database password for the |
truth.twistPwd |
Value of truth.oaPwd |
Specify the database password for the |
truth.vaultPwd |
Value of truth.oaPwd |
Specify the database password for the |
twist.buildmgr.passwd |
Value of truth.oaPwd |
Specify the database password for the |
twist.default_gid |
70001 |
Specify the default UNIX Group ID to assign to SA users (number only, no less than 1024 and no greater than 90000000, with no leading zeros |
twist.integration.passwd |
Value of truth.oaPwd |
Specify the password for the |
twist.min_uid |
80001 |
Specify the minimum ID to use when assigning UNIX User IDs to Opsware users (number only, no less than 1024 and no greater than 90000000, with no leading zeros). UNIX UIDs are generated automatically for each SA user. UIDs are allocated counting up from the minimum specified in this parameter. |
twist.nasdata.host |
none |
Specify the hostname or IP address of the NA (Network Automation) server (Enter "none" if NA is not installed). |
windows_util_loc |
none |
Specify the path to the directory in which SA should install the Microsoft patching utilities or, if you have already manually downloaded the utilities, the path to the directory that contains the files. For a list of required files, press Ctrl-I at the prompt. Enter "none" if you do not wish to install the utilities. |
word.enable_content_mirroring |
Y(es) |
Enable/disable mirroring of all Software Repository content in a Multimaster Mesh. |
word.store.host |
Software Repository Storage host |
Specify the IP address of the NFS server for the Software Repository. For satellite installs, enter the IP address of the Software Repository Cache. Storage for the Software Repository will be mounted from the server specified in this parameter.. |
word.store.path |
|
Specify the absolute path on the NFS server for the Software Repository. Storage for the Software Repository will be mounted from this directory on the server specified by the |
word_root |
|
Specify the mount point for the Software Repository root directory. For satellite installs, enter the root directory of the Software Repository Cache. Package Repository contents will be mounted from the server and directory specified by |
word_tmp_dir |
|
Specify the directory where the Package Repository will temporarily place content during uploads. |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to hpe_sa_docs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: