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)
Prerequisites for configuring a Management Server in HA-DR environment
Before you configure Veritas InfoScale Operations Manager in the high availability and disaster recovery environment, ensure the following:
A virtual IP and a virtual host name are available for installing and using Veritas InfoScale Operations Manager in high availability and disaster recovery environment. This IP is used and configured in VCS for SFM_Services_IP and should not be shared with other applications.
Storage Foundation HA 8.0, or later, and VCS cluster are installed on the hosts that you want to designate as Node1 and Node2 in local site (Site A) and Node3 and Node4 in remote site (Site B). Also, Node1 in Site A and Node3 in Site B are considered as primary nodes. In case of HADR configuration using asymmetrical nodes, only one node is configured on the remote site (Node3 ).
Global Cluster Option (GCO) is enabled in VCS in Site A and Site B. For more information on enabling GCO, see Cluster Server Administrator's Guide.
Volume Replicator (VVR) is configured in Site A and Site B at VxVM level. For more information on configuring VVR, refer to the Veritas Volume Replicator Administrator's Guide.
All the nodes on which you want to configure Veritas InfoScale Operations Manager in the high availability environment must report synchronized Universal Time Clock (UTC/UC) time.
You must specify the database location. You can either use the default database location
/var/opt/VTRSsfmcs/db
or specify another location. If you specify the location other than the default database location, you must make sure that it is not part of the shared file system that is used for failover. Later, the Veritas InfoScale Operations Manager DR script moves the database to the shared file system.If you do not use DNS Agent, you must add the host names to the
/etc/hosts
file.The SFM_Services and the SFM_SStore base service groups that are created on Site A and Site B should have similar attributes and values, except for SFM_SStore_IP.
Use different virtual IP addresses for GCO IP and SFM_Services_IP.
The virtual host name that is used on all domains in Site A and Site B are the same.
The SFM_Services base service group must be configured as Global Service group between the two clusters.
SFM_SStore service is online on any of the nodes before you execute the disaster recovery script.
You need to create a Storage Foundation disk group, file system, and a volume for the data with identical names on all the nodes. Use VxVM and VxFS to create the file system and volume. The disk group, file system, and volume are used to configure the Veritas InfoScale Operations Manager database in high availability environment.
For more information on creating disk groups and volume, see Veritas Storage Foundation Administrator's Guide.