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 |
|
Install SA Agent with Agent bootstrap certificate and update to third-party mode after installation using ADT
Phase 1: Install the SA Agent with the SA Agent Bootstrap certificate
- Launch the SA Client and connect to an SA Core installed in third-party certificate mode.
- Go to Administration > System Configuration > Configuration Parameters > Data Access Engine (spin) and make sure the
spin.agent.bootstrap_enabled
parameter is set to1
. For more information on this parameter, see The spin.agent.bootstrap_enabled parameter. - Click the Save button and restart the SA Spin component if you have any pending changes.
- Go to Devices > Servers > SA Agent installation and scan for unmanaged servers using the IP or the hostname of the server. Select the unmanaged servers on which you want to install the SA Agent.
The server icon indicates agentless servers. If the servers are not powered on, the Install SA Agent option is disabled. See Server status icons. -
Specify your login and installation options to control the way the Agent is installed on the server. See Install the SA Agent using ADT for information on these options.
- In the Options section, enable the Verify prerequisites, copy installer, and install agent option. This downloads the Agent binary and the bootstrap certificate (agent.srv) file to your server, and runs the Agent install command.
- Make sure that
cert_gen_enabled
parameter is not specified in the Advanced > Extra installer options field. - Click Start Job. When the Agent installation completes, the SA Client displays the results and updates the status icons for the servers.
Phase 2: Update your SA Agent certificate to use third-party certificate mode
After installing the SA Agent with the SA self-signed bootstrap certificate, generate a CSR for your CA, and import the third-party certificate using SA Agent scripts. This enables you to switch from SA Agent bootstrap certification to third-party certificate mode.
Alternatively, you can use the Recertify Agent Program Extension to automate some of the steps below. For more information, see
- Log into the managed server using a remote shell. On UNIX, log in as root. On Windows, log in as administrator.
- Remove any existing *.csr or .*crt files from your temporary PKI directory:
- Linux:
/var/tmp/pki
- Windows:
C:\Windows\Temp\PKI
-
Launch the following script to generate the Agent's CSR (agent.csr file) and the certificate's private key (agent.key file):
- Linux script:
/opt/opsware/agent/pylibs/cog/generate_csr
- Windows script:
C:\Program Files\Opsware\agent\pylibs\cog\generate_csr.bat
Optionally, you can add the--crypto_dir <your crypto folder>
parameter to generate the CSR in a customcrypto
folder. Otherwise, the script creates the CSR in the temporaryPKI
folder. - Linux script:
- Collect the CSR file from your custom
crypto
folder created in step 3 or from the defaultPKI
folder: - Submit the CSR to your CA and import the resulting third-party certificate using the following script:
/opt/opsware/agent/pylibs/cog/import_cert
.
This generates a .pkcs12 password-protected file under:- Linux:
/var/opt/opsware/crypto/agent/agent.p12
- Windows:
C:\Program Files\Common Files\Opsware\crypto\agent\agent.p12
- Linux:
- Restart the SA Agent to finalize updating the SA Agent certificate to third-party certificate mode.
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: