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 |
|
Agent Installer Options
Use the options listed below with the Agent Installer command. You must use either the --opsw_gw_addr
option or the --no_opsw_gw
option. All others are optional.
Option |
Description |
---|---|
--auth_path |
Specifies the complete path to the file that contains the trusted authorities in PEM format. |
--coreinstall |
Install initialization scripts in the proper location for the core server. |
--customer_id <customer> |
Assigns the managed server to the specified customer. This option requires the |
--del_opsw_gw_addr_list |
Deletes the list of gateway addresses. |
|
Forces the Agent to be installed even if environment check errors occur. This option is useful when the server is not connected to an SA core. When using the |
--fingerprint |
Specifies the fingerprint of the core certificate. If you specify a value for this option, the Agent installer will verify that the Certificate Authority certificate used to sign the core's SSL certificate matches the value you provided. Specifying a value for this option increases security during the Agent installation process by ensuring that the Agent attaches itself to the correct core. To obtain the correct value for the core certificate fingerprint option, log on to the core as root (you may need to have an SA System Administrator perform this task for you) and run the following command:
The output looks like the following:
The fingerprint is the string of hexadecimal numbers following the equal sign:
|
--force_full_hw_reg |
Causes a full hardware registration to be performed on the server after the Agent is installed. The default is for a minimal hardware registration to be performed. For more information, see Software and hardware inventory. |
--force_sw_reg |
Causes a software registration to be performed on the server after the Agent is installed. By default, the software registration is not performed until the regularly scheduled time. For more information, see Software and hardware inventory. |
--force_virt_reg |
Force full virtualization registration (default is no registration). |
-h |
Displays all the options available with the Agent installer command. |
|
Specifies the path and file name of the Agent installer log file. By default, the current directory is set as the path. By default, the log file is:
|
|
Sets the log level for log messages. The level |
--no_anonymous_ssl |
Disables anonymous SSL. This option configures the Agent so that browsers cannot connect to its web interface without a valid certificate. This option applies to dormant Agents only. If specified, the dormant Agent will require clients that connect to its web interface to have a valid certificate. |
--no_check_reachability |
Suppresses a reachability check. The default is to perform a reachability check during fresh installs, and not to perform this check during upgrades. |
--no_open_fw |
Does not open the Windows firewall to communicate with the SA core. By default, the Agent installer will modify the Windows firewall configuration on Windows 2003 (r2) or Windows 2008 servers to allow the core to contact the managed server on port 1002. If you specify this option, the firewall configuration will not be modified and the server may not be manageable by SA. |
--no_opsw_gw |
Specifies that no gateway is needed. Either this option or the |
--no_start_agent |
Prevents the Agent from starting after installation. By default, the Agent is started immediately after installation. See also Starting an Agent After Installation. |
--opsw_gw_addr <host:port> |
Specifies the host and port number of the gateways used during Agent installation. Either this option or |
--password <password> |
Specifies the password for the user specified in the |
|
Causes the server to be rebooted after the Agent is installed, but only if required. During Agent installation on a Windows server, the Agent installer copies the file ogshcap.dll to the following location:
If the file is open or is in use, the Agent installer is unable to copy this file. The Agent installer then asks the user whether to restart the machine and copies the file after restart. You can also specify |
--remediate |
Remediates the server against any software policies attached to the server, including all software policies specified in the |
--resetconf -r |
Resets the Agent configuration file to the default settings. |
|
Specifies the path to the RPM handler to use for RPM operations. Use this option, when an RPM handler is already installed on the server. If an RPM handler is not already installed on the server, use the It is not necessary to use this option with the |
--settime -t |
Sets the time on the server to that of the core. If the managed server’s clock is significantly ahead of the clock on the SA Core, the clock on the managed server will be set back. Since this can cause problems, do not use the If a managed server’s clock is significantly behind the clock on the core, the Agent installation might fail. To install an Agent successfully, use the |
|
Attaches the software policy <ID> to the server. <ID> must be the name of a software policy in the SA Library. If you want to remediate the software policy immediately, specify the |
--spin_host |
Specify the host name or IP address of the Data Access Engine component. If you specify this option, you must also specify the |
--username <name> |
Specifies an SA user name. This option requires the |
|
Installs Windows MSI 2.0 along with the Agent. If Windows MSI 2.0 is already installed, this option has no effect. Works with Windows 2000 and Windows 2003 or later. |
|
Installs the RPM handler with the Agent. By default, an Agent is not installed. It is recommended that you always include the Use this option only with the Agent installers for Solaris 5.8, 5.9 and 5.10. On Solaris 5.8 and 5.9, RPM 3.0.6 is installed in the directory On AIX, RPM 3.0.5 is installed in the directory If an RPM handler is already installed, you can use the |
|
Specifies the path to the Agent installer temporary working directory. Use this option if the default working directory causes problems with installation. |
Starting an Agent After Installation
You can manually start the Agent on a server as follows.
UNIX:
/etc/init.d/opsware-agent start
HP-UX:
/sbin/init.d/opsware-agent start
AIX:
/etc/rc.d/init.d/opsware-agent start
Windows:
net start opswareagent
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: