Veritas InfoScale™ Operations Manager 8.0.2 Installation and Configuration Guide
- Section I. Installing and configuring Veritas InfoScale Operations Manager
- Planning your Veritas InfoScale Operations Manager installation
- Downloading Veritas InfoScale Operations Manager 8.0.2
- Typical Veritas InfoScale Operations Manager deployment configuration
- System requirements
- Installing, upgrading, and uninstalling Veritas InfoScale Operations Manager
- About installing Management Server
- About installing managed host
- About upgrading Management Server
- About backing up and restoring Veritas InfoScale Operations Manager data
- About upgrading managed hosts to Veritas InfoScale Operations Manager 8.0.2
- Configuring Veritas InfoScale Operations Manager in a high availability and disaster recovery environment
- Configuring the high availability feature in Veritas InfoScale Operations Manager
- Configuring a new Veritas InfoScale Operations Manager installation in high availability environment
- Configuring an existing Veritas InfoScale Operations Manager installation in high availability environment
- Configuring a new Veritas InfoScale Operations Manager installation in high availability environment
- Configuring Management Server in one-to-one DR environment
- Configuring Veritas 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 Veritas InfoScale Operations Manager
- Installing and uninstalling Veritas InfoScale Operations Manager add-ons
- Uploading a Veritas InfoScale Operations Manager add-on to the repository
- Installing a Veritas InfoScale Operations Manager add-on
- Uninstalling a Veritas InfoScale Operations Manager add-on
- Removing a Veritas InfoScale Operations Manager add-on from the repository
- Canceling deployment request for a Veritas InfoScale Operations Manager add-on
- Installing a Veritas InfoScale Operations Manager add-on on a specific managed host
- Uninstalling a Veritas InfoScale Operations Manager add-on from a specific managed host
- Planning your Veritas InfoScale Operations Manager installation
- Section II. Setting up the Management Server environment
- Basic Veritas 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 Veritas 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)
Configuring Veritas InfoScale Operations Manager Management Server and Agents in FIPS mode on Linux
The Federal Information Processing Standards (FIPS) 140-2 standard (commonly referred as FIPS mode) specifies the security requirements for cryptographic modules. The U.S. federal government has set an encryption standard for its non-military agencies, contractors, and service providers who work with the U.S. government must also follow FIPS. Hence, it is mandatory to configure and enable the FIPS 140-2 standard.
You can configure and enable FIPS mode for Veritas InfoScale Operations Manager Management Server and Agents. By default, FIPS-compliant mode is turned off when the Veritas InfoScale Operations Manager Management Server platform is installed. However, you can turn on FIPS mode for one or more nodes in your deployment. Configuration of Veritas InfoScale Operations Manager to run in FIPS mode includes the following sequence of process:
Enabling the FIPS mode on Veritas InfoScale Operations Manager Management Server (installed on Linux)
Enabling the FIPS mode on the third-party components that are used in Veritas InfoScale Operations Manager (Tomcat, Java)
Enabling the FIPS mode on Veritas InfoScale Operations Manager Agents (Linux, Solaris, and AIX)
FIPS mode can be enabled only with a fresh installation of Veritas InfoScale Operations Manager Server on a Linux system. Configuration of an existing Veritas InfoScale Operations Manager to run in FIPS mode is not supported in this release.
FIPS mode can be enabled only on Agents running on Linux, Solaris, or AIX. In this release, agents that are running on other operating systems cannot be configured in FIPS mode.
To verify if OpenSSL is installed, run the /usr/bin/openssl version command.
To enable FIPS mode on fresh installation of Veritas InfoScale Operations Manager Management Server on Linux
- Perform a fresh installation of Veritas InfoScale Operations Manager Management Server on Linux.
- Open the
VRTSatlocal.conf
configuration file that is located at/opt/VRTSsfmcs/sec/bin/.
- Under the Security\Authentication\Client section, enable the FIPS mode as follows:
[Security\Authentication\Client] "FipsMode"=dword:00000001 "ConnectTimeout"=dword:00000014
- Open a browser and configure Veritas InfoScale Operations Manager Management Server.
- Once the Veritas InfoScale Operations Manager Management Server configuration is successful, you may open the
VRTSatlocal.conf
configuration file that is located at/var/opt/VRTSsfmcs/sec/root/.VRTSat/profile/
and verify if the "FipsMode"=dword:00000001 is set.
To enable FIPS mode on Tomcat and Java components used in Veritas InfoScale Operations Manager
- Create a trusted Java KeyStore (JKS) for the Tomcat web server with imported certificates provided by a trusted Certificate Authority. For more information, see https://www.veritas.com/support/en_US/article.100026835
- Back up the following files:
/opt/VRTSsfmcs/webgui/jre/conf/security/java.security
/opt/VRTSsfmcs/webgui/tomcat/conf/server.xml
- Copy and overwrite the following files as follows:
cp /opt/VRTSsfmcs/webgui/jre/conf/security/java.security.fips /opt/VRTSsfmcs/webgui/jre/conf/security/java.security
cp/opt/VRTSsfmcs/webgui/tomcat/conf/server.xml.fips /opt/VRTSsfmcs/webgui/tomcat/conf/server.xml
cp /opt/VRTSsfmcs/webgui/tomcat/bin/setenv.sh.fips /opt/VRTSsfmcs/webgui/tomcat/bin/setenv.sh
- Edit the server.xml that is located at
/opt/VRTSsfmcs/webgui/tomcat/conf/
and add the CMS hostname (FQDN) in the Connector tag and Connector > SSLHostConfig tag respectively as follows:defaultSSLHostConfigName="<FQDN>"
hostName="<FQDN>"
- Convert the Java KeyStore (JKS) to the BC FIPS Keystore (BCFKS) format using the following command:
/opt/VRTSsfmcs/webgui/jre/bin/keytool -importkeystore -srckeystore .keystore -srcstoretype pkcs12 -deststoretype BCFKS -destkeystore .keystore -srcstorepass changeit -deststorepass changeit -providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider -J--module-path=/opt/VRTSsfmcs/webgui/jre/lib/ccj-3.0.1.jar -J--add-modules=ccj -J--add-exports=java.base/sun.security.provider=ccj -J--add-exports=java.base/sun.security.internal.spec=ccj
Note:
To verify the conversion of JKS to BCFKS use the following command: /opt/VRTSsfmcs/webgui/jre/bin/keytool -list -keystore /opt/VRTSsfmcs/webgui/tomcat/cert/.keystore -storepass changeit -storetype BCFKS -providername CCJ -providerpath "/opt/VRTSsfmcs/webgui/jre/lib/ext/ccj-3.0.1.jar" -providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider
- Restart VIOM web server using the following command:/opt/VRTSsfmcs/bin/vomsc --restart web
To enable FIPS mode on Veritas InfoScale Operations Manager Agents running on Linux, Solaris, AIX
- Open Veritas InfoScale Operations Manager Management Server in a browser.
- Add Linux, Solaris, or AIX Agents having Veritas InfoScale Operations Manager version 8.0, 8.0.2 to Veritas InfoScale Operations Manager Management Server.
The FIPS mode can be enabled only on Agents running on Linux, Solaris, or AIX having Veritas InfoScale Operations Manager version 8.0 and 8.0.2
Note:
In this release, agents that are running on other operating systems cannot be configured in FIPS mode.