InfoScale™ Operations Manager 9.0 Installation and Configuration Guide
- Section I. Installing and configuring Arctera InfoScale Operations Manager
- Planning your Arctera InfoScale Operations Manager installation
- Downloading Arctera InfoScale Operations Manager 9.0
- Typical Arctera InfoScale Operations Manager deployment configuration
- System requirements
- Installing, upgrading, and uninstalling Arctera InfoScale Operations Manager
- About installing Management Server
- About installing managed host
- About upgrading the Management Server
- About backing up and restoring Arctera InfoScale Operations Manager data
- About upgrading managed hosts to Arctera InfoScale Operations Manager 9.0
- Configuring Arctera InfoScale Operations Manager in a high availability and disaster recovery environment
- Configuring the high availability feature in Arctera InfoScale Operations Manager
- Configuring a new Arctera InfoScale Operations Manager installation in high availability environment
- Configuring an existing Arctera InfoScale Operations Manager installation in high availability environment
- Configuring a new Arctera InfoScale Operations Manager installation in high availability environment
- Configuring Management Server in one-to-one DR environment
- Configuring Arctera InfoScale Operations Manager in high availability and disaster recovery environment
- About upgrading the high availability configurations
- About upgrading the high availability and disaster recovery configurations
- Configuring the high availability feature in Arctera InfoScale Operations Manager
- Installing and uninstalling Arctera InfoScale Operations Manager add-ons
- Uploading a Arctera InfoScale Operations Manager add-on to the repository
- Installing a Arctera InfoScale Operations Manager add-on
- Uninstalling a Arctera InfoScale Operations Manager add-on
- Removing a Arctera InfoScale Operations Manager add-on from the repository
- Canceling deployment request for a Arctera InfoScale Operations Manager add-on
- Installing a Arctera InfoScale Operations Manager add-on on a specific managed host
- Uninstalling a Arctera InfoScale Operations Manager add-on from a specific managed host
- Planning your Arctera InfoScale Operations Manager installation
- Section II. Setting up the Management Server environment
- Basic Arctera InfoScale Operations Manager tasks
- Adding and managing hosts
- Overview of host discovery
- Overview of agentless discovery
- About installing OpenSSH on a UNIX host
- Adding the managed hosts to Management Server using an agent configuration
- Adding the managed hosts to Management Server using an agentless configuration
- Adding Agentless hosts to the Management Server using Profile
- Editing the agentless host configuration
- Setting up user access
- Adding Lightweight Directory Access Protocol or Active Directory-based authentication on Management Server
- Configuring LDAP using CLI
- Setting up fault monitoring
- Creating rules in the Management Server perspective
- Editing rules in the Management Server perspective
- Deleting rules in the Management Server perspective
- Enabling rules in the Management Server perspective
- Disabling rules in the Management Server perspective
- Suppressing faults in the Management Server perspective
- Suppressing a fault definition in the Management Server perspective
- Setting up virtualization environment discovery
- Setting up near real-time discovery of VMware events
- Requirements for discovering the Solaris zones
- Adding a virtualization server
- Editing a virtualization discovery configuration
- Refreshing a virtualization discovery configuration
- Deploying hot fixes, packages, and patches
- Installing a Arctera InfoScale Operations Manager hot fix, package, or patch
- Configuring Management Server settings
- Configuring SNMP trap settings for alert notifications
- Setting up extended attributes
- Viewing information on the Management Server environment
- Appendix A. Troubleshooting
- Management Server (MS)
- Managed host (MH)
- Management Server (MS)
Importing third-party certificates for xprtld
Arctera InfoScale Operations Manager (VIOM)lets you import third-party certificates for the xprtld service on Management Servers that run on Linux. It also lets you import third-party certificates for the agents on AIX, Linux, and Solaris, provided that the agent version is 7.3.1 or later. VIOM supports the use of a third-party certificate without a passphrase for xprtld that runs on port 5634. However, it only supports 2048-bit certificates.
To generate a third-party certificate for xprtld
- Use the openssl command as follows to generate a private key and a certificate signing request (CSR):
openssl req -newkey rsa:2048 -nodes -keyout sfmAgentPrivateKeyFileName -out sfmAgentCSRFileName
For example:
openssl req -newkey rsa:2048 -nodes -keyout sfm_agent.private.key -out sfm_agent.csr
- The openssl command prompts you to provide some information that is to be added to the CSR. Specify the exact values that are provided in the following example:
Country Name (2 letter code) [XX]: . State or Province Name (full name) []: . Locality Name (eg, city) [Default City]: . Organization Name (eg, company) [Default Company Ltd]: vx Organizational Unit Name (eg, section) []: sfm_domain@nameOfCMS Common Name (eg, your name or your server's hostname) []: sfm_agent Email Address []:
Note:
The nameOfCMS value should match exactly with the value of the cs_config_name attribute that is present in the
/etc/default/sfm_resolv.conf
file on the Central Management Server (CMS).Specify the exact values that are provided in the following example for this additional information that is also to be sent with the CSR:
A challenge password []: . An optional company name []:
- Send the CSR file - for example,
sfm_agent.csr -
to your certificate signing authority and ask them to provide the corresponding certificate. The certificate should be provided in thepem
format, along with the intermediate CA certificate and the root CA certificate, and it should support SSL clients. Arctera recommends that you assign a validity of 10 years to the certificate, or the maximum duration possible. - Optionally, run the following command to verify the purpose of the certificate, including the support for SSL clients:
openssl x509 -purpose -noout -in sfmAgentCertFileName
For example:
openssl x509 -purpose -noout -in sfm_agent.cert.pem
Certificate purposes:
SSL client : Yes SSL client CA :No
SSL server : Yes SSL server CA :No
Netscape SSL server : Yes Netscape SSL server CA : No
- Ensure that you have the following files ready before you import the certification on a Management Server:
File
Sample file name
Private key file for
sfm_agent
sfm_agent.private.key
Certificate file for
sfm_agent
sfm_agent.cert.pem
Certificate file for intermediate CA
intermediate.cert.pem
Certificate file for root CA
ca.cert.pem
To import a third-party certificate on a Management Server and on the agents
Copy all the files that are mentioned in the last step of the previous procedure on the Management Server at the appropriate location, for example:
/viom/certs/
.Run the following command to import the certificates:
/opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/util/import_sfm_agent_certificate.pl --import_sfm_agent_cert --sfm_agent_certificate=/viom/certs/sfmAgentCertificateFileName --sfm_agent_privatekey=/viom/certs/sfmAgentPrivateKeyFileName --subCA_certificate=/viom/certs/intermediateCertificateFileName --rootCA_certificate=/viom/certs/caCertificateFileName
For example:
/opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/util/import_sfm_agent_certificate.pl --import_sfm_agent_cert --sfm_agent_certificate=/viom/certs/sfm_agent.cert.pem --sfm_agent_privatekey=/viom/certs/sfm_agent.private.key --subCA_certificate=/viom/certs/intermediate.cert.pem --rootCA_certificate=/viom/certs/ca.cert.pem
The certificates are imported on the agents automatically.
Follow the instructions and provide the appropriate input at the prompts that the command displays.
You may encounter certain situations that you can address as follows:
The certificate import process restarts all the VIOM services on the Management Server and the xprtld service on all the managed hosts. After the certificate is successfully imported, if a managed host does not yet use the new certificate, check whether that host is registered on multiple Management Servers. If so, unconfigure the managed host from the Management Servers other than the one on which this new certificate was installed, and then restart the xprtld service on the host.
The certificate cannot be imported on the managed hosts that are on VIOM 7.3 or an earlier version. Upgrade such hosts to VIOM 8.0 or a later supported version (refer to the Arctera InfoScale Operations Manager Hardware and Software Compatibility Lists document), and then run the command to import the certificate again.
The certificate cannot be imported on managed hosts that are unreachable from the Management Server. After the import process is complete, address the connectivity issue for the managed hosts that were unreachable. Then, add the managed hosts to the Management Server again; the new certificate gets automatically installed on the managed hosts.